Method for UDM (Unified Data Management Function), Method for AMF (Access and Mobility Management Function), UDM and AMF

Abstract

[assignment] The network does not know that the 5GMM parameters for the original USIM are deleted in the UE. [Solution] A method for a user equipment (UE) includes transmitting an indicator indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identity (SUPI) associated with the UE has changed, and receiving 5GS mobility management (5GMM) parameters associated with the UE after transmitting the indicator.

Description

[Technical Field]

[0001] The present disclosure relates to a method for a user equipment (UE), a method for an access and mobility management function (AMF), a unified data management (UDM), a UE, an AMF, and a UDM. [Background technology]

[0002] A user equipment (UE) includes a mobile equipment (ME) and a universal integrated circuit card (UICC) that includes a universal subscriber identity module (USIM) or an embedded subscriber identity module (eSIM). The ME has a permanent equipment identifier (PEI), a unique identifier permanently stored in the ME. The UICC includes a USIM application that includes various subscription data (e.g., an international mobile subscriber identity (SUPI), an international mobile subscriber identity (IMSI)), and security parameters for the user (e.g., an authentication key K). When a user subscribes to a PLMN, the user is given a UICC (commonly referred to as a SIM) that includes the SUPI / IMSI. A user within a PLMN is uniquely identified by the SUPI / IMSI stored on the UICC. A unified data management (UDM) stores various subscriber parameters (e.g., SUPI, IMSI), security parameters (e.g., the authentication key K), and other parameters related to the USIM's SUPI. The UICC is inserted into the ME by the user of the UE. Inserting the UICC is sometimes referred to as inserting a SIM or a USIM.

[0003] When a user (or UE) registers with a PLMN, the UE sends a Subscription Concealment Identifier (SUCI) to the AMF. The SUCI is generated by the UE based on the SUPI. For example, the SUCI is generated by concealing the SUPI. The AMF then initiates an authentication procedure with the AUSF, which then initiates an authentication procedure with the UDM. As part of the authentication procedure, the SUCI is transferred from the AMF to the UDM via the AUSF. The UDM hides the SUCI from the SUPI. After the authentication procedure between the UE and the PLMN is successfully completed, the UDM sends 5GS Mobility Management (5GMM) parameters (e.g., subscription parameters) to the UE via the AMF during the registration procedure. These parameters are used by the UE in various Non-Access Stratum (NAS) or Access Stratum (AS) procedures. The UE stores these parameters in non-volatile memory and uses them after the UE is powered on for a period of time. Some 5GMM parameters are stored in non-volatile memory in the UICC, while some 5GMM parameters are stored in non-volatile memory in the ME. These 5GMM parameters are required for the correct execution of various NAS or AS procedures or also utilize various services subscribed to by the subscriber. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TR 21.905:“Vocabulary for 3GPP Specifications”.V17.0.0(2020-07) [Non-patent document 2] GSM Association Official Document NG.116:“Generic Network Slice Template”V2.0(2019-10)-https: / / www.gsma.com / newsroom / wp-content / uploads / NG.116-v2.0.pdf [Non-patent document 3] 3GPP TR 22.835:“Study on Enhanced Access to and Support of Network Slices”V0.2.0(2020-11)-http: / / www.3gpp.org / ftp / Specs / archive / 22_series / 22.835 / 22835-020.zip [Non-patent document 4] 3GPP TS 23.501: “System architecture for the 5G System(5GS)”.V17.0.0(2021-03) [Non-Patent Document 5] 3GPP TS 23.502:“Procedures for the 5G System(5GS)”.V17.0.0(2021-03) [Non-patent document 6] 3GPP TS 24.501:“Non-Access-Stratum(NAS)protocol for 5G System(5GS);Stage 3”.V17.1.0(2020-12) [Non-Patent Document 7] 3GPP TS 33.501: “Security Architecture and Procedures for 5G System”.V17.0.0(2020-12) Summary of the Invention [Problem to be solved by the invention]

[0005] When a user inserts a new SIM (e.g., a new USIM) into the ME or activates a new USIM in the ME while the original USIM is associated with the ME, the UE deletes the 5GMM parameters of the original USIM stored in the non-volatile memory of the ME if the SUPI associated with the stored 5GMM parameters is different from the SUPI of the new SIM or new USIM. For example, the original USIM is inserted into the ME before the new USIM is inserted into the ME. When the original USIM is inserted, the UE (e.g., the ME) receives the 5GMM parameters of the original USIM from the UDM and stores the 5GMM parameters of the original USIM. The user may also activate the new USIM in place of the original USIM. Inserting a new USIM into the ME in place of the original USIM or activating a new USIM in place of the original USIM may also be referred to as replacing the original USIM with a new USIM. For example, the original USIM is removed from the ME, and then the new USIM is inserted into the ME.

[0006] In this scenario, the ME receives the new 5GMM parameters for the new SIM from the UDM and stores the new 5GMM parameters for the new SIM or new USIM in non-volatile memory after a successful registration procedure for the new SIM or new USIM. Subsequently, when the original USIM is reinserted into the ME or reactivated in the ME, the ME may not receive the relevant 5GMM parameters from the network (e.g., UDM) during the registration procedure because the network believes that the UE retains valid relevant 5GMM parameters for the original USIM.

[0007] For example, when the original USIM is inserted for the first time and a first registration procedure for the original USIM is performed, the network (e.g., UDM) sends the 5GMM parameters of the original USIM and stores the association of the original USIM and the PEI for the registered UE. When a new USIM is inserted in place of the original USIM and the original USIM is reinserted in place of the new USIM, a second registration procedure is performed. In this case, the network may not send the 5GMM parameters of the original USIM because it already stores the association of the original USIM and the PEI. That is, the network does not know that the 5GMM parameters for the original USIM are deleted in the UE. In other words, the network has no way of knowing that a USIM replacement has occurred. In other words, the network does not know that a USIM replacement will occur.

[0008] As a result, when a new USIM is inserted into the ME, the UE loses the 5GMM parameters of the original USIM because all 5GMM parameters of the original USIM in the non-volatile memory of the ME are deleted. In other words, the UE (e.g., ME) does not have the 5GMM parameters of the original USIM when the original USIM is reinserted. If the 5GMM parameters are not present in the ME, the UE may lose some subscribed services as long as the 5GMM parameter mismatch between the UE and the network continues. [Means for solving the problem]

[0009] In an aspect of the present disclosure, a method for a user equipment (UE) includes transmitting an indicator indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with the UE has changed, and receiving 5GS mobility management (5GMM) parameters associated with the UE after transmitting the indicator.

[0010] In an aspect of the present disclosure, a method for an Access and Mobility Management Function (AMF) includes receiving an indicator from a user equipment (UE) indicating that an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identity (SUPI) associated with the UE has changed; upon receiving the indicator from the UE, transmitting the indicator to a Unified Data Management (UDM); after transmitting the indicator, receiving 5GS Mobility Management (5GMM) parameters associated with the UE from the UDM; and transmitting the 5GMM parameters to the UE.

[0011] In an aspect of the present disclosure, a method for unified data management (UDM) includes receiving an indicator indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with user equipment (UE) has changed, and transmitting 5GS mobility management (5GMM) parameters associated with the UE after receiving the indicator.

[0012] In an aspect of the present disclosure, a method for an Access and Mobility Management Function (AMF) includes receiving a registration request message from a user equipment (UE), transmitting a permanent equipment identifier (PEI) associated with the UE and an international mobile subscriber identifier (SUPI) associated with the UE to a unified data management (UDM) after receiving the registration request message, receiving 5GS mobility management (5GMM) parameters associated with the UE from the UDM after transmitting the PEI and the SUPI, and transmitting the 5GMM parameters to the UE.

[0013] In an aspect of the present disclosure, a method for unified data management (UDM) includes receiving a permanent equipment identifier (PEI) associated with a user equipment (UE) and an international mobile subscriber identifier (SUPI) associated with the UE, and transmitting 5GS mobility management (5GMM) parameters associated with the UE after receiving the PEI and the SUPI.

[0014] In an aspect of the present disclosure, a method for an Access and Mobility Management Function (AMF) includes receiving a registration request message from a user equipment (UE); determining whether an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with the UE has changed; if determining that the association has changed, sending an indicator to a unified data management (UDM) indicating that the association has changed; after sending the indicator, receiving 5GS mobility management (5GMM) parameters associated with the UE from the UDM; and sending the 5GMM parameters to the UE.

[0015] In an aspect of the present disclosure, a method for unified data management (UDM) includes determining whether an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with user equipment (UE) has changed, and if it is determined that the association has changed, transmitting 5GS mobility management (5GMM) parameters associated with the UE.

[0016] In an aspect of the present disclosure, a user equipment (UE) includes means for transmitting an indicator indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with the UE has changed, and means for receiving 5GS mobility management (5GMM) parameters associated with the UE after transmitting the indicator.

[0017] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) includes means for receiving an indicator from a user equipment (UE) indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with the UE has changed, means for sending the indicator to a unified data management (UDM) upon receiving the indicator from the UE, means for receiving 5GS mobility management (5GMM) parameters associated with the UE from the UDM after sending the indicator, and means for sending the 5GMM parameters to the UE.

[0018] In an aspect of the present disclosure, a unified data management (UDM) includes means for receiving an indicator indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with a user equipment (UE) has changed, and means for transmitting 5GS mobility management (5GMM) parameters associated with the UE after receiving the indicator.

[0019] In an aspect of the present disclosure, an access and mobility management function (AMF) includes means for receiving a registration request message from a user equipment (UE), means for transmitting a permanent equipment identifier (PEI) associated with the UE and an international mobile subscriber identifier (SUPI) associated with the UE to a unified data management (UDM) after receiving the registration request message, means for receiving 5GS mobility management (5GMM) parameters associated with the UE from the UDM after transmitting the PEI and the SUPI, and means for transmitting the 5GMM parameters to the UE.

[0020] In an aspect of the present disclosure, a unified data management (UDM) includes means for receiving a permanent equipment identifier (PEI) associated with a user equipment (UE) and an international mobile subscriber identifier (SUPI) associated with the UE, and means for transmitting 5GS mobility management (5GMM) parameters associated with the UE after receiving the PEI and the SUPI.

[0021] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) includes means for receiving a registration request message from a user equipment (UE); means for determining whether an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with the UE has changed; means for transmitting an indicator to a unified data management (UDM) indicating that the association has changed if it is determined that the association has changed; means for receiving 5GS mobility management (5GMM) parameters associated with the UE from the UDM after transmitting the indicator; and means for transmitting the 5GMM parameters to the UE.

[0022] In an aspect of the present disclosure, a unified data management (UDM) includes means for determining whether an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with a user equipment (UE) has changed, and means for transmitting 5GS mobility management (5GMM) parameters associated with the UE if it is determined that the association has changed. [Brief explanation of the drawings]

[0023] [Figure 1] FIG. 1 illustrates a registration procedure for setting UE subscription parameters according to a first exemplary embodiment. [Figure 2] FIG. 2 illustrates a registration procedure for setting UE subscription parameters according to a second exemplary embodiment. [Figure 3] FIG. 3 illustrates a registration procedure for setting UE subscription parameters according to a third exemplary embodiment. [Figure 4] FIG. 4 shows a first variation of the registration procedure defined in FIG. [Figure 5] FIG. 5 shows a second variation of the registration procedure defined in FIG. [Figure 6] FIG. 6 is a block diagram of a UE. [Figure 7] FIG. 7 is a block diagram of an (R)AN node. [Figure 8] FIG. 8 is a block diagram of the AMF. [Figure 9] FIG. 9 is a block diagram of the UDM. [Figure 10] FIG. 10 is a block diagram of the EIR. [Figure 11] FIG. 11 shows the registration procedure. DETAILED DESCRIPTION OF THE INVENTION

[0024] <abbreviation> For the purposes of this document, the abbreviations in Non-Patent Document 1 and given below apply. Abbreviations defined in this document take precedence over the definitions of the same abbreviations in Non-Patent Document 1, if any. 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grandmaster 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AS access layer ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS Dual Active Protocol Stack DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Center GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HR Home Routing (Roaming) IAB Integrated access and backhaul IMEI / TAC IMEI Type Allocation Code IPUPS Inter PLMN Up Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Breakout (Roaming) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function MCC Mobile Country Code MCX Mission Critical Services MDBV Maximum Data Burst Volume MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MITM Man in the Middle MNC Mobile Network Code MPS Multimedia Priority Service MPTCP Multipath TCP Protocol N3IWF Non-3GPP InterWorking Function N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol NID Network identifier NPN Non-Public Network NR New Radio NRF Network Repository Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice-Specific Authentication and Authorization Function NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NW-TT Network-side TSN translator NWDAF Network Data Analytics Function PCF Policy Control Function PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience RACS Radio Capabilities Signalling optimisation (R)AN (Radio) Access Network RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RSN Redundancy Sequence Number SA NR Standalone New Radio SBA Service-Based Architecture SBI Service-Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN Name: Serving Network Name. SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI International Mobile Subscriber Identifier (Subscription Permanent Identifier) SV Software Version TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grandmaster TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UL Uplink UL CL Uplink Classifier UPF User Plane Function URLLC (Ultra Reliable Low Latency Communication) URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy VID VLAN Identifier VLAN Virtual Local Area Network W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function

[0025] <Definition> For the purposes of this document, the terms and definitions in Non-Patent Document 1 and given below apply. Where the same term appears in Non-Patent Document 1, the term defined herein takes precedence over that term's definition.

[0026] <General> Those skilled in the art will understand that elements in the figures are illustrated for simplicity and may not necessarily be drawn to scale. Further, with respect to the configuration of a device, one or more components of the device may be represented in the figures by conventional symbols, and the figures may show only certain details relevant to an understanding of the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to one of ordinary skill in the art having the benefit of the description herein.

[0027] For the purposes of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings, and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such modifications and further variations in the illustrated system, and such further applications of the principles of the present disclosure as would normally occur to one skilled in the art, are to be construed as being within the scope of the present disclosure.

[0028] The terms "comprise" or "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that includes a list of steps does not include only those steps, but may include other steps that are not expressly listed or that are inherent in such process or method.

[0029] Similarly, one or more devices or entities or subsystems or elements or structures or components preceded by "comprise...a" does not, without further constraints, preclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, appearances of the phrases "in an embodiment," "in another embodiment," and similar language may, but do not necessarily, all refer to the same embodiment.

[0030] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.

[0031] In the following specification and claims, reference will be made to a number of terms that shall be defined to have the following meanings: The singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

[0032] As used herein, information is associated with data and knowledge, as data represents meaningful information and values ​​attributed to parameters. Further knowledge indicates understanding of abstract or concrete concepts. Note that this exemplary system is simplified to facilitate explanation of the disclosed subject matter and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations can be used in addition to or instead of the system to practice the embodiments disclosed herein, and all such embodiments are considered to be within the scope of the present disclosure.

[0033] In the exemplary embodiment defined below, the 5GMM parameters may be UE subscription parameters stored in a UDM. The UDM sends the parameters to the UE during a registration procedure or a UE configuration update procedure. The UE stores these parameters and the USIM's SUPI in the ME's non-volatile memory. The UE uses the 5GMM parameters in various UE NAS or AS procedures. When the UE PEI-SUPI association is changed in the ME, the ME deletes the stored 5GMM parameters. For example, when a first USIM is inserted into the ME, the UE (e.g., the ME) stores a first association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM (this association may be referred to as a UE PEI-SUPI association or PEI-SUPI association). Also, when a second USIM is inserted into the ME instead of the first USIM, the UE (e.g., the ME) stores a second association between the PEI corresponding to the ME and the SUPI corresponding to the second USIM and deletes the first association and the 5GMM parameters of the first USIM. That is, when a second USIM is inserted in place of a first USIM, the UE PEI-SUPI association changes.

[0034] The following are examples of 5GMM parameters that may be stored in the non-volatile memory of the ME: In this disclosure, the 5GMM parameters are not limited to the 5GMM parameters listed below. a) 5G-GUTI; b) Last Visit Registration Tracking Area Identifier (TAI); c) 5GS update status; d) 5G NAS security context parameters from the complete native 5G NAS security context (see Non-Patent Document 7); e) KAUSF and KSEAF (see Non-Patent Document 7); f) Steering of Roaming (SOR) counter (see Non-Patent Document 7); and g) UE parameter update counter (see Non-Patent Document 7). h) Compatible slice configuration in the UE (see Non-Patent Document 4). i) Onboarding parameters related to non-public networks (NPNs), both standalone private networks and public network integrated NPNs, which are configured in the UE to find and camp on private networks (e.g., when the UE is turned on for the first time).

[0035] In the following exemplary embodiment, the 5GMM parameters may be sent to the UE using a UE configuration update procedure during the registration procedure (e.g., initial registration procedure) or after the registration procedure has finished.

[0036] The UE requires Closed Access Group (CAG) information (e.g., an allowed CAG list) to camp and register on a Public Network Integrated Non-Public Network (PNI-NPN). When a first USIM is inserted into the ME and the UE performs a registration procedure for the first USIM, the UDM sends the CAG information of the first USIM to the UE during the registration procedure or the UE configuration update procedure.

[0037] For example, CAG information is one of the 5GMM parameters. The UE stores the CAG information in its non-volatile memory of the ME. The UE then uses the CAG information to camp on the subscribed CAG cell and obtain related services from the PLMN. When a second USIM is inserted into the ME instead of the first USIM, the ME deletes the CAG information of the first USIM.

[0038] When the first USIM is reinserted, the UE does not have the CAG information of the first USIM.

[0039] If there is no CAG information of the first USIM, the UE cannot find the CAG cell to which the user subscribes and therefore cannot register with the PNI-NPN. In this situation, the UE cannot access the PNI-NPN even if the UE has a valid subscription.

[0040] In the following exemplary embodiments, the term USIM can also refer to an eSIM / eUICC when the eSIM / eUICC is part of a UE. When the term USIM is used for an eSIM / eUICC, the terms "USIM is inserted" or "USIM is activated" mean "the eSIM / eUICC is provisioned with a new user profile (e.g., a new SUPI and other eSIM Directory Files (DF) or Elementary Files (EF) associated with the new SUPI)."

[0041] In the following exemplary embodiment, when the USIM is removed and reinserted into the UE and the AMF has a valid context for the UE identified by the 5G-GUTI received in the registration request message, if the registration request message indicates a change in the PEI-SUPI association, or if the Kausf is deleted from the ME memory, or if all 5GMM parameters are deleted (the non-volatile memory is cleaned), the AMF initiates an authentication procedure to the UDM as described in non-patent document 7. Alternatively, if the UDM receives a Nudm_UECM_Registration message including a first indicator indicating that the SUPI-PEI association has changed or a second indicator indicating that the Kausf has been deleted, or if the 5GMM parameters have been deleted, the UDM sends a Nudm_UECM_Registration response message indicating to the AMF via the AUSF to initiate an authentication procedure to the UDM as described in non-patent document 7. If the authentication procedure and the subsequent registration procedure are successful, the UE and the AUSF start using the latest Kausf created during the authentication procedure.

[0042] <Description of the first exemplary embodiment to solve the problem (Solution 1: UE indicates change of PEI-SUPI association to the network)> The UE indicates the change in PEI-SUPI association to the network, and the network updates the UE with the current USIM subscription.

[0043] Detailed steps of the registration procedure are listed below.

[0044] 1. A first USIM is activated in an ME. For example, when the first USIM is inserted into an ME, the first USIM is activated in the ME. The ME creates an association between the PEI of the ME and the SUPI of the first USIM and stores the association.

[0045] 2. The ME checks whether it has the 5GMM parameters of the first USIM stored in the ME.

[0046] For example, the ME may check whether it is associated with a new USIM by checking whether the ME has the 5GMM parameters of the first USIM stored in the ME.

[0047] An example of a case in which the ME (or UE) does not store 5GMM parameters for a first USIM is when, for example, case i) the ME activates a second USIM and the ME does not have 5GMM parameters for the first USIM after the user reactivates / inserts the first USIM, or case ii) the first USIM is stored in ME memory and the 5GMM parameters are deleted from the ME memory because the ME is hard reset. An example of case i) is when the first USIM is reinserted after the second USIM is inserted in place of the first USIM. If the ME determines that the ME does not have 5GMM parameters for the first USIM, the UE (e.g., ME) determines that the PEI-SUPI association has changed. For example, the UE (e.g., ME) determines that the association between the PEI corresponding to the ME and the SUPI corresponding to the second USIM is changed to the association between the PEI and SUPI corresponding to the first USIM.

[0048] 3. The UE initiates a registration procedure to the network (e.g., AMF) by sending a registration request message. For example, the UE initiates an initial registration procedure by sending a registration request message. If the UE (e.g., ME) determines that the ME does not have 5GMM parameters for the first USIM (or if the UE determines that the association between the PEI corresponding to the ME and the SUPI corresponding to the second USIM is changed to an association between the PEI and the SUPI corresponding to the first USIM), the UE sends a registration request message with at least one of the following indicators: i) a first indicator indicating that the PEI-SUPI association has changed in the ME (e.g., a USIM update indicator); ii) A second indicator indicating that the UE does not have valid one or several 5GMM parameters for the first USIM stored in the ME memory.

[0049] In one example, the first indicator and the second indicator are transmitted as non-plaintext IEs as defined in Non-Patent Document 6. In another example, the first indicator and the second indicator are transmitted as plaintext IEs as defined in Non-Patent Document 6.

[0050] The first indicator may indicate that a USIM exchange has occurred. The second indicator may indicate 5GMM parameters required by the UE (e.g., ME). The first indicator may be referred to as an indicator indicating that an association between a PEI and an international mobile subscriber identity (SUPI) associated with the UE has changed. The first indicator may indicate when the PEI-SUPI association has changed in the ME after a successful registration procedure with the current PLMN. The first indicator may indicate when the PEI-SUPI association has changed in the ME after a successful registration procedure with the current associated AMF. The first indicator may indicate when the PEI-SUPI association has changed in the ME after a successful registration procedure with a current access type, which is either 3GPP access or non-3GPP access. The second indicator may indicate that the UE has lost one or several valid 5GMM parameters after a successful registration procedure with the current PLMN. The second indicator may indicate that the UE has lost one or several valid 5GMM parameters after a successful registration procedure with the current associated AMF. The second indicator may indicate that the UE has lost one or several valid 5GMM parameters after a successful registration procedure with the current access type, which may be either a 3GPP access or a non-3GPP access.

[0051] 4. Upon receiving the registration request message, the AMF can initiate the authentication procedure. Note that the first and second indicators can be sent from the UE to the AMF by any new or existing NAS message, such as a security mode complete message, after NAS security is established.

[0052] 5. When the AMF receives at least one of the first indicator and the second indicator in the registration request message, the AMF checks whether the AMF has a valid MM context for the UE (e.g., 5GMM parameters for the first USIM). If the AMF has a valid MM context for the UE, steps 6 to 10 are skipped and the process proceeds to step 11. Otherwise, the process proceeds to step 6.

[0053] Alternatively, the AMF shall always perform step 6. This is the case when the UDM provides a reporting event service for changes in PEI-SUPI associations.

[0054] 6. The AMF sends a Nudm_UECM_Registration message to the UDM. The Nudm_UECM_Registration message includes a SUPI, a PEI, and at least one of the first indicator and the second indicator. For example, the SUPI included in the Nudm_UECM_Registration message is the SUPI corresponding to the first USIM, and the PEI included in the Nudm_UECM_Registration message is the PEI corresponding to the ME. The AMF can obtain the SUPI and PEI from the registration request message after NAS security is established by the authentication procedure, or during the authentication procedure of step 4, or by any new or existing NAS message, such as a security mode complete message. For example, if the registration request message of step 3 includes the first indicator, the Nudm_UECM_Registration message includes the first indicator. For example, if the registration request message of step 3 includes the second indicator, the Nudm_UECM_Registration message includes the second indicator. For example, if the registration request in the message in step 3 includes a first indicator and a second indicator, the Nudm_UECM_Registration message includes the first indicator and the second indicator.

[0055] 7. In response to the Nudm_UECM_Registration message, the UDM sends a Nudm_UECM_Registration response message to the AMF.

[0056] 8. The AMF sends a Nudm_SDM_GET request message to the UDM. The Nudm_SDM_GET request message includes a SUPI, a PEI, and at least one of a first indicator and a second indicator. For example, the SUPI included in the Nudm_SDM_GET request message is a SUPI corresponding to the first USIM, and the PEI included in the Nudm_SDM_GET request message is a PEI corresponding to the ME.

[0057] For example, if the registration request message in step 3 includes a first indicator, the Nudm_SDM_GET request message includes the first indicator. For example, if the registration request message in step 3 includes a second indicator, the Nudm_SDM_GET request message includes the second indicator. For example, if the registration request message in step 3 includes a first indicator and a second indicator, the Nudm_SDM_GET request message includes the first indicator and the second indicator.

[0058] 9-10. Upon receiving the Nudm_SDM_GET request message, if the Nudm_SDM_GET request message or the Nudm_UECM_Registration message includes the first indicator, the UDM sends a Nudm_SDM_GET response message to the AMF, the Nudm_SDM_GET response message including at least one 5GMM parameter of the first USIM. If the Nudm_SDM_GET request message includes a second indicator instead of the first indicator, the UDM sends the 5GMM parameters for the first USIM as indicated by the second indicator in the Nudm_SDM_GET response message. For example, the UDM finds at least one 5GMM parameter of the first USIM based on the received SUPI or PEI in step 6 or 8, and sends a Nudm_SDM_GET response message to the AMF, the Nudm_SDM_GET response message including at least one 5GMM parameter of the first USIM.

[0059] The AMF may store the 5GMM parameters received from the UDM. The AMF may store the PEI-SUPI association (e.g., the association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM).

[0060] If the UDM provides a reporting event service for a change in the PEI-SUPI association, the UDM notifies the service consumer of the new PEI-SUPI association. The service consumer may be an NEF, an AF, or any other entity. For example, when the UDM receives a first indicator in a Nudm_UECM_Registration message or a Nudm_SDM_GET request message, the UDM notifies the service consumer of the new PEI-SUPI association (e.g., an association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM). The UDM may store the PEI-SUPI association (e.g., an association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM).

[0061] 11. Upon receiving the Nudm_SDM_GET response message from the UDM, the AMF sends a registration accept message including the 5GMM parameters. The 5GMM parameters may be those received in the Nudm_SDM_GET response message from the UDM (step 10) or those stored in the AMF in the MM context of the UE (step 5).

[0062] 12. Upon receiving a registration accept message containing 5GMM parameters from the AMF, the UE sends a registration complete message to the AMF. The UE stores the 5GMM parameters and uses them in subsequent procedures. For example, the UE sends a registration complete message to acknowledge receipt of the 5GMM parameters.

[0063] 13. Upon receiving a registration complete message from the UE, the AMF sends a message to the UDM indicating successful delivery of the 5GMM parameters. The message may be a Nudm_SDM_info message.

[0064] According to the above-described procedure, when the first USIM is reinserted (or when a USIM replacement occurs), the UE sends at least one of the first indicator and the second indicator, and the network (e.g., AMF and UDM) sends 5GMM parameters for the first USIM to the UE.

[0065] As a result, the UE can receive the 5GMM parameters for the first USIM and store them.

[0066] Therefore, the UE can receive some subscribed services based on the 5GMM parameters for the first USIM. Furthermore, the 5GMM parameters and the PEI-SUPI association can be synchronized between the UE and the network (e.g., AMF and UDM).

[0067] Furthermore, the UE can receive CAG information as one of the 5GMM parameters, so that the UE can find the CAG cell to which the user is subscribed and thus can register with the PNI-NPN.

[0068] In this situation, the UE can access the PNI-NPN.

[0069] <Description of the second exemplary embodiment that solves the problem (Solution 2: UDM always provides 5 GMM parameters)> The UDM provides 5GMM parameters whenever the UE registers with the network.

[0070] The detailed steps of the registration procedure are listed below.

[0071] 1. A first USIM is activated in an ME. For example, when the first USIM is inserted into an ME, the first USIM is activated in the ME. The ME creates an association between the PEI of the ME and the SUPI of the first USIM and stores the association.

[0072] 2. The ME checks whether it has the 5GMM parameters of the first USIM stored in the ME.

[0073] For example, the ME may check whether it is associated with a new USIM by checking whether the ME has the 5GMM parameters of the first USIM stored in the ME.

[0074] The ME does not store 5GMM parameters for the first USIM, for example, in case i) when the ME activates a second USIM and the user reactivates / inserts the first USIM, after which the ME does not have 5GMM parameters for the first USIM, or in case ii) when the first USIM is stored in ME memory and the 5GMM parameters are deleted from the ME memory due to a hard reset of the ME. An example of case i) is when the first USIM is reinserted after the second USIM is inserted in place of the first USIM. If the ME determines that the ME does not have 5GMM parameters for the first USIM, the UE (e.g., ME) determines that the PEI-SUPI association has changed. For example, the UE (e.g., ME) determines that the association between the PEI corresponding to the ME and the SUPI corresponding to the second USIM is changed to the association between the PEI and SUPI corresponding to the first USIM.

[0075] 3. The UE initiates a registration procedure to the network (e.g., AMF) by sending a registration request message. For example, the UE initiates an initial registration procedure by sending a registration request message. If the UE (e.g., ME) determines that the ME does not have 5GMM parameters for the first USIM (or if the UE determines that the association between the PEI corresponding to the ME and the SUPI corresponding to the second USIM is changed to an association between the PEI and the SUPI corresponding to the first USIM), the UE sends a registration request message with at least one of the following indicators: i) a first indicator indicating that the PEI-SUPI association has changed in the ME (e.g., a USIM update indicator); ii) A second indicator indicating that the UE does not have valid one or several 5GMM parameters for the first USIM stored in the ME memory.

[0076] In one example, the first indicator and the second indicator are transmitted as non-plaintext IEs as defined in Non-Patent Document 6. In another example, the first indicator and the second indicator are transmitted as plaintext IEs as defined in Non-Patent Document 6.

[0077] The first indicator may indicate that a USIM swap has occurred, and the second indicator may indicate 5GMM parameters required by the UE (e.g., ME).

[0078] 4. Upon receiving the registration request message, the AMF can initiate the authentication procedure. Note that the first and second indicators can be sent from the UE to the AMF by any new or existing NAS message, such as a security mode complete message, after NAS security is established.

[0079] 5. When the AMF receives at least one of the first indicator and the second indicator in the registration request message, the AMF checks whether the AMF has a valid MM context for the UE (e.g., 5GMM parameters for the first USIM). If the AMF has a valid MM context for the UE, steps 6 to 10 are skipped and the process proceeds to step 11. Otherwise, the process proceeds to step 6.

[0080] Alternatively, the AMF shall always perform step 6. This is the case when the UDM provides a reporting event service for changes in PEI-SUPI associations.

[0081] 6. The AMF sends a Nudm_UECM_Registration message to the UDM. The Nudm_UECM_Registration message includes a SUPI and a PEI. For example, the SUPI included in the Nudm_UECM_Registration message is the SUPI corresponding to the first USIM, and the PEI included in the Nudm_UECM_Registration message is the PEI corresponding to the ME. The AMF can obtain the SUPI and the PEI from the registration request message after NAS security is established by the authentication procedure, or during the authentication procedure of step 4, or by any new or existing NAS message, such as a security mode complete message.

[0082] 7. In response to the Nudm_UECM_Registration message, the UDM sends a Nudm_UECM_Registration response message to the AMF.

[0083] 8. The AMF sends a Nudm_SDM_GET request message to the UDM. The Nudm_SDM_GET request message includes a SUPI and a PEI. For example, the SUPI included in the Nudm_SDM_GET request message is the SUPI corresponding to the first USIM, and the PEI included in the Nudm_SDM_GET request message is the PEI corresponding to the ME.

[0084] 9-10. Upon receiving the Nudm_SDM_GET request message, the UDM sends a Nudm_SDM_GET response message to the AMF, the Nudm_SDM_GET response message including at least one 5GMM parameter of the first USIM. For example, upon receiving the Nudm_SDM_GET request message, the UDM always sends a Nudm_SDM_GET response message to the AMF, the Nudm_SDM_GET response message including at least one 5GMM parameter. In addition, the UDM finds at least one 5GMM parameter of the first USIM based on the received SUPI or PEI in step 8, and sends a Nudm_SDM_GET response message to the AMF, the Nudm_SDM_GET response message including at least one 5GMM parameter of the first USIM.

[0085] If the UDM provides a reporting event service for a change in the PEI-SUPI association, the UDM notifies the service consumer of the new PEI-SUPI association. The service consumer can be an NEF, an AF, or any other entity. For example, when the UDM receives a Nudm_UECM_Registration message or a Nudm_SDM_GET request message, the UDM notifies the service consumer of the new PEI-SUPI association (e.g., an association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM). The UDM may store the PEI-SUPI association (e.g., an association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM).

[0086] 11. Upon receiving the Nudm_SDM_GET response message from the UDM, the AMF sends a registration accept message including the 5GMM parameters. The 5GMM parameters may be those received in the Nudm_SDM_GET response message from the UDM (step 10) or those stored in the AMF in the MM context of the UE (step 5).

[0087] 12. Upon receiving a registration accept message containing 5GMM parameters from the AMF, the UE sends a registration complete message to the AMF. The UE stores the 5GMM parameters and uses them in subsequent procedures. For example, the UE sends a registration complete message to acknowledge receipt of the 5GMM parameters.

[0088] 13. Upon receiving a registration complete message from the UE, the AMF sends a message to the UDM indicating successful delivery of the 5GMM parameters. The message may be a Nudm_SDM_info message.

[0089] In one example, if the AMF receives at least one of the first indicator and the second indicator in step 3 of Figure 2, the AMF may perform step 6 above.

[0090] In one example, if the AMF does not receive at least one of the first indicator and the second indicator in step 3 of Figure 2, the AMF may perform step 6 above. That is, the AMF may perform step 6 above regardless of receiving at least one of the first indicator and the second indicator. For example, the AMF may perform step 6 above when the AMF receives a registration request message that does not include the first indicator and the second indicator, or after any new or existing NAS message, such as a security mode complete message, or after NAS security is established by an authentication procedure. The AMF may also perform the process according to Figure 2. The UDM may also always perform step 9 above when it receives a Nudm_Registration message in step 6 of Figure 2 or a Nudm_SDM_GET request message in step 8 of Figure 2. In other words, the UDM may perform step 9 above regardless of a change in association between a PEI and a SUPI or a replacement of a USIM. The UDM may also perform the process according to Figure 2.

[0091] According to the above-mentioned procedure, when the first USIM is reinserted, the UE sends at least one of the first indicator and the second indicator, and the network (e.g., AMF and UDM) sends 5GMM parameters for the first USIM to the UE.

[0092] As a result, the UE can receive the 5GMM parameters for the first USIM and store them.

[0093] Therefore, the UE can receive some subscribed services based on the 5GMM parameters for the first USIM. Furthermore, the 5GMM parameters and the PEI-SUPI association can be synchronized between the UE and the network (e.g., AMF and UDM).

[0094] Furthermore, the UE can receive CAG information as one of the 5GMM parameters, so that the UE can find the CAG cell to which the user is subscribed and thus can register with the PNI-NPN.

[0095] In this situation, the UE can access the PNI-NPN.

[0096] <Description of the third exemplary embodiment to solve the problem (Solution 3: Network detects changes in PEI-SUPI association)> During a registration procedure (e.g., an initial registration procedure), the AMF determines whether the PEI-SUPI association has changed. When the AMF receives a registration request message or any NAS message containing the UE's PEI (e.g., the PEI of the ME in the UE), the AMF compares the received PEI with the PEI of the UE context stored in the AMF. If the PEI received from the UE matches the PEI of any stored UE context and the SUPI of the matched UE context is different from the SUPI in the UE context corresponding to the received registration request message or any NAS message, the AMF sends a signaling message to the network indicating that the PEI-SUPI association has changed. Upon receiving the signaling message, the UDM sends at least one 5GMM parameter to the AMF. The AMF includes the 5GMM parameter in a registration accept message to the UE. The UE receives the registration accept message, stores the 5GMM parameters, and uses them in related subsequent procedures.

[0097] The detailed steps of the procedure are defined below.

[0098] 1. A first USIM is activated in an ME. For example, when the first USIM is inserted into an ME, the first USIM is activated in the ME. The ME creates an association between the PEI of the ME and the SUPI of the first USIM and stores the association.

[0099] 2. The UE initiates a registration procedure to the network (e.g., AMF) by sending a registration request message. For example, the UE initiates an initial registration procedure by sending a registration request message.

[0100] 3. Upon receiving the registration request message, the AMF can initiate an authentication procedure. The ME's PEI (e.g., the ME's PEI in the UE) and the first USIM's SUPI can be sent from the UE to the AMF via any new or existing NAS message, such as a security mode complete message, after NAS security is established by the authentication procedure.

[0101] The AMF stores the PEI-SUPI association (eg, the association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM).

[0102] 4-5. After the successful authentication procedure, the AMF determines whether the PEI-SUPI association has changed for the ME. When the AMF receives a registration request message or any NAS message including the PEI of the ME (e.g., the ME of the UE), the AMF compares the received PEI with the PEI of the UE context stored in the AMF. If the received PEI in the registration request message or any NAS message from the UE matches the PEI of any stored UE context in the AMF, the AMF compares the SUPI corresponding to the matched PEI in the UE context stored in the AMF with the SUPI corresponding to the received PEI in the UE context corresponding to the registration request message or any NAS message. If the SUPI in the UE context stored in the AMF is different from the SUPI in the UE context corresponding to the registration request message or any NAS message, the AMF determines that the PEI-SUPI association has changed or a USIM replacement has occurred. The AMF then sends a Nudm_UECM_Registration message to the UDM. The Nudm_UECM_Registration message includes the SUPI, the PEI, and a first indicator. For example, the SUPI included in the Nudm_UECM_Registration message is the SUPI corresponding to the first USIM, and the PEI included in the Nudm_UECM_Registration message is the PEI corresponding to the ME. The first indicator (e.g., a USIM update indicator) indicates that the PEI-SUPI association has changed in the ME. The first indicator can indicate that a USIM replacement has occurred.

[0103] For example, after a first USIM is inserted into the ME of the UE and the UE sends a first registration request message triggered by the insertion of the first USIM and successful authentication of the UE, the AMF stores a first association between the PEI of the ME and the first SUPI of the first USIM. Subsequently, a second USIM is inserted into the ME and the UE sends a registration request message triggered by the insertion of the second USIM. In this case, after successful authentication, the AMF obtains a second association between the PEI of the ME and the second SUPI of the second USIM. The AMF then compares the PEI of the second association with the PEI of the first association stored in the AMF. In this case, the AMF determines that the PEIs of the first and second associations are the same. The AMF also compares the first SUPI of the first association with the second SUPI of the second association. In this case, the AMF determines that the first SUPI is different from the second SUPI (i.e., the AMF determines that the PEI is the same but the SUPIs are different from each other, and therefore the AMF determines that the PEI-SUPI association has changed or a USIM replacement has occurred). The AMF then sends a Nudm_UECM_Registration message to the UDM, which includes the first SUPI, the PEI, and the first indicator.

[0104] Otherwise (for example, if the AMF has a UE context (e.g., 5GMM parameters) corresponding to the PEI or SUPI corresponding to the received registration request message or any NAS message, and the AMF determines that the PEI-SUPI association has not changed or a USIM replacement has not occurred), steps 5 to 10 can be skipped and the process proceeds to step 10. The first indicator can be named as a PEI-SUPI association change indicator or any other name.

[0105] 6. In response to the Nudm_UECM_Registration message, the UDM sends a Nudm_UECM_Registration response message to the AMF.

[0106] 7. The AMF sends a Nudm_SDM_GET request message to the UDM. The Nudm_SDM_GET request message includes a SUPI, a PEI, and a first indicator. For example, the SUPI included in the Nudm_SDM_GET request message is the SUPI corresponding to the first USIM, and the PEI included in the Nudm_SDM_GET request message is the PEI corresponding to the ME.

[0107] 8-9. Upon receiving the Nudm_SDM_GET request message, if the Nudm_SDM_GET request message or the Nudm_UECM_Registration message includes a first indicator, the UDM sends a Nudm_SDM_GET response message including at least one 5GMM parameter to the AMF.

[0108] If the UDM provides a reporting event service for a change in the PEI-SUPI association, the UDM notifies the service consumer of the new PEI-SUPI association. The service consumer may be an NEF, an AF, or any other entity. For example, when the UDM receives a first indicator in a Nudm_UECM_Registration message or a Nudm_SDM_GET request message, the UDM notifies the service consumer of the new PEI-SUPI association (e.g., an association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM). The UDM may store the PEI-SUPI association (e.g., an association between the PEI corresponding to the ME and the SUPI corresponding to the first USIM).

[0109] 10. Upon receiving the Nudm_SDM_GET response message from the UDM, the AMF sends a registration accept message including the 5GMM parameters. The 5GMM parameters may be those received in the Nudm_SDM_GET response message from the UDM (step 9) or those stored in the AMF in the MM context of the UE (step 4).

[0110] 11. Upon receiving a registration accept message containing 5GMM parameters from the AMF, the UE sends a registration complete message to the AMF. The UE stores the 5GMM parameters and uses them in subsequent procedures. For example, the UE sends a registration complete message to acknowledge receipt of the 5GMM parameters.

[0111] 12. Upon receiving a registration complete message from the UE, the AMF sends a message to the UDM indicating that the 5GMM parameters have been successfully delivered. The message may be a Nudm_SDM_info message.

[0112] According to the above-described procedure, the AMF determines that the PEI-SUPI association has changed or a USIM replacement has occurred, and the network (e.g., the AMF and UDM) sends the 5GMM parameters for the first USIM to the UE.

[0113] As a result, the UE can receive the 5GMM parameters for the first USIM and store them.

[0114] Therefore, the UE can receive some subscribed services based on the 5GMM parameters for the first USIM. Furthermore, the 5GMM parameters and the PEI-SUPI association can be synchronized between the UE and the network (e.g., AMF and UDM).

[0115] Furthermore, the UE can receive CAG information as one of the 5GMM parameters, so that the UE can find the CAG cell to which the user is subscribed and thus can register with the PNI-NPN.

[0116] In this situation, the UE can access the PNI-NPN.

[0117] <Variation 1 of Solution 3> Variant 1 uses an Equipment Identity Register (EIR) to detect changes in the PEI-SUPI association. The EIR may be a 5G-EIR. In this variant 1, the EIR maintains (or stores) an association between the PEI and the SUPI (PEI-SUPI association). During a registration procedure (e.g., an initial registration procedure), the AMF sends a message to the EIR including the PEI of the ME (e.g., the PEI of the ME in the UE) inserted in the ME of the UE that initiated the registration procedure and the SUPI of the USIM. If the EIR does not have a context for the PEI, the EIR stores the PEI-SUPI association and time information when the association was made. The time information may be referred to as time data. If the EIR has an entry for the PEI (i.e., if the EIR has a context for the PEI), the EIR checks whether the SUPI received in the message is different from the SUPI associated with the PEI stored in the EIR. If these two SUPIs are different, the EIR sends a PEI-SUPI association change indicator in the response message to the AMF; otherwise, the EIR sends an indicator to the AMF indicating that the PEI-SUPI association remains the same in the response message.

[0118] The following steps 4-1 to 4-4 can be performed as step 4 in Fig. 3 of the third exemplary embodiment. For example, steps 4-1 to 4-4 may be performed instead of step 4.

[0119] 4-1. The AMF sends an N5g-eir_EquipmentIdentityCheck_Get message to the EIR. The N5g-eir_EquipmentIdentityCheck_Get message includes a PEI and a SUPI. The PEI and SUPI included in the N5g-eir_EquipmentIdentityCheck_Get message are the PEI and SUPI that can be sent from the UE to the AMF by any new or existing NAS message, such as a Security Mode Complete message, after NAS security has been established by the authentication procedure, as described in step 3 of the third exemplary embodiment.

[0120] 4-2. Upon receiving the N5g-eir_EquipmentIdentityCheck_Get message, the EIR checks whether it has a context for the received PEI. If the EIR does not have a context for the received PEI (e.g., the association between the PEI and SUPI received in step 4-1), the EIR creates a context for the PEI and stores the PEI-SUPI association (e.g., the association between the PEI and SUPI received in step 4-1). The EIR optionally stores a time record when the association was created.

[0121] For example, when an EIR receives an N5g-eir_EquipmentIdentityCheck_Get message that includes a PEI and a SUPI, the EIR determines whether the received PEI matches a PEI in a PEI-SUPI association previously stored in the EIR. If the EIR determines that the received PEI does not match any PEI in a PEI-SUPI association previously stored in the EIR, the EIR determines that the EIR does not have a context for the received PEI.

[0122] 4-3. If the EIR has the context of the PEI (e.g., the PEI-SUPI association of the received PEI), the EIR checks whether the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message matches the SUPI associated with the PEI stored in the EIR.

[0123] For example, when an EIR receives an N5g-eir_EquipmentIdentityCheck_Get message that includes a PEI and a SUPI, the EIR determines whether the received PEI matches a PEI in a PEI-SUPI association previously stored in the EIR. If the EIR determines that the received PEI matches a PEI in a PEI-SUPI association previously stored in the EIR, the EIR determines that the EIR has a context for the received PEI.

[0124] Also, for example, if the EIR checks whether the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message matches the SUPI associated with the PEI stored in the EIR, the EIR may check whether the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message is different from the SUPI associated with the PEI stored in the EIR.

[0125] For example, the EIR determines whether the received SUPI matches the SUPI of a PEI-SUPI association previously stored in the EIR (this association includes the matched PEI described above).

[0126] If these two SUPIs (e.g., the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message and the SUPI associated with the PEI stored in the EIR) are different, the EIR determines that the PEI-SUPI association has changed or a USIM replacement has occurred. The EIR then indicates a PEI-SUPI association change indicator to the AMF. The indicator indicates that the PEI-SUPI association has changed. The indicator may indicate that a USIM replacement has occurred. For example, the EIR sends an N5g-eir_EquipmentIdentityCheck_Get response message including the PEI-SUPI association change indicator to the AMF.

[0127] If not (e.g., if the two SUPIs are the same), the EIR sends an indicator indicating that the PEI-SUPI association remains the same in an N5g-eir_EquipmentIdentityCheck_Get response message. In one example, the response message is sent from the EIR only if the EIR determines that the PEI-SUPI association has changed. The N5g-eir_EquipmentIdentityCheck_Get response optionally includes the SUPI previously associated with the PEI and time data when the association of the PEI with the previously stored SUPI occurred. For example, the EIR sends a PEI check result to the AMF indicating that the PEI-SUPI association remains the same in the N5g-eir_EquipmentIdentityCheck_Get response message.

[0128] The PEI-SUPI association change indicator may be a SUPI previously associated with the PEI. For example, the PEI-SUPI association change indicator may indicate a SUPI previously associated with the PEI stored in the EIR. For example, if an association between the PEI and a first SUPI is changed to an association between the PEI and a second SUPI, the PEI-SUPI association change indicator may indicate the second SUPI.

[0129] 4-4. When the AMF receives the N5g-eir_EquipmentIdentityCheck_Get response message, the AMF refers to the information in the N5g-eir_EquipmentIdentityCheck_Get response message to determine (or judge or check) whether the PEI-SUPI association has changed (or whether a USIM replacement has occurred). For example, the AMF indicates a PEI-SUPI association change indicator. Also, for example, when the AMF receives a PEI-SUPI association change indicator indicating that the PEI-SUPI association has changed, the AMF performs step 5 in the third exemplary embodiment (i.e., the AMF sends a Nudm_UECM_Registration message to the UDM). Furthermore, when the AMF receives a PEI-SUPI association change indicator indicating a SUPI previously associated with the PEI, the AMF determines that the PEI-SUPI association has changed by determining that the SUPI indicated by the PEI-SUPI association change indicator is different from the received SUPI referred to in step 3 of the third exemplary embodiment.

[0130] In one example of variant 1 of Solution 3, the AMF subscribes to a PEI-SUPI association change monitoring service provided by the EIR. In this example, the AMF sends an N5g-eir_EquipmentIdentityMonitor message along with the PEI received from the UE via a NAS message. The EIR notifies the AMF every time the PEI-SUPI association changes. The EIR notification message includes the PEI, a PEI-SUPI association change indicator, and optionally the newly associated SUPI.

[0131] Upon receiving notification about a PEI-SUPI association change, the AMF may take one of the following actions: The AMF maintains (or stores) the PEI-SUPI association change indicator in the MM context of the SUPI. After that, the AMF shall update the 5GMM parameters of the UE each time the UE contacts the AMF. -AMF purges SUPI. The AMF sends a deregistration request message to the UE with re-registration. Upon receiving the deregistration request message, the UE sends a registration request message to the AMF so that the 5GMM parameters in the UE can be reinstalled.

[0132] <Variation 2 of Solution 3> Variation 2 uses the EIR to detect changes in the PEI-SUPI association. In this variation 2, the UDM sends a request to the EIR to store the PEI-SUPI association. The EIR maintains (or stores) the PEI-SUPI association. The EIR also indicates whether the PEI-SUPI association has changed.

[0133] The following steps 8-1 to 8-4 may be performed as step 8 in FIG. 3 of the third exemplary embodiment. For example, if the UDM receives the SUPI, PEI, and the first indicator in step 5 or 7 in FIG. 3, it performs steps 8-1 to 8-4. For example, if the UDM does not receive the first indicator in step 5 or 7 in FIG. 3, it performs steps 8-1 to 8-4. That is, if the UDM receives the SUPI and PEI in step 5 or 7 in FIG. 3, it may perform steps 8-1 to 8-4. For example, the UDM can perform steps 8-1 to 8-4 regardless of whether the first indicator is included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message.

[0134] 8-1. The UDM sends an N5g-eir_EquipmentIdentityCheck_Get message to the EIR. The N5g-eir_EquipmentIdentityCheck_Get message includes the PEI and SUPI. The PEI and SUPI included in the N5g-eir_EquipmentIdentityCheck_Get message are the PEI and SUPI received by the UDM in step 5 or 7 of the third exemplary embodiment.

[0135] 8-2. Upon receiving the N5g-eir_EquipmentIdentityCheck_Get message, the EIR checks whether it has a context for the received PEI. If the EIR does not have a context for the PEI (e.g., the association between the PEI and SUPI received in step 8-1), the EIR creates a context for the PEI and stores the PEI-SUPI association (e.g., the association between the PEI and SUPI received in step 8-1). The EIR optionally stores a time record when the association was created.

[0136] For example, when the EIR receives an N5g-eir_EquipmentIdentityCheck_Get message containing a PEI and a SUPI, the AMF determines whether the received PEI matches a PEI in a PEI-SUPI association previously stored in the EIR. If the EIR determines that the received PEI does not match any PEI in a PEI-SUPI association previously stored in the EIR, the EIR determines that the EIR does not have a context for the received PEI.

[0137] 8-3. If the EIR has the context of the received PEI and the PEI-SUPI association of the received PEI, the EIR checks whether the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message matches the SUPI associated with the PEI stored in the EIR.

[0138] For example, when an EIR receives an N5g-eir_EquipmentIdentityCheck_Get message that includes a PEI and a SUPI, the EIR determines whether the received PEI matches a PEI in a PEI-SUPI association previously stored in the EIR. If the EIR determines that the received PEI matches a PEI in a PEI-SUPI association previously stored in the EIR, the EIR determines that the EIR has a context for the received PEI.

[0139] Also, for example, if the EIR checks whether the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message matches the SUPI associated with the PEI stored in the EIR, the EIR may check whether the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message is different from the SUPI associated with the PEI stored in the EIR.

[0140] For example, the EIR determines whether the received SUPI matches the SUPI of a PEI-SUPI association previously stored in the EIR (this association includes the matched PEI described above).

[0141] If these two SUPIs (e.g., the SUPI received in the N5g-eir_EquipmentIdentityCheck_Get message and the SUPI associated with the PEI stored in the EIR) are different, the EIR determines that the PEI-SUPI association has changed or a USIM replacement has occurred. The EIR then indicates a PEI-SUPI association change indicator to the UDM. The indicator indicates that the PEI-SUPI association has changed. The indicator can indicate that a USIM replacement has occurred. For example, the EIR sends an N5g-eir_EquipmentIdentityCheck_Get response message including the PEI-SUPI association change indicator to the UDM.

[0142] If not (e.g., if the two SUPIs are the same), the EIR sends an indicator indicating that the PEI-SUPI association remains the same in an N5g-eir_EquipmentIdentityCheck_Get response message. In one example, the response message is sent from the EIR only if the EIR determines that the PEI-SUPI association has changed. The N5g-eir_EquipmentIdentityCheck_Get response optionally includes the SUPI previously associated with the PEI and time data when the association of the PEI with the previously stored SUPI occurred. For example, the EIR sends a PEI check result to the UDM indicating that the PEI-SUPI association remains the same in the N5g-eir_EquipmentIdentityCheck_Get response message.

[0143] The PEI-SUPI association change indicator may be a SUPI previously associated with the PEI. For example, the PEI-SUPI association change indicator may indicate a SUPI previously associated with the PEI stored in the EIR. For example, if an association between the PEI and a first SUPI is changed to an association between the PEI and a second SUPI, the PEI-SUPI association change indicator may indicate the second SUPI.

[0144] 8-4. When the UDM receives the N5g-eir_EquipmentIdentityCheck_Get response message, the UDM determines (or judges or checks) whether the PEI-SUPI association has changed (or whether a USIM replacement has occurred) by referring to the information in the N5g-eir_EquipmentIdentityCheck_Get response message. For example, the UDM indicates a PEI-SUPI association change indicator. Additionally, for example, when the UDM receives a PEI-SUPI association change indicator indicating that the PEI-SUPI association has changed, the UDM performs step 9 in the third exemplary embodiment (i.e., the UDM sends a Nudm_SDM_GET response message to the AMF). Furthermore, when the UDM receives a PEI-SUPI association change indicator indicating a SUPI previously associated with the PEI, the UDM determines that the PEI-SUPI association has changed by determining that the SUPI indicated by the PEI-SUPI association change indicator is different from the received SUPI referred to in step 5 or 7 of the third exemplary embodiment.

[0145] In one example of Variant 2 of Solution 3, the UDM subscribes to a PEI-SUPI association change monitoring service provided by the EIR. In this example, the UDM sends an N5g-eir_EquipmentIdentityMonitor message with the PEI received from the UE via a NAS message. The EIR notifies the UDM whenever the PEI-SUPI association changes. The EIR notification message includes the PEI, a PEI-SUPI association change indicator, and optionally the newly associated SUPI.

[0146] Upon receiving notification about a PEI-SUPI association change, the UDM can take one of the following actions: The UDM maintains (or stores) the PEI-SUPI association change indicator in the SUPI subscriber data. After that, each time the AMF contacts the UDM, the UDM shall provide the UE with 5GMM parameters. The UDM notifies the service consumer of the new PEI-SUPI association. The service consumer can be an NEF, an AF, or any other entity. -UDM sends Nudm_UECM_Update to the service consumer indicating that the PEI has been invalidated. -UDM sends a Nudm_SDM_Notification to the service consumer indicating that the PEI has been invalidated.

[0147] In one example of Variant 2 of Solution 3, if the UDM receives the first indicator in step 5 or step 7 of Figure 3, the UDM can perform step 8-1 above.

[0148] In one example of Variation 2 of Solution 3, if the UDM does not receive the first indicator in step 5 or step 7 of Figure 3, the UDM can perform step 8-1 above. That is, the UDM can perform step 8-1 above regardless of whether it receives the first indicator.

[0149] In the above exemplary embodiment, the PEI-SUPI association or the association between the PEI and the SUPI can be referred to as the association between the PEI and the SUPI, association information indicating the association between the PEI and the SUPI related to the UE.

[0150] In the above example embodiment, the 5GMM parameters may be referred to as parameters related to 5GMM or information related to 5GMM or 5GMM parameters related to the UE.

[0151] In the above exemplary embodiment, the PEI and SUPI may be referred to as the UE-associated PEI and the UE-associated SUPI, respectively.

[0152] In the above exemplary embodiments, the UE, the AMF, the UDM, and the EIR may be referred to as communication devices or communication nodes, and the AMF, the UDM, and the EIR may be referred to as core network devices or core network nodes.

[0153] In the above exemplary embodiment, the USIM may be referred to as a SIM.

[0154] In the above exemplary embodiment, the change of the PEI-SUPI association due to a replacement of the USIM was described.

[0155] However, the exemplary embodiments are applicable to an embedded SIM (eSIM). For example, when a USIM is activated in place of another USIM in an eSIM (e.g., when first configuration information for receiving services from one carrier is activated in place of second configuration information for receiving services from another carrier in an eSIM. In this case, the second configuration information is deleted from the eSIM when the first configuration information is activated or after the first configuration information is activated), the UE can perform step 3 of the first exemplary embodiment, or the UE can perform step 3 of the second exemplary embodiment, or the UE can perform step 2 of the third exemplary embodiment. After these processes by the UE, subsequent processes are performed according to each exemplary embodiment.

[0156] <User Equipment (UE)> FIG. 6 is a block diagram illustrating the main components of a mobile device 3 (UE 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit signals to and receive signals from connected nodes via one or more antennas 32. Although not necessarily shown in FIG. 6, the UE 3 may have all the usual functionality of a conventional mobile device (e.g., a user interface 34), which may be provided by any one or any combination of hardware, software, and firmware, as appropriate. The software may be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of the UE 3 in accordance with software stored in the memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for processing (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 10. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE 3). The controller 33 interacts with one or more universal subscriber identity modules (USIMs) 35. If equipped with multiple USIMs 35, the controller 33 may activate only one USIM 35 or multiple USIMs 35 simultaneously. The UE 3 may support, for example, a non-public network (NPN), which may be a standalone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).UE3 may be, for example, an item of equipment for production or manufacturing and / or an item of energy-related machinery (e.g., equipment or machinery, such as boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power plants; nuclear generators; batteries; nuclear systems and / or related equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; hydraulic equipment; pneumatic equipment; metalworking machinery; manipulators; robots and / or application systems thereof; tools; molds or dies; rolls; conveying equipment; elevators; material handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting equipment; chemical machinery; mining machinery and / or construction machinery and / or related equipment; machinery and / or implements for the agricultural, forestry and / or fisheries industries; safety and / or environmental protection equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubrication equipment; valves; pipe fittings; and / or application systems for any of the foregoing equipment or machinery, etc.). The UE 3 may be, for example, an item of transportation equipment (e.g., transportation equipment such as rolling stock; automobiles; motorcycles; bicycles; trains; buses; carts; human-powered vehicles; ships and other watercraft; aircraft; rockets; satellites; drones; balloons, etc.). The UE 3 may be, for example, an item of information and communication equipment (e.g., information and communication equipment such as electronic computers and related equipment; communication and related equipment; electronic components, etc.). The UE 3 may be, for example, a refrigerator, a refrigerator-applied product, goods and / or service industry equipment, vending machines, automatic service machines, office machines or equipment, consumer electronics and electronic devices (e.g., consumer electronic devices such as audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related equipment; vacuum cleaners, etc.). The UE 3 may be, for example, an electrical application system or equipment (e.g., an electrical application system or equipment such as an X-ray system; particle accelerators; radioisotope devices; sonic devices; electromagnetic application devices; electronic power application devices, etc.).The UE 3 may be, for example, an electronic lamp, lighting fixture, measuring instrument, analyzer, tester, or surveying or sensing equipment (e.g., surveying or sensing equipment such as a smoke alarm, a motion sensor, a radio frequency tag, etc.), a watch or clock, inspection equipment, optical device, medical equipment and / or system, weapon, blade, hand tool, etc. The UE 3 may be, for example, a wireless-equipped personal digital assistant or related equipment (e.g., a wireless card or module designed to be attached to or inserted into another electronic device (e.g., a personal computer, an electrical measuring instrument)). The UE 3 may be part of a device or system that uses various wired and / or wireless communication technologies to provide applications, services, and solutions described below with respect to the “Internet of Things (IoT).” The UE 3 may be a smartphone (e.g., an iPhone® or an Android®-based phone) or a wearable device (e.g., smart glasses or a smart watch). The UE 3 may be an automobile, a connected car, an autonomous vehicle, a vehicle device, a motorcycle, or a V2X communication module. Internet of Things devices (or "things") can be equipped with appropriate electronics, software, sensors, network connectivity, etc. that enable these devices to collect and exchange data with each other and other communicating devices. IoT devices can include automated machines that follow software instructions stored in internal memory. IoT devices can operate without the need for human supervision or interaction. IoT devices can also remain stationary and / or inactive for extended periods of time. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be embedded in non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.It will be appreciated that IoT technology can be implemented on any communication device capable of connecting to a communication network to transmit / receive data, regardless of whether such communication device is controlled by human input or software instructions stored in memory. It will be appreciated that an IoT device may also be referred to as a machine-type communication (MTC) device, a machine-to-machine (M2M) communication device, or a narrowband IoT UE (NB-IoT UE). It will be appreciated that a UE 3 can support one or more IoT or MTC applications.

[0157] <(R)AN node> FIG. 7 is a block diagram illustrating the main components of an exemplary (R)AN node 5, e.g., a base station (eNB in ​​LTE, gNB in ​​5G, base station for beyond 5G, base station for 6G). As shown, the (R)AN node 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from connected UEs 3 via one or more antennas 52 and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls operation of the (R)AN node 5 in accordance with software stored in memory 55. The software may be pre-installed in the memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521. The communication control module 5521 (using its transceiver control submodule) is responsible for processing (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 10, and the UPF 12 (e.g., directly or indirectly). The signaling may include, for example, appropriately formatted signaling messages related to the radio connection and connectivity with the core network 7 (for a particular UE 3), in particular, connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages over the N2 reference point) and Xn Application Protocol (XnAP) messages (i.e., messages over the Xn reference point), etc. Such signaling may also include, for example, broadcast information (e.g., master information and system information) in the transmission case. When implemented, the controller 54 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.The (R)AN node 5 may support a non-public network (NPN), which may be a standalone non-public network (SNPN) or a public network integrated NPN (PNI-NPN).

[0158] <amf> FIG. 8 is a block diagram illustrating the main components of the AMF 10. As shown, the device includes a transceiver circuit 101 operable to transmit signals to and receive signals from other nodes (including UE 3) via a network interface 102. A controller 103 controls the operation of the AMF 10 according to software stored in a memory 104. The software may be pre-installed in the memory 104 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 1041 and a communications control module 1042 having at least a transceiver control module 10421. The communications control module 1042 (using its transceiver control module 10421) is responsible for processing (generating / sending / receiving) signaling between the AMF 10 and other nodes, such as the UE 3 (e.g., via the (R)AN node 5) and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE 3). The AMF 10 may support non-public networks (NPNs), which may be standalone non-public networks (SNPNs) or public network integrated NPNs (PNI-NPNs).

[0159] <udm> 9 is a block diagram illustrating the main components of the UDM 15. As shown, the device includes a transceiver circuit 151 operable to transmit signals to and receive signals from other nodes (including the AMF 10) via a network interface 152. A controller 153 controls the operation of the UDM 15 according to software stored in a memory 154. The software may be pre-installed in the memory 154 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 1541 and a communication control module 1542 having at least a transceiver control module 15421. The communication control module 1542 (using its transceiver control module 15421) is responsible for processing (generating / sending / receiving) signaling between the UDM 15 and other nodes, such as the AMF 10 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP convenience methods based on service-based interfaces) related to mobility management procedures (for the UE 3). The UDM 15 may support non-public networks (NPNs), which may be standalone non-public networks (SNPNs) or public network integrated NPNs (PNI-NPNs).

[0160] <eir> FIG. 10 is a block diagram illustrating the main components of the EIR 16. As shown, the device includes a transceiver circuit 161 operable to transmit signals to and receive signals from other nodes (including the AMF 10 and the UDM 15) via a network interface 162. A controller 163 controls the operation of the EIR 16 according to software stored in a memory 164. The software may be pre-installed in the memory 164 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 1641 and a communications control module 1642 having at least a transceiver control module 16421. The communications control module 1642 (using its transceiver control module 16421) is responsible for processing (generating / sending / receiving) signaling between the EIR 16 and other nodes, such as the AMF 10, the UDM 15, and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP convenience methods based on service-based interfaces) related to network data analysis function procedures (for UE 3). The EIR 16 may support non-public networks (NPNs), which may be standalone non-public networks (SNPNs) or public network integrated NPNs (PNI-NPNs).

[0161] User equipment (or "UE," "mobile station," "mobile device," or "wireless device") in this disclosure is an entity connected to a network via an air interface. Note that UE in this specification is not limited to a dedicated communication device, but can apply to any device having communication capabilities as a UE as described in the following paragraphs. The terms "user equipment" or "UE" (as the term is used by 3GPP), "mobile station," "mobile equipment," and "wireless apparatus" are generally intended to be synonymous with each other and include standalone mobile stations such as terminals, mobile phones, smartphones, tablets, cellular IoT devices, IoT devices, and machines. It will be understood that the terms "UE" and "wireless device" also encompass devices that remain stationary for long periods of time. The UE may be, for example, an item of equipment for production or manufacturing and / or an item of energy-related machinery (e.g., equipment or machinery, such as boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power plants; nuclear generators; batteries; nuclear systems and / or related equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; hydraulic equipment; pneumatic equipment; metalworking machinery; manipulators; robots and / or application systems thereof; tools; molds or dies; rolls; conveying equipment; elevators; material handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting equipment; chemical machinery; mining machinery and / or construction machinery and / or related equipment; machinery and / or implements for the agriculture, forestry and / or fisheries industries; safety and / or environmental protection equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubrication equipment; valves; pipe fittings; and / or application systems for any of the aforementioned equipment or machinery, etc.).

[0162] The UE may be, for example, an item of transportation equipment (e.g., transportation equipment such as rolling stock; automobiles; motorcycles; bicycles; trains; buses; carts; human-powered vehicles; ships and other watercraft; aircraft; rockets; satellites; drones; balloons, etc.). The UE may be, for example, an item of information and communications equipment (e.g., information and communications equipment such as electronic computers and related equipment; communications and related equipment; electronic components, etc.). The UE may be, for example, a refrigerator, a refrigerator-based product, goods and / or service industry equipment, vending machines, automated service machines, office machines or equipment, consumer electronics and electronic devices (e.g., consumer electronic devices such as audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related equipment; vacuum cleaners, etc.). The UE may be, for example, an electrical application system or equipment (e.g., an electrical application system or equipment such as an x-ray system; particle accelerators; radioisotope devices; sonic devices; electromagnetic application devices; electronic power application devices, etc.). A UE may be, for example, an electronic lamp, lighting fixture, measuring instrument, analyzer, tester, or surveying or sensing equipment (e.g., surveying or sensing equipment such as smoke alarms; motion sensors; radio frequency tags; etc.), a watch or clock, inspection equipment, optical device, medical equipment and / or system, weapon, blade, hand tool, etc. A UE may be, for example, a wireless-equipped personal digital assistant or related equipment (e.g., a wireless card or module designed to be attached to or inserted into another electronic device (e.g., a personal computer, electrical measuring equipment)). A UE may be part of a device or system that uses various wired and / or wireless communication technologies to provide applications, services, and solutions described below with respect to the "Internet of Things (IoT)." Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, etc. that enable these devices to collect and exchange data with each other and other communicating devices. IoT devices may include automated equipment that follows software instructions stored in internal memory.IoT devices can operate without the need for human supervision or interaction. They can also remain stationary and / or inactive for long periods of time. IoT devices may be implemented as part of (generally) fixed equipment. IoT devices may also be embedded in non-fixed equipment (e.g., vehicles) or attached to animals or people being monitored / tracked. It will be understood that IoT technology can be implemented on any communication device capable of connecting to a communication network to transmit / receive data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory. It will be understood that IoT devices may also be referred to as machine-type communication (MTC) devices, machine-to-machine (M2M) communication devices, or narrowband IoT UEs (NB-IoT UEs). It will be understood that a UE can support one or more IoT or MTC applications. Some examples of MTC applications are listed in Table 1 (Source: 3GPP TS 22.368, Annex B, the contents of which are incorporated herein by reference). This list is not exhaustive and is intended to illustrate some examples of machine-type communication applications. Table 1: Some examples of machine-type communication applications TIFF0007750303000001.tif197145

[0163] The applications, services, and solutions may be MVNO (Mobile Virtual Network Operator) services, emergency wireless communication systems, PBX (Private Branch eXchange) systems, PHS / digital cordless communication systems, POS (Point of sale) systems, advertising call systems, MBMS (Multimedia Broadcast and Multicast Service), V2X (Vehicle to Everything) systems, train radio systems, location-related services, disaster / emergency wireless communication services, community services, video streaming services, femtocell application services, VoLTE (Voice over LTE) services, billing services, wireless on-demand services, roaming services, activity monitoring services, carrier / communication network selection services, function restriction services, PoC (Proof of Concept) services, personal information management services, ad hoc networks / DTN (Delay Tolerant Network) services, etc.

[0164] Furthermore, the above-mentioned UE categories are merely examples of applications of the concepts and exemplary embodiments described herein, and of course, these concepts and exemplary embodiments are not limited to the above-mentioned UEs and may be modified in various ways.

[0165] <Modifications and Alternatives> Detailed embodiments have been described above. As those skilled in the art will appreciate, several modifications and alternatives can be made to the above embodiments while still benefiting from the disclosure embodied therein. By way of example only, some of these alternatives and modifications are described herein.

[0166] In the above description, for ease of understanding, the UE 3 and network devices are described as having several separate modules (e.g., a communications control module). While these modules may be provided in this manner for certain applications, such as when an existing system is modified to implement the present disclosure, or for other applications, such as systems designed from the beginning with the features of the present invention in mind, these modules may not be identifiable as separate entities because they may be incorporated into an overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a combination thereof. Each control unit may comprise any suitable form of processing circuitry, including, but not limited to, one or more hardware-implemented computer processors; a microprocessor; a central processing unit (CPU); an arithmetic logic unit (ALU); input / output (IO) circuitry; internal memory / cache (program and / or data); processing registers; communication buses (e.g., control buses, data and / or address buses); direct memory access (DMA) functions; hardware or software-implemented counters, pointers, and / or timers; etc.

[0167] In the above embodiments, a number of software modules have been described. As will be appreciated by those skilled in the art, the software modules may be provided in compiled or uncompiled form and may be supplied to the UE 3 and network devices via a computer network or as a signal on a recording medium. Furthermore, the functions performed by some or all of this software may be performed using one or more dedicated hardware circuits. However, using software modules is preferred because it facilitates updating the UE 3 and network devices to update their functionality.

[0168] In the above embodiment, 3GPP radio access technology is used. However, any other radio access technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed line communication technology (e.g., BBF access, cable access, optical access, etc.) can also be used according to the above embodiment.

[0169] Items of user equipment may include, for example, communication devices such as mobile phones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, etc. Such mobile (or even generally fixed) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, this application will refer to mobile devices (or UE) in the description, but it will be understood that the described techniques can be implemented in any communication device (mobile and / or generally fixed) that can connect to a communication network to transmit and receive data, regardless of whether such communication device is controlled by human input or software instructions stored in memory.

[0170] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0171] Furthermore, the first to third exemplary embodiments and modifications 1 and 2 have mainly been described with reference to the 5G system. However, these exemplary embodiments and modifications can also be applied to wireless communication systems other than the 5G system, such as a 6G system, a system beyond 5G, an LTE system, a 3GPP Universal Mobile Telecommunications System (UMTS), a 3GPP2 CDMA2000 system (1xRTT, HRPD (High Rate Packet Data)), a GSM (Global System for Mobile Communications) system, a WiMAX system, and the like.

[0172] The entire or part of the exemplary embodiments disclosed above can be described as, but not limited to, the following supplementary notes.

[0173] Appendix 1 1. A method for a user equipment (UE), comprising: transmitting an indicator indicating that an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identity (SUPI) associated with the UE has changed; and receiving 5GS Mobility Management (5GMM) parameters associated with the UE after transmitting the indicator; A method comprising:

[0174] Appendix 2 transmitting an indicator if the UE determines that it does not have the 5GMM parameters. 2. The method of claim 1, further comprising:

[0175] Appendix 3 sending an indicator if it is determined that the association has changed. 2. The method of claim 1, further comprising:

[0176] Appendix 4 The indicator is included in the registration request message. 4. A method for a UE according to any one of claims 1 to 3.

[0177] Appendix 5 5GMM parameters are included in the registration accept message. 5. A method for a UE according to any one of Supplementary Notes 1 to 4.

[0178] Appendix 6 1. A method for Access and Mobility Management Function (AMF), the method comprising: receiving an indicator from a user equipment (UE) indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identifier (SUPI) associated with the UE has changed; sending the indicator to a unified data management (UDM) if the indicator is received from the UE; receiving 5GS Mobility Management (5GMM) parameters associated with the UE from the UDM after transmitting the indicator; and transmitting 5GMM parameters to the UE; A method comprising:

[0179] Appendix 7 The indicator received from the UE is included in the registration request message; AMF method described in Appendix 6.

[0180] Appendix 8 The indicator sent to the UDM is included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. AMF method as described in appendix 6 or 7.

[0181] Appendix 9 The 5GMM parameters received from the UDM are included in the Nudm_SDM_GET response message. 9. The AMF method of any one of appendices 6 to 8.

[0182] Appendix 10 The 5GMM parameters sent to the UE are included in the registration accept message. 10. The AMF method of any one of appendices 6 to 9.

[0183] Appendix 11 1. A method of integrated data management (UDM), comprising: receiving an indicator indicating that an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identity (SUPI) associated with a user equipment (UE) has changed; and transmitting 5GS Mobility Management (5GMM) parameters associated with the UE after receiving the indicator; A method comprising:

[0184] Appendix 12 The indicator is included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. The UDM method described in Appendix 11.

[0185] Appendix 13 1. A method for Access and Mobility Management Function (AMF), the method comprising: receiving a registration request message from a user equipment (UE); sending, to a Unified Data Management (UDM) after receiving the registration request message, a Permanent Equipment Identifier (PEI) associated with the UE and an International Mobile Subscriber Identifier (SUPI) associated with the UE; receiving 5GS Mobility Management (5GMM) parameters associated with the UE from the UDM after transmitting the PEI and SUPI; and transmitting 5GMM parameters to the UE; A method comprising:

[0186] Appendix 14 sending the PEI and SUPI if the registration request message includes an indicator that indicates that the association between the PEI and the SUPI has changed; 14. The AMF method of claim 13, further comprising:

[0187] Appendix 15 The PEI and SUPI are included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. 15. The AMF method of claim 13 or 14.

[0188] Appendix 16 The 5GMM parameters received from the UDM are included in the Nudm_SDM_GET response message. 16. The AMF method of any one of appendices 13 to 15.

[0189] Appendix 17 The 5GMM parameters sent to the UE are included in the registration accept message. 17. The AMF method of any one of appendices 13 to 16.

[0190] Appendix 18 1. A method of integrated data management (UDM), comprising: receiving a Permanent Equipment Identifier (PEI) associated with a User Equipment (UE) and an International Mobile Subscriber Identity (SUPI) associated with the UE; and transmitting 5GS Mobility Management (5GMM) parameters associated with the UE after receiving the PEI and SUPI; A method comprising:

[0191] Appendix 19 The PEI and SUPI are included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. The UDM method described in Appendix 18.

[0192] Appendix 20 5GMM parameters are included in the Nudm_SDM_GET response message. 19. The method of UDM described in Appendix 18 or 19.

[0193] Appendix 21 1. A method for Access and Mobility Management Function (AMF), the method comprising: receiving a registration request message from a user equipment (UE); determining whether an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identity (SUPI) associated with the UE has changed; if it is determined that the association has changed, sending an indicator to a unified data manager (UDM) indicating that the association has changed; receiving 5GS Mobility Management (5GMM) parameters associated with the UE from the UDM after transmitting the indicator; and transmitting 5GMM parameters to the UE; A method comprising:

[0194] Appendix 22 determining that the association has changed if the SUPI stored in the AMF is different from the SUPI of the association; 22. The AMF method of claim 21, further comprising:

[0195] Appendix 23 determining that the association has changed if an indicator indicating that the association has changed is received from an Equipment Identification Register (EIR); 22. The AMF method of claim 21, further comprising:

[0196] Appendix 24 1. A method of integrated data management (UDM), comprising: determining whether an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identifier (SUPI) associated with a user equipment (UE) has changed; and transmitting 5GS Mobility Management (5GMM) parameters associated with the UE if it is determined that the association has changed; A method comprising:

[0197] Appendix 25 determining that the association has changed if an indicator indicating that the association has changed is received from an Equipment Identification Register (EIR); 25. The UDM method of claim 24, further comprising:

[0198] Appendix 26 A user equipment (UE), means for transmitting an indicator that indicates that an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identity (SUPI) associated with the UE has changed; and means for receiving 5GS Mobility Management (5GMM) parameters associated with the UE after transmitting the indicator; a user equipment (UE) including:

[0199] Appendix 27 Means for transmitting an indicator when the UE determines that it does not have 5GMM parameters 27. The UE of claim 26, further comprising:

[0200] Appendix 28 A means of sending an indicator when it determines that an association has changed 27. The UE of claim 26, further comprising:

[0201] Appendix 29 The indicator is included in the registration request message. 29. The UE of any one of Supplementary Notes 26 to 28.

[0202] Appendix 30 5GMM parameters are included in the registration accept message. 30. The UE of any one of Supplementary Notes 26 to 29.

[0203] Appendix 31 An Access and Mobility Management Function (AMF), comprising: means for receiving, from a user equipment (UE), an indicator indicating that an association between a permanent equipment identifier (PEI) and an international mobile subscriber identity (SUPI) associated with the UE has changed; means for transmitting an indicator to a unified data management (UDM) upon receiving the indicator from the UE; means for receiving 5GS Mobility Management (5GMM) parameters associated with the UE from the UDM after transmitting the indicator; and Means for transmitting 5GMM parameters to the UE Access and Mobility Management Function (AMF), including:

[0204] Appendix 32 The indicator received from the UE is included in the registration request message; AMF as described in Appendix 31.

[0205] Appendix 33 The indicator sent to the UDM is included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. An AMF as described in Appendix 31 or 32.

[0206] Appendix 34 The 5GMM parameters received from the UDM are included in the Nudm_SDM_GET response message. 34. The AMF of any one of appendices 31 to 33.

[0207] Appendix 35 The 5GMM parameters sent to the UE are included in the registration accept message. 35. The AMF of any one of appendices 31 to 34.

[0208] Appendix 36 An integrated data management (UDM) system comprising: means for receiving an indicator indicating that an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identifier (SUPI) associated with a user equipment (UE) has changed; and means for transmitting 5GS Mobility Management (5GMM) parameters associated with the UE after receiving the indicator; Integrated Data Management (UDM), including:

[0209] Appendix 37 The indicator is included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. UDM as described in Appendix 36.

[0210] Appendix 38 An Access and Mobility Management Function (AMF), comprising: means for receiving a registration request message from a user equipment (UE); means for sending, to a unified data management (UDM) after receiving the registration request message, a permanent equipment identifier (PEI) associated with the UE and an international mobile subscriber identifier (SUPI) associated with the UE; means for receiving 5GS Mobility Management (5GMM) parameters associated with the UE from the UDM after transmitting the PEI and SUPI; and Means for transmitting 5GMM parameters to the UE Access and Mobility Management Function (AMF), including:

[0211] Appendix 39 means for transmitting the PEI and SUPI when the registration request message includes an indicator that indicates that the association between the PEI and the SUPI has changed; 39. The AMF of claim 38, further comprising:

[0212] Appendix 40 The PEI and SUPI are included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. An AMF as described in Appendix 38 or 39.

[0213] Appendix 41 The 5GMM parameters received from the UDM are included in the Nudm_SDM_GET response message. 41. The AMF of any one of appendices 38 to 40.

[0214] Appendix 42 The 5GMM parameters sent to the UE are included in the registration accept message. 42. The AMF of any one of appendices 38 to 41.

[0215] Appendix 43 An integrated data management (UDM) system comprising: means for receiving a Permanent Equipment Identifier (PEI) associated with a User Equipment (UE) and an International Mobile Subscriber Identity (SUPI) associated with the UE; and means for transmitting 5GS Mobility Management (5GMM) parameters associated with the UE after receiving the PEI and SUPI; Integrated Data Management (UDM), including:

[0216] Appendix 44 The PEI and SUPI are included in the Nudm_UECM_Registration message or the Nudm_SDM_GET request message. UDM as described in Appendix 43.

[0217] Appendix 45 5GMM parameters are included in the Nudm_SDM_GET response message. A UDM as described in Appendix 43 or 44.

[0218] Appendix 46 An Access and Mobility Management Function (AMF), comprising: means for receiving a registration request message from a user equipment (UE); means for determining whether an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identity (SUPI) associated with the UE has changed; means for transmitting an indicator to a unified data manager (UDM) indicating that the association has changed if the association has been determined to have changed; means for receiving 5GS Mobility Management (5GMM) parameters associated with the UE from the UDM after transmitting the indicator; and means for transmitting 5GMM parameters to the UE; Access and Mobility Management Function (AMF), including:

[0219] Appendix 47 A means of determining that an association has changed if the SUPI stored in the AMF differs from the SUPI of the association. 47. The AMF of claim 46, further comprising:

[0220] Appendix 48 means for determining that an association has changed when an indicator indicating that the association has changed is received from an Equipment Identification Register (EIR); 48. The AMF of claim 46 or 47, further comprising:

[0221] Appendix 49 An integrated data management (UDM) system comprising: means for determining whether an association between a Permanent Equipment Identifier (PEI) and an International Mobile Subscriber Identity (SUPI) associated with a user equipment (UE) has changed; and means for transmitting 5GS Mobility Management (5GMM) parameters associated with the UE upon determining that the association has changed; Integrated Data Management (UDM), including:

[0222] Appendix 50 means for determining that an association has changed when an indicator indicating that the association has changed is received from an Equipment Identification Register (EIR); 49. The UDM of claim 49, further comprising:

[0223] The whole or part of the exemplary embodiments disclosed above can be described as follows, but are not limited thereto.

[0224] 4.2.2.2 Registration Procedure 4.2.2.2.1 General A UE needs to register with a network to be authorized to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration procedure using one of the following registration types: -Early registration to 5GS; Mobility registration updates when changing to a new Tracking Area (TA) outside the UE's registration area in both the CM-CONNECTED and CM-IDLE states, or when the UE needs to update its capabilities or protocol parameters negotiated in the registration procedure, whether or not changing to a new TA; a change in the UE's preferred network behavior that would result in incompatibility with the supported network behavior provided by the serving AMF; or when the UE attempts to retrieve LADN information; or - Periodic registration renewal (after a predetermined period of inactivity); or - Urgent registration.

[0225] The general registration call flow in Section 4.2.2.2.2 applies to all these registration procedures, but standing registration does not need to include all the parameters used in the other registration cases.

[0226] The following are the plaintext IEs defined in TS 24.501

[25] that may be sent by the UE in a Registration Request message if the UE does not have a NAS security context: -Registration type -SUCI or 5G-GUTI or PEI -security parameters -Additional GUTI -4G tracking area update -Indication that the UE is moving out of the EPS.

[0227] Aspects related to dual registration in 3GPP and non-3GPP access are described in section 4.12. The general Registration call flow in section 4.2.2.2.2 is also used when the UE registers in 3GPP access when it is already registered in non-3GPP access, and vice versa. Registration in 3GPP access when the UE is already registered in a non-3GPP access scenario may require AMF modifications, as further detailed in section 4.12.8.

[0228] The general registration call flow in section 4.2.2.2.2 may also be used by UEs in a limited service state (see TS 23.122

[22] ) that register for emergency services only (referred to as emergency registration) (see TS 23.501 [2] section 5.16.4).

[0229] During initial registration, the PEI is obtained from the UE. If a PEI is required (e.g., for EIR checking), the AMF shall retrieve the PEI when establishing the NAS security context using the Security Mode Command during initial registration. The AMF operator may check the PEI in the EIR. If the PEI is obtained by the AMF (either from the UE or another AMF), the AMF shall provide it to the UDM using Nudm_UECM_Registration to ensure that the UDM always has the latest PEI available for reporting, for example, event SUPI-PEI association changes. The AMF passes the PEI to the UDM, SMF, and PCF. The UDM can store the data in the UDR by Nudr_SDM_Update.

[0230] NOTE 1: The use of NSI ID in 5GC is optional and subject to operator deployment choices.

[0231] During registration, the home network may provide roaming steering information to the UE via the AMF (i.e., a list of preferred PLMN / access technology combinations or an HPLMN indication indicating that no change to the "operator controlled PLMN selector with access technology" list stored in the UE is required). The home network may include an indication to send that the UE acknowledges receipt of that information. Details regarding the roaming steering information, including how it is managed between the AMF and the UE, are defined in TS 23.122

[22] .

[0232] The AMF determines the access type and RAT type as defined in clause 5.3.2.3 of TS 23.501 [2].

[0233] 4.2.2.2.2 General Registration Figure 4.2.2.2.2-1: Registration Procedure (See Figure 11 of this application) 1. UE to (R)AN:AN message (AN parameters, Registration Request (Registration Type, SUCI or 5G-GUTI or PEI, [Last Visited TAI (if available)], Security Parameters, [Requested NSSAI], [Requested NSSAI Mapping], [Default Configured NSSAI Indication], [UE Radio Capability Update], [UE MM Core Network Capabilities], [PDU Session Status], [List of PDU Sessions to be Activated], [Follow-On Request], [MICO Mode Priority], [Requested Active Time], [Requested DRX Parameters for E-UTRA and NR], [Requested DRX Parameters for NB-IoT], [Extended Idle Mode DRX Parameters], [LADN DNN or LADN Information Request Indicator], [NAS Message Container], [Support for Extended Coverage Usage Restrictions], [Preferred Network Behavior], [UE Paging Probability Information], [UE Policy Container (List of PSI, Indication of UE Support for ANDSP and Operating System Identifier)] and [UE Radio Capability ID], PEI.PEI-SUPI Association Change Indicator).

[0234] NOTE 1: The UE Policy Container and its usage are defined in TS 23.503

[20] .

[0235] For NG-RAN, the AN parameters include, for example, the 5G-S-TMSI or GUAMI, the selected PLMN ID (or PLMN ID and NID, see TS 23.501 [2], clause 5.30), and the NSSAI information. The AN parameters also include an establishment cause, which provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the NSSAI information as part of the AN parameters depends on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter, as specified in TS 23.501 [2], clause 5.15.9.

[0236] If the UE is an IAB node accessing 5GS, the AN parameter shall also include an IAB indication.

[0237] The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration procedure due to mobility, or because the UE needs to update its capabilities or protocol parameters, or to request a change in the set of network slices that the UE is authorized to use), a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration procedure due to expiration of the periodic registration update timer, see Section 4.2.2.2.1), or an emergency registration (i.e., the UE is in a limited service state).

[0238] When the UE is using E-UTRA, the UE indicates support for CIoT 5GS optimizations related to AMF selection in the RRC connection establishment signaling associated with the registration request.

[0239] If the UE is performing initial registration, the UE shall indicate the UE identity in the Registration Request message as follows: Listed in order of decreasing priority for registration to a PLMN: i) If the UE has a valid EPS GUTI, the 5G-GUTI mapped from the EPS GUTI. ii) If available, the native 5G-GUTI assigned by the PLMN to which the UE is attempting to register; iii) If available, the native 5G-GUTI assigned by the equivalent PLMN to the PLMN to which the UE is attempting to register; iv) Native 5G-GUTI allocated by any other PLMN, if available. NOTE 2: This may also be a 5G-GUTI allocated via another access type. v) Otherwise, the UE shall include its SUCI in the registration request as defined in TS 33.501

[15] .

[0240] If the UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE shall also indicate the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE shall select the 5G-GUTI in the order of priority from items (ii) to (iv) in the above list.

[0241] When registering with an SNPN of 5G-GUTI as UE identity, the UE shall only use 5G-GUTIs previously assigned by the same SNPN.

[0242] If the UE is sending a Registration Request message as an initial NAS message, the UE has a valid 5G NAS security context, and the UE needs to send non-plaintext IEs, the NAS message container shall be included, see clause 4.4.6 of TS 24.501

[25] . If the UE does not need to send non-plaintext IEs, the UE shall send the Registration Request message without the NAS message container.

[0243] If the UE does not have a valid 5G NAS security context, the UE shall send a registration request message without a NAS message container. The UE shall include the entire registration request message (i.e., including cleartext and non-cleartext IEs) in the NAS message container sent as part of the security mode complete message in step 9b.

[0244] When the UE is performing initial registration with native 5G-GUTI (i.e., the UE is in RM-DEREGISTERED state), the UE shall indicate the relevant GUAMI information in the AN parameters. When the UE is performing initial registration with its SUCI, the UE shall not indicate any GUAMI information in the AN parameters.

[0245] If the UE is performing initial registration or mobility registration and CIoT 5GS optimization is supported, the UE shall indicate its preferred network behavior (see clause 5.31.2 of TS 23.501 [2]). If S1 mode is supported, the preferred network behavior of the UE's EPC shall be included in the S1 UE network capabilities of the registration request message, see clause 8.2.6.1 of TS 24.501

[25] .

[0246] In case of emergency registration, if the UE does not have a valid 5G-GUTI available, the SUCI shall be included. The PEI shall be included if the UE does not have a SUPI and a valid 5G-GUTI. In other cases, the 5G-GUTI is included, which indicates the last serving AMF.

[0247] The UE may provide its usage preferences based on its configuration as defined in TS 23.501 [2] clause 5.16.3.7. The UE provides the requested NSSAI as described in TS 23.501 [2] clause 5.15.5.2.1. In the case of initial registration or mobility registration update, the UE includes a mapping of the requested NSSAI (if available) to the HPLMN S-NSSAI for each S-NSSAI in the requested NSSAI, ensuring that the network can verify whether the S-NSSAI in the requested NSSAI is allowed based on the subscribed S-NSSAI. In the case of inter-PLMN mobility, if the UE does not have a serving PLMN S-NSSAI corresponding to the established PDU session, the associated HPLMN S-NSSAI associated with the established PDU session shall be provided to the requested NSSAI mapping as described in TS 23.501 [2] clause 5.15.5.2.1.

[0248] If the UE is using a default configured NSSAI as defined in TS 23.501 [2], the UE includes a default configured NSSAI indication.

[0249] If the UE supports allocation of WUS assistance information from the AMF, it may include UE paging probability information (see TS 23.501 [2]).

[0250] In case of a mobility registration update, the UE shall include in the list of PDU sessions to be activated PDU sessions for which there is pending uplink data. When the UE includes in the list of PDU sessions to be activated, it shall indicate PDU sessions associated only with the access to which the registration request relates. As defined in TS 24.501

[25] , the UE shall include in the list of PDU sessions to be activated always-on PDU sessions that are accepted by the network even if there is no pending uplink data for those PDU sessions.

[0251] NOTE 3: If the UE is outside the area of ​​availability of the LADN, the PDU session corresponding to the LADN is not included in the list of PDU sessions to be activated.

[0252] The UE MM Core Network Function is provided by the UE and processed by the AMF as defined in clause 5.4.4a of TS 23.501 [2]. The UE includes in the UE MM Core Network Function an indication of whether it supports the request type flag "Handover" in the PDN connection request during the attach procedure as defined in clause 5.17.2.3.1 of TS 23.501 [2]. If the UE supports "Strict Periodic Registration Timer Indication", the UE indicates the capability of "Strict Periodic Registration Timer Indication" in the UE MM Core Network Function. If the UE supports CAG, the UE indicates the capability "CAG Supported" in the UE MM Core Network Function.

[0253] The UE may provide either the LADN DNN or an indication of requesting LADN information as described in clause 5.6.5 of TS 23.501 [2].

[0254] If available, the last visited TAI shall be included to assist the AMF in creating the registration area for the UE.

[0255] The security parameters are used for authentication and integrity protection. See TS 33.501

[15] . The requested NSSAI indicates network slice selection assistance information (as defined in clause 5.15 of TS 23.501 [2]). The PDU session status indicates the previously established PDU session in the UE. If the UE is connected to two AMFs belonging to different PLMNs via 3GPP and non-3GPP accesses, the PDU session status indicates the established PDU session of the current PLMN in the UE.

[0256] A follow-on request is included when the UE has pending uplink signaling and the UE does not include a list of PDU sessions to be activated, or the registration type indicates that the UE wants to perform an emergency registration. During initial registration and mobility registration updates, the UE provides the UE request DRX parameters as defined in clause 5.4.5 of TS 23.501 [2]. To request extended idle mode DRX, the UE can provide the extended idle mode DRX parameters as defined in clause 5.31.7.2 of TS 23.501 [2].

[0257] The UE provides the UE radio capability update indication as described in TS 23.501 [2].

[0258] If the UE wishes to use MICO mode with active time, the UE includes a MICO mode preference and, optionally, a requested active time value.

[0259] The UE can indicate its service gap control capability to the UE MM core network function, see clause 5.31.16 of TS 23.501 [2].

[0260] If the UE has a service gap timer running, the UE shall not set the follow-on required indicator or the uplink data status in the registration request message, except for network access for restricted priority services such as emergency services or exception reporting (see clause 5.31.16 of TS 23.501 [2]).

[0261] If the UE supports RACS and has been assigned a UE Radio Capability ID, the UE shall indicate the UE Radio Capability ID as defined in clause 5.4.4.1a of TS 23.501 [2] as a non-plaintext IE.

[0262] The PEI may be obtained from the UE at initial registration as described in section 4.2.2.2.1.

[0263] 2. If the 5G-S-TMSI or GUAMI is not included, or if the 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN shall select an AMF, if available, based on the (R)AT and the requested NSSAI.

[0264] The (R)AN selects the AMF as described in clause 6.3.5 of TS 23.501 [2]. If the UE is in CM-CONNECTED state, the (R)AN can forward the registration request message to the AMF based on the UE's N2 connection.

[0265] If the (R)AN cannot select a suitable AMF, it forwards the registration request to an AMF configured to perform AMF selection in the (R)AN.

[0266] 3. (R)AN to new AMF: N2 message (N2 parameters, registration request (described in step 1) and [LTE-M indication]).

[0267] If NG-RAN is used, the N2 parameter contains a UE context request indicating that a UE context should be set up in the NG-RAN, including the selected PLMN ID (or PLMN ID and NID, see TS 23.501 [2], clause 5.30), location and cell identity information related to the cell on which the UE is camped, and security information.

[0268] If NG-RAN is used, the N2 parameter shall also contain the establishment cause and IAB indication if an indication was received in the AN parameter in step 1.

[0269] Mapping of the requested NSSAI will be provided only if available.

[0270] If the registration type indicated by the UE is periodic registration update, steps 4 to 19 may be omitted.

[0271] If the establishment cause is associated with a priority service (e.g., MPS, MCS), the AMF includes a priority header in the message to indicate the priority information. Other NFs relay the priority information by including a priority header in the message in their service-based interfaces, as specified in TS 29.500

[17] .

[0272] The RAT type used by the UE is determined (see section 4.2.2.2.1) and based on that the AMF decides whether the UE is performing inter-RAT mobility to or from NB-IoT. If the AMF receives an LTE-M indication, the RAT type is considered to be LTE-M and stores the LTE-M indication in the UE context.

[0273] When a UE includes a preferred network behavior, this defines the network behavior that the UE supports and expects to be available in the network as defined in clause 5.31.2 of TS 23.501 [2].

[0274] If the UE includes a preferred network behavior and what the UE indicates it supports in its preferred network behavior is not compatible with the network support, the AMF shall reject the registration request with an appropriate cause value (e.g., one that avoids retries in that PLMN).

[0275] If a service gap timer is running in the UE context in the AMF of the UE and the registration request message contains a follow-on request indication or an uplink data status, the AMF shall ignore the follow-on request indication and the uplink data status and shall not perform any of the actions related to the status.

[0276] If the UE includes the UE radio capability ID in step 1 and the AMF supports RACS, the AMF stores the radio capability ID in the UE context.

[0277] For NR satellite access, if the AMF can determine, based on the selected PLMN ID and ULI (including cell ID) received from the gNB, that the UE is attempting to register with a PLMN that is not authorized to operate with the current UE location, the AMF SHOULD reject the registration request indicating an appropriate cause value and, if known to the AMF, the country of the UE's location. Otherwise, for example, if the AMF does not know the UE location with sufficient accuracy to make a final decision, the AMF may proceed with the registration procedure, initiate the UE location procedure as specified in clause 6.10.1 of TS 23.273

[51] , and prepare for UE deregistration if the information received from the LMF establishes that the UE is registered with a PLMN that is not authorized to operate with the UE location.

[0278] NOTE 4: It cannot be guaranteed that the location information is accurate enough for the AMF to determine in all cases the country in which the UE is located.

[0279] NOTE 5: Because some countries use multiple MCCs and some MCCs, such as 901, may be allowed in multiple countries, the UE may register with a PLMN with a different MCC than the one returned to the UE.

[0280] If the UE receives a registration rejection for the country in which it is located, the UE shall attempt to register with a PLMN that is authorized to operate in UE location as specified in TS 23.122

[22] .

[0281] 4. [Conditional] From new AMF to old AMF: Namf_Communication_UEContextTransfer (Registration request completed), or from new AMF to UDSF: Nudsf_Unstructured Data Management_Query().

[0282] (For UDSF deployment): If the UE's 5G-GUTI is included in the registration request, the serving AMF has changed since the last registration procedure, the new AMF and the old AMF are in the same AMF set, and UDSF is deployed, the new AMF can either obtain the stored UE's SUPI and UE context directly from the UDSF using the Nudsf_UnstructuredDataManagement_Query service operation, or share the stored UE context via implementation-specific means if UDSF is not deployed. This also includes event subscription information by each NF consumer for the given UE. In this case, the new AMF performs and verifies integrity protection using the integrity-protected complete registration request NAS message.

[0283] (Without UDSF deployment): If the UE's 5G-GUTI is included in the registration request and the serving AMF has changed since the last registration procedure, the new AMF can request the UE's SUPI and UE context by invoking the Namf_Communication_UEContextTransfer service operation of the old AMF, including the complete, integrity-protected registration request NAS message and the access type. For details about the operation of this service, see Section 5.2.2.2.2. In this case, if the context transfer service operation call corresponds to the requested UE, the old AMF uses either the 5G-GUTI and the integrity-protected complete registration request NAS message, or an indication that the SUPI and the UE have been verified from the new AMF to verify the integrity protection. The old AMF also forwards the event subscription information by each NF consumer for the UE to the new AMF. If the old AMF has not yet reported a non-zero MO exception data counter to the (H-)SMF, the context response also includes the MO exception data counter.

[0284] If the old AMF has a PDU session with a different access type (different from the access type indicated in this step) and the old AMF determines that there is no possibility of relocating the N2 interface to the new AMF, the old AMF returns the UE's SUPI, indicating that the registration request has been validated for integrity protection, but does not include the remainder of the UE context.

[0285] In case of inter-PLMN mobility, the UE context information includes the HPLMN S-NSSAI corresponding to the allowed NSSAI for each access type, without the allowed NSSAI of the old PLMN.

[0286] NOTE 6: The new AMF sets an indication that the UE is verified according to step 9a if the new AMF successfully authenticates the UE after a previous integrity check failure in the old AMF.

[0287] NOTE 7: After the UE has successfully registered with the new AMF, the NF consumer does not need to re-subscribe to events in the new AMF.

[0288] If the new AMF has already received the UE context from the old AMF during the handover procedure, steps 4, 5 and 10 shall be skipped.

[0289] In case of emergency registration, if the UE identifies itself with a 5G-GUTI that is not known to the AMF, steps 4 and 5 are skipped and the AMF immediately requests a SUPI from the UE. If the UE identifies itself with a PEI, the SUPI request shall be skipped. Allowing emergency registration without user identity depends on local regulations.

[0290] 5. [Conditional] Response to Namf_Communication_UEContextTransfer from old AMF to new AMF (SUPI, UE context in AMF (according to Table 5.2.2.2.2-1)) or Nudsf_Unstructured Data Management_Query() from UDSF to new AMF. The old AMF may start an implementation-specific (guard) timer for the UE context.

[0291] If the UDSF was queried in step 4, the UDSF responds to the new AMF for a Nudsf_Unstructured Data Management_Query call with the relevant context including the established PDU session, the old AMF includes the SMF information DNN, S-NSSAI, and PDU session ID, the active NGAP UE-TNLA binding to the N3IWF / TNGF / W-AGF, and the old AMF includes information about the NGAP UE-TNLA binding.If the old AMF was queried in step 4, the old AMF responds to the new AMF for a Nudsf_Communication_UEContextTransfer call by including the UE's SUPI and UE context.

[0292] If the old AMF holds information about the established PDU session and it is not an initial registration, the old AMF includes SMF information, DNN, S-NSSAI, and PDU session ID.

[0293] If the old AMF holds the UE context established via N3IWF, W-AGF, or TNGF, the old AMF includes the CM state via N3IWF, W-AGF, or TNGF. If the UE is in the CM-CONNECTED state via N3IWF, W-AGF, or TNGF, the old AMF includes information about the NGAP UE-TNLA binding.

[0294] If the old AMF fails the integrity check of the registration request NAS message, the old AMF shall indicate the integrity check failure. If the new AMF is configured to allow emergency services for unauthenticated UEs, the new AMF shall operate as follows: If the UE only has an emergency PDU session, the AMF skips the authentication and security procedures or accepts that authentication may fail and continues with the mobility registration update procedure; or If the UE has both emergency and non-emergency PDU sessions and authentication fails, the AMF continues the mobility registration update procedure and deactivates all non-emergency PDU sessions as specified in clause 4.3.4.2.

[0295] NOTE 8: The new AMF can determine whether a PDU session is used for emergency services by checking whether the DNN matches the emergency DNN.

[0296] If the old AMF holds information about AM policy associations and information about UE policy associations (i.e., policy control request triggers for updating UE policies as defined in TS 23.503

[20] ), the old AMF contains information about AM policy associations, UE policy associations, and PCF IDs. In roaming cases, this includes V-PCF IDs and H-PCF IDs.

[0297] If the old AMF was a consumer of the UE-related NWDAF service, the old AMF includes information about the active analysis subscription, i.e., the NWDAF identifier (i.e., instance ID or set ID), and associated analysis-specific data (i.e., analyst ID, analyst filter information, target of analyst report, analyst report information) in the Namf_Communication_UEContextTransfer response.

[0298] Editor's note: Whether the old AMF includes analytics subscription binding details and how the new AMF uses them is up to FFS.

[0299] Editor's note: The mechanism for whether and how a new AMF initiates a new analytical subscription using the NWDAF ID received from the old AMF or a new NWDAF ID, as well as if the new AMF is not within the NWDAF's service area, is FFS.

[0300] During inter-PLMN mobility, the handling of the UE radio capability ID in the new AMF is as defined in TS 23.501 [2].

[0301] NOTE 9: If the new AMF uses UDSF for context lookup, the interaction between the old AMF, the new AMF and the UDSF due to the UE signaling in the old AMF at the same time is an implementation issue.

[0302] 6. [Conditional] New AMF to UE:Identity Request().

[0303] If the SUCI is not provided by the UE and is not obtained from the old AMF, the identity request procedure is initiated by the AMF sending an identity request message to the UE requesting the SUCI.

[0304] 7. [Conditional] New AMF:Identity Response() from UE.

[0305] The UE responds with an Identity Response message containing the SUCI, which the UE derives using the HPLMN's provisioned public key as specified in TS 33.501

[15] .

[0306] 8. The AMF may decide to initiate UE authentication by invoking the AUSF, in which case the AMF selects the AUSF based on the SUPI or SUCI as described in clause 6.3.4 of TS 23.501 [2].

[0307] If the AMF is configured to support emergency registration for unauthenticated SUPI and the UE indicates registration type emergency registration, the AMF skips authentication or the AMF accepts that authentication may fail and continues with the registration procedure.

[0308] 9a. If authentication is required, the AMF requests it from the AUSF. If the trace requirements for the UE are available in the AMF, the AMF provides the trace requirements to the AUSF in the request. Upon request from the AMF, the AUSF shall perform authentication of the UE. Authentication is performed as described in TS 33.501

[15] . The AUSF selects a UDM as described in clause 6.3.8 of TS 23.501 [2] and obtains authentication data from the UDM.

[0309] Once the UE is authenticated, the AUSF provides the relevant security-related information to the AMF. If the AMF provides the AUSF with a SUPI, the AUSF shall return the SUPI to the AMF only after successful authentication.

[0310] After successful authentication in the new AMF, triggered by a failed integrity check in the old AMF in step 5, the new AMF invokes step 4 above again and indicates that the UE has been verified (i.e., via the reason parameter specified in clause 5.2.2.2.2).

[0311] 9b If no NAS security context exists, NAS security initiation is performed as described in TS 33.501

[15] . If the UE did not have a NAS security context in step 1, the UE includes a complete Registration Request message as defined in TS 24.501

[25] .

[0312] The AMF determines whether the registration request needs to be rerouted as described in section 4.2.2.2.3, where the initial AMF refers to the AMF.

[0313] 9c. If the 5G-AN has requested a UE context, the AMF shall initiate an NGAP procedure to provide the 5G-AN with the security context specified in TS 38.413

[10] . If the AMF determines that EPS fallback is supported (e.g., based on the UE capability to support the request type flag "Handover" for the PDN connection request during the attach procedure defined in clause 5.17.2.3.1 of TS 23.501 [2], subscription data, and local policies), the AMF shall send an indication "Redirection for EPS fallback for voice is possible" towards the 5G-AN as specified in TS 38.413

[10] . Otherwise, the AMF shall indicate "Redirection for EPS fallback for voice is not possible." Furthermore, if the tracing requirements for the UE are available in the AMF, the AMF shall provide the tracing requirements to the 5G-AN in the NGAP procedure.

[0314] 9d. The 5G-AN stores the security context and authorization in the AMF. The 5G-AN uses the security context to protect messages exchanged with the UE as described in TS 33.501

[15] .

[0315] 10. [Conditional] New AMF to old AMF: Namf_Communication_RegistrationStatusUpdate (PDU Session ID released due to unsupported slicing).

[0316] When the AMF is changed, the new AMF notifies the old AMF that the UE's registration to the new AMF is complete by calling the Namf_Communication_RegistrationStatusUpdate service operation.

[0317] If the authentication / security procedures fail, the registration shall be rejected and the new AMF shall call the Namf_Communication_RegistrationStatusUpdate service operation with a rejection indication to the old AMF. The old AMF shall continue as if the UE context transfer service operation had not been received.

[0318] If one or more of the S-NSSAIs used in the old registration area cannot be served in the target registration area, the new AMF determines which PDU sessions cannot be supported in the new registration area. The new AMF invokes the Namf_Communication_RegistrationStatusUpdate service operation with the rejected PDU session IDs for the old AMF. The new AMF then changes the PDU session status accordingly. The old AMF notifies the corresponding SMF to locally release the UE's SM context by invoking the Nsmf_PDUSession_ReleaseSMContext service operation.

[0319] If the new AMF received in the UE context in step 2 forwards information about the AM policy association and the UE policy association, and decides based on the local policy not to use the PCFs identified by the PCF IDs of the AM policy association and the UE policy association, it notifies the old AMF that the AM policy association and the UE policy association in the UE context are no longer in use, and then PCF selection is performed in step 15.

[0320] If the old AMF used the UE related analysis NWDAF service, it is now possible to unsubscribe the UE from the NWDAF service according to TS 23.288

[50] .

[0321] 11. [Conditional] New AMF to UE: Identity Request / Response (PEI).

[0322] If the PEI is not provided by the UE and has not been retrieved from the old AMF, the identity request procedure is initiated by the AMF, which sends an identity request message to the UE to retrieve the PEI. The PEI shall be transferred encrypted unless the UE performs an emergency registration and cannot be authenticated.

[0323] In case of emergency registration, the UE may include the PEI in the registration request, in which case the PEI lookup is skipped.

[0324] If the UE supports RACS as indicated in the UE MM Core Network Capabilities, the AMF shall use the UE's PEI to obtain the IMEI / TAC for the purpose of RACS operation.

[0325] 12. Optionally, the new AMF initiates an ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation (see Section 5.2.4.2.2).

[0326] The PEI check is performed as described in Section 4.7.

[0327] In the case of emergency registration, if the PEI is blocked, operator policy determines whether the emergency registration procedure continues or is stopped.

[0328] 13. If step 14 is to be performed, the new AMF selects a UDM based on the SUPI, and then the UDM can select a UDR instance. See section 6.3.9 of TS 23.501 [2].

[0329] The AMF selects the UDM as described in clause 6.3.8 of TS 23.501 [2].

[0330] 14a-c. If the AMF has changed since the last registration procedure, or if the UE has provided a SUPI that does not reference a valid context in the AMF, or if the UE has registered with the same AMF that is already registered for non-3GPP access (i.e., the UE is registered via non-3GPP access and initiates this registration procedure to add 3GPP access), the new AMF registers with the UDM using Nudm_UECM_Registration for the access to which it is registered (and subscribes to be notified when the UDM deregisters this AMF). The AMF includes a SUPI-PEI association change indicator in Nudm_UECM_Registration. In this case, if the AMF does not have event publication subscription information for this UE, the AMF indicates this to the UDM. Then, if the UDM has existing applicable event publication subscriptions (possibly retrieved from the UDR) for events detected in the AMF for this UE or for any of the groups to which this UE belongs, the UDM calls the Namf_EventExposure_Subscribe service to recreate the event publication subscriptions. Upon receiving the SUPI-PEI association change indicator, the UDM may provide subscription information (eg, CAG information) for the SUPI in a Nudm_UECM_Registration response message.

[0331] The AMF shall provide the "Uniform support of IMS Voice over PS sessions" indication (see clause 5.16.3.3 of TS 23.501 [2]) to the UDM. The "Uniform support of IMS Voice over PS sessions" indication shall not be included unless the AMF has completed its evaluation of support for "IMS Voice over PS sessions" as specified in clause 5.16.3.2 of TS 23.501 [2].

[0332] During initial registration, if the AMF and UE support SRVCC from NG-RAN to UTRAN, the AMF provides the UE SRVCC capability to the UDM.

[0333] If the AMF determines that only the UE SRVCC capability has changed, the AMF sends the UE SRVCC capability to the UDM.

[0334] NOTE 10: At this step, the AMF may not have all the information necessary to determine the configuration of the IMS Voice over PS Session Support indication for this UE (see clause 5.16.3.2 of TS 23.501 [2]). Therefore, the AMF may send "Uniform support for IMS Voice over PS Sessions" later in this procedure.

[0335] If the AMF does not have the UE's subscription data, it uses Nudm_SDM_Get to obtain the access and mobility subscription data, SMF selection subscription data, the UE context in the SMF data, and LCS mobile origination. If the AMF already has the UE's subscription data but the SoR update indicator in the UE context requires the AMF to obtain SoR information depending on the NAS registration type ('initial registration' or 'emergency registration') (see Annex C of TS 23.122

[22] ), the AMF uses Nudm_SDM_Get to obtain roaming steering information. This requires that the UDM can obtain this information from the UDR by Nudr_DM_Query. After a successful response is received, the AMF subscribes to be notified using Nudm_SDM_Subscribe when the requested data is modified, and the UDM can subscribe to the UDR by Nudr_DM_Subscribe. If GPSI is available in the UE subscription data, the GPSI is provided to the AMF in the access and mobility subscription data from the UDM. The UDM may provide an indication that the subscription data for network slicing is updated for the UE. If the UE subscribes to an MPS in the serving PLMN, the "MPS priority" is included in the access and mobility subscription data provided to the AMF. If the UE subscribes to an MCX in the serving PLMN, the "MCX priority" is included in the access and mobility subscription data provided to the AMF. The UDM also provides an IAB operation allowed indication to the AMF as part of the access and mobility subscription data. The AMF shall trigger the setup of the UE context in the NG-RAN, or, if the initial setup is in step 9c, a change of the UE context in the NG-RAN, including an indication that the IAB node is allowed. When the AMF receives the PEI-SUPI association change indicator, the AMF may include the PEI-SUPI association change indicator in a Nudm_SDM_Get message and send it to the UDM.When the UDM receives a PEI-SUPI association change indicator in either a Nudm_UECM_Registration message or a Nudm_SDM_GET message, the UDM includes the UE subscription information (e.g., CAG information) AMF.

[0336] The new AMF provides the UDM with the access type to serve the UE, and the access type is set to "3GPP access". The UDM stores the associated access type together with the serving AMF and does not delete the AMF identification information associated with the other access type, if any. The UDM can store the information provided at the time of AMF registration by Nudr_DM_Update in the UDR.

[0337] If the UE is registered to the old AMF for access and the old AMF and new AMF are in the same PLMN, the new AMF sends a separate / independent Nudm_UECM_Registration to update the UDM with the access type configured for the access used by the old AMF after the relocation of the old AMF is successfully completed. The new AMF creates a UE context for the UE after obtaining the access and mobility subscription data from the UDM. The access and mobility subscription data includes whether the UE is authorized to include NSSAI in the 3GPP access RRC connection establishment in clear text. The access and mobility subscription data may include extended coverage restriction information. If the UDM and data received from the UE in step 1 included support for extended coverage usage restriction, the AMF determines whether extended coverage is restricted for the UE as specified in clause 5.31.12 of TS 23.501 [2] and stores the updated extended coverage restriction information in the UE context.

[0338] The access and mobility subscription data may include NB-IoT UE priority.

[0339] The subscription data may include a service gap time parameter. If received from the UDM, the AMF stores this service gap time in the UE context within the AMF for the UE.

[0340] In the case of emergency registration where the UE is not successfully authenticated, the AMF shall not register with the UDM.

[0341] The AMF shall enforce mobility restrictions as specified in clause 5.3.4.1.1 of TS 23.501 [2]. In case of emergency registration, the AMF shall not check mobility restrictions, access restrictions, regional restrictions or subscription restrictions. In case of emergency registration, the AMF shall ignore any failure in the registration response from the UDM and continue with the registration procedure.

[0342] NOTE 11: If the corresponding feature is supported by both the AMF and the UDM, the AMF can use the Nudm_SDM_Subscribe service operation with an immediate report indication instead of the Nudm_SDM_Get service operation to trigger the UDM to return the subscribed data immediately.

[0343] 14d. Once the UDM stores the associated access type (e.g., 3GPP) with the serving AMF as indicated in step 14a, if an old AMF exists corresponding to the same (e.g., 3GPP) access, it causes the UDM to initiate a Nudm_UECM_DeregistrationNotification (see Section 5.2.3.2.2). If the timer started in step 5 is not running, the old AMF may delete the UE context of the same access type. Otherwise, the AMF may delete the UE context of the same access type when the timer expires. If the serving NF removal reason indicated by the UDM is initial registration, the old AMF shall invoke the Nsmf_PDUSession_ReleaseSMContext(SM Context ID) service operation to all associated SMFs of the UE to notify them that the UE has been deregistered from the old AMF for the same access type, as described in Section 4.2.2.3.2. The SMF shall release the PDU session upon obtaining this notification.

[0344] If the old AMF established an AM policy association and a UE policy association with a PCF and the old AMF did not transfer the PCF ID to the new AMF (for example, the new AMF is in a different PLMN), the old AMF performs the AMF-initiated policy association termination procedure defined in subclause 4.16.3.2 and the AMF-initiated UE policy association termination procedure defined in subclause 4.16.13.1. In addition, if the old AMF transferred the PCF ID of the UE context but the new AMF notified in step 10 that the AM policy association information and UE policy association information in the UE context will not be used, the old AMF performs the AMF-initiated policy association termination procedure as defined in subclause 4.16.3.2 and the AMF-initiated UE policy association termination procedure as defined in subclause 4.16.13.1.

[0345] If the old AMF has an N2 connection for the UE (e.g. because the UE was in RRC inactive state but has now moved to E-UTRAN or moved to an area not served by the old AMF), the old AMF shall perform an AN release (see section 4.2.6) with a cause value indicating that the UE has already locally released the RRC connection in the NG-RAN.

[0346] At the end of the registration procedure, if the AMF does not indicate unavailability of the event publishing subscription in step 14a, the AMF can start synchronizing the event publishing subscription with the UDM.

[0347] NOTE 12: The AMF may initiate synchronization with the UDM even if the event is available in the UE context (e.g., received from the old AMF) based on local policy at any given time. This may be done during subscription change related events.

[0348] 14e. [Conditional] If the old AMF does not have a UE context of another access type (i.e., non-3GPP access), the old AMF unsubscribes in UDM for subscription data using Nudm_SDM_unsubscribe.

[0349] 15. If the AMF decides to initiate PCF communication, the AMF operates as follows:

[0350] If the new AMF decides to use the (V-)PCF identified by the (V-)PCF ID included in the UE context from the old AMF in step 5, the AMF contacts the (V-)PCF identified by the (V-)PCF ID to obtain the policy. If the AMF decides to perform PCF discovery and selection and the AMF selects a (V)-PCF, it can select an H-PCF (for roaming scenarios) as described in clause 6.3.7.1 of TS 23.501 [2] and according to the V-NRF to H-NRF interaction described in clause 4.3.2.2.3.3.

[0351] 16. [Optional] The new AMF performs AM Policy Association Establishment / Modification. In case of emergency registration, this step is skipped.

[0352] If the new AMF selects a new (V-)PCF in step 15, the new AMF performs AM policy association establishment with the selected (V-)PCF as defined in clause 4.16.1.2.

[0353] If the (V-)PCF identified by the (V-)PCF ID included in the UE context from the old AMF is used, the new AMF performs the AM policy association change using the (V-)PCF defined in section 4.16.2.1.2.

[0354] When the AMF notifies the PCF of mobility restrictions (e.g., UE location) for adjustment, or when the PCF updates the mobility restrictions itself due to some conditions (e.g., application in use, date and time), the PCF shall provide the updated mobility restrictions to the AMF. If the subscription information includes trace requirements, the AMF shall provide the trace requirements to the PCF.

[0355] If the AMF supports DNN substitution, the AMF provides the PCF with the allowed NSSAI and, if available, the mapping of the allowed NSSAI.

[0356] If the PCF supports DNN substitution, the PCF provides a trigger for DNN substitution to the AMF.

[0357] 17. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext().

[0358] For an urgently registered UE (see TS 23.501 [2]), this step applies if the registration type is a mobility registration update.

[0359] AMF calls Nsmf_PDUSession_UpdateSMContext (see Section 5.2.8.2.6) in the following scenarios: If the registration request in step 1 includes a list of PDU sessions to be activated, the AMF sends an Nsmf_PDUSession_UpdateSMContext Request to the SMF associated with the PDU sessions to activate the user plane connections for these PDU sessions. Steps 5 and following steps described in subclause 4.2.3.2 are performed to complete the user plane connection activation without sending RRC inactive support information and without sending an MM NAS service accept from the AMF to the (R)AN described in step 12 of subclause 4.2.3.2. Once the user plane connection for the PDU session is activated, the AS layer of the UE indicates it to the NAS layer. - If in step 3 the AMF determines that the UE is performing inter-RAT mobility to or from NB-IoT, the AMF sends an Nsmf_PDUSession_UpdateSMContext Request to the SMF associated with the UE PDU sessions so that the SMF can update them according to the subscription data for "PDU session continuity in inter-RAT mobility". The steps from step 5 described in subclause 4.2.3.2 are performed without sending an MM NAS service accept from the AMF to the (R)AN described in step 12 of subclause 4.2.3.2.

[0360] When the serving AMF changes, the new serving AMF informs the SMF for each PDU session that it assumes responsibility for the signaling path to the UE: the new serving AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using the SMF information received from the old AMF in step 5. It also indicates whether the PDU session should be reactivated.

[0361] NOTE 13: When a UE moves to a different PLMN, the AMF in the serving PLMN may insert or change the V-SMF in the serving PLMN for the home routed PDU session. In this case, the same procedures as for an I-SMF change (i.e., by replacing an I-SMF with a V-SMF) apply for the V-SMF change as described in subclause 4.23.3. If the same SMF is used during an inter-PLMN change, session continuity may be supported depending on the operator's policy.

[0362] The steps from step 5 onwards described in section 4.2.3.2 are performed. If an insertion, removal or modification of an Intermediate UPF is performed for a PDU session that is not included in the "PDU sessions to be reactivated", the procedure is performed without interaction of N11 and N2 to update the N3 user plane between the (R)AN and the 5GC.

[0363] AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation to SMF in the following scenarios: -If any PDU session status indicates that it is released in the UE, the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF to release any network resources associated with the PDU session.

[0364] If the serving AMF has changed, the new AMF shall wait until step 18 has been completed for all SMFs associated with the UE. Otherwise, steps 19 to 22 may continue in parallel with this step.

[0365] 18. [Conditional] If the new AMF and the old AMF are in the same PLMN, the new AMF sends a UE context modification request to the N3IWF / TNGF / W-AGF as specified in TS 29.413

[64] .

[0366] When the AMF is changed and the old AMF indicates that the UE is in CM-CONNECTED state via an N3IWF, W-AGF, or TNGF, and the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association towards the N3IWF / TNGF / W-AGF to which the UE is connected, which automatically releases the existing NGAP UE association between the old AMF and the N3IWF / TNGF / W-AGF.

[0367] 19. N3IWF / TNGF / W-AGF sends UE context modification response to new AMF.

[0368] 19a. [Conditional] After the new AMF receives a response message from the N3IWF, W-AGF, or TNGF in step 19, the new AMF registers with the UDM using Nudm_UECM_Registration as step 14a, but with the access type set to "non-3GPP access". The UDM stores the associated access type with the serving AMF and does not delete the AMF identification information associated with the other access type, if any. The UDM may store the information provided during AMF registration in the UDR by Nudr_DM_Update.

[0369] 19b. [Conditional] Once the UDM stores the associated access type (i.e., non-3GPP) with the serving AMF as shown in step 19a, it causes the UDM to initiate a Nudm_UECM_DeregistrationNotification (see section 5.2.3.2.2) to the old AMF corresponding to the same (i.e., non-3GPP) access. The old AMF deletes the UE context for the non-3GPP access.

[0370] 19c. The old AMF unsubscribes from UDM for subscription data using Nudm_SDM_unsubscribe.

[0371] 20a. Invalid

[0372] 21. New AMF to UE: Registration Acceptance (5G-GUTI, Registration Area, [Mobility Restrictions], [PDU Session Status], [Allowed NSSAI], [Allowed NSSAI Mapping], [Configured NSSAI for Serving PLMN], [Configured NSSAI Mapping], [Rejected S-NSSAI], [Pending NSSAI], [Pending NSSAI Mapping], [Periodic Registration Update Timer], [Active Time], [Strictly Periodic Registration Timer Indicator], [LADN Information], [Accepted MICO Mode], [IMS Voice over PS Session Support Indicator], [Emergency Services Support Indicator], [Accepted D for E-UTRA and NR 5G-S-TMSI Configuration]).

[0373] If the requested NSSAI does not contain an S-NSSAI that maps to an S-NSSAI of the HPLMN that is subject to network slice specific authentication and authorization, and the AMF determines that it cannot provide an S-NSSAI for the UE's authorized NSSAI in the current UE's tracking area and cannot further consider a default S-NSSAI that has not yet been involved in the current UE registration procedure, the AMF shall reject the UE registration and include in the rejection message a list of rejected S-NSSAIs, each of which shall have an appropriate rejection cause value.

[0374] The allowed NSSAIs for the UE's access type are included in the N2 message carrying the registration accept message. The allowed NSSAIs include only S-NSSAIs that do not require network slice-specific authentication and authorization based on subscription information, and S-NSSAIs for which network slice-specific authentication and authorization have previously been successful, regardless of access type, based on the UE context in the AMF. The mapping of pending NSSAIs is the mapping of each S-NSSAI of the pending NSSAIs for the serving PLMN to the HPLMN S-NSSAI.

[0375] If the UE indicates support for network slice-specific authentication and authorization procedures in the UE MM core network function in the registration request, the AMF includes in the subscription information an S-NSSAI that maps to the S-NSSAI of the HPLMN that has an indication of undergoing network slice-specific authentication and authorization as described in clause 4.6.2.4 of TS 24.501

[25] . In such a case, the AMF shall trigger the network slice-specific authentication and authorization procedures specified in clause 4.2.9.2 in step 25 based on the network policy, except for S-NSSAIs for which network slice-specific authentication and authorization has already been initiated with another access type of the same S-NSSAI. The UE shall not attempt to re-register with an S-NSSAI included in the list of pending NSSAIs until the network slice-specific authentication and authorization procedures are completed, regardless of the access type.

[0376] If the UE does not indicate support for network slice-specific authentication and authorization procedures in the UE 5GMM core network function in the registration request and the requested NSSAI contains S-NSSAIs that map to HPLMN S-NSSAIs subject to network slice-specific authentication and authorization, the AMF shall include those S-NSSAIs in the requested NSSAIs within the rejected S-NSSAI.

[0377] If you are unable to provide the S-NSSAI to the authorized NSSAI, -All S-NSSAIs within the requested NSSAI should be subject to network slice-specific authentication and authorization; or - If a requested NSSAI was not provided or none of the S-NSSAIs in the requested NSSAI matches any of the subscribed S-NSSAIs, all S-NSSAIs marked as default within the subscribed S-NSSAIs are subject to network slice-specific authentication and authorization.

[0378] The AMF shall provide an empty Authorized NSSAI. Upon receiving the empty Authorized NSSAI and any pending NSSAIs, the UE shall register with the PLMN but shall await completion of network slice specific authentication and authorization procedures without attempting to use any services offered by the PLMN with any access except, for example, emergency services (see TS 24.501

[25] ) until the UE receives the Authorized NSSAI.

[0379] The AMF stores the NB-IoT priority obtained in step 14 and associates it with the 5G-S-TMSI assigned to the UE.

[0380] The AMF sends a registration accept message to the UE indicating that the registration request has been accepted. If the AMF assigns a new 5G-GUTI, the 5G-GUTI is included. Upon receiving a registration request message of type "Initial Registration" or "Mobility Registration Update" from the UE, the AMF shall include the new 5G-GUTI in the registration accept message. Upon receiving a registration request message of type "Periodic Registration Update" from the UE, the AMF shall include the new 5G-GUTI in the registration accept message. If the UE is already in RM-REGISTERED state via another access of the same PLMN, the UE shall use the 5G-GUTI received in the registration accept for both registrations. If the registration accept does not include a 5G-GUTI, the UE shall use the 5G-GUTI assigned to the existing registration for the new registration as well. If the AMF assigns a new registration area, the AMF shall send the registration area to the UE via the registration accept message. If no registration area is included in the registration accept message, the UE shall consider the old registration area to be valid. If mobility restrictions apply to the UE and the registration type is not emergency registration, the mobility restrictions are included. The AMF indicates the established PDU session to the UE in the PDU session status. The UE locally deletes any internal resources related to the PDU session that are not marked as established in the received PDU session status. If the AMF invokes the Nsmf_PDUSession_UpdateSMContext procedure for UP activation of the PDU session in step 18 and receives a rejection from the SMF, the AMF indicates to the UE the PDU session ID and the reason why the user plane resources were not activated. When a UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally deletes any internal resources related to the PDU session of the current PLMN that are not marked as established in the received PDU session status. If the PDU session status information was in the registration request, the AMF shall indicate the PDU session status to the UE.

[0381] If the RAT type is NB-IoT and the network is configured to use the control plane relocation indication procedure, the AMF shall include in the registration accept message a truncated 5G-S-TMSI configuration that a UE using control plane CIoT 5GS optimization will use to create a truncated 5G-S-TMSI, see clause 5.31.4.3 of TS 23.501 [2].

[0382] The Allowed NSSAIs provided in the registration acceptance are valid in the registration area and apply to all PLMNs with tracking areas contained in the registration area. The Allowed NSSAI mapping is the mapping of each S-NSSAI of the Allowed NSSAI to the HPLMN S-NSSAI. The Configured NSSAI mapping is the mapping of each S-NSSAI of the Configured NSSAI for the Serving PLMN to the HPLMN S-NSSAI.

[0383] The AMF shall include in the registration accept message the LADN information from the list of LADNs described in clause 5.6.5 of TS 23.501 [2] that are available within the registration area determined by the AMF for the UE. The AMF may include operator-defined access category definitions as described in TS 24.501

[25] to allow the UE to determine the applicable operator-defined access category definitions.

[0384] If the UE includes MICO mode in the registration request, the AMF responds with a registration accept message indicating whether MICO mode should be used. If MICO mode is permitted for the UE, the AMF may include an active time value and / or a strict periodic registration timer indication in the registration accept message. The AMF determines the periodic registration update timer value, active time value, and strict periodic registration timer indication based on local configuration, expected UE behavior if available, UE indicated priorities, UE capabilities, UE subscription information, and network policies, or any combination thereof, to enable UE power saving, as described in clause 5.31.7 of TS 23.501 [2]. If the UE indicates the capability of strict periodic registration timer indication in the registration request message, as described in step 1, the AMF determines to apply the strict periodic registration timer indication to the UE. If the AMF provides the strict periodic registration timer indication to the UE in the periodic registration update timer value, the UE and the AMF start the periodic registration update timer after this step, as described in clause 5.31.7.5 of TS 23.501 [2].

[0385] In case of registration via 3GPP access, the AMF sets the IMS Voice over PS Session Supported Indication as described in clause 5.16.3.2 of TS 23.501 [2]. To set the IMS Voice over PS Session Supported Indication, the AMF may need to perform the UE Capability Match Request procedure of clause 4.2.8a to check the UE compatibility and the NG-RAN radio capabilities related to IMS Voice over PS. If the AMF does not receive the Voice Support Match Indicator from the NG-RAN on time, the AMF may set the IMS Voice over PS Session Supported Indication and update it at a later stage based on the implementation.

[0386] In case of registration over non-3GPP access, the AMF sets the IMS Voice over PS Session Supported Indication as described in clause 5.16.3.2a of TS 23.501 [2].

[0387] The Emergency Service Support Indicator informs the UE that emergency services are supported, i.e., the UE is authorized to request emergency service PDU sessions. Based on operator policy, if the "MPS Priority" AMF is received from the UDM as part of the access and mobility subscription data, the "MPS Priority" is included in the registration accept message to the UE to inform the UE whether the configuration of Access Identity 1 is valid within the selected PLMN, as specified in TS 24.501

[25] . Based on operator policy and the UE subscription to MCX services, if the "MCX Priority" AMF is received from the UDM as part of the access and mobility subscription data, the "MCX Priority" is included in the registration accept message to the UE to inform the UE whether the configuration of Access Identity 2 is valid within the selected PLMN, as specified in TS 24.501

[25] . The accepted DRX parameters are defined in clause 5.4.5 of TS 23.501 [2]. If the UE included requested DRX parameters for NB-IoT in the registration request message, the AMF includes the accepted DRX parameters for NB-IoT. The AMF configures network support for interworking without N26 parameters as described in clause 5.17.2.3.1 of TS 23.501 [2]. If the AMF accepts the use of extended idle mode DRX, the AMF includes the extended idle mode DRX parameters and paging time window as described in clause 5.31.7.2 of TS 23.501 [2].

[0388] A network slicing subscription change indication is included if the UDM is intended to indicate to the UE that a subscription has changed. If the AMF includes a network slicing subscription change indication, the UE shall locally clear all network slicing configurations for all PLMNs and, if applicable, update the current PLMN configuration based on any received information.

[0389] As specified in clause 5.15.9 of TS 23.501 [2], the access stratum connection establishment NSSAI inclusion mode is included to instruct the UE which NSSAI, if any, to include in the access stratum connection establishment. The AMF can set values ​​for operation modes a, b, and c defined in clause 5.15.9 of TS 23.501 [2] for 3GPP access only if they indicate that the inclusion of NSSAI in the RRC connection establishment is allowed.

[0390] For a UE registered in a PLMN, the AMF may provide a list of equivalent PLMNs, which shall be processed as specified in TS 24.501

[25] . For a UE registered in an SNPN, the AMF shall not provide a list of equivalent PLMNs to the UE.

[0391] If the UE included support for extended coverage usage restrictions in step 1, the AMF sends the extended coverage restriction information to the NG-RAN in the N2 message. The AMF also sends the extended coverage restriction information to the UE in the registration accept message.

[0392] If the UE receives the extended coverage restriction information in the registration accept message, the UE shall store this information and use the value of the extended coverage restriction information to determine whether to use the extended coverage feature.

[0393] If the UE and the AMF negotiate to enable MICO mode and the AMF uses the extended connection timer, the AMF provides the extended connection time value to the NG-RAN in this step (see clause 5.31.7.3 of TS 23.501 [2]). The extended connection time value indicates the minimum time that the RAN should keep the UE in RRC-CONNECTED state regardless of inactivity.

[0394] The AMF indicates the CIoT 5GS optimizations it supports and accepts in the supported network behavior information (see TS 23.501 [2], section 5.31.2) if the UE includes the preferred network behavior in its registration request.

[0395] The AMF can steer the UE out of 5GC by rejecting the registration request. The AMF should take into account the preferred and supported network behavior (see TS 23.501 [2], clause 5.31.2) and the availability of EPC to the UE before steering the UE out of 5GC.

[0396] If the AMF accepts the MICO mode and knows that there may be mobile terminated data or signaling pending, the AMF shall maintain the N2 connection for at least the extended connection time as described in clause 5.31.7.3 of TS 23.501 [2] and provide the extended connection time value to the RAN.

[0397] The AMF includes the service gap time if it is present in the subscription information (steps 14a-c) or if the service gap time is updated by the Subscriber Data Update Notification procedure to the AMF (see section 4.5.1) and the UE indicates UE Service Gap Control capability.

[0398] If the UE receives a service gap time in the registration accept message, the UE shall store this parameter and apply the service gap control (see clause 5.31.16 of TS 23.501 [2]).

[0399] If the network supports WUS grouping (see TS 23.501 [2]), the AMF shall send WUS assistance information to the UE. If the UE provided UE paging probability information in step 1, the AMF shall take this into consideration when determining the WUS assistance information.

[0400] If the UE and AMF support RACS as defined in clause 5.4.4.1a of TS 23.501 [2], the AMF must configure the UE with a UE radio capability ID, and the AMF already has UE radio capabilities other than the NB-IoT radio capability of the UE, the AMF can provide the UE with the UE radio capability ID, which the AMF returns to the AMF in the Nucmf_assign service operation for this UE. Alternatively, if the UE and AMF support RACS, the AMF can provide the UE with an indication to delete any PLMN-assigned UE radio capability IDs within this PLMN (see clause 5.4.4.1a of TS 23.501 [2]).

[0401] If the UE is "CAG-supporting" and the AMF needs to update the UE's CAG information, the AMF may include the CAG information as part of the mobility restriction in the registration accept message.

[0402] 21b. [Optional] The new AMF performs UE policy association establishment as defined in clause 4.16.11. In case of emergency registration, this step is skipped.

[0403] The new AMF sends an Npcf_UEPolicyControl Create Request to the PCF. The PCF sends an Npcf_UEPolicyControl Create Response to the new AMF.

[0404] The PCF triggers the UE configuration update procedure as defined in section 4.2.4.3.

[0405] 22. [Conditional] New AMF:Registration Complete() from UE.

[0406] If the UE successfully updates itself after receiving the [Configured NSSAI for Serving PLMN], [Configured NSSAI Mapping], and either the network slicing subscription change indication or CAG information in step 21, it sends a registration complete message to the AMF.

[0407] The UE sends a registration complete message to the AMF to acknowledge that a new 5G-GUTI has been assigned.

[0408] If a new 5G-GUTI is assigned, the UE passes the new 5G-GUTI to the lower layers of its 3GPP access (either 3GPP access or non-3GPP access) when the lower layers indicate to the UE's RM layer that a registration complete message has been successfully transferred over the air interface.

[0409] NOTE 14: This is necessary because the NG-RAN can use the RRC inactive state and part of the 5G-GUTI is used to calculate paging frames (see TS 38.304

[44] and TS 36.304

[43] ). It is assumed that the registration complete is delivered reliably to the AMF after the 5G-AN acknowledges its receipt to the UE.

[0410] If the list of PDU sessions to be activated is not included in the registration request and the registration procedure was not started in the CM-CONNECTED state, the AMF shall release the signaling connection with the UE according to clause 4.2.6.

[0411] If a follow-on request is included in the registration request, the AMF should not release the signaling connection after the completion of the registration procedure.

[0412] If the AMF is aware that some signaling is pending within the AMF or between the UE and the 5GC, the AMF should not release the signaling connection immediately after the registration procedure is completed.

[0413] If the PLMN-assigned UE radio capability ID is included in step 21, the AMF stores the PLMN-assigned UE radio capability ID in the UE context upon receiving the registration complete message.

[0414] If the UE receives the PLMN assigned UE radio capability ID removal indication in step 21, the UE shall remove the PLMN assigned UE radio capability ID for this PLMN.

[0415] 23. [Conditional] If the access and mobility subscription data provided by the UDM to the AMF in AMF to UDM:14b contains roaming steering information accompanied by an indication of a request that the UDM acknowledges receiving this information from the UE, the AMF provides the UDM with an acknowledgement of the UE's receipt using Nudm_SDM_Info. For further details on handling of roaming steering information, see TS 23.122

[22] .

[0416] 23a. In the case of registration on 3GPP access, if the AMF does not release the signaling connection, the AMF sends RRC inactive support information to the NG-RAN.

[0417] For registration on non-3GPP access, if the UE is also in CM-CONNECTED state in 3GPP access, the AMF sends RRC inactive support information to the NG-RAN.

[0418] The AMF also uses the Nudm_SDM_Info service operation to provide an acknowledgement to the UDM that the UE has received and acted upon the CAG information or network slicing subscription change indication (see steps 21 and 22).

[0419] 24. [Conditional] AMF to UDM: After step 14a, in parallel with any of the previous steps, the AMF shall send the "Uniform support for IMS Voice over PS sessions" indication to the UDM using Nudm_UECM_Update: - If the AMF has assessed support for IMS Voice over PS sessions, please refer to clause 5.16.3.2 of TS 23.501 [2]; If the AMF determines that uniform support for IMS voice over PS sessions needs to be updated, refer to clause 5.16.3.3 of TS 23.501 [2].

[0420] 25. [Conditional] If the UE indicates support for network slice-specific authentication and authorization procedures in the UE MM Core Network Function in the Registration Request and any S-NSSAI in the HPLMN undergoes network slice-specific authentication and authorization, the relevant procedures are performed in this step (see Section 4.2.9.1). Once the network slice-specific authentication and authorization procedures are completed for all S-NSSAIs, the AMF shall trigger the UE Configuration Update procedure and deliver the allowed NSSAIs, including the S-NSSAIs for which network slice-specific authentication and authorization were successful, and any rejected NSSAIs with an appropriate rejection cause value.

[0421] If the tracking area of ​​the registration area was previously assigned as a non-authorized area for pending network slice-specific authentication and authorization, the AMF shall lift the mobility restriction.

[0422] The AMF stores an indication in the UE context for any S-NSSAI of the HPLMN that follows network slice-specific authentication and authorization where the network slice-specific authentication and authorization is successful.

[0423] Upon completion of the network slice specific authentication and authorization procedures, if the AMF determines that it cannot provide an S-NSSAI for the authorized NSSAI of a UE that has already been authenticated and successfully authorized by the PLMN, and if no default S-NSSAI can be further considered, the AMF shall perform the network-initiated deregistration procedure described in clause 4.2.2.3.3 and shall include in the explicit deregistration request message a list of rejected S-NSSAIs, each of them with an appropriate rejection cause value.

[0424] While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, the invention is not limited to these embodiments, and those skilled in the art will recognize that various changes in form and detail can be made therein without departing from the spirit and scope of the invention as defined by the claims.

[0425] This application claims the benefit of priority to Indian Provisional Patent Application No. 202111016593, filed on April 8, 2021, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0426] 1 USIM 2 ME 3UE 5 (R)AN nodes 10 AMF 11 AUSF 15 UDM 16 EIR 31 Transceiver Circuit 32 Antenna 33 Control Unit 34 User Interface 35 USIM 36 memory 51 Transceiver circuit 52 Antenna 53 Network Interface 54 Control Unit 55 memory 101 Transceiver Circuit 102 Network Interface 103 Control Unit 104 memory 151 Transceiver Circuit 152 network interfaces 153 Control Unit 154 memory 161 Transceiver Circuit 162 network interfaces 163 Control Unit 164 memory 361 Operating Systems 362 Communication Control Module 551 Operating Systems 552 Communication Control Module 1041 Operating Systems 1042 Communication Control Module 1541 Operating Systems 1542 Communication Control Module 1641 Operating Systems 1642 Communication Control Module 3621 Transceiver Control Module 5521 Transceiver Control Module 10421 Transceiver Control Module 15421 Transceiver Control Module 16421 Transceiver Control Module< / eir> < / udm> < / amf>

Claims

1. maintaining information for a Permanent Equipment Identifier (PEI) for a User Equipment (UE); Send information to an Access and Mobility Management Function (AMF) to cause the UE to transmit Single Network Slice Selection Assistance Information (S-NSSAI) based on the information for the PEI, depending on whether the UE supports a registration procedure for a specific network slice; A method for the Unified Data Management Function (UDM).

2. receiving first information about a User Equipment (UE) from a Unified Data Management Function (UDM) based on information for a Permanent Equipment Identifier (PEI); Based on the first information, sending a Single Network Slice Selection Assistance Information (S-NSSAI) to the UE depending on whether the registration procedure for a specific network slice is supported; A method for an Access and Mobility Management Function (AMF).

3. means for maintaining information for a Permanent Equipment Identifier (PEI) for a User Equipment (UE); A means for transmitting information to an Access and Mobility Management Function (AMF) to cause the UE to transmit Single Network Slice Selection Assistance Information (S-NSSAI) based on the information for the PEI, depending on whether the UE supports a registration procedure for a specific network slice; A Unified Data Management Function (UDM) is provided.

4. means for receiving first information about a User Equipment (UE) from a Unified Data Management Function (UDM) based on information for a Permanent Equipment Identifier (PEI); A means for sending Single Network Slice Selection Assistance Information (S-NSSAI) to the UE based on the first information, depending on whether the UE supports a registration procedure for a specific network slice; An AMF (Access and Mobility Management Function).

Images