The registration process for network requests is initiated

Abstract

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

Description

Background Art

[0001] Generally, unless clearly given and / or different meanings are implied from the context, all terms used in this article will be interpreted according to their common meaning in the relevant technical field. Unless otherwise clearly stated, all references to "one / an / element, equipment, assembly, device, step, etc." should be openly interpreted as referring to at least one example in an element, equipment, assembly, device, step, etc. Unless a step must be clearly described as after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0002] Current 3rd Generation Partnership Project (3GPP) 5th Generation System (5GS) Non-Access Stratum (NAS) specifications support indication of network supported features from the network to the User Equipment (UE) to inform the UE of the features that the UE can use and is allowed to use. This indication of network supported features is signaled during the registration procedure, which is a UE initiated procedure. When the network needs to change the support of a feature for a specific UE, the Access and Mobility Management Function (AMF) may initiate a UE Configuration Update procedure and instruct the UE to perform a request for a Registration procedure. In case of AMF relocation, the request for registration may result in the release of the current N1 NAS signaling connection, or without N1 NAS signaling connection release, depending on the parameter settings and indications in the Configuration Update Command message. Summary of the invention

[0003] There are currently some challenges. When registration is requested via the UE configuration update procedure, the flag indicating the requested registration will result in an N1 NAS signaling connection release unless an additional information element (IE) is included for the specific reason for the requested registration. The only such additional indication currently specified is the Mobile Initiated Connection Only (MICO) indication. In order to support additional reasons for the network to request registration from the UE, a new IE indicating the specific reason needs to be introduced, as the use of the MICO specific indication will not be applicable. If no additional actions are required in the UE other than the initiation of the registration procedure, the more such reasons that may be introduced in the future, the more IEs will be required, which will lead to inefficient protocol design and larger message sizes.

[0004] Certain aspects of the present disclosure and embodiments thereof may provide solutions to the above or other challenges. Disclosed herein are systems and methods for providing a general indication of requesting registration from a UE while maintaining a current N1 NAS signaling connection during a UE configuration update procedure. 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 an N1 NAS signaling connection, the UE initiates a registration procedure without releasing the current N1 NAS signaling connection and without evaluating a specific network reason for requesting the registration.

[0005] Various embodiments are presented herein that address one or more of the issues disclosed herein.

[0006] Certain embodiments may provide one or more of the following technical advantages. By maintaining a generic indication of an N1 NAS signaling connection when requesting a registration, no additional new IEs are required. For any future new cases where an N1 NAS signaling connection is maintained when requesting a registration, no new case specific IEs are required. The new flag may be used for all cases when the network needs to request a registration without other specific actions in the UE. Therefore, there is a need to define and include no cause specific IEs in the "Configuration Update Command" message, thereby reducing message size and specification complexity. In cases where there is more than one reason for requesting a registration, the benefit of the generic indication will be even greater. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 An example of a cellular communication system 100 is shown in which embodiments of the present disclosure may be implemented.

[0008] Figure 2 A wireless communication system represented as a 5G network architecture is shown, which can be viewed as Figure 1 A specific implementation of system 100.

[0009] Figure 3 A 5G network architecture using service-based interfaces between NFs in the control plane is shown.

[0010] Figure 4 A UE configuration update process according to an embodiment of the present disclosure is shown.

[0011] Figure 5 is a schematic block diagram of a network node 500 according to some embodiments of the present disclosure.

[0012] Figure 6 is a schematic block diagram illustrating a virtualized embodiment of a network node 500 according to some embodiments of the present disclosure.

[0013] Figure 7 is a schematic block diagram of a network node 500 according to some other embodiments of the present disclosure.

[0014] Figure 8 is a schematic block diagram of a wireless communication device 800 according to some embodiments of the present disclosure.

[0015] Fig. 9 is a schematic block diagram of a wireless communication device 800 according to some other embodiments of the present disclosure. DETAILED DESCRIPTION

[0016] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the files provided in the appendix.

[0017] Radio Node: As used herein, a "radio node" is a radio access node or a wireless communication device.

[0018] 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 communication network that operates to send and / or receive signals wirelessly. Some examples of radio access nodes include, 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 that implements part of the functionality of a base station (e.g., a network node that implements a gNB central unit (gNB-CU) or a network node that implements a gNB distributed unit (gNB-DU)) or a network node that implements a gNB distributed unit (gNB-DU) or a network node that implements part of the functionality of some other type of radio access node.

[0019] 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 exposure function (SCEF), a home subscriber server (HSS), etc. Some other examples of core network nodes include nodes that implement access and mobility management function (AMF), user plane function (UPF), session management function (SMF), authentication server function (AUSF), network slice selection function (NSSF), network exposure function (NEF), network function (NF) storage function (NRF), policy control function (PCF), unified data management (UDM), etc.

[0020] Communication device: As used herein, a "communication device" is any type of device that accesses an access network. Some examples of communication devices include, but are not limited to, mobile phones, smart phones, sensor devices, meters, vehicles, household appliances, medical devices, media players, cameras, or any type of consumer electronic device (such as, but not limited to, televisions, radios, lighting devices, tablet computers, laptop computers, or personal computers (PCs)). A communication device can be a portable, handheld, computer-included, or vehicle-mounted mobile device capable of transmitting voice and / or data via a wireless or wired connection.

[0021] Wireless communication device: One type of communication device is a wireless communication device, which may be any type of wireless device that accesses (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 Devices (UE) in 3GPP networks, Machine Type Communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be or may be integrated into a mobile phone, a smart phone, a sensor device, a meter, a vehicle, a home appliance, a medical device, a media player, a camera, or any type of consumer electronic device (e.g., but not limited to: a television, a radio, a lighting device, a tablet computer, a laptop computer, or a PC). A communication device may be a portable, handheld, computer-included, or vehicle-mounted mobile device capable of transmitting voice and / or data via a wireless connection.

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

[0023] Note that the description given herein focuses on 3GPP cellular communication systems and therefore often uses 3GPP LTE terminology or terminology similar to 3GPP LTE terminology. However, the concepts disclosed herein are not limited to 3GPP systems.

[0024] Note that in the description of this document, the term "cell" may be mentioned; however, particularly for 5G NR concepts, beams may be used instead of cells, and therefore it is important to note that the concepts described in this document apply equally to both cells and beams.

[0025] Figure 1

[0026] Figure 1 An example of a cellular communication system 100 in which embodiments of the present disclosure may be implemented is shown. 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 optional next generation eNBs (ng-eNBs) (i.e., LTE RAN nodes connected to the 5GC). In this example, the RAN includes base stations 102-1 and 102-2 that control corresponding (macro) cells 104-1 and 104-2, which are referred to as gNBs (i.e., NR RAN nodes) or optional ng-eNBs (i.e., LTE RAN nodes connected to the 5GC) in the NG-RAN. Base stations 102-1 and 102-2 are generally referred to herein as base stations 102 and individually as base stations 102. Similarly, macro cells 104-1 and 104-2 are generally referred to herein as macro cells 104 and individually as macro cells 104. The RAN may also include a plurality of 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 (e.g., micro base stations or femto base stations) or remote radio heads (RRHs), etc. It is noteworthy that, although not shown, one or more small cells 108-1 to 108-4 may alternatively be provided by the base station 102. The low-power nodes 106-1 to 106-4 are generally collectively referred to as low-power nodes 106 herein, and are respectively referred to as low-power nodes 106. Similarly, the small cells 108-1 to 108-4 are generally collectively referred to as small cells 108 herein, and are respectively referred to as small cells 108. The cellular communication system 100 also includes a core network 110, which is referred to as a 5G core (5GC) in 5GS. The base station 102 (and the optional low-power node 106) are connected to the core network 110.

[0027] Base station 102 and low power node 106 provide services to wireless communication devices 112-1 to 112-5 in corresponding cells 104 and 108. Wireless communication devices 112-1 to 112-5 are generally referred to herein as wireless communication devices 112, and are individually referred to as wireless communication devices 112. In the following description, wireless communication device 112 is generally a UE, but the present disclosure is not limited thereto.

[0028] Figure 2

[0029] Figure 2 A wireless communication system is shown represented as a 5G network architecture consisting of core network functions (NFs), where the interaction between any two NFs is represented by point-to-point reference points / interfaces. Figure 2 can be considered as Figure 1 A specific implementation of the system 100.

[0030] From the access side, Figure 2 The 5G network architecture shown in FIG. 1 includes multiple UEs 112 connected to a RAN 102 or access network (AN) and an access and mobility management function (AMF) 200. Typically, the RAN 102 includes a base station, such as an eNB or gNB. From the core network side, Figure 2 The 5G core NF shown 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.

[0031] In the specification standardization, the reference point representation of the 5G network architecture is used to form a detailed call flow. The N1 reference point is defined to carry signaling between UE 112 and AMF 200. The reference points for the connection between AN 102 and AMF 200 and between AN 102 and UPF214 are defined as N2 and N3, respectively. There is a 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 the UPF 214 can be set using the control signal generated by SMF 208, and UPF 214 can report its status to SMF 208. Respectively, N9 is a reference point for connections between different UPFs 214, and N14 is a reference point for connections between different AMFs 200. N15 and N7 are defined because PCF 210 applies policies to AMF 200 and SMF 208, respectively. AMF 200 requires N12 to perform authentication of UE 112. N8 and N10 are defined because AMF 200 and SMF 208 require subscription data of UE 112.

[0032] The 5GC network is designed to separate the user plane and the control plane. In the network, the user plane carries user services, while the control plane carries signaling. Figure 2In the UE, UPF 214 is in the user plane, while all other NFs, namely AMF 200, SMF 208, PCF 210, AF 212, NSSF 202, AUSF 204 and UDM 206 are in the control plane. Separating the user plane and the control plane ensures that each plane resource can be scaled independently. It also allows the UPF to be deployed separately from the control plane functions in a distributed manner. In this architecture, the UPF can be deployed very close to the UE to shorten the round trip time (RTT) between the UE and the data network for some applications that require low latency.

[0033] The core 5G network architecture consists of modular functions. For example, AMF 200 and SMF 208 are independent functions in the control plane. Separating AMF 200 and SMF 208 allows independent evolution and scaling. Other control plane functions (such as PCF 210 and AUSF 204) can be separated, such as Figure 2 The modular functional design enables the 5GC network to flexibly support various services.

[0034] Each NF interacts directly with another NF. An intermediate function 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 it can be reused. This service implementation supports modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0035] Figure 3

[0036] Figure 3 Figure 5 shows a 5G network architecture that uses service-based interfaces between NFs in the control plane instead of Figure 2 point-to-point reference points / interfaces used in the 5G network architecture. Figure 2 The NF described corresponds to Figure 3 The services provided by NF to other authorized NFs can be opened to authorized NFs through service-based interfaces. Figure 3 In the NF, the service-based interface is represented by the letter “N” followed by the name of the NF, for example, Namf for the service-based interface of AMF 200, Nsmf for the service-based interface of SMF 208, and so on. Figure 3 The network open function (NEF) 300 and the network repository function (NRF) 302 in the above discussion are not shown. Figure 2 However, it should be clarified that although Figure 2 There is no clear instruction in Figure 2 All NFs depicted in Figure 3 The NEF 300 and NRF 302 interact.

[0037] It can be described as follows Figure 2 and 3 110. AMF 200 provides UE-based authentication, authorization, mobility management, etc. Even UE 112 using multiple access technologies is basically connected to a single AMF 200 because AMF 200 is independent of the access technology. SMF 208 is responsible for session management and allocates an Internet Protocol (IP) address to the UE. It also selects and controls UPF 214 for data transmission. If UE 112 has multiple sessions, different SMFs 208 can be assigned to each session to manage them separately and possibly provide different functions for each session. AF 212 provides information about packet flows to PCF 210, which is responsible for policy control, in order to support quality of service (QoS). Based on this information, PCF 210 determines policies on mobility and session management so that AMF 200 and SMF 208 can operate normally. AUSF 204 supports authentication functions for UE, etc., and therefore stores data for authenticating UE, etc., while UDM 206 stores subscription data for UE 112. The data network (DN), which is not part of the 5GC network, provides Internet access or operator services, etc.

[0038] NFs can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on an appropriate platform (e.g., cloud infrastructure).

[0039] Figure 4

[0040] Embodiments of the present disclosure will now be described in detail. In this regard, Figure 4 The UE configuration update process according to an embodiment of the present disclosure is shown. As shown in the figure, AMF 200 sends a configuration update command to UE 112 (step 400). In one embodiment, AMF 200 starts a timer (T3555) when sending the configuration update command. UE 112 performs one or more actions according to the configuration update command (step 402). In one embodiment, UE 112 sends a configuration update completion message to AMF 200 (step 404). In one embodiment, AMF 200 stops the timer (T3555) when receiving the configuration update completion message. However, as shown in the figure, in another embodiment, AMF 200 sends a configuration update command to UE 112 in step 400, but UE 112 does not send a configuration update completion message to AMF 200, and AMF 200 does not start or stop the timer.

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

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

[0043] The one or more actions performed by UE 112 in step 402 include releasing or suppressing the release of the existing N1 NAS signaling connection according to the indication included in the configuration update command. In addition, 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 the existing N1 NAS signaling connection being released or not released according to the indication).

[0044] The currently specified way of using the UE configuration update procedure to request registration to change the MICO mode is achieved by the following combination of the registration request 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:

[0045]

[0046] Registration Requested (RED) (octet 1, bit 2):

[0047] 0Registration not requested

[0048] 1Registration Requested

[0049]

[0050] Note that the content of the MICO Indication IE is not important for use in the UE Configuration Update procedure, as only presence is evaluated.

[0051] To support other cases where registration is requested via the UE configuration update procedure, where N1NAS signaling connection release is not expected or required and no other case-specific actions are required in UE 112, in one embodiment of the present disclosure, a new flag is defined using one of the spare bits in the Configuration Update Indication IE. For example, a new flag called Signaling Connection Release Request (SCRR) may be provided as follows:

[0052]

[0053] Signaling Connection Release Request (SCRR) (octet 1, bit 3)

[0054] 0 Need to release N1 NAS signaling connection

[0055] 1No need to release N1 NAS signaling connection

[0056] In an example alternative embodiment, a new optional IE may be defined. For example, in this example alternative embodiment, the new optional IE is referred to herein as a configuration update parameter IE and may be defined as follows:

[0057]

[0058] Signaling Connection Release Request (SCRR) (octet 1, bit 1)

[0059] 0 Need to release N1 NAS signaling connection

[0060] 11 No need to release N1 NAS signaling connection

[0061] What both of the above protocol implementation alternatives have in common is that the flag (SCRR) is not bound to a specific case, but can be used by the network when subsequent execution of the registration process is sufficient for the specific use case at hand.

[0062] Further details of an example embodiment of the proposed protocol solution are provided in the attached draft Change Request (CR) to 3GPP TS 24.501.

[0063] Figure 5

[0064] Figure 5is a schematic block diagram of a network node 500 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. For example, the network node 500 can be a network node that implements the AMF 200 or implements at least some of the functions of the AMF 200 described herein. As shown in the figure, 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 as processing circuits in this document. The one or more processors 504 operate to provide one or more functions of the network node 500 as described herein (e.g., the functions described herein, for example, with respect to Figure 4 In some embodiments, the functionality may be implemented in software stored in, for example, the memory 506 and executed by one or more processors 504.

[0065] Figure 6

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

[0067] 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 one or more functions of the network node 500 or a virtual environment implementing the functions 610 of the network node 500 according to any embodiment described herein (e.g., as described herein, for example, with respect to Figure 4 The computer program product described herein may be implemented by a node (e.g., processing node 600) that implements one or more functions of the AMF 200 described herein. In some embodiments, a carrier including the above-mentioned computer program product is provided. 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).

[0068] Figure 7

[0069] Figure 7 700 is a schematic block diagram of a network node 500 according to some other embodiments of the present disclosure. The network node 500 includes one or more modules 700, each of which is implemented by software. The module 700 provides the functions of the network node 500 described herein (e.g., Figure 4 The discussion also applies to one or more functions of the AMF 200 described in Figure 6 6. The processing node 600 of FIG. 600 may be implemented at one of the processing nodes 600 or distributed among two or more of the processing nodes 600.

[0070] Figure 8

[0071] Figure 8 is a schematic 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.), a memory 804, and one or more transceivers 806, each transceiver 806 including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812. The transceiver 806 includes a radio front-end circuit connected to the antenna 812, which is configured to condition signals transmitted between the antenna 812 and the processor 802, as will be understood by a person of ordinary skill 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 functions of the wireless communication device 800 described above (e.g., as described herein, for example) Figure 4 One or more functions of the UE 112 described herein may be implemented in whole or in part by software stored in the memory 804 and executed by the processor 802, for example. Note that the wireless communication device 800 may include Figure 8Additional components not shown in the figure, such as one or more user interface components (e.g., input / output interfaces including displays, buttons, touch screens, microphones, speakers, etc., and / or any other components that allow information to be input to the wireless communication device 800 and / or allow information to be output from the wireless communication device 800), power sources (e.g., batteries and associated power circuits), etc.

[0072] In some embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of the wireless communication device 800 according to any embodiment described herein (e.g., providing the present invention, for example, regarding Figure 4 In some embodiments, a carrier including the above-mentioned computer program product is provided. 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).

[0073] Fig. 9

[0074] Fig. 9 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 module 900 provides the functions of the wireless communication device 800 described herein (e.g., Figure 4 one or more functions of the AMF 200 described herein).

[0075] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented by a processing circuit, which may include one or more microprocessors or microcontrollers and other digital hardware (which may include a digital signal processor (DSP), dedicated digital logic, etc.). The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, the processing circuit may be used to cause the corresponding functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0076] Although the processes in the figures illustrate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that this order is exemplary (for example, alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0077] Some embodiments

[0078] Some of the embodiments disclosed above can be summarized in the following way:

[0079] 1. A method performed by a wireless communication device (112), the method comprising:

[0080] receiving (400) a configuration update command from a network node (200), the configuration update command including an indication as to whether the wireless communication device (112) is to maintain an existing non-access stratum (NAS) connection; and

[0081] One or more actions are performed (402) according to the configuration update command.

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

[0083] 3. The method of embodiment 1 or 2, wherein performing (402) the one or more actions includes releasing or refraining from releasing the existing NAS connection based on the indication.

[0084] 4. The method of any one of embodiments 1 to 3, wherein the indication is a 1-bit indication, and if the 1-bit indication is set to a first binary value, it indicates that the wireless communication device (112) is required to release the existing NAS connection, and if the 1-bit indication is set to a second binary value, it indicates that the communication device (112) is not required to release the existing NAS connection.

[0085] 5. The method of any one of embodiments 1 to 4, 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 process.

[0086] 6. The method of embodiment 5, wherein performing (402) the one or more actions comprises: performing the registration procedure, and releasing or refraining from releasing the existing NAS connection according to the indication when performing the registration procedure.

[0087] 7. The method of any one of embodiments 1 to 6, wherein the indication is a general indication applicable to two or more reasons for the configuration update command.

[0088] 8. The method according to any one of embodiments 1 to 7, wherein the indication is included in a configuration update indication information element included in the configuration update command.

[0089] 9. The method of embodiment 8, wherein the indication is a 1-bit indication included in bit 3 or bit 4 of octet 1 of the configuration update indication information element.

[0090] 10. The method of any one of embodiments 1 to 7, wherein the indication is included in an information element other than a configuration update indication information element included in the configuration update command.

[0091] 11. A method according to any one of embodiments 1 to 10, wherein the network node (200) is an access and mobility management function AMF (200).

[0092] 12. A wireless communication device (112), adapted to:

[0093] receiving (400) a configuration update command from a network node (200), the configuration update command including an indication as to whether the wireless communication device (112) is to maintain an existing non-access stratum (NAS) connection; and

[0094] One or more actions are performed (402) according to the configuration update command.

[0095] 13. The wireless communication device (112) of embodiment 12, wherein the wireless communication device (112) is further adapted to perform the method of any one of embodiments 2 to 11.

[0096] 14. The wireless communication device (112) of embodiment 12 or 13, wherein the wireless communication device (112) comprises:

[0097] one or more transmitters (808);

[0098] one or more receivers (810); and

[0099] a processing circuit (802) associated with the one or more transmitters (808) and the one or more receivers (810), the processing circuit (802) being configured to cause the wireless communication device (112):

[0100] receiving (400) the configuration update command from the network node (200); and

[0101] The one or more actions are performed (402) according to the configuration update command.

[0102] 15. A method performed by a network node (200) of a wireless communication system (100), the method comprising:

[0103] A configuration update command is sent (400) to the wireless communication device (112), the configuration update command including an indication as to whether the wireless communication device (112) is to maintain an existing non-access stratum (NAS) connection.

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

[0105] 17. The method of any one of embodiments 15 to 16, wherein the indication is a 1-bit indication, wherein the 1-bit indication, if set to a first binary value, indicates that the wireless communication device (112) is required to release an existing NAS connection, and wherein the 1-bit indication, if set to a second binary value, indicates that the communication device (112) is not required to release the existing NAS connection.

[0106] 18. The method of any one of embodiments 15 to 17, 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.

[0107] 19. The method of any one of embodiments 15 to 18, wherein the indication is a general indication applicable to two or more reasons for the configuration update command.

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

[0109] 21. The method of embodiment 20, wherein the indication is a 1-bit indication included in bit 3 or bit 4 of octet 1 of the configuration update indication information element.

[0110] 22. The method of any one of embodiments 15 to 18, wherein the indication is included in an information element other than a configuration update indication information element included in the configuration update command.

[0111] 23. A method according to any one of embodiments 15 to 22, wherein the network node (200) is an access and mobility management function AMF (200).

[0112] 24. A network node (200) of a wireless communication system (100), the network node (200) being adapted to:

[0113] A configuration update command is sent (400) to the wireless communication device (112), the configuration update command including an indication as to whether the wireless communication device (112) is to maintain an existing non-access stratum (NAS) connection.

[0114] 25. The network node (200) according to embodiment 24, wherein the network node (200) is further adapted to perform the method according to any one of embodiments 16 to 23.

[0115] 26. A network node (200) according to embodiment 24 or 25, wherein the network node (200) includes a processing circuit (504; 604), and the processing circuit (504; 604) is configured to cause the network node (200) to send (400) the configuration update command to the wireless communication device (112).

[0116] abbreviation

[0117] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, how it is used above shall take precedence. If listed multiple times below, the first listing shall take precedence over any subsequent listings.

[0118] 3GPP Third Generation Partnership Project

[0119] 5G Fifth Generation

[0120] 5GC Fifth Generation Core

[0121] 5GS Fifth Generation System

[0122] AF Application Function

[0123] AMF Access and Mobility Management Function

[0124] AN Access Network

[0125] AUSF authentication server function

[0126] DN Data Network

[0127] eNB Enhanced or evolved Node B

[0128] EPC Evolved Packet Core

[0129] E-UTRA Evolved Universal Terrestrial Radio Access

[0130] gNB New Radio Base Station

[0131] HSS Home Subscriber Server

[0132] IoT

[0133] IP Internet Protocol

[0134] LTE Long Term Evolution

[0135] MME Mobility Management Entity

[0136] MTC Machine Type Communication

[0137] NEF Network Exposure Function

[0138] NF Network Function

[0139] NR New Radio

[0140] NRF Network Function Repository Features

[0141] NSSF network slice selection function

[0142] PCF Policy Control Function

[0143] P-GW Packet Data Network Gateway

[0144] QoS Quality of Service

[0145] RAN Radio Access Network

[0146] SCEF service capability exposure function

[0147] SMF session management functions

[0148] UDM Unified Data Management

[0149] UE User Equipment

[0150] UPF User Plane Function.

[0151] appendix

[0152] 3GPP TSG-CT WG1 Meeting #123-e C1-20wxyz

[0153] Electronic conference, April 16-24, 2020

[0154]

[0155] For assistance, use the following form: Comprehensive instructions can be found at http: / / www.3gpp.org / Change-Requests.

[0156] Proposed changes impact: UICC applications ME Radio Access Network Core Network

[0157]

[0158]

[0159]

[0160]

[0161]

[0162]

[0163] ***First Change***

[0164] 5.3.18 Restrictions on the use of enhanced overlays

[0165] In order to handle the large usage of resources from the network, operators may block specific subscribers from using enhanced coverage (see 3GPP TS 23.501[8]). When in NB-N1 mode, the UE shall indicate support for restriction on the use of enhanced coverage. When in WB-N1 mode, a UE supporting CE mode A or CE mode B shall indicate support for restriction on the use of enhanced coverage. A UE supporting restriction on the use of enhanced coverage indicates in the REGISTRATION REQUEST message that it supports restriction on the use of enhanced coverage. If the UE supports restriction on the use of enhanced coverage, the AMF indicates in the REGISTRATION ACCEPT message whether the use of enhanced coverage is restricted (see subsections 5.5.1.2 and 5.5.1.3). If the use of enhanced coverage is restricted, the UE shall not use enhanced coverage in any PLMN in the registered PLMN and equivalent PLMN list.

[0166] If the UE supports CE Mode B and the network determines

[0167] - the use of enhanced coverage is not restricted for UE; or

[0168] -CE mode B does not restrict UE;

[0169] Applicable NAS timer values ​​shall be calculated by the network as described in subsections 4.19 and 4.20.

[0170] For UEs supporting restriction on use of enhanced coverage or CE Mode B, if:

[0171] a) the AMF determines to force a change in restrictions on the use of enhanced coverage or to force a change in restrictions on the use of CE Mode B as described in 3GPP TS 23.501 [8]; and

[0172] b) The UE is in "5GMM-Connected" mode and there is no ongoing registration procedure;

[0173] The AMF shall initiate the Generic UE Configuration Update procedure to indicate the requested registration and to indicate to maintain the existing N1 NAS signalling connection as described in subclause 5.4.4.

[0174] NOTE: After successful completion of the registration procedure and registration update for mobility (including changing the restriction on the use of enhanced coverage), the AMF updates the SMF with an indication of the use of extended NAS timer settings for any SMF with which a PDU session has been established, as described in 3GPP TS 23.501 [8] and 3GPP TS 23.502 [9].

[0175] ***Next Change***

[0176] 5.4.4 General UE Configuration Update Procedure

[0177] 5.4.4.1 Overview

[0178] The purpose of this process is to:

[0179] a) allowing the AMF to update the UE configuration for parameters related to access and mobility management determined and provided by the AMF by providing new parameter information in the command; or

[0180] b) Request the UE to perform a mobility registration procedure and periodic registration updates with the network to update parameters related to access and mobility management determined and provided by the AMF (see subsection 5.5.1.3).

[0181] NOTE: When requesting to perform a registration procedure and periodic registration update for mobility, the AMF may also request the UE to release or maintain the existing N1 NAS signalling connection.

[0182] This procedure is initiated by the network and can only be used when the UE has an established 5GMM context and the UE is in "5GMM-CONNECTED" mode. When the UE is in 5GMM-IDLE mode, the AMF may use a paging or notification procedure to initiate a generic UE configuration update procedure. The AMF may request a confirmation response in order to ensure that the parameters have been updated by the UE.

[0183] This procedure shall be initiated by the network to allocate a new 5G-GUTI to the UE after a successful invocation of the Service Request procedure as a response to a Paging Request from the network and before releasing the N1 NAS signalling connection. If the Service Request procedure is triggered due to pending 5GSM downlink signalling, the procedure for allocating a new 5G-GUTI may be initiated by the network after transmitting the 5GSM downlink signalling.

[0184] The following parameters are supported by the generic UE configuration update procedure without requiring the UE to perform a registration procedure and periodic registration updates for mobility:

[0185] a) 5G-GUTI;

[0186] b)TAI list;

[0187] c) List of service areas;

[0188] d) Network identification and time zone information (full name of the network, abbreviation of the network, local time zone, universal time and local time zone, network daylight saving time);

[0189] e) LADN information;

[0190] f) rejected NSSAI;

[0191] g) invalid;

[0192] h) Operator-defined access category definitions;

[0193] i) SMS instructions;

[0194] j) service gap time value;

[0195] k) “CAG information list”;

[0196] 1) UE radio capability ID; and

[0197] m)5GS registration results.

[0198] The following parameters may be sent to the UE with or without requesting to perform the registration procedure and periodic registration updates for mobility:

[0199] a) permitted NSSAI;

[0200] b) configured NSSAI; or

[0201] c) Network slice subscription change indication.

[0202] In case of a request to perform a registration procedure for mobility and a periodic registration update, the following parameters may be sent to the UE:

[0203] a) MICO instructions; or

[0204] b) UE radio capability ID deletion indication.

[0205] The following parameters are sent only via 3GPP access:

[0206] a) LADN information;

[0207] b) MICO instructions;

[0208] c)TAI list;

[0209] d) List of service areas;

[0210] e) Service gap time value;

[0211] f) “CAG Information List”; and

[0212] g) UE radio capability ID.

[0213] The following parameters are managed and sent depending on the access type (i.e., 3GPP independent access or non-3GPP access):

[0214] a) permitted NSSAI; and

[0215] b) Rejected NSSAI (when NSSAI is rejected for the current registration area).

[0216] The following parameters are jointly managed and sent via 3GPP access or non-3GPP access:

[0217] a) 5G-GUTI;

[0218] b) Network identification and time zone information;

[0219] c) rejected NSSAI (when NSSAI is rejected for the current PLMN);

[0220] d) configured NSSAI;

[0221] e) SMS instructions;

[0222] f)5GS registration results.

[0223]

[0224] Figure 5 .4.4.1.1: General UE configuration update procedure

[0225] ***Next Change***

[0226] 5.4.4.2 General UE configuration update procedure initiated by the network

[0227] The AMF shall initiate the general UE configuration update procedure by sending a "Configuration Update Command" message to the UE.

[0228] The AMF shall, in the Configuration Update Command message:

[0229] a) includes one or more of the following parameters: 5G-GUTI, TAI list, allowed NSSAI which may include mapped S-NSSAI, LADN information, service area list, MICO indication NITZ information, configured NSSAI which may include mapped S-NSSAI, rejected NSSAI, network slice subscription change indication, operator defined access class definition, SMS indication, service gap time value, "CAG information list", UE radio capability ID, 5GS registration result or UE radio capability ID deletion indication;

[0230] b) includes a Configuration Update Indication IE with the Registration Requested bit set to "Registration Requested"; or

[0231] c) includes a combination of a) and b).

[0232] If confirmation from the UE is requested, the AMF shall indicate "Confirmation Requested" in the Confirmation bit of the Configuration Update Indication IE in the Configuration Update Command message and shall start timer T3555. Confirmation shall be requested for all parameters unless only NITZ is included.

[0233] To initiate parameter re-negotiation between the UE and the network, the AMF shall indicate “Registration Requested” in the Registration Requested bit of the Configuration Update Indication IE in the Configuration Update Command message.

[0234] If new Allowed NSSAI information or AMF reconfiguration of supported S-NSSAI requires AMF relocation, the AMF shall indicate “Registration Requested” in the Registration Requested bit of the Configuration Update Indication IE and include the Allowed NSSAI IE in the Configuration Update Command message.

[0235] If the AMF includes a new configured NSSAI in the "Configuration Update Command" message and the new configured NSSAI requires AMF relocation as specified in 3GPP TS 23.501 [8], the AMF shall indicate "Registration Requested" in the Registration Requested bit of the Configuration Update Indication IE in this message.

[0236] If the AMF indicates "Registration Requested" in the Registration Requested bit of the Configuration Update Indication IE, confirmation shall be requested.

[0237] If the Configuration Update Command message is initiated only due to changes to 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], then the Configuration Update Command message shall indicate "Registration Requested" in the Registration Requested bit of the Configuration Update Indication IE and shall not include any other parameters.

[0238] In order to request the UE to maintain the existing N1 NAS signalling connection upon registration request, the AMF shall indicate "No need to release N1 NAS signalling connection" in the Signalling Connection Release Request bit of the Configuration Update Indication IE in the Configuration Update Command message.

[0239] If the network slice specific authentication and authorization process for S-NSSAI is done as:

[0240] If successful, the AMF shall include the S-NSSAI in the allowed NSSAIs; or

[0241] If the S-NSSAI fails, the AMF shall include this S-NSSAI in the rejected NSSAI with the rejection reason "S-NSSAI not available due to failed or revoked network slice specific authorization and authentication" included in the rejected NSSAI.

[0242] The allowed NSSAI and rejected NSSAI shall be included in the "Configuration Update Command" message to reflect the results of the network slice specific authentication and authorization process.

[0243] NOTE: If there are multiple S-NSSAIs that are subject to network slice specific authentication and authorization, then it is implementation specific if the AMF informs the UE about the outcome of this procedure in one or more Configuration Update Command messages.

[0244] If the AMF includes a Network Slice Indication IE in a Configuration Update Command with the Network Slice Subscription Change Indication set to "Network Slice Subscription Changed", and the change to the allowed NSSAI requires 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], then the Configuration Update Command message shall additionally indicate "Registration Requested" in the Registration Requested bit of the Configuration Update Indication IE and shall not include the allowed NSSAI.

[0245] If the AMF needs to update the LADN information, the AMF shall include the LADN information in the LADN Information IE of the Configuration Update Command message.

[0246] If the AMF needs to update the CAG information, the AMF shall include the CAG Information List IE in the Configuration Update Command message.

[0247] During an established 5G MM context, the network may send zero, one, or more "Configuration Update Command" messages to the UE. If more than one "Configuration Update Command" message is sent, these messages do not need to have the same content.

[0248] ***Next Change***

[0249] 5.4.4.3 General UE configuration updates accepted by the UE

[0250] Upon receiving the "Configuration Update Command" message, if timer T3346 is running, the UE shall stop timer T3346 and use the content to update the appropriate information stored within the UE.

[0251] If "Confirmation Requested" is indicated in the Confirmation bit of the Configuration Update Indication IE in the "Configuration Update Command" message, the UE shall send a "CONFIGURATION UPDATE COMPLETE" message.

[0252] If the UE receives a new 5G-GUTI in the "Configuration Update Command" message, the UE shall consider the new 5G-GUTI valid and the old 5G-GUTI invalid, stop timer T3519 if it is running, and delete any stored SUCI; otherwise, the UE shall consider the old 5G-GUTI valid. If the "Configuration Update Command" message is sent via non-3GPP access and the UE is in the "5GMM-REGISTERED" state in both 3GPP access and non-3GPP access in the same PLMN, the UE shall provide the 5G-GUTI to the lower layers of the 3GPP access.

[0253] If the UE receives a new TAI list in the "Configuration Update Command" message, the UE shall consider the new TAI list to be valid and the old TAI list to be invalid; otherwise, the UE shall consider the old TAI list to be valid.

[0254] If the UE receives a new service area list in the "Configuration Update Command" message, the UE shall consider the new service area list to be valid and the old service area list to be invalid; otherwise, the UE shall consider the old service area list (if any) to be valid.

[0255] If the UE receives new NITZ information in the "Configuration Update Command" message, the UE shall consider the new NITZ information to be valid and the old NITZ information to be invalid; otherwise, the UE shall consider the old NITZ information to be valid.

[0256] If the UE receives the LADN information IE in the "Configuration Update Command" message, the UE shall consider the old LADN information invalid and the new LADN information (if any) valid; otherwise, the UE shall consider the old LADN information valid.

[0257] If the UE receives a new allowed NSSAI for the associated access type in the "Configuration Update Command" message, the UE shall consider the new allowed NSSA to be valid for the associated access type, store the allowed NSSAI for the associated access type as specified in subsection 4.6.2.2, and consider the old allowed NSSAI for the associated access type to be invalid; otherwise, the UE shall consider the old allowed NSSAI to be valid for the associated access type.

[0258] If the UE receives a new configured NSSAI in the "Configuration Update Command" message, the UE shall consider the new configured NSSAI of the registered PLMN valid and the old configured NSSAI of the registered PLMN invalid; otherwise, the UE shall consider the old configured NSSAI of the registered PLMN valid. The UE shall store the new configured NSSAI as specified in subsection 4.6.2.2.

[0259] 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 Changed", the UE shall delete the network slice information for each and every PLMN except the current PLMN as specified in subsection 4.6.2.2.

[0260] If the UE receives an Operator Defined Access Class Definitions IE in a Configuration Update Command message and the Operator Defined Access Class Definitions IE contains one or more operator defined access class definitions, the UE shall delete any operator defined access class definitions stored for the RPLMN and shall store the received operator defined access class definitions for the RPLMN. If the UE receives an Operator Defined Access Class Definitions IE in a Configuration Update Command message and the Operator Defined Access Class Definitions IE does not contain operator defined access class definitions, the UE shall delete any operator defined access class definitions stored for the RPLMN. If the Configuration Update Command message does not contain the Operator Defined Access Class Definitions IE, the UE shall not delete the operator defined access class definitions stored for the RPLMN.

[0261] If the UE receives the SMS Indication IE in the Configuration Update Command message with the SMS Availability Indication set to:

[0262] a) "SMS over NAS not available", the UE shall assume that the network does not allow SMS delivery over NAS; and

[0263] b) "SMS over NAS is available", the UE may request to use SMS transport over NAS by performing a registration procedure for mobility and a periodic registration update after completing the general UE configuration update procedure, as specified in subclause 5.5.1.3.

[0264] If the UE receives a CAG Information List IE in a "Configuration Update Command" message, the UE shall delete any stored "CAG Information List" and shall store the received "CAG Information List" via the CAG Information List IE as specified in Annex C.

[0265] If the received "CAG Information List" includes an entry containing the identity of the current PLMN, the UE shall operate as follows.

[0266] a) If the UE receives a "Configuration Update Command" message via a CAG cell, the "Allowed CAG List" for the current PLMN in the received "CAG Information List" does not include the CAG-ID of the current CAG cell, and:

[0267] i) the entry for the current PLMN in the received "CAG Information List" does not include an "indication that the UE is only allowed to access the 5GS via CAG cells", the UE shall enter state "5GMM-REGISTERED.LIMITED-SERVICE" and shall search for a suitable cell according to 3GPP TS 38.304

[28] using the updated "CAG Information List"; or

[0268] ii) the entry for the current PLMN in the received "CAG Information List" includes an "indication that the UE is only allowed to access the 5GS via CAG cells", and:

[0269] 1) If the "Allowed CAG List" for the current PLMN in the received "CAG Information List" includes one or more CAG-IDs, the UE shall enter state "5GMM-REGISTERED.LIMITED-SERVICE" and shall search for a suitable cell according to 3GPP TS 38.304

[28] using the updated "CAG Information List"; or

[0270] 2) if the "Allowed CAG List" for the current PLMN in the received "CAG Information List" does not include any CAG-ID, the UE shall enter state "5GMM-DEREGISTERED.PLMN-SEARCH" and shall apply the PLMN selection procedure defined in 3GPP TS 23.122 [6] using the updated "CAG Information List"; or

[0271] b) If 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" includes an "indication that the UE is only allowed to access the 5GS via CAG cells", and:

[0272] i) if the "Allowed CAG List" for the current PLMN in the received "CAG Information List" includes one or more CAG-IDs, the UE shall enter state "5GMM-REGISTERED.LIMITED-SERVICE" and search for a suitable cell according to 3GPP TS 38.304

[28] using the updated "CAG Information List"; or

[0273] ii) If the "Allowed CAG List" for the current PLMN in the received "CAG Information List" does not include any CAG-ID, the UE shall enter state "5GMM-DEREGISTERED.PLMN-SEARCH" and apply the PLMN selection procedure defined in 3GPP TS 23.122 [6] using the updated "CAG Information List".

[0274] If the Configuration Update Command message indicates "Registration Requested" in the Registration Requested bit of the Configuration Update Indication IE, and:

[0275] a) contains no other parameters or contains at least one of the following parameters: new allowed NSSAI, new configured NSSAI, or network slice subscription change indication, and:

[0276] 1) if an emergency PDU session exists, the UE shall release the existing N1 NAS signalling connection after completing the general UE configuration update procedure and releasing the emergency PDU session, and initiate the registration procedure and periodic registration update for mobility as specified in subclause 5.5.1.3; or

[0277] 2) In the absence of an emergency PDU session, the UE shall initiate the registration procedure and periodic registration update for mobility as specified in subsection 5.5.1.3 after completing the general UE configuration update procedure and releasing the existing N1 NAS signalling connection;

[0278] b) including a MICO indication without a new allowed NSSAI or a new configured NSSAI, the UE shall initiate the Registration procedure and Registration Update for mobility as specified in subclause 5.5.1.3 after completing the general UE configuration update procedure to renegotiate the MICO mode with the network; or

[0279] c) In the absence of a new allowed NSSAI or a new configured NSSAI, and the “No release of N1 NAS signalling connection required” is indicated in the Signalling Connection Release Request bit of the Configuration Update Indication IE, the UE shall initiate the Registration procedure and Registration Update for mobility after completing the general UE Post-Configuration Update procedure as specified in subsection 5.5.1.3.

[0280] A UE that receives a rejected NSSAI in a Configuration Update Command message takes the following actions based on the rejection cause in the rejected NSSAI:

[0281] "S-NSSAI is not available in the current PLMN or SNPN"

[0282] The UE shall add the rejected S-NSSAI to the rejected NSSAI of the current PLMN as specified in clause 4.6.2.2 and shall not attempt to use that S-NSSAI in the current PLMN until the UE is switched off, the UICC containing the USIM is removed, or the entry of the "Subscriber Data List" is updated with the SNPN identity of the current SNPN.

[0283] "S-NSSAI is not available in the current registration area"

[0284] The UE shall add the rejected S-NSSAI to the rejected NSSAI 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 switched off, the UE moves out of the current registration area, removes the UICC including the USIM, or updates the entry of the "Subscriber Data List" with the SNPN identification of the current SNPN.

[0285] If the UE receives the T3447 Value IE in the "Configuration Update Command" message and has indicated "Service Gap Control Supported" in the "Registration Request", the UE shall replace the stored T3447 value with the received value in the T3447 Value IE, and if the received T3447 value is neither zero nor deactivated, use the received T3447 value when starting timer T3447 next time. If the received T3447 value is zero or deactivated, the UE shall stop timer T3447 if it is running.

[0286] If the UE is not in NB-N1 mode, the UE has set the RACS bit to “RACS supported” in the 5GMM Capability IE of the Registration Request message, and the Configuration Update Command message includes:

[0287] a) the UE Radio Capabilities ID Deletion Indication IE is set to "Network assigned UE Radio Capabilities ID Requested", the UE shall delete any network assigned UE Radio Capabilities ID associated with the RPLMN or RSNPN stored at the UE, and the UE shall then initiate the Registration procedure for mobility and periodic Registration Updates as specified in subsection 5.5.1.3.2. If the UE has a manufacturer assigned UE Radio Capabilities ID applicable to the current UE radio configuration, the UE shall include the manufacturer assigned UE Radio Capabilities ID in the UE Radio Capabilities ID IE of the Registration Request message; and

[0288] b) UE Radio Capability ID IE, the UE shall store the UE Radio Capability ID as specified in Annex C.

[0289] 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 consider itself registered for emergency services.

[0290] ***Next Change***

[0291] 9.11.3.18 Configuration Update Indication

[0292] The purpose of the Configuration Update Indication information element is to indicate additional information associated with the general UE configuration update procedure.

[0293] The configuration update indication information element is encoded as follows Fig. 9 .11.3.18.1 and Table 9.11.3.18.1.

[0294] A configuration update indication is a type 1 information element.

[0295]

[0296] Fig. 9 .11.3.18.1: Configuration Update Indication

[0297] Table 9.11.3.18.1: Configuration update indication

[0298]

[0299]

[0300] ***CHANGES END***.

Claims

1. A method performed by a user equipment UE (112) in a UE configuration update process, the method comprising: receiving (400) a configuration update command from a network node (200), the configuration update command comprising information indicating to the UE (112) that the UE is to perform a registration procedure and an indication that the UE (112) is to maintain an existing N1 non-access stratum NAS connection of the UE; as well as One or more actions are performed (402) in accordance with the configuration update command, wherein when the configuration update command does not include a mobile initiated connection only (MICO) indication, performing (402) the one or more actions includes performing the registration procedure without releasing the existing N1 NAS connection in accordance with the indication when performing a registration procedure.

2. The method according to claim 1, wherein: The indication is a 1-bit indication, which, if set to a first binary value, indicates that the UE (112) is required to release an existing NAS connection, and which, if set to a second binary value, indicates that the UE (112) is not required to release the existing NAS connection.

3. The method according to any one of claims 1 to 2, wherein: The indication is a general indication applicable to two or more reasons for the configuration update command.

4. The method according to any one of claims 1 to 2, wherein: The network node (200) is an Access and Mobility Management Function AMF (200).

5. A user equipment UE (112), adapted to: receiving (400) a configuration update command from a network node (200), the configuration update command comprising information indicating to the UE (112) that the UE is to perform a registration procedure and an indication that the UE (112) is to maintain an existing N1 non-access stratum (NAS) connection of the UE; and One or more actions are performed (402) according to the configuration update command, wherein: When the configuration update command does not include a mobile initiated connection only (MICO) indication, performing (402) one or more actions includes performing a registration procedure without releasing the existing N1 NAS connection according to the indication when performing the registration procedure.

6. The UE (112) according to claim 5, wherein: The UE (112) is further adapted to perform the method according to any one of claims 1 to 4.

7. The UE (112) according to claim 5 or 6, wherein: The UE (112) comprises: one or more transmitters (808); one or more receivers (810); and A processing circuit (802) is associated with the one or more transmitters (808) and the one or more receivers (810), the processing circuit (802) being configured to cause the UE (112): receiving (400) the configuration update command from the network node (200); and The one or more actions are performed (402) according to the configuration update command.

Images