System and Method for Sharing a SIP Communication Service Identifier

• US 20090068996A1
• Filed: 09/11/2008
• Published: 03/12/2009
• Est. Priority Date: 09/11/2007
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Research In Motion Corporation (Blackberry Limited)
• Inventors: ALLEN, Andrew, BUCKLEY, Adrian, BAKKER, John-Luc
• Granted Patent: US 8,249,561 B2
• Time in Patent Office: Days
• US Class Current: 455/414.100
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

A method for providing a user agent (UA) with service identification data. The method includes an application server (AS) transmitting Session Initiation Protocol (SIP) data. The SIP data comprises an identifier of the AS and a service identifier for at least one service supported by the AS. The method further includes the UA receiving the SIP data.

Claims

1. A method for providing a user agent (UA) with service identification data, comprising:

an application server (AS) transmitting Session Initiation Protocol (SIP) data comprising;

an identifier of the AS, and

a service identifier for at least one service supported by the AS; and

the UA receiving the SIP data.

2. The method of claim 1 wherein the identifier of the AS is a uniform resource identifier (URI).

3. The method of claim 2 wherein the URI is Globally Routable UA URI (GRUU).

4. The method of claim 2 wherein the URI contains a ‘

gr’

parameter.

5. The method of claim 2 wherein the service identifier is an IP (Internet Protocol) Multimedia Subsystem (IMS) Communication Service Identifier (ICSI).

6. The method of claim 5 wherein a URI parameter in the URI is set equal to the ICSI.

7. The method of claim 6 wherein the URI parameter is a g.3ppp.app_ref tag.

8. The method of claim 2 wherein the URI is included in one of:

a Record-Route header;

a Record header;

a Via header; and

a Contact address.

9. The method of claim 8 wherein the URI is included in a SIP INVITE message.

10. The method of claim 9 wherein a user portion of the URI identifies at least one of:

a UA that originated the SIP INVITE message; and

a UA that terminates the SIP INVITE message.

11. The method of claim 1 wherein the service identifier is associated with the at least one service by one of:

an agreement between the UA and the AS;

a hard coding of the association; and

execution of an algorithm that performs the association.

12. A user agent (UA) comprising:

a processor configured to receive Session Initiation Protocol (SIP) data comprising;

an identifier of an application server (AS); and

a service identifier for at least one service supported by the AS.

13. The UA of claim 12 wherein the identifier of the AS is a uniform resource identifier (URI).

14. The UA of claim 13 wherein the URI is Globally Routable UA URI (GRUU).

15. The UA of claim 13 wherein the URI contains a ‘

gr’

parameter.

16. The UA of claim 13 wherein the service identifier is an IP (Internet Protocol) Multimedia Subsystem (IMS) Communication Service Identifier (ICSI).

17. The UA of claim 16 wherein a URI parameter in the URI is set equal to the ICSI.

18. The UA of claim 17 wherein the URI parameter is a g.3ppp.app_ref tag.

19. The UA of claim 13 wherein the URI is included in one of:

a Record-Route header;

a Record header;

a Via header; and

a Contact address.

20. The UA of claim 19 wherein the URI is included in a SIP INVITE message.

21. The UA of claim 20 wherein a user portion of the URI identifies at least one of:

a UA that originated the SIP INVITE message; and

a UA that terminates the SIP INVITE message.

22. The UA of claim 12 wherein the service identifier is associated with the at least one service by one of:

an agreement between the UA and the AS;

a hard coding of the association; and

execution of an algorithm that performs the association.

23. A network component comprising:

a processor configured to transmit Session Initiation Protocol (SIP) data comprising;

an identifier of the network component; and

a service identifier for at least one service supported by the network component.

24. The network component of claim 23 wherein the identifier of the network component is a uniform resource identifier (URI).

25. The UA of claim 24 wherein the URI is Globally Routable UA URI (GRUU).

26. The UA of claim 24 wherein the URI contains a ‘

gr’

parameter.

27. The network component of claim 24 wherein the service identifier is an IP (Internet Protocol) Multimedia Subsystem (IMS) Communication Service Identifier (ICSI).

28. The network component of claim 27 wherein a URI parameter in the URI is set equal to the ICSI.

29. The network component of claim 28 wherein the URI parameter is a g.3ppp.app_ref tag.

30. The network component of claim 24 wherein the URI is included in one of:

a Record-Route header;

a Record header;

a Via header; and

a Contact address.

31. The network component of claim 30 wherein the URI is included in a SIP INVITE message.

32. The network component of claim 31 wherein a user portion of the URI identifies at least one of:

a user agent that originated the SIP INVITE message; and

a user agent that terminates the SIP INVITE message.

33. The network component of claim 23 wherein the service identifier is associated with the at least one service by one of:

an agreement between a user agent and the network component;

a hard coding of the association; and

execution of an algorithm that performs the association.

34. The network component of claim 23 wherein the network component is one of:

an application server; and

a telephony application server.