Granted Patent B2

US 12,706,961 · App. 18/393,214 · Granted Aug 11, 2026

Inventors: Jan Hendrik Lucas Bakker (Fort Worth, TX); Andrew Michael Allen (Hallandale Beach, FL); Adrian Buckley (Tracy, CA)

Assignee: Malikie Innovations Limited

H04L65/1063H04L65/1016H04L65/1104

Abstract

Claims (30)

1 . A method for indicating an application server (AS) capability, the method comprising:

generating, at the AS, a Session Initiation Protocol (SIP) request including a SIP header comprising a token that identifies at least one service supported by the AS and the SIP request further including an address of the AS, wherein the address is a uniform resource identifier (URI) that is included in a Record-Route header, wherein the AS is included in a signaling route;

transmitting, by the AS, the SIP request; and

transmitting, by the AS, a SIP response including the token.

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

3 . The method of claim 1 wherein the token indicates whether the at least one service is provided by the AS as an originating AS or a terminating AS.

4 . The method of claim 1 wherein the token is an IP (Internet Protocol) Multimedia Subsystem (IMS) Communication Service Identifier (ICSI).

5 . The method of claim 4 wherein the URI includes a URI parameter set equal to an ICSI value for a particular service provided by the AS.

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

7 . The method of claim 1 wherein a SIP request that the AS receives from a first UA is a SIP INVITE message.

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

a hard coding of the association; and

execution of an algorithm that performs the association.

9 . A network component comprising a processor configured to:

generate, at the network component, a Session Initiation Protocol (SIP) request including a SIP header comprising a token that identifies at least one service supported by the network component, the SIP request further including an address of the network component, wherein the address is a uniform resource identifier (URI) that is included in a Record-Route header;

transmit by the network component, the SIP request; and

transmit, by the network component, a SIP response including the token.

10 . The network component of claim 9 wherein the URI is a Globally Routable UA URI (GRUU).

11 . The network component of claim 10 wherein the URI contains a ‘gr’ parameter.

12 . The network component of claim 9 wherein the token is an IP (Internet Protocol) Multimedia Subsystem (IMS) Communication Service Identifier (ICSI).

13 . The network component of claim 12 wherein the URI includes a URI parameter that is set equal to the ICSI.

14 . The network component of claim 13 wherein the URI parameter is a g.3gpp.app_ref tag.

15 . The network component of claim 9 , further comprising; receiving, by the network component, a SIP invite from a user agent before generating the SIP request.

16 . The network component of claim 15 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.

17 . The network component of claim 15 wherein the network component is a telephony application server.

18 . The network component of claim 9 wherein the token is associated with the at least one service by one of:

a hard coding of the association; and

execution of an algorithm that performs the association.

Continuity (6)

References Cited (54)