US2018262580A1PendingUtilityA1
State Information For a Service
Assignee: MICROSOFT TECHNOLOGY LICENSING LLCPriority: Mar 4, 2016Filed: May 15, 2018Published: Sep 13, 2018
Est. expiryMar 4, 2036(~9.6 yrs left)· nominal 20-yr term from priority
H04L 67/02H04L 67/306H04L 67/16H04L 67/2838H04L 67/32H04L 67/42H04L 67/26H04L 67/51H04L 67/567H04L 67/60H04L 67/55
39
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Techniques for state change information for a service are described. In an implementation, a request is received for state change information for a service provided by a server. State change information is then determined indicating whether a state of the service at the server is changed. In an implementation, the state change information is communicated for receipt by a receiving device to enable the receiving device to determine whether to suppress a polling of the server for the state of the service.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A system comprising:
at least one processor; and at least one memory storing computer code that, when executed by the at least one processor, causes the system to perform operations including:
receiving a request for state change information for a service provided by a server, the request including information of a current state of the service as recorded by a data processing system;
determining state change information indicating whether a state of the service at the server is different than the current state of the service as recorded by the data processing system; and
communicating the state change information for receipt by the data processing system effective to enable the data processing system to determine whether to suppress a polling of the server for the state of the service.
2 . A system comprising as recited in claim 1 , wherein the service includes multiple microservices, and wherein said determining state change information comprises determining whether a state of one or more of the microservices has changed.
3 . A system comprising as recited in claim 1 , wherein said determining state change information comprises:
ascertaining that the service includes multiple microservices; and determining whether a state of one or more of the microservices has changed.
4 . A system comprising as recited in claim 1 , wherein said determining state change information comprises receiving a notification from the server indicating the state of the service at the server.
5 . A system comprising as recited in claim 1 , wherein said determining comprises querying the server for a current state of the service.
6 . A system comprising as recited in claim 1 , wherein the data processing system is associated with a user terminal that utilizes the service.
7 . A system comprising as recited in claim 1 , wherein state change information comprises an indication that the state of the service at the server is not different than the current state of the service as recorded by the data processing system, and wherein said communicating the state change information for receipt by the data processing system is effective to cause the data processing system to cancel a scheduled polling of the server for the state of the service.
8 . A system comprising as recited in claim 1 , wherein state change information comprises an indication that the state of the service at the server is different than the current state of the service as recorded by the data processing system, and wherein said communicating the state change information for receipt by the data processing system is effective to cause the data processing system to poll the server for the state of the service.
9 . A system comprising as recited in claim 1 , wherein the system comprises a different server.
10 . A system comprising as recited in claim 1 , wherein said communicating the state change information for receipt by the data processing system comprises communicating, for receipt by the data processing system, an identifier of the current state of the service at the server.
11 . A method comprising:
receiving a request for state change information for a service provided by a server, the request including information of a current state of the service as recorded by a data processing system; determining state change information indicating whether a state of the service at the server is different than the current state of the service as recorded by the data processing system; and communicating the state change information for receipt by the data processing system effective to enable the data processing system to determine whether to suppress a polling of the server for the state of the service.
12 . A method as recited in claim 11 , wherein the service includes multiple microservices, and wherein said determining state change information comprises determining based on state notification from the server whether a state of one or more of the microservices has changed.
13 . A method as recited in claim 11 , wherein the service includes both a real-time service and non-real-time service, and wherein the state of the service pertains to a state of the non-real-time service.
14 . A method as recited in claim 11 , wherein state change information comprises an indication that the state of the service at the server is not different than the current state of the service as recorded by the data processing system, and wherein said communicating the state change information for receipt by the data processing system is effective to cause the data processing system to cancel a scheduled polling of the server for the state of the service.
15 . A method as recited in claim 11 , wherein state change information comprises an indication that the state of the service at the server is different than the current state of the service as recorded by the data processing system, and wherein said communicating the state change information for receipt by the data processing system is effective to cause the data processing system to poll the server for the state of the service.
16 . A method comprising:
receiving a request for state change information for a service provided by a server, the request including information of a current state of the service as recorded by a data processing system; determining state change information indicating that a state of the service at the server is not different than the current state of the service as recorded by the data processing system; and communicating the state change information for receipt by the data processing system effective to enable the data processing system to determine to suppress a polling of the server for the state of the service.
17 . A method as recited in claim 16 , wherein the service includes multiple microservices, and wherein said determining state change information comprises determining whether a state of one or more of the microservices has changed.
18 . A method as recited in claim 16 , wherein said determining state change information comprises:
ascertaining that the service includes multiple microservices; and determining whether a state of one or more of the microservices has changed.
19 . A method as recited in claim 16 , wherein said communicating the state change information for receipt by the data processing system is effective to enable the data processing system to cancel a scheduled polling of the server for the state of the service.
20 . A method as recited in claim 16 , further comprising:
receiving a further request for state change information for the service provided by the server, the request including information of the current state of the service as recorded by the data processing system; determining further state change information indicating that the state of the service at the server is different than the current state of the service as recorded by the data processing system; and communicating the further state change information for receipt by the data processing system effective to cause the data processing system to poll the server for the state of the service.Join the waitlist — get patent alerts
Track US2018262580A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.