Abstract
A User Equipment (UE) and IP Multimedia Subsystem (IMS) network node for indicating the IMS services and IMS applications to which a Session Initiation Protocol (SIP) message relates. An IMS communication service identifier and an IMS application reference are added to the SIP message. The identifier and the reference may be added as Feature Tags. The reference may also be added as an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.
Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Number | ||||||
4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member |
Specification Information
Specification Information
Technologies
Family Information
All Granted Patents In Patent Family : | ---- |
All Pending Patents In Patent Family : | ---- |
Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
---|---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Number | |||||||
US2009144429A1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Basis Patent | ||||
US2009144429A1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Basis Patent | ||||
US8285852B2 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Basis Patent | ||||
US8285852B2 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Basis Patent | ||||
AT429767T | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
AT429767T | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | No | Family Member | ||||
BRPI0520192A2 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
BRPI0520192A2 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
CA2609639A1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
CA2609639A1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
CA2609639C | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
CA2609639C | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
CN101185304A | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
CN101185304A | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
CN101185304B | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
CN101185304B | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
EP1886458A1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
EP1886458A1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
EP1886458B1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
EP1886458B1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
EP1886458B2 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
EP1886458B2 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
ES2325378T3 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
ES2325378T3 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
ES2325378T5 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
ES2325378T5 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
JP2008543133A | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
JP2008543133A | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
JP4851516B2 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
JP4851516B2 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
KR101245915B1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
KR101245915B1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
KR20080015804A | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
KR20080015804A | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
US2012331159A1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
US2012331159A1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
US2014040489A1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
US2014040489A1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
US8984146B2 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
US8984146B2 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
WO2006125471A1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
WO2006125471A1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
US2015188950A1 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
US2015188950A1 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
US9210196B2 | 4G,3G,2G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
US9210196B2 | 4G,3G,2G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
BRPI0520192B8 | ----- | ----- | ----- | ----- | ----- | ----- | ----- |
Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | Status | National Phase Entries | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Information | |||||||||
----- | ----- | ----- | ----- | ----- |
S1
|
----- | ----- | ----- | ----- |
Technologies

Product
Use Cases
Services
Claim
1. A User Equipment (UE) for communicating with an IP Multimedia Subsystem (IMS) network node utilizing Session Initiation Protocol (SIP) signaling, wherein the UE comprises a processor coupled to a memory that stores computer program instructions, wherein when the processor executes the instructions, the UE is caused to:
set an IMS communication service identifier to identify one of a plurality of IMS communication services;
set an IMS application reference to identify one of a plurality of IMS applications to be used for handling the identified one of the plurality of IMS communication services; and
send to the IMS network node, a SIP message that includes the IMS communication service identifier and the IMS application reference, thereby enabling an IMS protocol stack in the IMS network node to utilize the IMS communication service identifier to forward the SIP message to the identified one of the plurality of IMS communication services, and enabling the identified one of the plurality of IMS communication services to utilize the IMS application reference to forward the SIP message to the identified one of the plurality of IMS applications.', 'set an IMS communication service identifier to identify one of a plurality of IMS communication services;', 'set an IMS application reference to identify one of a plurality of IMS applications to be used for handling the identified one of the plurality of IMS communication services; and', 'send to the IMS network node, a SIP message that includes the IMS communication service identifier and the IMS application reference, thereby enabling an IMS protocol stack in the IMS network node to utilize the IMS communication service identifier to forward the SIP message to the identified one of the plurality of IMS communication services, and enabling the identified one of the plurality of IMS communication services to utilize the IMS application reference to forward the SIP message to the identified one of the plurality of IMS applications.
2. The UE as recited in claim 1, wherein the UE is configured to include the IMS communication service identifier in the SIP message as a first feature tag in a header of the SIP message.
3. The UE as recited in claim 2, wherein the UE is configured to include the IMS application reference in the SIP message as a second feature tag in a header of the SIP message.
4. The UE as recited in claim 2, wherein the UE is configured to include the application reference in the SIP message as an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.
5. The UE as recited in claim 2, wherein the UE is configured to include the application reference in the SIP message as a second feature tag in a header of the SIP request message and as an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.
6. A User Equipment (UE) for communicating with an IP Multimedia Subsystem (IMS) network node utilizing Session Initiation Protocol (SIP) signaling, the UE comprising:
a processor coupled to a memory that stores computer program instructions, wherein when the processor executes the instructions, the processor implements an IMS protocol stack;
a plurality of IMS communication services in communication with the IMS protocol stack; and
a plurality of IMS applications interfaced with the plurality of IMS communication services;
wherein the processor controls the IMS protocol stack to:
receive from the IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;
utilize the IMS communication service identifier to identify one of the plurality of IMS communication services; and
forward the received SIP message to the identified one of the plurality of IMS communication services;
wherein the identified one of the plurality of IMS communication services is configured to:
receive the SIP message from the IMS protocol stack;
utilize the IMS application reference to identify one of the plurality of IMS applications; and
forward the received SIP message to the identified one of the plurality of IMS applications.', 'a processor coupled to a memory that stores computer program instructions, wherein when the processor executes the instructions, the processor implements an IMS protocol stack;', 'a plurality of IMS communication services in communication with the IMS protocol stack; and', 'a plurality of IMS applications interfaced with the plurality of IMS communication services;', 'wherein the processor controls the IMS protocol stack to:
receive from the IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;
utilize the IMS communication service identifier to identify one of the plurality of IMS communication services; and
forward the received SIP message to the identified one of the plurality of IMS communication services;', 'receive from the IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;', 'utilize the IMS communication service identifier to identify one of the plurality of IMS communication services; and', 'forward the received SIP message to the identified one of the plurality of IMS communication services;', 'wherein the identified one of the plurality of IMS communication services is configured to:
receive the SIP message from the IMS protocol stack;
utilize the IMS application reference to identify one of the plurality of IMS applications; and
forward the received SIP message to the identified one of the plurality of IMS applications.', 'receive the SIP message from the IMS protocol stack;', 'utilize the IMS application reference to identify one of the plurality of IMS applications; and', 'forward the received SIP message to the identified one of the plurality of IMS applications.
7. The UE as recited in claim 6, wherein the IMS protocol stack is configured to read the IMS communication service identifier from a first feature tag in a header of the SIP message.
8. The UE as recited in claim 7, wherein the UE is configured to read the IMS application reference from a second feature tag in a header of the SIP message.
9. The UE as recited in claim 7, wherein the UE is configured to read the application reference from an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message
10. The UE as recited in claim 7, wherein the UE is configured to read the application reference from a second feature tag in a header of the SIP message and from an a-line augmenting an rn-line in a Session Description Protocol (SDP) part of the SIP message
11. A Session Initiation Protocol Application Server (SIP AS) in an IP Multimedia Subsystem (IMS) network, wherein the SIP AS comprises a processor coupled to a memory that stores computer program instructions, wherein when the processor executes the instructions, the SIP AS is caused to:
set an IMS communication service identifier to identify one of a plurality of IMS communication services;
set an IMS application reference to identify one of a plurality of IMS applications to be used for handling the identified one of the plurality of IMS communication services; and
send to a User Equipment (UE), a SIP message that includes the IMS communication service identifier and the IMS application reference, thereby enabling an IMS protocol stack in the UE to utilize the IMS communication service identifier to forward the SIP message to the identified one of the plurality of IMS communication services, and enabling the identified one of the plurality of IMS communication services to utilize the IMS application reference to forward the SIP message to the identified one of the plurality of IMS applications.', 'set an IMS communication service identifier to identify one of a plurality of IMS communication services;', 'set an IMS application reference to identify one of a plurality of IMS applications to be used for handling the identified one of the plurality of IMS communication services; and', 'send to a User Equipment (UE), a SIP message that includes the IMS communication service identifier and the IMS application reference, thereby enabling an IMS protocol stack in the UE to utilize the IMS communication service identifier to forward the SIP message to the identified one of the plurality of IMS communication services, and enabling the identified one of the plurality of IMS communication services to utilize the IMS application reference to forward the SIP message to the identified one of the plurality of IMS applications.12. The SIP AS as recited in claim 11, wherein the SIP AS is configured to include the IMS communication service identifier in the SIP message as a first feature tag in a header of the SIP message.13. The SIP AS as recited in claim 12, wherein the SIP AS is configured to include the IMS application reference in the SIP message as a second feature tag in a header of the SIP message.14. The SIP AS as recited in claim 12, wherein the SIP AS is configured to include the application reference in the SIP message as an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.15. The SIP AS as recited in claim 12, wherein the SIP AS is configured to include the application reference in the SIP message as a second feature tag in a header of the SIP message and as an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.16. A node in an IP Multimedia Subsystem (IMS) network for communicating with a User Equipment (UE) or another IMS network node utilizing Session Initiation Protocol (SIP) signaling, the node in the IMS network comprising:
a processor coupled to a memory that stores computer program instructions, wherein when the processor executes the instructions, the processor implements an IMS protocol stack;
a plurality of IMS communication services in communication with the IMS protocol stack; and
a plurality of IMS applications interfaced with the plurality of IMS communication services;
wherein the processor controls the IMS protocol stack to:
receive from the UE or the other IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;
utilize the IMS communication service identifier to identify one of the plurality of IMS communication services; and
forward the received SIP message to the identified one of the plurality of IMS communication services;
wherein the identified one of the plurality of IMS communication services is configured to:
receive the SIP message from the IMS protocol stack;
utilize the IMS application reference to identify one of the plurality of IMS applications; and
forward the received SIP message to the identified one of the plurality of IMS applications.', 'a processor coupled to a memory that stores computer program instructions, wherein when the processor executes the instructions, the processor implements an IMS protocol stack;', 'a plurality of IMS communication services in communication with the IMS protocol stack; and', 'a plurality of IMS applications interfaced with the plurality of IMS communication services;', 'wherein the processor controls the IMS protocol stack to:
receive from the UE or the other IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;
utilize the IMS communication service identifier to identify one of the plurality of IMS communication services; and
forward the received SIP message to the identified one of the plurality of IMS communication services;', 'receive from the UE or the other IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;', 'utilize the IMS communication service identifier to identify one of the plurality of IMS communication services; and', 'forward the received SIP message to the identified one of the plurality of IMS communication services;', 'wherein the identified one of the plurality of IMS communication services is configured to:
receive the SIP message from the IMS protocol stack;
utilize the IMS application reference to identify one of the plurality of IMS applications; and
forward the received SIP message to the identified one of the plurality of IMS applications.', 'receive the SIP message from the IMS protocol stack;', 'utilize the IMS application reference to identify one of the plurality of IMS applications; and', 'forward the received SIP message to the identified one of the plurality of IMS applications.17. The IMS network node as recited in claim 16, wherein the IMS protocol stack is configured to read the IMS communication service identifier from a first feature tag in a header of the SIP message.18. The IMS network node as recited in claim 17, wherein the IMS network node is configured to read the IMS application reference from a second feature tag in a header of the SIP message.19. The IMS network node as recited in claim 17, wherein the IMS network node is configured to read the application reference from an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.
20. The IMS network node as recited in claim 17, wherein the IMS network node is configured to read the application reference from a second feature tag in a header of the SIP message and from an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.']
Associated Portfolios

![]() |
![]() |
![]() |
![]() |
---|---|---|---|
Claim charts will soon be available!
|
SUMMARY
ClaimChart-US8572261B2-STO
Patent number:US8572261B2
Claim Chart Type : SEP Claim Chart
Price: 200 €
To view claim charts you must become a Gold or Platinum Member.
Upgrade your subscriptionYou have reached the maximum number of patents which can be associated to your account per your subscription. If you wish to associate more patents
Please upgrade your subscription.Note:
The information in blue was extracted from the third parties (Standard Setting Organisation, Espacenet)
The information in grey was provided by the patent holder
The information in purple was extracted from the FrandAvenue
Explicitly disclosed patent:openly and comprehensibly describes all details of the invention in the patent document.
Implicitly disclosed patent:does not explicitly state certain aspects of the invention, but still allows for these to be inferred from the information provided.
Basis patent:The core patent in a family, outlining the fundamental invention from which related patents or applications originate.
Family member:related patents or applications that share a common priority or original filing.