IP Library Granted Patent US 11,917,521
Granted Patent B2
US 11,917,521 · App. 17/576,072 · Granted Feb 27, 2024

Method and apparatus for unique identification of individual users in the radio access network (RAN) intelligent controller

Inventors: Rajarajan Sivaraj (Plano, TX); Peter McCann (Bridgewater, NJ); Kuntal Chowdhury (Andover, MA)
Assignee: Mavenir Systems, Inc.
H04W40/246H04W8/005H04W8/26H04W80/02
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,917,521
App. No.
17/576,072
Granted
Feb 27, 2024
Kind
B2
Abstract

A method of uniquely identifying a user equipment (UE) connected to a radio access network (RAN) includes: providing a radio access network intelligent controller (RIC) component associated with the RAN; configuring, by a packet data convergence protocol (PDCP) layer, a default data radio bearer (DRB) for the UE to maintain Internet Protocol (I) Protocol Data Unit (PDU) connectivity with the RAN; and using, by the RIC, one of NG uplink (UL) user plane (UP) Transport Layer Information or S1 UL UP Transport Layer Information of the default DRB for uniquely identifying the UE for the entire time the UE is connected to the RAN. The unique identification for the UE is retained across at least one of i) multiple connectivity sessions for the UE, ii) multiple mobility sessions for the UE, and iii) multiple context sessions for the UE.

Claims (43)

1. A method of uniquely identifying a user equipment (UE) connected to a radio access network (RAN), comprising:

providing a radio access network intelligent controller (RIC) component associated with the RAN;

configuring, by a packet data convergence protocol (PDCP) layer, a default data radio bearer (DRB) for the UE to maintain Internet Protocol (I) Protocol Data Unit (PDU) connectivity with the RAN; and

using, by the RIC, one of NG uplink (UL) user plane (UP) Transport Layer Information or S1 UL UP Transport Layer Information of the default DRB for uniquely identifying the UE for the entire time the UE is connected to the RAN.

2. The method of claim 1 , wherein the unique identification is retained across at least one of i) multiple connectivity sessions for the UE, ii) multiple mobility sessions for the UE, and iii) multiple context sessions for the UE.

3. The method of claim 1 , wherein:

the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information is commonly exchanged as part of UE-associated messages across all the network interfaces in the RAN.

4. The method of claim 2 , wherein the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information is exchanged in at least one of the following interfaces: F1 interface, E1 interface, Xn interface, NG interface, X2 interface, and S1 interface.

5. The method of claim 4 , wherein the UE is uniquely identified by correlating the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB with at least one other RAN network-interface-specific identifier for the UE.

6. The method of claim 5 , wherein the at least one other RAN network-interface-specific identifier for the UE includes at least one RAN UE identifier used over at least one of the following interfaces: F1 interface, E1 interface, Xn interface, NG interface, X2 interface, and S1 interface.

7. The method of claim 1 , wherein:

the UE is uniquely identified by correlating the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB with at least one other RAN network-interface-specific identifier for the UE used over at least one of the following interfaces: F1 interface, E1 interface, Xn interface, NG interface, X2 interface, and S1 interface.

8. The method of claim 7 , wherein in initial access to the RAN by the UE, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in at least one of a call flow between Access and Mobility Management Function (AMF) to gNodeB-Centralized Unit-Control Plane (gNB-CU-CP), a call flow between gNB-CU-CP and gNodeB-Centralized Unit-User Plane (gNB-CU-UP), and a call flow between gNB-CU-CP and gNodeB-Distributed Unit (gNB-DU); and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over at least one of the NG interface, the E1 interface, and the F1 interface.

9. The method of claim 7 , wherein in intra-centralized-unit (CU), intra-distributed-unit (DU), inter-cell handover for the UE, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in a call flow between gNodeB-Centralized Unit (gNB-CU) and gNodeB-Distributed Unit (gNB-DU); and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over the F1 interface.

10. The method of claim 7 , wherein in intra-centralized-unit (CU), inter-distributed-unit (DU), inter-cell handover for the UE, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in a call flow between gNodeB-Centralized Unit (gNB-CU) and gNodeB-Distributed Unit (gNB-DU); and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over the F1 interface.

11. The method of claim 7 , wherein in inter-centralized-unit-control plane (CU-CP) handover for the UE, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in at least one of a call flow between a source gNodeB-CU-CP (gNB-CU-CP) and a target gNodeB-CU-CP (gNB-CU-CP), a call flow between the target gNB-CU-CP and a target gNodeB-Centralized-Unit-User Plane (gNB-CU-UP), a call flow between a source gNB-CU-UP and the source gNB-CU-CP, and a call flow between the target gNB-CU-UP and the target gNB-CU-CP; and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over at least one of the Xn interface, the E1 interface, and the F1 interface.

12. The method of claim 7 , wherein in inter-centralized-unit-user-plane (CU-UP) handover for the UE, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in at least one of a call flow between a gNodeB-centralized-unit-control plane (gNB-CU-CP) and a target gNodeB-Centralized-Unit-User Plane (gNB-CU-UP), a call flow between the gNB-CU-CP and a source gNB-CU-UP, and a call flow between the gNB-CU-CP and the target gNB-CU-UP; and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over at least one of the E1 interface and the F1 interface.

13. The method of claim 7 , wherein in at least one of UE context release and bearer context release procedure, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in at least one of a call flow between a gNodeB-centralized-unit-control plane (gNB-CU-CP) and a gNodeB-Centralized-Unit-User Plane (gNB-CU-UP), and a call flow between the gNB-CU-CP and a gNB-DU; and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over at least one of the E1 interface and the F1 interface.

14. The method of claim 13 , wherein the at least one other RAN network-interface-specific identifier for the UE includes at least one of gNB-CU-CP UE E1AP ID used over the E1 interface, gNB-CU-UP UE E1AP ID used over the E1 interface, gNB-CU UE F1AP ID used over the F1 interface, and the gNB DU UE F1AP ID used over the F1 interface.

15. The method of claim 7 , wherein in Radio Resource Control (RRC) reestablishment procedure, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in at least one of a call flow between gNodeB-Centralized Unit (gNB-CU) and gNodeB-Distributed Unit (gNB-DU), and a call flow between a source gNB and a target gNB; and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over at least one of the F1 interface and the Xn interface.

16. The method of claim 15 , wherein the at least one other RAN network-interface-specific identifier for the UE includes at least one of gNB-CU UE F1AP ID used over the F1 interface, gNB-DU UE F1AP ID used over the F1 interface, UE XnAP ID for the source gNB used over the Xn interface, and UE XnAP ID for the target gNB used over the Xn interface.

17. The method of claim 7 , wherein for transition of Radio Resource Control (RRC) states from RRC_INACTIVE to RRC_CONNECTED for the UE, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in at least one of a call flow between gNodeB-distributed-unit (gNB-DU) and a gNodeB-centralized-unit (gNB-CU), and a call flow between a gNodeB-centralized-unit-control-plane (gNB-CU-CP) and the gNB-DU; and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over at least one of the F1 interface and the E1 interface.

18. The method of claim 17 , wherein the at least one other RAN network-interface-specific identifier for the UE includes at least one of gNB-CU-CP UE E1AP ID used over the E1 interface, gNB-CU-UP UE E1AP ID used over the E1 interface, gNB-CU UE F1AP ID used over the F1 interface, and the gNB DU UE F1AP ID used over the F1 interface.

19. The method of claim 7 , wherein for transition of Radio Resource Control (RRC) states from RRC_CONNECTED to RRC_INACTIVE for the UE, at least one of:

i) the one of the NG UL UP Transport Layer Information or the S1 UL UP Transport Layer Information of the default DRB is available in at least one of a call flow between a gNodeB-centralized-unit-control plane (gNB-CU-CP) and a gNodeB-Centralized-Unit-User Plane (gNB-CU-UP); and

ii) the at least one other RAN network-interface-specific identifier for the UE includes at least one identifier for the UE used over at least one of the F1 interface and the E1 interface.

20. The method of claim 19 , wherein the at least one other RAN network-interface-specific identifier for the UE includes at least one of gNB-CU-CP UE E1AP ID used over the E1 interface, gNB-CU-UP UE E1AP ID used over the E1 interface, gNB-CU UE F1AP ID used over the F1 interface, and the gNB DU UE F1AP ID used over the F1 interface.

Assignments (13)
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 069113 AND FRAME 0558 Recorded Jul 31, 2025
From: GLAS USA LLC
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072308/0172 →
RELEASE OF SECURITY INTERESTS (SIDECAR) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0041 →
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 INTEREST IN COLLATERAL RECORDED AT REEL 067565 AND FRAME 0678 Recorded Jul 29, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0421 →
RELEASE OF SECURITY INTERESTS (SYNDICATED) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0121 →
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 →
RELEASE OF SECURITY INTEREST Recorded Oct 4, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 069113/0596 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 4, 2024
From: MAVENIR SYSTEMS, INC.
To: GLAS USA LLC
Reel/Frame 069113/0558 →
SECURITY INTEREST Recorded Aug 30, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 068822/0966 →
SECURITY INTEREST Recorded May 29, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 067565/0678 →
SECURITY AGREEMENT SUPPLEMENT Recorded Jul 13, 2022
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 060640/0155 →
SECURITY AGREEMENT Recorded Jul 13, 2022
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 060641/0242 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 14, 2022
From: SIVARAJ, RAJARAJAN; MCCANN, PETER; CHOWDHURY, KUNTAL
To: MAVENIR SYSTEMS INC
Reel/Frame 059255/0556 →
Continuity (2)
Provisional Application 63139333 · Jan 20, 2021
Related Publication 20220232452A1 · Jul 21, 2022