Methods and systems for integrating independent ims and webrtc networks
US-2015280963-A1 · Oct 1, 2015 · US
US10218766B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10218766-B2 |
| Application number | US-201414532503-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 4, 2014 |
| Priority date | Nov 4, 2014 |
| Publication date | Feb 26, 2019 |
| Grant date | Feb 26, 2019 |
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 service capability notification including receiving a service capability of a representational state transfer (REST) client and a request for a service capability of a target client from an application server, sending the service capability of the target client to the application server in response to the request, and sending the service capability of the REST client to a notification server so that the notification server is able to provide the service capability of the REST client to the target client.
Opening claim text (preview).
What is claimed: 1. A method of service capability notification, comprising: receiving, from an application server of a target client, a service capability of a representational state transfer (REST) client provided to the application server of the target client at about a same time as a request for a service capability of the target client from the REST client, the service capability of the target client indicating whether or not the target client is RESTful, the application server being a Web Real-Time Communications (WebRTC) user network interface (UNI) server and the REST client being associated with a first Internet Protocol (IP) multimedia system (IMS) network; and sending, to the target client, the service capability of the REST client, the target client being associated with a second IP IMS network different from the first IP IMS network. 2. The method of claim 1 , wherein the application server of the target client comprises an Application Programming Interface (API) server. 3. The method of claim 1 , wherein the service capability of the REST client is sent to the target client after the application server of the target client has responded to the request for the service capability of the target client by the REST client. 4. The method of claim 1 , wherein the service capability of the REST client is sent to the target client before the application server of the target client has responded to the request for the service capability of the target client by the REST client. 5. The method of claim 1 , wherein the service capability of the REST client is sent to the target client using a notification channel established when the target client is started. 6. The method of claim 1 , wherein the service capability of the REST client and the request for the service capability of the target client are packaged in a session initiation protocol (SIP) OPTIONS message. 7. The method of claim 1 , wherein the application server comprises a Web Real-Time Communications (WebRTC) user network interface (UNI) server, wherein the REST client is associated with a first Internet Protocol (IP) multimedia system (IMS) network, and wherein the target client is associated with a second IP IMS network different from the first IP IMS network. 8. A notification server, comprising: a processor operably coupled to a memory; and a notification module stored in the memory that, when executed by the processor is configured to: receive, from an application server of a target client, a service capability of a representational state transfer (REST) client provided to the application server of the target client at about a same time as a request for a service capability of the target client by the REST client, the service capability of the target client indicating whether or not the target client is RESTful, the application server being a Web Real-Time Communications (WebRTC) user network interface (UNI) server and the REST client being associated with a first Internet Protocol (IP) multimedia system (IMS) network; and send, to the target client, the service capability of the REST client using a notification channel established by the target client at startup, the target client being associated with a second IP IMS network different from the first IP IMS network. 9. The notification server of claim 8 , wherein the service capability of the REST client is sent to the target client simultaneously with a response by the application server of the target client to the request for the service capability of the target client by the REST client. 10. The notification server of claim 8 , wherein the service capability of the REST client and the request for the service capability of the target client are packaged in a session initiation protocol (SIP) OPTIONS message.
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Electricity · mapped topic
Electricity · mapped topic
Electricity · mapped topic
Session initiation protocol [SIP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.