Method and apparatus for identifying an IMS service
A method of indicating IP Multimedia Subsystem (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.
1. A method in a User Equipment (UE) for communicating with an IP Multimedia Subsystem (IMS) network node utilizing Session Initiation Protocol (SIP) signaling, the method comprising:
setting an IMS communication service identifier to identify one of a plurality of IMS communication services;
setting an IMS application reference to identify one of a plurality of IMS applications to be used for handling the IMS communication service identified by the IMS communication service identifier;
generating a SIP message that includes both the IMS communication service identifier and the IMS application reference; and
sending the SIP message to the IMS network node to initiate the identified IMS communication service, and wherein an IMS protocol stack forwards the SIP message to the identified one of the plurality of IMS communication services using the IMS communication service identifier.
2. The method as recited in claim 1 , wherein generating the SIP message includes placing the IMS communication service identifier in the SIP message as a first feature tag in a header of the SIP message.
3. The method as recited in claim 2 , wherein generating the SIP message includes placing the IMS application reference in the SIP message as a second feature tag in a header of the SIP message.
4. The method as recited in claim 2 , wherein generating the SIP message includes placing 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 method as recited in claim 2 , wherein generating the SIP message includes placing 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 method in a User Equipment (UE) for communicating with an IP Multimedia Subsystem (IMS) network node utilizing Session Initiation Protocol (SIP) signaling, the UE including 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, the method comprising:
by the IMS protocol stack:
receiving from the IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;
utilizing the IMS communication service identifier to identify one of the plurality of IMS communication services; and
forwarding the received SIP message to the identified IMS communication service; and
by the identified IMS communication service:
receiving the SIP message from the IMS protocol stack;
utilizing the IMS application reference to identify one of the plurality of IMS applications; and
forwarding the received SIP message to the identified IMS application.
7. The method as recited in claim 6 , comprising reading by the IMS protocol stack, the IMS communication service identifier from a first feature tag in a header of the SIP message.
8. The method as recited in claim 7 , comprising reading by the identified IMS communication service, the IMS application reference from a second feature tag in a header of the SIP message.
9. The method as recited in claim 7 , comprising reading by the identified IMS communication service, the application reference from an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.
10. The method as recited in claim 7 , comprising reading by the identified IMS communication service, 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.
11. A method in a Session Initiation Protocol Application Server (SIP AS) in an IP Multimedia Subsystem (IMS) network, the method comprising:
setting an IMS communication service identifier to identify one of a plurality of IMS communication services;
setting an IMS application reference to identify one of a plurality of IMS applications to be used for handling the IMS communication service identified by the IMS communication service identifier;
generating a SIP message that includes both the IMS communication service identifier and the IMS application reference; and
sending the SIP message to the IMS network node to initiate the identified IMS communication service, and wherein an IMS protocol stack forwards the SIP message to the identified one of the plurality of IMS communication services using the IMS communication service identifier.
12. The method as recited in claim 11 , wherein generating the SIP message includes placing the IMS communication service identifier in the SIP message as a first feature tag in a header of the SIP message.
13. The method as recited in claim 12 , wherein generating the SIP message includes placing the IMS application reference in the SIP message as a second feature tag in a header of the SIP message.
14. The method as recited in claim 12 , wherein generating the SIP message includes placing 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 method as recited in claim 12 , wherein generating the SIP message includes placing 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.
16. A method in a first IP Multimedia Subsystem (IMS) network node for communicating with a User Equipment (UE) or a second IMS network node utilizing Session Initiation Protocol (SIP) signaling, the first IMS network node including 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, the method comprising:
by the IMS protocol stack:
receiving from the UE or the second IMS network node, a Session Initiation Protocol (SIP) message that includes an IMS communication service identifier and an IMS application reference;
utilizing the IMS communication service identifier to identify one of the plurality of IMS communication services; and
forwarding the received SIP message to the identified IMS communication service; and
by the identified IMS communication service:
receiving the SIP message from the IMS protocol stack;
utilizing the IMS application reference to identify one of the plurality of IMS applications; and
forwarding the received SIP message to the identified IMS application.
17. The method as recited in claim 16 , comprising reading by the IMS protocol stack, the IMS communication service identifier from a first feature tag in a header of the SIP message.
18. The method as recited in claim 17 , comprising reading by the identified IMS communication service, the IMS application reference from a second feature tag in a header of the SIP message.
19. The method as recited in claim 17 , comprising reading by the identified IMS communication service, the application reference from an a-line augmenting an m-line in a Session Description Protocol (SDP) part of the SIP message.
20. The method as recited in claim 17 , comprising reading by the identified IMS communication service, 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.