Receiving secured data using optical codes and urls
US-2024214391-A1 · Jun 27, 2024 · US
US9208244B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9208244-B2 |
| Application number | US-201113329145-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 16, 2011 |
| Priority date | Dec 16, 2011 |
| Publication date | Dec 8, 2015 |
| Grant date | Dec 8, 2015 |
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.
The subject disclosure relates to techniques for referencing a change in data utilizing a network resource locator. An interface component can receive one or more requests that are associated with a data set from a client, and send, based on the one or more requests, a network resource locator and at least one portion of the data set to the client. Further, a data service component can compute a parameter that is associated with a change of the data set, and include the parameter in the network resource locator. In other embodiments, the data service component can receive a request utilizing the network resource locator, determine the change of the data set based on the parameter, and send the change of the data set to the client.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving, by a data service component of at least one computing device, a first request that is associated with a data set from a client; and in response to the receiving the first request, computing a token for referencing a change of the data set, and communicating one or more portions of the data set and a link including the token to the client. 2. The method of claim 1 , wherein the computing the token further includes at least one of: determining the token prior to computing a first portion of the one or more portions or communicating the first portion to the client; or determining a change identifier that is associated with a most recent detected change of the data set. 3. The method of claim 1 , wherein the computing the token further includes determining a timestamp enumerating a time that is associated with the change. 4. The method of claim 1 , wherein the computing the token further includes determining a date of the change. 5. The method of claim 1 , wherein the communicating the one or more portions of the data further includes: sending a first portion of the one or more portions and a first uniform resource locator (URL) including the token to the client; and in response to receiving a second request that is associated with a next portion of the one or more portions of the data set from the client, sending the next portion of the one or more portions and a next URL including the token to the client. 6. The method of claim 1 , wherein the communicating the one or more portions of the data further includes: sending a first portion of the one or more portions and a first uniform resource locator (URL) including the token and to the client; and in response to receiving a second request that is associated with the data set from the client, sending a second URL including the token to the client. 7. The method of claim 1 , further comprising: receiving a second request including the link from the client; determining the change of the data set based on the link; and sending the change of the data set to the client. 8. The method of claim 7 , further comprising: ordering the sending the change based on a chronological order that respective changes in the data set occurred. 9. The method of claim 1 , wherein the communicating the one or more portions of the data further includes: sending a first uniform resource locator (URL) including the token to the client; receiving a second request that is associated with the data set including the first URL from the client; and sending a second URL including an other token to the client. 10. The method of claim 1 , wherein the receiving the first request further includes receiving at least one operator for defining a result that is associated with the one or more portions of the data set. 11. The method of claim 10 , wherein the communicating further includes communicating the result and the link including the at least one operator. 12. The method of claim 1 , wherein the receiving the first request further includes receiving at least one operator for formatting a result that is associated with the one or more portions of the data set. 13. A computer-readable storage device comprising computer executable instructions that, in response to execution, cause a computing device to perform operations, comprising: in response to sending a first request that is associated with a data set to a data service, receiving first information that is associated with the data set from the data service; in response to receiving a link including a token for referencing a change of the data set from the data service, sending, utilizing the link, a second request to the data service; and receiving second information that is associated with the change of the data set from the data service based on the second request. 14. The computer-readable storage device of claim 13 , wherein the receiving the link further includes receiving a uniform resource locator (URL) including the token, and wherein the sending the sending the second request further includes sending the second request including the URL to the data service. 15. The computer-readable storage device of claim 13 , the operations further comprising: populating a cache based on the first information; and updating the cache based on the second information. 16. The computer-readable storage device of claim 13 , wherein the sending the first request to the data service further comprises including one or more operators in the first request for at least one of defining a result that is associated with the second information or formatting the result. 17. The computer-readable storage device of claim 16 , wherein the receiving the second information from the data service further includes receiving an other link including the one or more operators. 18. A system comprising: an interface component stored in a computable readable storage device configured to: receive one or more requests that are associated with a data set from a client, and send, based on the one or more requests, a network resource locator and at least one portion of the data set to the client; and a data service component configured to: compute a parameter that is associated with a change of the data set, and include the parameter in the network resource locator. 19. The system of claim 18 , wherein the one or more requests include a request including the network resource locator, wherein the data service component is further configured to determine the change of the data set based on the parameter, and wherein the at least one portion of the data set includes the change of the data set. 20. The system of claim 18 , wherein the one or more requests include a request including one or more operators for at least one of defining a result that is associated with the at least one portion of the data set or formatting the result. 21. A method, comprising: computing an initial data set; computing a token for referencing one or more changes to the initial data set; providing one or more portions of the initial data set and a link including the token to a client; receiving, by a data service component of at least one computing device, a request using the link from the client; and in response to the receiving the request, communicating the one or more changes to the initial data set to the client based on the token.
Routing (G06F30/396 takes precedence) · CPC title
Information retrieval; Database structures therefor; File system structures therefor · CPC title
Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes · CPC title
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Lexical analysis, e.g. tokenisation or collocates · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.