Initiating the network-requested registration procedure

Abstract

Disclosed herein is a method performed by a wireless communication device (112), the method including receiving (400) a configuration update command from a network node (200) that includes an indication as to whether the wireless communication device (112) should maintain an existing non-access stratum (NAS) connection, and performing (402) one or more actions in accordance with the configuration update command.

Description

[Technical field]

[0001] [Background technology]

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is clearly given and / or is implied from the context in which they are used. References to elements, devices, components, means, steps, etc. are to be interpreted openly as referring to at least one of the elements, devices, components, means, steps, etc., unless expressly stated otherwise. The steps of the methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is clearly described as following or preceding another step, and / or unless it is implicitly indicated that a step must precede or follow another step. Any feature of the embodiments disclosed herein may be applied to other embodiments, as appropriate. Similarly, any advantage of an embodiment may be applied to other embodiments, and vice versa. Other objects, features, and advantages of the present embodiments will become apparent from the following description.

[0003] The current 3rd Generation Partnership Project (3GPP®) 5th Generation System (5GS) Non-Access Stratum (NAS) specifications support network-to-UE indication of network supported capabilities to inform the user equipment (UE) of the capabilities it can perform and the capabilities it is authorized to use. This indication of network supported capabilities is signaled in a registration procedure, which is a UE initiated procedure. If the network needs to change the capability support for a particular UE, the Access and Mobility Management Function (AMF) can initiate a UE configuration update procedure to indicate a request for the UE to perform a registration procedure. Depending on the configuration update command message parameter and indication settings, the registration request may result in the current N1 NAS signaling connection being released in case of AMF relocation, or may result in the N1 NAS signaling connection not being released. Summary of the Invention [Problem to be solved by the invention]

[0004] Currently, certain challenges exist. When registration is requested via the UE configuration update procedure, a flag indicating requested registration will cause the N1 NAS signaling connection to be released unless an additional Information Element (IE) for the specific reason of the requested registration is included. The only such additional indication currently specified is the Mobile Initiated Connection Only (MICO) indication. To support additional reasons for the network to request registration from the UE, a new IE indicating the specific reason would need to be introduced, as the use of a MICO specific indication does not apply. The more such reasons are likely to be introduced in the future, the more IEs would be required, leading to inefficiencies in the protocol design and large message sizes if no additional action is required by the UE beyond initiating the registration procedure. [Means for solving the problem]

[0005] Certain aspects of the present disclosure and embodiments thereof may provide solutions to the above-mentioned or other problems. Disclosed herein are systems and methods that provide a generic indication to request registration from a UE in a UE configuration update procedure while maintaining a current N1 NAS signaling connection. In one embodiment, the indication is added to an existing IE with the requested registration. When the UE receives a configuration update command message with a registration indication and a new indication to maintain the N1 NAS signaling connection, the UE initiates a registration procedure without releasing the current N1 NAS signaling connection and does not need to evaluate a specific network reason for requesting registration.

[0006] Various embodiments exist and are proposed herein that solve one or more of the disclosed problems.

[0007] Certain embodiments may provide one or more of the following technical advantages: Since there is a generic indication to maintain the N1 NAS signaling connection when registration is requested, no further new IEs are required. In future new cases of maintaining the N1 NAS signaling connection when registration is requested, no new case specific IEs are required. The new flag can be used in all cases where the network needs to request registration without any other specific action in the UE. Thus, there is no need to define and include reason specific IEs in the configuration update command message, reducing the message size and specification complexity. In case of multiple reasons for requesting registration, the advantage of the generic indication is even greater. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of a cellular communication system 100 in which embodiments of the present disclosure may be implemented. [Diagram 2] 1 illustrates a wireless communication system represented as a 5G network architecture, which may be considered as one particular implementation of the system 100 of FIG. 1. [Diagram 3] Diagram showing 5G network architecture with service-based interfaces between NFs in the control plane. [Figure 4] FIG. 2 illustrates a UE configuration update procedure according to one embodiment of the present disclosure. [Diagram 5] 5 is a block diagram of a network node 500 in accordance with some embodiments of the present disclosure. [Figure 6] 5 is a block diagram illustrating a virtualization embodiment of a network node 500 in accordance with some embodiments of the present disclosure. [Figure 7] 5 is a block diagram of a network node 500 in accordance with some other embodiments of the present disclosure. [Figure 8] 8 is a block diagram of a wireless communication device 800 according to some embodiments of the present disclosure. [Figure 9] 8 is a block diagram of a wireless communication device 800 in accordance with some other embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Some of the embodiments contemplated herein are more fully described with reference to the accompanying drawings. However, other embodiments are within the scope of the subject matter disclosed herein, and the subject matter disclosed should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art. Additional information is also provided in the appendix documents.

[0010] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0011] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Some examples of a radio access node are, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP®) fifth generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP® Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a Home eNB, etc.), a relay node, a network node implementing some of the functionality of a base station (e.g., a network node implementing a gNB central unit (gNB-CU) or a network node implementing a gNB distributed unit (gNB-DU)) or a network node implementing some of the functionality of another type of radio access node.

[0012] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Publication Function (SCEF), a Home Subscriber Server (HSS), etc. Some other examples of core network nodes include nodes that implement an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Publication Function (NEF), a Network Function (NF), a Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc.

[0013] Communications Device: As used herein, a "communications device" is any type of device that has access to an access network. Some examples of communications devices include, but are not limited to, mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical equipment, media players, cameras, or any type of consumer electronics such as televisions, radios, lighting fixtures, tablet computers, laptops, or personal computers (PCs). A communications device can be a portable, handheld, computer-based, or vehicle-mounted mobile device that can communicate voice and / or data over a wireless or wired connection.

[0014] Wireless Communication Device: One type of communication device is a wireless communication device, which can be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to, user equipment (UE) in a 3GPP network, machine-type communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices can be or be implemented in mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablet computers, laptops, personal computers (PCs), etc. A wireless communication device can be a portable, handheld, computer-contained, or vehicle-mounted mobile device that can communicate voice and / or data over a wireless connection.

[0015] Network Node: As used herein, a "network node" is any node that is part of the RAN or core network of a cellular communications network / system.

[0016] It should be noted that the description herein focuses on 3GPP® cellular communication systems, and as such, 3GPP® terminology or terminology similar to 3GPP® terminology is often used, however, the concepts disclosed herein are not limited to 3GPP® systems.

[0017] In the description herein, reference may be made to the term "cell", however, it is important to note that, particularly with regard to 5G NR concepts, a beam may be used instead of a cell, and therefore the concepts described herein are equally applicable to both cells and beams.

[0018] Figure 1 FIG. 1 illustrates an example of a cellular communication system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 100 is a 5G system (5GS). The 5GS includes a 5G Core (5GC) and a Next Generation RAN (NG-RAN), which includes NR base stations (gNBs) and optionally Next Generation eNBs (ng-eNBs) (i.e., LTE RAN nodes connected to 5GC). In this example, the RAN includes base stations 102-1 and 102-2, which in the NG-RAN are referred to as gNBs (i.e., NR RAN nodes) or optionally ng-eNBs (i.e., LTE RAN nodes connected to 5GC), and which control corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are referred to herein collectively as base stations 102 and individually as base stations 102. Similarly, the (macro) cells 104-1 and 104-2 are referred to herein collectively as the (macro) cell 104 and individually as a (macro) cell. The RAN may also include several low power nodes 106-1 to 106-4 that control corresponding small cells 108-1 to 108-4. The low power nodes 106-1 to 106-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), etc. Notably, although not shown, one or more of the small cells 108-1 to 108-4 may instead be provided by the base station 102. The low power nodes 106-1 to 106-4 are referred to herein collectively as the low power nodes 106 and individually as the low power nodes 106. Similarly, small cells 108-1 through 108-4 are referred to herein collectively as small cells 108 and individually as small cells 108. The cellular communication system 100 also includes a core network 110, referred to in 5GS as 5G Core (5GC). The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.

[0019] The base station 102 and low power node 106 serve wireless communication devices 112-1 through 112-5 in corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are referred to herein collectively as wireless communication devices 112 and individually as wireless communication devices 112. In the following description, the wireless communication devices 112 are often UEs, although the disclosure is not limited in this respect.

[0020] Figure 2 2 illustrates a wireless communication system represented as a 5G network architecture composed of core network functions (NFs), where the interaction between any two NFs is represented by a point-to-point reference point / interface. FIG 2 may be considered as one particular implementation of the system 100 of FIG 1.

[0021] From the access side, the 5G network architecture shown in FIG. 2 includes multiple UEs 112 connected to either a RAN 102 or an access network (AN), and an access and mobility management function (AMF) 200. Typically, the RAN (AN) 102 includes a base station, such as an eNB or a gNB. From the core network side, the 5G core NF shown in FIG. 2 includes a network slice selection function (NSSF) 202, an authentication server function (AUSF) 204, a unified data management (UDM) 206, an AMF 200, a session management function (SMF) 208, a policy control function (PCF) 210, and an application function (AF) 212.

[0022] Reference point representation of 5G network architecture is used to develop detailed call flows in normative standardization. N1 reference point is defined to carry signaling between UE 112 and AMF 200. Reference points for connection between AN 102 and AMF 200 and between AN 102 and UPF 214 are defined as N2 and N3, respectively. There is reference point N11 between AMF 200 and SMF 208, which means that SMF 208 is at least partially controlled by AMF 200. N4 is used by SMF 208 and UPF 214 so that UPF 214 is configured using control signals generated by SMF 208 and UPF 214 can report its status to SMF 208. N9 is the reference point for connection between different UPF 214 and N14 is the reference point for connection between different AM 200F. N15 and N7 are defined because the PCF 210 applies policies to the AMF 200 and the SMF 208, respectively. N12 is required for the AMF 200 to perform authentication of the UE 112. N8 and N10 are defined because the subscriber data of the UE 112 is required for the AMF 200 and the SMF 208.

[0023] The 5GC network intends to separate the user plane and the control plane. The user plane carries the user traffic while the control plane carries the signaling in the network. In Figure 2, the UPF 214 is in the user plane and all other NFs, i.e., AMF 200, SMF 208, PCF 210, AF 212, AUSF 204 and UDM 206, are in the control plane. Separating the user plane and the control plane ensures that the resources of each plane are scaled independently. It is also possible to deploy the UPF separately and distributed from the control plane functions. In this architecture, for some applications that require low latency, the UPF can be deployed very close to the UE to reduce the round trip time (RTT) between the UE and the data network.

[0024] The core 5G network architecture consists of modularized functions. For example, AMF200 and SMF208 are independent functions in the control plane. Separated AMF200 and SMF208 allow independent evolution and scaling. Other control plane functions such as PCF210 and AUSF204 can be separated as shown in Figure 2. The modularized function design allows the 5GC network to flexibly support various services.

[0025] Each NF interacts directly with another NF. Intermediate functions can be used to route messages from one NF to another. In the control plane, a set of interactions between two NFs is defined as a service, so that they can be reused. The services allow for the support of modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0026] Figure 3 FIG. 3 illustrates a 5G network architecture using service-based interfaces between NFs in the control plane instead of the point-to-point reference points / interfaces used in the 5G network architecture of FIG. 2. However, the NFs described above with reference to FIG. 2 correspond to the NFs shown in FIG. 3. The services etc. that an NF provides to other authenticated NFs may be exposed to the authenticated NFs via the service-based interfaces. In FIG. 3, the service-based interfaces are indicated by the letter "N" followed by the name of the NF. For example, Namf for the service-based interface of the AMF 200 and Nsmf for the service-based interface of the SMF 208. The Network Publication Function (NEF) 300 and the Network Repository Function (NRF) 302 of FIG. 3 are not shown in FIG. 2 above. However, it should be clarified that all NFs shown in FIG. 2 can interact with the NEF 300 and NRF 302 of FIG. 3 as needed, even if not explicitly shown in FIG. 2.

[0027] Some characteristics of the NFs shown in Figures 2 and 3 can be explained as follows: The AMF 200 provides UE-based authentication, authorization, mobility management, etc. The AMF 200 is independent of the access technology, so even a UE 112 using multiple access technologies is essentially connected to a single AMF 200. The SMF 208 is responsible for session management and assigns an Internet Protocol (IP) address to the UE. The SMF 208 also selects and controls the UPF 214 for data forwarding. If the UE 112 has multiple sessions, a different SMF 208 can be assigned to each session to manage them separately and provide different features for each session. The AF 212 provides information about the packet flow to the PCF 210, which is responsible for policy control, to support Quality of Service (QoS). Based on this information, the PCF 210 determines the policies regarding mobility and session management to make the AMF 200 and SMF 208 work properly. The AUSF 204 supports an authentication function for UEs, etc., and stores data for authenticating UEs, etc., and the UDM 206 stores subscription data for the UE 112. A data network (DN) that is not part of the 5GC network provides Internet access, operator services, etc.

[0028] An NF may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, e.g., a cloud infrastructure, etc.

[0029] Figure 4 The details of the embodiment of the present disclosure will be described below. In this regard, FIG. 4 illustrates a UE configuration update procedure according to one embodiment of the present disclosure. As illustrated, the AMF 200 sends a configuration update command to the UE 112 (step 400). In one embodiment, the AMF 200 starts a timer (T3555) when sending the configuration update command. The UE 112 performs one or more actions according to the configuration update command (step 402). In one embodiment, the UE 112 sends a configuration update complete message to the AMF 200 (step 404). In one embodiment, the AMF 200 stops the timer (T3555) when receiving the configuration update complete message. However, as illustrated, in another embodiment, the AMF 200 sends a configuration update command to the UE 112 in step 400, but the UE 112 does not send a configuration update complete message to the AMF 200, and the AMF 200 does not start or stop the timer.

[0030] According to one embodiment of the present disclosure, the configuration update command of step 400 includes an indication to the UE 112 whether the UE 112 should maintain the existing N1 NAS signaling connection. For example, the indication may be a single bit, where the single bit indication is set to one binary value (e.g., "0") to indicate that the existing N1 NAS signaling connection should be released, and the single bit indication is set to another binary value (e.g., "1") to indicate that it should not be released. In one embodiment, the indication is a generic indication in that it is applicable regardless of the reason for the configuration update command. In one embodiment, the indication indicating whether the UE 112 should maintain the existing N1 NAS signaling connection is included in a configuration update indication IE included in the configuration update command.

[0031] In one embodiment, the configuration update command of step 400 includes both a registration request and an indication to UE 112 whether UE 112 should maintain the existing N1 NAS signaling connection. The registration request and indication together indicate to UE 112 that UE 112 should perform a registration procedure and that UE 112 should or should not maintain the existing N1 NAS signaling connection with the requested registration. In one embodiment, both the registration request and the indication to UE 112 should maintain the existing N1 NAS signaling connection are included in a configuration update indication IE included in the configuration update command.

[0032] The one or more actions performed by UE 112 in step 402 include releasing or refraining from releasing an existing N1 NAS signaling connection according to an indication included in the configuration update command, and if the configuration update command includes a request for UE 112 to perform a registration procedure, UE 112 performs the registration procedure according to the request (with or without releasing the existing N1 NAS signaling connection according to the indication).

[0033] The currently specified method for requesting registration using the UE configuration update procedure for a MICO mode change is achieved by a combination of the registration requested flag (RED) in the configuration update indication IE included in the configuration update command and the inclusion of the MICO indication IE in the configuration update command, as follows:

[0034] [Table 1] It should be noted that the content of the MICO Indication IE is not significant for its use in the UE Configuration Update procedure, as only its presence is evaluated.

[0035] To support other cases of requested registration via UE Configuration Update procedure where release of N1 NAS signaling connection is not desired or required at UE 112 and no other case specific action is required, in one embodiment of the present disclosure, a new flag is defined using one of the reserved bits of the Configuration Update Indication IE. For example, a new flag referred to as Signaling Connection Solution Request (SCRR) may be provided as follows:

[0036] [Table 2]

[0037] In one example alternative embodiment, a new optional IE may be defined. For example, in this example alternative embodiment, the new optional IE, referred to herein as the Configuration Update Parameters IE, may be defined as follows:

[0038] [Table 3]

[0039] What both of the above protocol implementation alternatives have in common is that the flag (SCRR) is not tied to a specific case and may be used in networks when a subsequent execution of the registration procedure is sufficient for the particular use case at hand.

[0040] Details of one exemplary embodiment of the proposed protocol solution are provided in the attached Draft Request for Change (CR) to 3GPP TS® 24.501.

[0041] Figure 5 FIG. 5 is a block diagram of a network node 500 according to some embodiments of the disclosure. Optional features are indicated with dashed lines. The network node 500 may be, for example, a network node that implements the AMF 200 or at least some of the functionality of the AMF 200 described herein. As shown, the network node 500 includes one or more processors 504 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), a memory 506, and a network interface 508. The one or more processors 504 are also referred to herein as processing circuits. The one or more processors 504 operate to provide one or more functions of the network node 500 described herein (e.g., one or more functions of the AMF 200 described herein with respect to FIG. 4). In some embodiments, the functionality is implemented by software, for example, stored in the memory 506 and executed by the one or more processors 504.

[0042] Figure 6 FIG. 6 is a block diagram illustrating a virtualized embodiment of a network node 500, according to some embodiments of the disclosure. As used herein, a "virtualized" network node is an implementation of a network node 500 in which at least some of the functionality of the network node 500 is realized as virtual components (e.g., via virtual machines running on physical processing nodes in the network). As shown, in this example, the network node 500 includes one or more processing nodes 600 coupled to or included as part of a network 602. Each processing node 600 includes one or more processors 604 (e.g., CPU, ASIC, FPGA, etc.), memory 606, and a network interface 608. In this example, the functionality 610 of the network node 500 described herein (e.g., one or more functionality of the AMF 200 described with respect to FIG. 4) is implemented in one or more processing nodes 600, or distributed across two or more processing nodes 600 in any desired manner. In some particular embodiments, some or all of the functions 610 of the network node 500 described herein (e.g., one or more functions of the AMF 200 described herein with respect to FIG. 4 ) are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 600.

[0043] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of a network node 500 according to any of the embodiments described herein, or a node (e.g., processing node 600) that performs one or more functions 610 of the network node 500 in a virtual environment (e.g., one or more functions of the AMF 200 described herein with respect to FIG. 4). In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0044] Figure 7 7 is a block diagram of a network node 500 in accordance with some other embodiments of the present disclosure. The network node 500 includes one or more modules 700, each of which is implemented in software. The modules 700 operate to provide the functionality of the network node 500 described herein (e.g., one or more functions of the AMF 200 described herein with respect to FIG. 4). This discussion is equally applicable to the processing nodes 600 of FIG. 6, where the modules 700 may be implemented in one of the processing nodes 600 or distributed across two or more processing nodes 600.

[0045] Figure 8 8 is a block diagram of a wireless communication device 800 according to some embodiments of the present disclosure. The wireless communication device 800 may be the UE 112 described above. As shown, the wireless communication device 800 includes one or more processors 802 (e.g., CPU, ASIC, FPGA, etc.), memory 804, and one or more transceivers 806, each including one or more transmitters 808 and one or more receivers 810, coupled to one or more antennas 812. The transceiver 806 includes radio front-end circuitry connected to the antenna 812 configured to condition signals communicated between the antenna 812 and the processor 802, as will be understood by those skilled in the art. The processor 802 is also referred to herein as a processing circuit. The transceiver 806 is also referred to herein as a radio circuit. In some embodiments, the functionality of the wireless communication device 800 described above (e.g., one or more functions of the UE 112 described herein, e.g., with respect to FIG. 4) may be implemented, fully or partially, in software stored in the memory 804 and executed by the processor 802. It should be noted that the wireless communication device 800 may include additional components not shown in FIG. 8, such as, for example, one or more user interface components (e.g., input / output interfaces including a display, buttons, touch screen, microphone, speaker, and / or any other components that allow for input of information into and / or output of information from the wireless communication device 800) and a power source (e.g., a battery and associated power circuitry).

[0046] In some embodiments, a computer program product is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of the wireless communication device 800 according to any of the embodiments described herein (e.g., one or more functions of the AMF 200 described herein with respect to FIG. 4). In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0047] Figure 9 9 is a block diagram of a wireless communication device 800 according to some other embodiments of the present disclosure. The wireless communication device 800 includes one or more modules 900, each of which is implemented in software. The modules 900 provide the functionality of the wireless communication device 800 described herein (e.g., one or more functions of the AMF 200 described herein with respect to FIG. 4).

[0048] Any suitable steps, methods, features, functions, or advantages disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may include several of these functional units. These functional units may include processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry is configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols and, in some embodiments, program instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0049] Although the processes in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such orders are exemplary (e.g., alternative embodiments may perform operations in different orders, combine certain operations, and overlap certain operations).

[0050] Some embodiments Some of the embodiments disclosed above can be summarized as follows.

[0051] 1. A method implemented in a wireless communication device (112), comprising: receiving (400) a configuration update command from a network node (200) that includes an indication as to whether the wireless communication device (112) should maintain an existing non-access stratum (NAS) connection; performing (402) one or more actions in accordance with the configuration update command; The method includes:

[0052] 2. The method of embodiment 1, comprising: The method, wherein the existing NAS connection is an existing N1 NAS connection of the wireless communication device (112).

[0053] 3. The method according to embodiment 1 or 2, The method, wherein performing 402 one or more actions includes releasing or refraining from releasing the existing NAS connection depending on the indication.

[0054] 4. The method according to any one of embodiments 1 to 3, comprising: The method, wherein the indication is a one-bit indication that, when set to a first binary value, indicates that the wireless communication device (112) needs to release the existing NAS connection and, when set to a second binary value, indicates that the wireless communication device (112) does not need to release the existing NAS connection.

[0055] 5. The method according to any one of embodiments 1 to 4, comprising: The method, wherein the configuration update command further includes information indicating to the wireless communication device (112) that the wireless communication device (112) is to perform a registration procedure.

[0056] 6. The method of embodiment 5, comprising: The method in which performing (402) one or more actions includes, if performing a registration procedure, performing a registration procedure and, depending on the indication, releasing or refraining from releasing the existing NAS connection.

[0057] 7. The method according to any one of the preceding claims, comprising: The method, wherein the indication is a generic indication that may apply to more than one reason for the configuration update command.

[0058] 8. The method according to any one of the preceding claims, comprising: The method, wherein the indication is included in a configuration update indication information element that is included in a configuration update command.

[0059] 9. The method of embodiment 8, comprising: The method, wherein the indication is a one-bit indication contained in bit 3 or bit 4 of octet 1 of a configuration update indication information element.

[0060] 10. The method according to any one of the preceding claims, comprising: The indication is included in an information element that is different from a configuration update indication information element that is included in the configuration update command.

[0061] 11. The method according to any one of the preceding claims, comprising: The method, wherein the network node (200) is an Access and Mobility Management Function (AMF) (200).

[0062] 12. A wireless communication device (112), comprising: receiving (400) a configuration update command from a network node (200) that includes an indication as to whether the wireless communication device (112) should maintain an existing non-access stratum (NAS) connection; performing (402) one or more actions in accordance with the configuration update command; 23. A wireless communication device configured to:

[0063] 13. A wireless communication device (112) according to embodiment 12, comprising: The wireless communication device (112) is further configured to perform the method according to any one of embodiments 2 to 11.

[0064] 14. A wireless communication device (112) according to any one of the preceding claims 12 to 13, one or more transmitters (808); One or more receivers (810); a processing circuit (802) associated with one or more transmitters (808) and one or more receivers (810); Equipped with The processing circuit (802) is configured to: receiving (400) a configuration update command from a network node (200); performing (402) one or more actions in accordance with the configuration update command; 23. A wireless communication device configured to:

[0065] 15. A method performed by a network node (200) of a wireless communication system (100), comprising: A method comprising: sending (400) a configuration update command to a wireless communication device (112) that includes an indication as to whether the wireless communication device (112) should maintain an existing non-access stratum (NAS) connection.

[0066] 16. The method of embodiment 15, comprising: The method, wherein the existing NAS connection is an existing N1 NAS connection of the wireless communication device (112).

[0067] 17. The method according to embodiment 15 or 16, The method, wherein the indication is a one-bit indication that, when set to a first binary value, indicates that the wireless communication device (112) needs to release the existing NAS connection and, when set to a second binary value, indicates that the wireless communication device (112) does not need to release the existing NAS connection.

[0068] 18. The method according to any one of embodiments 15 to 17, The method, wherein the configuration update command further includes information indicating to the wireless communication device (112) that the wireless communication device (112) is to perform a registration procedure.

[0069] 19. The method according to any one of embodiments 15 to 18, The method, wherein the indication is a generic indication that may apply to more than one reason for the configuration update command.

[0070] 20. The method according to any one of embodiments 15 to 18, The method, wherein the indication is included in a configuration update indication information element that is included in a configuration update command.

[0071] 21. The method of embodiment 20, comprising: The method, wherein the indication is a one-bit indication contained in bit 3 or bit 4 of octet 1 of a configuration update indication information element.

[0072] 22. The method according to any one of embodiments 15 to 18, comprising: The indication is included in an information element that is different from a configuration update indication information element that is included in the configuration update command.

[0073] 23. The method according to any one of embodiments 15 to 22, comprising: The method, wherein the network node (200) is an Access and Mobility Management Function (AMF) (200).

[0074] 24. A network node (200) of a wireless communication system (100), comprising: A network node configured to send (400) a configuration update command to a wireless communication device (112) that includes an indication as to whether the wireless communication device (112) should maintain an existing non-access stratum (NAS) connection.

[0075] 25. A network node (200) according to embodiment 24, The network node (200), further configured to execute a method according to any one of embodiments 16 to 23.

[0076] 26. The network node (200) according to embodiment 24 or 25, A network node comprising: a processing circuit (504, 604) configured to cause a network node (200) to send (400) a configuration update command to a wireless communication device (112).

[0077] Abbreviation At least some of the following abbreviations may be used in this disclosure. In case of discrepancies between abbreviations, the above usage should prevail. If listed multiple times below, the first listing takes precedence over subsequent listings. ·3GPP: 3rd Generation Partnership Project 5G: 5th generation 5GC: 5th generation core 5GS: 5th generation system ·AF: Application Function AMF: Access and Mobility Management Function ·AN: Access Network -AUSF: Authentication server function ·DN: Data Network eNB: Enhanced or evolved Node B EPC: Evolved Packet Core E-UTRA: Evolved Universal Terrestrial Radio Access ·gNB: New Radio Base Station ·HSS: Home Subscriber Server IoT: Internet of Things IP: Internet Protocol ·LTE: Long Term Evolution MME: Mobility Management Entity ·MTC: Machine Type Communication NEF: Network Publishing Function ·NF: Network function NR: New Radio · NRF: Network Function Repository Function ·NSSF: Network Slice Selection Function ·PCF: Policy Control Function P-GW: Packet Data Network Gateway ·QoS: Quality of Service RAN: Radio Access Network · SCEF: Service Capability Exposure Function ·SMF: Session Management Function · UDM: Unified Data Management UE: User Equipment UPF: User Plane Function

[0078] [Table 4]

[0079] [Table 5]

[0080] ***First Change*** 5.3.18 Extended Coverage Usage Restrictions To address the extensive resource usage from the network, operators may prevent certain subscribers from using extended coverage (see 3GPP TS 23.501 [8]). In NB-N1 mode, the UE must indicate support for extended coverage usage restriction. In WB-N1 mode, a UE supporting either CE mode A or CE mode B must indicate support for extended coverage usage restriction. A UE supporting extended coverage usage restriction indicates support for extended coverage usage restriction in the registration request message. If the UE supports extended coverage usage restriction, the AMF indicates whether the extended coverage usage is restricted in the registration accept message (see subsections 5.5.1.2 and 5.5.1.3). If the extended coverage usage is restricted, the UE shall not use extended coverage in the registered PLMN and all PLMNs in the equivalent PLMN list. If the UE supports CE mode B and the network: -The UE is not restricted from using extended coverage, or - if it is determined that CE mode B is not restricted for the UE, The applicable NAS timer values ​​are calculated by the network as described in clauses 4.19 and 4.20. For UEs that support extended coverage or CE Mode B usage restrictions: a) the AMF decides to impose changes to the restrictions on the use of extended coverage or changes to the restrictions on the use of CE Mode B as described in 3GPP TS 23.501[8]; and b) If the UE is in 5GMM-CONNECTED mode and there is no ongoing registration procedure, The AMF should initiate a Generic UE Configuration Update procedure, as described in section 5.4.4, to indicate the requested registration and to maintain the existing N1 NAS signaling connection. NOTE: After successful completion of the registration procedure for mobility and registration update including modification of restrictions on the use of extended coverage, for any SMF for which the UE has established PDU sessions, the AMF updates the SMR with an indication on the use of the extended NAS timer configuration as described in 3GPP TS 23.501 [8] and 3GPP TS 23.502 [9]. ***Next Change*** 5.4.4 Generic UE configuration update procedure 5.4.4.1 Overview The purpose of this procedure is to a) enabling the AMF to update the UE configuration for access and mobility management related parameters determined and provided by the AMF by providing new parameter information in the command; or b) requesting the UE to perform a registration procedure for mobility and periodic registration update towards the network in order to update the access and mobility management related parameters determined and provided by the AMF (see subclause 5.5.1.3); It is. Note: When requesting the execution of registration procedures for mobility and periodic registration updates, the AMF may also request the UE to release or maintain an existing N1 NAS signaling connection. This procedure is initiated by the network and can only be used when the UE has an established 5GMM context and is in 5GMM-CONNECTED mode. If the UE is in 5GMM-IDLE mode, the AMF can initiate a generic UE configuration update procedure using a paging or notification procedure. The AMF can request an acknowledgement to ensure that the parameters have been updated by the UE. This procedure is initiated by the network to assign a new 5G-GUTI to the UE after a successful service request procedure initiated in response to a paging request from the network and before the N1 NAS signaling connection is released. If the service request procedure was triggered due to pending 5GSM downlink signaling, the procedure to assign a new 5G-GUTI may be initiated by the network after the transfer of the 5GSM downlink signaling. The following parameters are supported by the Generic UE Configuration Update procedure without the need to require the UE to perform the registration procedure for mobility and periodic registration updates: a) 5G-GUTI; b) TAI list; c) Service area list; d) network identifier and time zone information (network full name, network abbreviation, local time zone, universal time and local time zone, network daylight saving time); e) LADN information; f) Rejected NSSAI; g) blank; h) operator defined access category definitions; i) SMS indication; j) Service gap time value; k) "CAG Information List"; l) UE Radio Capability ID; and m) 5GS registration results The following parameters may be sent to the UE with or without the requirement to perform registration procedures for mobility and periodic registration updates. a) Authorised NSSAI; b) A constituted NSSAI; or c) Network slice subscription change indication The following parameters are sent to the UE along with a request to perform the registration procedure for mobility and periodic registration updates: a) A MICO indication; or b) UE Radio Capability ID Deletion Indication The following parameters are only transmitted via 3GPP access: a) LADN information; b) MICO indication; c) TAI list; d) Service area list; e) Service gap time value; f) "CAG Information List"; and g) UE radio capability ID; The following parameters are managed and transmitted per access type, i.e. transmitted separately over 3GPP access or non-3GPP access. a) Authorised NSSAI; b) Rejected NSSAI (if the NSSAI is rejected in the current registration area) The following parameters are commonly managed and transmitted over 3GPP or non-3GPP access: a) 5G-GUTI; b) Network identifier and time zone information; c) Rejected NSSAI (if the NSSAI is rejected in the current PLMN). d) the constituted NSSAI; e) SMS indication; f) 5GS registration results [Table 6] ***Next Change*** 5.4.4.2 Network initiated general UE configuration update procedure The AMF should initiate the general UE configuration update procedure by sending a configuration update command message to the UE. AMF sends the following to the configuration update command message: a) including one or more of: 5G-GUTI, TAI list, allowed NSSAI which may include a mapped S-NSSAI, LADN information, service area list, MICO indication NITZ information, configured NSSAI which may include a mapped S-NSSAI, rejected NSSAI, network slice subscription change indication, operator defined access category definition, SMS indication, service gap time value, "CAG information list", UE radio capability ID, and 5GS registration result or UE radio capability ID deletion indication; b) Includes a Configuration Update Indication IE with the Registration Required bit set to "Registration Required", or c) Includes a combination of both a) and b). If an acknowledgement from the UE is required, the AMF shall indicate "acknowledgement required" in the Acknowledgement bit of the Configuration Update Indication IE in the Configuration Update Command message and start timer T3555. An acknowledgement is required for all parameters except if only NITZ is included. To initiate parameter renegotiation between the UE and the network, the AMF indicates "registration is requested" in the registration request bit of the configuration update indication IE in the configuration update command message. If newly allowed NSSAI information or AMF reconfiguration of a supported S-NSSAI requires AMF relocation, the AMF indicates "registration requested" in the registration requested bit of the configuration update indication IE and includes the allowed NSSAI IE in the configuration update command message. If the AMF includes a newly configured NSSAI in the configuration update command message and the newly configured NSSAI requires AMF relocation as specified in 3GPP TS 23.501 [8], the AMF indicates "registration is requested" in the Registration Required bit of the Configuration Update Indication IE in the message. If the AMF indicates "registration required" in the Registration Required bit of the Configuration Update Indication IE, an acknowledgement is required. If the Configuration Update Command message is initiated only due to changes in the allowed NSSAI and these changes require the UE to initiate a registration procedure but the AMF is unable to determine the allowed NSSAI for the UE as specified in 3GPP TS 23.501 [8], the Configuration Update Command message shall indicate "Registration requested" in the Registration Requested bit of the Configuration Update Indication IE and shall contain no other parameters. To request the UE to maintain the existing N1 NAS signaling connection upon registration request, the AMF indicates "release of N1 NAS signaling connection is not requested" in the signaling connection release request bit of the configuration update indication IE in the configuration update command message. S-NSSAI network slice-specific authentication and authorization procedures, If successful, the AMF shall include this S-NSSAI in the allowed NSSAIs. If it completes unsuccessfully, the AMF includes this S-NSSAI in the rejected NSSAI and gives the rejected NSSAI the rejection reason "S-NSSAI is not available because network slice specific authorization and authentication failed or was revoked." The allowed and rejected NSSAIs are included in the configuration update command message to reflect the results of the network slice-specific authentication and authorization procedures. Note: If multiple S-NSSAIs are subject to network slice-specific authentication and authorization, it is implementation specific whether the AMF informs the UE of the result of the procedure in one or more configuration update command messages. If the AMF includes the network slice indication IE in the configuration update command, the network slice subscription change indication is set to "network slice subscription has changed", and the change to the allowed NSSAI requires the UE to initiate a registration procedure, but the AMF cannot determine the allowed NSSAI for the UE as specified in 3GPP TS 23.501 [8], the configuration update command message shall additionally indicate "registration is requested" in the registration requested bit of the configuration update indication IE and shall not include the allowed NSSAI. If the AMF needs to update the LADN information, the AMF includes the LADN information in the LADN information IE of the configuration update command message. If the AMF needs to update the CAG information, the AMF includes the CAG Information List IE in the Configuration Update Command message. During the establishment of a 5GMM context, the network may send one or multiple configuration update command messages to the UE, or may not send any. If multiple configuration update command messages are sent, the content of the messages does not have to be the same. ***Next Change*** 5.4.4.3 General UE Configuration Updates Accepted by the UE Upon receiving the CONFIGURATION UPDATE COMMAND message, the UE shall stop timer T3346 if it is running and use its contents to update the appropriate information stored in the UE. If the Acknowledge bit in the Configuration Update Indication IE in the Configuration Update Command message indicates "acknowledge required", the UE shall send an Update Complete message. If the UE receives a new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new 5G-GUTI as valid and the old 5G-GUTI as invalid, stop timer T3519 if running, delete all stored SUCI, otherwise the UE shall consider the old 5G-GUTI as valid. If the CONFIGURATION UPDATE COMMAND message is sent via non-3GPP access and the UE is in 5GMM-REGISTERED in both 3GPP and non-3GPP accesses of the same PLMN, the UE shall provide the 5G-GUTI to the lower layers of the 3GPP access. If the UE receives a new TAI list in the configuration update command message, the UE considers the new TAI list as valid and the old TAI list as invalid; otherwise, the UE considers the old TAI list as valid. If the UE receives a new service area list in the configuration update command message, the UE shall consider the new service area list as valid and the old service area list as invalid, otherwise the UE shall consider the old service area list, if any, as valid. If the UE receives new NITZ information in the configuration update command message, the UE considers the new NITZ information as valid and the old NITZ information as invalid; otherwise, the UE considers the old NITZ information as valid. If the UE receives the LADN Information IE in the Configuration Update Command message, the UE shall consider the old LADN information as invalid and, if there is new LADN information, shall consider it as valid; otherwise, the UE shall consider the old LADN information as valid. If the UE receives a new authorized NSSAI for the associated access type in a CONFIGURATION UPDATE COMMAND message, the UE shall consider the new authorized NSSAI as valid for the associated access type and store the authorized NSSAI for the associated access type as specified in subclause 4.6.2.2 and shall consider the old authorized NSSAI for the associated access type as invalid; otherwise, the UE shall consider the old authorized NSSAI as valid for the associated access type. If the UE receives a newly configured NSSAI in the Configuration Update Command message, the UE shall consider the newly configured NSSAI for the registered PLMN as valid and the old NSSAI configured for the registered PLMN as invalid; otherwise, the UE shall consider the old NSSAI configured for the registered PLMN as valid. If the UE receives a network slice indication IE in a Configuration Update Command message with the network slice subscription change indication set to "network slice subscription has changed", the UE shall delete the network slice information of all PLMNs except the current PLMN, as specified in Subclause 4.6.2.2. If the UE receives an operator-defined access category definition IE in a configuration update command message and the operator-defined access category definition IE includes one or more operator-defined access category definitions, the UE shall delete all operator-defined access category definitions stored for the RPLMN and store the received operator-defined access category definitions for the RPLMN. If the UE receives an operator-defined access category definition IE in a configuration update command message and the operator-defined access category definition IE does not include an operator-defined access category definition, the UE shall delete all operator-defined access category definitions stored for the RPLMN. If the configuration update command message does not include an operator-defined access category definition IE, the UE shall not delete any operator-defined access category definitions stored for the RPLMN. The UE receives an SMS indication IE in a configuration update command message, and the SMS availability indication is a) if "SMS via NAS not available" is set, the UE shall assume that SMS transfer via NAS is not allowed by the network; b) If "SMS via NAS available" is configured, the UE may request the use of SMS transport via NAS after completion of the General UE Configuration Update procedure by performing the registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3. When the UE receives a CAG Information List IE in a Configuration Update Command message, the UE shall delete all stored "CAG Information Lists" and store the received "CAG Information List" via the CAG Information List IE as specified in Appendix C. If the received "CAG information list" contains an entry containing the identifier of the current PLMN, the UE shall act as follows: a) The UE receives a configuration update command message through a CAG cell, and the "Allowed CAG List" of the current PLMN in the received "CAG Information List" does not include the CAG-ID of the current CAG cell; i) if the entry for the current PLMN in the received "CAG Information List" does not contain an "indication that the UE can access 5GS only via a CAG cell", the UE shall transition to state 5GMM-REGISTERED.LIMITED-SERVICE and use the updated "CAG Information List" to search for a suitable cell according to 3GPP TS 38.304

[28] , or ii) The entry for the current PLMN in the received "CAG Information List" contains an "indication that the UE can access 5GS only via the CAG cell", and 1) If the "Allowed CAG List" of the current PLMN in the received "CAG Information List" contains one or more CAG-IDs, the UE transitions to state 5GMM-REGISTERED.LIMITED-SERVICE and searches for suitable cells according to 3GPP TS 38.304

[28] using the updated "CAG Information List", or 2) If the "Allowed CAG List" of the current PLMN in the received "CAG Information List" does not contain any CAG-ID, the UE shall enter the 5GMM-DEREGISTERED.PLMN-SEARCH state and apply the PLMN selection process defined in 3GPP TS 23.122 [6] using the updated "CAG Information List", or b) the UE receives a Configuration Update Command message via a non-CAG cell, and the entry for the current PLMN in the received "CAG Information List" contains an "indication that the UE can access 5GS only via a CAG cell", 1) If the "Allowed CAG List" of the current PLMN in the received "CAG Information List" contains one or more CAG-IDs, the UE shall enter the 5GMM-REGISTERED.LIMITED-SERVICE state and use the updated "CAG Information List" to search for suitable cells according to 3GPP TS 38.304

[28] , or 2) If the "Allowed CAG List" of the current PLMN in the received "CAG Information List" does not contain any CAG-ID, the UE transitions to 5GMM-DEREGISTERED.PLMN-SEARCH state and applies the PLMN selection process defined in 3GPP TS 23.122[6] using the updated "CAG Information List". The Configuration Update Command message indicates "Registration Requested" in the Registration Requested bit of the Configuration Update Indication IE, and a) does not include other parameters or includes at least one of a newly authorized NSSAI, a newly configured NSSAI, and a network slice subscription change indication; and 1) if an emergency PDU session exists, the UE shall, after completion of the General UE Configuration Update procedure and after release of the emergency PDU session, release the existing N1 NAS signalling connection and initiate registration procedures for mobility and periodic registration updates as specified in subclause 5.5.1.3, or 2) if no emergency PDU session exists, the UE shall, after completion of the General UE Configuration Update procedure and after release of the existing N1 NAS signalling connection, initiate the registration procedures for mobility and periodic registration updates as specified in subclause 5.5.1.3; b) if the MICO indication is included without a newly authorized NSSAI or a newly configured NSSAI, the UE shall, after completion of the General UE Configuration Update procedure, initiate the registration procedures for mobility and periodic registration update as specified in subclause 5.5.1.3 in order to renegotiate the MICO mode with the network, or c) If the signaling connection release requested bit in the Configuration Update Indication IE indicates "N1 NAS signaling connection release not required" without a newly authorized NSSAI or a newly configured NSSAI, the UE shall initiate the registration procedures for mobility and periodic registration updates as specified in subclause 5.5.1.3 after completion of the general UE configuration update procedure. A UE that receives a rejected NSSAI in a Configuration Update Command message shall take the following actions based on the rejection reason in the rejected NSSAI: "S-NSSAI is not available in the current PLMN or SNPN" The UE adds the rejected S-NSSAI to the rejected NSSAIs of the current PLMN as specified in subclause 4.6.2.2 and does not attempt to use this S-NSSAI in the current PLMN until the UE is turned off, the UICC containing the USIM is removed, or the entry in the "Subscriber Data List" with the SNPN identifier of the current SNPN is updated. "S-NSSAI is not available in the current registration area" The UE adds the rejected S-NSSAI to the rejected NSSAIs of the current registration area as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current registration area until the UE is turned off, until the UE moves out of the current registration area, until the UICC containing the USIM is removed, or until the entry in the "List of Subscriber Data" with the SNPN identifier of the current SNPN is updated. If the UE receives the T3447 Value IE in a Configuration Update Command message and the Registration Request indicates "Service Gap Control is supported", the UE shall replace its stored T3447 value with the value received in the T3447 Value IE and shall use the received T3447 value the next time timer T3447 is started if it is not zero or deactivated. If the received T3447 value is zero or deactivated, the UE shall stop timer T3447 if it is running. The UE is not in NB-N1 mode, the UE sets the RACS bit in the 5GMM Capability IE in the Registration Request message to "RACS supported", and the Configuration Update Command message is a) if the UE Radio Capability ID Deletion Indication IE is set to "Network assigned UE Radio Capability IDs required", the UE shall delete all network assigned UE radio capability IDs associated with the RPLMN or RSNPN stored in the UE and the UE shall initiate registration procedures for mobility and periodic registration update as specified in subclause 5.5.1.3.2. If the UE has manufacturer assigned UE radio capability IDs applicable to the current UE radio configuration, the UE shall include the manufacturer assigned UE radio capability IDs in the UE Radio Capability IDs IE in the Registration Request message; b) If the UE Radio Capability ID IE is included, the UE shall store the UE Radio Capability ID as specified in Annex C. If the UE is not currently registered for emergency services and the 5GS Registration Result IE in the Configuration Update Command message is set to "Registered for emergency services", the UE shall be considered to be registered for emergency services. ***Next Change*** 9.11.3.18 Configuration Updated Indication The purpose of the configuration update indication information element is to indicate additional information associated with the general UE configuration update procedure. The configuration update indication information element is coded as shown in Figure 9.11.3.18.1 and Table 9.11.3.18.1. The configuration update indication is a Type 1 information element. [Table 7] ***END OF CHANGE***

Claims

1. A method in a UE configuration update procedure performed by a user equipment (UE) (112), comprising: receiving (400) a configuration update command from a network node (200) including information indicating to the UE (112) that the UE will perform a registration procedure and an indication that the UE (112) will maintain the UE's existing N1 Non-Access Stratum (NAS) connection; performing (402) one or more actions in accordance with the configuration update command; Including, The method, wherein performing (402) the one or more actions includes, when performing the registration procedure, performing the registration procedure without releasing the existing N1 NAS connection in accordance with the indication.

2. 2. The method of claim 1 , The method, wherein the indication is a one-bit indication, which when set to a first binary value indicates that the UE (112) needs to release the existing N1 NAS connection, and when set to a second binary value indicates that the UE (112) does not need to release the existing N1 NAS connection.

3. 3. The method according to claim 1 or 2, A method, wherein the indication is a generic indication that may apply to more than one reason for the configuration update command.

4. 4. The method according to claim 1 , further comprising: The method, wherein the network node (200) is an Access and Mobility Management Function (AMF) (200).

5. A user equipment (UE) (112), receiving (400) a configuration update command from a network node (200) including information indicating to the UE (112) that the UE will perform a registration procedure and an indication that the UE (112) will maintain the UE's existing N1 Non-Access Stratum (NAS) connection; performing (402) one or more actions in accordance with the configuration update command; It is configured to perform the following: The UE, performing (402) one or more actions includes, when performing the registration procedure, performing the registration procedure without releasing the existing N1 NAS connection in accordance with the indication.

6. 6. The UE (112) of claim 5, The UE (112) is further configured to perform a method according to any one of claims 1 to 4.

7. 7. A UE (112) according to claim 5 or 6, One or more transmitters (808); One or more receivers (810); a processing circuit (802) associated with the one or more transmitters (808) and the one or more receivers (810); Equipped with The processing circuit (802) is configured to transmit to the UE (112): receiving (400) said configuration update command from said network node (200); and performing (402) the one or more actions in accordance with the configuration update command.

Images