User equipment, access and mobility management function and methods used thereby

Abstract

The invention relates to a user equipment, an access and mobility management function and methods used thereby. The method used by a user equipment, UE, comprises: receiving, from an access and mobility management function, AMF, a first temporary mobile identity of the UE on a 3GPP access during a first non-access stratum procedure, first NAS procedure, between the UE and the AMF; receiving, from the AMF, a second temporary mobile identity of the UE on a non-3GPP access during a second NAS procedure between the UE and the AMF; and paging using a third temporary mobile identity sent from the AMF to a next generation radio access network, NG-RAN, in a 3GPP access, wherein the third temporary mobile identity is derived from the second temporary mobile identity.

Description

[0001] This application is a divisional application of Chinese Patent Application No. 201980006116.7, filed on May 10, 2019, entitled "Method for Synchronizing the Status of UEs in a Communication Network". Technical Field

[0002] This invention relates to a method and system for synchronizing the status of a UE in a communication network. Specifically, this invention relates to synchronizing the temporary identity of the UE and the network in scenarios where the UE is connected to the same AMF via 3GPP access and non-3GPP access, the UE is in an RRC inactive state on the 3GPP access, and the UE's temporary identity changes on the non-3GPP access. Background Technology

[0003] In 5GS, both 3GPP access and non-3GPP access connect to the AMF. A UE can simultaneously connect to a PLMN or different PLMNs via both 3GPP and non-3GPP access. The UE and network maintain separate registration management contexts and CM states for 3GPP and non-3GPP access. When a UE connects to the same PLMN via both 3GPP and non-3GPP access, the UE connects to the same AMF via both 3GPP and non-3GPP access. The AMF assigns a single 5G-GUTI as a temporary identifier for both RM contexts. The UE will use the same 5G-GUTI to communicate via both 3GPP and non-3GPP access. The RAN will use the S-TMSI to perform RAN paging for UEs in an RRC inactive state. Here, the 5G-GUTI can consist of a GUAMI and a 5G-S-TMSI.

[0004] S-TMSI stands for Mobile NAS Temporary Identifier used for paging, specifically the 5GS-TMSI used for paging on EUTRA, the I-RNTI used for paging the UE on the new radio when the UE is in RRC_INACTIVE (RRC inactive) state, and the 5G S-TMSI used for paging the UE on the new radio when the UE is in RRC_IDLE (RRC idle) state. The I-RNTI is a unique identifier used to identify the UE context for RRC_INACTIVE.

[0005] When the UE is in the CM-CONNECTED state and the RRC INACTIVE state, the above UE and network procedures will cause the following two problems.

[0006] The first problem with the existing technology is that when the UE is in an INACTIVE state under CM-CONNECTED and the UE's GUTI changes on a non-3GPP access, the UE cannot be paged with the correct mobile identity. This is why, in cases where no AMF pager occurs due to the CM-CONNECTED state between the UE and the AMF, the mobile identities stored in the UE and the 3GPP access respectively have different values ​​(i.e., are out of sync).

[0007] More specifically, in scenarios where the UE is undergoing initial registration on a non-3GPP access network, or where the UE has already attached to a non-3GPP access network, and the UE is in the INACTIVE state of CM-CONNECTED on a 3GPP access network and the 5G-GUTI can be changed on a non-3GPP access network, the UE is in the CM-CONNECTED state and the AMF assigns a new 5G-GUTI to the UE. In this scenario, the S-TMSI stored in the NG-RAN will not be updated from the old S-TMSI, which is part of the old assigned 5G-GUTI, to the new S-TMSI, which is part of the new assigned 5G-GUTI. Therefore, the NG-RAN still contains the UE's old S-TMSI. When the NG-RAN needs to page the UE, the NG-RAN will use the old S-TMSI during the paging process, and the paging process will fail because the UE will use the new S-TMSI to identify the paging message. Hereinafter, "CM (Connectivity Management)" is also referred to as "5GMM (5GS Mobility Management)".

[0008] In other words, the following definition of “5GMM” related modes applies to any aspect.

[0009] 5GMM-IDLE mode: In any respect, the UE being in 5GMM-IDLE mode means that the UE can be in 5GMM-IDLE mode on 3GPP access or in 5GMM-IDLE mode on non-3GPP access.

[0010] 5GMM-CONNECTED mode: In any respect, the UE being in 5GMM-CONNECTED mode means that the UE can be in 5GMM-CONNECTED on 3GPP access or on non-3GPP access.

[0011] 5GPP MM-IDLE mode on 3GPP access: In the absence of an N1 NAS signaling connection between the UE and the network (e.g., AMF) on 3GPP access, the UE is in 5GPP MM-IDLE mode on 3GPP access. The term "5GPP MM-IDLE mode on 3GPP access" corresponds to the term "CM-IDLE (CM idle) state for 3GPP access used in any aspect".

[0012] 5GMM-CONNECTED mode on 3GPP access: When an N1 NAS signaling connection exists between the UE and the network (e.g., AMF) on 3GPP access, the UE is in 5GMM-CONNECTED mode on 3GPP access. The term "5GMM-CONNECTED mode on 3GPP access" corresponds to the term "CM-CONNECTED state for 3GPP access used in any aspect".

[0013] 5GMM-IDLE mode on non-3GPP access: In the absence of an N1 NAS signaling connection between the UE and the network (e.g., AMF) on non-3GPP access, the UE is in 5GMM-IDLE mode on non-3GPP access. The term "5GMM-IDLE mode on non-3GPP access" corresponds to the term "CM-IDLE state for non-3GPP access used in any aspect".

[0014] 5GMM-CONNECTED mode on non-3GPP access: When an N1 NAS signaling connection exists between the UE and the network (e.g., AMF) on non-3GPP access, the UE is in 5GMM-CONNECTED mode on non-3GPP access. The term "5GMM-CONNECTED mode on non-3GPP access" corresponds to the term "CM-CONNECTED state for non-3GPP access used in any aspect".

[0015] Another problem with the existing technology is that when the AMF is relocated on a non-3GPP access, the NG-RAN cannot route the UE to the new AMF on a 3GPP access.

[0016] The UE registers with the AMF via 3GPP access and is in the INACTIVE state within the CM-CONNECTED state. If the UE is in the CM-CONNECTED state with the same AMF via a non-3GPP access, for example, if the UE initiates the registration process with the same AMF via a non-3GPP access, or if the UE has already registered with the same AMF via a non-3GPP access and is in the CM-CONNECTED state, the AMF can perform an AMF relocation process due to the load rebalancing process, relocating the UE context to the new AMF or UDSF. In this scenario, the new AMF assigns a new 5G-GUTI to the UE and sends this new 5G-GUTI to the UE in a NAS message via the non-3GPP access. In this scenario, the UE will use the new S-TMSI during AS signaling via 3GPP access, causing the NG-RAN to route the UE to the new AMF. However, when the UE is in the INACTIVE state in CM-CONNECTED mode and the recovery process is performed via 3GPP access, the UE cannot set the new S-TMSI as the UE temporary identifier to the NG-RAN in the RRC connection recovery request message. This is because the S-TMSI is not defined as a fillable parameter in the RRC connection recovery request message. If the NG-RAN receives an RRC connection recovery request without the new S-TMSI, the NG-RAN will revert to the old AMF connection because the NG-RAN maintains the old S-TMSI for the UE. Therefore, an effective communication method and system are needed to synchronize the temporary identities of the UE and the network in scenarios where the UE is connected to the same AMF via 3GPP access and non-3GPP access, the UE is in an RRC inactive state on the 3GPP access, and the UE's temporary identity changes on the non-3GPP access. Summary of the Invention

[0017] The problem the invention aims to solve

[0018] The first problem with the existing technology is that when the UE is in an INACTIVE state under CM-CONNECTED and the UE's GUTI changes on a non-3GPP access, the UE cannot be paged with the correct mobile identity. This is why, in cases where no AMF pager occurs due to the CM-CONNECTED state between the UE and the AMF, the mobile identities stored in the UE and the 3GPP access respectively have different values ​​(i.e., are out of sync).

[0019] More specifically, in scenarios where the UE is undergoing initial registration on a non-3GPP access network, or where the UE has already attached to a non-3GPP access network, and the UE is in the INACTIVE state of CM-CONNECTED on a 3GPP access network and the 5G-GUTI can be changed on a non-3GPP access network, the UE is in the CM-CONNECTED state and the AMF assigns a new 5G-GUTI to the UE. In this scenario, the S-TMSI stored in the NG-RAN will not be updated from the old S-TMSI, which is part of the old assigned 5G-GUTI, to the new S-TMSI, which is part of the new assigned 5G-GUTI. Therefore, the NG-RAN still contains the UE's old S-TMSI. When the NG-RAN needs to page the UE, the NG-RAN will use the old S-TMSI during the paging process, and the paging process will fail because the UE will use the new S-TMSI to identify the paging message. Hereinafter, "CM (Connectivity Management)" is also referred to as "5GMM (5GS Mobility Management)".

[0020] In other words, the following definition of “5GMM” related modes applies to any aspect.

[0021] 5GMM-IDLE mode: In any respect, the UE being in 5GMM-IDLE mode means that the UE can be in 5GMM-IDLE mode with 3GPP access or in 5GMM-IDLE mode with non-3GPP access.

[0022] 5GMM-CONNECTED mode: In any respect, the UE being in 5GMM-CONNECTED mode means that the UE can be in 5GMM-CONNECTED mode on 3GPP access or in 5GMM-CONNECTED mode on non-3GPP access.

[0023] 5GPP MM-IDLE mode on 3GPP access: In the absence of an N1 NAS signaling connection between the UE and the network (e.g., AMF) on 3GPP access, the UE is in 5GPP MM-IDLE mode on 3GPP access. The term "5GPP MM-IDLE mode on 3GPP access" corresponds to the term "CM-IDLE (CM idle) state for 3GPP access used in any aspect".

[0024] 5GMM-CONNECTED mode on 3GPP access: When an N1 NAS signaling connection exists between the UE and the network (e.g., AMF) on 3GPP access, the UE is in 5GMM-CONNECTED mode on 3GPP access. The term "5GMM-CONNECTED mode on 3GPP access" corresponds to the term "CM-CONNECTED state for 3GPP access used in any aspect".

[0025] 5GMM-IDLE mode on non-3GPP access: In the absence of an N1 NAS signaling connection between the UE and the network (e.g., AMF) on non-3GPP access, the UE is in 5GMM-IDLE mode on non-3GPP access. The term "5GMM-IDLE mode on non-3GPP access" corresponds to the term "CM-IDLE state for non-3GPP access used in any aspect".

[0026] 5GMM-CONNECTED mode on non-3GPP access: When an N1 NAS signaling connection exists between the UE and the network (e.g., AMF) on non-3GPP access, the UE is in 5GMM-CONNECTED mode on non-3GPP access. The term "5GMM-CONNECTED mode on non-3GPP access" corresponds to the term "CM-CONNECTED state for non-3GPP access used in any aspect".

[0027] Another problem with the existing technology is that when the AMF is relocated on a non-3GPP access, the NG-RAN cannot route the UE to the new AMF on a 3GPP access.

[0028] The UE registers with the AMF via 3GPP access and is in the INACTIVE state within the CM-CONNECTED state. If the UE is in the CM-CONNECTED state with the same AMF via a non-3GPP access, for example, if the UE initiates the registration process with the same AMF via a non-3GPP access, or if the UE has already registered with the same AMF via a non-3GPP access and is in the CM-CONNECTED state, the AMF can perform an AMF relocation process due to the load rebalancing process, relocating the UE context to the new AMF or UDSF. In this scenario, the new AMF assigns a new 5G-GUTI to the UE and sends this new 5G-GUTI to the UE in a NAS message via the non-3GPP access. In this scenario, the UE will use the new S-TMSI during AS signaling via 3GPP access, causing the NG-RAN to route the UE to the new AMF. However, when the UE is in the INACTIVE state in CM-CONNECTED mode and the recovery process is performed via 3GPP access, the UE cannot set the new S-TMSI as the UE temporary identifier to the NG-RAN in the RRC connection recovery request message. This is because the S-TMSI is not defined as a fillable parameter in the RRC connection recovery request message. If the NG-RAN receives an RRC connection recovery request without the new S-TMSI, the NG-RAN will revert to the old AMF connection because the NG-RAN maintains the old S-TMSI for the UE. Therefore, an effective communication method and system are needed to synchronize the temporary identities of the UE and the network in scenarios where the UE is connected to the same AMF via 3GPP access and non-3GPP access, the UE is in an RRC inactive state on the 3GPP access, and the UE's temporary identity changes on the non-3GPP access.

[0029] Solution for solving the problem

[0030] The following is a simplified summary of the topic to provide a basic understanding of certain aspects of the topic. This summary is not a comprehensive overview of the topic. Its purpose is not to identify the main / key elements of the aspects or to define the scope of the topic.

[0031] To overcome the problems discussed above, the present invention provides a solution, in which, in one aspect, it is proposed that the problem can be solved by synchronizing the temporary identity of the UE and the network when the UE is connected to the same AMF via 3GPP access and non-3GPP access, the UE is in an RRC inactive state on the 3GPP access and the UE's temporary identity changes on the non-3GPP access.

[0032] In other aspects of the invention, it is proposed that when the temporary mobile identity of the UE is changed via non-3GPP access through the AMF, the UE releases the assigned RRC resources and enters an RRC idle state.

[0033] Other aspects of the invention propose that, in the event that the UE’s temporary mobile identity is changed via non-3GPP access through the AMF, the UE and NG-RAN release the assigned RRC resources and enter an RRC idle state.

[0034] Other aspects of the invention propose that the UE updates its new temporary mobility identity to the NG-RAN via an RRC message.

[0035] Another aspect of the present invention proposes that the AMF updates the new temporary mobile identity assigned to the UE via non-3GPP access to the NG-RAN.

[0036] The solution proposed in this invention offers technical advantages, wherein temporary identity synchronization for paging between the UE and the network is utilized even in scenarios where the UE is connected to the same AMF via 3GPP access and non-3GPP access, the UE is in an RRC inactive state on the 3GPP access, and the UE's temporary identity changes on the non-3GPP access. Therefore, when the UE is in an inactive state in CM connection mode and the UE's GUTI changes via non-3GPP access, the correct temporary identity can be used to paging the UE, and in the event of AMF relocation on non-3GPP access, NG-RAN can route the UE to the new AMF on 3GPP access.

[0037] In an aspect of the invention, a method for a user equipment (UE) is provided, the method comprising the steps of: during a first non-access stratum procedure (NAS) between the UE and the Access and Mobility Function (AMF) of a Public Land Mobile Network (PLMN), receiving a first temporary mobility identity of the UE from the AMF via a 3GPP access node; on 3GPP access, entering a 5GS Mobility Management Connection State (5GMM Connection State) in a Radio Resource Control (RRC) inactive state; and during a second NAS procedure on non-3GPP access between the UE and the AMF, receiving a second temporary mobility identity of the UE from the AMF via a non-3GPP access node. The method further comprises: upon receiving the second temporary mobility identity, transitioning from the 5GMM Connection State in the RRC inactive state to a 5GMM Idle State in the RRC Idle state.

[0038] The method further includes: upon receiving the second temporary mobile identity, releasing the stored RRC context and the RRC resources stored in the UE, and releasing the RRC connection established with the 3GPP access node.

[0039] According to another aspect, the method further includes: before entering the 5GMM idle state from the RRC inactive state to the RRC idle state, sending an RRC message to the 3GPP access node to release the RRC resources associated with the UE and release the RRC connection established with the UE.

[0040] In another aspect of the invention, a method for use by a 3GPP access node is provided, the method comprising: transmitting a first temporary mobility identity of the UE from the AMF during a first non-access stratum procedure, i.e., a first NAS procedure, between a user equipment (UE) and an access and mobility function (AMF) of a public land mobile network (PLMN); instructing the UE to enter a radio resource control inactive state, i.e., an RRC inactive state, wherein the UE maintains a 5GS mobility management connection state, i.e., a 5GMM connection state, after entering the RRC inactive state; and storing an identity corresponding to the first temporary mobility identity for use in radio access network paging, i.e., RAN paging, wherein the method further comprises: receiving from the UE or the AMF a message for releasing RRC resources associated with the UE and for releasing an RRC connection established with the UE; and upon receiving the message for releasing RRC resources associated with the UE, releasing the RRC resources including the stored temporary mobility identity and the RRC connection.

[0041] According to another aspect, a method used by the Access and Mobility Management Function (AMF) is disclosed. The method includes: during a first Non-Access Stratum (NAS) procedure between the UE and the AMF of a Public Land Mobile Network (PLMN), sending a first temporary mobile identity (TMI) of the UE to the UE via a 3GPP access node; and during a second NAS procedure between the UE and the AMF, updating the first TMI to a second TMI and sending the second TMI to the UE via a non-3GPP access node. The method further includes: if the second TMI is sent to the UE via the non-3GPP access node, sending a message to the 3GPP access node for releasing RRC resources associated with the UE and for releasing the RRC connection established with the UE.

[0042] According to another aspect of the present invention, a method for a user equipment (UE) is disclosed, the method comprising: during a first non-access stratum procedure (NAS) between the UE and the access and mobility function (AMF) of a public terrestrial mobile network (PLMN), receiving a first temporary mobility identity of the UE from the AMF via a 3GPP access node; entering a 5GS mobility management connection state (5GMM connection state) in a radio resource control inactive state (RRC inactive state); and during a second NAS procedure between the UE and the AMF on a non-3GPP access, receiving a second temporary mobility identity of the UE from the AMF via a non-3GPP access node, wherein the method further comprises: sending a third temporary mobility identity of the UE to the 3GPP access node, wherein the third temporary mobility identity is the second temporary mobility identity or derived from the second mobility identity.

[0043] The UE sends a third temporary mobility identity in one of the RRC connection restoration request message and the RRC connection re-establishment request message, wherein the UE is configured to be able to re-enter or remain in the RRC inactive state after sending the third temporary mobility identity.

[0044] According to another aspect, a method used by a 3GPP access node is disclosed, the method comprising: transmitting a first temporary mobility identity of the UE from the AMF during a first non-access stratum procedure, i.e., a first NAS procedure, between a user equipment (UE) and an access and mobility function (AMF) of a public land mobile network (PLMN); instructing the UE to enter a radio resource control inactive state, i.e., an RRC inactive state, wherein the UE maintains a 5GS mobility management connection state, i.e., a 5GMM connection state, after entering the RRC inactive state; and storing an identity corresponding to the first temporary mobility identity for use in radio access network paging, i.e., RAN paging, wherein the method further comprises: receiving a third temporary mobility identity of the UE from the UE or the AMF, wherein the third temporary mobility identity is a second temporary mobility identity or derived from the second temporary mobility identity.

[0045] According to another aspect, a method for use by the Access and Mobility Function (AMF) is disclosed, the method comprising: during a first non-access stratum procedure (NAS) between a UE and the AMF of a Public Land Mobile Network (PLMN), sending a first temporary mobility identity (TMI) of the UE to the UE via a 3GPP access node; and during a second NAS procedure between the UE and the AMF on a non-3GPP access, updating the first TMI to a second TMI and sending the second TMI to the UE via a non-3GPP access node, wherein the method further comprises: if the second TMI is sent to the UE via the non-3GPP access node, sending a third TMI of the UE to the 3GPP access node, wherein the third TMI is the second TMI or derived from the second TMI. Attached Figure Description

[0046] The foregoing and other objects, features and advantages of this subject matter will become apparent from the following description of exemplary aspects with reference to the accompanying drawings, wherein the same reference numerals are used to denote the same elements.

[0047] However, it should be noted that the accompanying drawings and reference numerals only illustrate typical aspects of the subject matter and are therefore not considered as a limitation on the scope of the subject matter, as other equivalent aspects may be permitted.

[0048] Figure 1 A user equipment according to the present invention is shown.

[0049] Figure 2 The (R)AN according to the present invention is shown.

[0050] Figure 3 An AMF according to the present invention is shown.

[0051] Figure 4A The UE local release process according to the present invention is illustrated.

[0052] Figure 4B Another UE local release process according to the present invention is shown.

[0053] Figure 5A The UE and NG-RAN release process according to the present invention is illustrated.

[0054] Figure 5B Another UE and NG-RAN release process according to the present invention is shown.

[0055] Figure 6A The procedure for updating a temporary mobile identifier according to the present invention is illustrated.

[0056] Figure 6BAnother temporary movement identifier update process according to the present invention is shown.

[0057] Figure 7A The UE and network process according to the present invention are illustrated.

[0058] Figure 7B Another UE and network process according to the present invention is shown.

[0059] Figure 8A The UE and network process according to the present invention are illustrated.

[0060] Figure 8B Another UE and network process according to the present invention is shown.

[0061] Figure 9 A general block diagram of a communication system according to the present invention is shown. Detailed Implementation

[0062] Exemplary aspects will now be described with reference to the accompanying drawings. However, the invention may be embodied in many different forms and should not be construed as limited to the aspects set forth herein; rather, these aspects are provided so that the invention will be exhaustive and complete, and its scope will be fully conveyed to those skilled in the art. The terminology used in the detailed description of the specific exemplary aspects shown in the drawings is not intended to be limiting. In the drawings, the same reference numerals refer to the same elements.

[0063] However, it should be noted that the reference numerals in the claims are merely illustrative of typical aspects of the subject matter and are therefore not considered as a limitation on the scope of the subject matter, as other equivalent aspects may be permitted.

[0064] The specification may refer to "an," "a," or "some" aspects in multiple places. This does not necessarily mean that every such reference refers to the same aspect or that the feature applies only to a single aspect. Individual features of different aspects may also be combined to provide other aspects.

[0065] As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms, unless otherwise expressly stated. It should also be understood that the terms “includes,” “comprises,” “including,” and / or “comprising,” as used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof. It should be understood that where an element is referred to as “connected” or “coupled” to another element, the element may be directly connected or coupled to that other element, or there may be intermediate elements. Furthermore, as used herein, “connected” or “coupled” can include operatively connected or coupled. As used herein, the term “and / or” includes any and all combinations and arrangements of one or more of the related listed items.

[0066] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms (such as those defined in common dictionaries) shall be interpreted as having a meaning consistent with their meaning in the context of the relevant field and shall not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0067] These figures depict a simplified structure showing only a few elements and functional entities, all of which are logical units whose implementation may differ from the one shown. The connections shown are logical connections; actual physical connections may differ. It will be apparent to those skilled in the art that this structure may also include other functions and structures.

[0068] Additionally, all logical units described and depicted in the figures include the software and / or hardware components required for the unit to operate. Furthermore, each unit itself may include one or more components, as implicitly understood. These components may be operatively coupled to each other and configured to communicate with each other to perform the functions of the unit.

[0069] In such Figure 1 In the aspects of the invention shown, a user equipment according to the invention is described.

[0070] As shown in the figure, the UE (100) includes a transceiver circuit (103) that is operatively capable of transmitting and receiving signals from connected nodes via one or more antennas (104). Although Figure 1While not necessarily shown, the UE will certainly have all the common functions of a conventional mobile device (such as a user interface), and these functions can be appropriately provided through any one or any combination of hardware, software, and firmware. For example, software may be pre-installed in memory and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD).

[0071] The controller (101) controls the operation of the UE based on software stored in the memory (105). The software includes an operating system and a communication control module (106) having at least a transceiver control module (107). The communication control module (106) (using its transceiver control submodule) is responsible for processing (generating / sending / receiving) signaling and uplink / downlink data packets between the UE and other nodes such as base stations / (R)AN nodes, AMFs (and other core network nodes). Such signaling may include, for example, appropriately formatted signaling messages related to connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), periodic location update related messages (e.g., tracking area update, paging area update, location area update), etc. Such signaling may also include, for example, broadcast information in the case of reception (e.g., master information and system information).

[0072] The term "UE" is generally intended to be synonymous with the terms "mobile station," "mobile device," and "wireless device," and includes standalone mobile stations such as terminals, cellular phones, smartphones, tablets, cellular IoT devices, IoT devices, and machines. The term "UE" is also the UE used by 3GPP.

[0073] UE can be production equipment, energy-related machinery (such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal generators, nuclear generators, batteries, nuclear systems and equipment, etc.), heavy-duty electric motors, pumps, compressors, vacuum pumps, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, robotic arms, robots and their application systems, tools, injection molds and die-casting molds, rolls, conveying, lifting, material handling equipment and their application systems, textile machinery, sewing machines, printing and related machinery, papermaking machinery, chemical machinery, mining and construction machinery and equipment, machinery and equipment for agriculture, forestry and fisheries, safety and environmental protection equipment, traction devices, construction machinery, precision bearings, chains, gears, power transmission, lubrication equipment, valves, pipe fittings, etc.

[0074] UE can be transportation equipment (such as rail vehicles, motor vehicles, motorcycles, bicycles, trains, buses, handcarts, rickshaws, ships and vessels, airplanes, rockets, satellites, drones, balloons, etc.).

[0075] Optionally, the UE can be an information and communication device (such as electronic computers and related equipment, communication and related equipment, electronic components, etc.).

[0076] Optionally, UE can be a refrigeration unit, refrigeration unit application products, trade and service industry equipment, vending machines, automated service machines, office machines and equipment, consumer electronics and appliances (such as audio equipment, video equipment, speakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electric fans and related equipment, cleaners, etc.).

[0077] UE can be an electrical application system (such as an X-ray system, particle accelerator, radio isotope equipment, audio equipment, electromagnetic application equipment, power application equipment, etc.).

[0078] UE can be electronic lamps, lighting devices, measuring instruments, analyzers, testers and mapping instruments (such as smoke detectors, human body alarm sensors, motion sensors, wireless tags, etc.), clocks, laboratory instruments, optical equipment, medical devices and systems, weapons, tableware, and hand tools.

[0079] The UE can be a wirelessly equipped personal digital assistant (such as a wireless card or module, which is designed to be attached to or inserted into another electronic device (such as a personal computer or electronic measuring machine)).

[0080] The UE can be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services and solutions described below regarding the "Internet of Things (IoT)".

[0081] Applications, services, and solutions can include MVNO (Mobile Virtual Network Operator) services, emergency radio communication systems, PBX (Private Branch Exchange) systems, PHS / digital cordless telecommunications systems, POS systems, advertising call systems, MBMS (Multimedia Broadcast and Multicast Service) systems, V2X (Vehicle-to-Everything) systems, train radio systems, location-related services, disaster / emergency wireless communication services, community services, video streaming services, femtocell application services, VoLTE services, pay-per-view services, radio on-demand services, roaming services, activity monitoring services, telecom operator / communication NW selection services, feature-limited services, PoC (Proof of Concept) services, personal information management services, and self-organizing network / DTN (Depth Tolerant Network) services, etc.

[0082] Furthermore, the UE described above is merely an example of the application of technical concepts, and these technical concepts are not limited to the UE described above, and can be modified in various ways.

[0083] Figure 2This is a block diagram illustrating the main components of an exemplary (R)AN node (200) (e.g., a base station (e.g., an "eNB" in LTE, an "NG-RAN" or "gNB" in 5G)). As shown, the (R)AN node (200) includes transceiver circuitry (203) operable to transmit and receive signals from a connected UE via one or more antennas (204), and to transmit and receive signals from other network nodes via a network interface (directly or indirectly). A controller (201) controls the operation of the (R)AN node based on software stored in a memory (205). For example, the software may be pre-installed in the memory and / or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system and a communication control module (206) having at least a transceiver control module (207), etc. The (R)AN may include a 3GPP access node and a non-3GPP access node.

[0084] The communication control module (206) (using its transceiver control submodule) is responsible for processing (generating / sending / receiving) signaling between the (R)AN node and other nodes such as the UE, MME, AMF, etc. (e.g., directly or indirectly). Signaling may include, for example, appropriately formatted signaling messages related to (for a specific UE) radio connection and positioning procedures, particularly those related to connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), periodic location update related messages (e.g., tracking area update, paging area update, location area update), S1 AP messages, and NG AP messages (i.e., messages via the N2 reference point), etc. Such signaling may also include, for example, broadcast information in the case of transmission (e.g., master information and system information).

[0085] The controller is also configured (via software or hardware) to handle related tasks such as UE motion estimation and / or motion trajectory estimation (where applicable).

[0086] Figure 3 This is a block diagram showing the main components of the AMF (300). The AMF is included in the 5GC. As shown, the AMF (300) includes transceiver circuitry (303) that is operatively capable of sending and receiving signals from other nodes (including UEs) via a network interface. A controller (301) controls the operation of the AMF (300) based on software stored in memory. For example, the software may be pre-installed in memory and / or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system and a communication control module (305) having at least a transceiver control module (306), etc.

[0087] The communication control module (using its transceiver control submodule) is responsible for handling (generating / transmitting / receiving) signaling between the AMF and other nodes such as the UE, base station / (R)AN nodes (e.g., "gNB" or "eNB"), either directly or indirectly. This signaling may include, for example, appropriately formatted signaling messages related to the procedures described herein, such as NG AP messages (i.e., messages via the N2 reference point) for transmitting NAS messages from and to the UE.

[0088] Figure 4A The UE local release process is described, in which the UE releases the assigned RRC resources and enters the RRC IDLE state when the UE's temporary mobile identity is changed via non-3GPP access via AMF.

[0089] At (401), the UE has registered with the PLMN's AMF via 3GPP access with a first temporary mobile identity (e.g., 5G-GUTI). The UE has entered a CM-CONNECTED state that is in RRC inactive. More specifically, in step 401, the UE sends a first registration request message to the AMF via a 3GPP access node (e.g., an NG-RAN node), and the UE receives a first registration acceptance message from the AMF via 3GPP access. The first registration request message and the first registration acceptance message can be NAS messages. Therefore, the messages are transmitted transparently through the 3GPP access node. The first registration acceptance message may include the first temporary mobile identity. The UE may adjust to a CM-CONNECTED state that is in RRC inactive in response to an instruction from the 3GPP access node. Furthermore, when the UE adjusts to an RRC inactive state, the 3GPP access node may store an identity (e.g., old S-TMSI) corresponding to the first mobile identity for use in radio access network (RAN) paging. Step 401 may be performed as part of a first registration process between the UE and the AMF. At (402), the AMF assigns a second temporary mobile identity to the UE and sends the second temporary mobile identity to the UE in a NAS message on a non-3GPP access. More specifically, in step 402, the UE sends a second registration request message to the same AMF via a non-3GPP access node (e.g., a WLAN access point). The AMF updates the UE's first mobile identity to the second mobile identity. Then, the UE receives a second registration acceptance message from the AMF via a non-3GPP access. The second registration request message and the second registration acceptance message can both be NAS messages. Therefore, the messages are transparently sent via a non-3GPP access node. The second registration acceptance message may include the second temporary mobile identity. Step 402 can be performed as part of a second registration process between the UE and the AMF. At (403), upon receiving the second mobile identity, the UE enters a CM-IDLE state in an RRC-IDLE state. Optionally, in step 403, the UE may release stored RRC context and resources.

[0090] A second temporary mobility identity is assigned to the UE by AMF1 or AMF2 (which is not AMF1). The second temporary mobility identity is sent to the UE in a NAS message in the following cases:

[0091] (1) The UE is undergoing an initial registration process with the PLMN's AMF1 via a non-3GPP access; or

[0092] (2) The UE has registered with the PLMN's AMF1 via a non-3GPP access and the UE (e.g., for reasons defined in 3GPP 24.501) is currently in the process of registering with the PLMN's AMF1 via a non-3GPP access; or

[0093] (3) The UE is in CM-CONNECTED mode and the AMF is relocated for the UE. The UE moves to AMF2, and AMF2 assigns a new 5G-GUTI to the UE; or

[0094] (4) AMF1 decides to proceed with the AMF program removal process and AMF2 is reassigned to the UE.

[0095] here, Figure 4B This illustrates another UE local release procedure in the AMF relocation scenario described in some of the above cases.

[0096] The NAS message is either an existing registration management message (e.g., an attachment acceptance message, registration acceptance message, or configuration update command) or a new NAS message. The UE enters the CM-IDLE state from the RRC-IDLE state. The UE also releases the stored RRC context and resources. The UE releases the RRC context and resources and deletes the first temporary mobility identifier.

[0097] Figure 5A The diagram illustrates the UE and NG-RAN release process, in which, when the UE's temporary mobile identity changes via non-3GPP access via AMF, the UE and NG-RAN release the assigned RRC resources and enter the RRC IDLE state.

[0098] At (501), the UE has registered with the PLMN's AMF via 3GPP access with a first temporary mobile identity (e.g., 5G-GUTI). The UE has entered a CM-CONNECTED state that is in RRC inactive. More specifically, in step 501, the UE sends a first registration request message to the AMF via a 3GPP access node (e.g., an NG-RAN node), and the UE receives a first registration acceptance message from the AMF via 3GPP access. The first registration request message and the first registration acceptance message can be NAS messages. Therefore, the messages are transmitted transparently through the 3GPP access node. The first registration acceptance message may include the first temporary mobile identity. The UE may adjust to a CM-CONNECTED state that is in RRC inactive in response to an instruction from the 3GPP access node. Furthermore, when the UE adjusts to an RRC inactive state, the 3GPP access node may store an identity (e.g., old S-TMSI) corresponding to the first mobile identity for use in radio access network (RAN) paging. Step 501 may be performed as part of a first registration process between the UE and the AMF. At (502), the AMF assigns a second temporary mobile identity to the UE and sends the second temporary mobile identity to the UE in a NAS message on a non-3GPP access node. More specifically, in step 502, the UE sends a second registration request message to the same AMF via a non-3GPP access node (e.g., a WLAN access point). The AMF updates the UE's mobile identity from the first mobile identity to the second mobile identity. Then, the UE receives a second registration acceptance message from the AMF via a non-3GPP access node. The second registration request message and the second registration acceptance message can both be NAS messages. Therefore, the messages are transmitted transparently through the non-3GPP access node. The second registration acceptance message may include the second temporary mobile identity. Step 502 can be performed as part of a second registration process between the UE and the AMF.

[0099] Regarding step 502, a second temporary mobility identity is assigned to the UE by AMF1 or AMF2 (which is not AMF1). The second temporary mobility identity is sent to the UE in the NAS message in the following cases:

[0100] (1) The UE is undergoing an initial registration process with the PLMN's AMF1 via a non-3GPP access; or

[0101] (2) The UE has registered with the PLMN's AMF1 via a non-3GPP access and the UE (e.g., for reasons defined in 3GPP 24.501) is currently in the process of registering with the PLMN's AMF1 via a non-3GPP access; or

[0102] (3) The UE is in CM-CONNECTED mode and the AMF for the UE is relocated. The UE moves to AMF2, and AMF2 assigns a new 5G-GUTI to the UE; or

[0103] (4) AMF1 decides to proceed with the AMF program removal process and AMF2 is reassigned to the UE.

[0104] here, Figure 5B This illustrates another UE and NG-RAN release procedure in the AMF relocation scenario described in some of the above cases.

[0105] At (503), upon receiving the second mobility identity, the UE enters the CM-IDLE state, which is in the RRC-IDLE state. The UE releases the stored RRC context and resources. In this scenario, the NAS message is an existing registration management message (e.g., a registration acceptance message or a configuration update command) or a new NAS message. Upon entering the CM-IDLE state, the UE releases the stored RRC context and resources. At (504), the UE sends an RRC message with a first temporary mobility identifier and a release indication to the NG-RAN, causing the NG-RAN to release the RRC resources used by the UE at (505). The first temporary mobility identifier can be S-TMSI, I-RNTI, GUTI, or 5G GUTI. The release indication indicates that the purpose of the message is to release the RRC resources for the UE in the NG-RAN. This RRC message can be an RRC connection restoration request message or an RRC connection establishment request message. The RRC message is an RRC RESUME REQUEST message or an RRC CONNECTION REQUEST message, another existing RRC message, or a new RRC message. The NG-RAN releases the RRC resources used by the UE identified by the temporary mobility identifier. Optionally, at (506), the NG-RAN sends an RRC message to the UE. This message may have a reason indicating a successful resource release in the NG-RAN. The RRC message may be an RRC release message. The RRC message is an existing RRC message (e.g., an RRC connection restoration or a new RRC message). Optionally, at (507), the UE may send an RRC completion message to the NG-RAN in response to the received RRC message to acknowledge receipt of the RRC message. The RRC completion message may contain some UE-related parameters. The UE deletes the first temporary mobility identifier.

[0106] Here, in order to send an RRC message to the NG-RAN that no longer has a connection with the UE, the UE can retain the information used to identify the NG-RAN node even if the UE releases the stored RRC context and resources in step 503. Alternatively, step 503 can be performed after step 507.

[0107] Figure 6A The temporary mobility identifier update process is described, in which the UE updates the new temporary mobility identity to the NG-RAN via an RRC message.

[0108] At (601), the UE has registered with the PLMN's AMF with a first temporary mobile identity (e.g., 5G-GUTI) via 3GPP access. The UE has entered a CM-CONNECTED state that is in RRC inactive. More specifically, in step 601, the UE sends a first registration request message to the AMF via a 3GPP access node (e.g., an NG-RAN node), and the UE receives a first registration acceptance message from the AMF via 3GPP access. The first registration request message and the first registration acceptance message can be NAS messages. Therefore, the messages are transmitted transparently through the 3GPP access node. The first registration acceptance message may include the first temporary mobile identity. The UE may adjust to a CM-CONNECTED state in RRC inactive in response to an instruction from the 3GPP access node. Furthermore, when the UE adjusts to an RRC inactive state, the 3GPP access node may store an identity (e.g., old S-TMSI) corresponding to the first mobile identity for use in radio access network (RAN) paging. Step 601 may be performed as part of a first registration process between the UE and the AMF. At (602), the AMF assigns a second temporary mobile identity (e.g., 5G-GUTI) to the UE via a non-3GPP access point and sends the second temporary mobile identity to the UE in a NAS message on the non-3GPP access point. More specifically, in step 602, the UE sends a second registration request message to the same AMF via a non-3GPP access node (e.g., a WLAN access point). The AMF updates the UE's mobile identity from the first mobile identity to the second mobile identity. Then, the UE receives a second registration acceptance message from the AMF via the non-3GPP access point. The second registration request message and the second registration acceptance message can both be NAS messages. Therefore, the messages are transparently sent via the non-3GPP access node. The second registration acceptance message can include the second temporary mobile identity. Step 602 can be performed as part of a second registration process between the UE and the AMF.

[0109] Regarding step 602, a second temporary mobility identity is assigned to the UE by AMF1 or AMF2 (which is not AMF1). The second temporary mobility identity is sent to the UE in the NAS message in the following cases:

[0110] (1) The UE is undergoing an initial registration process with the PLMN's AMF1 via a non-3GPP access; or

[0111] (2) The UE has registered with the PLMN's AMF1 via a non-3GPP access and the UE (e.g., for reasons defined in 3GPP 24.501) is currently in the process of registering with the PLMN's AMF1 via a non-3GPP access; or

[0112] (3) The UE is in CM-CONNECTED mode and the AMF is relocated for the UE. The UE moves to AMF2, and AMF2 assigns a new 5G-GUTI to the UE; or

[0113] (4) AMF1 decides to proceed with the AMF program removal process and AMF2 is reassigned to the UE.

[0114] here, Figure 6B This illustrates another UE local release procedure in the AMF relocation scenario described in some of the above cases.

[0115] At (603), the UE sends a third temporary mobility identity (e.g., 5G-GUTI, S-TMSI) to the NG-RAN in an RRC message. The third temporary mobility identity is derived from or is based on the second temporary mobility identity. In subsequent AS and NAS procedures, the UE and AMF use either the third temporary mobility identity or the second temporary mobility identity. The NAS message is an existing NAS message (e.g., an attachment acceptance message, a registration acceptance message, or a configuration update command) or a new NAS message.

[0116] In step 603, in addition to the third temporary mobility identity, the UE may also send a first temporary mobility identity. As described above, the third temporary identity is derived from the second temporary mobility identity (e.g., the third mobility identity is an S-TMSI derived from the new GUTI (second temporary mobility identity), or the second temporary mobility identity (e.g., the new GUTI). The first temporary mobility identity is an I-RNTI as defined in 38.300, a recovery identity as defined in 36.331, or a temporary mobility identity (e.g., 5G-GUTI or 5G-S-TMSI). The NG-RAN uses the first temporary mobility identity to obtain the UE AS context. The RRC message may be an RRC connection restoration request message or an RRC connection establishment request message.

[0117] At (604), NG-RAN stores the UE's third temporary mobility identity, and NG-RAN uses the third temporary mobility identity in subsequent processes related to the UE (e.g., in a scenario where the UE is in an RRC INACTIVE state in NG-RAN, or when NG-RAN initiates RAN paging, NG-RAN sends the third temporary mobility identity).

[0118] Optionally, at (605), the NG-RAN sends an RRC message to the UE. This message may contain a reason indicating a successful temporary mobility identity update in the NG-RAN. The RRC message may be an RRC connection setup message, an RRC connection restoration message, another RRC message, or a new RRC message. The UE deletes the first temporary mobility identifier.

[0119] Optionally, at (606), the UE may send an RRC completion message to the NG-RAN. This RRC message may be an RRC connection setup completion message, an RRC connection restoration completion message, another RRC message, or a new RRC message.

[0120] Figure 7A The UE and network behavior is described, in which the AMF updates the new temporary mobile identity assigned to the UE via non-3GPP access to the NG-RAN.

[0121] At (701), the UE has registered with the PLMN's AMF via 3GPP access with a first temporary mobile identity (e.g., 5G-GUTI). The UE has entered a CM-CONNECTED state that is in RRC inactive. More specifically, in step 701, the UE sends a first registration request message to the AMF via a 3GPP access node (e.g., an NG-RAN node), and the UE receives a first registration acceptance message from the AMF via 3GPP access. The first registration request message and the first registration acceptance message can be NAS messages. Therefore, the messages are transmitted transparently through the 3GPP access node. The first registration acceptance message may include the first temporary mobile identity. The UE may adjust to a CM-CONNECTED state in RRC in response to an instruction from the 3GPP access node. Furthermore, when the UE adjusts to an RRC inactive state, the 3GPP access node may store an identity (e.g., old S-TMSI) corresponding to the first mobile identity for use in radio access network (RAN) paging. Step 701 can be performed as part of a first registration process between the UE and the AMF. At (702), the AMF assigns a second temporary mobile identity (e.g., 5G-GUTI) to the UE via a non-3GPP access point and sends the second temporary mobile identity to the UE in a NAS message. More specifically, in step 702, the UE sends a second registration request message to the same AMF via a non-3GPP access node (e.g., a WLAN access point). The AMF updates the UE from a first mobile identity to a second mobile identity. Then, the UE receives a second registration acceptance message from the AMF via a non-3GPP access point. The second registration request message and the second registration acceptance message can both be NAS messages. Therefore, the messages are transparently sent via a non-3GPP access node. The second registration acceptance message can include the second temporary mobile identity. Step 702 can be performed as part of a second registration process between the UE and the AMF. At (703), the AMF updates the NG-RAN with a new temporary mobile identity (represented as a third temporary mobile identity) derived from the second temporary mobile identity assigned via a non-3GPP access point by sending the new temporary mobile identity in an NGAP message. The NG-RAN uses the new temporary mobile identity in subsequent AS and NAS processes.

[0122] Regarding step 702, a second temporary mobility identity is assigned to the UE by AMF1 or AMF2 (which is not AMF1). The second temporary mobility identity is sent to the UE in the NAS message in the following cases:

[0123] (1) The UE is undergoing an initial registration process with the same AMF1 of the PLMN via a non-3GPP access; or

[0124] (2) The UE has registered with the same AMF1 of the PLMN via a non-3GPP access and the UE (e.g., for reasons defined in 3GPP24.501) is in the process of registering with the same AMF1 of the PLMN via a non-3GPP access.

[0125] (3) The UE is in CM-CONNECTED mode and the AMF is relocated for the UE. The UE moves to AMF2 and a new 5G-GUTI is assigned to the UE; or

[0126] (4) AMF1 decides to proceed with the AMF program removal process and AMF2 is reassigned to the UE.

[0127] here, Figure 7B This illustrates another UE and network behavior in the AMF relocation scenario described in some of the above cases.

[0128] The NAS message is either an existing NAS message (e.g., an Attach Accept message, a Registration Accept message, or a Configuration Update command) or a new NAS message. The UE deletes the first temporary mobility identifier and uses a second temporary mobility identifier or a third temporary mobility identity derived from the second temporary mobility identity. At (703), the AMF (1 or 2) sends a message containing the third temporary mobility identity to the NG-RAN. The third temporary identity is derived from the second temporary mobility identity (e.g., the third temporary mobility identity is an S-TMSI derived from the new GUTI (second temporary mobility identity), or the second temporary mobility identity (e.g., the new GUTI). The message is either an existing NGAP message (e.g., a UE CONTEXT MODIFICATION REQUEST) or a new NGAP message. At (704), the NG-RAN may send an N2 message response to the AMF (1 or 2). At (705), the NG-RAN maintains the CM-CONNECTED state of the UE with the third temporary mobility identity in an RRC inactive state. Then, NG-RAN stores the UE's third temporary mobility identity, and NG-RAN uses the third temporary mobility identity in subsequent processes related to the UE (e.g., in a scenario where the UE is in RRC INACTIVE state and NG-RAN initiates RAN paging, NG-RAN sends the third temporary mobility identity).

[0129] The present invention Figure 8A The UE and network procedures were disclosed, in which the N2 connection was released by the AMF.

[0130] At (801), the UE has registered with the PLMN's AMF via 3GPP access with a first temporary mobile identity (e.g., 5G-GUTI). The UE has entered a CM-CONNECTED state that is in RRC inactive. More specifically, in step 801, the UE sends a first registration request message to the AMF via a 3GPP access node (e.g., an NG-RAN node), and the UE receives a first registration acceptance message from the AMF via 3GPP access. The first registration request message and the first registration acceptance message can be NAS messages. Therefore, the messages are transmitted transparently through the 3GPP access node. The first registration acceptance message may include the first temporary mobile identity. The UE may adjust to a CM-CONNECTED state that is in RRC inactive in response to an instruction from the 3GPP access node. Furthermore, when the UE adjusts to an RRC inactive state, the 3GPP access node may store an identity (e.g., old S-TMSI) corresponding to the first mobile identity for use in radio access network (RAN) paging. Step 401 may be performed as part of the first registration process between the UE and the AMF. At (802), the AMF assigns a second temporary mobile identity (e.g., 5G-GUTI) to the UE and sends the second temporary mobile identity to the UE in a NAS message. More specifically, in step 802, the UE sends a second registration request message to the same AMF via a non-3GPP access node (e.g., a WLAN access point). The AMF updates the UE's mobile identity from the first mobile identity to the second mobile identity. Then, the UE receives a second registration acceptance message from the AMF via the non-3GPP access node. The second registration request message and the second registration acceptance message can both be NAS messages. Therefore, the messages are transparently sent via the non-3GPP access node. The second registration acceptance message may include the second temporary mobile identity. Step 802 can be performed as part of a second registration process between the UE and the AMF.

[0131] Regarding step 802, AMF1 assigns a second temporary mobility identity to the UE. The second temporary mobility identity is sent to the UE in the NAS message under the following circumstances:

[0132] (1) The UE is undergoing an initial registration process with the same AMF1 of the PLMN via a non-3GPP access; or

[0133] (2) The UE has registered with the same AMF1 of the PLMN via a non-3GPP access and the UE (e.g., for reasons defined in 3GPP24.501) is in the process of registering with the same AMF1 of the PLMN via a non-3GPP access.

[0134] (3) The UE is in CM-CONNECTED mode and the AMF is relocated for the UE. The UE moves to AMF2, and the AMF assigns a new 5G-GUTI to the UE; or

[0135] (4) AMF1 decides to proceed with the AMF program removal process and AMF2 is reassigned to the UE.

[0136] here, Figure 8B This illustrates another UE and network procedure in the AMF relocation scenario described in some of the above cases.

[0137] At (803), the AMF (1 or 2) releases the connection between the NG-RAN and the AMF for the UE by sending a message to the NG-RAN instructing the NG-RAN to release the UE context and the connection between the NG-RAN and the AMF.

[0138] In one example, the connection between NG-RAN and AMF is an N2 connection. AMF (1 or 2) initiates an N2 release procedure. At (804), NG-RAN may send an N2 message response to AMF (1 or 2). At (805), if NG-RAN receives an NGAP message requesting it to release the connection between NG-RAN and AMF, NG-RAN releases the connection between NG-RAN and AMF. NG-RAN also releases the UE context stored in NG-RAN. The NGAP message is either an existing NGAP message (e.g., UECONTEXT RELEASE COMMAND (UE context release command)) or a new NGAP message.

[0139] Following this process, the following procedures can be performed.

[0140] (1) When the UE receives a second temporary mobile identity, the UE enters the CM IDLE state and the RRCIDLE state, and releases the RRC resources assigned to the UE. If a NAS procedure is initiated, the UE initiates a new RRC connection.

[0141] (2) The UE triggers the recovery process by sending an RRC message. The NG-RAN rejects the recovery process or sets up a new RRC connection.

[0142] Figure 9A block diagram of the communication system (900) of the present invention is described. A UE (901) in the communication network is configured to register with the AMF (902) of the PLMN on a 3GPP access (NG-RAN) (903). The UE (901) is also configured to register with the AMF (902) of the PLMN on a non-3GPP access (WLAN node) (904). The 3GPP access (903) is configured to transmit messages from the UE (901) to the AMF (902) and messages from the AMF to the UE. The non-3GPP access (903) is configured to transmit messages from the UE (901) to the AMF (902) and messages from the AMF to the UE. The AMF (902) is configured to assign a temporary mobility identity to the UE.

[0143] As will be understood by those skilled in the art, the present invention can be embodied as methods and systems. Therefore, the present invention can take the form of entirely hardware, software, or a combination of both.

[0144] It should be understood that the individual blocks in the block diagram can be implemented using computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, or other programmable data processing device to produce a machine, such that these instructions, executed via the processor of the computer or other programmable data processing device, create components for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. The general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., multiple microprocessors, more than one microprocessor, or any other such configuration).

[0145] The methods or algorithms described in conjunction with the examples disclosed herein can be directly embodied in hardware, software modules executed by a processor, or a combination of both. The software modules can reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. The storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with the processor. The processor and storage medium can reside in an ASIC.

[0146] The prior description of the disclosed examples is provided to enable those skilled in the art to make or utilize the invention. Various modifications to these examples will be apparent to those skilled in the art, and the general principles defined herein can be applied to other examples without departing from the spirit or scope of the invention. Therefore, the invention is not limited to the examples shown herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

[0147] abbreviation

[0148] For the purposes of this invention, the following abbreviations shall be used:

[0149] 5GC 5G Core Network

[0150] 5GS 5G system

[0151] 5G-AN 5G Access Network

[0152] 5G-GUTI 5G Globally Unique Temporary Identifier

[0153] 5GMM 5GS Mobility Management

[0154] 5G S-TMSI 5G S-Temporary Mobile Subscription Identifier

[0155] 5QI 5G QoS identifier

[0156] AF Application Functions

[0157] AMF Access and Mobility Management Functions

[0158] AN access node

[0159] AS Access Layer

[0160] AUSF Authentication Server Functionality

[0161] CP control plane

[0162] CM Connection Management

[0163] DL downlink

[0164] DN Data Network

[0165] DNAI DN Access Identifier

[0166] DNN Data Network Name

[0167] Early Data Transmission (EDT)

[0168] EPS Evolution Grouping System

[0169] EPC Evolution Group Core

[0170] FQDN (Fully Qualified Domain Name)

[0171] GFBR guarantees stream bit rate

[0172] GMLC Gateway Mobile Location Center

[0173] GPSI General Public Subscription Identifier

[0174] GUAMI Globally Unique AMF Identifier

[0175] HR Home Router (Roaming)

[0176] I-RNTI (I-Radio Network Temporary Identifier)

[0177] LADN Local Data Network

[0178] LBO Local Traffic Management (Roaming)

[0179] LMF location management function

[0180] LRF location retrieval function

[0181] MAC Media Access Control

[0182] MFBR Maximum Stream Bit Rate

[0183] MICO only initiates connections via mobile.

[0184] MME Mobility Management Entity

[0185] N3IWF Non-3GPP Interoperability Function

[0186] NAI Network Access Identifier

[0187] NAS Non-Access Layer

[0188] NEF Network Open Functions

[0189] NF Network Functions

[0190] NG-RAN (Next Generation Radio Access Network)

[0191] NR New Radio

[0192] NRF Network Repository Functionality

[0193] NSI ID (Network Slice Instance Identifier)

[0194] NSSAI Network Slice Selection Auxiliary Information

[0195] NSSF Network Slice Selection Function

[0196] NSSP Network Slice Selection Strategy

[0197] PCF policy control function

[0198] PEI Permanent Device Identifier

[0199] PER grouping error rate

[0200] PFD Packet Flow Description

[0201] PLMN Public Land Mobile Network

[0202] PPD Paging Strategy Differentiation

[0203] PPI Paging Strategy Instruction

[0204] PSA PDU Session Anchor

[0205] QFI QoS Flow Identifier

[0206] QoE (Quality of Experience)

[0207] (R)AN (Radio) Access Network

[0208] RLC Wireless Link Control

[0209] RM Registration Management

[0210] RQA Reflection QoS Attributes

[0211] RQI Reflection QoS Indicator

[0212] RRC Radio Resource Control

[0213] SA NR Standalone New Radio Interface

[0214] SBA Service-Based Architecture

[0215] SBI Service-Based Interface

[0216] SD slice differential

[0217] SDAP Service Data Adaptive Protocol

[0218] SEAF Safety Anchor Function

[0219] SEPP Secure Edge Protection Agent

[0220] SMF Session Management Function

[0221] S-NSSAI Single Network Slice Selection Auxiliary Information

[0222] SSC Session and Service Continuity

[0223] SST slices / service types

[0224] SUCI subscription hidden identifier

[0225] SUPI subscription permanent identifier

[0226] UDSF Unstructured Data Storage Function

[0227] UL uplink

[0228] UL CL Uplink Classifier

[0229] UPF User Face Functions

[0230] UDR Unified Data Repository

[0231] URSP UE routing policy

[0232] This application is based on and claims the benefit of priority to Indian Patent Application 201811018792, filed on May 18, 2018, the disclosure of which is incorporated herein by reference in its entirety.

[0233] List of reference numerals

[0234] 101 Controller

[0235] 102 User Interface

[0236] 103 Transceiver Circuit

[0237] 104 antennas

[0238] 105 Memory

[0239] 106 Communication Control Module

[0240] 107 Transceiver Control Module

[0241] 201 Controller

[0242] 202 Network Interface

[0243] 203 Transceiver Circuit

[0244] 204 antennas

[0245] 205 Memory

[0246] 206 Communication Control Module

[0247] 207 Transceiver Control Module

[0248] 301 Controller

[0249] 302 Network Interface

[0250] 303 Transceiver Circuit

[0251] 304 Memory

[0252] 305 Communication Control Module

[0253] 306 Transceiver Control Module

Claims

1. A method used by a user equipment (UE), the method comprising: During the first configuration update process, a first configuration update command message including the first temporary mobile identity of the UE is received from the Access and Mobility Management Function (AMF) on the 3GPP access. During the first configuration update process, a configuration update completion message is sent to the AMF; During the second configuration update process, a second configuration update command message including the second temporary mobility identity of the UE is received from the AMF on a non-3GPP access. as well as Use a third temporary mobile identity to paging. The third temporary mobile identity is transmitted from the AMF to the next-generation radio access network (NG-RAN) in 3GPP access. The third temporary mobile identity is derived from the second temporary mobile identity.

2. The method according to claim 1, further comprising: The connection management state transitions from the Radio Resource Control (RRC) connected state (i.e., the RRC connected state) to the CM connected state with an RRC inactive state.

3. A method used by an Access and Mobility Management Function (AMF), the method comprising: During the first configuration update process, a first configuration update command message including the first temporary mobility identity of the UE is sent to the user equipment (UE) on the 3GPP access; During the first configuration update process, a configuration update completion message is received from the UE; During the second configuration update process, a second configuration update command message including the second temporary mobility identity of the UE is sent to the UE on a non-3GPP access; as well as In the 3GPP access, the third temporary mobility identity of the UE is sent to the next-generation radio access network, i.e., NG-RAN, wherein the third temporary mobility identity is derived from the second temporary mobility identity of the UE.

4. The method according to claim 3, wherein, The third temporary mobile identity of the UE is used for paging.

5. A user equipment, or UE, comprising: A component for receiving a first configuration update command message including the first temporary mobile identity of the UE from the Access and Mobility Management Function (AMF) on a 3GPP access during a first configuration update process; A component for sending a configuration update complete message to the AMF during the first configuration update process; A component for receiving a second configuration update command message, including the second temporary mobility identity of the UE, from the AMF on a non-3GPP access during a second configuration update process; as well as Components used for paging using a third temporary mobile identity. The third temporary mobile identity is transmitted from the AMF to the next-generation radio access network (NG-RAN) in 3GPP access. The third temporary mobile identity is derived from the second temporary mobile identity.

6. The UE according to claim 5, further comprising: A component used to transition from a Radio Resource Control (RRC) connected state (i.e., a Connection Management (CM) connected state) to a CM connected state with an RRC inactive state.

7. An Access and Mobility Management Function (AMF), comprising: Components for sending a first configuration update command message, including the first temporary mobility identity of the UE, to a user equipment (UE) on a 3GPP access during a first configuration update process; A component for receiving a configuration update completion message from the UE during the first configuration update process; A component for sending a second configuration update command message, including the second temporary mobility identity of the UE, to the UE on a non-3GPP access during a second configuration update process; as well as A component for transmitting the third temporary mobility identity of the UE to the next-generation radio access network (NG-RAN) in the 3GPP access, wherein the third temporary mobility identity of the UE is derived from the second temporary mobility identity of the UE.

8. The AMF according to claim 7, wherein, The third temporary mobile identity of the UE is used for paging.

Images