Method and system for handling registration and session management in a wireless communication system

Abstract

Embodiments of the present invention implement a method for processing registration and session management in a wireless communication system. The method includes: registering with a first core network entity by a user equipment (UE) through a 3GPP access network and a non-3GPP access network. In addition, the method includes: when a periodic timer of the UE expires in an OOS state, triggering a registration procedure to a second core network by the UE through the 3GPP access network. In addition, the method includes receiving a non-access stratum (NAS) message by the UE through the 3GPP access network, the NAS message indicating registration with the second core network entity for the non-3GPP access network. In addition, the method includes restarting the registration procedure to register with the second core network entity again for the non-3GPP access through the non-3GPP access network.

Description

[0001] This application is a divisional application of a patent application with an application date of August 9, 2018, application number 201880039263.X, and titled “Method and system for processing registration and session management in a wireless communication system”. Technical Field

[0002] The present application relates to a wireless communication system, and more particularly to a method and system for processing registration and session management of non-3GPP access in a wireless communication system. Background Art

[0003] In order to meet the demand for wireless data services that has increased since the deployment of the fourth generation (4G) communication system, efforts have been made to develop improved fifth generation (5G) or pre-5G communication systems. 5G or pre-5G communication systems are also called "super 4G networks" or "post-long term evolution (LTE) systems". 5G communication systems are considered to be implemented in higher frequency bands (millimeter waves) (e.g., 60 GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, development for system network improvements is underway based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. In 5G systems, hybrid frequency shift keying (FSK) and Fehertz quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) have been developed as advanced access technologies.

[0004] The Internet, a human-centric connected network where humans generate and consume information, is evolving towards the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, which is a combination of IoT technology and big data processing technology through connection with cloud servers. Since technical elements such as "sensing technology", "wired / wireless communication and network architecture", "service interface technology" and "security technology" are required for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), etc. have been studied recently. This IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated by connected things. IoT can be applied to various fields including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart instruments and advanced medical services through the integration and combination between existing information technology (IT) and various industrial applications.

[0005] Correspondingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications can be implemented through beamforming, MIMO, and array antennas. The use of cloud RAN as an application of the above-mentioned big data processing technology can also be regarded as an example of the fusion of 5G technology and IoT technology.

[0006] As described above, various services can be provided according to the development of wireless communication systems, and thus a method for easily providing such services is required. Summary of the invention

[0007] Technical issues

[0008] In the case where a user equipment (UE) is registered to the same network via 3GPP access and non-3GPP access and the periodic timer of the UE expires in an out-of-service state (OOS) (in 3GPP access), there are no various mechanisms for non-3GPP access handling in a 5G network in existing methods and systems. Therefore, it is desirable to address the above-mentioned or other disadvantages or at least provide a useful alternative.

[0009] Technical Solution

[0010] The present application provides a method for processing registration and session management in a wireless communication system. The method includes registering, by a user equipment (UE), with a first core network entity through a 3GPP access network and a non-3GPP access network. In addition, the method includes: when a periodic timer of the UE expires in an OOS state, triggering, by the UE, a registration procedure with a second core network through the 3GPP access network.

[0011] Advantageous Effects of the Invention

[0012] A main object of the embodiments herein is to provide a method and system for handling registration and session management of non-3GPP access in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The present invention is illustrated in the accompanying drawings, in which the same reference numerals indicate corresponding parts in different drawings. The embodiments of the present invention will be better understood by the following description with reference to the accompanying drawings, in which:

[0014] Figure 1 shows a situation where the access management function (AMF) has deleted the context of the UE 100 for 3GPP access;

[0015] Figure 2 A timing diagram is shown according to an embodiment of the present invention, in which the AMF sends a Registration Reject to indicate that the UE context is not available for 3GPP only (e.g., implicitly detached);

[0016] Figure 3 A timing diagram is shown in which the AMF sends a Non-Access Stratum (NAS) message (e.g., Registration Reject) with implicit separation for 3GPP access and non-3GPP access according to an embodiment of the present invention;

[0017] Figure 4 It shows the situation where the second AMF cannot obtain the context from the first AMF via communication_UE_context_transfer;

[0018] Figure 5 A timing diagram according to an embodiment of the present invention is shown, in which the AMF will send a NAS message (e.g., Registration Reject) with a cause such as implicit detach, which indicates to the UE that the UE will initiate a registration procedure through both 3GPP access and non-3GPP access;

[0019] Figure 6 It shows the situation where the second AMF cannot successfully perform N2AP UE-TNLA binding using the N3IWF interface;

[0020] Figure 7 A timing diagram according to an embodiment of the present invention is shown, in which the second AMF sends a registration accept / registration reject with an indication of registering for a non-3GPP access to the UE;

[0021] Figure 8 The case where a UE according to an embodiment of the present invention is attached to different AMFs on the same PLMN is shown;

[0022] Fig. 9 A timing diagram according to an embodiment of the present invention is shown, in which a UE performs a registration of a "mobility registration update" type in a 5G core network (5GC) using two indications, one of which is a 5G-GUTI mapped from a 4G-GUTI and the other indication should be explained to an AMF (e.g., a second AMF), so that the second AMF knows that if the UE is registered via non-3GPP access, the second AMF may obtain the non-3gpp access from an old AMF (e.g., a first AMF) by including other identifiers (e.g., a GUTI of another 5G for non-3gpp access);

[0023] Fig.10 It shows a case where the AMF according to an embodiment of the present invention sends a notification message indicating that the AMF wants to obtain a response access;

[0024] Fig.11 A timing diagram according to an embodiment of the present invention is shown, in which the UE sends a service request, otherwise a notification rejection including all non-3GPP PDUs that cannot be activated via 3GPP is sent;

[0025] Fig.12 The case of activating a service request (including a list of non-3GPP PDUs) via 3GPP is shown;

[0026] Fig.13 The case of activating a service request (including a list of non-3GPP PDUs) through 3GPP according to an embodiment of the present invention is shown;

[0027] Fig.14 and Fig.15 is a timing diagram illustrating inconsistent behavior of the AMF when service requests arrive in different orders at different times;

[0028] Fig.16 A timing diagram according to an embodiment of the present invention is shown, in which the UE does not trigger a service request on a non-3GPP until the service request on the 3GPP ends;

[0029] Fig.17 A timing diagram according to an embodiment of the present invention is shown, in which the UE 100 does not trigger a service request on 3GPP in response to a paging indicating a non-3gpp access until the 3GPP service request on non-3GPP ends;

[0030] Fig.18 A timing diagram is shown according to an embodiment of the present invention, in which the UE ignores paging through a non-3gpp access when the UE's non-3gpp is already in connected mode;

[0031] Fig.19A timing diagram is shown according to an embodiment of the present invention, in which the UE will abort the service request procedure on 3GPP and will continue the service request through Wi-Fi;

[0032] Fig. 20 A timing diagram according to an embodiment of the present invention is shown in which the AMF may ignore the service request (in response to a non-3gpp paging) if the same PDU is already connected (or active) via a non-3GPP access (non-3gpp connected CM state);

[0033] Fig.21 A timing diagram is shown according to an embodiment of the present invention, in which the AMF simultaneously receives a service request through 3GPP (in response to non-3gpp paging) and a service request from Wi-Fi;

[0034] Fig. 22 shows a timing diagram according to an embodiment of the present invention, in which the AMF will use 3GPP access to send a new paging message;

[0035] Fig.23 is a timing diagram according to an embodiment of the present invention, in which the network does not control the moving of a specific PDN to a specific RAT;

[0036] Fig.24 is a block diagram of a UE according to an embodiment of the present invention;

[0037] Fig.25 is a block diagram of an AMF according to an embodiment of the present invention;

[0038] Figures 26 to 30 is a flowchart illustrating various steps implemented by a UE for processing registration and session management in a wireless communication system according to an embodiment of the present invention; and

[0039] Figure 31 to Figure 36 is a flowchart illustrating various steps implemented by the AMF for processing registration and session management in a wireless communication system according to an embodiment of the present invention;

[0040] Fig.37 is a block diagram illustrating an access management function (AMF) entity according to another exemplary embodiment of the present disclosure;

[0041] Fig.38 is a block diagram illustrating a UE according to another exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0042] Embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes registering with a first core network entity by a user equipment (UE) through a 3GPP access network and a non-3GPP access network. In addition, the method includes: when a periodic timer of the UE expires in an OOS state, the UE triggers a registration procedure to a second core network entity through the 3GPP access network. In addition, the method includes receiving, by the UE through the 3GPP access network, a NAS message (e.g., a registration acceptance or registration rejection message or a detachment message) with an indication of registering a non-3GPP access network to the second core network entity. In addition, the method includes restarting the registration procedure to register the non-3GPP access to the second core network entity again through the non-3GPP access.

[0043] In an embodiment, the first core network entity decides to send the indication when the first core network entity receives from the UE a request with an indication to obtain context from two different core network nodes and context transfer from one of the core network nodes fails.

[0044] In an embodiment, the registration procedure for non-3GPP access is restarted upon expiration of the retry timer, and the registration procedure is restarted to create an N2 interface between the N3IWF and the second AMF entity.

[0045] In an embodiment, the first core network entity comprises one of a mobility management entity (MME) in a fourth generation (4G) network or an access management function (AMF) in a fifth generation (5G) network.

[0046] In an embodiment, when the non-3GPP access context transfer from the first core network entity to the second core network entity is unsuccessful, the second core network entity instructs the UE to register the non-3GPP access network.

[0047] Embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes receiving a registration procedure from a UE via a 3GPP access network by a second AMF entity. The UE registers to the 3GPP access network via an MME and registers to a non-3GPP access network via a first AMF entity. In addition, the method includes obtaining a context from the MME by the second AMF entity and obtaining a non-3GPP context from the first AMF entity. In addition, the method includes sending a NAS message (e.g., a registration acceptance or registration rejection or a network-initiated detachment message) having an indication to register the non-3GPP access network to the second AMF entity again by the second AMF entity. In addition, the method includes: receiving an updated registration procedure by the second AMF entity to register the UE for the non-3GPP access network again, and creating an N2 interface between the N3IWF and the second AMF entity.

[0048] The embodiments of this document disclose a method for processing registration and session management in a wireless communication system. The method includes registering with a mobile management entity (MME) by a UE through a 3GPP access network, and registering with a first AMF entity through a non-3GPP access network. In addition, the method includes triggering a registration procedure from the MME to a second AMF entity by the UE. In addition, the method includes configuring an indication by the UE to instruct the second AMF entity to obtain a non-3gpp access from the first AMF entity. In addition, the method includes sending a GUTI maintained on a non-3GPP access by the UE to the second AMF entity to bind the N2AP UE-TNLA to the N3IWF interface, i.e., the UE must use the GUTI received from the second AMF through the 3GPP access for routing purposes of non-3GPP access (i.e., to the N3IWF), but the registration message should contain a GUTI identifying the first AMF so that the message reaches the second AMF and the second AMF can obtain the context from the first AMF.

[0049] Embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes registering with an AMF entity for 3GPP access context and non-3GPP access context by a UE. In addition, the method includes detecting, by the UE, an inter-system change from a fifth generation (5G) network to a fourth generation (4G) network through a 3GPP access network. In addition, the method includes: configuring, by the UE, the transmission of a 3GPP access context from an AMF entity to an MME entity, and continuously maintaining a non-3GPP access context with the AMF through an N3IWF for non-3GPP access.

[0050] Embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes receiving, by a UE, a paging message indicating a non-3GPP access from a 3GPP access network. In addition, the method includes detecting, by the UE, that a connection management (CM) state of the non-3GPP access is in a connected mode or in the process of entering a connected mode. In addition, the method includes performing one of the following operations: ignoring the paging message indicating the non-3GPP access, or sending a service request message without indicating an allowed PDU session state IE to an access management function (AMF) entity.

[0051] Embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes receiving a service request message from a UE via a non-3GPP access network by an AMF entity. In addition, the method includes activating a PDU on the non-3GPP access network by the AMF entity. In addition, the method includes receiving a service request message by the AMF entity without indicating a PDU session identifier. In addition, the method includes sending a radio resource control (RRC) connection release message to the UE by the AMF entity.

[0052] The embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes receiving, by a UE, one of a paging message indicating a non-3GPP access or a notification message indicating a non-3GPP access from a 3GPP access network. In addition, the method includes detecting, by the UE, that the CM state of the non-3GPP access network is in a CM idle state. The UE responds with a service request message including an allowed PDU session state IE. In addition, the method includes detecting, by the UE, that a non-3GPP access network service is available and that the non-3GPP access network moves to a connected mode. In addition, the method includes performing one of the following operations: before the service request process for the 3GPP access network is completed, a service request message for a PDU that is allowed to be reactivated in the 3GPP access network is not triggered through the non-3GPP access network; or a service request message for a PDU that is not allowed to be activated through the 3GPP access network is triggered; or based on uplink data, a service request message for a PDU that is not allowed to be activated based on uplink data through the 3GPP access network is triggered.

[0053] The embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes receiving a paging message indicating non-3GPP access by a UE from a 3GPP access network. In addition, the method includes detecting by the UE that a service request message sent to an AMF entity together with an allowed PDU session status IE has expired and a retry timer has been started. In addition, the method includes detecting by the UE that the CM state of the non-3GPP access network has moved to a connected mode. The UE stops the retry timer and terminates the service request process on the 3GPP access network. In addition, the method includes sending a service request message including an uplink data status information element (IE) to the AMF entity by the UE through the non-3GPP access network, wherein a PDU associated with the non-3GPP access network that is allowed to move to the 3GPP access network is included in the uplink data status IE. Alternatively, the AMF entity terminates paging with a non-3GPP access type and directly establishes a dedicated radio bearer (DRB) through the non-3GPP access network.

[0054] Embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes sending a paging message indicating non-3GPP access to a UE by an AMF entity through a 3GPP access network. In addition, the method includes the AMF entity receiving a service request message from the UE through the non-3GPP access network. In addition, the method includes activating a PDU on the non-3GPP access network at the AMF entity. In addition, the method includes processing the service request message at the AMF entity and not activating the PDU of the non-3GPP access network through the 3GPP access network, wherein the PDU is activated through the non-3GPP access network.

[0055] Embodiments of the present invention disclose a method for processing registration and session management in a wireless communication system. The method includes sending a paging message indicating non-3GPP access to a UE by an AMF entity through a 3GPP access network. In addition, the method includes: the AMF entity receives a service request message from the UE through the non-3GPP access network; and detects that the AMF entity is in the process of activating a PDU on the 3GPP access network. In addition, the method includes: processing the service request message at the AMF entity; terminating the activation of a PDU of a non-3GPP access network through the 3GPP access network; and activating a PDU through the non-3GPP access network.

[0056] Embodiments of the present invention disclose a UE for processing registration and session management in a wireless communication system. The UE includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to register with a first core network entity through a 3GPP access network and a non-3GPP access network. In addition, the context matching controller is configured to trigger a registration procedure to a second core network entity through the 3GPP access network when a periodic timer of the UE expires in an OOS state. In addition, the context matching controller is configured to receive a NAS message (e.g., a registration acceptance or registration rejection or separation message with a non-3GPP indication) having an indication of registering a non-3GPP access network to a core network AMF entity again through the 3GPP access network. In addition, the context matching controller is configured to restart the registration procedure to register a non-3GPP access to the second core network entity again through the non-3GPP access network.

[0057] Embodiments of the present invention disclose an AMF entity for processing registration and session management in a wireless communication system. The AMF entity includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to receive a registration program from a UE via a 3GPP access network. The UE registers to the 3GPP access network via an MME and registers to a non-3GPP access network via another AMF entity. In addition, the context matching controller is configured to obtain a context from the other AMF entity. In addition, the context matching controller is configured to send a NAS message (e.g., a registration acceptance or rejection message) with an indication of registering the non-3GPP access network to the AMF entity again. In addition, the context matching controller is configured to receive an update registration program to register the UE for the non-3GPP access network again and create an N2 interface between the N3IWF and the second AMF entity.

[0058] Embodiments of the present invention disclose a UE for processing registration and session management in a wireless communication system. The UE includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to register with an MME through a 3GPP access network and to register with a first AMF entity through a non-3GPP access network. In addition, the context matching controller is configured to trigger an update registration procedure from the MME to a second AMF entity. In addition, the context matching controller configures a GUTI mapped from the 3GPP access network and an indication that the second AMF entity obtains non-3gpp access from the first AMF entity. In addition, the context matching controller is configured to send a GUTI to the second AMF entity to bind the N2AP UE-TNLA to the N3IWF interface.

[0059] The embodiments of this document disclose an AMF entity for processing registration and session management in a wireless communication system. The core network entity (i.e., AMF entity) in 5GS is capable of supporting 3GPP access and non-3GPP access contexts. When a system-to-system change occurs in the 4G network, the UE registers with the MME. In the prior art for context transfer between traditional RATs, the complete UE context is transferred to the target core network node, but the problem here is that the target core network node MME does not support non-3GPP access contexts, so when the UE moves to the 4G RAT, the non-3GPP access context will be lost. In order to solve this problem, a solution is proposed. In the proposed method, the UE includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to register 3GPP access contexts and non-3GPP access contexts with the AMF entity. The context matching controller is configured to detect inter-system changes from a 5G network to a 4G network through a 3GPP access network. The context matching controller configures the transmission of the 3GPP access context from the AMF entity to the MME entity, and continuously maintains the non-3GPP access context with the AMF through the N3IWF.

[0060] Embodiments of the present invention disclose a UE for processing registration and session management in a wireless communication system. The UE includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to receive a paging message indicating a non-3GPP access from a 3GPP access network, and detect that the CM state of the non-3GPP access is in a connected mode or in the process of entering a connected mode. In addition, the context matching controller is configured to perform one of the following operations: ignoring the paging message indicating the non-3GPP access, or sending a service request message without including an allowed PDU session status IE to the AMF entity.

[0061] The embodiments of the present invention disclose an AMF entity for processing registration and session management in a wireless communication system. The AMF entity includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to receive a service request message from a UE via a non-3GPP access network. In addition, the context matching controller is configured to activate a PDU on the non-3GPP access network and receive a service request message that does not indicate a PDU session identifier. In addition, the context matching controller is configured to send an RRC connection release message to the UE.

[0062] The embodiments of the present invention disclose a UE for processing registration and session management in a wireless communication system. The UE includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to receive one of a paging message indicating a non-3GPP access or a notification message indicating a non-3GPP access from a 3GPP access network. The context matching controller is configured to detect that the CM state of the non-3GPP access network is in a CM idle state and a connected mode. The UE responds with a service request message including an allowed PDU session state IE. The context matching controller is configured to detect that a non-3GPP access network service is available and that the non-3GPP access network moves to a connected mode. The context matching controller is configured to perform one of the following operations: before the service request process for the 3GPP access network is completed, a service request message for a PDU that is allowed to be reactivated in a 3GPP access network is not triggered through a non-3GPP access network; or a service request message for a PDU that is not allowed to be activated through a 3GPP access network is triggered; or based on uplink data, a service request message for a PDU that is not allowed to be activated based on uplink data through a 3GPP access network is triggered.

[0063] The embodiments of the present invention disclose a UE for processing registration and session management in a wireless communication system. The UE includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to receive a paging message indicating non-3GPP access from a 3GPP access network, and detect that a service request message sent to an AMF entity together with an allowed PDU session status IE has expired and a retry timer has been started. The context matching controller is configured to detect that the CM state of the non-3GPP access network is in a connected mode. The UE stops the retry timer and terminates the service request process on the 3GPP access network. The context matching controller is configured to send a service request message including an uplink data status information element (IE) to the AMF entity through the non-3GPP access network, wherein the PDU associated with the non-3GPP access network that is allowed to move to the 3GPP access network is included in the uplink data status IE. Alternatively, paging with a non-3GPP access type is performed in the AMF entity, and a dedicated radio bearer (DRB) is directly established through the non-3GPP access network.

[0064] The embodiments of the present invention disclose an AMF entity for processing registration and session management in a wireless communication system. The AMF entity includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to send a paging message indicating non-3GPP access to a UE through a 3GPP access network. The context matching controller is configured to receive a service request message from the UE through a non-3GPP access network and activate a PDU on the non-3GPP access network. The context matching controller is configured to process the service request message and not activate a PDU of a non-3GPP access network through a 3GPP access network, wherein the PDU is activated through the non-3GPP access network.

[0065] The embodiments of the present invention disclose an AMF entity for processing registration and session management in a wireless communication system. The AMF entity includes a context matching controller coupled to a memory and a processor. The context matching controller is configured to send a paging message indicating non-3GPP access to a UE through a 3GPP access network. The context matching controller is configured to receive a service request message from the UE through a non-3GPP access network, and detect that the AMF entity is in the process of activating a PDU on the 3GPP access network. The context matching controller is configured to process the service request message and not activate a PDU of a non-3GPP access network through a 3GPP access network, wherein the PDU has been activated through the non-3GPP access network.

[0066] Embodiments of this document disclose a method for handling registration and session management in a wireless communication system. In many cases, it is beneficial to limit the use of PDU sessions to specific accesses or RATs. For example, the network can be configured to use IOT PDU sessions only in non-3GPP accesses because IOT PDU sessions are less expensive from an operational perspective, so the network can manage them. Therefore, the network can configure this information in the UE, or can provide a message indicating which access or RAT a specific PDU session must operate on. In the proposed method, the method includes storing information related to the PDU session by the UE. The PDU session belongs to at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT, 5G RAT, etc. In addition, the method includes activating a PDU session for at least one of 3GPP access, non-3GPP access, 3GRAT, 4G RAT, and 5G RAT by the UE based on the stored information. In addition, the method includes: rejecting the activation request by the core network entity; and sending a reason indicating that the UE is not allowed to activate the PDU session when the UE triggers the PDU session activation for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT. The core network entity provides information that the PDU session of at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT is allowed to be activated. If the network indicates to the UE that the PDU session should not be run in a specific RAT or access, the UE can search for PDU sessions activated through other accesses or RATs, or perform PLMN selection registration on other PLMNs, and the other PLMNs can provide services for the specific PDU session to the UE through the same access or RAT on which the UE previously received the rejection reason.

[0067] Embodiments of the present invention disclose a system for processing registration and session management in a wireless communication system. The system includes a UE and a core network entity. The UE is configured to store information related to a PDU session. The PDU session belongs to at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT. The UE is configured to activate a PDU session for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT based on the stored information. The core network entity is configured to reject the activation request and send a reason indicating that the UE is not allowed to activate the PDU session when the UE triggers the PDU session activation for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT. The core network entity provides information about the PDU session that is allowed to be activated for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT.

[0068] In an embodiment, the UE indicates when activating a PDU Session whether the UE policy allows reactivation of the PDU Session via non-3GPP access. The network uses this information to determine if the UE must be paged with the access type of the non-3GPP access if it is in IDLE mode for non-3GPP access. If the UE policy indicates that activation of a specific PDU Session via 3GPP access is allowed and there is only downlink data, the AMF will page with the non-3GPP access type.

[0069] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the embodiments herein will be better understood and learned. However, it should be understood that although the following description indicates preferred embodiments and many specific details thereof, they are illustrative and not restrictive. Without departing from the spirit of the present invention, many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all of these modifications.

[0070] Invention method

[0071] The embodiments herein and their various features and beneficial details are explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily confuse the embodiments herein. Moreover, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" used herein refers to a non-exclusive or. The examples used herein are intended only to facilitate an understanding of the ways in which the embodiments herein can be practiced, and to further enable those skilled in the art to practice the embodiments herein. Therefore, the examples should not be interpreted as limiting the scope of the embodiments herein.

[0072] As is customary in the art, embodiments may be described and illustrated according to the blocks that perform the one or more functions described. These blocks may be referred to herein as units or modules, etc., which are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, storage circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may be optionally driven by firmware and software. The circuit may, for example, be contained in one or more semiconductor chips, or be contained on substrate supports such as printed circuit boards, etc. The circuits constituting the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware that performs some functions of the block and a processor that performs other functions of the block. Without departing from the scope of the present invention, each block of the embodiment may be physically divided into more than two interacting and discrete blocks. Similarly, without departing from the scope of the present invention, the blocks of the embodiment may be physically combined into more complex blocks.

[0073] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments proposed herein are not limited by the accompanying drawings. In this way, except for those specifically listed in the accompanying drawings, the present disclosure should be interpreted as extending to any changes, equivalent forms and substitutions. Although the terms first, second, etc. can be used herein to describe various elements, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.

[0074] Consider a situation where a user equipment (UE) registers to the same network through 3GPP access as well as non-3GPP access, and the periodic timer of the UE (in 3GPP access) expires in an out-of-service state (OOS). After a period of time, when the UE resumes service, the UE triggers a periodic registration in the 5G network, at which time the access management function (AMF) entity has deleted the context of the UE for 3GPP access. In addition, various mechanisms for non-3GPP access handling in the 5G network are not available in the existing methods and systems.

[0075] It would therefore be desirable to address the above-mentioned or other disadvantages or at least provide a useful alternative.

[0076] Embodiments of the present invention implement a method for processing registration and session management in a wireless communication system. The method includes registering with a first core network entity by a user equipment (UE) through a 3GPP access network and a non-3GPP access network. In addition, the method includes: when a periodic timer of the UE expires in an OOS state, the UE triggers a registration procedure to a second core network entity through the 3GPP access network. In addition, the method includes receiving a NAS message (e.g., a registration acceptance or rejection message) by the UE through the 3GPP access network, the NAS message indicating registration with the second core network entity for a non-3GPP access network. In addition, the method includes restarting the registration procedure to register with the second core network entity again for a non-3GPP access.

[0077] Referring now to the drawings and more particularly to the Figure 2 , Figure 3 , Figure 5 , Figures 7 to 9 , Fig.11 , Fig.13 and Figures 16 to 36 , wherein like reference numerals indicate corresponding features throughout the several views, preferred embodiments are shown.

[0078] Figure 1 A situation is shown where the AMF 200 has deleted the context of the UE 100 for 3GPP access.

[0079] Reference Figure 1 , consider the following case: at 1-3, UE 100 registers to the same network through 3GPP access as well as non-3GPP access, and the periodic timer (in 3GPP) of UE 100 expires in the out-of-service state (OOS). At 4-6, after a period of time, when UE 100 resumes service, UE 100 triggers registration in 5G, at which time, AMF 200 has deleted the context of UE 100 for 3GPP access. In this case, the behavior of AMF 200 is currently undefined.

[0080] Figure 2 A timing diagram according to an embodiment of the present invention is shown, in which the AMF 200 sends a Registration Reject to indicate that the UE context is not available for 3GPP only (e.g., implicitly detached). Consider a situation where, at 1-3, the UE 100 is registered to the same network via 3GPP access as well as non-3GPP access, and the periodic timer (in 3GPP) of the UE 100 expires in the OOS state. At 4-6, after a period of time, when the UE 100 resumes service, the UE 100 triggers a (periodic) registration in the 5G network. In this case, the AMF 200 has deleted the context of the UE 100 for 3GPP access. Therefore, the AMF 200 should send an indication at 7 that the 3GPP context is not available (e.g., implicitly detached), and the UE 100 will think that it is still attached to the non-3GPP and retry the registration request via 3GPP access.

[0081] Figure 3 A timing diagram according to an embodiment of the present invention is shown, in which the AMF 200 sends a non-access stratum (NAS) message (e.g., a Registration Reject or Detach message) with implicit separation for 3GPP access and non-3GPP access.

[0082] At 1-3, when UE 100 has been registered to the same network through 3GPP access and non-3GPP access, the periodic timer of UE 100 expires when UE 100 is in OOS of 3GPP. At 4-6, after a period of time, when UE 100 resumes service, UE 100 triggers periodic registration in the 5G network. At this time, AMF 200 has deleted the context of UE 100 for 3GPP access. At 7, AMF 200 should send NAS messages for 3GPP access and non-3GPP access (e.g., registration reject with implicit detach or detach message). UE 100 will consider that the context of both accesses is unavailable, and UE 100 will re-trigger the registration request on 3GPP and non-3GPP.

[0083] Figure 4 It shows the situation where the second AMF 200b cannot obtain the context from the first AMF 200a via communication_UE_context_transfer.

[0084] Reference Figure 4, the UE 100 has registered to the same network through 3GPP access and non-3GPP access through the same AMF (i.e., the first AMF 200a), and the UE 100 moves to a new AMF (i.e., the second AMF 200b) and a mobility registration is triggered through 3GPP access. However, the second AMF 200b cannot obtain the context from the first AMF 200a via communication_UE context transfer (Communication_UE Context Transfer), and how the second AMF 200b will manage the registration contexts for both 3GPP access and non-3GPP access is not handled in 1-4.

[0085] Figure 5 A timing diagram according to an embodiment of the present invention is shown, in which the AMF 200 will send a NAS message (e.g., Registration Reject) with a cause (e.g., Implicit Detach, etc.) to the UE 100, which indicates to the UE 100 that the UE 100 should initiate a registration procedure on both 3GPP access and non-3GPP access.

[0086] Reference Figure 5 , the UE 100 has registered to the same network through the same AMF (i.e., the first AMF 200a) through 3GPP access and non-3GPP access, or the UE 100 is registered with the MME 400 through 3GPP access and with the AMF (i.e., the first AMF 200a) for non-3GPP access, and the UE 100 moves to a new AMF (i.e., the second AMF 200b) and triggers mobility registration through 3GPP access. However, the second AMF 200b cannot obtain the context from the first AMF 200a via Communication_UE context transfer. In this case, at 1-5, the second AMF 200b may send a NAS message (e.g., a registration reject or deregistration message, etc.) with a cause (e.g., implicit detach or re-registration, etc.) to the UE 100, which indicates to the UE 100 that the UE 100 should initiate a registration procedure on both 3GPP access and non-3GPP access.

[0087] Figure 6 It shows the situation where the second AMF 200b cannot successfully perform N2AP UE-TNLA binding using the N3IWF interface 300.

[0088] Figure 7 A timing diagram according to an embodiment disclosed herein is shown, in which the second AMF 200b sends a Registration Accept / Registration Reject with an indication to register for non-3GPP access to the UE 100.

[0089] Reference Figure 7 , consider that at 1-2, the UE 100 has registered to the same network through the same AMF (i.e., the first AMF 200a) via 3GPP access and non-3GPP access, or, the UE 100 has registered with the first AMF 200a via non-3GPP access and with the MME 400 via 3GPP access. At 2-7, the UE 100 moves to a new AMF (i.e., the second AMF 200b) and triggers mobility registration via 3GPP access. The second AMF 200b is able to successfully acquire the context from the first AMF 200a via communication_UE context transfer, alternately, via non-3GPP access, the context acquisition fails. The second AMF 200b is unable to successfully perform N2AP UE-TNLA binding (N2AP UE-TNLA-binding) with the N3IWF interface 300. The second AMF 200b will send a Registration Accept / Registration Reject or Detach message indicating to register again for non-3GPP access (with a reason to register again for non-3GPP access) to the UE 100. The UE 100 will consider that it is not currently registered with the second AMF 200b for non-3GPP access, and initiate a NAS message (for example Registration Procedure or Service Request) over the non-3GPP access to establish a non-3GPP access context and recreate the N2 interface between the N3IWF 300 and the AMF 200 (or it may do so after the retry timer expires).

[0090] Alternatively, the UE 100 may run a retry timer and restart the registration procedure via 3GPP access, and with the registration message, the second AMF 200b will attempt to create the N2AP UE-TNLA binding again. Alternatively, the second AMF 200b will provide a registration acceptance to the UE 100 and run a retry timer, after which the second AMF 200b will retry to create the N2 interface with the N3IWF 300, which is transparent to the UE 100.

[0091] The purpose of the 5GS Registration Result information element is to specify the result of the registration procedure. The encoding of the 5GS Registration Result information element is shown in Tables 1 and 2. The 5GS Registration Result is a type 4 information element with a length of 3 octets. For code point 3GPP access, the UE 100 will assume that it has only self-registered for 3GPP access and has re-initiated the registration procedure for non-3GPP access. For code points 3GPP access and non-3GPP access, the UE 100 will assume that the context transfer from the non-3GPP access has been successful and that the UE 100 has registered to both 3GPP and non-3GPP access using the same AMF.

[0092]

[0093] Table 1

[0094]

[0095] Table 2

[0096] Figure 8 A situation is shown where the UE 100 is attached to different AMFs on the same PLMN according to the embodiments disclosed herein.

[0097] Reference Figure 8 , consider a UE 100 attached to an MME 400 via 4G radio and to a first AMF 200a via a non-3GPP access. During mobility, the UE 100 moves from the MME 400 to a second AMF 200b and is provided with a mapped GUTI by 4G in a NAS message (e.g., a Registration Request message). Based on the mapped Globally Unique Temporary Identifier (GUTI), the second AMF 200b will obtain a context from the MME 400, but since the context of the second AMF 200b will not be obtained, the first AMF 200a (to which the UE 100 is attached via a non-3GPP access) is located on the same PLMN. This will result in the UE 100 being attached to a different AMF of the same PLMN, and missing paging messages for the non-3GPP access.

[0098] Fig. 9A timing diagram according to an embodiment of the present invention is shown, in which the UE 100 performs a "mobility registration update" type registration in the 5G core network (5GC) using two indications, one of which is a 5G-GUTI mapped from a 4G-GUTI and should be indicated to the AMF (e.g., a second AMF 200b), so that the second AMF 200b knows that if the UE 100 is registered via non-3GPP access, the second AMF 200b may obtain the non-3gpp access from the old AMF (e.g., the first AMF 200a) by including an additional identifier (e.g., an additional 5G GUTI for non-3gpp access).

[0099] Reference Fig. 9 For mobility from EPC to 5GC, the UE 100 performs a registration procedure in the 5GC using the 5G-GUTI mapped from the 4G-GUTI, and if the UE 100 is registered for non-3GPP access, the UE 100 should include an additional 5G GUTI. Based on an indication or identifier (in the example, an additional GUTI) that also indicates the required TLNA binding (non-3GPP access registration), the new AMF will obtain the context from the old AMF and transfer the context from the old AMF to the new AMF, and the new AMF will also perform N2AP UE-TNLA-binding with the N3IWF interface 300.

[0100] Fig.10 It shows the case where the AMF 200 sends a notification message with a relevant access type to the UE 100. The notification message indicates the access from which the AMF 200 wants to get a response.

[0101] After receiving the notification message, the UE 100 shall reply to the 5GC via 3GPP access using a NAS Service Request message, which shall contain an indication as to whether the PDU session can be reactivated via 3GPP.

[0102] Fig.11 A timing diagram according to an embodiment of the present invention is shown in which the UE 100 sends a service request, otherwise a notification reject containing all non-3GPP PDUs that cannot be activated through 3GPP. The above solution is unclear about what the UE 100 will do if the PDU session id cannot be moved to 3GPP, and how the AMF 200 will behave for subsequent paging procedures. In the proposed method, the method can be used to send a notification reject message to the network in CM_CONNECTED mode, which indicates all PDU sessions of non-3GPP that cannot be moved to 3GPP. The AMF 200 will use this information to not send paging notifications for the PDU session id indicated in the notification reject in subsequent 3GPP attempts.

[0103] Fig.12 The case of activating a service request (containing a list of non-3GPP PDUs) through 3GPP is shown. Currently, the UE 100 sends a non-3GPP PDU that can be activated through 3GPP. The AMF 200 checks whether the list sent by the UE 100 has a PDU session id, because paging for the PDU session id for downlink data is sent, so it will establish user plane resources for this PDU. However, further processing of the AMF 200 is not defined.

[0104] Fig.13 The case of activating a service request (including a list of non-3GPP PDUs) through 3GPP according to an embodiment of the present invention is shown.

[0105] When there are X PDUs in CM IDLE state on non-3GPP and non-3GPP, and the UE 100 receives paging for non-3GPP access PDUs via 3GPP access, the UE 100 sends a service request with a list of PDUs that can be moved from non-3GPP to 3GPP based on the policy. Upon receiving the PDU list, the AMF 200 will determine whether the list contains the PDU session id for which paging was sent via 3GPP access. If the list is included, the network will establish user plane resources for the PDU and send downlink data. In addition, the AMF 200 will determine that there is no information that all PDUs cannot be moved from non-3GPP to 3GPP, and will not send paging / notification for these PDUs via 3GPP (for example, until the relevant timer is achieved). Alternatively, when the policy of the UE 100 does not allow all currently activated non-3GPP access PDUs to be reactivated via 3GPP access, the UE 100 will ignore paging for "non-3GPP access" in 3GPP.

[0106] In the conventional method, when there is no PDN interworking between the 4G network and the 5G network, there is no mechanism to handle the behavior of the UE 100 and the network 200. Also, what will be the network behavior when a certain RAT does not support a certain PDU. For the case when the network supports registration for one access but not for another access, the behavior of the UE.

[0107] In an embodiment, the system is used to handle dual registration in a wireless communication system. The system includes a UE 100 and a core network entity. The UE 100 is configured to store information related to a PDU session. The PDU session belongs to at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT. In addition, the UE 100 is configured to activate a PDU session for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT based on the stored information. When the UE triggers PDU session activation for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT, the core network entity is configured to reject the activation request and send a reason indicating that the UE 100 is not allowed to activate the PDU session. The core network entity provides information about the PDU session that is allowed to be activated for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT.

[0108] Unlike conventional methods and systems, the proposed method indicates that a field should be present in the SIM card or network slice selection policy file, which should indicate that the RAT supported by the interworking RAT-based PDU can be 4G, 5G, non-3GPP, or a combination thereof. If the UE 100 is not subscribed to the PDU session to be activated to a certain access, the network should subscribe based on the rejection reason. The rejection reason may include allowing or not allowing access to the PDU session. The rejection reason may include allowing only 3GPP access, allowing only non-3GPP access. The subscription information should also be saved in the SIM card, which can provide information about the access subscription (only 3GPP access, only non-3GPP access, or both).

[0109] In addition, if the UE 100 does not subscribe to the PDU for a certain access, the network should give a subscription for the PDN connection request based on the rejection reason, which may include allowing or not allowing the registered access. The rejection reason may include, for example, allowing only 3GPP access, only non-3GPP access, or neither. The subscription information of the PDU should also be stored in the SIM card, which can provide information about the access subscription (only 3GPP access, only non-3GPP access, or both).

[0110] Problem situation : The UE is in CM-IDLE state on a non-3GPP access and the network triggers paging via 3GPP to reactivate PDU sessions associated with the non-3GPP access. The UE triggers the Service Request procedure and includes a list of PDU sessions associated with the non-3GPP access that can be reactivated via 3GPP (e.g. PDU sessions #1, #2).

[0111] At the same time, if Wi-Fi becomes available, the UE 100 also triggers a service request through Wi-Fi (ie, non-3GPP access) to transition from the idle state to the connected state. The AMF 200 receives service requests from both 3GPP and non-3GPP (ie, conflict situation).

[0112] Fig.14 and Fig.15 is a timing diagram illustrating inconsistent behavior of AMF 200 when service requests arrive in different orders at different times.

[0113] Case 1 : If the AMF 200 receives a service request from Wi-Fi first and then receives a service request from 3GPP, the AMF 200 must change the data path of the PDU session that the UE 100 has requested to be activated through 3GPP (such as Fig.14 shown).

[0114] Case 2 : If the AMF 200 receives a service request from 3GPP first and then receives a service request from non-3GPP, the AMF 200 must first change the data path of the PDU session on 3GPP, and then the UE 100 needs to move these PDUs to Wi-Fi due to UE policy (such as Fig.14 shown).

[0115] like Fig.14 As shown, at 1, AMF 200 sends a paging message indicating non-3GPP access to RAN. At 2, UE 100 changes from CM idle to connected on WiFi. At 3, RAN 500 sends a paging message indicating non-3GPP access to UE. At 4, UE 100 sends a service request to N3IWF 300, and at 5, N3IWF 300 sends a service request to AMF 200. At 6, AMF 200 activates PDU on WiFi. At 7, UE 100 sends a service request to AMF 200. At 8, AMF 200 starts PDU transmission on 3GPP.

[0116] like Fig.15As shown, at 1, UE 100 is in CM Idle on WiFi. At 2, AMF 200 sends a paging message indicating non-3GPP access to RAN. At 3, UE 100 is changing from CM Idle to Connected on WiFi. At 4, RAN 500 sends a paging message indicating non-3GPP access to UE. At 5, UE 100 sends a service request to AMF 200. At 6, AMF 200 starts wifi PDU activation on 3GPP. At 7, UE 100 sends a service request to N3IWF 300. At 8, N3IWF 300 sends a service request to AMF 200. At 9, the PDU that has been moved to 3GPP and UE 100 need to move the PDN again on wifi.

[0117] Fig.16 A timing diagram according to an embodiment of the present invention is shown, in which the UE 100 does not trigger a service request on the non-3GPP until the service request on the 3GPP ends.

[0118] If a service request on non-3GPP access is triggered for CM idle to CM connected transition, the UE 100 should trigger a service request on 3GPP in response to a paging indicating non-3gpp access only after the procedure on non-3GPP is completed. In general, if a service request procedure is triggered on one RAT (3GPP or non-3GPP), the same procedure should not be triggered on other RATs (3GPP or non-3GPP) (i.e., the UE 100 should maintain a single service request state machine for 3GPP and non-3GPP).

[0119] like Fig.16 As shown, at 1, UE 100 is in CM idle state on WiFi. At 2, AMF 200 sends a paging indicating non-3GPP access to RAN. At 3, RAN 500 sends a paging indicating non-3GPP access to UE 100. At 4, UE 100 sends a service request to AMF 200. At 5, UE 100 changes from CM idle state to connected state on WiFi. At 6, AMF 200 starts wifi PDU activation on the 3GPP network. At 7, UE 100 will not trigger a service request on N3GPP for a PDU that is allowed to be reactivated in the 3GPP network until the 3GPP service request process ends. In addition, UE 100 can trigger a service request for a PDU that is not allowed to be activated on the 3GPP network.

[0120] Fig.17 A timing diagram according to an embodiment of the present invention is shown, in which the UE 100 does not trigger a service request on 3GPP in response to a paging indicating non-3gpp access until the 3GPP service request on non-3GPP ends.

[0121] When the non-3gpp access is already in connected mode or in the transition phase from idle state to connected mode, the UE 100 ignores paging for the non-3gpp access. (Alternatively, the UE 100 may send a service request without PDN so that the AMF 200 can release the connection without transmitting PDN on the 3GPP network).

[0122] At 1, AMF 200 sends a paging indicating non-3GPP access to RAN network 500. At 2, UE 100 changes from CM idle state to connected state on WiFi. At 3, RAN 500 sends a paging indicating non-3GPP access to UE 100. At 4, UE 100 sends a service request to N3IWF 300. At 5, N3IWF 300 sends a service request to AMF 200. At 6, UE 100 changes from CM idle state to connected state on N3GPP. At 7, AMF 200 activates PDUs on WiFi. At 8, UE 100 does not trigger a service request on N3GPP for PDUs that are allowed to be reactivated in the 3GPP network until the 3GPP service request process ends. UE 100 can trigger a service request for N3GPP PDUs that are not allowed to be activated on the 3GPP network based on uplink data.

[0123] Fig.18 A timing diagram according to an embodiment of the present invention is shown, in which when the non-3gpp of UE 100 is already in connected mode, UE 100 ignores paging through non-3gpp access. Consider the following situation, at 1-5, UE 100 receives paging indicating non-3GPP access on 3GPP, UE 100 starts a service request, but cannot complete the process due to lower layers. After the timer expires (retry attempt), the service request process is attempted, and between the expiration of the timer and the attempt of the service request process, non-3gpp (e.g., Wi-Fi coverage) of UE 100 is found. UE 100 will abort the service request process on 3GPP and will continue the service request through Wi-Fi at 6. At 7, AMF 200 activates PDU on Wi-Fi. At 8, UE 100 sends a service request without any PDU session id to AMF 200, and AMF 200 sends an RRC connection release to UE 100.

[0124] like Fig.18As shown, at 1, AMF 200 sends a paging indicating non-3GPP access to RAN. At 2, RAN 500 sends a paging indicating non-3GPP access to UE 100. At 3, UE 100 moves from CM idle state to connected state on WiFi. At 4, UE 100 sends a service request to N3IWF 300. At 5, N3IWF 300 sends a service request to AMF 200. At 6, AMF 200 activates PDU on WiFi. At 7, if the non-3GPP access is in connected mode, the UE 100 will ignore the paging or will send a service request without indicating a PDU session identifier. At 8, UE 100 sends a service request without any PDU session ID to AMF 200. At 9, AMF 200 sends an RRC connection release to UE 100.

[0125] Fig.19 A timing diagram according to an embodiment of the present invention is shown, in which the UE 100 will abort the service request procedure on 3GPP and will continue to make service requests through Wi-Fi.

[0126] At 1 and 2, the UE 100 receives a paging indicating non-3GPP access on 3GPP. At 3, the UE 100 starts a service request, but cannot complete the process due to lower layers. At 4-9, the service request process will be attempted after the timer expires (i.e., a retry attempt), and between the timer expiration and the attempt of the service request process, the Wi-Fi coverage of the UE 100 is found, so that the UE 100 will abort the service request process on 3GPP and should continue the service request over Wi-Fi.

[0127] Fig. 20 A timing diagram according to an embodiment of the present invention is shown, in which the AMF 200 may ignore the service request with the PDU session state IE allowed (in response to non-3gpp paging) if the same PDU is already connected (or active) via a non-3GPP access (i.e., non-3gpp connected CM state). The AMF 200 may ignore the service request (in response to non-3gpp paging) if the same PDU is already connected (or active) via a non-3GPP access (i.e., non-3gpp connected CM state).

[0128] If the AMF 200 has received a service request over 3GPP (in response to non-3gpp paging) and a service request from Wi-Fi is also received simultaneously. In this case, the AMF 200 shall abort the PDN delivery over 3GPP and shall activate the PDN over Wi-Fi. Thereafter, the AMF 200 shall not send paging for Wi-Fi PDN over 3gpp, i.e. paging with a step-type non-3GPP access.

[0129] like Fig. 20 As shown, at 1, AMF 200 sends a paging indicating non-3GPP access to RAN. At 2, RAN 500 sends a paging indicating non-3GPP access to UE 100. At 3, UE 100 changes from CM idle state to connected state on WiFi. At 4, UE 100 sends a service request to N3IWF 300. At 5, N3IWF 300 sends a service request to AMF 200. At 6, AMF 200 activates PDU on WiFi. At 7, UE 100 sends a service request to AMF 200. At 8, AMF 200 will process the service request, but will not activate the N3GPP PDU activated by the N3GPP network on 3GPP.

[0130] Fig.21 A timing diagram according to an embodiment of the present invention is shown, in which the AMF 200 has received a service request through 3GPP (in response to non-3gpp paging) and simultaneously receives a service request from Wi-Fi.

[0131] If the AMF 200 has received a service request via 3GPP (in response to non-3gpp paging) and also receives a service request from Wi-Fi at the same time. In this case, the AMF 200 shall abort the PDN delivery on 3GPP and shall activate the PDN on Wi-Fi. Thereafter, the AMF 200 shall not send paging on 3gpp for the Wi-Fi PDN.

[0132] like Fig.21 As shown, at 1, UE 100 is in CM idle state on WiFi. At 2, AMF 200 sends a paging indicating non-3GPP access to RAN. At 3, RAN 500 sends a paging indicating non-3GPP access to UE 100. At 4, UE 100 sends a service request to AMF 200. At 5, UE 100 changes from CM idle state to connected state on WiFi. At 6, AMF 200 starts wifi PDU activation on the 3GPP network. At 7, UE 100 sends a service request to N3IWF 300. At 8, N3IWF 300 sends a service request to AMF 200. At 9, AMF 200 will abort PDU transmission on 3GPP and activate on Wifi.

[0133] Fig. 22 A timing diagram according to an embodiment of the present invention is shown, in which the AMF 200 will send a new paging message using 3GPP access.

[0134] Consider that AMF 200 sent paging for non-3gpp and UE 100 ignored the paging when UE 100 changed to Wi-Fi. Once UE 100 is connected via Wi-Fi, AMF 200 can page 3GPP PDN again. AMF 200 should send a cancel paging for the previous paging type (e.g., paging for non-3gpp). AMF 200 should send a new paging message using 3GPP access. E-NodeB should send the latest available access type (Note: the change from CM idle to connected on Wi-Fi means the transition from CM idle to CM connected state of non-3gpp access). When non-3GPP access is in idle mode, if data of both 3GPP and non-3GPP access PDU sessions are waiting at the network side, AMF 200 will trigger a paging procedure with access type non-3GPP access. Since the UE 100 will change to connected mode in 3GPP access, this will avoid two AMF pagings, and in addition, the AMF 200 can establish DRBs for 3GPP access. In addition, the AMF 200 can send downlink data for 3GPP access at the same time that the AMF 200 will receive the allowed PDU session status IE to know the UE policy about which PDU sessions can be changed from non-3GPP access to 3GPP access.

[0135] like Fig. 22 As shown, at 1, AMF 200 sends a paging indicating non-3GPP access to RAN. At 2, RAN 500 sends a paging indicating non-3GPP access to UE 100. At 3, UE 100 changes from CM idle state to connected state on WiFi. At 4, UE 100 will ignore the paging and send a SR on WiFi. At 5, UE 100 sends a service request to N3IWF 300. At 6, N3IWF 300 sends a service request to AMF 200. At 7, AMF 200 receives data for 3GPP PDN. At 8, AMF 200 will cancel the paging to RAN for WiFi, and at 9, AMF 200 sends a new paging for the 3GPP network.

[0136] Fig.23 is a timing diagram according to an embodiment of the present invention, in which the network does not control the movement of a specific PDN to a specific RAT.

[0137] Case 1: In existing methods, the network wants to restrict certain PDNs / DNNs on specific RATs (e.g., data only on Wi-Fi). The user may have subscribed to voice and data on Wi-Fi. In this case, the UE 100 can activate the IMS PDN on 5G and the data PDN / DNN on Wi-Fi. However, there is no method to keep only the data PDN / DNN on Wi-Fi.

[0138] Case 2 In existing methods, the network wants to prioritize a specific PDN / DNN on a specific RAT (e.g., data Wi-Fi is prioritized). In some cases, the network may want to prioritize a specific PDN / DNN on a specific RAT (e.g., if 5G is not available, keep the data PDN on 5G and then use Wi-Fi).

[0139] Case 3 In the existing methods, the network wants to give the conditions for PDN / DNN HO (e.g., signal conditions, packet delay, etc.). All the above strategies can be configured by the network using ANDSF (now FFS). However, ANDSF may not be available in some PDN / DNN, so there should be other mechanisms to support it.

[0140] Based on the proposed method, the SMF 1000 will obtain the policy from the PCF 1100 in step 4. The PCF 1100 can also change the policy later. In this case, the network will follow the PDU Session Modification procedure to update the new policy.

[0141] like Fig.23 As shown, at 1, UE 100 sends a PDU session establishment request to AMF. At 2, AMF 200 sends Nsmf_PDUSession_CreateSMRequest to SMF 1000. At 3, SMF 1000 sends Npcf_PolicyControl_PolicyCreateRequest to PCF 1100. At 4, PCF 1100 sends EventExposure_Notify to SMF 1000. At 5, SMF 1000 sends Nsmf_PDUSession_CreateSMysponse(policy) to AMF 200. At 6, AMF200 sends N2 PDU session request(policy) to RAN 500. At 7, RAN 500 sends N2 PDU session establishment accept to UE 100.

[0142] The UE is configured to store information related to a PDU session. The PDU session belongs to at least one of 3GPP access, non-3GPP access, 3GRAT, 4G RAT and 5G RAT. The UE is configured to activate a PDU session for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT based on the stored information. The core network entity is configured to reject the activation request and send a reason indicating that the UE is not allowed to activate the PDU session when the UE triggers the activation of a PDU session for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT. The core network entity provides information about the activation of a PDU session for at least one of 3GPP access, non-3GPP access, 3G RAT, 4G RAT and 5G RAT.

[0143] Fig.24 1 is a block diagram of a UE 100 according to an embodiment of the present invention. The UE 100 includes a context matching controller 110, a communicator 120, a memory 130, and a processor 140. The processor 140 is coupled to the context matching controller 110, the communicator 120, and the memory 130.

[0144] In an embodiment, the context matching controller 110 is configured to register with the first AMF entity 200a through a 3GPP access network and a non-3GPP access network. In addition, the context matching controller 110 is configured to trigger an update registration procedure to the second AMF entity 200b through the 3GPP access network when the periodic timer of the UE expires in the OOS state. In addition, the context matching controller 110a is configured to receive a registration acceptance or rejection message through the 3GPP access network, and the registration acceptance or rejection message indicates to register with the second AMF entity 200b again for the non-3GPP access network. In addition, the context matching controller 110 is configured to restart the update registration procedure to register with the second AMF entity 200b again for the non-3GPP access through the non-3GPP access network.

[0145] In an embodiment, the context matching controller 110 is configured to register with the MME 400 through the 3GPP access network and to register with the first AMF entity 200a through the non-3GPP access network. In addition, the context matching controller 110 is configured to trigger an update registration procedure from the MME 400 to the second AMF entity 200b. In addition, the context matching controller 110 configures the GUTI mapped from the 3GPP access network and an indication that the second AMF entity 200b obtains non-3gpp access from the first AMF entity 200a. In addition, the context matching controller 110 is configured to send the GUTI to the second AMF entity 200b to bind the N2AP UE-TNLA to the N3IWF interface 300.

[0146] In an embodiment, the context matching controller 110 is configured to receive a paging message indicating a non-3GPP access from a 3GPP access network, and detect that the CM state of the non-3GPP access is in a connected mode or is in the process of entering a connected mode. In addition, the context matching controller 110 is configured to perform one of the following operations: ignoring the paging message indicating the non-3GPP access, or sending a service request that does not include an allowed PDU session state IE to the AMF entity 200.

[0147] In an embodiment, the context matching controller 110 is configured to receive one of a paging message indicating a non-3GPP access or a notification message indicating a non-3GPP access from a 3GPP access network. The context matching controller 110 is configured to detect that the CM state of the non-3GPP access network is in a CM idle state and a connected mode. The UE 100 responds with a service request message including an allowed PDU session state IE. The context matching controller 110 is configured to detect that a non-3GPP access network service is available and that the non-3GPP access network changes to a connected mode. The context matching controller 110 is configured to perform one of the following operations: before the service request process for the 3GPP access network is completed, a service request message for a PDU that is allowed to be reactivated in the 3GPP access network is not triggered through the non-3GPP access network; or a service request message for a PDU that is not allowed to be activated through the 3GPP access network is triggered; or based on uplink data, a service request message for a PDU that is not allowed to be activated based on uplink data through the 3GPP access network is triggered.

[0148] In an embodiment, the context matching controller 110 is configured to receive a paging message indicating a non-3GPP access from a 3GPP access network, and detect that a service request message that sends an allowed PDU session status IE to the AMF entity 200 is invalid. The context matching controller 110 is configured to detect that the CM state of the non-3GPP access network has changed to connected mode. The UE 100 stops the retry timer and terminates the service request process on the 3GPP access network. The context matching controller 110 is configured to send a service request including an uplink data status IE to the AMF entity 200 through the non-3GPP access network. The PDU associated with the non-3GPP access network that is allowed to change to a 3GPP access network is included in the uplink data status IE. The context matching controller 110 is configured to stop the service request for the 3GPP access network.

[0149] The communicator 120 is configured to communicate internally between internal hardware components and to communicate with external devices via one or more networks. The communicator 120 is configured to communicate with the context matching controller 110 to handle dual registration and session management in the wireless communication system. In an embodiment, the context matching controller 110 includes a binding controller and a context updater for handling dual registration and session management in the wireless communication system.

[0150] In addition, the processor 140 is configured to execute instructions stored in the memory 130 and perform various processes. The memory 130 also stores instructions to be executed by the processor 140. The memory 130 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory 130 may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or a propagated signal. However, the term "non-transitory" should not be interpreted as a memory that is non-removable. In some examples, the memory 130 may be configured to store a larger amount of information than the memory. In some examples, a non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache).

[0151] Although Fig.24 Various hardware components of UE 100 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, UE 100 may include fewer or more components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present invention. One or more components may be combined together to perform the same or substantially similar functions to handle dual registration and session management in a wireless communication system.

[0152] Fig.25 2 is a block diagram of an AMF 200 according to an embodiment of the present invention. The AMF 200 includes a context matching controller 210, a communicator 220, a memory 230, and a processor 240. The processor 240 is coupled to the context matching controller 210, the communicator 220, and the memory 230.

[0153] In an embodiment, the context matching controller 210 is configured to receive an update registration procedure from the UE 100 via a 3GPP access network. The UE 100 is registered to the 3GPP access network and the non-3GPP access network via another AMF entity 200b. In addition, the context matching controller 210 is configured to obtain a non-3GPP context from another AMF entity 200b and a 3GPP context from the MME 400. In addition, the context matching controller is configured to send a registration acceptance or rejection message with an indication to register the non-3GPP access network to the AMF entity 200a again. In addition, the context matching controller 210 is configured to receive an update registration procedure to register the UE 100 for the non-3GPP access network again, thereby creating an N2 interface between the N3IWF 300 and the second AMF entity 200b.

[0154] In an embodiment, the context matching controller 210 is configured to register the 3GPP access context and the non-3GPP access context with the AMF entity 200. In addition, the context matching controller 210 is configured to detect the inter-system change from the 5G network to the 4G network through the 3GPP access network. In addition, the context matching controller 210 configures the transfer of the 3GPP access context from the AMF entity 200 to the MME entity 400, and continuously retains the non-3GPP access context with the AMF 200 through the N3IWF 400.

[0155] In an embodiment, the context matching controller 210 is configured to receive an update registration procedure from the UE 100. The UE 100 is connected to the MME 400 via a 3GPP access network and is connected to another AMF entity 200b via a non-3GPP access network. In addition, the context matching controller 210 is configured to receive a GUTI mapped from the 3GPP access network from the UE 100. The GUTI includes an indication that the AMF entity 200a obtains non-3gpp access from another AMF entity 200b. In addition, the context matching controller 210 is configured to obtain a context from another AMF entity 200b and bind the N2AP UE-TNLA to the N3IWF interface 300.

[0156] In an embodiment, the context matching controller 210 is configured to receive a service request message from the UE 100 via a non-3GPP access network. In addition, the context matching controller 210 is configured to activate a PDU on the non-3GPP access network and receive a service request without indicating a PDU session identifier. In addition, the context matching controller 210 is configured to send an RRC connection release message to the UE 100.

[0157] In an embodiment, the context matching controller 210 is configured to send a paging message indicating non-3GPP access to the UE 100 through the 3GPP access network. The context matching controller 210 is configured to receive a service request from the UE 100 through the non-3GPP access network, and detect that the AMF entity 200 is in the process of activating a PDU on the non-3GPP access network. The context matching controller 100 is configured to process the service request through the 3GPP access network and not activate a PDU for the non-3GPP access network, wherein the PDU is activated through the non-3GPP access network.

[0158] In an embodiment, the context matching controller 210 is configured to send a paging message indicating non-3GPP access to the UE 100 through the 3GPP access network. The context matching controller 210 is configured to receive a service request from the UE 100 through the non-3GPP access network and activate a PDU on the 3GPP access network. The context matching controller 210 is configured to process the service request through the 3GPP access network and not activate a PDU for the non-3GPP access network, wherein the PDU has been activated through the non-3GPP access network.

[0159] The communicator 220 is configured to communicate internally between internal hardware components and to communicate with external devices via one or more networks. The communicator 220 is configured to communicate with the context matching controller 210 to handle dual registration in the wireless communication system. In one embodiment, the context matching controller 210 includes a binding controller and a context updater for handling dual registration in the wireless communication system.

[0160] In addition, the processor 240 is configured to execute instructions stored in the memory 230 and to perform various processes. The memory 230 also stores instructions to be executed by the processor 240. The memory 230 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory 230 may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or a propagated signal. However, the term "non-transitory" should not be interpreted as a memory that is non-removable. In some examples, the memory 230 may be configured to store a larger amount of information than the memory. In some examples, a non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache).

[0161] Although Fig.25Various hardware components of AMF 200 are shown, but it is understood that other embodiments are not limited thereto. In other embodiments, AMF 200 may include fewer or more components. In addition, the labels or names of the components are only for illustrative purposes and do not limit the scope of the present invention. One or more components may be combined together to perform the same or substantially similar functions to handle dual registration and session management in a wireless communication system.

[0162] Figures 26 to 30 2600 - 3000 are flow charts illustrating various steps implemented by UE 100 for handling registration and session management in a wireless communication system according to an embodiment of the present invention.

[0163] Operations (2602-2608) are performed by the context matching controller 110. Fig.26 As shown, at 2602, the method includes registering, by the UE 100, with the first AMF entity 200a through the 3GPP access network and the non-3GPP access network. At 2604, the method includes: when the periodic timer of the UE expires in the OOS state, triggering an update registration procedure to the second AMF entity 200b through the 3GPP access network. At 2606, the method includes: receiving a registration acceptance or rejection message through the 3GPP access network, the registration acceptance or rejection message indicating to register again with the second AMF entity 200b for the non-3GPP access network. At 2608, the method includes restarting the update registration procedure to register again with the second AMF entity 200b for the non-3GPP access through the non-3GPP access network.

[0164] Operations (2702-2708) are performed by the context matching controller 110. Fig. 27 As shown, at 2702, the method includes: registering with MME 400 through a 3GPP access network, and registering with a first AMF entity 200a through a non-3GPP access network. At 2704, the method includes: triggering an update registration procedure to a second AMF entity 200b. At 2706, the method includes: configuring two indications, one of which is used to obtain a 3GPP access context from MME 400, and the other is used to obtain a non-3gpp access context from the first AMF entity 200a. At 2708, the method includes: sending another indication to the second AMF entity 200b to obtain a non-3GPP access context and binding the N2AP UE-TNLA to the N3IWF interface 300.

[0165] Operations (2802-2806) are performed by the context matching controller 110. Fig.28As shown, at 2802, the method includes: receiving a paging message indicating non-3GPP access from a 3GPP access network. At 2804, the method includes: detecting whether the CM state of the non-3GPP access is in a connected mode or in the process of entering a connected mode. At 2806, the method includes performing one of the following operations: ignoring the paging message indicating the non-3GPP access, or sending a service request that does not include an allowed PDU session status IE to the AMF entity 200.

[0166] Operations (2902-2908) are performed by the context matching controller 110. Fig.29 As shown, at 2902, the method includes: receiving one of a paging message indicating a non-3GPP access or a notification message indicating a non-3GPP access from a 3GPP access network. At 2904, the method includes: detecting that the CM state of the non-3GPP access network is in a CM idle state and a connected mode. At 2904, the method includes detecting that a non-3GPP access network service is available and that the non-3GPP access network changes to a connected mode. At 2910, the method includes: before the service request process for the 3GPP access network is completed, not triggering a service request message for a PDU that is allowed to be reactivated in the 3GPP access network through the non-3GPP access network, or triggering a service request for a PDU that is not allowed to be activated through the 3GPP access network. At 2908, the method includes: based on uplink data, triggering a service request message for a PDU that is not allowed to be activated through the 3GPP access network.

[0167] Operations (3002-3008) are performed by the context matching controller 110. Fig.30 As shown, at 3002, the method includes: receiving a paging message indicating non-3GPP access from a 3GPP access network. At 3004, the method includes: detecting that a service request message sent to the AMF entity 200 is invalid. At 3006, the method includes: detecting that the CM state of the non-3GPP access network is in connected mode. At 3008, the method includes: sending a service request including an uplink data status IE to the AMF entity 200. The PDU associated with the non-3GPP access network is included in the uplink data status IE. At 3010, the method includes: stopping the service request to the 3GPP access network.

[0168] Figure 31 to Figure 36 3100-3600 are flowcharts illustrating the various steps implemented by the AMF 200a / 200b for processing registration and session management in a wireless communication system according to an embodiment of the present invention.

[0169] Operations (3102-3108) are performed by the context matching controller 210. Fig.30As shown, at 3102, the method includes: receiving an update registration procedure from UE 100 through a 3GPP access network. UE 100 is registered to the 3GPP access network and the non-3GPP access network through another AMF entity 200b. At 3104, the method includes: attempting to obtain a 3GPP context from MME 400 and a non-3GPP context from a first AMF entity 200a. At 3106, the method includes: sending a NAS message (in the example, a registration acceptance or rejection message) indicating re-registration to the AMF entity 200a for the non-3GPP access network. At 3108, the method includes: receiving an update registration procedure to register UE 100 for the non-3GPP access network again to create an N2 interface between the N3IWF 300 and the AMF entity 200a.

[0170] Operations (3202-3208) are performed by the context matching controller 210. Fig.32 As shown, at 3202, the method includes: receiving an update registration procedure from UE 100. UE 100 communicates with MME 400 via a 3GPP access network, and communicates with another AMF entity 200b via a non-3GPP access network. At 3204, the method includes: receiving a GUTI mapped from a 3GPP access network from UE 100. The GUTI includes an indication that the AMF entity 200a obtains non-3gpp access from another AMF entity 200b. At 3206, the method includes: obtaining a context from another AMF entity 200b. At 3208, the method includes: binding the N2AP UE-TNLA to the N3IWF interface 300.

[0171] Operations (3302-3308) are performed by the context matching controller 210. Fig.33 As shown, at 3302, the method includes: receiving a service request message from UE 100 via a non-3GPP access network. At 3304, the method includes: activating a PDU on the non-3GPP access network. At 3306, the method includes: receiving a service request message that does not indicate a PDU session identifier. At 3308, the method includes: sending an RRC connection release message to the UE.

[0172] Operations (3402-3408) are performed by the context matching controller 210. Fig.34As shown, at 3402, the method includes: sending a paging message indicating non-3GPP access to the UE through the 3GPP access network. At 3404, the method includes: receiving a service request from the UE through the non-3GPP access network, and detecting that the AMF entity is in the process of activating a PDU on the non-3GPP access network. At 3406, the method includes: processing the service request on N3GPP, and not activating the PDU for the non-3GPP access network through the 3GPP access network. The PDU is activated through the non-3GPP access network.

[0173] Operations (3502-3508) are performed by the context matching controller 210. Fig.35 As shown, at 3502, the method includes: sending a paging message indicating non-3GPP access to UE 100 through a 3GPP access network. At 3504, the method includes receiving a service request from the UE through the non-3GPP access network. At 3506, the method includes: activating a PDU on the non-3GPP access network. At 3508, the method includes: processing the service request on the non-3GPP access network, and not activating a PDU for the non-3GPP access network through the 3GPP access network. The PDU has been activated through the non-3GPP access network.

[0174] Operations (3602-3606) are performed by the context matching controller 210. Fig.36 As shown, at 3602, the method includes: sending a paging message indicating non-3GPP access to UE 100 through the 3GPP access network. At 3604, the method includes: when UE 100 changes from the CM idle state to the CM connected state, receiving a service request from UE 100 through the non-3GPP access network. At 3606, the method includes: terminating the paging message for the non-3GPP access network and sending a new paging message for the 3GPP access network.

[0175] The various behaviors, actions, blocks, steps, etc. in the flowcharts 2600-3600 can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some behaviors, actions, blocks, steps, etc. can be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.

[0176] Fig.37 is a block diagram illustrating an access management function (AMF) entity according to another exemplary embodiment of the present disclosure.

[0177] Reference Fig.37 , the device 3700 may include a processor 3710, a transceiver 3720, and a memory 3730. However, not all of the components shown are required. The device 3700 may be composed of Fig.37In addition, according to another embodiment, the processor 3710, the transceiver 3720, and the memory 3730 may be implemented as a single chip.

[0178] The aforementioned components will now be described in detail.

[0179] The processor 3710 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The processor may include a context matching controller coupled to the memory 3730. The operation of the device 3700 may be implemented by the processor 3710.

[0180] Processor 3710 can receive a registration procedure from a user equipment (UE) through a third generation partnership project (3GPP) access network, wherein the UE registers to the 3GPP access network through a mobility management entity (MME), registers to a non-3GPP access network through another AMF entity, attempts to obtain a non-3GPP context from another AMF entity, and obtains a 3GPP context from the MME, sends a non-access stratum (NAS) message with an indication through the 3GPP access network to register the non-3GPP access network with the AMF entity again, and receives a registration procedure to register the UE for the non-3GPP access network and create an N2 interface between the N3IWF and the AMF entity.

[0181] The transceiver 3720 may include an RF transmitter for up-converting and amplifying a transmit signal and an RF receiver for down-converting the frequency of a receive signal. However, according to another embodiment, the transceiver 3720 may be implemented by more or fewer components than those shown.

[0182] The transceiver 3720 may be connected to the processor 3710 and transmit and / or receive signals. The signal may include control information and data. In addition, the transceiver 3720 may receive a signal through a wireless or wired channel and output the signal to the processor 3710. The transceiver 3720 may transmit a signal output from the processor 3710 through a wireless channel. The transceiver 3720 may communicate with other entities through a wired channel.

[0183] The memory 3730 may store control information or data included in the signal obtained by the device 3700. The memory 3730 may be connected to the processor 3710 and store at least one instruction or protocol or parameter for the proposed function, process, and / or method. The memory 3730 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0184] Fig.38 is a block diagram illustrating a UE according to another exemplary embodiment of the present disclosure.

[0185] Reference Fig.38 , the device 3800 may include a processor 3810, a transceiver 3820, and a memory 3830. However, not all of the components shown are required. The device 3800 may be composed of Fig.38 In addition, according to another embodiment, the processor 3810, the transceiver 3820, and the memory 3830 may be implemented as a single chip.

[0186] The aforementioned components will now be described in detail.

[0187] The processor 3810 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The processor 3810 may include a context matching controller coupled to the memory 3830. The operation of the device 3800 may be implemented by the processor 3810.

[0188] Processor 3810 can register with the first core network entity through the 3GPP access network and the non-3GPP access network, trigger a registration procedure to the second core network entity through the 3GPP access network when the periodic timer of the UE expires in the out-of-service (OOS) state, receive a non-access stratum (NAS) with an indication through the 3GPP access network to register the non-3GPP access network with the second core network entity, and restart the re-registration procedure to register the non-3GPP access to the second core network entity again through the non-3GPP access network.

[0189] The transceiver 3820 may include an RF transmitter for up-converting and amplifying a transmit signal and an RF receiver for down-converting the frequency of a receive signal. However, according to another embodiment, the transceiver 3820 may be implemented by more or fewer components than those shown.

[0190] The transceiver 3820 may be connected to the processor 3810 and transmit and / or receive signals. The signal may include control information and data. In addition, the transceiver 3820 may receive a signal through a wireless channel and output the signal to the processor 3810. The transceiver 3820 may transmit a signal output from the processor 3810 through a wireless channel.

[0191] The memory 3830 may store control information or data included in the signal obtained by the device 3800. The memory 3830 may be connected to the processor 3810 and store at least one instruction or protocol or parameter for the proposed function, process and / or method. The memory 3830 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0192] Those skilled in the art will appreciate that all or part of the steps in the above method embodiments can be implemented by program commands associated with hardware, and the program can be stored in a computer-readable storage medium. When executed, it includes one of the steps of the method embodiment or a combination of the steps of the embodiment.

[0193] In addition, the functional units in the various embodiments of the present application can be integrated in the processing module, or each unit can exist physically separately, or more than two units can be integrated in one module. The integrated module can be implemented in the form of hardware, or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and is sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0194] UE 100 may be, for example, but not limited to, a cellular phone, a tablet computer, a smart phone, a laptop computer, a personal digital assistant (PDA), a global positioning system, a multimedia device, a video device, a game console, etc. UE 100 may also be referred to as a mobile station, a user station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, etc. by those skilled in the art.

[0195] The UE 100 follows a variety of different communication protocols that can be used as a multi-mode device by communicating in a 5G network or a fourth generation (4G) network that employs any common type of LTE or Advanced LTE (LTE-A) radio access technology (RAT) and in a third generation (3G) or second generation (2G) network that employs any common type of legacy RAT or Vo-NR networks and Vo-WiFi networks.

[0196] The embodiments disclosed herein may be implemented by at least one software program running on at least one hardware device and performing network management functions to control the elements.

[0197] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein so that others can easily modify and / or adapt to various applications of such specific embodiments by applying current knowledge without departing from the general concepts, and therefore, such adaptations and modifications should and are intended to be understood as being within the meaning and scope of equivalent forms of the disclosed embodiments. It should be understood that the wording or terminology employed herein is for descriptive purposes and not limiting. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the spirit and scope of the embodiments as described herein.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising: Sending a first registration request message to the access management function AMF entity for a mobility registration procedure via the third generation partnership project 3GPP access; as well as receiving a Registration Accept message from the AMF entity, the Registration Accept message including an indication that the UE is not registered for non-3GPP access as a result of the mobility registration procedure.

2. The method according to claim 1, wherein: The first registration request message includes a 5G-GUTI mapped from a 4G-Globally Unique Temporary Identifier GUTI and a further 5G-GUTI, and The additional 5G-GUTI is a 5G-GUTI for non-3GPP access, wherein the UE is registered before starting the mobility registration procedure.

3. The method according to claim 1, further comprising: Send a second registration request message to the AMF entity through the non-3GPP access.

4. The method according to claim 1, wherein: The UE considers that it is registered for the 3GPP access only based on the REGISTRATION ACCEPT message.

5. The method according to claim 1, wherein: The UE registers with the same AMF entity through the 3GPP access and the non-3GPP access.

6. A method performed by an access management function (AMF) entity in a wireless communication system, the method comprising: receiving a first registration request message from a user equipment UE for a mobility registration procedure via a third generation partnership project 3GPP access; as well as A registration accept message is sent to the UE, the registration accept message including an indication that the UE is not registered for non-3GPP access as a result of the mobility registration procedure.

7. The method according to claim 6, wherein: The first registration request message includes a 5G-GUTI mapped from a 4G-Globally Unique Temporary Identifier GUTI and a further 5G-GUTI, and The additional 5G-GUTI is a 5G-GUTI for non-3GPP access, wherein the UE is registered before starting the mobility registration procedure.

8. The method according to claim 6, further comprising: A second registration request message is received from the UE via the non-3GPP access.

9. A user equipment UE in a wireless communication system, the UE comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: Sending a first registration request message to the access management function AMF entity for a mobility registration procedure via the third generation partnership project 3GPP access; as well as receiving a Registration Accept message from the AMF entity, the Registration Accept message including an indication that the UE is not registered for non-3GPP access as a result of the mobility registration procedure.

10. The UE according to claim 9, wherein: The first registration request message includes a 5G-GUTI mapped from a 4G-Globally Unique Temporary Identifier GUTI and a further 5G-GUTI, and The additional 5G-GUTI is a 5G-GUTI for non-3GPP access, wherein the UE is registered before starting the mobility registration procedure.

11. The UE according to claim 9, wherein: The controller is also configured to: Send a second registration request message to the AMF entity through the non-3GPP access.

12. The UE according to claim 9, wherein: The UE considers that it is registered for the 3GPP access only based on the REGISTRATION ACCEPT message.

13. The UE according to claim 9, wherein: The UE registers with the same AMF entity through the 3GPP access and the non-3GPP access.

14. An access management function AMF entity in a wireless communication system, the AMF entity comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: receiving a first registration request message from a user equipment UE for a mobility registration procedure via a third generation partnership project 3GPP access; as well as A registration accept message is sent to the UE, the registration accept message including an indication that the UE is not registered for non-3GPP access as a result of the mobility registration procedure.

15. The AMF entity according to claim 14, wherein: The first registration request message includes a 5G-GUTI mapped from a 4G-Globally Unique Temporary Identifier GUTI and a further 5G-GUTI, and The additional 5G-GUTI is a 5G-GUTI for non-3GPP access, wherein the UE is registered before starting the mobility registration procedure.

16. The AMF entity according to claim 14, wherein: The controller is also configured to: A second registration request message is received from the UE via the non-3GPP access.

Images