IP Library Granted Patent US 11,490,255
Granted Patent B2
US 11,490,255 · App. 17/064,234 · Granted Nov 1, 2022

RCS authentication

Inventors: Anish Sharma (McKinney, TX); Bejoy Pankajakshan (Allen, TX)
Assignee: Mavenir Networks, Inc.
H04W12/068H04L69/24H04W8/04H04W12/04H04W12/08H04W80/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,490,255
App. No.
17/064,234
Granted
Nov 1, 2022
Kind
B2
Abstract

In a system and a method for providing authentication for Rich Communication Services (RCS) application on a user equipment (UE), a Proxy Call Session Control Function (P-CSCF) of the IMS receives a SIP REGISTER request message sent from an IMS Session Initiation Protocol (SIP) client on the UE as part of an authentication of the IMS SIP client. A Serving Call Session Control Function (S-CSCF) of the IMS or a registration service performs an Authentication and Key Agreement (AKA) challenge with the IMS SIP client as part of the authentication. A Home Subscriber Server (HSS) of the IMS or a Unified Data Management (UDM) function provides, upon successful authentication of the IMS SIP client, an initial authorization grant for the IMS SIP client. The RCS application, after obtaining the initial authorization grant, registers for RCS service with the RCS network, via RCS Application Programming Interface Gateway (API GW).

Claims (53)

1. A method of providing authentication for Rich Communication Services (RCS) application on a user equipment (UE) for RCS service provided by an RCS network, wherein the RCS network is separate from an IP Multimedia Subsystem (IMS), and wherein IMS Session Initiation Protocol (SIP) client is provided on the UE, the method comprising:

performing an authentication of the IMS SIP client, wherein the authentication comprises:

sending, by the IMS SIP client, a SIP REGISTER request message to a Proxy Call Session Control Function (P-CSCF) of the IMS; and

performing, by one of a Serving Call Session Control Function (S-CSCF) of the IMS or a registration service, an Authentication and Key Agreement (AKA) challenge with the IMS SIP client;

providing, by one of a Home Subscriber Server (HSS) of the IMS or a Unified Data Management (UDM) function module, an initial authorization grant for the IMS SIP client, upon successful authentication of the IMS SIP client;

obtaining, by the RCS application, the initial authorization grant; and registering, by the RCS application, via RCS Application Programming Interface Gateway (API GW) of the RCS network, for RCS service with the RCS network;

wherein the initial authorization grant comprises one of an access token or an authorization code, and wherein the initial authorization grant is provided by one of the HSS or the UDM function module to one of the S-CSCF or the registration service, and wherein one of the S-CSCF or the registration service provides the initial authorization grant to the IMS SIP client; and

upon receipt of the initial authorization grant by the IMS SIP client, i) the initial authorization grant is transmitted by the IMS SIP client to the RCS application; or ii) the initial authorization grant is transmitted by the IMS SIP client to the RCS application in response to a query from the RCS application.

2. The method of claim 1 , wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW.

3. The method of claim 1 , wherein the initial authorization grant is an authorization code, and wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW; and

obtaining, by the RCS API GW, an access token from one of the HSS or the UDM function module.

4. A method of providing authentication for Rich Communication Services (RCS) application on a user equipment (UE) for RCS service provided by an RCS network, wherein the RCS network is separate from an IP Multimedia Subsystem (IMS), and wherein IMS Session Initiation Protocol (SIP) client is provided on the UE, the method comprising:

performing an authentication of the IMS SIP client, wherein the authentication comprises:

sending, by the IMS SIP client, a SIP REGISTER request message to a Proxy Call Session Control Function (P-CSCF) of the IMS; and

performing, by one of a Serving Call Session Control Function (S-CSCF) of the IMS or a registration service, an Authentication and Key Agreement (AKA) challenge with the IMS SIP client;

providing, by one of a Home Subscriber Server (HSS) of the IMS or a Unified Data Management (UDM) function module, an initial authorization grant for the IMS SIP client, upon successful authentication of the IMS SIP client;

obtaining, by the RCS application, the initial authorization grant; and

registering, by the RCS application, via RCS Application Programming Interface Gateway (API GW) of the RCS network, for RCS service with the RCS network;

wherein the initial authorization grant comprises one of an access token or an authorization code, and wherein the initial authorization grant is provided by one of the HSS or the UDM function module to one of the P-CSCF and wherein the P-CSCF provides the initial authorization grant to the IMS SIP client;

upon receipt of the initial authorization grant by the IMS SIP client, i) the initial authorization grant is transmitted by the IMS SIP client to the RCS application; or ii) the initial authorization grant is transmitted by the IMS SIP client to the RCS application in response to a query from the RCS application.

5. The method of claim 4 , wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW.

6. The method of claim 4 , wherein the initial authorization grant is an authorization code, and wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW; and

obtaining, by the RCS API GW, an access token from one of the HSS or the UDM function module.

7. A system for providing authentication for Rich Communication Services (RCS) application on a user equipment (UE) for RCS service provided by an RCS network, wherein the RCS network is separate from an IP Multimedia Subsystem (IMS), and wherein IMS Session Initiation Protocol (SIP) client is provided on the UE, the system comprising:

a hardware processor executing instructions stored on a memory to implement a Proxy Call Session Control Function (P-CSCF) of the IMS configured to receive a SIP REGISTER request message sent from an IMS SIP client as part of an authentication of the IMS SIP client;

a hardware processor executing instructions stored on a memory to implement one of a Serving Call Session Control Function (S-CSCF) of the IMS or a registration service configured to perform an Authentication and Key Agreement (AKA) challenge with the IMS SIP client as part of the authentication of the IMS SIP client; and

a hardware processor executing instructions stored on a memory to implement one of a Home Subscriber Server (HSS) of the IMS or a Unified Data Management (UDM) function module configured to provide an initial authorization grant for the IMS SIP client, upon successful authentication of the IMS SIP client; wherein the RCS application, after obtaining the initial authorization grant, registers for RCS service with the RCS network, via RCS Application Programming Interface Gateway (API GW) of the RCS network;

wherein the initial authorization grant comprises one of an access token or an authorization code, and wherein the initial authorization grant is provided by one of the HSS or the UDM function module to one of the S-CSCF or the registration service, and wherein one of the S-CSCF or the registration service provides the initial authorization grant to the IMS SIP client; and

upon receipt of the initial authorization grant by the IMS SIP client,

i) transmit, by the IMS SIP client, the initial authorization grant to the RCS application; or

ii) transmit, by the IMS SIP client, the initial authorization grant to the RCS application in response to a query from the RCS application.

8. The system of claim 7 , wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW.

9. The system of claim 7 , wherein the initial authorization grant is an authorization code, and wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW; and

obtaining, by the RCS API GW, an access token from one of the HSS or the UDM function module.

10. A system for providing authentication for Rich Communication Services (RCS) application on a user equipment (UE) for RCS service provided by an RCS network, wherein the RCS network is separate from an IP Multimedia Subsystem (IMS), and wherein IMS Session Initiation Protocol (SIP) client is provided on the UE, the system comprising:

a hardware processor executing instructions stored on a memory to implement a Proxy Call Session Control Function (P-CSCF) of the IMS configured to receive a SIP REGISTER request message sent from an IMS SIP client as part of an authentication of the IMS SIP client;

a hardware processor executing instructions stored on a memory to implement one of a Serving Call Session Control Function (S-CSCF) of the IMS or a registration service configured to perform an Authentication and Key Agreement (AKA) challenge with the IMS SIP client as part of the authentication of the IMS SIP client; and

a hardware processor executing instructions stored on a memory to implement one of a Home Subscriber Server (HSS) of the IMS or a Unified Data Management (UDM) function module configured to provide an initial authorization grant for the IMS SIP client, upon successful authentication of the IMS SIP client; wherein the RCS application, after obtaining the initial authorization grant, registers for RCS service with the RCS network, via RCS Application Programming Interface Gateway (API GW) of the RCS network;

wherein the initial authorization grant comprises one of an access token or an authorization code, and wherein the initial authorization grant is provided by one of the HSS or the UDM function module to the P-CSCF, and wherein the P-CSCF provides the initial authorization grant to the IMS SIP client; and

upon receipt of the initial authorization grant by the IMS SIP client,

i) transmit, by the IMS SIP client, the initial authorization grant to the RCS application; or

ii) transmit, by the IMS SIP client, the initial authorization grant to the RCS application in response to a query from the RCS application.

11. The system of claim 10 , wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW.

12. The system of claim 10 , wherein the initial authorization grant is an authorization code, and wherein the registering via the RCS API GW comprises:

sending, by the RCS application, a message containing the initial authorization grant to the RCS API GW; and

obtaining, by the RCS API GW, an access token from one of the HSS or the UDM function module.

Assignments (13)
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 069115 AND FRAME 0815 Recorded Jul 31, 2025
From: GLAS USA LLC
To: MAVENIR NETWORKS, INC.
Reel/Frame 072307/0408 →
GRANT OF SECURITY INTEREST - PATENTS Recorded Jul 29, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: GLAS USA LLC
Reel/Frame 072245/0764 →
RELEASE OF SECURITY INTERESTS (SIDECAR) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR NETWORKS, INC.
Reel/Frame 072262/0363 →
RELEASE OF SECURITY INTERESTS (SYNDICATED) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR NETWORKS, INC.
Reel/Frame 072262/0409 →
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 067554 AND FRAME 0789 Recorded Jul 29, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR NETWORKS, INC.
Reel/Frame 072263/0211 →
SECURITY INTEREST Recorded Jul 28, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: BLUE TORCH FINANCE LLC
Reel/Frame 072268/0439 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 4, 2024
From: MAVENIR NETWORKS, INC.
To: GLAS USA LLC
Reel/Frame 069115/0815 →
RELEASE OF SECURITY INTEREST RECORDED AT R/F 068453/0642 Recorded Oct 4, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR NETWORKS, INC.
Reel/Frame 069117/0074 →
SECURITY INTEREST Recorded Aug 30, 2024
From: MAVENIR NETWORKS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 068453/0642 →
SECURITY INTEREST Recorded May 29, 2024
From: MAVENIR NETWORKS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 067554/0789 →
SECURITY AGREEMENT Recorded Jul 13, 2022
From: MAVENIR NETWORKS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 060640/0125 →
SECURITY AGREEMENT Recorded Aug 18, 2021
From: MAVENIR NETWORKS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 057221/0866 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2020
From: SHARMA, ANISH; PANKAJAKSHAN, BEJOY
To: MAVENIR NETWORKS, INC.
Reel/Frame 053988/0954 →