IP Library Granted Patent US 12,587,828
Granted Patent B2
US 12,587,828 · App. 18/005,128 · Granted Mar 24, 2026

Managing multiple subscriber identities in cellular network

Inventors: Kishore Krishne Gowda (Bangalore, IN); Nandagopal Peethambaran Nair Rajalakshmi (Bangalore, IN); Sharath Raveendran (Bangalore, IN); Jitendra Kumar Saini (Bangalore, IN); Sambhram Kanavalli (Bangalore, IN); Nanda Kumar (Bangalore, IN); Frank Frederiksen (Klarup, DK); Jakob Lindbjerg Buthler (Aalborg, DK)
Assignee: Nokia Solutions and Networks Oy
H04W8/20H04W36/0069H04W36/385H04W88/06
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 12,587,828
App. No.
18/005,128
Granted
Mar 24, 2026
Kind
B2
Abstract

This document discloses a solution for sharing information on subscriber identifiers in a network. According to an aspect, a method comprises: storing, in a mobility management node, at least two subscriber identifiers; and transmitting, by the mobility management node to a target network node during setup of a bearer for a first subscriber identifier of the at least two subscriber identifiers, a message comprising at least a second subscriber identifier of the at least two subscriber identifiers.

Claims (34)

1 . An apparatus for a mobility management node that is an access and mobility management function (AMF) in a 5G system controlling a plurality of access nodes, the apparatus comprising:

at least one processor; and

at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to:

store a record for a terminal device in a subscriber identifier database maintained by the AMF, the record comprising at least two subscriber identifiers, the at least two subscriber identifiers comprising a first subscriber identifier and a second subscriber identifier, wherein the second subscriber identifier is associated with a radio resource control (RRC) connection in an idle state, an inactive state, or a connected state, and wherein the record further stores (i) an equipment identifier for the terminal device, and (ii) an identifier of an access node currently serving the second subscriber identifier;

receive, from an access node of the plurality of access nodes, over an NG interface using NGAP, a handover required message requesting a handover procedure for the first subscriber identifier that is internal to the AMF;

receive, from a target network node that is under control of the AMF and before a setup of a bearer for the first subscriber identifier has been initiated, a setup message comprising at least one information element indicating that the target network node accepts information on multiple subscriber identifiers; and

based on the handover required request message and the setup message, transmit, to the target network node during the setup of the bearer as part of the handover procedure, a further handover request message to the target network node, the further handover request message comprising:

the second subscriber identifier encoded in an information element;

at least one equipment identifier for the terminal device, the equipment identifier being included together with the information element in the handover request message; and

a data structure defining a mapping of the first subscriber identifier and the second subscriber identifier to the at least one equipment identifier, the mapping indicating which equipment identifier is currently used by each subscriber identifier and an identifier of an access node serving the second subscriber identifier.

2 . The apparatus of claim 1 , wherein the access node is a first access node controlled by the apparatus and the target network node is a second access node controlled by the apparatus.

3 . The apparatus of claim 2 , wherein the mobility management node is a first mobility management node, and wherein the target network node is a second mobility management node different from the first mobility management node.

4 . An apparatus for a network node comprising:

at least one processor; and

at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to:

transmit, to a mobility management node before a setup of a bearer has been initiated, a setup message comprising an information element indicating that the apparatus accepts information on multiple subscriber identifiers;

based on the setup message, receive, by the network node from the mobility management node controlling a plurality of access nodes, a handover message during the setup of the bearer for a first subscriber identifier, the handover message comprising at least a second subscriber identifier different from the first subscriber identifier, at least one equipment identifier, and a data structure defining a mapping of the first subscriber identifier and the second subscriber identifier to the at least one equipment identifier, wherein the second subscriber identifier is associated with a radio resource control (RRC) connection in an idle state, an inactive state, or a connected state;

store, by the network node, the first subscriber identifier, the second subscriber identifier, the at least one equipment identifier, and the data structure; and

perform, by the network node, at least one procedure using the second subscriber identifier, wherein the at least one procedure is a paging procedure, and wherein performing the paging procedure comprises reducing a paging area for the second subscriber identifier based on a location associated with the first subscriber identifier.

5 . The apparatus of claim 4 , wherein the network node is an access node, and wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to setup the bearer between the access node and the mobility management node.

6 . The apparatus of claim 5 , wherein the mobility management node is a first mobility management node and the network node is a second mobility management node different from the first mobility management node, and wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to setup the bearer between the second mobility management node and an access node controlled by the second mobility management node.

7 . A method comprising:

storing, in a mobility management node a record for a terminal device in a subscriber identifier database maintained by an access and mobility management function (AMF), the record comprising at least two subscriber identifiers, the at least two subscriber identifiers comprising a first subscriber identifier and a second subscriber identifier, wherein the second subscriber identifier is associated with a radio resource control (RRC) connection in an idle state, an inactive state, or a connected state, and wherein the record further stores (i) an equipment identifier for the terminal device, and (ii) an identifier of an access node currently serving the second subscriber identifier;

receiving, from an access node of a plurality of access nodes, over an NG interface using NGAP, a handover required message requesting a handover procedure for the first subscriber identifier that is internal to the AMF;

receiving, from a target network node that is under control of the AMF and before a setup of a bearer for the first subscriber identifier has been initiated, a setup message comprising at least one information element indicating that the target network node accepts information on multiple subscriber identifiers; and

based on the handover request message and the setup message, transmitting, by the mobility management node to the target network node during the setup of the bearer as part of the handover procedure, a further handover request message comprising:

the second subscriber identifier encoded in an information element;

at least one equipment identifier for the terminal device, the equipment identifier being included together with the information element in the handover request message; and

a data structure defining a mapping of the first subscriber identifier and the second subscriber identifier to the at least one equipment identifier, the mapping indicating which equipment identifier is currently used by each subscriber identifier and an identifier of an access node serving the second subscriber identifier.

8 . A method comprising:

transmitting, by an apparatus to a mobility management node before setup of a bearer has been initiated, a setup message comprising an information element indicating that the apparatus accepts information on multiple subscriber identifiers;

based on the setup message, receiving, by a network node from the mobility management node controlling a plurality of access nodes, a handover message during the setup of the bearer for a first subscriber identifier, the handover message comprising at least a second subscriber identifier different from the first subscriber identifier, at least one equipment identifier, and a data structure defining a mapping the first subscriber identifier and the second subscriber identifier to the at least one equipment identifier, wherein the second subscriber identifier is associated with a radio resource control (RRC) connection in an idle state, an inactive state, or a connected state;

storing, by the network node, the first subscriber identifier, the second subscriber identifier, the at least one equipment identifier, and the data structure; and

performing, by the network node, at least one procedure using the second subscriber identifier, wherein the at least one procedure is a paging procedure, and wherein performing the paging procedure comprises reducing a paging area for the second subscriber identifier based on a location associated with the first subscriber identifier.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2023
From: KRISHNE GOWDA, KISHORE; FREDERIKSEN, FRANK; KUMAR, NANDA; PEETHAMBARAN NAIR RAJALAKSHMI, NANDAGOPAL; BUTHLER, JAKOB; RAVEENDRAN, SHARATH; KUMAR SAINI, JITENDRA; KANAVALLI, SAMBHRAM
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 062447/0008 →
Priority Claims (1)
FI 20205757 · Jul 17, 2020 · national
Continuity (1)
Related Publication 20230262563A1 · Aug 17, 2023
References Cited (63)
US 8121601B2 · Huang et al. · 2012 [cited by applicant]
US 8457635B2 · Bachmann et al. · 2013 [cited by applicant]
US 8718688B2 · Shaheen et al. · 2014 [cited by applicant]
US 8818356B2 · Young et al. · 2014 [cited by applicant]
US 11395130B2 · Sabouri-Sichani et al. · 2022 [cited by applicant]
US 20120021744A1 · Chin et al. · 2012 [cited by applicant]
US 20120155428A1 · Bovo et al. · 2012 [cited by applicant]
US 20130303203A1 · Wang et al. · 2013 [cited by applicant]
US 20150065106A1 · Catovic · 2015 [cited by examiner]
US 20150237597A1 · Kanamarlapudi et al. · 2015 [cited by applicant]
US 20150282017A1 · Wang et al. · 2015 [cited by applicant]
US 20160183156A1 · Chin et al. · 2016 [cited by applicant]
US 20170127217A1 · Miao · 2017 [cited by examiner]
US 20190037531A1 · Pantus et al. · 2019 [cited by applicant]
US 20190350027A1 · Centonza · 2019 [cited by examiner]
US 20200068647A1 · Jha · 2020 [cited by examiner]
US 20210044964A1 · Lindheimer · 2021 [cited by examiner]
US 20220053355A1 · Stjernholm · 2022 [cited by examiner]
US 20220295264A1 · Hong · 2022 [cited by examiner]
US 20230093965A1 · Velev · 2023 [cited by examiner]
US 20230232296A1 · Hong · 2023 [cited by examiner]
US 20240244496A1 · Krishne Gowda · 2024 [cited by examiner]
US 20240430755A1 · Talebi Fard · 2024 [cited by examiner]
CN 110710237A · 2020 [cited by applicant]
CN 111277999A · 2020 [cited by applicant]
EP 2605563A1 · 2013 [cited by applicant]
WO 2012138141A2 · 2012 [cited by applicant]
WO 2015180126A1 · 2015 [cited by applicant]
WO 2015180779A1 · 2015 [cited by applicant]
WO 2016118248A1 · 2016 [cited by applicant]
WO 2017012228A1 · 2017 [cited by applicant]
WO 2017027115A1 · 2017 [cited by applicant]
WO 2018141148A1 · 2018 [cited by applicant]
Extended European Search Report received for corresponding European Patent Application No. 21843315.9, dated Jul. 1, 2024, 10 pages. [cited by applicant]
“KI #1, New Sol: Network-based paging filtering”, SA WG2 Meeting #139E, S2-2004589, Agenda : 8.10, LG Electronics, Jun. 1-12, 2020, 4 pages. [cited by applicant]
“K##2: New solution: Resolving paging conflict using MUSIM Assistance Information”, SA WG2 Meeting #139E, S2-2004601, Agenda : 8.10, Nokia, Jun. 1-12, 2020, 6 pages. [cited by applicant]
“Kl#3 New Solution: Coordinated Leaving Using Musim Assistance Information”, SA WG2 Meeting #139E, S2-2003767, Agenda : 8.10, Nokia, Jun. 1-12, 2020, 3 pages. [cited by applicant]
“Inter-system direct forwarding with shared SgNB/gNB”, 3GPP TSG-RAN WG3 #106, R3-197144, Agenda : 31.3.3 , Samsung, Nov. 18-22, 2019, 7 pages. [cited by applicant]
Extended European Search Report received for corresponding European Patent Application No. 21842242.6, dated Jul. 15, 2024, 10 pages. [cited by applicant]
“On the paging area management for light connection”, 3GPP TSG-RAN WG2 Meeting #95, R2-165258, Agenda item: 8.9.1, ASUSTeK, Aug. 22-26, 2016, 3 pages. [cited by applicant]
“Revised SID: Study on system enablers for multi-SIM devices”, TSG SA Meeting #SP-83, SP-190248, Agenda: 17B.19, SA WG2, Mar. 20-22, 2019, 4 pages. [cited by applicant]
“New Rel-17 SID proposal: Study on multi-SIM devices in RAN”, 3GPP TSG RAN Meeting #83, RP-190282, Agenda: 9.1.2, vivo, Mar. 18-21, 2019, 4 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Support for Multi-USIM Devices (Release 17)”, 3GPP TR 22.834, V17.2.0, Dec. 2019, pp. 1-17. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for Machine-Type Communications (MTC); Stage 1 (Release 15)”, 3GPP TS 22.368, V15.0.0, Jul. 2019, pp. … [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 16)”, 3GPP TS 38.423, V16.0.0, Dec. 2019, pp. 1-330. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.501, V16.3.0, Dec. 2019, pp. 1-417. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 16)”, 3GPP TS 38.300, V16.0.0, Dec. 2019, pp. 1-101. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 15)”, 3GPP TS 3… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode (Release 15)”, 3GPP TS 36.304, V1… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 16)”, 3GPP TS 36.413, V16.1.… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 16)”, 3GPP TS 38.413, V16.1.0, Mar. 2020, pp. 1-341. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.501, V16.4.0, Mar. 2020, pp. 1-430. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 16)”, 3GPP TS 38.300, V16.1.0, Mar. 2020, pp. 1-133. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 16)”, 3GPP TS 3… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode (Release 16)”, 3GPP TS 36.304, V1… [cited by applicant]
“LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description (3GPP TS 36,401 version 8.6.0 Release 8)”, ETSI TS 136 401, V8.6.0, Jul. 2009, pp. 1-20. [cited by applicant]
Tayyab et al., “A Survey on Handover Management: From LTE to NR”, IEEE Access, vol. 7, Aug. 26, 2019, pp. 118907-118930. [cited by applicant]
Office action received for corresponding Finnish Patent Application No. 20205753, dated Mar. 9, 2021, 7 pages. [cited by applicant]
Office action received for corresponding Finnish Patent Application No. 20205757, dated Mar. 18, 2021, 7 pages. [cited by applicant]
International Search Report and Written Opinion received for corresponding Patent Cooperation Treaty Application No. PCT/FI2021/050461, dated Sep. 29, 2021, 16 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) (Release 17)”, 3GPP TR 23… [cited by applicant]
International Search Report and Written Opinion received for corresponding Patent Cooperation Treaty Application No. PCT/FI2021/050462, dated Oct. 5, 2021, 16 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.502, V16.5.0, Jul. 2020, pp. 1-594. [cited by applicant]