Method for node, method for UE, node and UE
Through a combined registration method that works collaboratively between the core network node and the access network node, the signaling and delay problems in the multi-SIM UE registration, re-registration and unregistration process are solved, and more efficient and reliable multi-SIM UE operation is achieved.
Patent Information
- Application Number
- CN202510194930.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-05-03
- Filing Date
- 2020-04-24
- Publication Date
- 2025-05-13
AI Technical Summary
The prior art is difficult to effectively solve the problems of multi-SIM UE registration, re-registration and cancellation in the network, resulting in increased signaling and delay delay, affecting the normal operation of multi-SIM UEs.
A combined registration method for multiple SIM UEs is proposed, allowing multiple SIM UEs to register and/or cancel registration of more than one SIM at the same time, and reduce signaling and delays through the coordinated work of the core network node and the access network node.
The combined registration method significantly reduces signaling and delay during registration and re-registration of multi-SIM UEs, and improves the operation efficiency and reliability of multi-SIM UEs.
Smart Images
Figure CN119997193A_ABST
Abstract
Description
[0001] This application is a divisional application of an application with a filing date of April 24, 2020, application number 202080032343.X, and invention name “Core network node, UE, access network node and control method”. Technical Field
[0002] The present invention relates to communication systems. In particular, but not exclusively, the present invention relates to wireless communication systems and apparatus thereof operating in accordance with 3rd Generation Partnership Project (3GPP) standards or equivalents or derivatives thereof. In particular, but not exclusively, the present invention relates to registration of multi-SIM user equipment (UE) in so-called "5G" (or "next generation") systems. Background Art
[0003] background
[0004] The 3GPP SA2 working group has approved the study of a system enabler for multiple USIM devices (FS_MUSIM). Many commercially deployed devices support more than one (usually two) USIM cards. Multiple USIM devices typically address the following two use cases:
[0005] 1) User has both a personal subscription and a corporate subscription and wants to use both from the same device. This use case has become popular in BYOD initiatives in the corporate world.
[0006] 2) The user has multiple personal subscriptions and chooses which one to use based on the selected services (e.g., using one personal subscription and a "Family Circle" plan).
[0007] In either of these two use cases, the USIM can be from the same MNO or a different MNO.
[0008] Support for multiple USIMs is currently handled in an implementation specific manner without any support from the 3GPP specifications, resulting in various implementations and UE behaviors (eg, dual SIM single standby, dual SIM dual standby, dual SIM dual active, etc.).
[0009] As the complexity of 5G-enabled UEs increases and the demand for multi-USIM devices grows in the market, it becomes imperative for 3GPP to consider system enhancements that will allow for more cost-effective implementation of such devices.
[0010] 3GPP SA2 agreed studies in TR 23.761 related to system enabler for multiple USIM devices address the following objectives:
[0011] - Mechanism for delivering pages to USIM A during active communication of the UE with USIM B.
[0012] - A mechanism to allow suspension (or release) and resumption of an ongoing connection in the 3GPP system associated with USIM A so that the UE can temporarily leave to the 3GPP system associated with USIM B and then return to the 3GPP system in a network controlled manner. This study should determine how the network handles the occurrence of MT data or MT control plane activities when the connection is suspended.
[0013] -Mechanism to avoid paging conflicts between USIM A and USIM B for the UE.
[0014] -Handling of emergency calls and sessions.
[0015] - Handling of service priorities, i.e. this study should determine whether the UE behavior upon receiving a paging message is driven by the USIM configuration, by user preference, or by both.
[0016] The study should be limited to single Rx / single Tx and dual Rx / single Tx UE implementations.
[0017] The system enabler for multiple USIM devices is intended to be applicable to the case where multiple USIMs are owned by the same MNO or different MNOs. Summary of the invention
[0018] Problem that the invention aims to solve
[0019] Problem Description
[0020] The multi-SIM study in 3GPP is limited to single Rx / single Tx and dual Rx / single Tx UE implementations. However, the focus of the study is on the enablers of multi-USIM implementations, which rely on common radio and baseband components shared between multiple USIMs.
[0021] A problem with such multi-SIM UEs is how they register, re-register and de-register with the network.
[0022] There are two alternatives:
[0023] 1) Multi-SIM UEs register and / or deregister for each SIM separately. This alternative has the least impact on the network, however, it will result in increased signaling, especially when the number of SIMs to be registered is high. The registration process will also take a longer time (i.e., introduce latency). Considering that UEs re-register each time they change registration areas, and they also re-register periodically due to the expiration of periodic registration timers, the increase in signaling and latency may not be acceptable for the normal operation of multi-SIM UEs.
[0024] 2) Multi-SIM UE registers and / or deregisters for more than 1 SIM simultaneously. This alternative can significantly improve the registration process in terms of signaling and latency. This alternative can be particularly advantageous for use cases where all SIMs are from the same PLMN and can be supported by the same AMF (which is expected to be the most common deployment according to 3GPP multi-SIM study). Such simultaneous registration for all SIMs requires assistance from the network involving standardization changes, however, such standardization improvements (i.e. enablers) are actually the target of a multi-SIM study work item in the 3GPP SA2 working group.
[0025] This document proposes combined registration for Multi-SIM UEs. A Multi-SIM UE registers for more than 1 SIM or all SIMs simultaneously. This enables a significant reduction in signaling and delays during registration and re-registration of a Multi-SIM UE.
[0026] The use case discussed in this document is for 2 SIMs. However, the following embodiments are equally applicable to a larger number of SIMs. The proposal uses SIM symbology which is equally applicable to (U)SIM symbology or UICC symbology.
[0027] Solutions for solving problems
[0028] According to aspects of the present invention, a core network node for mobility management includes: a component for receiving a registration request message including a user identity from a user equipment (UE) configured to have multiple subscriber identity modules (SIMs), each of which corresponds to one of the multiple SIMs; and a component for performing a registration process for at least one of the user identities.
[0029] According to another aspect of the present invention, a core network node for mobility management comprises: a component for receiving a deregistration request message including a user identity from a user equipment (UE) configured to have multiple subscriber identity modules (i.e., multiple SIMs) or a user data management entity (i.e., UDM entity), each of the user identities corresponding to one of the multiple SIMs; and a component for performing a deregistration procedure for at least one of the user identities.
[0030] According to another aspect of the present invention, a user equipment, i.e., UE, comprises: a component for maintaining multiple subscriber identity modules, i.e., multiple SIMs; a component for sending a registration request message including multiple user identities to a core network node for mobility management, each of the multiple user identities corresponding to one of the multiple SIMs; a component for receiving a registration acceptance message including multiple temporary user identities, each of the multiple temporary user identities corresponding to one of the user identities accepted by the core network node in a registration process; and a component for performing a registration process for each of the multiple temporary user identities included in the registration acceptance message.
[0031] According to another aspect of the present invention, an access network node includes: a component for receiving a configuration update message including information indicating a capability of supporting at least one of a multiple subscriber identity module user equipment, i.e., a multiple SIM UE, and supporting at least one of multiple SIM combination registration and multiple SIM combination deregistration from a core network node; and a component for sending information indicating at least one of support for multiple SIM UE and supporting at least one of multiple SIM combination registration and multiple SIM combination deregistration via system information broadcast so that the UE can send a request related to at least one of the multiple SIM UEs and at least one of the multiple SIM combination registration and multiple SIM combination deregistration.
[0032] According to another aspect of the present invention, a control method for a core network node for mobility management includes: receiving a registration request message including a user identity from a user equipment (UE) configured to have multiple subscriber identity modules (i.e., multiple SIMs), each of the user identities corresponding to one of the multiple SIMs; and performing a registration process for at least one of the user identities.
[0033] According to another aspect of the present invention, a control method for a core network node for mobility management includes: receiving a deregistration request message including a user identity from a user equipment (UE) configured to have multiple subscriber identity modules (i.e., multiple SIMs) or a user data management entity (i.e., UDM entity), each of the user identities corresponding to one of the multiple SIMs; and performing a deregistration process for at least one of the user identities.
[0034] According to another aspect of the present invention, a control method of a user equipment, i.e., a UE, includes: maintaining multiple subscriber identity modules, i.e., multiple SIMs; sending a registration request message including multiple user identities to a core network node for mobility management, each of the multiple user identities corresponding to one of the multiple SIMs; receiving a registration acceptance message including multiple temporary user identities, each of the multiple temporary user identities corresponding to one of the user identities accepted by the core network node in a registration process; and performing a registration process for each of the multiple temporary user identities included in the registration acceptance message.
[0035] According to another aspect of the present invention, a control method of an access network node includes: receiving a configuration update message including information indicating a capability of supporting at least one of a multiple subscriber identity module user equipment, i.e., a multiple SIM UE, and supporting at least one of multiple SIM combination registration and multiple SIM combination deregistration from a core network node; and sending information indicating at least one of support for multiple SIM UE and supporting at least one of multiple SIM combination registration and multiple SIM combination deregistration via system information broadcast, so that the UE can send a request related to at least one of the multiple SIM UEs and at least one of the multiple SIM combination registration and multiple SIM combination deregistration.
[0036] Effects of the Invention
[0037] In certain aspects, a core network node, a user equipment, an access network node, a control method of a core network node, a control method of a user equipment, and a control method of an access network node may provide techniques for solving the problems described above. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] Figure 1 The following schematically illustrates the typical process of combined registration of a multi-SIM UE with the same PLMN and AMF.
[0039] Figure 2 The following schematically illustrates a typical process of combined registration of multi-SIM UEs with the same PLMN but different AMFs.
[0040] Figure 3 The typical process of combined registration of multi-SIM UE to the same PLMN but different RATs is schematically illustrated.
[0041] Figure 4 The typical process of combined deregistration of a multi-SIM UE from the same PLMN and AMF is schematically illustrated.
[0042] Figure 5The typical process of combined deregistration of a multi-SIM UE from the same PLMN and AMF is schematically illustrated.
[0043] Figure 6 The typical process of multi-SIM support indication and / or multi-SIM combined registration / deregistration support indication in SI broadcast is schematically illustrated.
[0044] Figure 7 A mobile telecommunication system 1 is schematically illustrated.
[0045] Figure 8 is a block diagram illustrating the main components of a UE.
[0046] Fig. 9 is a block diagram illustrating the main components of a typical (R)AN node.
[0047] Fig.10 is a block diagram illustrating the main components of a generic core network node. DETAILED DESCRIPTION
[0048] Detailed Description
[0049] Embodiment 1 - Combined registration of multiple SIM UE 3 to the same PLMN and the same AMF 710
[0050] Use case - UE 3 with SIM_A and SIM_B from the same PLMN registers with the same AMF 710 via combined multiple SIM (Multi-SIM) registration, i.e. registering SIM_A and SIM_B at the same time. A new registration type = "Multi-SIM" is used so that the AMF 710 is aware that the UE 3 is requesting a combined registration for multiple SIMs, and the AMF 710 obtains the details of both SIM_A and SIM_B from the UDM 720, and the AMF 710 maintains the context of both SIM_A and SIM_B.
[0051] Figure 1 The typical process of a multi-SIM UE 3 performing combined registration with the same PLMN and AMF 710 is schematically illustrated.
[0052] Figure 1 The combined registration of multi-SIM UE 3 to the same PLMN and the same AMF 710 proposed in includes the following steps:
[0053] 1). Registration Request (Registration Type = "Multi-SIM", UE_Id for SIM_A, UE_Id for SIM_B) - Multi-SIM UE 3 requests a combined registration for SIM_A and SIM_B. UE 3 includes the UE Identity (UE_Id) for SIM_A and SIM_B in the Registration Request message, which may be SUPI, SUCI, 5G-GUTI, 5G-TMSI, PEI or any other symbol to identify UE 3 and / or the subscription identity of the UE. UE 3 also includes a new parameter "Multi-SIM" or any other parameter symbol in the Registration Request message to indicate to the AMF 710 the intention or request from UE 3 to register multiple SIMs (e.g., SIM_A and SIM_B) simultaneously. The registration request message has two kinds of parameters, some of which are UE Id related, such as security parameters, requested NSSAI, [mapping of requested NSSAI], default configuration NSSAI indication, PDU session status, list of PDU sessions to be activated, subsequent request, MICO mode preference, [requested active time], requested DRX parameters, [extended idle mode DRX parameters], etc. Other parameters are non-UE Id related, such as UE radio capability update, UE MM core network capability, etc.
[0054] In case AMF 710 cannot identify Registration Type = "Multi-SIM", AMF 710 sends a Registration Reject message with an existing cause value to UE 3. For example, "Invalid mandatory information", "Information element does not exist or is not implemented". This may happen if AMF 710 is a Rel15 AMF. In this case, UE 3 sends separate Registration Request messages, one for SIM_A and another for SIM_B.
[0055] 2). Authentication / Security - With both SIM_A and SIM_B connected to the same AMF 710 via a single transceiver and a single receiver, the AMF 710 may run common authentication and security procedures for SIM_A and SIM_B so that the two SIMs may share the same password and encryption keys. However, the AMF 710 may verify the user identity via separate procedures for SIM_A and SIM_B. Alternatively, the AMF 710 may decide from a set of passwords and encryption keys one password and encryption key to use and associated with both SIMs (i.e., SIM_A and SIM_B). Although Figure 1 One UDM / UDR 720 is shown, but the AMF 710 may interwork with multiple UDM / UDR 720 where each SIM is associated with a different UDM / UDR 720 .
[0056] 3). If the AMF 710 has changed since the last registration process (e.g., the AMF 710 does not hold a valid UE context), the AMF 710 interacts with the UDM / UDR 720 to register UE 3 and retrieve the UE subscription and access and mobility restriction details for both SIM_A and SIM_B. If the AMF 710 holds a valid UE context, the AMF 710 may verify the UE subscription details with the UDM / UDR 720.
[0057] AMF 710 may contact the old AMF to retrieve the UE context. In this case, the Namf_Communication_UEContextTransfer (Complete Registration Request) service is used. Since the Namf_Communication_UEContextTransfer message contains the completed Registration Request message, the old AMF may fill multiple UE contexts into the Namf_Communication_UEContextTransfer response message for all SIMs set on the Registration Request message.
[0058] 4). Nudm_SDM_Get / Response(UE_Id for SIM_A, UE_Id for SIM_B) - Since the registration type is multi-SIM registration, the AMF 710 requests the subscription details of both SIM_A and SIM_B. The AMF 710 may request the subscription and access and mobility restriction details of SIM_A and SIM_B from the UDM / UDR 720 via one procedure or via separate procedures for each subscription (e.g., for SIM_A and SIM_B).
[0059] 5). AMF 710 creates or updates UE context for both SIM_A and SIM_B. AMF 710 may correlate SIM_A and SIM_B. This information (i.e., correlation) may be used by AMF 710 for further processing (e.g., paging SIM_A using SIM_B's temporary ID).
[0060] If AMF 710 finds that some SIMs can be accepted by AMF 710, but some SIMs cannot be accepted by AMF 710 (for example, AMF 710 cannot process a specific request S-NSSAI from SIM_B, but can process all request S-NSSAI from SIM_A), AMF 710 has several options to take.
[0061] 1) Registration Reject Message with New Reject Cause Code: AMF 710 sends a Registration Reject message with a new cause value "Separate Registration Required" to UE 3. Once UE 3 receives the Registration Reject message, UE 3 sends separate Registration Request messages, one for SIM_A and another for SIM_B.
[0062] 2) Partial Acceptance. In this case, the AMF 710 sends a Registration Accept message with an explicit indication to the UE 3 indicating which SIMs are accepted by the registration process. The UE 3 then sends another Registration Request message to the network regarding the SIMs that have not been accepted by the network.
[0063] 6a). Registration Accept (Temporary UE_Id for SIM_A, Temporary UE_Id for SIM_B) – The AMF 710 sends a Registration Accept message to the UE 3 indicating that the registration request has been accepted. The AMF 710 confirms the registration of the UE 3 for each SIM (e.g., SIM_A and SIM_B) by allocating a new temporary ID (e.g., 5G-GUTI or 5G-TMSI) for each SIM (e.g., SIM_A and SIM_B). If the 5G-GUTI is not included in the Registration Accept, the UE 3 uses the 5G-GUTI allocated for the existing registration for the new registration as well.
[0064] In the case where some registration parameters of SIM_A and SIM_B are different, AMF 710 can provide different registration parameters of SIM_A and SIM_B in the same registration accept message (e.g., allowing S-NSSAI, DRX, periodic update timer, access and mobility restrictions, etc.).
[0065] In the case where SIM_A and SIM_B have different DRX values or / and periodic update timer values, AMF 710 may set a single value for DRX, periodic update timer. For example, if AMF 710 can take into account multiple SIMs for MT call processing (i.e., SIM_B can be paged by the temporary ID of SIM_A), AMF 710 may set the most frequent DRX value to all SIMs. AMF 710 may then set both SIM_A and SIM_B to RM-REGISTERED state.
[0066] At this time, the N2 message carrying the registration acceptance message may also have UE-related parameters. Some N2 parameters of SIM_A and SIM_B may be different, and AMF 710 may provide different parameters of SIM_A and SIM_B in the same N2 message (e.g., 5G-GUTI or 5G-TMSI and allowed S-NSSAI, etc.).
[0067] 6b). Alternatively, if the registration parameters of SIM_A and SIM_B are different (e.g., AMF 710 assigns different allowed network slices (S-NSSAI) for SIM_A and SIM_B, assigns different DRX cycles, different periodic update timers, or different access and mobility restrictions for SIM_A and SIM_B), then AMF 710 may confirm the registration of SIM_A and SIM_B with separate registration accept messages (e.g., a registration accept message for SIM_A and another registration accept message for SIM_B). In this case, AMF 710 may indicate in the first registration accept message (one or more) parameters (e.g., "registration pending") or any other parameter symbol to indicate that the registration has not been completed and another registration accept message is expected.
[0068] 7). UE 3 registers both SIM_A and SIM_B from the same PLMN to one AMF 710 via combined multi-SIM registration, and UE 3 maintains registration for both SIM_A and SIM_B. In the event that AMF 710 confirms the registration for SIM_A and SIM_B in separate registration accept messages (i.e., UE 3 receives registration confirmation and a "registration pending" indication for SIM_A), UE 3 starts a timer (e.g., a timer called "registration pending" or any other timer symbol whose purpose is to delay UE 3 entering idle mode while multi-SIM registration is still pending) to wait for SIM_B registration confirmation before entering idle mode.
[0069] This use case may trigger the registration process on both 3GPP access and non-3GPP access.
[0070] In the above description, the registration request in step 1) includes a "multi-SIM" parameter. However, this parameter may be optional. If the "multi-SIM" parameter or its equivalent is not included in the registration request message, the AMF 710 determines whether the registration request is for a single SIM registration or a multi-SIM registration based on the number of UE_Ids for different SIMs. If the registration request message includes a UE_Id for SIM_A and a UE_Id for SIM_B, the AMF 710 recognizes that this is a case of multi-SIM registration and proceeds to step 2) and further steps.
[0071] The UE 3 may use the new parameter "Multi-SIM" to indicate different use cases. For example, in case the "Multi-SIM" parameter is "0" or "False", it indicates any use case with a "Single SIM" UE, and in case the "Multi-SIM" parameter is "1" or "True", it indicates any use case with a "Multi-SIM" UE. Another alternative use of the "Multi-SIM" parameter is to indicate the number of SIMs in the UE 3.
[0072] The above description shows an example of a use case of a UE 3 having two SIMs. The concept may also be applicable to the case of a UE 3 having three or more SIMs.
[0073] Embodiment 2 - Combined registration of multiple SIM UE 3 to the same PLMN but different AMF 710
[0074] Use case - UE 3 with SIM_A and SIM_B from the same PLMN registers with different AMFs 710 via combined multi-SIM registration. This may be applicable in cases where SIM_A and SIM_B need to be served by different AMFs 710 (e.g. SIM_A and SIM_B subscribe to different mutually exclusive network slices). In this use case, UE 3 registers SIM_A with AMF_1 710-1 and SIM_B with AMF_2 710-2. The registrations with AMF_1 710-1 and AMF_2 710-2 may be confirmed with separate Registration Accept messages.
[0075] Figure 2 The typical process of combined registration of a multi-SIM UE 3 to the same PLMN but different AMFs 710-1 and 710-2 is schematically illustrated.
[0076] Figure 2 The combined registration of multi-SIM UE 3 to the same PLMN but different AMFs 710-1 and 710-2 proposed in includes the following steps:
[0077] 1). Registration Request (Registration Type = "Multi-SIM", UE_Id for SIM_A, UE_Id for SIM_B) - Multi-SIM UE 3 requests a combined registration for SIM_A and SIM_B. UE 3 includes the UE Identity (UE_Id) for SIM_A and SIM_B in the Registration Request message, which may be SUPI, SUCI, 5G-GUTI, 5G-TMSI, PEI or any other symbol to identify UE 3 and / or the subscription identity of the UE. UE 3 also includes a new parameter "Multi-SIM" or any other parameter symbol in the Registration Request message to indicate to the AMF 710 the intention or request from UE 3 to register multiple SIMs (e.g., SIM_A and SIM_B) simultaneously.
[0078] 2). After querying UDM / UDR 720 and / or NRF, AMF_1 710-1 finds that it can serve UE 3 only for SIM_A, while AMF_2 710-2 can serve UE 3 for SIM_B. The reason for this result may be that SIM_A and SIM_B subscribe to different network slices (e.g., S-NSSAI), that is, SIM_A and SIM_B cannot be served by the same AMF 710.
[0079] 3). UE 3 registers SIM_A with AMF_1 710-1.
[0080] 4). Registration Accept (Temporary UE_Id for SIM_A, Registration Pending) - AMF_1 710-1 confirms the registration of UE 3 for SIM_A. Since the registration of UE 3 for SIM_B is still pending, AMF_1 710-1 can indicate this to UE 3 by adding a "Registration Pending" parameter in the Registration Accept message or any other parameter symbol to indicate that the registration is not yet complete and another Registration Accept message is expected. In the case that UE 3 receives the registration confirmation of SIM_A and the "Registration Pending" indication, UE 3 starts a timer (e.g., a timer called "Registration Pending" or any other timer symbol whose purpose is to delay UE 3 entering idle mode while multi-SIM registration is still pending) to wait for SIM_B registration confirmation before entering idle mode.
[0081] 5). Reroute (Registration Request (Registration Type = "Multi-SIM", UE_Id for SIM_B)) - AMF_1 710-1 reroutes the registration request from US 3 for SIM_B to AMF_2 710-2 via a RAN node (e.g., gNB 5).
[0082] 6). Initial NAS message (Registration Request (Registration Type = "Multi-SIM", UE_Id for SIM_B)) - gNB 5 forwards the Registration Request from UE 3 for SIM_B to AMF_2 710-2.
[0083] 7).UE 3 registers SIM_B with AMF_2 710-2.
[0084] 8). Registration Accept (Temporary UE_Id for SIM_B) - AMF_2 710-2 confirms the registration of UE 3 for SIM_B.
[0085] 9). UE 3 registers SIM_A with AMF_1 710-1 and SIM_B with AMF_2 710-2.
[0086] UE 3 may send registration confirmation messages to both AMF_1 710-1 and AMF_2 710-2, or send one registration confirmation message to AMF_1 710-1 and another registration confirmation message to AMF_2 710-2.
[0087] As an alternative to Example 2, the following steps may be taken.
[0088] 1). Registration Request (Registration Type = "Multi-SIM", UE_Id for SIM_A, UE_Id for SIM_B) - Multi-SIM UE 3 requests a combined registration for SIM_A and SIM_B. UE 3 includes the UE Identity (UE_Id) for SIM_A and SIM_B in the Registration Request message, which may be SUPI, SUCI, 5G-GUTI, 5G-TMSI, PEI or any other symbol to identify UE 3 and / or the subscription identity of the UE. UE 3 also includes a new parameter "Multi-SIM" or any other parameter symbol in the Registration Request message to indicate to the AMF 710 the intention or request from UE 3 to register multiple SIMs (e.g., SIM_A and SIM_B) simultaneously.
[0089] 2). After querying UDM / UDR 720 and / or NRF, AMF_1 710-1 finds that it can only serve UE 3 for SIM_A, while AMF_2 710-2 can serve UE 3 for SIM_B. The reason for this result may be that SIM_A and SIM_B subscribe to different mutually exclusive network slices (e.g., S-NSSAI), that is, SIM_A and SIM_B cannot be served by the same AMF710.
[0090] 3). UE 3 registers SIM_A with AMF_1 710-1.
[0091] 4).AMF_1 710-1 does not send a registration acceptance message to UE 3.
[0092] 5). AMF_1 710-1 reroutes the entire registration request message received in step 1 together with SIM_A's registration accept message. The message may have a parameter indicating successful registration of SIM_A with AMF_1 710-1.
[0093] 6). Initial NAS message (Registration Request (Registration Type = "Multi-SIM", UE_Id for SIM_B)) - gNB 5 forwards the Registration Request from UE 3 together with the additional N2 message of SIM_A to AMF_2 710-2.
[0094] 7).UE 3 registers SIM_B with AMF_2 710-2.
[0095] 8). Registration Accept (Temporary UE_Id for SIM_A, Temporary UE_Id for SIM_B) - AMF_2 710-2 confirms the registration of UE 3 for SIM_A and SIM_B.
[0096] 9). UE 3 registers SIM_A with AMF_1 710-1 and SIM_B with AMF_2 710-2.
[0097] UE 3 may send registration confirmation messages to both AMF_1 710-1 and AMF_2 710-2, or send one registration confirmation message to AMF_1 710-1 and another registration confirmation message to AMF_2 710-2.
[0098] In the above description, the registration request message in step 1) includes a "multi-SIM" parameter. However, this parameter may be optional. If the "multi-SIM" parameter or its equivalent is not included in the registration request message, the AMF 710 determines whether the registration request is for a single SIM registration or a multi-SIM registration based on the number of UE_Ids for different SIMs. If the registration request includes a UE_Id for SIM_A and a UE_Id for SIM_B, the AMF 710 recognizes that this is a case of multi-SIM registration and proceeds to step 2) and further steps.
[0099] The UE 3 may use the new parameter "Multi-SIM" to indicate different use cases. For example, in case the "Multi-SIM" parameter is "0" or "False", it indicates any use case with a "Single SIM" UE, and in case the "Multi-SIM" parameter is "1" or "True", it indicates any use case with a "Multi-SIM" UE. Another alternative use of the "Multi-SIM" parameter is to indicate the number of SIMs in the UE 3.
[0100] The above description shows an example of a use case of a UE 3 having two SIMs. The concept may also be applicable to the case of a UE 3 having three or more SIMs.
[0101] Example 3 - Combined registration of multiple SIM UE 3 to the same PLMN but different RATs
[0102] Use case - A dual mode UE 3 (LTE & 5G) with SIM_A and SIM_B from the same PLMN registers for 5G and LTE via combined registration. UE 3 first registers SIM_A with AMF 710 on 5G. AMF 710 then triggers an Attach Request procedure to MME 730 to register SIM_B with MME 730 on LTE for UE 3. AMF 710 confirms the registration of SIM_A on 5G and the registration of SIM_B on LTE to UE 3.
[0103] Figure 3 The typical process of combined registration of a multi-SIM UE 3 to the same PLMN but different RATs is schematically illustrated.
[0104] Figure 3 The combined registration of multiple SIM UE 3 to the same PLMN but different RATs proposed in includes the following steps:
[0105] 1). Registration Request (Registration Type = "Multi-SIM", UE_5G_Id for SIM_A, UE_LTE_Id for SIM_B) - Multi-SIM UE 3 requests a combined registration of SIM_A on 5G and SIM_B on LTE. UE 3 includes the UE 5G Identity for SIM_A (which may be SUPI, SUCI, 5G-GUTI, 5G-TMSI, PEI for 5G or any other symbol used to identify UE 3 and / or the subscription identity of the UE) and the UE LTE Identity for SIM_B (which may be IMSI, S-TMSI, 4G-GUTI for LTE or any other symbol used to identify UE 3 and / or the subscription identity of the UE) in the Registration Request message. UE 3 also includes a new parameter "Multi-SIM" or any other parameter symbol in the Registration Request message to indicate to the AMF 710 the intention or request from UE 3 to register multiple SIMs (e.g., SIM_A and SIM_B) simultaneously.
[0106] 2). According to the 5G registration procedure in TS23.502, UE 3 registers SIM_A with AMF 710.
[0107] 3). Attach (UE_LTE_Id for SIM_B) - AMF 710 triggers the Attach Request procedure for SIM_B to MME 730. AMF 710 includes the UE Identity (UE_Id) of LTE in the Attach Request message, which may be IMSI, S-TMSI or 4G-GUTI.
[0108] 4). Attach Accept (Temporary UE_LTE_Id for SIM_B) - MME 730 registers UE 3 for LTE and confirms the registration for SIM_B with an Attach Accept message returned to AMF 710. MME 730 may allocate a new LTE temporary UE_Id, e.g., S-TMSI or 4G-GUTI.
[0109] 5).AMF 710 confirms the registration for SIM_A and SIM_B.
[0110] 6). Registration Accept (Temporary UE_5G_Id for SIM_A, Temporary UE_LTE_Id for USIM_B) - The AMF 710 uses the Registration Accept message to confirm the registration of SIM_A on 5G to the AMF 710 and the registration of SIM_B on LTE to the MME 730. The UE 3 may be assigned a new temporary 5G ID (which may be a 5G-GUTI or a 5G-TMSI) and a temporary LTE ID (which may be an S-TMSI or a 4G-GUTI).
[0111] 7).UE 3 registers SIM_A with AMF 710 on 5G and SIM_B with MME 730 on LTE using a combined registration procedure.
[0112] In the above description, the registration request message in step 1) includes a "multi-SIM" parameter. However, this parameter may be optional. If the "multi-SIM" parameter or its equivalent is not included in the registration request message, the AMF 710 determines whether the registration request is for a single SIM registration or a multi-SIM registration based on the number of UE_Ids for different SIMs. If the registration request includes a UE_Id for SIM_A and a UE_Id for SIM_B, the AMF 710 recognizes that this is a multi-SIM case and proceeds to step 2) and further steps.
[0113] The UE 3 may use the new parameter "Multi-SIM" to indicate different use cases. For example, in case the "Multi-SIM" parameter is "0" or "False", it indicates any use case with a "Single SIM" UE, and in case the "Multi-SIM" parameter is "1" or "True", it indicates any use case with a "Multi-SIM" UE. Another alternative use of the "Multi-SIM" parameter is to indicate the number of SIMs in the UE 3.
[0114] The above description shows an example of a use case of a UE 3 having two SIMs. The concept may also be applicable to the case of a UE 3 having three or more SIMs.
[0115] Example 4 - Multi-SIM UE 3 deregisters from the same PLMN and AMF 710 combination
[0116] Use Case 1 (Multi-SIM UE 3 requests combined deregistration) - UE 3 with SIM_A and SIM_B from the same PLMN is registered with the same AMF 710. UE 3 requests a combined deregistration procedure (e.g. deregistration for SIM_A and SIM_B). The network deregisters both SIM_A and SIM_B within the same deregistration procedure.
[0117] Figure 4 The typical process of combined de-registration of a multi-SIM UE 3 from the same PLMN and AMF 710 is schematically illustrated - use case 1.
[0118] Figure 4 The combined deregistration of a multi-SIM UE 3 from the same PLMN and the same AMF 710 (use case 1) as proposed in FIG. 1 comprises the following steps:
[0119] 1). Cancellation Request (Cancellation Type = "Multi-SIM", UE_Id for SIM_A, UE_Id for SIM_B) - Multi-SIM UE 3 requests a combined cancellation of SIM_A and SIM_B. UE 3 includes the UE Identity (UE_Id) for SIM_A and SIM_B in the Cancellation Request, which may be SUPI, SUCI, 5G-GUTI, 5G-TMSI, PEI or any other symbol to identify UE 3 and / or the subscription identity of the UE. UE 3 also includes a new parameter "Multi-SIM" or any other parameter symbol in the Cancellation Request message to indicate to the AMF 710 the intention or request from UE 3 to cancel multiple SIMs (e.g., SIM_A and SIM_B) simultaneously.
[0120] 2). If the UE 3 has (one or more) PDU sessions established for SIM_A or / and SIM_B, the SMF 750 releases all PDU sessions of the UE 3 as defined in TS23.502.
[0121] 3). If dynamic PCC is applied to the established PDU session, SMF 750 performs the SM policy association termination procedure as defined in TS23.502.
[0122] 4). Nudm_SDM_Unsubscribe(UE_Id for SIM_A, UE_Id for SIM_B).
[0123] 5) Cancellation Registration Accept (UE_Id for SIM_A, UE_Id for SIM_B) - AMF 710 sends a NAS message "Cancellation Registration Accept" to UE 3 according to the Cancellation Registration Type, i.e., if the Cancellation Registration Type is "Close", AMF 710 does not send a Cancellation Registration Accept message.
[0124] 6). Signalling Connection Release - AMF 710 sends an N2 UE Release Command to the NG-RAN with the cause set to Cancel Registration to release the N2 signalling connection.
[0125] In the event that the UE 3 initiates a de-registration procedure for one SIM, the de-registration procedure as defined in 3GPP TS 23.502 [3] then takes place, except that:
[0126] Since the AMF 710 still manages other SIMs, the cleanup process will not be started at the AMF 710.
[0127] In the above description, the registration request in step 1) includes a "multi-SIM" parameter. However, this parameter may be optional. If the "multi-SIM" parameter or its equivalent is not defined in the registration request, the AMF 710 determines whether the registration request is for a single SIM registration or a multi-SIM registration based on the number of UE_Ids for different SIMs. If the registration request includes a UE_Id for SIM_A and a UE_Id for SIM_B, the AMF 710 recognizes that this is a multi-SIM case and proceeds to step 2) and further steps.
[0128] In the above description, the deregistration request in step 1) includes a "multi-SIM" parameter. However, this parameter may be optional. If the "multi-SIM" parameter or equivalent is not defined in the deregistration request, the AMF 710 determines whether the registration request is for a single SIM or for multiple SIMs based on the number of UE_ids for different SIMs. If the deregistration request includes a UE_Id for SIM_A and a UE_Id for SIM_B, the AMF 710 recognizes that this is a multi-SIM case and processes step 2) and further steps.
[0129] The new parameter "Multi-SIM" may be used by the UE 3 to indicate different use cases. For example, in case the "Multi-SIM" parameter is "0" or "False", it indicates any use case with a "Single SIM" UE 3, and in case the "Multi-SIM" parameter is "1" or "True", it indicates any use case with a "Multi-SIM" UE 3. Another alternative use of the "Multi-SIM" parameter is to indicate the number of SIMs in the UE 3.
[0130] The above description shows an example of a use case of a UE 3 having two SIMs. The concept may also be applicable to the case of a UE 3 having three or more SIMs.
[0131] Use Case 2 (Network Requested Combined De-registration) - UE 3 with SIM_A and SIM_B from the same PLMN is registered with the same AMF 710. The network requests a combined de-registration procedure, i.e. de-registration for both SIM_A and SIM_B. The network de-registers SIM_A and SIM_B within the same network initiated de-registration procedure.
[0132] Figure 5 The typical process of combined deregistration of a multi-SIM UE 3 from the same PLMN and AMF 710 is schematically illustrated - use case 2.
[0133] Figure 5 The combined deregistration of a multi-SIM UE 3 from the same PLMN and the same AMF 710 (Use Case 2) as proposed in FIG. 1 comprises the following steps:
[0134] 0). Nudm_UECM_DeregistrationNotification (UE_Id for SIM_A, UE_Id for SIM_B) - If the UDM / UDR 720 wants to request immediate deletion of all subscriber registration contexts for a multi-SIM UE 3 and PDU sessions, the UDM / UDR 720 shall send a Nudm_UECM_DeregistrationNotification message including the UE_Id for SIM_A and SIM_B and parameter Deregistration Type = "Multi-Parameters" to the AMF 710. The UDM 720 includes the UE Identity (UE_Id) for SIM_A and SIM_B in the Deregistration Notification, which may be SUPI, SUCI, 5G-GUTI, 5G-TMSI, PEI or any other symbol to identify the UE 3 and / or the UE's subscription identity. The UDM / UDR 720 also includes a new parameter “Multi-SIM” or any other parameter symbol in the deregistration request message to indicate to the AMF 710 the intention or request from the UDM / UDR 720 to deregister multiple SIMs (e.g., SIM_A and SIM_B) simultaneously.
[0135] 1). Cancellation registration request (cancellation type = "multi-SIM", UE_Id for SIM_A, UE_Id for SIM_B).
[0136] The deregistration process initiated by AMF 710 is explicit or implicit. AMF 710 does not send a deregistration request message to UE 3 for implicit deregistration. If UE 3 is in CM-CONNECTED state, AMF 710 can explicitly deregister UE 3 by sending a deregistration request message to UE 3. AMF 710 includes UE_Id for SIM_A and UE_Id for SIM_B to indicate that deregistration is performed for both SIMs at the same time. AMF 710 can also set the deregistration type to "multi-SIM" to indicate that deregistration is performed for multiple SIMs at the same time. If the deregistration request message is sent on 3GPP access and UE 3 is in CM-IDLE state in 3GPP access, AMF 710 pages UE3.
[0137] 2). If UE 3 has (one or more) PDU sessions established for SIM_A or / and SIM_B, SMF 750 releases all PDU sessions of the UE 3 as defined in TS23.502.
[0138] 3). If dynamic PCC is applied to the established PDU session, SMF 750 performs the SM policy association termination procedure as defined in TS23.502.
[0139] 4). Nudm_SDM_Unsubscribe(UE_Id for SIM_A, UE_Id for SIM_B).
[0140] 5) Cancellation Registration Accept (UE_Id for SIM_A, UE_Id for SIM_B) - AMF 710 sends a NAS message "Cancellation Registration Accept" to UE 3 according to the Cancellation Registration Type, i.e., if the Cancellation Registration Type is "Close", AMF 710 does not send a Cancellation Registration Accept message.
[0141] 6) Signalling Connection Release - AMF 710 sends an N2 UE Release Command to the NG-RAN with the cause set to Deregistration to release the N2 signalling connection.
[0142] In the event that the UE 3 initiates a de-registration procedure for one SIM, the de-registration procedure occurs as defined in 3GPP TS 23.502 [3], except that:
[0143] Since the AMF 710 still manages other SIMs, the cleanup process will not be started at the AMF 710.
[0144] The UE 3 may use the new parameter "Multi-SIM" to indicate different use cases. For example, in case the "Multi-SIM" parameter is "0" or "False", it indicates any use case with a "Single SIM" UE, and in case the "Multi-SIM" parameter is "1" or "True", it indicates any use case with a "Multi-SIM" UE. Another alternative use of the "Multi-SIM" parameter is to indicate the number of SIMs in the UE 3.
[0145] The above description shows an example of a use case of a UE 3 having two SIMs. The concept may also be applicable to the case of a UE 3 having three or more SIMs.
[0146] In the above description, the Nudm_UECM_Deregistration Notification in step 0) and the deregistration request in step 1) include a "multi-SIM" parameter. However, this parameter may be optional. If the "multi-SIM" parameter or its equivalent is not defined in the message, the AMF 710 or the UE 3 determines whether the registration request is for a single SIM or for multiple SIMs based on the number of UE_Ids for different SIMs.
[0147] Embodiment 5 - Multi-SIM combination registration / cancellation support indication in SI broadcast
[0148] Use Case - For a multi-SIM UE 3 with the capability of combined multi-SIM registration / de-registration (e.g., registering / de-registering SIM_A and SIM_B at a time), it is required that the UE 3 be aware of whether the network supports the multi-SIM feature and / or whether the combined multi-SIM registration / de-registration feature is supported. Network support for multi-SIM UEs and / or combined multi-SIM registration / de-registration may be indicated via a "Multi-SIM Support Indication" or / and a "Multi-SIM Registration / De-registration Support" indication in a System Information (SI) broadcast.
[0149] Figure 6 The typical process of multi-SIM support indication and / or multi-SIM combined registration / deregistration support indication in SI broadcast is schematically illustrated.
[0150] Figure 6 The support for multi-SIM UE and / or support for multi-SIM combined registration / deregistration through network indication in SI broadcast proposed in hereinafter includes the following steps:
[0151] 1).AMF configuration update message (multi-SIM support / multi-SIM registration / cancellation support) - If the network supports multi-SIM UE or / and multi-SIM UE combined registration / cancellation, the AMF 710 uses the AMF configuration update message or any other message on the AMF / gNB interface to indicate to the RAN node the network capability of supporting multi-SIM UE or / and supporting multi-SIM UE combined registration / cancellation.
[0152] 2). System Information Broadcast (Multi-SIM Support / Multi-SIM Registration / De-registration Support) - If the RAN node (e.g., gNB 5) is configured for multi-SIM UE support or / and supports multi-SIM UE combined registration / de-registration feature, the RAN node broadcasts network support for multi-SIM UE or / and network support for multi-SIM UE combined registration / de-registration feature in one of the system information messages.
[0153] 3). If support for multi-SIM UEs or / and support for multi-SIM UE registration / deregistration is broadcast in one of the system information messages and UE 3 has subscriptions for multiple SIMs and / or UE 3 is capable of multi-SIM combined registration / deregistration, UE 3 may attempt registration / deregistration for multiple SIMs and / or multi-SIM combined registration / deregistration in the network.
[0154] Summarize
[0155] Advantageously, the above aspects include but are not limited to one or more of the following functions:
[0156] 1) Multi-SIM UE 3 registers with a combined multi-SIM of the same AMF 710 and PLMN.
[0157] 2) Multi-SIM UE 3 de-registers from the combined multi-SIM of the same AMF 710 and PLMN.
[0158] 3) Combined multi-SIM registration of multi-SIM UE 3 from the same PLMN to different AMFs 710-1 / 710-2.
[0159] 4) Multi-SIM UE 3 combines multi-SIM registrations from the same PLMN to different RATs.
[0160] 5) A registration pending indication when confirming combined multi-SIM registration individually for each SIM.
[0161] 6) Multi-SIM support indication and / or multi-SIM combined registration / deregistration support indication broadcast by the network via system information.
[0162] 7) Combined multi-SIM deregistration support through network broadcast via system information.
[0163] To provide these functions, the above aspects describe a typical method including (at least some of) the following steps:
[0164] Embodiment 1 - Combined registration of multiple SIM UE 3 to the same PLMN and the same AMF 710
[0165] 1) UE 3 triggers the combined registration of multiple SIMs to the same PLMN at the same time.
[0166] 2) Confirm, simultaneously or individually for each SIM, that the UE registers multiple SIMs with the same AMF 710 and the same PLMN.
[0167] Embodiment 2 - Combined registration of multi-SIM UE 3 to the same PLMN and different AMFs
[0168] 1) UE 3 triggers the combined registration of multiple SIMs to different AMFs 710 and the same PLMN at the same time.
[0169] 2) Confirming that the UE 3 is registered with multiple SIMs simultaneously or individually for each SIM.
[0170] Embodiment 3 - Multi-SIM UE 3 combined registration to the same PLMN and different RATs
[0171] 1) UE 3 triggers combined registration of multiple SIMs from different RATs and the same PLMN.
[0172] 2) Confirm that UE 3 simultaneously registers multiple SIMs for 5G and LTE.
[0173] Example 4 - Multi-SIM UE 3 deregisters from the same PLMN and AMF 710 combination
[0174] 1) UE 3 triggers a combined deregistration of multiple SIMs from the same PLMN.
[0175] 2) UE 3 cancels registration of multiple SIMs simultaneously.
[0176] Embodiment 5 - Multi-SIM combination registration / cancellation support indication in SI broadcast
[0177] 1) The RAN node broadcasts a multi-SIM UE 3 support indication and / or a multi-SIM UE 3 combined registration / de-registration support indication in an SI broadcast message.
[0178] benefit
[0179] The present invention proposes a combined registration for multi-SIM UEs, which enables reduced signaling and reduced delays in the registration and re-registration procedures.
[0180] System Overview
[0181] Figure 7 A mobile (cellular or wireless) telecommunication system 1 is schematically illustrated to which the above embodiments are applicable.
[0182] In this network, users of mobile devices 3 (UE) can communicate with each other and other users via corresponding base stations 5 and core network 7 using appropriate 3GPP radio access technologies (RATs) (e.g., E-UTRA and / or 5G RAT). It will be appreciated that a plurality of base stations 5 form a (radio) access network or (R)AN. Those skilled in the art will appreciate that, although not shown for purposes of illustration, Figure 7 One mobile device 3 and one base station 5 are shown in the figure, but the system will generally include other base stations and mobile devices (UE) when implemented.
[0183] Each base station 5 controls one or more associated cells (directly or via other nodes such as home base stations, repeaters, remote radio heads, distributed units, and / or equivalents). Base stations 5 that support E-UTRA / 4G protocols may be referred to as "eNBs", and base stations 5 that support next generation / 5G protocols may be referred to as "gNBs". It should be understood that some base stations 5 may be configured to support both 4G and 5G and / or any other 3GPP or non-3GPP communication protocols.
[0184] The mobile device 3 and its serving base station 5 are connected via a suitable air interface, such as a so-called "Uu" interface, etc. Neighboring base stations 5 are connected to each other via suitable base station-to-base station interfaces, such as so-called "X2" interfaces and / or "Xn" interfaces, etc. The base stations 5 are also connected to core network nodes via suitable interfaces, such as so-called "S1", "N1", "N2" and / or "N3" interfaces, etc.
[0185] The core network 7 typically includes logical nodes (or "functions") for supporting communications in the telecommunications system 1. Typically, for example, the core network 7 of a "next generation" / 5G system will include a control plane function (CPF) and a user plane function (UPF), etc. It should be understood that the core network 7 may also include: one or more access and mobility management functions (AMF) 710; one or more unified data management (UDM) / unified data repository (UDR) nodes 720; session management function (SMF) / UPF 750, policy control function (PCF) 740, and mobile management entity (MME) 730, etc.
[0186] A connection to an external IP network 20 such as the Internet is also provided from the core network 7 .
[0187] The components of the system 1 are configured to carry out the exemplary embodiments described above.
[0188] User Equipment (UE)
[0189] Figure 8 is an example Figure 7 3. As shown in the figure, the UE includes a transceiver circuit 31 operable to send signals to and receive signals from a connected node (or nodes) via one or more antennas 33. Although it is not necessary to Figure 8 39, but of course the UE will have all the common functionality of a conventional mobile device (such as a user interface 35, etc.), and the functionality may be provided by any one or any combination of hardware, software and firmware as appropriate. The controller 37 controls the operation of the UE according to the software stored in the memory 39. For example, the software may be pre-installed in the memory 39, and / or may be downloaded via the telecommunications network 1 or from a removable data storage device (RMD). The software includes an operating system 41 and a communication control module 43, etc. The communication control module 43 is responsible for processing (generating / sending / receiving) signaling messages and uplink / downlink data packets between the UE 3 and other nodes including the (R)AN node 5, the core network node and application functions. Such signaling includes appropriately formatted requests and responses related to the registration / cancellation of multi-SIM UEs.
[0190] The term "UE" generally refers to a mobile phone, which includes at least the following components:
[0191] - Mobile Equipment (ME): ME is a "mobile phone" as a hardware device. Fig. 9 The ME includes at least one processor (controller), a memory unit, an antenna, a transceiver unit, a user interface (such as a screen, buttons, a cable socket, etc.), a battery unit, etc.
[0192] -Subscriber Identity Module (SIM) or Universal Subscriber Identity Module (USIM): SIM or USIM is an application running in the UICC card. The UICC card is a small integrated circuit that includes an associated processor (controller), a communication module, a memory unit, and an interface unit to communicate with the ME part of the UE3. The UICC is also called a "smart card". The processor controls the operation of the USIM according to the software stored in the memory. The USIM software includes an operating system (OS) and a communication control module, etc.
[0193] The term "SIM" generally refers to the application in the UICC card used in the 2G GSM mobile system. The term "USIM" generally refers to the application in the UICC card used in 3G (UMTS), 4G (LTE) and 5G systems. In addition, "eSIM" is a SIM function that is embedded in the ME30 itself, rather than provided using a physical (removable) UICC card. In most technical contexts, these terms are interchangeable and the term "SIM" is more general. From the perspective of the present invention, the terms "SIM", "USIM" and "eSIM" are used interchangeably. SIM and USIM applications and eSIM contain credentials, such as long-term identifiers (IMSI in 3GPP) and long-term keys.
[0194] In this disclosure, "ME", "mobile device" or simply "device" is used to refer to the same entity, i.e. a mobile handset generally used for any generation of technology. In addition, "SIM" or "USIM" is used in this disclosure, depending on the context. However, they generally refer to applications that reside in the UICC.
[0195] The UE 3 may be a multi-SIM device. Typically, a mobile device supporting multi-SIM is equipped with two SIM card slots, so it is also generally referred to as a "dual SIM phone". In another UE implementation, the mobile device is equipped with one SIM card slot, and the other SIM functionality is embedded in hardware ("eSIM"). The mobile device may have a separate IMEI for each SIM, or a single IMEI common to all SIMs in the mobile device. An example of having a single IMEI common to all SIMs is the case where a single UICC card contains multiple USIM applications.
[0196] Depending on the hardware implementation, a multi-SIM device / UE may be equipped with one or more transceiver circuits 31. When present, such multiple transceiver circuits 31 enable simultaneous connections using multiple SIMs.
[0197] (R)AN Node
[0198] Fig. 9 is an example Figure 71 is a block diagram of the main components of a typical (R) AN node 5 (base station) shown in FIG. As shown, the (R) AN node 5 includes a transceiver circuit 51 that is operable to send signals to and receive signals from connected (one or more) UEs 3 via one or more antennas 53, and is operable to send signals to and receive signals from other network nodes via a network interface 55 (directly or indirectly). The network interface 55 typically includes an appropriate base station-base station interface (such as X2 / Xn, etc.) and an appropriate base station-core network interface (such as S1 / N1 / N2 / N3, etc.). The controller 57 controls the operation of the (R) AN node 5 according to the software stored in the memory 59. For example, the software can be pre-installed in the memory 59, and / or can be downloaded via the telecommunications network 1 or from a removable data storage device (RMD). The software includes an operating system 61 and a communication control module 63, etc. The communication control module 63 is responsible for processing (generating / sending / receiving) signaling between the (R) AN node 5 and other nodes such as UE 3 and core network nodes / AF, etc. Such signalling includes appropriately formatted requests and responses related to registration / de-registration of multiple SIM UEs.
[0199] Core network nodes
[0200] Fig.10 is an example Figures 1 to 7 710, UDM / UDR720, SMF / UPF 750, PCF 740 and MME 730). As shown, the core network node includes a transceiver circuit 71 operable to send signals to other nodes (including UE 3 and (R) AN node 5) and receive signals from other nodes via a network interface 75. A controller 77 controls the operation of the core network node according to software stored in a memory 79. For example, the software may be pre-installed in the memory 79 and / or may be downloaded via the telecommunications network 1 or from a removable data storage device (RMD). The software includes an operating system 81 and at least a communication control module 83. The communication control module 83 is responsible for processing (generating / sending / receiving) signaling between the core network node and other nodes such as UE 3, (R) AN node 5, AF and other core network nodes. Such signaling includes appropriately formatted requests and responses related to registration / cancellation of multi-SIM UEs.
[0201] Modifications and Alternatives
[0202] Specific embodiments are described above. As will be appreciated by those skilled in the art, various modifications and substitutions may be made to the above embodiments while still benefiting from the disclosure implemented therein. Many such alternatives and modifications will now be described only by way of example.
[0203] In the above description, the UE, (R)AN node and core network node are described as having multiple discrete modules (such as communication control modules, etc.) for ease of understanding. Although these modules may be provided in this way for certain applications, for example, where an existing system has been modified to implement the present invention, in other applications, such as in a system designed from the outset with the features of the present invention in mind, these modules may be built into the entire operating system or code, and therefore these modules may not be discernible as discrete entities. These modules may be implemented in the form of software, hardware, firmware or a combination thereof.
[0204] Each controller may include any suitable form of processing circuitry, including, for example (but not limited to): one or more hardware-implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memory / buffers (program and / or data); processing registers; communication buses (e.g., control buses, data buses, and / or address buses); direct memory access (DMA) functionality; hardware or software-implemented counters; pointers and / or timers, and / or equivalents.
[0205] In the above embodiments, a plurality of software modules are described. As will be appreciated by those skilled in the art, the software modules can be provided in compiled or uncompiled form and can be provided to the UE, (R)AN node and core network node as a signal over a computer network, or provided on a recording medium. In addition, one or more dedicated hardware circuits may be used to perform the functions performed by part or all of the software. However, the use of software modules is preferred because it facilitates the updating of the UE, (R)AN node and core network node to update their functions.
[0206] The above embodiments may also be applicable to "non-mobile" or generally stationary user equipment.
[0207] Various other modifications will be apparent to those skilled in the art and will not be described in further detail herein.
[0208] abbreviation
[0209] 5GC 5G Core Network
[0210] 5GS 5G System
[0211] 5G-AN 5G Access Network
[0212] 5G-GUTI 5G Globally Unique Temporary Identity
[0213] 5G-TMSI 5G Temporary Mobile Subscriber Identity
[0214] AMF Access and Mobility Management Function
[0215] AN Access Network
[0216] AS Access Layer
[0217] BYOD Bring Your Own Device
[0218] DRX Discontinuous Reception
[0219] gNBNext Generation Node B
[0220] MME mobility management entity
[0221] NAS Non-Access Stratum
[0222] NF Network Function
[0223] NG-RAN Next Generation Radio Access Network
[0224] NR New Radio
[0225] PCC Policy and Charging Control
[0226] PCF Policy Control Function
[0227] PDU Protocol Data Unit
[0228] PEI Persistent Equipment Identifier
[0229] PLMN Public Land Mobile Network
[0230] (R)AN (Radio) Access Network
[0231] RAT Radio Access Technology
[0232] RRC Radio Resource Control
[0233] SMF session management functions
[0234] SUCI Subscription Hidden Identifier
[0235] SUPI Subscription Persistent Identifier
[0236] S-NSSAI single network slice selection auxiliary information
[0237] UDM Unified Data Management
[0238] UDR Unified Data Repository
[0239] UE User Equipment
[0240] UICC Universal Integrated Circuit Card
[0241] (U)SIM Universal Subscriber Identity Module
[0242] definition
[0243] For the purposes of this document, the terms and definitions given in 3GPP TR 21.905 [1] and below apply. A term defined in this document takes precedence over the definition of the same term in 3GPP TR 21.905 [1], if any.
[0244] Reference List
[0245] Non-patent literature
[0246] [Non-patent document 1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”. V15.0.0 (2018-03)
[0247] [Non-patent document 2] 3GPP TS23.501: “System Architecture for the 5G System; Stage 2”. V15.4.0 (2019-03)
[0248] [Non-patent document 3] 3GPP TS23.502: “Procedures for the 5G System; Stage 2” V15.4.1 (2019-03)
[0249] [Non-patent document 4] 3GPP TR 23.761 / S2-1901392: “Architectural enhancements for 5G multicast-broadcast services” (2019-01)
[0250] This application is based upon and claims the benefit of priority from European patent application 19172648.8, filed on May 3, 2019, the disclosure of which is incorporated herein in its entirety by reference.
[0251] Reference numerals list
[0252] 1Telecommunications System
[0253] 3 Mobile Device (UE)
[0254] 31 Transceiver Circuit
[0255] 33 Antenna
[0256] 35 User Interface
[0257] 37 Controller
[0258] 39 Memory
[0259] 41 Operating System
[0260] 43 Communication control module
[0261] 45(U)SIM
[0262] 5(R)AN Node (gNB)
[0263] 51 Transceiver Circuit
[0264] 53 Antenna
[0265] 55 Network Interface
[0266] 57 Controller
[0267] 59 Memory
[0268] 61 Operating System
[0269] 63 Communication control module
[0270] 7 Core Network
[0271] 71 Transceiver Circuit
[0272] 75 Network Interface
[0273] 77 Controller
[0274] 79 Memory
[0275] 81 Operating System
[0276] 83 Communication control module
[0277] 710AMF
[0278] 720UDM / UDR
[0279] 730MME
[0280] 740PCF
[0281] 750SMF / UPF
[0282] 20 External IP Network
Claims
1. A method for a node, comprising: In a registration process, receiving a first message from a user equipment (UE), the first message comprising a first parameter related to a multiple subscriber identity module (multi-SIM) of the UE, wherein the first parameter is based on the multiple SIMs of the UE; After receiving the first message, sending a second message to the UE, the second message including a second parameter related to the multiple SIMs of the UE; as well as A third message is received from the UE, the third message including a third parameter related to the multiple SIMs of the UE, wherein a value of the third parameter is different from a value of the first parameter and the third parameter is based on the single SIM of the UE.
2. The method for a node according to claim 1, wherein: The first parameter is different from a UE identity related parameter, ie, a UEID related parameter, and the third parameter is different from the UE ID related parameter.
3. The method for a node according to claim 1 or 2, wherein: The value of the first parameter is 1, and the value of the third parameter is 0.
4. The method for a node according to claim 1, wherein: The node is used for mobility management.
5. The method for a node according to claim 4, wherein: The node is an access and mobility management function node, namely an AMF node.
6. A method for a user equipment (UE), the method comprising: During the registration process, a first message is sent to a node, the first message comprising a first parameter related to a multiple subscriber identity module (multi-SIM) of the UE, wherein the first parameter is based on the multiple SIMs of the UE; After sending the first message, receiving a second message from the node, the second message comprising a second parameter related to multiple SIMs of the UE; as well as A third message is sent to the node, the third message including a third parameter related to the multiple SIMs of the UE, wherein a value of the third parameter is different from a value of the first parameter and the third parameter is based on the single SIM of the UE.
7. The method for UE according to claim 6, wherein: The first parameter is different from a UE identity related parameter, ie, a UEID related parameter, and the third parameter is different from the UE ID related parameter.
8. The method for UE according to claim 6 or 7, wherein: The value of the first parameter is 1, and the value of the third parameter is 0.
9. The method for UE according to claim 6, wherein: The node is used for mobility management.
10. The method for UE according to claim 9, wherein: The node is an access and mobility management function node, namely an AMF node.
11. A node, comprising: means for receiving a first message from a user equipment (UE) during a registration procedure, the first message comprising a first parameter related to a multiple subscriber identity module (multi-SIM) of the UE, wherein the first parameter is based on the multiple SIMs of the UE; means for sending a second message to the UE after receiving the first message, the second message comprising a second parameter related to a multi-SIM of the UE; as well as Means for receiving a third message from the UE, the third message comprising a third parameter related to the multiple SIMs of the UE, wherein a value of the third parameter is different from a value of the first parameter and the third parameter is based on the single SIM of the UE.
12. A user equipment, namely, UE, comprising: means for sending a first message to a node during a registration procedure, the first message comprising a first parameter related to a multiple subscriber identity module (multi-SIM) of the UE, wherein the first parameter is based on the multiple SIMs of the UE; means for receiving a second message from the node after sending the first message, the second message comprising second parameters related to multiple SIMs of the UE; as well as means for sending a third message to the node, the third message comprising a third parameter related to the multiple SIMs of the UE, wherein the value of the third parameter is different from the value of the first parameter and the third parameter is based on the single SIM of the UE.