US2018262581A1PendingUtilityA1

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/306H04L 67/02H04L 67/32H04L 67/42H04L 67/26H04L 67/2838H04L 67/16H04L 67/51H04L 67/567H04L 67/55H04L 67/60
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-modified
What is claimed is: 
     
         1 . A system comprising:
 a first server including a first processing system configured to execute operations including:
 providing a service that is accessible to one or more user terminals; and 
 responding to a polling request from a user terminal of the one or more user terminals with updated state information configured to update a state of the service at the user terminal; and 
   a second server including a second processing system configured to execute operations including:
 determining whether the state of the service is changed at the first server; and 
 providing an indication to the user terminal of whether the state of the service is changed at the first server effective to enable the user terminal to determine whether to suppress a polling of the first server for the state of the service. 
   
     
     
         2 . A system as recited in  claim 1 , wherein said determining whether the state of the service is changed at the first server comprises receiving, at the second server, a notification from the first server indicating whether the state of the service is changed at the first server. 
     
     
         3 . A system as recited in  claim 1 , wherein said determining whether the state of the service is changed at the first server comprises:
 receiving, at the second server, an indication from the first server of the current state of the service at the first server; and   determining whether the current state of the service at the first server is different than an indication of the state of the service stored at the second server.   
     
     
         4 . A system as recited in  claim 1 , wherein said providing the service comprises providing a set of microservices that represent the service, and wherein said responding to the polling request comprises responding with updated state information for one or more of the microservices. 
     
     
         5 . A system as recited in  claim 1 , 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. 
     
     
         6 . A system as recited in  claim 1 , wherein said determining whether the state of the service is changed at the first server comprises determining that the state of the service at the first server is not changed, and wherein said providing an indication to the user terminal of whether the state of the service is changed comprises an indication that the state of the service is not changed effective to cause the user terminal to cancel a scheduled polling of the first server for state information for the service. 
     
     
         7 . A system as recited in  claim 1 , wherein said determining whether the state of the service is changed at the first server comprises determining that the state of the service at the first server is changed, and wherein said providing an indication to the user terminal of whether the state of the service is changed comprises an indication that the state of the service is changed effective to cause the user terminal to poll the first server for state information for the service. 
     
     
         8 . A method comprising:
 providing, by a first server, a service that is accessible to one or more user terminals;   determining, by a second server, whether the state of the service is changed at the first server; and   providing, by the first server and to a user terminal of the one or more user terminals, an indication of whether the state of the service is changed at the first server effective to enable the user terminal to determine whether to suppress a polling of the first server for the state of the service; and   responding, by the first server, to a polling request from the user terminal with updated state information configured to update a state of the service at the user terminal.   
     
     
         9 . A method as recited in  claim 8 , wherein said determining whether the state of the service is changed at the first server comprises receiving, at the second server, a notification from the first server indicating whether the state of the service is changed at the first server. 
     
     
         10 . A method as recited in  claim 8 , wherein the service comprises multiple microservices, and wherein said determining comprises determining, by the second server, whether a state of one or more of the microservices is changed at the first server. 
     
     
         11 . A method as recited in  claim 8 , wherein said determining whether the state of the service is changed at the first server comprises:
 receiving, at the second server, an indication from the first server of the current state of the service at the first server; and   determining whether the current state of the service at the first server is different than an indication of the state of the service stored at the second server.   
     
     
         12 . A method as recited in  claim 8 , 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. 
     
     
         13 . A method as recited in  claim 8 , wherein said determining whether the state of the service is changed at the first server comprises determining that the state of the service at the first server is not changed, and wherein said providing an indication to the user terminal of whether the state of the service is changed comprises an indication that the state of the service is not changed effective to cause the user terminal to cancel a scheduled polling of the first server for state information for the service. 
     
     
         14 . A method as recited in  claim 8 , wherein said determining whether the state of the service is changed at the first server comprises determining that the state of the service at the first server is changed, and wherein said providing an indication to the user terminal of whether the state of the service is changed comprises an indication that the state of the service is changed effective to cause the user terminal to poll the first server for state information for the service. 
     
     
         15 . 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:
 providing, by a first server, a service that is accessible to one or more user terminals; 
 determining, by a second server, whether the state of the service is changed at the first server; and 
 providing, by the first server and to a user terminal of the one or more user terminals, an indication of whether the state of the service is changed at the first server effective to enable the user terminal to determine whether to suppress a polling of the first server for the state of the service; and 
 responding, by the first server, to a polling request from the user terminal with updated state information configured to update a state of the service at the user terminal. 
   
     
     
         16 . A system as recited in  claim 15 , wherein the service comprises multiple microservices, and wherein said determining comprises determining, by the second server, whether a state of one or more of the microservices at the first server is changed. 
     
     
         17 . A system as recited in  claim 15 , wherein said determining whether the state of the service is changed at the first server comprises:
 receiving, at the second server, an indication from the first server of the current state of the service at the first server; and   determining whether the current state of the service at the first server is different than an indication of the state of the service stored at the second server.   
     
     
         18 . A system as recited in  claim 15 , wherein the service includes both a real-time service and non-real-time service, and wherein said determining whether the state of the service is changed at the first server comprises determining whether the state of the non-real-time service is changed. 
     
     
         19 . A system as recited in  claim 15 , wherein said determining whether the state of the service is changed at the first server comprises determining that the state of the service at the first server is not changed, and wherein said providing an indication to the user terminal of whether the state of the service is changed comprises an indication that the state of the service is not changed effective to cause the user terminal to cancel a scheduled polling of the first server for state information for the service. 
     
     
         20 . A system as recited in  claim 15 , wherein said determining whether the state of the service is changed at the first server comprises determining that the state of the service at the first server is changed, and wherein said providing an indication to the user terminal of whether the state of the service is changed comprises an indication that the state of the service is changed effective to cause the user terminal to poll the first server for state information for the service.

Join the waitlist — get patent alerts

Track US2018262581A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.