# US 10,320,949 B2 · Referencing change(s) in data utilizing a network resource locator > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,320,949 B2 - Document ID: US10320949B2 - Status: Granted - Kind: B2 - Application number: 15/373,905 - Filed: 2016-12-09 - Published: 2017-03-30 - Granted: 2019-06-11 - Earliest claimed: 2011-12-16 - Assignees: Microsoft Technology Licensing, LLC - Applicants: Microsoft Technology Licensing, LLC - Inventors: Alex James; Michael Pizzo; Pablo Castro; Mike Flasko; Lance Olson; Jason Clark; Sid Jayadevan - Web page: https://patentgrep.com/patent/US10320949B2 ## CPC - G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links} - G06F 16/00: Information retrieval; Database structures therefor; File system structures therefor - G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs} - G06F 16/2322: {using timestamps} - G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)} - G06F 16/282: {Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes} - G06F 16/951: Indexing; Web crawling techniques - G06F 16/953: Querying, e.g. by the use of web search engines - G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking - G06F 30/394: Routing (G06F30/396 takes precedence) - G06F 40/284: Lexical analysis, e.g. tokenisation or collocates - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract 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. ## Claims ### Claim 1 A computer-implemented method for managing a data services environment that comprises a service application system from which a data set is accessed by a client computing system, and wherein the client computing system is able to update one or more portions of a cache based on changes made to the data set at the service application system, but without having to retrieve the full data set or having to repopulate the client cache in its entirety in order to account for the changes made to the data set, the computer-implemented method being implemented by one or more processors when executing computer-executable instructions for the method, which comprises: accessing a data set in a data store of the service application system; computing at the service application system a token for referencing one or more changes to the data set; providing from the service application system one or more portions of the data set and the computed token to the client computing system; receiving at the service application system a request from the client computing system to change the data set, wherein the request includes the computed token; in response to the request and the computed token, identifying one or more changes to the data set; and communicating from the service application system the one or more changes to the data set to the client computing system. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the token is computed by determining the token prior to determining the one or more portions that are provided to the client computing system. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein the token is computed by determining a change identifier that is associated with a most recent detected change of the data set. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein the token is computed by determining a timestamp enumerating a time that is associated with the one or more changes. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, wherein the token is computed by determining a date of the one or more changes. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein the one or more portions of the data set are provided to the client computing system in a first portion of the data set with the token and wherein the token is referenced in a first uniform resource locator (URL) . ### Claim 7 (depends on 1) The computer-implemented method of claim 1, wherein the one or more portions of the data set are provided to the client computing system in at least two different portions of the data set, and wherein each of the different portions are provided in response to receiving different requests that are associated with each of the different portions, respectively, and wherein each request is sent with a URL that references the computed token. ### Claim 8 (depends on 7) The computer-implemented method of claim 7, wherein at least one change to the data set is determined for each different portion based on the respective request that includes the computed token. ### Claim 9 (depends on 8) The computer-implemented method of claim 8, wherein each change to the data set is sent to the client computing system. ### Claim 10 (depends on 9) The computer-implemented method of claim 9, wherein each change to the data set is ordered based on a chronological order in which the respective changes in the data set were determined. ### Claim 11 (depends on 1) The computer-implemented method of claim 1, wherein: a new request is received from the client computing system, the new request being associated with the data set and including a first URL that includes the token; and a new token identified by a second URL is sent to the client computing system. ### Claim 12 (depends on 1) The computer-implemented method of claim 1, wherein the request includes at least one operator for defining a result that is associated with the one or more portions of the data set. ### Claim 13 A computer-implemented method for managing a data services environment that comprises a service application system from which a data set is accessed by a client computing system, and wherein the client computing system is able to update one or more portions of a cache based on changes made to the data set at the service application system, but without having to retrieve the full data set or having to repopulate the client cache in its entirety in order to account for the changes made to the data set, the computer-implemented method being implemented by one or more processors when executing computer-executable instructions for the method, which comprises: receiving at the service application system a request from the client computing system to change a portion of the data set stored in the data store, wherein the request includes at least one operator for defining a result associated with the portion of the data set; computing at the service application system a token that is used to reference the requested change to the portion of the data set; and sending from the service application system to the client computing system a link that includes the computed token and operator associated with the requested change to the portion of the data set. ### Claim 14 (depends on 13) The computer-implemented method of claim 13, wherein the change to the data set is based on the operator. ### Claim 15 (depends on 13) The computer-implemented method of claim 13, wherein the link sent to the client computing system comprises a uniform resource locator. ### Claim 16 A computer-implemented method for managing a data services environment that comprises a service application system from which a data set is accessed by a client computing system, and wherein the client computing system is able to update one or more portions of a cache based on changes made to the data set at the service application system, but without having to retrieve the full data set or having to repopulate the client cache in its entirety in order to account for the changes made to the data set, the computer-implemented method being implemented by one or more processors when executing computer-executable instructions for the method, which comprises: receiving, at the service application system, a first request from the client computing system that is associated with a data set stored at a data store of the service application system; in response to the receiving the first request, the service application computing a token for referencing a change to a portion of the data set, wherein the token is determined prior to determining the portion of the data set to be changed; and communicating, from the service application system, the portion of the data set and a link including the token to the client computing system. ### Claim 17 (depends on 16) The computer-implemented method of claim 16, wherein computing the token comprises determining a timestamp enumerating a time that is associated with the change. ### Claim 18 (depends on 16) The computer-implemented method of claim 16, wherein computing the token comprises determining a date of the change. ### Claim 19 (depends on 16) The computer-implemented method of claim 16, wherein communicating the portion of the data set and the link comprises sending a first uniform resource locator (URL) including the token to the client computing system, and wherein the computer-implemented method further comprises: receiving a second request that is associated with the data set including the first URL from the client computing system; and sending a second URL including another token to the client computing system. ### Claim 20 (depends on 16) The computer-implemented method of claim 16, wherein communicating the portion of the data set and the link comprises: sending a first portion of the data set and a first uniform resource locator (URL) including the computed token and to the client computing system; and in response to receiving a second request that is associated with the data set from the client computing system, sending a second URL including the computed token to the client computing system. ### Claim 21 A computer system for managing a data services environment that comprises: a service application system from which a data set is accessed by a client computing system; a data store maintained at the service application system and which contains the data set; one or more processors; a computer-readable storage device storing computer-executable instructions which, when executed by the one or more processors, configure the computer system with an architecture that enables the client computing system to update one or more portions of a cache based on changes made to the data set at the service application system, but without having to retrieve the full data set or having to repopulate the client cache in its entirety in order to account for the changes made to the data set, and wherein the architecture performs at least the following: accesses a data set in a data store of the service application system; computes at the service application system a token for referencing one or more changes to the data set; provides from the service application system one or more portions of the data set and the computed token to the client computing system; receives at the service application system a request from the client computing system to change the data set, wherein the request includes the computed token; in response to the request and the computed token, identifies one or more changes to the data set; and communicates from the service application system the one or more changes to the data set to the client computing system. ### Claim 22 (depends on 21) The computer system of claim 21, wherein the token is computed by determining the token prior to determining the one or more portions that are provided to the client computing system. ### Claim 23 (depends on 21) The computer system of claim 21, wherein the token is computed by determining a change identifier that is associated with a most recent detected change of the data set. ### Claim 24 (depends on 21) The computer system of claim 21, wherein the token is computed by determining a timestamp enumerating a time that is associated with the one or more changes. ### Claim 25 (depends on 21) The computer system of claim 21, wherein the token is computed by determining a date of the one or more changes. ### Claim 26 (depends on 21) The computer system of claim 21, wherein the one or more portions of the data set are provided to the client system in a first portion of the data set with the token and wherein the token is referenced in a first uniform resource locator (URL) . ### Claim 27 (depends on 21) The computer system of claim 21, wherein the one or more portions of the data set are provided to the client computing system in at least two different portions of the data set, and wherein each of the different portions are provided in response to receiving different requests that are associated with each of the different portions, respectively, and wherein each request is sent with a URL that references the computed token. ### Claim 28 (depends on 27) The computer system of claim 27, wherein at least one change to the data set is determined for each different portion based on the respective request that includes the computed token. ### Claim 29 (depends on 28) The computer system of claim 28, wherein each change to the data set is sent to the client computing system. ### Claim 30 (depends on 29) The computer system of claim 29, wherein each change to the data set is ordered based on a chronological order in which the respective changes in the data set were determined. ### Claim 31 (depends on 21) The computer system of claim 21, wherein: a new request is received from the client system, the new request being associated with the data set and including a first URL that includes the token; and a new token identified by a second URL is sent to the client computing system. ### Claim 32 (depends on 21) The computer system of claim 21, wherein the request includes at least one operator for defining a result that is associated with the one or more portions of the data set. ### Claim 33 A computer system for managing a data services environment that comprises: a service application system from which a data set is accessed by a client computing system; a data store maintained at the service application system and which contains the data set; one or more processors; a computer-readable storage device storing computer-executable instructions which, when executed by the one or more processors, configure the computer system with an architecture that enables the client computing system to update one or more portions of a cache based on changes made to the data set at the service application system, but without having to retrieve the full data set or having to repopulate the client cache in its entirety in order to account for the changes made to the data set, and wherein the architecture performs at least the following: receives at the service application system a request from the client computing system to change a portion of the data set stored in the data store, wherein the request includes at least one operator for defining a result associated with the portion of the data set; computes at the service application system a token that is used to reference the requested change to the portion of the data set; and sends from the service application system to the client computing system a link that includes the computed token and operator associated with the requested change to the portion of the data set. ### Claim 34 (depends on 33) The computer system of claim 33, wherein the change to the data set is based on the operator. ### Claim 35 (depends on 33) The computer system of claim 33, wherein the link sent to the client computing system comprises a uniform resource locator. ### Claim 36 A computer system for managing a data services environment that comprises: a service application system from which a data set is accessed by a client computing system; a data store maintained at the service application system and which contains the data set; one or more processors; a computer-readable storage device storing computer-executable instructions which, when executed by the one or more processors, configure the computer system with an architecture that enables the client computing system to update one or more portions of a cache based on changes made to the data set at the service application system, but without having to retrieve the full data set or having to repopulate the client cache in its entirety in order to account for the changes made to the data set, and wherein the architecture performs at least the following: receives, at the service application system, a first request from the client computing system that is associated with a data set stored at a data store of the service application system; in response to the receiving the first request, the service application computes a token for referencing a change to a portion of the data set, wherein the token is determined prior to determining the portion of the data set to be changed; and communicates, from the service application system, the portion of the data set and a link including the token to the client computing system. ### Claim 37 (depends on 36) The computer system of claim 36, wherein computing the token comprises determining a timestamp enumerating a time that is associated with the change. ### Claim 38 (depends on 36) The computer system of claim 36, wherein computing the token comprises determining a date of the change. ### Claim 39 (depends on 36) The computer system of claim 36, wherein communicating the portion of the data set and the link comprises sending a first uniform resource locator (URL) including the token to the client computing system, and wherein the architecture of the computing system is further configured to perform: receiving a second request that is associated with the data set including the first URL from the client computing system; and sending a second URL including another token to the client computing system. ### Claim 40 (depends on 36) The computer system of claim 36, wherein communicating the portion of the data set and the link comprises: sending a first portion of the data set and a first uniform resource locator (URL) including the computed token and to the client computing system; and in response to receiving a second request that is associated with the data set from the client computing system, sending a second URL including the computed token to the client computing system.