Efficient retrieval of 4g lte capabilities
US-2015271318-A1 · Sep 24, 2015 · US
US9667691B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9667691-B2 |
| Application number | US-201414549341-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 20, 2014 |
| Priority date | Nov 20, 2014 |
| Publication date | May 30, 2017 |
| Grant date | May 30, 2017 |
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 method of retrieving service capability in bulk is provided. The method includes a client sending a request to create a group of contacts whose service capability is desired to an application server. The application server sends a response to the client indicating that the group of contacts has been created. The client then sends a request to retrieve the service capability of each of the contacts within the group to the application server. The application server sends a response identifying the service capability of each of the contacts within the group to the client.
Opening claim text (preview).
What is claimed: 1. A method of retrieving service capability in bulk, comprising: receiving, from a representational state transfer (REST) client, a request to create a group of contacts whose service capability is desired; sending, to the REST client, a response indicating that the group of contacts has been created; receiving, from the REST client, a request to retrieve the service capability of each of the contacts within the group; and sending, to the REST client, a response identifying the service capability of each of the contacts within the group, wherein the response includes a default service capability for each of the contacts within the group whose service capability was not able to be retrieved. 2. The method of claim 1 , wherein the group of contacts corresponds to all contacts stored by the REST client. 3. The method of claim 1 , wherein the group of contacts includes all contacts in a phone book of the REST client. 4. The method of claim 1 , wherein the group of contacts is based on a current use of a same application by the contacts and the REST client. 5. The method of claim 1 , wherein the group of contacts is based on one of a common geographic area of the contacts and the REST client and a proximity of the contacts to the REST client. 6. The method of claim 1 , wherein the group of contacts is based on a common membership of the contacts and the REST client. 7. The method of claim 1 , wherein the service capability is one of a chat capability and a file transfer capability. 8. The method of claim 1 , wherein the request to create the group of contacts comprises a Hypertext Protocol (HTTP) POST message. 9. The method of claim 1 , wherein the request to retrieve the service capability of each of the contacts within the group of contacts comprises a Hypertext Protocol (HTTP) GET message. 10. The method of claim 1 , wherein each of the contacts is a mobile phone. 11. The method of claim 1 , wherein one or more of the contacts is a mobile phone. 12. The method of claim 1 , further comprising creating the group of contacts based on the request and retrieving, from a contact application server corresponding to each of the contacts, the service capability of the contacts within the group. 13. The method of claim 1 , further comprising retrieving the service capability of less than all of the contacts within the group. 14. A method of retrieving service capability in bulk, comprising: sending, to an application server, a request to create a group of contacts whose service capability is desired; receiving, from the application server, a response indicating that the group of contacts has been created; sending, to the application server, a request to retrieve the service capability of each of the contacts within the group; and receiving, from the application server, a response identifying the service capability of each of the contacts within the group, wherein the response includes a default service capability for each of the contacts within the group whose service capability was not able to be retrieved. 15. The method of claim 14 , wherein the group of contacts corresponds to all contacts stored by a representational state transfer (REST) client. 16. The method of claim 14 , wherein the group of contacts includes all contacts in a phone book of a representational state transfer (REST) client. 17. The method of claim 14 , wherein the service capability is one of a chat capability and a file transfer capability, and wherein one or more of the contacts is a mobile phone. 18. An application server, comprising: a processor operably coupled to a memory, and a bulk service capability module stored in the memory that, when executed by the processor, is configured to: receive, from a representational state transfer (REST) client, a request to create a group of contacts whose service capability is desired; create the group of contacts based on the request; send, to the REST client, a response indicating that the group of contacts has been created; receive, from the REST client, a request to retrieve the service capability of each of the contacts within the group; retrieve, from a contact application server corresponding to each of the contacts, the service capability of the contacts within the group; and send, to the REST client, a response identifying the service capability of each of the contacts within the group, wherein the response includes a default service capability for each of the contacts within the group whose service capability was not able to be retrieved. 19. The application server of claim 18 , wherein the group of contacts corresponds to the contacts saved in a phone book of the REST client, and wherein the service capability is one of a chat capability and a file transfer capability. 20. The application server of claim 18 , wherein one or more of the contacts is a mobile phone.
IP multimedia subsystem [IMS] · CPC title
User group management · CPC title
Application servers providing network services (systems providing special services to telephonic subscribers H04M3/42) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Electricity · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.