Dynamic filtering and precision alteration of query responses responsive to request load
US-11232225-B2 · Jan 25, 2022 · US
US11921879B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11921879-B2 |
| Application number | US-202217583059-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 24, 2022 |
| Priority date | Jun 11, 2014 |
| Publication date | Mar 5, 2024 |
| Grant date | Mar 5, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments relate to processing a request from a user device for access rights for a resource. An access management system can send a request to query a (e.g., cached or authoritative) data store for available access rights. The query may include an exact-match or fuzzy query. A set of access-right results responsive to the query can be identified. The system may transmit a communication to the user device that identifies the set, or a subset thereof. Upon receiving a selection of a result, the system can facilitate assigning access rights corresponding to the identified result to the user. In some instances, a level of precision at which a characteristic of an access-right result is identified and/or whether or how access rights are held depends on a request load.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for facilitating assignments of tickets for on-sale events by automatically modifying received requests, the computer-implemented method comprising: receiving a plurality of requests for tickets of an on-sale event, wherein: the plurality of requests for tickets comprises a plurality of constraints for available tickets, and the plurality of constraints represents characteristics of the available tickets; generating a set of queries for querying a ticket data store for the available tickets in response to reception of the plurality of requests for tickets, wherein a first query from the set of queries corresponds to a first request of the plurality of requests and a second query from the set of queries corresponds to a second request of the plurality of requests; prioritizing the first request and the second request from the plurality of requests based on a parameter of each of the plurality of requests, wherein the parameter includes a quantity of tickets associated with each of the first request and the second request; prioritizing a set of constraints of the plurality of constraints for the first request and the second request based on a type of constraint that can be expanded, user input, or historical data associated with the set of constraints, expanding a range of a first constraint of the first request based on a priority of the first constraint to produce a second constraint; expanding a range of a third constraint of the second request based on a priority of the third constraint to produce a fourth constraint, wherein a type of the first constraint is different from a type of the third constraint; assigning a performance order to the set of queries for execution of the set of queries based on the set of constraints and expanding of the first constraint and the third constraint to produce a performed order of a set of queries; receiving query responses for the performed order of the set of queries including a plurality of temporarily held tickets based on the order of execution of the set of queries, wherein the plurality of temporarily held tickets include first tickets that satisfy the second constraint corresponding to the first request and second tickets that satisfy the fourth constraint corresponding to the second request; transmitting a notification over a network based on the query responses, wherein the notification includes data for identification of the plurality of temporarily held tickets; receiving user responses from a plurality of user devices for the plurality of temporarily held tickets based on the notification; and assigning the plurality of temporarily held tickets to corresponding user devices of the plurality of user devices based on the user responses. 2. The computer-implemented method, as recited in claim 1 , further comprising prioritizing the first request and the second request based on a sequence of receiving the first request and the second request among the plurality of requests, a demand of a number of tickets included in the first request and the second request, or a user profile associated with the first request and the second request. 3. The computer-implemented method, as recited in claim 1 , wherein a fifth constraint of the plurality of constraints having higher priority has less probability of expansion as compared to a sixth constraint of the plurality of constraints having lower priority. 4. The computer-implemented method, as recited in claim 1 , further comprising identifying a load-related variable associated with the tickets, the load-related variable identifies a volume of requests received from the plurality of user devices. 5. The computer-implemented method, as recited in claim 4 , further comprising determining the expanding of the range of the first constraint and the third constraint based on the load-related variable. 6. The computer-implemented method, as recited in claim 1 , further comprising determining a level of precision, from a plurality of levels of precision, for representing the characteristics of the available tickets of the query responses, wherein: the level of precision being determined individually for each query of the set of queries, the level of precision being determined based on a request load existing at a time of receiving the set of queries during a time period, and the level of precision indicates how precisely the characteristics of the available tickets of the query responses is presented to the plurality of user devices in response to the plurality of requests. 7. The computer-implemented method, as recited in claim 1 , further comprising: determining a hold variable based on an identified load-related variable, wherein: the hold variable is selected from a plurality of hold variables, and each hold variable of the plurality of hold variables indicating whether an available ticket from the available tickets associated with a query response of the query responses is to be held for a corresponding user device of the plurality of user devices; and executing a hold on the available ticket associated with the query response in accordance with the hold variable. 8. A system for facilitating assignments of access-rights for resources by facilitating query execution, the system comprising: a processor configured to: receive a plurality of requests for tickets of an on-sale event, wherein: the plurality of requests for tickets comprises a plurality of constraints for available tickets, and the plurality of constraints represents characteristics of the available tickets; generate a set of queries for querying a ticket data store for the available tickets in response to reception of the plurality of requests for tickets, wherein a first query from the set of queries corresponds to a first request of the plurality of requests and a second query from the set of queries corresponds to a second request of the plurality of requests; prioritize the first request and the second request from the plurality of requests based on a parameter of each of the plurality of requests, wherein the parameter includes a quantity of tickets associated with each of the first request and the second request; prioritize a set of constraints of the plurality of constraints for the first request and the second request based on a type of constraint that can be expanded, user input, or historical data associated with the set of constraints; expand a range of a first constraint of the first request based on a priority of the first constraint to produce a second constraint; expand a range of a third constraint of the second request based on a priority of the third constraint to produce a fourth constraint, wherein a type of the first constraint is different from a type of the third constraint; assign a performance order to the set of queries for execution of the set of queries based on the set of constraints and expand the first constraint and the third constraint to produce a performed order of a set of queries; receive query responses for the performed order of the set of queries including a plurality of temporarily held tickets based on the order of execution of the set of queries, wherein the plurality of temporarily held tickets include first tickets that satisfy the second constraint corresponding to the first request and second tickets that satisfy the fourth constraint corresponding to the second request; transmit a notification over a network based on the query responses, wherein the notification includes data for identification of the plurality of temporarily held tickets; receive user responses from a plurality of user devices for the plurality of temporarily held tickets based on the notification; and assign th
where protection concerns the structure of data, e.g. records, types, queries · CPC title
Support for shared access to files; File sharing support · CPC title
Search customisation based on user profiles and personalisation · CPC title
Protecting access to data via a platform, e.g. using keys or access control rules · CPC title
Multiple levels of security · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.