System and method for user equipment registration

Abstract

Systems and methods are provided for user equipment registration to a network. A wireless communication node may receive a first registration request from a wireless communication device, the first registration request including at least one information element (IE). The wireless communication node may determine operation of the network function based on the at least one IE.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for user equipment (UE) to register to a network. Background Technology

[0002] The standards organization Third Generation Partnership Project (3GPP) is currently developing a new radio interface (called 5G New Radio (5G NR)) and a next-generation packet core network (NG-CN or NGC). 5G NR will have three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and the User Equipment (UE). To facilitate the implementation of different data services and requirements, the elements of the 5GC (also known as network functions) have been simplified, with some elements being software-based and others hardware-based, so that these elements can be adapted as needed. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues raised in the prior art, and to provide additional features that will become apparent from the following detailed description taken in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are provided by way of example and are not restrictive, and that various modifications can be made to the disclosed embodiments by those skilled in the art who read this disclosure, while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium in which a wireless communication node (e.g., a base station (BS) or radio access network (RAN) node) can receive a first registration request from a wireless communication device (e.g., a user equipment (UE)), the first registration request including at least one information element (IE). The wireless communication node can determine, based on the at least one IE, the operation of a network function (e.g., operation associated with or related to the network function).

[0005] In some embodiments, the at least one IE may include indications of at least one of the following: registration type; subscription concealed identifier (SUCI); globally unique temporary identity (GUTI); permanent equipment identifier (PEI); at least one security parameter; protocol data unit (PDU) session state; user equipment (UE) policy container; session management function (SMF) selected subscription data; or a list of PDU sessions to be activated. The wireless communication node may receive user equipment (UE) context from the data function (DF) according to the first registration request.

[0006] In some embodiments, the operation may include at least one of the following: the wireless communication node selecting the network function based on a local policy, or information of the network function included in the user equipment (UE) context, or the address of the network function retrieved from the network repository function (NRF); the wireless communication node distributing at least one parameter to the network function; the wireless communication node interacting with the session management function (SMF) to deactivate at least one PDU session; the wireless communication node sending an establishment request to the policy control function (PCF); the wireless communication node sending a request to the unified data management (UDM) to select subscription data for the SMF; or the wireless communication node sending a request to the SMF to activate the user plane connection.

[0007] In some embodiments, when the Protocol Data Unit (PDU) session state of the at least one IE indicates whether a PDU session is active in the wireless communication device, the wireless communication node can interact with the SMF to deactivate the deactivated PDU session in the wireless communication device. In some embodiments, when receiving a User Equipment (UE) policy container from the at least one IE from the wireless communication device, the wireless communication node can select a Policy Control Function (PCF) according to the at least one IE. The wireless communication node can send the establishment request to the selected PCF.

[0008] In some embodiments, when the Session Management Function (SMF) selects subscription data and determines that it is stored in the Data Function (DF), the wireless communication node may send the request for the SMF selects subscription data to the UDM. In some embodiments, when the list of PDU sessions to be activated is included in the at least one IE, the wireless communication node may send the request to the SMF to activate the user plane connection of the PDU session.

[0009] In some embodiments, the wireless communication node may select an access and mobility management function (AMF) based on the GUTI, the SUCI, or the Subscription Permanent Identifier (SUPI). The wireless communication node may send a second registration request to the selected AMF. The wireless communication node may receive a first registration acceptance message from the selected AMF. The registration acceptance message may include at least one of the following: the SUPI, the GUTI, the access mobility (AM) container, an indication of a registration area, permitted network slice selection assistance information (NSSAI), or an indication of mobility restrictions.

[0010] In some embodiments, the wireless communication node may send a second registration acceptance message to the wireless communication device. The second registration acceptance message may include at least one of the following: at least one radio access network (RAN) parameter, or at least one access mobility (AM) container. The wireless communication node may receive a registration completion message from the wireless communication device based on the second registration acceptance message.

[0011] In some embodiments, a wireless communication device (e.g., a user equipment (UE)) may send a first registration request to a wireless communication node (e.g., a base station (BS) or a radio access network (RAN) node), the first registration request including at least one information element (IE). The wireless communication node may determine operation of network functions based on the at least one IE. Attached Figure Description

[0012] Various exemplary embodiments of this solution are described in detail below with reference to the following figures or drawings. These figures are provided for illustrative purposes only and depict only exemplary embodiments of this solution to facilitate the reader's understanding. Therefore, these figures should not be construed as limiting the breadth, scope, or applicability of this solution. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of explanation.

[0013] Figure 1 An example cellular communication network that can implement the techniques disclosed herein according to embodiments of this disclosure is shown; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 An example 5G system architecture according to some embodiments of this disclosure is shown; Figure 4 An example control plane protocol stack according to some embodiments of this disclosure is shown; Figure 5 An example next-generation network architecture according to some embodiments of this disclosure is shown; Figure 6 An example user equipment (UE) registration process according to some embodiments of this disclosure is illustrated; and Figure 7 A flowchart of an example method for user equipment (UE) registration according to an embodiment of this disclosure is shown. Detailed Implementation

[0014] 1. Mobile communication technology and environment Figure 1 An example wireless communication network and / or system 100 according to an embodiment of this disclosure is illustrated, in which the techniques disclosed herein can be implemented. In the following discussion, the wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as network 100. Such an example network 100 includes base stations 102 (hereinafter referred to as BS 102, also referred to as wireless communication nodes) and user equipment 104 (hereinafter referred to as UE 104, also referred to as wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the respective geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0015] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are described herein as "communication nodes," non-limiting examples of methods generally practiced herein. According to various embodiments of this scheme, such communication nodes may be capable of wireless and / or wired communication.

[0016] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM (Orthogonal Frequency Division Multiplexing) / OFDMA (Orthogonal Frequency Division Multiple Access) signals) according to some embodiments of this scheme is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, system 200 may be used in wireless communication environments (such as those described above) Figure 1 In a wireless communication environment 100, communication (e.g., sending and receiving) data symbols.

[0017] System 200 typically includes a base station 202 (hereinafter referred to as BS 202) and a user equipment 204 (hereinafter referred to as UE 204). BS 202 includes a BS (base station) transceiver module 210 (hereinafter also referred to as BS transceiver 210, transceiver 210), a BS antenna 212 (hereinafter also referred to as antenna 212 or downlink antenna 212), a BS processor module 214 (hereinafter also referred to as processor module 214), a BS memory module 216 (hereinafter also referred to as memory module 216), and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230 (also referred to as UE transceiver 230, transceiver 230), a UE antenna 232 (hereinafter also referred to as antenna 232 or uplink antenna 232), a UE memory module 234 (hereinafter also referred to as memory module 234), and a UE processor module 236 (hereinafter also referred to as processor module 236), each module being coupled to and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via communication channel 250, which can be any wireless channel or other medium suitable for the data transmission described herein.

[0018] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described in general terms of their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art can implement this functionality appropriately for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0019] According to some embodiments, UE transceiver 230 may be referred to herein as an uplink transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the uplink receiver circuitry is coupled to the uplink antenna 232 so that transmissions are received over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time, such that the uplink transmitter is coupled to the uplink antenna 232 while the downlink receiver is coupled to the downlink antenna 212 to receive transmissions via the wireless transmission link 250. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0020] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0021] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be implemented in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of such configurations.

[0022] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0023] Network communication module 218 typically represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX (World Interoperability for Microwave Access) services. In a typical deployment, but without limitation, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured as,” “configured to,” and their variations, used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted, and / or arranged to perform a specified operation or function.

[0024] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is other layers.

[0025] Various exemplary embodiments of the present technical solution are described below with reference to the accompanying drawings to enable those skilled in the art to make and use the present technical solution. As will be apparent to those skilled in the art, after reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present technical solution. Therefore, the present technical solution is not limited to the exemplary embodiments and applications described and shown herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example method. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of the present technical solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, the present technical solution is not limited to the specific order or hierarchy presented.

[0026] 2. Systems and methods for user equipment (UE) to register to the network Registration process for service-based interface N2 A service-based architecture (SBA) can be implemented in the 5G core network. This SBA architecture improves the flexibility and scalability of the 5G core network. Network functions (NFs) can provide one or more services (e.g., registration or communication services). An NF service can be a type of capability that an NF (e.g., an NF service producer) exposes to other authorized NFs (e.g., NF service consumers) through a service-based interface. NFs can provide different capabilities and different NF services to different consumers. Therefore, NF communication based on service interfaces is more flexible and scalable.

[0027] In 5G systems, the interface N2 between the NG-RAN and AMF may not be a service-based interface. To further improve the flexibility and scalability of next-generation networks, particularly the flexibility and scalability of the services provided by the RAN, the interface between the RAN and core network functions can be configured / implemented as a service-based interface. Therefore, this disclosure describes the interface between the RAN and the core network (CN) as a service-based interface. If the interface between the RAN and CN is defined as a service-based interface, the functions of the RAN and CN NFs can be recombined, and the process can subsequently be redesigned.

[0028] This disclosure proposes to define the registration process based on one or more of the following preconditions.

[0029] 1. The interface between RAN and CN can be defined as a service-based interface.

[0030] 2. The RAN takes over at least one security function (e.g., authentication, encryption, integrity protection, or key storage) from the CN network function (NF).

[0031] During the registration process, the RAN can terminate all integrated and encrypted Non-Access Stratum (NAS) messages and distribute containers to different CN NFs based on the terminated NAS messages.

[0032] This disclosure contemplates a deployment of a joint data function, which may include / be a separate new NF or several NFs distributed across existing CN NFs. The joint data function can provide data functions, such as data storage, data registration, data subscription, and / or data change notification. In such a deployment scenario, the RAN can interact with the joint data function to register UE contexts.

[0033] Figure 3 An example 5G system architecture according to some embodiments of this disclosure is shown. This 5G system architecture may include one or more of the following network functions (NFs) or components.

[0034] (1) UE: User Equipment.

[0035] (2) RAN: Radio Access Network. This RAN can transparently transmit at least one NAS message from the UE to the CN.

[0036] (3) AMF: Access and Mobility Management Function. This NF may include a number of functions. For example, these functions may include at least one of the following: UE mobility management, reachability management, connection management, or registration management. The AMF may terminate the RAN control plane (CP) interface N2 and the non-access stratum (NAS) interface N1, and / or NAS encryption and integrity protection. The AMF may terminate all integrated and encrypted NAS messages, and then distribute the session management (SM) NAS to the appropriate session management function (SMF) or other containers to the CN NF via the N11 interface.

[0037] (4) UDM: Unified Data Management. This NF can manage the UE's subscription profile. Subscription data can be stored in the unified data repository (UDR). Subscription information may include network slicing-related subscription data used for mobility management and / or session management. AMF and SMF can retrieve subscription data from the UDM.

[0038] (5) NSSF: Network slice selection function. This NF may support at least one of the following functions: selecting a set of network slice instances serving the UE; determining the allowed NSSAI and the mapping to HPLMN (Home Public Land Mobile Network) S-NSSAI (Single Network Slice Selection Assistance Information) (if required); determining the configured NSSAI and the mapping to HPLMN S-NSSAI (if required); determining the set of AMFs to serve the UE, or, based on configuration, possibly by querying the Network Repository Function (NRF) to determine the list of candidate AMFs.

[0039] (6) SMF: Session Management Function. The NF may include at least one of the following functions: session establishment, modification and release, UE IP address allocation and management, or selection and control of user plane (UP) functions.

[0040] (7) UPF: User plane function. This NF can be used as an anchor point for same / different radio access technology (RAT) mobility and / or as an external PDU session point for interconnection with a data network (DN). The UPF can route and forward packets according to instructions from the SMF. When the UE is in idle mode, the UPF can buffer downlink (DL) data.

[0041] (8) PCF: Policy Control Function. This NF can support a unified policy framework to manage network behavior. The PCF can provide access management policies to the AMF, session management policies to the SMF, or UE policies to the UE. The PCF can access the Unified Data Repository (UDR) to obtain subscription information related to policy decisions.

[0042] Figure 4 An example control plane protocol stack between a UE and an AMF according to some embodiments of this disclosure is shown.

[0043] NAS-MM: The NAS protocol for mobility management (MM) functions supports registration management, connection management, and user plane connection activation and deactivation. NAS-MM is responsible for the encryption and integrity protection of NAS signaling.

[0044] 5G-AN Protocol Layer: This set of protocols / layers may depend on the 5G Access Network (AN). In the case of Next Generation Radio Access Network (NG-RAN), the radio protocol between the UE and NG-RAN nodes (e.g., eNodeB or gNodeB) may include the access stratum (AS) layer and lower layers.

[0045] This disclosure proposes the following improvements to the control plane protocol stack.

[0046] - The interface between RAN and CN can be defined as a service-based interface.

[0047] - The RAN can take over security functions (e.g., authentication, encryption, integrity protection, and / or key storage) from the CN NF.

[0048] This disclosure proposes a definition of the registration process based on the above improvements.

[0049] During the registration process, the RAN can terminate all integrated and encrypted NAS messages and distribute containers to different CN NFs based on the terminated NAS messages.

[0050] This disclosure considers the deployment of a joint data function, which may be / include a separate new NF or several NFs distributed across existing CN NFs. The joint data function can provide data functions such as data storage, data registration, data subscription, and / or data change notification. In such deployment scenarios, the RAN can interact with the joint data function to register UE contexts.

[0051] Implementation Example 1: Next-Generation Network Architecture Figure 5 An example next-generation network architecture according to some embodiments of this disclosure is shown.

[0052] (R)AN can terminate the NAS interface N1 and supports NAS encryption and integrity protection. UE authentication and security mode command procedures can be initiated and executed by (R)AN. (R)AN uses the UE security context created in (R)AN and stored in (R)AN / DF to decrypt and / or check the integrity protection of NAS messages.

[0053] The interface between the (R)AN and the core network can be defined as a service-based interface. The (R)AN can, for example, distribute / send registration messages to the appropriate AMF via the service-based interface Namf. Similarly, the (R)AN can distribute / send session management messages to the appropriate SMF via the service-based interface Nsmf. The (R)AN can distribute / send policy management messages for the UE to the appropriate PCF via the service-based interface Npcf. The (R)AN can distribute / send subscription management messages to the appropriate UDM via the service-based interface Nudm. The (R)AN can distribute / send context management messages to the appropriate DF via the service-based interface Ndf. Network functions (e.g., AMF, SMF, UDM, and / or PCF) can invoke Nran service operations via the service-based interface Nran.

[0054] A data function may be dedicated to data storage and / or management to store and manage all data in the network, including at least one of the following: UE data, network function data, performance data, or policy data. The data function may be named a data function, data center, data repository function, data storage function, or any other name with the same functionality.

[0055] If a Data Function (DF) is deployed, all UE information, including PDU session information, can be stored in the DF. The (R)AN can select the DF based on local configuration or information obtained from the NRF. The (R)AN can select the AMF / SMF / UDM / PCF based on local configuration, UE context, or information obtained from the NRF.

[0056] Implementation Example 2: UE Authentication and Security Process Figure 6 An example PDU session establishment process according to some embodiments of this disclosure is shown.

[0057] Step 1 (from UE to RAN): The UE may initiate a registration request to the RAN node. The registration request may include at least one of the following: registration type, Subscription Hidden Identifier (SUCI) or 5G Globally Unique Temporary Identifier (GUTI), Permanent Device Identifier (PEI), or one or more security parameters.

[0058] Step 2: If a DF has been deployed and the UE context has been uploaded to the DF after the final RRC release, the RAN node can retrieve the UE context from the DF. The RAN node can send messages to the DF, such as Ndf_UEContext_retrieval (e.g., SUPI, SUCI, and / or GUTI). The DF can return (or respond to) the UE context based on SUPI, SUCI, and / or GUTI. If no DF is deployed in the network, or if the UE context was not released in the RAN node when the UE enters idle mode and the RAN node remains unchanged, the RAN node can directly utilize the UE context.

[0059] Step 3: If a secure connection has not yet been established, the RAN node can initiate a UE authentication process with the authentication server function (AUSF). Upon successful authentication, the AUSF can store the UE. AUSF The authentication result can be notified to the UDM and RAN nodes. The RAN can then initiate a security mode command procedure with the UE to use the newly generated security context.

[0060] After successful authentication and security procedures, the RAN can decide whether to interact with the CN NF based on the information included in the registration request. Since access and mobility checks are performed by the AMF, the RAN node can interact with the AMF. If UE access to the network is not permitted, the RAN node may not need to interact with other CN NFs.

[0061] RAN nodes can select AMF based on GUTI (if available) or SUPI / SUCI. RAN nodes can forward access and mobility control-related parameters (e.g., requested network slice selection assistance information (NSSAI), last visited tracking area identity (TAI) (if available), UE mobility management (MM) core network capabilities) to the AMF.

[0062] Step 4: The RAN node can select an AMF based on the GUTI included in the registration request. If the GUTI is not included, the RAN can select a new AMF for the UE.

[0063] Step 5 (between RAN and AMF): The RAN node may invoke a Namf_Registration request to the AMF, which may include the GUTI, TAI (e.g., cell ID), and last visited TAI (if available) based on parameters included in the registration request message from the UE. In some embodiments, the registration request may include parameters other than those listed.

[0064] Step 6 (between AMF and UDM): If the AMF has changed since the last registration procedure, or if the UE registration type is initial registration or emergency registration, or if the UE provides a SUPI that does not involve a valid context in the AMF, or if the UE registers to the same AMF that the UE has already registered to for non-3GPP access (e.g., the UE registered for non-3GPP access and initiated a registration procedure to add 3GPP access), the new AMF can be registered with the UDM using the Nudm_UECM_Registration operation.

[0065] After the AMF has successfully completed the Nudm_UECM_Registration operation, and if the AMF does not have the UE's subscription data, the AMF can use operations / procedures such as Nudm_SDM_Get to retrieve access and mobility subscription data, the UE context in the SMF data, and / or LCS (Location Services) mobile origination. If it is determined that the SMF selection subscription data should be transmitted to the RAN node because the SMF selection can be performed by the RAN node, then the UDM may not need to transmit the SMF selection subscription data to the AMF. Otherwise, the SMF selection subscription data may be transmitted to the AMF.

[0066] Steps 7 and 8: The AMF can decide / determine whether to initiate PCF communication based on the UE context and local configuration. Based on the registration type (e.g., initial registration and mobility registration) and AMF relocation, the (new) AMF can decide whether to select a new PCF or contact an existing PCF, and can initiate AM policy association establishment / modification.

[0067] Steps 9 and 10: For UE-PCF, there are two options for establishing UE policy association. Option A can be initiated by the AMF, and option B can be initiated by the RAN.

[0068] Option A (steps 9a to 10a): If an IE of the UE policy container is received from the UE, the AMF may send an Npcf_UEPolicyControl creation request (e.g., SUPI, access type) to the PCF.

[0069] Option B (Steps 9b to 10b): When the RAN receives a UE policy container for at least one IE from the UE, it can select a PCF based on the at least one IE. The RAN can send an establishment request (e.g., UE policy association establishment) to the selected PCF. In some embodiments, these two steps can be performed after step 11 (after successful access and mobility checks).

[0070] Step 11 (between AMF and RAN): The AMF can invoke Nnr_Registrationaccecpt (e.g., SUPI / GUTI, mobility restrictions, AM container) to indicate successful access and mobility checks, and the AMF can assign a GUTI to the UE. Parameters assigned by the AMF (e.g., registered area and / or allowed NSSAI) can be included in the AM container. Parameters sent to the RAN (e.g., mobility restrictions) may not be included in the AM container.

[0071] After successful registration, the RAN node can invoke service operations based on the registration request from the UE or one or more parameters included in the UE context to distribute parameters to the appropriate CN NF based on the UE context (retrieved from the DF). If the UE context does not include the relevant CN NF, the RAN node can select the corresponding CN NF based on local policies.

[0072] The following example shows an example where some optional parameters may exist.

[0073] i. If the IE includes the PDU session state, which indicates a previously established PDU session in the UE, the RAN node can interact with the relevant SMF to deactivate the PDU session that has already been deactivated in the UE.

[0074] ii. If an IE for the UE policy container is received from the UE, the RAN may send an Npcf_UEPolicyControl creation request (e.g., SUPI, access type) to the PCF (Option B: steps 9b to 10b).

[0075] iii. If it is determined that the SMF selection subscription data is stored in the DF and the UE context from the DM does not include the SMF selection subscription data, the RAN node can send a message (e.g., Nudm_SDM_Get) to the UDM to obtain the SMF selection subscription data.

[0076] iv. If the list of PDU sessions to be activated is included in the registration request (step 12), the RAN node may send an Nsmf_PDUSession_UpdateSMContext request to the SMF associated with the PDU session in order to activate the user plane connection of these PDU sessions.

[0077] RAN nodes can select a CN NF based on at least one of the following.

[0078] (1) Local strategy.

[0079] (2) Information about NFs included in the UE context. For example, if the UE context includes the address or ID of an AMF, SMF, or PCF, and the RAN node determines that this information remains unchanged, the RAN node can invoke operations performed with existing NFs.

[0080] (3) Obtain the address of the NF from the NRF using the parameters provided by the UE or the location of the UE.

[0081] Step 13 (from RAN to UE): The RAN can send a registration acceptance (e.g., RAN parameters, AM container) to the UE. The RAN node can generate at least one parameter of the radio interface based on information from the CN NF.

[0082] Step 14 (from UE to RAN): If any parameters included in the registration acceptance message require confirmation, the UE can send a registration complete message to the RAN node. The RAN node can then invoke the appropriate CN NF service operation based on the confirmation included in the registration complete message. For example, if a UDM container is included, the RAN can invoke the appropriate UDM service operation to send the container.

[0083] Step 15: After the registration process is complete, the RAN node can release radio resources. Additionally, the RAN node can upload all UE contexts to the DF and release local contexts. When the RAN node receives a request from a UE, it can retrieve the UE context from the DF, as described in Step 2.

[0084] It should be understood that one or more features in the above / below implementation examples are not unique to a particular implementation example, but can be combined in any way (e.g., with any priority and / or order, concurrently or otherwise).

[0085] Figure 7 A flowchart of method 700 for the UE registration process is shown. This document can be used in conjunction with... Figures 1 to 6 The method 700 may be implemented by any one or more of the detailed components and devices. Generally, in some embodiments, the method 600 may be performed by a wireless communication node (e.g., a base station (BS) or a radio access network (RAN) node). Depending on the embodiment, additional, fewer, or different operations may be performed in method 700. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0086] A wireless communication node (e.g., a base station (BS) or a radio access network (RAN) node) may receive a first registration request from a wireless communication device (e.g., a user equipment (UE)), the first registration request including at least one information element (IE). The wireless communication node may determine, based on the at least one IE, the operation of a network function (e.g., the operation associated with the network function).

[0087] In some embodiments, the at least one IE may include indications of at least one of the following: registration type; Subscription Hidden Identifier (SUCI); Globally Unique Temporary Identifier (GUTI); Permanent Device Identifier (PEI); at least one security parameter; Protocol Data Unit (PDU) session state; User Equipment (UE) policy container; Session Management Function (SMF) selection subscription data; or a list of PDU sessions to be activated. The wireless communication node may receive a User Equipment (UE) context from a Data Function (DF) based on the first registration request.

[0088] In some embodiments, the operation may include at least one of the following: the wireless communication node selecting the network function based on a local policy, or information of the network function included in the user equipment (UE) context, or the address of the network function retrieved from the network repository function (NRF); the wireless communication node distributing at least one parameter to the network function; the wireless communication node interacting with the session management function (SMF) to deactivate at least one PDU session; the wireless communication node sending an establishment request to the policy control function (PCF); the wireless communication node sending a request to the unified data management (UDM) to select subscription data for the SMF; or the wireless communication node sending a request to the SMF to activate the user plane connection.

[0089] In some embodiments, when the Protocol Data Unit (PDU) session state of the at least one IE indicates whether a PDU session is active in the wireless communication device, the wireless communication node can interact with the SMF to deactivate the deactivated PDU session in the wireless communication device. In some embodiments, when receiving a User Equipment (UE) policy container from the at least one IE from the wireless communication device, the wireless communication node can select a Policy Control Function (PCF) according to the at least one IE. The wireless communication node can send the establishment request to the selected PCF.

[0090] In some embodiments, when the Session Management Function (SMF) selects subscription data and determines that it is stored in the Data Function (DF), the wireless communication node may send the request for the SMF selects subscription data to the UDM. In some embodiments, when the list of PDU sessions to be activated is included in the at least one IE, the wireless communication node may send the request to the SMF to activate the user plane connection of the PDU session.

[0091] In some embodiments, the wireless communication node may select an Access and Mobility Management Function (AMF) based on the GUTI, the SUCI, or the Subscription Permanent Identifier (SUPI). The wireless communication node may send a second registration request to the selected AMF. The wireless communication node may receive a first registration acceptance message from the selected AMF. The registration acceptance message may include at least one of the following: the Subscription Permanent Identifier (SUPI), the Globally Unique Temporary Identifier (GUTI), the Access Mobility (AM) container, an indication of a registration area, Allowed Network Slice Selection Assistance Information (NSSAI), or an indication of mobility restrictions.

[0092] In some embodiments, the wireless communication node may send a second registration acceptance message to the wireless communication device. The second registration acceptance message may include at least one of the following: at least one radio access network (RAN) parameter, or at least one access mobility (AM) container. The wireless communication node may receive a registration completion message from the wireless communication device based on the second registration acceptance message.

[0093] In some embodiments, a wireless communication device (e.g., a user equipment (UE)) may send a first registration request to a wireless communication node (e.g., a base station (BS) or a radio access network (RAN) node), the first registration request including at least one information element (IE). The wireless communication node may determine operation of network functions based on the at least one IE.

[0094] While various embodiments of the present solution have been described above, it should be understood that these embodiments are presented by way of example only and not as limitations. Similarly, various diagrams may depict exemplary architectures or configurations provided to enable those skilled in the art to understand exemplary features and functionality of the present solution. However, those skilled in the art will understand that the solution is not limited to the illustrated exemplary architectures or configurations, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative embodiments described above.

[0095] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of elements. Therefore, references to the first and second elements do not imply that only two elements can be used or that the first element must precede the second element in some way.

[0096] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0097] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation will not depart from the scope of this disclosure.

[0098] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein.

[0099] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, with communication media including any medium that enables the transfer of computer programs or code from one location to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and that is accessible to a computer.

[0100] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the associated functions described herein. Furthermore, for purposes of discussion, various modules are described as separate modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of this solution.

[0101] Furthermore, memory or other storage devices and communication components may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality among different functional units, processing logic elements, or domains can be used without diminishing the effectiveness of this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0102] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is accorded the broadest scope consistent with the novel features and principles disclosed herein as set forth in the appended claims.

Claims

1. A method comprising: A first registration request is received by a wireless communication node from a wireless communication device, the first registration request including at least one information element (IE); as well as The operation of the network function is determined by the wireless communication node based on the at least one IE.

2. The method according to claim 1, wherein, The at least one IE includes an indication of at least one of the following: Registration type; Subscription Hidden Identifier (SUCI); Globally Unique Temporary Identifier (GUTI); Permanent Device Identifier (PEI); At least one safety parameter; Protocol Data Unit (PDU) session state; User Equipment (UE) policy container; Session Management Function (SMF) selects contract data; or A list of PDU sessions to be activated.

3. The method according to claim 1, comprising: The wireless communication node receives the user equipment (UE) context from the data function (DF) according to the first registration request.

4. The method according to claim 1, wherein, The operation includes at least one of the following: The network function is selected by the wireless communication node based on a local policy, or information of the network function included in the user equipment (UE) context, or the address of the network function retrieved from the network repository function (NRF); The wireless communication node distributes at least one parameter to the network function; The wireless communication node interacts with the Session Management Function (SMF) to deactivate at least one PDU session; The wireless communication node sends an establishment request to the Policy Control Function (PCF); The wireless communication node sends a request to the Unified Data Management (UDM) to select subscription data for the SMF; or The wireless communication node sends a request to the SMF to activate the user plane connection.

5. The method according to claim 4, comprising: When the Protocol Data Unit (PDU) session state of the at least one IE indicates whether the PDU session is active in the wireless communication device... The wireless communication node interacts with the SMF to deactivate the PDU session that was deactivated in the wireless communication device.

6. The method according to claim 4, comprising: When the user equipment (UE) policy container of the at least one Internet Explorer is received from the wireless communication device, The wireless communication node controls the function (PCF) according to the at least one IE selection policy; and The wireless communication node sends the establishment request to the selected PCF.

7. The method according to claim 4, comprising: When the Session Management Function (SMF) selects that the subscription data be stored in the Data Function (DF), The wireless communication node sends the request to the UDM to select subscription data for the SMF.

8. The method according to claim 4, comprising: When the list of PDU sessions to be activated is included in at least one of the IEs, The wireless communication node sends the request to the SMF to activate the user plane connection of the PDU session.

9. The method according to claim 2, comprising: The wireless communication node selects the Access and Mobility Management Function (AMF) based on the GUTI, the SUCI, or the Subscribed Permanent Identifier (SUPI). as well as The wireless communication node sends a second registration request to the selected AMF.

10. The method of claim 9, comprising: The wireless communication node receives a first registration acceptance message from the selected AMF, wherein the registration acceptance message includes at least one of the following: The SUPI, The GUTI, Access Mobility (AM) container, Instructions for the registration area, Allowed Network Slice Selection Auxiliary Information (NSSAI), or Instructions on mobility restrictions.

11. The method according to claim 1, comprising: The wireless communication node sends a second registration acceptance message to the wireless communication device, wherein the second registration acceptance message includes at least one of the following: At least one Radio Access Network (RAN) parameter, or At least one access mobility (AM) container.

12. The method of claim 11, comprising: The wireless communication node receives a registration completion message from the wireless communication device based on the second registration acceptance message.

13. A method comprising: A first registration request is sent from a wireless communication device to a wireless communication node, the first registration request including at least one information element (IE). The wireless communication node determines the operation of the network function based on the at least one IE.

14. A non-transitory computer-readable medium, wherein, The non-transitory computer-readable medium storage instructions, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 13.

15. An apparatus comprising: At least one processor is configured to perform the method according to any one of claims 1 to 13.

Images