Resolving conflicts within saved state data
US-9141682-B1 · Sep 22, 2015 · US
US9942394B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9942394-B2 |
| Application number | US-201615337087-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 28, 2016 |
| Priority date | Sep 21, 2011 |
| Publication date | Apr 10, 2018 |
| Grant date | Apr 10, 2018 |
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.
A system and method for communicating presence information that can include at a first server of a communication platform, receiving an authorization token of a first client application; verifying at least one permission associated with the authorization token; registering a presence status of the first client application upon verifying the at least one permission of the authorization token; at a second server of the communication platform, accepting an incoming communication request; retrieving communication instructions according to the incoming communication request; identifying an instruction to communicate with a communication destination of the first client application; accessing the presence status resource of the first client application; establishing communication with the first client application according to the accessed presence status resource.
Opening claim text (preview).
We claim: 1. A method comprising: responsive to a presence status change of a first client application of a first client device, the first client device providing presence information of the first client application for a first account to an external presence server via an API of the presence server; the first client device providing a first presence request to the presence server via the API, the first presence request being a request for presence information for a first contact list of a plurality of accounts specified by the first presence request; the first client device receiving the presence information for the first contact list from the presence server via the API; the first client device processing the presence information of the first presence request by using the first client application; the first client device providing a second presence request to the presence server via the API, the second presence request being a request for presence information for the first contact list; the first client device receiving the presence information of the second presence request from the presence server via the API; the first client device processing the presence information of the second presence request by using a second client application of the first client device; and responsive to a presence status change of a third client application of a second client device of a second account, the second client device providing presence information of the third client application for the second account to the presence server via the API of the presence server. 2. The method of claim 1 , wherein the presence server stores first presence information for the first account. 3. The method of claim 2 , wherein the first presence information for the first account includes the presence information of the first client application. 4. The method of claim 3 , wherein the presence information of the first client application indicates whether the first client application for the first account is available for communication. 5. The method of claim 4 , wherein the presence information of the first presence request indicates each client application available for communication for each account of the first contact list, wherein the presence information of the second presence request indicates each client application available for communication for each account of the first contact list, and wherein the second client application is different from the first client application. 6. The method of claim 5 , wherein the first client application of the first client device provides the first presence request to the presence server via the API, and wherein the second client application of the first client device provides the second presence request to the presence server via the API. 7. The method of claim 6 , wherein the presence information of the third client application for the second account indicates whether the third client application for the second account is available for communication, wherein the presence server stores second presence information for the second account, wherein the second presence information for the second account includes the presence information of the third client application, and wherein the presence information of the first presence request includes the second presence information for the second account. 8. The method of claim 7 , wherein the presence information of the first presence request includes presence information of a plurality of accounts, and for each account, the presence information of the first presence request includes presence information for each client application and each device of the account, and wherein the presence information of the second presence request includes presence information of the plurality of accounts included in the presence information of the first presence request, and for each account, the presence information of the first presence request includes presence information for each client application and each device of the account. 9. The method of claim 5 , further comprising: responsive to a presence status change of a client application of a second client device of the first account, the second client device providing presence information of the client application of the second client device for the first account to the presence server via the API of the presence server, wherein the presence server stores the presence information of the client application of the second client device in association with the first presence information for the first account, and wherein the presence information of the client application of the second client device for the first account indicates whether the client application of the second client device is available for communication. 10. The method of claim 8 , further comprising: responsive to a presence status change of a client application of a second client device of the first account, the second client device providing presence information of the client application of the second client device to the presence server via the API of the presence server, wherein the presence server stores the presence information of the client application of the second client device in association with the first presence information for the first account, and wherein the presence information of the client application of the second client device for the first account indicates whether the client application of the second client device is available for communication. 11. The method of claim 5 , wherein the presence information of the third client application for the second account indicates whether the third client application for the second account is available for communication, wherein the presence server stores second presence information for the second account, wherein the second presence information for the second account includes the presence information of the third client application, and wherein the presence information of the first presence request includes the second presence information for the second account. 12. The method of claim 5 , wherein the presence information of the second presence request includes the second presence information for the second account. 13. The method of claim 11 , further comprising: the second client device providing a third presence request to the presence server via the API, the third presence request being a request for presence information for a second contact list of a plurality of accounts specified by the third presence request, wherein the first account is included in the second contact list, the second client device receiving the presence information for the second contact list from the presence server via the API, and the second client device processing the presence information of the second contact list by using the third client application, wherein the received presence information for the second contact list includes the first presence information for the first account. 14. The method of claim 1 , wherein the presence information of the third client application for the second account indicates whether the third client application for the second account is available for communication, wherein the presence server stores second presence information for the second account, wherein the second presence information for the second account includes the presence information of the third client application, and wherein the presence information of the first presence request includes the second presence information for the second account. 15. A method comprising: responsive
where the information is provided to a monitoring entity such as a potential calling party or a call processing server · CPC title
Communication-related supplementary services, e.g. call-transfer or call-hold · CPC title
for remote control or remote monitoring of applications · CPC title
using or handling presence information · CPC title
for controlling access to devices or network resources · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.