IP Library Granted Patent US 11,720,703
Granted Patent B1
US 11,720,703 · App. 17/852,212 · Granted Aug 8, 2023

Online software platform (OSP) querying client data about relationship instances for application of permission digital rules in addition to resource digital rules for the relationship instances

Inventors: Mark Janzen (Wichita, KS); Gregory T. Kavounas (Bellevue, WA); Charles M. Morrisette (Everett, WA); Rohit Ghule (Pune Maharashatra, IN)
Assignee: Avalara, Inc.
G06F21/6227G06F21/629
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,720,703
App. No.
17/852,212
Granted
Aug 8, 2023
Kind
B1
Abstract

Systems and methods electronically determine whether a dataset is permitted or excluded based on permission digital rules. Primary entities often are required, or choose to, exclude proposed relationship instances with secondary entities. The systems and methods described herein allow permission digital rules to be defined and applied to datasets obtained from secondary entities relating to a proposed relationship instance with the primary entity, and permit or exclude a resource from being produced for the dataset based on the permission digital rules.

Claims (87)

1. A system, comprising:

one or more processors; and

one or more non-transitory computer-readable storage media coupled to the one or more processors, the media having stored thereon instructions which, when executed by the one or more processors, result in operations including at least:

receiving input indicating an item;

identifying a primary entity and a secondary entity which are each parties to a proposed relationship instance involving the item;

generating a dataset based on the item, the primary entity, and the secondary entity, the dataset indicating the proposed relationship instance between the primary entity and the secondary entity;

transmitting the dataset to an online service platform (OSP);

receiving, from the OSP, a response, wherein the response includes an indication of whether the dataset is excluded from being used to produce a resource associated with the proposed relationship instance due to the secondary entity being a participant in the relationship instance;

if it is indicated that the dataset is not thus excluded, then:

accessing, from the response, a resource associated with the proposed relationship instance; and

taking an action to facilitate the proposed relationship instance based on the accessed resource; and

else if it is indicated that the dataset is thus excluded, then:

taking an action to prevent the proposed relationship instance.

2. The system of claim 1 , in which the operations further include:

transmitting one or more permission digital rules to the OSP, the permission digital rules being usable to determine whether a dataset should be excluded from being used to produce the resource associated with the proposed relationship instance due to the secondary entity being a participant in the relationship instance.

3. The system of claim 2 , in which the operations further include:

receiving input indicating the one or more permission digital rules.

4. The system of claim 1 , in which the operations further include:

transmitting a list of one or more distinguished secondary entities to the OSP, in which the list of one or more distinguished secondary entities is usable to determine whether a dataset should be excluded from being used to produce the resource associated with the proposed relationship instance due to the secondary entity being a participant in the relationship instance.

5. The system of claim 4 , in which the operations further include:

receiving input indicating that another secondary entity should be added to the list; and

transmitting an indication to the OSP that the secondary entity should be added to the list, responsive to the input indicating that the other secondary entity should be added to the list.

6. The system of claim 4 , in which the operations further include:

receiving input indicating that another secondary entity should be removed from the list; and

transmitting an indication to the OSP that the secondary entity should be removed from the list, responsive to the input indicating that the other secondary entity should be removed from the list.

7. The system of claim 4 , in which the operations further include:

receiving input indicating that another secondary entity should be removed from the list after a predetermined period of time; and

transmitting an indication to the OSP that the secondary entity should be removed from the list after the predetermined period of time has elapsed, responsive to the input indicating that the secondary entity should be removed from the list after a predetermined period of time.

8. The system of claim 1 , in which the operations further include:

transmitting a safe list of one or more safe secondary entities deemed safe and that are not to be excluded to the OSP.

9. The system of claim 1 , in which the operations further include:

identifying a base value for the generated dataset, based on at least the input indicating the item;

including the base value in the generated dataset; and

receiving the response from the OSP, wherein the response further includes the base value of the dataset.

10. The system of claim 1 , in which the operations further include:

identifying a base value for the generated dataset, based on at least the input indicating the item;

including the base value in the generated dataset; and

receiving the response from the OSP, wherein the response further includes a negative of the base value of the dataset.

11. A method in a primary entity computing device, the method including:

receiving, via input, an indication of an item;

identifying, by the primary entity computing device, a primary entity and a secondary entity which are parties to a proposed relationship instance involving the item;

generating, by the primary entity computing device, a dataset based on the item, the primary entity, and the secondary entity, the dataset indicating the proposed relationship instance between the primary entity and the secondary entity;

transmitting, by the primary entity computing device, the dataset to an online service platform (OSP);

receiving, from the OSP, a response, wherein the response includes an indication of whether the dataset is excluded from being used to produce a resource associated with the proposed relationship instance due to the secondary entity being a participant in the relationship instance;

if it is indicated that the dataset is not thus excluded, then:

accessing, from the response, by the primary entity computing device, a resource associated with the proposed relationship instance; and

taking an action, by the primary entity computing device, to facilitate the proposed relationship instance based on the accessed resource; and

else if it is indicated that the dataset is thus excluded, then:

taking an action, by the primary entity computing device, to prevent the proposed relationship instance.

12. The method of claim 11 , in which the method further includes:

transmitting, by the primary entity computing device, one or more permission digital rules to the OSP, the permission digital rules being usable to determine whether a dataset should be excluded from being used to produce the resource associated with the proposed relationship instance due to the secondary entity being a participant in the relationship instance.

13. The method of claim 12 , in which the method further includes:

receiving, by the primary entity computing device, input indicating the one or more permission digital rules.

14. The method of claim 11 , in which the method further includes:

identifying, by the primary entity computing device, a base value for the generated dataset, based on at least the input indicating the item;

including, by the primary entity computing device, the base value in the generated dataset; and

receiving, by the primary entity computing device, the response from the OSP, wherein the response further includes the base value of the dataset.

15. The method of claim 11 , in which the method further includes:

identifying, by the primary entity computing device, a base value for the generated dataset, based on at least the input indicating the item;

including, by the primary entity computing device, the base value in the generated dataset; and

receiving, by the primary entity computing device, the response from the OSP, wherein the response further includes a negative of the base value of the dataset.

16. The method of claim 11 , in which the method further includes:

identifying, by the primary entity computing device, a base value for the generated dataset, based on at least the input indicating the item;

including, by the primary entity computing device, the base value in the generated dataset; and

receiving, by the primary entity computing device, the response from the OSP, wherein the response further includes the base value of the dataset.

17. A non-transitory computer-readable storage medium having computer-executable instructions stored thereon that, when executed by at least one processor, cause a computing system to perform operations including:

receiving input indicating an item;

identifying a primary entity and a secondary entity which are parties to a proposed relationship instance involving the item;

generating a dataset based on the item, the primary entity, and the secondary entity, the dataset indicating the proposed relationship instance between the primary entity and the secondary entity;

transmitting the dataset to an online service platform (OSP);

receiving, a response from the OSP, wherein the response includes an indication of whether the dataset is excluded from being used to produce a resource associated with the proposed relationship instance due to the secondary entity being a participant in the relationship instance;

if it is indicated that the dataset is not thus excluded, then:

accessing, from the response, a resource associated with the proposed relationship instance; and

taking an action to facilitate the proposed relationship instance based on the accessed resource; and

else if it is indicated that the dataset is thus excluded, then:

taking an action to prevent the proposed relationship instance.

18. The non-transitory computer-readable storage medium of claim 17 , in which the operations further include:

transmitting a list of one or more distinguished secondary entities to the OSP, in which the list of one or more distinguished secondary entities is usable to determine whether a dataset should be excluded from being used to produce the resource associated with the proposed relationship instance due to the secondary entity being a participant in the relationship instance.

19. The non-transitory computer-readable storage medium of claim 18 , in which the operations further include:

receiving input indicating that another secondary entity should be added to the list; and

transmitting an indication to the OSP that the secondary entity should be added to the list, responsive to the input indicating that the other secondary entity should be added to the list.

20. The non-transitory computer-readable storage medium of claim 18 , in which the operations further include:

receiving input indicating that another secondary entity should be removed from the list; and

transmitting an indication to the OSP that the secondary entity should be removed from the list, responsive to the input indicating that the other secondary entity should be removed from the list.

21. The non-transitory computer-readable storage medium of claim 18 , in which the operations further include:

receiving input indicating that another secondary entity should be removed from the list after a predetermined period of time; and

transmitting an indication to the OSP that the secondary entity should be removed from the list after the predetermined period of time has elapsed, responsive to the input indicating that the secondary entity should be removed from the list after a predetermined period of time.

Assignments (4)
SECURITY INTEREST Recorded Mar 28, 2025
From: AVALARA, INC.; EDISON VAULT, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 070671/0097 →
RELEASE OF SECURITY INTEREST Recorded Mar 28, 2025
From: BLUE OWL CREDIT INCOME CORP. (F/K/A OWL ROCK CORE INCOME CORP.), AS COLLATERAL AGENT
To: AVALARA, INC.
Reel/Frame 070671/0413 →
SECURITY INTEREST Recorded Dec 15, 2023
From: AVALARA, INC.
To: BLUE OWL CREDIT INCOME CORP., AS COLLATERAL AGENT
Reel/Frame 065885/0119 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2023
From: JANZEN, MARK; KAVOUNAS, GREGORY T.; MORRISETTE, CHARLES M.; GHULE, ROHIT
To: AVALARA, INC.
Reel/Frame 063556/0227 →