WO2020034449A1

WO2020034449A1 - Methods and systems for user equipment mobility management and registration

Info

Publication number: WO2020034449A1
Application number: PCT/CN2018/114104
Authority: WO
Inventors: Fei Lu; Jinguo Zhu
Original assignee: Zte Corporation
Priority date: 2018-11-06
Filing date: 2018-11-06
Publication date: 2020-02-20
Also published as: CN112956222A; CN112956222B

Abstract

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

Description

METHODS AND SYSTEMS FOR USER EQUIPMENT MOBILITY MANAGEMENT AND REGISTRATION

TECHNICAL FIELD

The disclosure relates generally to wireless communications and, more particularly, to methods and systems for performing user equipment (UE) mobility management and registration in a 5 ^th 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, the demands and challenges placed on network resources and operators will continue to increase. Being able to deliver a wide variety of network performance characteristics that future services will demand is one of the primary technical challenges faced by service providers today. The performance requirements placed on the network will demand connectivity in terms of data rate, latency, QOS, security, availability, and many other parameters, all of which will vary from one service to the next. Thus, enabling a network to allocate resources in a flexible manner to provide customized connectivity for each different type of service will greatly enhance the network’s ability to meet future demands.

To provide different types of connectivity and services, a wireless communication system or network may allow user equipment (UE) device, such as a mobile terminal (MT) or mobile station (MS) , for example, to communicate with a core network (CN) over at least two different radio access technologies (RATs) . Examples of MTs and MSs include but are not limited to cellular telephones, smart phones, tablet computers, laptop computers, and any device capable of wireless communications via 3GPP and non-3GPP access technologies. For example, a first RAT may be a 3rd Generation Partnership Project (3GPP) technology such as the 5 ^th Generation (5G) communication protocols currently being standardized by the 3GPP. The second RAT may be a non-3GPP technology such as, for example, the wireless local area network (WLAN) communication protocols standardized by the IEEE 802.11 Working Group and commonly referred to as "WiFi. "

Figure 1 illustrates a block diagram of an exemplary 5G network capable of providing simultaneous access via a 3GPP RAT and a non-3GPP RAT. As shown in Figure 1, the 5G network 100 includes a user equipment device (UE) 102, a 3GPP access technology such as Next Generation (NG or 5G) Radio Access Network (RAN) 104, a non-3GPP access technology such as a non-3GPP interworking function (N3IWF) 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.

The AMF 108 and the SMF 110 are network entities that process control signals 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 authorization. The AMF 108 further serves as the non-access stratum (NAS) security termination and relay node or module of the session management (SM) NAS between the UE 102 and the SMF 110, etc.

The SMF 110 performs session control functions (e.g., establishing, changing and releasing a session) , UE IP address allocation &management (including optional authorization) , selection and control of UPF 112, downlink data notification, etc. Furthermore, the SMF 110 can establish a signaling procedure for a PDU session for each UE 102 and control data paths between the UPF 112 and the NG RAN 104, for example.

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 can also connect data planes between multiple access networks (e.g., the 3GPP access network and the non-3GPP access network (N3IWF) of Fig. 1) and the core network (not shown) , and a traffic of the UE 102) may be transmitted and received via the connected data planes. The UDM node or module 114 is communicatively coupled to the AMF 108 via an N8 interface and can perform functions such as user identification handling, access authorization based on user subscription data (e.g., roaming restrictions) , subscription management, short message service (SMS) management, etc.

As described above, the 5G network 100 has an integrated structure that simultaneously accommodates 3GPP and non-3GPP access technologies. In the integrated network as described above, a method for UE mobility management and registration in a non-3GPP access network is needed. For example, when the UE 102 connects to the same AMF 108 via an untrusted non-3GPP RAT (e.g., N3IWF) 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 mobility registration with the new AMF via the 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 try to establish an N2 connection with the N3IWF 106. However, it is possible that the N2 connection cannot be established successfully because the link between the AMF and the N3IWF is temporarily unavailable or in failure mode. In this situation, there is currently no method for re-establishing the N2 connection between the new AMF and N3IWF 106. Furthermore, when the N3IWF 106 detects that the N2 connection has been disconnected for the UE 102, the N3IWF 106 will continue trying 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 a communication network utilizing both 3GPP and non-3GPP access technologies are not entirely satisfactory.

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

SUMMARY OF THE INVENTION

The exemplary embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, exemplary systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of the present disclosure.

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

In another embodiment, a method performed by a user equipment device (UE) includes: receiving a first message from a first network node, wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3GPP) access technology.

In a further embodiment, the invention provides a non-transitory computer-readable medium having stored thereon computer-executable instructions that when executed carry out the above-described methods.

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

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

Figure 2 illustrates a signal flow diagram of a method of UE registration in a 5G network utilizing both 3GPPP and non-3GPPP access technologies, in accordance with some embodiments.

Figure 3 illustrates a signal flow diagram of a method of UE registration in a 5G network utilizing both 3GPPP and non-3GPPP access technologies, in accordance with further embodiments.

Figure 4 illustrates a block diagram of a network node configured for performing the methods disclosed herein, in accordance with some embodiments of the present disclosure.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Various exemplary embodiments of the present disclosure are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present disclosure. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.

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

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

At step 202, the UE registers with the same AMF (AMF1) via a N3IWF (e.g., a non-3GPP access technology as specified in sub-clause 4.12.2.2 of 3GPP TS 23.502) . In this procedure, AMF1 will not allocate a new 5G-GUTI to the UE, and the UE will continue to use the same 5G-GUTI for the non-3GPP access that was allocated above for the 3GPP access. Furthermore, AMF1 will provide a de-registration timer to the UE. After the UE is registered with AMF1 via the N3IWF, the UE can send a request to establish a PDU session via N3IWF to a second SMF (SMF2) and a second UPF (UPF2) as specified in the sub-clause 4.3.2 of 3GPP TS 23.502, for example.

As discussed above, if the UE moves to a new registration area associated with a different, second AMF (AMF2) , the UE must perform a registration procedure with AMF2 via NG RAN. At step 203, if the UE transitions to a 5G Mobility Management (MM) -IDLE mode in 3GPP access and travels to a different registration area, for example, the UE will perform a registration procedure with AMF2 with its registration type set to “mobility update. ” The UE sends a registration request message that includes its 5G-GUTI, the UE’s security capability, etc. to AMF2.

At step 204, if the UE's 5G-GUTI was included in the registration request message and the serving AMF has changed from AMF1 to AMF2 since the last registration procedure, the new AMF (AMF2) may invoke the Namf_Communication_UEContextTransfer service operation on the old AMF (AMF1) by sending a Registration Request NAS message, which may be integrity protected, to request the UE's Subscription Permanent Identifier (SUPI) and UE context information from AMF1.

At step 205, AMF1 responds to AMF2 with a Namf_Communication_UEContext Transfer message which contains the UE’s SUPI, context information, SMF information, etc. In some embodiments, the AMF UE Next Generation Application Protocol (NGAP) ID for non-3GPP access and N3IWF UE NGAP ID are included in the UE context information. At step 206, AMF2 notifies AMF1 that the registration of the UE in AMF2 is complete by invoking the Namf_Communication_RegistrationCompleteNotify service operation. At step 207, AMF2 notifies SMF1 for each 3GPP access PDU Session assigned to the UE by SMF1 that it has taken over the responsibility of the signalling path towards the UE for each PDU session. In some embodiments, AMF2 invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from AMF1 at step 205, as described above.

At step 208, the SMF1 responds with a Nsmf_PDUSession_UpdateSMContext Response. At step 209, AMF2 sends a Registration Accept message containing the UE’s 5G-GUTI and registration area to the UE , wherein the 5G-GUTI includes a new GUAMI related with the AMF2. At step 210, the UE responds with a Registration Complete message.

Similarly, for PDU sessions utilizing non-3GPP access technologies (N3IWF) , at step 211, AMF2 notifies SMF2 for each PDU Session that it has taken over the responsibility of the signaling path towards the UE. In some embodiments, AMF2 invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from AMF1 at step 205.

At step 212, the SMF2 responds with a Nsmf_PDUSession_UpdateSMContext Response. At this point, if an N2 connection between AMF2 and N3IWF can be successfully established, and the old AMF (AMF1) has indicated an existing NGAP UE association towards 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 the N3IWF. A new AMF UE NGAP ID may be allocated by the new AMF. Alternatively, if AMF1 and AMF2 are in the same AMF set, AMF2 can also use AMF1’s UE NGAP ID for non-3GPP access which was retrieved in step 205. In either case, N3IWF can send a Mobility Response message containing a new N3IWF UE NGAP ID to AMF2 to complete the process for UE mobility registration for non-3GPP access, in which case the remaining steps 213-218 described below need not be performed.

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

If the UE is in an idle state for non-3GPP access (i.e., the UE is not currently using the non-3GPP access technology for a PDU session) , then in response to the Notification message, at step 214, the UE moves to the 5GMM-IDLE mode for non-3GPP access and performs a mobility registration update procedure. 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 a Registration Request message to the N3IWF. At step 215, the N3IWF selects the new AMF based on the new GUAMI received and sends an N2 UE Initialization message to AMF2, which is identified by the new GUAMI, to establish the N2 connection between N3IWF and AMF2. In some embodiments, the N2 UE Initialization message contains the NAS PDU containing the Registration Request.

At step 216, in response to receiving the N2 UE Initialization message, the AMF2 sends an Initial UE context Request message to N3IWF. 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 a security key and algorithm, which are used to establish the UE’s security context in the N3IWF, and the mobility restriction list includes one or more forbidden areas and/or allowed areas for the UE. The NAS PDU is a transparent container to the N3IWF such 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 acknowledging successful receipt of the Initial UE Context Request message. At step 218, the N3IWF responds to the UE with an IKE_Auth_Response message. In this message, the Registration Accept message received at step 217 is included, which informs the UE that registration for non-3GPP access has been successfully completed.

As described above, the UE receives a Notification message from a new AMF utilizing a 3GPP access and, in response, the UE performs a registration procedure for non-3GPP access technologies and/or informs the N3IWF of the new AMF to continue a previously established non-3GPP access PDU session using the new AMF. Thus, a procedure for establishing a new N2 connection between the new AMF (AMF2) and the N3IWF is provided, thereby allowing UE mobility registration with a new AMF (AMF2) for a non-3GPP PDU session and/or continue a previously established non-3GPP access PDU session, in accordance with some embodiments of the invention.

In another embodiment, at step 214, instead of being in an IDLE mode during the registration procedure as described above, the UE may stay in a connected state (e.g., 5G MM-Connected state) to continue a PDU session utilizing the non-3GPP access technology (e.g., WiFi) . In this connected state, at step 214, the UE sends the IKE_Auth_Request message to the N3IWF as before, however, the message need only provide the new GUAMI to the N3IWF and need not 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 there is no need for the UE to provide updated UE information to the new AMF. As used herein, the term “registration procedure” refers to a process of establishing a connection between a non-3GPP access node (e.g., N3IWF) and a new AMF when the UE is in idle mode as determined by the non-3GPP access node, and also refers to updating the GUAMI associated with a new AMF when the UE remains in a connected state to continue a previously established non-3GPP access PDU session and has moved to a new location allocated to the new AMF.

Figure 3 illustrates a signal flow diagram of a mobility management and registration protocol 300 implemented in a 5G network utilizing at least two different RATs, in accordance with further embodiments of the invention. At step 301, a UE first registers with a first AMF (AMF1) utilizing an NG RAN (e.g., a 3GPP access technology in accordance with 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. AMF1 may also provide a periodic registration timer (e.g., T3512) to the UE. After the UE is registered with AMF1, the UE can send a request to establish a PDU session to a first SMF (SMF1) and a first UPF (UPF1) . In some embodiments, the request to establish the PDU session is generated and transmitted in accordance with sub-clause 4.3.2 of 3GPP TS 23.502.

At step 302, the UE registers with the same AMF (AMF1) via a N3IWF (e.g., a non-3GPP access technology as specified in sub-clause 4.12.2.2 of 3GPP TS 23.502) . In this procedure, AMF1 will not allocate a new 5G-GUTI to the UE, and the UE will continue to use the same 5G-GUTI for the non-3GPP access that was allocated above for the 3GPP access. Furthermore, AMF1 will provide a de-registration timer to the UE. After the UE is registered with AMF1 via the N3IWF, the UE can send a request to establish a PDU session via N3IWF to a second SMF (SMF2) and a second UPF (UPF2) as specified in the sub-clause 4.3.2 of 3GPP TS 23.502, for example.

As discussed above, if the UE moves to a new registration area associated with a different, second AMF (AMF2) , the UE must perform a registration procedure with AMF2 via NG RAN. At step 303, if the UE transitions to a 5G Mobility Management (MM) -IDLE mode in 3GPP access and travels to a different registration area, for example, the UE will perform a registration procedure with AMF2 with its registration type set to “mobility update. ” The UE sends a registration request message that includes its 5G-GUTI, the UE’s security capability, etc. to AMF2.

At step 304, if the UE's 5G-GUTI was included in the registration request message and the serving AMF has changed from AMF1 to AMF2 since the last registration procedure, the new AMF (AMF2) may invoke the Namf_Communication_UEContextTransfer service operation on the old AMF (AMF1) by sending a Registration Request NAS message, which may be integrity protected, to request the UE's Subscription Permanent Identifier (SUPI) and UE context information from AMF1.

At step 305, AMF1 responds to AMF2 with a Namf_Communication_UEContext Transfer message which contains the UE’s SUPI, context information, SMF information, etc. In some embodiments, the AMF UE Next Generation Application Protocol (NGAP) ID for non-3GPP access and N3IWF UE NGAP ID are included in the UE context information. At step 306, AMF2 notifies AMF1 that the registration of the UE in AMF2 is complete by invoking the Namf_Communication_RegistrationCompleteNotify service operation.

At step 307, AMF2 notifies SMF1 for each 3GPP access PDU Session assigned to the UE by SMF1 that it has taken over the responsibility of the signaling path towards the UE for each PDU session. In some embodiments, AMF2 invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from AMF1 at step 305, as described above. At step 308, the SMF1 responds with a Nsmf_PDUSession_UpdateSMContext Response.

At step 309, AMF2 notifies SMF2 for each non-3GPP access PDU Session that it has taken over the responsibility of the signaling path towards the UE. In some embodiments, AMF2 sends the Nsmf_PDUSession_UpdateSMContext Request signal to SMF2 using the SMF information received from AMF1 at step 305. At step 310, the SMF2 responds with a Nsmf_PDUSession_UpdateSMContext Response.

At step 311, AMF2 sends the Registration Accept message to the UE. In some embodiments, the Registration Accept message contains the UE’s 5G-GUTI, Registration Area and a Registration Result, wherein the 5G-GUTI includes a new GUAMI related with the AMF2. The Registration Result can be a value (e.g. a 0 or 1) that can be set to indicate that “non-3GPP access registration is required. ” Here, the Registration Result can be the same as the Notification message containing information indicating to the UE that a registration procedure is required for non-3GPP access, as described above for step 213. At step 312, the UE responds with the Registration Complete message. At step 313, the UE transitions to the 5GMM-IDLE mode for non-3GPP access and performs a mobility registration updating procedure. In some embodiments, the mobility registration updated procedure performed at step 313 may be the same or similar to step 302 discussed above, except that AMF2 replaces AMF1. In other embodiments, the mobility registration updating procedure at step 313 may be the same as or similar to steps 214-218 described above with respect to Figure 2.

Figure 4 illustrates a block diagram of a network node (NN) 400 that can be configured to implement the various methods described herein. In some embodiments, the NN 400 may be an AMF or include some of the 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 of the components or modules of a UE to perform UE functions, as described above in accordance with various embodiments. In further embodiments, the NN 400 may be an N3IWF or include some of the components or modules of an N3IWF to perform N3IWF functions, as described above in accordance with various embodiments.

As shown in Figure 4, the NN 400 includes a system clock 402, a processor 404, a memory 406, a transceiver 410 comprising a transmitter 412 and receiver 414, a power module 408, and a mobility registration module 420. The system clock 402 provides the 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 can include one or more processing circuits or modules such as a central processing unit (CPU) and/or any combination of general-purpose microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate array (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 can perform calculations or other manipulations of data.

The memory 406, which can include both read-only memory (ROM) and random access memory (RAM) , can provide instructions and data to the processor 404. A portion of the memory 406 can 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. The instructions (a.k.a., software) stored in the memory 406 can 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” means any type of instructions, whether referred to as software, firmware, middleware, microcode, etc. which can configure a machine or device to perform one or more desired functions or processes. Instructions can include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code) . The instructions, when executed by the one or more processors, cause the processing system to perform the various functions described herein.

The transceiver 410, which includes the transmitter 412 and receiver 414, allows the NN 400 to transmit and receive data to and from a remote device (e.g., a Sat-gNB) . An antenna 440 is electrically coupled to the transceiver 410. In some embodiments, the antenna may be a phase-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, the antenna 450 can be a multi-antenna array that can form a plurality of beams each of which points in a distinct 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. In accordance with 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 signals as described in steps 213-218 above. In some embodiments, the mobility registration module 420 can be implemented as software (i.e., computer executable instructions) stored in a non-transitory computer-readable medium that when executed by 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 can include a data bus and, for example, a power bus, a control signal bus, and/or a status signal bus in addition to the data bus. It is understood that the modules of the NN 400 can be operatively coupled to one another using any suitable techniques and mediums.

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 by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand exemplary features and functions of the present disclosure. Such persons would understand, however, that the present disclosure is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can 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 is also understood that any reference to an element herein using a designation such as "first, " "second, " and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.

Additionally, a person having ordinary skill in the art would 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, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

A person of ordinary skill in the art 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 can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software" or a "software module) , or any combination of these techniques.

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 techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure. In accordance with various embodiments, a processor, device, component, circuit, structure, machine, module, etc. can be configured to perform one or more of the functions described herein. The term “configured to” or “configured for” as used herein with respect to a specified operation or function refers 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, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A processor programmed to perform the functions herein will become a specially programmed, or special-purpose processor, and can 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 to perform the functions described herein.

If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by 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 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 associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would 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 associated functions according embodiments of the present disclosure.

Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.

Claims

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

transmitting a first message to a user equipment device (UE) , wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3GPP) access technology.
The method of claim 1, wherein the notification further includes an indication that registration is required for non-3GPP access.
The method of claim 1, wherein the first message further includes identification information that identifies the first network node.
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-3GPP access technology.
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 acknowledging successful receipt of the UE context setup information.
The method of claim 5 further comprising transmitting a registration accept message to the second network node, for forwarding to the UE.
A method for mobility registration performed by a user equipment device (UE) , the method comprising:

receiving a first message from a first network node, wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3GPP) access technology.
The method of claim 7, wherein the notification further includes an indication that registration is required for non-3GPP access.
The method of claim 7, wherein the first message further includes identification information that identifies the first network node.
The method of claim of claim 7, further comprising:

transmitting a second message to a second network node, wherein the second message contains identification information that identifies the first network node.
The method of claim 10, wherein the second message further includes a registration request message to be forwarded to the first network node.
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.
A non-transitory computer-readable medium having stored thereon computer-executable instructions that when executed carry out the method of any one of claims 1 through 12.
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 device (UE) , wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3GPP) access technology.
The first network node of claim 14, wherein the notification further includes an indication that registration is required for non-3GPP access when the UE is in an idle state for non-3GPP access.
The first network node of claim 14, wherein the first message further includes identification information that identifies the first network node.
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-3GPP access technology.
The first network node of claim 17, wherein:

the transceiver is further configured to:

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

receive a UE context setup response message from the second network node acknowledging successful receipt of the UE context setup information.
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.
A user equipment device (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, wherein the first message includes a notification that a registration procedure is required over a non-third generation partnership project (non-3GPP) access technology.
The UE of claim 20, wherein the notification further includes an indication that registration is required for non-3GPP access.
The UE of claim 20, wherein the first message further includes identification information that identifies the first network node.
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 that identifies the first network node.
The UE of claim 23, wherein the second message further includes a registration request message to be forwarded to the first network node.
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 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.