# US 12,603,779 B2 · Authorizing third party specific user identities

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,603,779 B2
- Document ID: US12603779B2
- Status: Granted
- Kind: B2
- Application number: 18/728,648
- Filed: 2022-03-29
- Published: 2025-05-15
- Granted: 2026-04-14
- Earliest claimed: 2022-03-29
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Kefeng Zhang; Haris Zisimopoulos; Sebastian Speicher; Yan Li; Zhimin Du
- Web page: https://patentgrep.com/patent/US12603779B2

## CPC

- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 63/126: {the source of the received data}
- H04L 65/1045: Proxies, e.g. for session initiation protocol [SIP]
- H04L 65/1046: Call controllers; Call servers
- H04L 65/1069: Session establishment or de-establishment
- H04L 65/1073: Registration or de-registration
- H04L 65/1104: Session initiation protocol [SIP]
- H04W 12/108: Source integrity
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04L 2209/80: Wireless
- H04W 12/069: using certificates or pre-shared keys
- H04W 12/126: Anti-theft arrangements, e.g. protection against subscriber identity module [SIM] cloning
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, an authentication, authorization, and accounting (AAA) server may authorize a use of a third party specific user identity based at least in part on verifying a token associated with a session initiation protocol (SIP) INVITE message with the third party specific user identity. The (AAA) server may transmit, to a call session control function (CSCF) of an originating service provider via a network exposure function (NEF) of the originating service provider, an enterprise name card that indicates the third party specific user identity based at least in part on authorizing the use of the third party specific user identity. Numerous other aspects are described.

## Claims

### Claim 1

A method of wireless communication performed by a call session control function (CSCF) of an originating service provider for wireless communication, comprising:
receiving, from a session initiation protocol (SIP) user agent (UA) of the originating service provider, a SIP INVITE message with a third party specific user identity and a token;
transmitting the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); and
receiving, from the AAA server via the NEF, an enterprise name card that indicates the third party specific user identity, wherein the enterprise name card is received based at least in part on a verification of the token.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
transmitting, to a SIP UA of a terminating service provider, the enterprise name card that indicates the third party specific user identity for display on the SIP UA of the terminating service provider.

### Claim 3 (depends on 1)

The method of claim 1, wherein the token is assigned by the AAA server to the SIP UA of the originating service provider.

### Claim 4 (depends on 1)

The method of claim 1, wherein the enterprise name card that indicates the third party specific user identity indicates one or more of: a name of a user, a photo of the user, a user identifier, or a company associated with the user.

### Claim 5 (depends on 1)

The method of claim 1, wherein the verification of the token is based at least in part on signaling between the CSCF of the originating service provider and the AAA server via the NEF.

### Claim 6 (depends on 1)

The method of claim 1, wherein a derivation of the enterprise name card that indicates the third party specific user identity is based at least in part on a signature-based handling of asserted information using tokens (SHAKEN) framework.

### Claim 7 (depends on 1)

The method of claim 1, wherein the AAA server is a third party AAA server, and wherein an authorization of the AAA server is based at least in part on the NEF.

### Claim 8

A method of wireless communication performed by an authentication, authorization, and accounting (AAA) server, comprising:
authorizing a use of a third party specific user identity based at least in part on verifying a token associated with a session initiation protocol (SIP) INVITE message with the third party specific user identity; and
transmitting, to a call session control function (CSCF) of an originating service provider via a network exposure function (NEF) of the originating service provider, an enterprise name card that indicates the third party specific user identity based at least in part on authorizing the use of the third party specific user identity.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
transmitting the token to a SIP user agent (UA) of the originating service provider, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

### Claim 10 (depends on 8)

The method of claim 8, wherein the SIP INVITE message is created with the third party specific user identity and the token.

### Claim 11 (depends on 8)

The method of claim 8, wherein the enterprise name card that indicates the third party specific user identity is for display on a SIP UA of a terminating service provider.

### Claim 12 (depends on 8)

The method of claim 8, wherein the enterprise name card that indicates the third party specific user identity indicates one or more of: a name of a user, a photo of the user, a user identifier, or a company associated with the user.

### Claim 13 (depends on 8)

The method of claim 8, wherein authorizing the use of the third party specific user identity is based at least in part on signaling between the AAA server and the CSCF of the originating service provider via the NEF of the originating service provider.

### Claim 14 (depends on 8)

The method of claim 8, wherein a derivation of the enterprise name card that indicates the third party specific user identity is based at least in part on a signature-based handling of asserted information using tokens (SHAKEN) framework.

### Claim 15 (depends on 8)

The method of claim 8, wherein the AAA server is a third party AAA server, and wherein an authorization of the AAA server is based at least in part on a network exposure function.

### Claim 16

An apparatus of a call session control function (CSCF) of an originating service provider for wireless communication, comprising:
a memory; and
one or more processors, coupled to the memory, configured to:
receive, from a session initiation protocol (SIP) user agent (UA) of the originating service provider, a SIP INVITE message with a third party specific user identity and a token;
transmit the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); and
receive, from the AAA server via the NEF, an enterprise name card that indicates the third party specific user identity, wherein the enterprise name card is received based at least in part on a verification of the token.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein the one or more processors are configured to:
transmit, to a SIP UA of a terminating service provider, the enterprise name card that indicates the third party specific user identity for display on the SIP UA of the terminating service provider.

### Claim 18 (depends on 16)

The apparatus of claim 16, wherein the token is assigned by the AAA server to the SIP UA of the originating service provider.

### Claim 19 (depends on 16)

The apparatus of claim 16, wherein the enterprise name card that indicates the third party specific user identity indicates one or more of: a name of a user, a photo of the user, a user identifier, or a company associated with the user.

### Claim 20 (depends on 16)

The apparatus of claim 16, wherein the verification of the token is based at least in part on signaling between the CSCF of the originating service provider and the AAA server via the NEF.

### Claim 21 (depends on 16)

The apparatus of claim 16, wherein a derivation of the enterprise name card that indicates the third party specific user identity is based at least in part on a signature-based handling of asserted information using tokens (SHAKEN) framework.

### Claim 22 (depends on 16)

The apparatus of claim 16, wherein the AAA server is a third party AAA server, and wherein an authorization of the AAA server is based at least in part on the NEF.

### Claim 23

An apparatus of an authentication, authorization, and accounting (AAA) server, comprising:
a memory; and
one or more processors, coupled to the memory, configured to:
authorize a use of a third party specific user identity based at least in part on verifying a token associated with a session initiation protocol (SIP) INVITE message with the third party specific user identity; and
transmit, to a call session control function (CSCF) of an originating service provider via a network exposure function (NEF) of the originating service provider, an enterprise name card that indicates the third party specific user identity based at least in part on authorizing the use of the third party specific user identity.

### Claim 24 (depends on 23)

The apparatus of claim 23, wherein the one or more processors are configured to:
transmit the token to a SIP user agent (UA) of the originating service provider, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

### Claim 25 (depends on 23)

The apparatus of claim 23, wherein the SIP INVITE message is created with the third party specific user identity and the token.

### Claim 26 (depends on 23)

The apparatus of claim 23, wherein the enterprise name card that indicates the third party specific user identity is for display on a SIP UA of a terminating service provider.

### Claim 27 (depends on 23)

The apparatus of claim 23, wherein the enterprise name card that indicates the third party specific user identity indicates one or more of: a name of a user, a photo of the user, a user identifier, or a company associated with the user.

### Claim 28 (depends on 23)

The apparatus of claim 23, wherein the one or more processors are configured to authorize the use of the third party specific user identity based at least in part on signaling between the AAA server and the CSCF of the originating service provider via the NEF of the originating service provider.

### Claim 29 (depends on 23)

The apparatus of claim 23, wherein a derivation of the enterprise name card that indicates the third party specific user identity is based at least in part on a signature-based handling of asserted information using tokens (SHAKEN) framework.

### Claim 30 (depends on 23)

The apparatus of claim 23, wherein the AAA server is a third party AAA server, and wherein an authorization of the AAA server is based at least in part on a network exposure function.