Method for configuring network identifier in user equipment mobile scenario and user equipment

Abstract

A method for supporting enhanced NID configuration in UE mobility scenarios between different types of networks is proposed. When the UE registers to a SNPN, the SNPN allocates a 5G‑GUTI to the UE. The SNPN is identified by SNPN ID == PLMN ID + NID. When the UE moves from the SNPN to another target network with a target AMF, the UE triggers a mobile registration update procedure and provides 5G‑GUTI and NID information to the target AMF in the registration request. The target AMF can use the NID information and 5G‑GUTI to find the source AMF for obtaining the UE context for subsequent operations during the mobile registration update procedure. Providing NID information together with the 5G‑GUTI can help the target AMF find the source AMF efficiently and prevent potential registration process failures.

Description

[0001] Cross-references

[0002] The present invention claims the following priority: U.S. Provisional Patent Application No. 63 / 139,827, filed on January 21, 2021, and entitled “NID Provisioning under UE Mobility Scenarios” and U.S. Patent Application No. 17 / 558,298, filed on December 21, 2021, and the above-mentioned U.S. patent documents are hereby incorporated by reference. Technical Field

[0003] Embodiments of the present invention generally relate to wireless mobile communication networks, and more particularly, to a method for provisioning a network identifier (NID) in a user equipment (UE) mobile scenario. Background Art

[0004] A Public Land Mobile Network (PLMN) is a network established and operated by an administration or recognized operating agency (ROA) with the specific purpose of providing land mobile communication services to the public. PLMN provides the possibility of communication for mobile users. PLMN can provide services in one frequency band or a combination of frequency bands. Access to PLMN services is achieved through an air interface that involves radio communications between mobile phones and base stations with integrated IP network services. A PLMN may include multiple radio access networks (RAN) that use different radio access technologies (RAT) to access mobile services. A radio access network is part of a mobile communication system that implements radio access technology. Conceptually, RAN resides between mobile devices and provides a connection to its core network (CN). According to the standards, mobile phones and other wireless connection devices are referred to as UE, terminal equipment, mobile stations (MS), etc. Examples of different RATs include 2nd Generation (2G) GERAN (Global System For Mobile Communications, GSM) radio access network, 3rd Generation (3G) universal terrestrial radio access network (UTRAN) (Universal Mobile Telecommunications System (UMTS)) radio access network, 4th Generation (4G) evolved universal terrestrial radio access network (E-UTRAN) (Long-Term Evolution (LTE)), 5th Generation (5G) New Radio (NR) radio access network, and other non-3rd Generation Partnership Project (3GPP) wireless access networks including Wireless Fidelity (WiFi). rd generation partner project, 3GPP) access RAT.

[0005] Compared with PLMN, non-public network (NPN) is a 5G system (5GS) network deployed for non-public purposes. NPN can be a standalone non-public network (SNPN), that is, it is operated by an NPN operator and does not rely on the network functions provided by PLMN; NPN can also be a public network integrated NPN (NPI-NPN), that is, a non-public network deployed with the support of PLMN. The combination of PLMN ID and NID identifies SNPN. NID information refers to the entire NID value or a partial NID value (for example, the first digit of the NID value). The UE can be enabled for SNPN. The UE selects a SNPN configured with a user identifier and credentials. The UE can have multiple sets of subscriber identifiers, credentials, and SNPN identifiers.

[0006] When the UE moves within a PLMN or between PLMNs, the UE triggers the mobile registration update procedure and provides the target access and mobility management function (AMF) of the target PLMN with a 5G Global Unique Temporary Identifier (5G-GUTI) to help the target AMF find the correct source AMF for obtaining the UE context in subsequent procedures. However, the UE can move between different types of networks. For example, the UE can move within a PLMN, within a SNPN, between a PLMN and a SNPN, between two different PLMNs, between two different SNPNs, or between a PLMN and a SNPN. If the provided 5G-GUTI is allocated by the SNPN, the target AMF of the target network may not be able to find the correct source AMF because the information from the provided 5G-GUTI is not (globally) unique and may result in finding the wrong source AMF, and ultimately the mobile registration update procedure may enter an unexpected abnormal situation or fail. Therefore, the UE then needs to initiate an initial registration procedure.

[0007] The existing registration process needs to be improved to address the above issues. Summary of the invention

[0008] A method for supporting enhanced NID configuration in UE mobility scenarios between different types of networks is proposed. When the UE registers to a SNPN, the SNPN allocates a 5G-GUTI to the UE. The SNPN is identified by SNPN ID == PLMN ID + NID. When the UE moves from the SNPN to another target network with a target AMF, the UE triggers a mobile registration update procedure and provides 5G-GUTI and NID information to the target AMF in the registration request. The target AMF can use the NID information and 5G-GUTI to find the source AMF for obtaining the UE context for subsequent operations during the mobile registration update procedure. Providing NID information together with the 5G-GUTI can help the target AMF find the source AMF efficiently and prevent potential registration process failures.

[0009] In one embodiment, the UE registers to the SNPN. The SNPN is identified by the PLMN ID and the NID. The SNPN allocates the 5G-GUTI to the UE. The UE triggers the mobile registration update procedure and sends a registration request to the target AMF of the target network. The registration request includes the 5G-GUTI and NID information of the SNPN. The UE performs the mobile registration update procedure to the target network.

[0010] In another embodiment, a network entity (target AMF) receives a registration request from a UE in a target network. The registration request triggers a mobile registration update process. The target AMF receives 5G-GUTI and NID information of the source network. The source network is an SNPN identified by a PLMNID and a NID. The target AMF determines the source AMF using the received 5G-GUTI and NID information. The target AMF performs a mobile registration update process for the UE. The target AMF obtains UE context information from the source AMF.

[0011] The NID configuration method in the UE mobile scenario proposed by the present invention can prevent the mobile registration update process from entering an unexpected abnormal situation, and prevent the mobile registration update process from failing and then requiring the initial registration process to be initiated.

[0012] Other embodiments and advantages are described in the detailed description that follows. This summary is not intended to define the invention. The invention is defined by the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings depict embodiments of the present invention, wherein like numerals refer to like parts.

[0014] Figure 1 A communication system with a PLMN and a SNPN according to novel aspects is schematically described, supporting enhanced NID configuration in a UE mobility scenario.

[0015] Figure 2A simplified block diagram of a UE and network entities according to an embodiment of the present invention is described.

[0016] Figure 3A The concept of 5G-GUTI and examples of 5G-GUTI allocation by PLMN and SNPN are described.

[0017] Figure 3B Examples of NID allocation based on different allocation modes are described.

[0018] Figure 4 A mobile registration update procedure for a UE with enhanced NID configuration moving from a source AMF to a target AMF according to novel aspects is described.

[0019] Figure 5 It is a flow chart of a method for supporting enhanced NID configuration in a UE mobility scenario between different types of networks from a UE perspective according to novel aspects.

[0020] Figure 6 It is a flow chart of a method for supporting enhanced NID configuration in a UE mobility scenario between different types of networks from a network perspective according to novel aspects. DETAILED DESCRIPTION

[0021] Reference will now be made in detail to some embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

[0022] Figure 1 A communication system 100 with a PLMN 110 and a SNPN 120 is schematically described according to novel aspects, supporting enhanced NID configuration in UE mobility scenarios. The PLMN 110 includes a control plane function, a user plane function (UPF), and an application server for providing various services by communicating with multiple UEs including a UE 111. The UE 111 and its serving base station gNB 112 are part of a radio access network RAN ​​130. The RAN 130 provides wireless access, such as 3GPP access and non-3GPP access, to the UE 111 via a RAT. The AMF in the PLMN 110 communicates with the gNB 112 and other network functions (not shown) in the PLMN 110, such as a Session Management Function (SMF), an Authentication Server Function (AUSF), etc.

[0023] Similarly, SNPN 120 includes control plane functions, UPFs, and application servers that provide various services by communicating with multiple UEs including UE 121. The combination of PLMN ID and NID identifies the SNPN. UE 121 and its serving base station gNB 122 are part of the radio access network RAN ​​140. RAN 140 provides wireless access to UE 121 via RAT, such as 3GPP access and non-3GPP access. The AMF in SNPN 120 communicates with gNB 122 and other network functions (not shown) in SNPN 120, such as SMF, AUSF, etc. UE 111 / UE 121 can be configured with a radio frequency (RF) transceiver or multiple RF transceivers for different application services via different RATs.

[0024] When the UE moves within a PLMN or between PLMNs, the UE triggers the mobile registration update procedure and provides the 5G-GUTI to the target AMF of the target PLMN to help the target AMF find the correct source AMF for obtaining the UE context in subsequent procedures. However, the UE can move between different types of networks. For example, the UE can move within a PLMN, within a SNPN, between a PLMN and a SNPN, between two different PLMNs, and between two different SNPNs. If the provided 5G-GUTI is allocated by the SNPN, it may not be a globally unique number. Therefore, the target AMF of the target network may not be able to find the correct source AMF because the information from the non-unique 5G-GUTI provided may result in finding the wrong source AMF. Therefore, the mobile registration update procedure may enter an unexpected abnormal situation or fail. The UE then needs to initiate an initial registration procedure to the target AMF.

[0025] According to one novel aspect, a method for enhancing NID configuration is proposed to handle different UE mobility scenarios. When the UE registers to the SNPN, the SNPN allocates a 5G-GUTI to the UE. The SNPN is identified by the SNPN ID == PLMN ID + NID. When the UE moves from the SNPN to another target network with a target AMF, the UE triggers a mobile registration update procedure and provides the 5G-GUTI to the target AMF. For example, UE 121 moves from SNPN 120 to PLMN 110. Since the UE knows the SNPN ID when the UE registers to the SNPN, the UE knows that the 5G-GUTI allocated by the SNPN may not be globally unique. Therefore, if the UE knows that the 5G-GUTI is allocated by the SNPN, the existing mobile registration update procedure can be enhanced to allow the UE to provide 5G-GUTI and NID information. After receiving the 5G-GUTI and NID information provided by the UE, the target AMF can decide whether to initiate an identification request / response procedure based on the NID allocation mode. If the NID is a self-assigned value, the value of the PLMN ID+NID (of the 5G-GUTI) may not be (globally) unique. Therefore, the target AMF may need to request the UE to provide the UE Subscription Concealed Identifier (SUCI) / Subscription Permanent Identifier (SUPI) for subsequent procedures. If the NID is a coordinated assigned value, the value of the PLMN ID+NID (of the 5G-GUTI) is (globally) unique. Therefore, the target AMF can use this information together with the 5G-GUTI to find the correct source AMF. Figure 1 In the example of FIG1 , when UE 121 moves from SNPN 120 to PLMN 110, UE 121 triggers a mobile registration update procedure and provides a target AMF in PLMN 110 with 5G-GUTI and NID information, because UE 121 knows that 5G-GUTI is allocated by SNPN 120 and may not be unique. NID information can help the target AMF efficiently find the source AMF in SNPN 120, preventing potential registration process failure.

[0026] Figure 2A simplified block diagram of a wireless device (e.g., UE 201 and network entity 211) according to an embodiment of the present invention is described. The network entity 211 can be a base station combined with an MME / AMF. The network entity 211 has an antenna 215, which sends and receives radio signals. The RF transceiver 214 is coupled to the antenna 215, receives RF signals from the antenna 215, converts them to baseband signals, and sends them to the processor 213. The RF transceiver 214 also converts the baseband signals received from the processor 213, converts them to RF signals, and sends them to the antenna 215. The processor 213 processes the received baseband signals and calls different functional modules to perform functions in the network entity 211. The memory 212 stores program instructions and data 220 to control the operation of the network entity 211. In Figure 2 In the example of , the network entity 211 also includes a set of control function modules and circuits 290. The registration processing circuit 231 handles the registration and mobility process. The session management circuit 232 handles the session management function. The configuration and control circuit 233 provides different parameters for configuring and controlling the UE. The protocol stack 280 includes a NAS layer for communicating with the MME / AMF entity connected to the core network, a Radio Resource Control (RRC) layer for higher-layer configuration and control, a Packet Data Convergence Protocol / Radio Link Control (PDCP / RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer.

[0027] Similarly, UE 201 has a memory 202, a processor 203, and an RF transceiver 204. The RF transceiver 204 is coupled to an antenna 205, receives RF signals from the antenna 205, converts them to baseband signals, and sends them to the processor 203. The RF transceiver 204 also converts the baseband signals received from the processor 203, converts them to RF signals, and sends them to the antenna 205. The processor 203 processes the received baseband signals and calls different functional modules and circuits to perform functions in the UE 201. The memory 202 stores program instructions and data 210 to control the operation of the UE 201 by the processor. The memory 202 also includes a SIM / USIM 225. Suitable processors include, for example, special purpose processors, digital signal processors (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) circuits and other types of integrated circuits (IC) and / or state machines. The features of UE 201 can be implemented and configured using a processor associated with software.

[0028] UE 201 also includes a set of functional modules and control circuits that perform the functional tasks of UE 201. The protocol stack 260 includes a NAS layer for communicating with the MME / AMF entity of the core network, an RRC layer for higher-level configuration and control, a PDCP / RLC layer, a MAC layer, and a PHY layer. The system modules and circuits 270 can be implemented and configured by hardware, firmware, software, and any combination thereof. When the processor executes the functional modules and circuits through program instructions in the memory, they cooperate with each other to enable UE 201 to execute implementation plans and functional tasks and features in the network. In one example, the system modules and circuits 270 include a registration processing circuit 221 for performing registration with the network, a mobile processing circuit 222 for performing mobile management, and a configuration and control circuit 223 for processing configuration and control parameters.

[0029] Figure 3AThe concept of 5G-GUTI and examples of 5G-GUTI allocation by PLMN and SNPN are described. The temporary user identity 5G-GUTI based on 5GS services is used for identification in signaling procedures. When a registration request message of type "initial registration" or "mobile registration update" is received from the UE, the AMF sends a new 5G-GUTI to the UE in the registration accept message. When a registration request message of type "periodic registration update" is received from the UE, the AMF sends a new 5G-GUTI to the UE in the registration accept message. When a network-triggered service request message is received from the UE, the AMF sends a new 5G-GUTI to the UE using the UE configuration update procedure. The 5G-GUTI has two main components: the Global Unique AMF Identifier (GUAMI) and the 5G Temporary Mobile Subscriber Identifier (5G-TMSI), which provides unambiguous identification of the UE within the AMF identified by the GUAMI. The GUAMI also includes two network identifiers: PLMN ID and AMF ID. The PLMN ID includes the mobile country code (MCC) and the mobile network code (MNC).

[0030] For a PLMN, the allocated 5G-GUTI is globally unique. When the UE moves between PLMNs, the UE provides the 5G-GUTI to the target AMF in the registration request. The target AMF obtains the GUAMI information from the provided 5G-GUTI to find the source AMF that allocated the 5G-GUTI to the UE. Figure 3AAs shown, the GUAMI 310 contains the MCC, MNC, and AMF identifiers. The MCC and MNC constitute the PLMNID 320, which is typically unique when assigned by the PLMN. Therefore, the target AMF can use the unique GUAMI to find the source AMF for retrieving the UE context. For SNPNs, the PLMN ID of the SNPN in the 5G-GUTI is unique within the SNPN, but may not be globally unique when assigned by the SNPN. Since the PLMN ID 320 of the SNPN ID (composed of the PLMN ID and the NID) may not be globally unique (for example, the MCC 330 may be assigned as 999 by any SNPN), the target AMF may not be able to find the source AMF using the GUAMI obtained using the 5G-GUTI assigned by the SNPN. The mobile registration update process may fail. Therefore, when the UE moves from an SNPN to another network, the UE provides the 5G-GUTI and NID to the target AMF in the registration request. The target AMF obtains the GUAMI information from the provided 5G-GUTI using the provided NID to find the source AMF that allocated the 5G-GUTI to the UE.

[0031] Figure 3B Examples of NID allocation based on different allocation modes are described. Figure 3B As shown, NID 350 includes an allocation mode, NID PEN and NID code. The NID value can be determined according to different allocation modes specified in TS23.003. For example, if the allocation mode is set to 0, it means that the NID is assigned as globally unique, regardless of the PLMN ID of the SNPN. In another example, if the allocation mode is set to 2, it means that the NID is assigned as globally unique by a combination of the NID and the PLMN ID. Please note that the NID information here refers to the entire NID value or a partial NID value (for example, the first bit of the NID value). Providing NID information together with 5G-GUTI can help the target AMF find the source AMF efficiently and prevent potential registration process failures. The target AMF can use the NID information together with the 5G-GUTI to find the source AMF in order to obtain the UE context for subsequent operations during the mobile registration update process.

[0032] Figure 4A mobile registration update procedure is described for a UE 401 with an enhanced NID configuration moving from a source AMF 404 to a target AMF 403 according to novel aspects. The NG RAN 402 is responsible for transmitting the registration request of the UE 401 to the target AMF 403. In step 411, the UE 401 performs an initial registration in the source network (e.g., a SNPN with a source AMF 404). The UE needs to register with the network to obtain authorization to receive services, enable mobile tracking, and enable reachability. The UE initiates the registration procedure using one of the following registration types: initial registration to 5GS; mobile registration update when switching to a new tracking area (TA) outside the UE's registration area or when the UE needs to update its performance or protocol parameters; periodic registration update (due to a predefined period of inactivity); or emergency registration; or disaster registration; or SNPN onboarding registration.

[0033] When sending the initial registration request to the source AMF 404, the UE 401 is assigned a 5G-GUTI by the SNPN, which may not be a globally unique number. The source SNPN may be identified by an SNPN ID, which includes a PLMN ID and an NID. Later, the UE 401 moves to a target network with a target AMF 403. The target network may be another SNPN or PLMN. In step 421, the UE 401 triggers a mobile registration update procedure or other NAS procedure. If the 5G-GUTI is assigned by the source network SNPN, the UE 401 may determine that its 5G-GUTI may not be unique. In response, the UE 401 provides the 5G-GUTI and the NID information of the source network to the target network during the registration process or other NAS processes using existing NAS messages or new NAS messages. In one example, the UE 401 sends a registration request to the target AMF 403. The Registration Request includes the Registration Type (e.g., Mobile Registration Update); SUCI or 5G-GUTI or PEI; Security Parameters; Additional GUTI; 4G Tracking Area Update; Indication that the UE has moved from EPS; PLMN with disaster conditions. If the UE is registering with an SNPN, the Registration Request also includes the NID of the SNPN that assigned the 5G-GUTI.

[0034] In step 422, the target AMF 403 receives the registration request, obtains the information of GUAMI from the received 5G-GUTI, and finds the source AMF 404 accordingly. NID information may also be provided in the registration request. If the NID is a self-defined value (i.e., the value specified in TS23.003 is set to 1), the value of PLMN ID+NID (of 5G-GUTI) may not be (globally) unique. Therefore, the target AMF 403 may need to request UE 401 to provide UE SUCI / SUPI for subsequent procedures. If the NID is a coordinated assigned value, the value of PLMN ID+NID (of 5G-GUTI) is (globally) unique. Therefore, the target AMF 403 can use this information together with the 5G-GUTI to find the correct source AMF. When the correct source AMF 404 is found, in step 431, the target AMF 403 sends a request (Namf_Communication_UEContext_Request) message to the source AMF 404 to request the UE context information of the UE 401. In step 432, the source AMF 404 sends a response message (Namf_Communication_UEContext_Response) back to the target AMF 403 to provide the UE context information. In step 441, a mobile registration update procedure is performed between the UE 401 and other network entities. In step 442, the target AMF 403 sends a registration accept message to the UE 401 to complete the registration update.

[0035] Figure 5 It is a flow chart of a method for supporting enhanced NID configuration in a UE mobility scenario between different types of networks from the perspective of the UE according to novel aspects. In step 501, the UE registers to the SNPN. The SNPN is identified by the PLMN ID and the NID. In step 502, the UE determines that the SNPN allocates a 5G-GUTI to the UE. In step 503, the UE triggers a mobile registration update procedure and sends a registration request to a target AMF of the target network. The registration request includes the 5G-GUTI and NID information of the SNPN. In step 504, the UE performs a mobile registration update procedure to the target network.

[0036] Figure 6It is a flow chart of a method for supporting enhanced NID configuration in UE mobility scenarios between different types of networks from a network perspective according to novel aspects. In step 601, the network entity (target AMF) receives a registration request from the UE in the target network. The registration request triggers a mobile registration update process. In step 602, the target AMF receives 5G-GUTI and NID information of the source network. The source network is an SNPN identified by a PLMNID and a NID. In step 603, the target AMF determines the source AMF using the received 5G-GUTI and NID information. In step 604, the target AMF performs a mobile registration update process for the UE. The target AMF obtains UE context information from the source AMF.

[0037] Although the present invention has been described in conjunction with certain specific embodiments for instructional purposes, it is not limited thereto. Accordingly, various modifications, adaptations and combinations of the various features of the described embodiments may be effected without departing from the scope of the present invention as set forth in the claims.

Claims

1. A method for configuring a network identifier in a user equipment mobile scenario, characterized in that: include: The user equipment registers with an independent non-public network, the independent non-public network being identified by a public land mobile network identifier and a network identifier; determining whether a fifth-generation globally unique temporary identifier is allocated by the independent non-public network; triggering a mobile registration update procedure by sending a registration request to a target access and mobility function of a target network, wherein the registration request includes the fifth generation globally unique temporary identifier and network identifier information of the independent non-public network, wherein when the user equipment determines that the fifth generation globally unique temporary identifier is allocated by the independent non-public network, the registration request includes the network identifier information; as well as The mobile registration update procedure to the target network is performed.

2. The method for configuring a network identifier in a user equipment mobile scenario according to claim 1, characterized in that: The network identifier information refers to the entire network identifier value or a partial network identifier value of the independent non-public network.

3. The method for configuring a network identifier in a user equipment mobile scenario according to claim 1, characterized in that: The fifth generation globally unique temporary identifier comprises a globally unique access and mobility function identifier and a fifth generation temporary mobile subscriber identifier, wherein the globally unique access and mobility function identifier further comprises a public land mobile network identifier and an access and mobility function identifier.

4. The method for configuring a network identifier in a user equipment mobile scenario according to claim 3, characterized in that: The public land mobile network identifier further comprises a mobile country code and a mobile network code, wherein the mobile country code is not globally unique when assigned by the independent non-public network.

5. The method for configuring a network identifier in a user equipment mobile scenario according to claim 1, characterized in that: Both the fifth generation globally unique temporary identifier and the network identifier information are used to find a source access and mobility function of the independent non-public network that assigned the fifth generation globally unique temporary identifier to the user equipment.

6. A user equipment for configuring a network identifier in a user equipment mobile scenario, comprising: a registration processing circuit to register the user equipment with an independent non-public network, the independent non-public network being identified by a public land mobile network identifier and a network identifier; Configuration and control circuitry to determine whether a fifth generation globally unique temporary identifier is assigned by the independent non-public network; a radio frequency transceiver, sending a registration request to a target access and mobility function of a target network, wherein the registration request includes the fifth-generation globally unique temporary identifier and network identifier information of the independent non-public network, wherein when the user equipment determines that the fifth-generation globally unique temporary identifier is allocated by the independent non-public network, the registration request includes the network identifier information; The mobile processing circuit performs a mobile registration update process to the target network.

7. The user equipment according to claim 6, characterized in that The network identifier information refers to the entire network identifier value or a partial network identifier value of the independent non-public network.

8. The user equipment according to claim 6, characterized in that The fifth generation globally unique temporary identifier comprises a globally unique access and mobility function identifier and a fifth generation temporary mobile subscriber identifier, wherein the globally unique access and mobility function identifier further comprises a public land mobile network identifier and an access and mobility function identifier.

9. The user equipment according to claim 8, characterized in that The public land mobile network identifier further comprises a mobile country code and a mobile network code, wherein the mobile country code is not globally unique when assigned by the independent non-public network.

10. The user equipment according to claim 6, characterized in that Both the fifth generation globally unique temporary identifier and the network identifier information are used to find a source access and mobility function of the independent non-public network that assigned the fifth generation globally unique temporary identifier to the user equipment.

11. A method for configuring a network identifier in a user equipment mobile scenario, characterized in that: include: A target access and mobility function of a target network receives a registration request from a user equipment, the registration request triggering a mobility registration update procedure; receiving a fifth generation globally unique temporary identifier and a network identifier of a source network, the source network being an independent non-public network identified by a public land mobile network identifier and a network identifier; determining a source access and mobility function using the received fifth generation globally unique temporary identifier and network identifier information, wherein the registration request includes the network identifier information when the user equipment determines that the fifth generation globally unique temporary identifier is allocated by the independent non-public network; as well as The mobility registration update procedure is performed for the user equipment, wherein the target access and mobility function obtains user equipment context information from the source access and mobility function.

12. The method for configuring a network identifier in a user equipment mobile scenario according to claim 11, characterized in that: The network identifier information refers to the entire network identifier value or a partial network identifier value of the independent non-public network.

13. The method for configuring a network identifier in a user equipment mobile scenario according to claim 11, characterized in that: The fifth generation globally unique temporary identifier comprises a globally unique access and mobility function identifier and a fifth generation temporary mobile subscriber identifier, wherein the globally unique access and mobility function identifier further comprises a public land mobile network identifier and an access and mobility function identifier.

14. The method for configuring a network identifier in a user equipment mobile scenario according to claim 13, characterized in that: The public land mobile network identifier further comprises a mobile country code and a mobile network code, wherein the mobile country code is not globally unique when assigned by the independent non-public network.

15. The method for configuring a network identifier in a user equipment mobile scenario according to claim 11, characterized in that: The target access and mobility function uses the fifth generation globally unique temporary identifier and the network identifier information to find a source access and mobility function of the independent non-public network that assigned the fifth generation globally unique temporary identifier to the user equipment.

16. The method for configuring a network identifier in a user equipment mobile scenario according to claim 15, characterized in that: The target access and mobility function sends a message to the source access and mobility function requesting user equipment context information.

17. The method for configuring a network identifier in a user equipment mobile scenario according to claim 15, characterized in that: If the network identifier is a self-defined value, the target access and mobility function sends a message to the user equipment requesting a user hidden identifier or a user permanent identifier.

Images