CN112956222B

CN112956222B - Method and system for user equipment mobility management and registration

Info

Publication number: CN112956222B
Application number: CN201880099300.6A
Authority: CN
Inventors: 卢飞; 朱进国
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-11-06
Filing date: 2018-11-06
Publication date: 2022-11-18
Anticipated expiration: 2038-11-06
Also published as: CN112956222A; WO2020034449A1

Abstract

Methods and systems for UE mobility management and registration in 5G networks are disclosed. In one embodiment, a method for mobility registration performed by a first network node comprises: transmitting a first message to a User Equipment (UE), wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3 GPP) access technology.

Description

Method and system for user equipment mobility management and registration

Technical Field

The present disclosure relates generally to wireless communications, and more particularly, to a method and system for performing User Equipment (UE) mobility management and registration in a fifth generation (5G) communication network utilizing at least two different radio access technologies.

Background

As the number of applications and services for digital data continues to increase, so will the demands and challenges for network resources and operators. Being able to provide the various network performance characteristics required for future services is one of the major technical challenges facing service providers today. The performance requirements for the network will require connectivity in terms of data rate, delay, QOS, security, availability and many other parameters, all of which will vary from service to service. Thus, enabling a network to allocate resources in a flexible manner to provide customized connectivity for each different type of service would greatly enhance the ability of the network to meet future demands.

To provide different types of connectivity and services, a wireless communication system or network may allow User Equipment (UE), such as a Mobile Terminal (MT) or a Mobile Station (MS), to communicate with a Core Network (CN) via at least two different Radio Access Technologies (RATs). Examples of MTs and MSs include, but are not limited to, cellular phones, smart phones, tablets, laptops, and any device capable of wireless communication over 3GPP and non-3 GPP access technologies. For example, the first RAT may be a third generation partnership project (3 GPP) technology, such as the fifth generation (5G) communication protocol currently being standardized by 3 GPP. The second RAT may be a non-3 GPP technology such as, for example, a Wireless Local Area Network (WLAN) communication protocol (commonly referred to as "WiFi") standardized by the IEEE 802.11 working group.

Fig. 1 shows a block diagram of an exemplary 5G network capable of providing simultaneous access via a 3GPP RAT and a non-3 GPP RAT. As shown in fig. 1, the 5G network 100 includes User Equipment (UE) 102, 3GPP access technologies such as a next generation (NG or 5G) Radio Access Network (RAN) 104, non-3 GPP access technologies such as a non-3 GPP interworking function (N3 IWF) 106, an access and mobility management function (AMF) 108, a Session Management Function (SMF) 110, a User Plane Function (UPF) 112, and a Unified Data Management (UDM) 114.

AMF 108 and SMF 110 are network entities that handle control signaling and perform Packet Data Unit (PDU) session management functions. For example, the AMF 108 performs UE registration management, connection management, reachability management, mobility management, access authentication, and access authentication. AMF 108 also serves as a non-access stratum (NAS) security termination and relay node or module, etc., of a Session Management (SM) NAS between UE 102 and SMF 110, etc.

SMF 110 performs session control functions (e.g., establishing, modifying, and releasing sessions), UE IP address assignment and management (including optional authentication), selection and control of UPF 112, downlink data notification, etc. In addition, SMF 110 may establish signaling procedures for PDU sessions for each UE 102 and control the data path between, for example, UPF 112 and NG RAN 104.

The UPF 112 is a network entity in the data plane that can communicate with one or more NG RANs 104 via an N3 interface. The UPF 112 may also connect a data plane between multiple access networks (e.g., the 3GPP access network and the non-3 GPP access network (N3 IWF) of fig. 1) and a core network (not shown), and traffic for the UE 102 may be transmitted and received via the connected data plane. UDM node or module 114 is communicatively coupled to AMF 108 via an N8 interface and may perform functions such as user identification processing, access authentication based on user subscription data (e.g., roaming restrictions), subscription management, short Message Service (SMS) management, and the like.

As described above, the 5G network 100 has an integrated structure that accommodates both 3GPP and non-3 GPP access technologies. In an integrated network as described above, there is a need for a method for UE mobility management and registration in a non-3 GPP access network. For example, when the UE 102 connects to the same AMF 108 via an untrusted non-3 GPP RAT (e.g., N3 IWF) and a trusted 3GPP RAT (e.g., NG RAN) in the same Public Land Mobile Network (PLMN), and the UE 102 moves to a new location (i.e., a new city) assigned to a new AMF (not shown), the UE 102 will perform a mobility registration with the new AMF via a 3GPP access technology (e.g., NG RAN 104). After the new AMF has retrieved the UE context from the old AMF 108, the new AMF will attempt to establish an N2 connection with the N3IWF 106. However, because the link between the AMF and the N3IWF is temporarily unavailable or in a failure mode, the N2 connection may not be successfully established. In this case, there is currently no method for re-establishing the N2 connection between the new AMF and the N3IWF 106. Further, when N3IWF 106 detects that the N2 connection for UE 102 has been disconnected, N3IWF 106 will continue to attempt to re-establish the N2 connection using the old globally unique access and management function identifier (GUAMI) associated with the old AMF 108. Thus, existing systems and methods for handling UE mobility management and registration in communication networks utilizing 3GPP and non-3 GPP access technologies are not entirely satisfactory.

The information disclosed in this background section is only intended to provide a context for the various embodiments of the invention described below, and thus, this background section may include information that is not necessarily prior art information (i.e., information known to one of ordinary skill in the art).

Disclosure of Invention

The exemplary embodiments disclosed herein are intended to solve the problems associated with one or more of the problems presented in the prior art, as well as to provide additional features that will become apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. In accordance with various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. It is to be understood, however, that these embodiments are presented by way of example rather than limitation, and that various modifications to the disclosed embodiments may be apparent to those of ordinary skill in the art in view of this disclosure, while remaining within the scope of the present disclosure.

In one embodiment, a method performed by a network node comprises: transmitting a first message to a User Equipment (UE), wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3 GPP) access technology.

In another embodiment, a method performed by a User Equipment (UE) comprises: a first message is received from a first network node, wherein the first message includes a notification of a required registration procedure over a non-third generation partnership project (non-3 GPP) access technology.

In another embodiment, the invention provides a non-transitory computer-readable medium having stored thereon computer-executable instructions that, when executed, perform the above-described method.

In a further embodiment, a first network node configured to perform a method for mobility registration comprises: a transceiver configured to transmit a first message to a User Equipment (UE), wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3 GPP) access technology.

In another embodiment, a User Equipment (UE) configured to perform a UE registration method includes: a transceiver configured to receive a first message from a first network node, wherein the first message comprises a notification of a required registration procedure over a non-third generation partnership project (non-3 GPP) access technology.

Drawings

Various exemplary embodiments of the present disclosure are described in detail below with reference to the following drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the disclosure to facilitate the reader's understanding of the disclosure. Accordingly, the drawings are not to be taken as limiting the breadth, scope, or applicability of the disclosure. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

Fig. 1 shows a block diagram of a conventional 5G network in which the methods of the present invention may be implemented, in accordance with various embodiments of the present invention.

Fig. 2 illustrates a signaling flow diagram of a method of UE registration in a 5G network utilizing 3GPP and non-3 GPP access technologies, in accordance with some embodiments.

Fig. 3 shows a signaling flow diagram of a UE registration method in a 5G network utilizing 3GPP and non-3 GPP access technologies according to further embodiments.

Fig. 4 illustrates a block diagram of a network node configured to perform the methods disclosed herein, in accordance with some embodiments of the present disclosure.

Detailed Description

Various exemplary embodiments of the disclosure are described below with reference to the drawings to enable one of ordinary skill in the art to make and use the disclosure. It will be apparent to those of ordinary skill in the art upon reading this disclosure that various changes or modifications can be made to the examples described herein without departing from the scope of the disclosure. Accordingly, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Moreover, the particular order and/or hierarchy of steps in the methods disclosed herein is merely exemplary. Based upon design preferences, the specific order or hierarchy of steps in the methods or processes disclosed may be rearranged while remaining within the scope of the present disclosure. Accordingly, one of ordinary skill in the art will appreciate that the methods and techniques disclosed herein present the various steps or actions in a sample order, and unless otherwise explicitly stated, the disclosure is not limited to the specific order or hierarchy presented.

Fig. 2 illustrates a signaling flow diagram of a mobility management and registration protocol 200 implemented in a 5G network utilizing at least two different RATs, in accordance with some embodiments of the present invention. For ease of description, the protocol 200 is described below using various network modules or nodes that perform the various steps of the protocol 200, similar to the nodes/modules described above with respect to fig. 1 (e.g., UE, AMF, SMF, UPF, etc.), according to some embodiments.

In step 201, the ue first registers with a first AMF (AMF 1) using a NG RAN (e.g., 3GPP access technology according to 3GPP TS 23.502 sub-clause 4.2.2.2). In this procedure, AMF1 allocates a 5G Globally Unique Temporary Identifier (GUTI) (including GUAMI identifying AMF 1) and a registration area to the UE. AMF1 may also provide the UE with a periodic registration timer (e.g., T3512 defined in 3gpp TS 24.501). After the UE registers with AMF1, the UE may send a request to establish a PDU session to a first SMF (SMF 1) and a first UPF (UPF 1). In some embodiments, the request to establish a PDU session is generated and transmitted according to sub-clause 4.3.2 of 3gpp TS 23.502.

In step 202, the ue registers with the same AMF (AMF 1) via N3IWF (e.g., the non-3 GPP access technology specified in sub-clause 4.12.2.2 of 3GPP TS 23.502). In this process, AMF1 will not assign a new 5G-GUTI to the UE, and the UE will continue to use the same 5G-GUTI for non-3 GPP accesses as the 5G-GUTI assigned for 3GPP accesses described above. In addition, AMF1 will provide a de-registration timer to the UE. After the UE registers with AMF1 via N3IWF, for example, the UE may send a request to establish a PDU session via N3IWF to a second SMF (SMF 2) and a second UPF (UPF 2), as specified in sub-clause 4.3.2 of 3gpp TS 23.502.

As described above, if the UE moves to a new registration area associated with a different second AMF (AMF 2), the UE must perform a registration procedure with AMF2 via the NG RAN. In step 203, for example, if the UE transitions to a 5G Mobility Management (MM) -IDLE mode in a 3GPP access and moves to a different registration area, the UE will perform a registration procedure using AMF2 whose registration type is set to "mobility update". The UE sends a registration request message to AMF2, which includes its 5G-GUTI, the security capabilities of the UE, etc.

In step 204, if the 5G-GUTI of the UE is included in the registration request message and the serving AMF has been changed from AMF1 to AMF2 since the last registration procedure, the new AMF (AMF 2) may request a subscription permanent identifier (SUPI) and UE context information of the UE from AMF1 by calling a Namf _ Communication _ UEContextTransfer service operation on the old AMF (AMF 1), sending an integrity-protected registration request NAS message.

In step 205, the AMF1 responds to the AMF2 with a Namf _ Communication _ UEContextTransfer response message containing SUPI of the UE, context information, SMF information, etc. In some embodiments, an AMF UE Next Generation Application Protocol (NGAP) ID and an N3IWF UE NGAP ID for non-3 GPP access are included in the UE context information. In step 206, AMF2 notifies AMF1 that registration of the UE in AMF2 is completed by calling the Namf _ Communication _ registration completion notification service operation. In step 207, the amf2 informs SMF1 for each 3GPP access PDU session that SMF1 allocates to the UE that it has taken over the responsibility of the signalling path towards the UE for each PDU session. In some embodiments, AMF2 uses the SMF information received from AMF1 at step 205 to invoke an Nsmf pdusesion _ update smcontext service operation, as described above.

In step 208, the SMF1 responds with an Nsmf _ PDUSESION _ UpdateSMContext response. In step 209, AMF2 sends a registration accept message to the UE containing the 5G-GUTI of the UE and the registration area, wherein the 5G-GUTI includes the new GUAMI associated with AMF2. In step 210, the ue responds with a registration complete message.

Similarly, for PDU sessions with non-3 GPP access technology (N3 IWF), at step 211, AMF2 informs SMF2 for each PDU session for which it has taken over responsibility for the signalling path towards the UE. In some embodiments, AMF2 uses the SMF information received from AMF1 at step 205 to invoke an Nsmf pdusesion _ UpdateSMContext service operation.

At step 212, the smf2 responds with an Nsmf pdusesion _ UpdateSMContext response. At this point, if the N2 connection between AMF2 and N3IWF can be successfully established and the old AMF (AMF 1) has indicated an existing NGAP UE association towards the N3IWF, AMF2 will create a new NGAP UE association towards the N3IWF to which the UE is connected. This automatically releases the existing NGAP UE association between AMF1 and N3 IWF. The new AMF UE NGAP ID may be assigned by the new AMF. Alternatively, if AMF1 and AMF2 are in the same AMF set, AMF2 may also use the UE NGAP ID of AMF1 for the non-3 GPP access retrieved in step 205. In either case, the N3IWF may send a mobility response message to AMF2 containing the new N3IWF UE NGAP ID to complete the procedure for UE mobility registration for non-3 GPP access, in which case the remaining steps 213-218 described below need not be performed.

On the other hand, if AMF2 did not successfully establish an N2 connection with the N3IWF, AMF2 will send a notification message to the UE in step 213. In some embodiments, the notification message will contain information indicating to the UE that a registration procedure is required for non-3 GPP access. In some embodiments, this information may cause the UE to move to the 5GMM-IDLE state in non-3 GPP and perform a mobility registration update procedure. In a further embodiment, this information may cause the UE to maintain the 5GMM-CONNECTED state in non-3 GPP access and provide the N3IWF with a new GUAMI (which is part of the new 5G-GUTI allocated in step 209).

If the UE is in an IDLE state for non-3 GPP access (i.e., the UE is not currently using non-3 GPP access technology for PDU sessions), then in response to the notification message, the UE moves to 5GMM-IDLE mode for non-3 GPP access and performs a mobility registration update procedure in step 214. In some embodiments, for this procedure, the UE sends an Internet Key Exchange (IKE) message (e.g., IKE _ Auth _ Request message) containing the new GUAMI and a NAS PDU containing the registration Request message to the N3 IWF. In step 215, the N3IWF selects a new AMF based on the received new GUAMI and sends an N2 UE initialization message to AMF2 identified by the new GUAMI to establish an N2 connection between the N3IWF and AMF2. In some embodiments, the N2 UE initialization message contains a NAS PDU of the registration request.

In step 216, AMF2 sends an initial UE context request message to the N3IWF in response to receiving the N2 UE initialization message. In some embodiments, the initial UE context request message includes security context information, a mobility restriction list, and a NAS PDU containing a registration accept message. In some embodiments, the security context information includes security keys and algorithms for establishing a security context for the UE in the N3IWF, and the mobility restriction list includes one or more forbidden regions and/or allowed regions for the UE. The NAS PDU is a transparent container for the N3IWF, so that when the N3IWF receives the container containing the registration accept message, it simply forwards the message to the UE. At step 217, the N3IWF responds with an initial UE context response message confirming successful receipt of the initial UE context request message. In step 218, the N3IWF responds to the UE with an IKE _ Auth _ Response message. In this message, a registration accept message received in step 217 is included, which informs the UE that the registration for the non-3 GPP access has been successfully completed.

As described above, the UE receives a notification message from the new AMF using the 3GPP access, and in response, the UE performs a registration procedure for the non-3 GPP access technology and/or notifies the N3IWF of the new AMF to continue the previously established non-3 GPP access PDU session using the new AMF. Thus, according to some embodiments of the present invention, a procedure is provided for establishing a new N2 connection between a new AMF (AMF 2) and an N3IWF, thereby allowing UE mobility registration with the new AMF (AMF 2) for a non-3 GPP PDU session and/or continuing a previously established non-3 GPP access PDU session.

In another embodiment, in step 214, the ue may remain in a Connected state (e.g., 5G MM-Connected state) to continue the PDU session using a non-3 GPP access technology (e.g., wiFi) instead of being in IDLE mode during the registration procedure as described above. In this connected state, the UE sends an IKE _ Auth _ Request message to the N3IWF as before in step 214, however, this message only needs to provide the new GUAMI to the N3IWF and does not need to provide the NAS PDU containing the registration Request message to be forwarded to the new AMF, since there is no need to establish a new connection between the N3IWF and the new AMF and the UE does not need to provide the new AMF with updated UE information. As used herein, the term "registration procedure" refers to a procedure to establish a connection between a non-3 GPP access node (e.g., N3 IWF) and a new AMF while the UE is in an idle mode as determined by the non-3 GPP access node, and also refers to updating the GUAMI associated with the new AMF when the UE remains in a connected state to continue a previously established non-3 GPP access PDU session and has moved to a new location assigned to the new AMF.

Fig. 3 shows a signaling flow diagram of a mobility management and registration protocol 300 implemented in a 5G network using at least two different RATs according to a further embodiment of the present invention. In step 301, the ue first registers with a first AMF (AMF 1) using a NG RAN (e.g., 3GPP access technology according to 3GPP TS 23.502 sub-clause 4.2.2.2). In this procedure, AMF1 allocates a 5G Globally Unique Temporary Identifier (GUTI) and a registration area to the UE. The AMF1 may also provide the UE with a periodic registration timer (e.g., T3512). After the UE registers with AMF1, the UE may send a request to establish a PDU session to a first SMF (SMF 1) and a first UPF (UPF 1). In some embodiments, the request to establish a PDU session is generated and transmitted according to sub-clause 4.3.2 of 3gpp TS 23.502.

In step 302, the ue registers with the same AMF (AMF 1) via an N3IWF (e.g., the non-3 GPP access technology specified in sub-clause 4.12.2.2 of 3GPP TS 23.502). In this process, AMF1 will not assign a new 5G-GUTI to the UE, and the UE will continue to use the same 5G-GUTI for non-3 GPP accesses as the 5G-GUTI assigned for 3GPP accesses described above. In addition, AMF1 will provide a de-registration timer to the UE. After the UE registers with AMF1 via N3IWF, for example, the UE may send a request to establish a PDU session via N3IWF to a second SMF (SMF 2) and a second UPF (UPF 2), as specified in sub-clause 4.3.2 of 3gpp TS 23.502.

As described above, if the UE moves to a new registration area associated with a different second AMF (AMF 2), the UE must perform a registration procedure with AMF2 via the NG RAN. In step 303, for example, if the UE transitions to a 5G Mobility Management (MM) -IDLE mode in a 3GPP access and moves to a different registration area, the UE will perform a registration procedure using AMF2 whose registration type is set to "mobility update". The UE sends a registration request message to AMF2, which includes its 5G-GUTI, the security capabilities of the UE, etc.

In step 304, if the 5G-GUTI of the UE is included in the registration request message and the serving AMF has been changed from AMF1 to AMF2 since the last registration procedure, the new AMF (AMF 2) may request the subscription permanent identifier (SUPI) and UE context information of the UE from AMF1 by sending a registration request NAS message, which may be integrity protected, to invoke a Namf _ Communication _ uexttransfer service operation on the old AMF (AMF 1).

In step 305, AMF1 responds to AMF2 with a naf _ Communication _ UEContextTransfer message containing SUPI of the UE, context information, SMF information, etc. In some embodiments, an AMF UE Next Generation Application Protocol (NGAP) ID and an N3IWF UE NGAP ID for non-3 GPP access are included in the UE context information. In step 306, AMF2 notifies AMF1 that registration of the UE in AMF2 is completed by calling a Namf _ Communication _ registration completion notification service operation.

In step 307, the amf2 informs the SMF1 for each 3GPP access PDU session allocated to the UE by the SMF1 that it has taken over the responsibility of the signalling path towards the UE for each PDU session. In some embodiments, AMF2 uses the SMF information received from AMF1 in step 305 to invoke an Nsmf pdusesion _ update smcontext service operation, as described above. In step 308, SMF1 responds with an Nsmf _ PDUSESION _ UpdateSMContext response.

In step 309, the amf2 informs SMF2 for each non-3 GPP access PDU session that it has taken over the responsibility of the signalling path towards the UE. In some embodiments, AMF2 sends Nsmf _ pdusesion _ update smcontext request signaling to SMF2 using the SMF information received from AMF1 in step 305. In step 310, SMF2 responds with an Nsmf _ PDUSESION _ UpdateSMContext response.

In step 311, the amf2 sends a registration accept message to the UE. In some embodiments, the registration accept message contains the 5G-GUTI of the UE, the registration area, and the registration result, wherein the 5G-GUTI includes the new GUAMI associated with AMF2. The registration result may be a value (e.g., 0 or 1) that may be set to indicate "non-3 GPP access registration is required". Here, the registration result may be the same as the notification message containing information indicating to the UE that the non-3 GPP access requires a registration procedure, as described above with respect to step 213. In step 312, the ue responds with a registration complete message. In step 313, the ue transitions to 5GMM-IDLE mode for non-3 GPP access and performs a mobility registration update procedure. In some embodiments, the mobility registration update procedure performed at step 313 may be the same as or similar to step 302 discussed above, except that AMF2 is substituted for AMF 1. In other embodiments, the mobility registration update procedure at step 313 may be the same as or similar to steps 214-218 described above with respect to fig. 2.

Fig. 4 illustrates a block diagram of a Network Node (NN) 400 that may be configured to implement the various methods described herein. In some embodiments, the NN 400 may be an AMF or include some components or modules of an AMF to perform AMF functions, as described above. In other embodiments, the NN 400 may be a UE or include some components or modules of a UE to perform UE functions, as described above in accordance with various embodiments. In further embodiments, NN 400 may be an N3IWF or some component or module including an N3IWF to perform N3IWF functions, as described above in accordance with various embodiments.

As shown in fig. 4, the NN 400 includes a system clock 402, a processor 404, a memory 406, a transceiver 410 including a transmitter 412 and a receiver 414, a power module 408, and a mobility registration module 420. The system clock 402 provides timing signals to the processor 404 for controlling the timing of all operations of the NN 400. The processor 404 controls the general operation of the NN 400 and may include one or more processing circuits or modules, such as any combination of Central Processing Units (CPUs) and/or general purpose microprocessors, microcontrollers, digital Signal Processors (DSPs), field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), controllers, state machines, gated logic, discrete hardware components, dedicated hardware finite state machines, or any other suitable circuits, devices, and/or structures that may perform calculations or other operations on data.

Memory 406, which may include Read Only Memory (ROM) and Random Access Memory (RAM), may provide instructions and data to processor 404. A portion of the memory 406 may also include non-volatile random access memory (NVRAM). The processor 404 typically performs logical and arithmetic operations based on program instructions stored within the memory 406. Instructions (a.k.a. Software) stored in the memory 406 may be executed by the processor 404 to perform the methods described herein. The processor 404 and memory 406 together form a processing system that stores and executes software. As used herein, "software" refers to any type of instructions, whether referred to as software, firmware, middleware, microcode, etc., that configures a machine or device to perform one or more desired functions or processes. The instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable code format). When executed by one or more processors, the instructions cause the processing system to perform the various functions described herein.

The transceiver 410, which includes a transmitter 412 and a receiver 414, allows the NN 400 to transmit data to and receive data from a remote device (e.g., a Sat-gNB). An antenna 450 is electrically coupled to the transceiver 410. In some embodiments, the antenna may be a phased array antenna or other suitable antenna structure suitable for satellite communications. In various embodiments, the NN 400 includes (not shown) multiple transmitters, multiple receivers, and multiple transceivers. In some embodiments, antenna 450 may be a multi-antenna array that may form multiple beams, each pointing in a different direction.

The mobility registration module 420 may be implemented as part of the processor 404 programmed to perform the functions herein, or it may be a separate module implemented in hardware, firmware, software, or a combination thereof. According to various embodiments, the mobility registration module 420 is configured to perform one or more of the methods or techniques disclosed herein, such as generating, transmitting, and receiving signaling as described in steps 213-218 above. In some embodiments, the mobility registration module 420 may be implemented as software (i.e., computer-executable instructions) stored in a non-transitory computer-readable medium that, when executed by the processor 404, transform the processor 404 into a special-purpose computer to perform the methods and operations described herein.

The various components and modules discussed above are coupled together by a bus system 430. The bus system 430 may include a data bus and, in addition to the data bus, include, for example, a power bus, a control signal bus, and/or a status signal bus. It should be appreciated that the modules of the NN 400 may be operatively coupled to each other using any suitable techniques and media.

While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. Likewise, the various figures may depict example architectures or configurations provided to enable those of ordinary skill in the art to understand the exemplary features and functionality of the present disclosure. However, those skilled in the art will appreciate that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, as one of ordinary skill in the art will appreciate, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

It will also be understood that any reference herein to an element using a name such as "first," "second," etc., does not generally limit the number or order of such elements. Rather, these names may be used herein as a convenient way to distinguish between two or more elements or instances of an element. Thus, reference to first and second elements does not imply that only two elements can be used or that the first element must somehow precede the second element.

Further, those of ordinary skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and the like that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

One of ordinary skill would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code containing instructions (which may be referred to herein, for convenience, as "software" or a "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 as a combination of such techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. According to various embodiments, a processor, device, component, circuit, structure, machine, module, etc. may be configured to perform one or more of the functions described herein. The terms "configured to" or "configured to" as used herein with respect to a specified operation or function refer to a processor, device, component, circuit, structure, machine, module, signal, etc., that is physically constructed, programmed, arranged, and/or formatted to perform the specified operation or function.

Furthermore, those of ordinary skill in the art will appreciate that the various illustrative logical blocks, modules, devices, components, and circuits described herein may be implemented or performed in or by Integrated Circuits (ICs) that may include Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs), or other programmable logic devices, or any combinations thereof. The logic blocks, modules, and circuits may also include antennas and/or transceivers to communicate with various components within the network or within the device. A processor programmed to perform functions herein will become a specially programmed or special purpose processor and may be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein.

If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein may be embodied as software stored on a computer readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can communicate a computer program or code from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise 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 desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Additionally, for purposes of discussion, the various modules are described as discrete modules; however, as will be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the relevant functions according to embodiments of the present disclosure.

Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims

1. A method for mobility registration performed by a first network node, the method comprising:

in the event that a user equipment, UE, is moved by a second network node to a registration area of the first network node and the first network node is unable to establish an N2 connection with a non-third generation partnership project, 3GPP, access network, transmitting a first message to the UE,

wherein the first message comprises a notification requiring a registration procedure over a non-3 GPP access technology for the UE to perform a mobility registration update procedure in an idle state of a non-3 GPP access or for the UE to provide an updated globally unique access and management function identifier, GUAMI, to the non-3 GPP access network in a connected state.

2. The method of claim 1, wherein the notification further comprises an indication that registration from a non-3 GPP access is required.

3. The method of claim 1, wherein the first message further comprises identification information identifying the first network node.

4. The method of claim 1, further comprising:

receiving a second message from a second network node to establish a connection between the second network node and the first network node, wherein the second network node provides access to the non-3 GPP access technology.

5. The method of claim 4, further comprising:

transmitting UE context setup information to the second network node; and

receiving a UE context setup response message from the second network node, the response message confirming successful receipt of the UE context setup information.

6. The method of claim 5, further comprising transmitting a registration accept message to the second network node for forwarding to the UE.

7. A method for mobility registration performed by a user equipment, UE, the method comprising:

receiving a first message from a first network node in the event that the UE moves from a second network node to a registration area of the first network node and the first network node is unable to establish an N2 connection with a non-third generation partnership project, 3GPP, access network,

wherein the first message comprises a notification of a non-3 GPP access technology required registration procedure for the UE to perform a mobility registration update procedure in an idle state of a non-3 GPP access or for the UE to provide an updated globally unique access and management function identifier, GUAMI, to the non-3 GPP access network in a connected state.

8. The method of claim 7, wherein the notification further comprises an indication that non-3 GPP access requires registration.

9. The method of claim 7, wherein the first message further comprises identification information identifying the first network node.

10. The method of claim 7, further comprising:

transmitting a second message to a second network node, wherein the second message contains identification information identifying the first network node.

11. The method of claim 10, wherein the second message further comprises a registration request message to be forwarded to the first network node.

12. The method of claim 11, further comprising receiving a registration accept message from the second network node, wherein the registration accept message is sent by the first network node to the second network node for forwarding to the UE, the registration accept message confirming that registration has been successfully completed.

13. A non-transitory computer-readable medium having stored thereon computer-executable instructions that, when executed by a computer, perform the method of any one of claims 1 to 12.

14. A first network node configured to perform a method for mobility registration, the first network node comprising:

a transceiver configured to transmit a first message to a user equipment, UE, in the event that the UE is moved by a second network node to a registration area of the first network node and the first network node is unable to establish an N2 connection with a non-third generation partnership project, 3GPP, access network, wherein the first message includes a notification that requires a registration procedure by a non-3 GPP access technology for the UE to perform a mobility registration update procedure in an idle state for a non-3 GPP access or for the UE to provide an updated globally unique access and management function identifier, GUAMI, to the non-3 GPP access network in a connected state.

15. The first network node of claim 14, wherein the notification further comprises an indication that a non-3 GPP access requires registration when the UE is in an idle state for a non-3 GPP access.

16. The first network node of claim 14, wherein the first message further comprises identification information identifying the first network node.

17. The first network node of claim 14, wherein:

the transceiver is further configured to receive a second message from a second network node to establish a connection between the second network node and the first network node, wherein the second network node provides access to the non-3 GPP access technology.

18. The first network node of claim 17, wherein:

the transceiver is further configured to:

transmitting UE context setup information to the second network node; and

19. The first network node of claim 18, wherein the transceiver is further configured to transmit a registration accept message to the second network node for forwarding to the second network node.

20. A user equipment, UE, configured to perform a method of UE registration, the UE comprising:

a transceiver configured to receive a first message from a first network node in an instance in which the UE moves from a second network node to a registration area of the first network node and the first network node is unable to establish an N2 connection with a non-third generation partnership project 3GPP access network, wherein the first message includes a notification that requires a registration procedure over a non-third generation partnership project (non-3 GPP) access technology for the UE to perform a mobility registration update procedure in an idle state of a non-3 GPP access or for the UE to provide an updated globally unique access and management function identifier (GUAMI) to the non-3 GPP access network in a connected state.

21. The UE of claim 20, wherein the notification further comprises an indication that non-3 GPP access requires registration.

22. The UE of claim 20, wherein the first message further comprises identification information identifying the first network node.

23. The UE of claim 20, wherein the transceiver is further configured to transmit a second message to a second network node, wherein the second message contains identification information identifying the first network node.

24. The UE of claim 23, wherein the second message further comprises a registration request message to be forwarded to the first network node.

25. The UE of claim 24, wherein the transceiver is further configured to receive a registration accept message from the second network node, wherein the registration accept message is transmitted by the first network node to the second network node for forwarding to the UE, the registration accept message confirming that registration has been successfully completed.