Apparatus and method for processing non-access stratum message in wireless communication system
The method for determining NAS transmission procedures based on TAI changes and S-NSSAI support addresses service continuity issues in wireless communication systems by optimizing network resource management and ensuring efficient communication.
Patent Information
- Application Number
- PCT/KR2024/003332
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-08
- Filing Date
- 2024-03-18
- Publication Date
- 2024-11-14
AI Technical Summary
Current wireless communication systems face challenges in effectively processing non-access stratum (NAS) messages, particularly when uplink NAS transport messages fail due to changes in tracking area identifiers (TAI) or lack of support for single network slice selection assistance information (S-NSSAI), leading to service continuity issues and inefficient network slice resource management.
The proposed solution involves an apparatus and method for determining whether to stop or re-execute a NAS transmission procedure based on whether the new tracking area supports S-NSSAI, using a combination of TAI list comparisons and reports from lower layers, allowing for partial network slice support and alternative S-NSSAI handling to ensure seamless communication.
This approach effectively processes NAS messages by determining the appropriate action based on TAI changes and S-NSSAI support, minimizing service disruptions and optimizing network resource utilization, thereby enhancing service continuity and network efficiency.
Smart Images

Figure KR2024003332_14112024_PF_FP_ABST
Abstract
Description
Device and method for processing non-connection layer messages in a wireless communication system
[0001] The present disclosure relates to a wireless communication system, and more particularly, to a device and method for processing a non-access stratum (NAS) message in a wireless communication system.
[0002] Wireless access systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless access systems are multiple access systems that support communications with multiple users by sharing available system resources (e.g., bandwidth, transmission power). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single-carrier frequency division multiple access (SC-FDMA).
[0003] In particular, as numerous communication devices demand greater communication capacity, enhanced mobile broadband (eMBB) communication technologies are being proposed, improving upon existing radio access technology (RAT). Furthermore, massive machine type communications (mMTC), which connects numerous devices and objects to provide diverse services anytime and anywhere, as well as communication systems that consider reliability and latency-sensitive services / user equipment (UE), are being proposed. Various technological configurations are being proposed for these purposes.
[0004] The present disclosure relates to a device and method for effectively processing a non-access stratum (NAS) message in a wireless communication system.
[0005] The present disclosure relates to a device and method for processing an uplink (UL) NAS transport message whose transmission has failed in a wireless communication system.
[0006] The present disclosure relates to a device and method for determining whether to interrupt an NAS transmission procedure initiated by a terminal based on a tracking area identifier (TAI) list in a wireless communication system.
[0007] The present disclosure relates to a device and method for determining whether to stop an NAS transmission procedure based on whether a changed TA supports S-NSSAI (single network slice selection assistance information) in a wireless communication system.
[0008] The present disclosure relates to a device and method for determining whether to interrupt an NAS transmission procedure based on a report of a lower layer related to S-NSSAI in a wireless communication system.
[0009] The present disclosure relates to a device and method for determining whether to suspend an NAS transmission procedure based on whether a terminal supports partial network slices in a wireless communication system.
[0010] The present disclosure relates to a device and method for determining whether to abort an NAS transmission procedure based on a partially accepted NSSAI or a partially rejected NSSAI in a wireless communication system.
[0011] The present disclosure relates to a device and method for determining whether to interrupt an NAS transmission procedure based on an alternative NSSAI in a wireless communication system.
[0012] The technical objectives to be achieved in the present disclosure are not limited to those mentioned above, and other technical tasks not mentioned can be considered by a person having ordinary skill in the technical field to which the technical configuration of the present disclosure is applied from the embodiments of the present disclosure described below.
[0013] As an example of the present disclosure, a method performed by a terminal in a wireless communication system includes the steps of initiating a non-access stratum (NAS) transport procedure, detecting a transmission failure of an uplink (UL) NAS transport message due to a change in a tracking area identifier (TAI), comparing the changed TAI with a TAI list, and determining whether to stop the NAS transport procedure based on a result of the comparison, wherein whether to stop the NAS transport procedure can be further determined based on at least one of whether a TA of the changed TAI supports single network slice selection assistance information (S-NSSAI) included in the UL NAS transport message and a report related to S-NSSAI obtained from a lower layer of the terminal.
[0014] As an example of the present disclosure, in a wireless communication system, a terminal includes a transceiver and a processor connected to the transceiver, wherein the processor initiates a non-access stratum (NAS) transport procedure, detects a transmission failure of an uplink (UL) NAS transport message due to a change in a tracking area identifier (TAI), compares the changed TAI with a TAI list, and determines whether to stop the NAS transport procedure based on a comparison result, wherein whether to stop the NAS transport procedure may be further determined based on at least one of whether a TA of the changed TAI supports single network slice selection assistance information (S-NSSAI) included in the UL NAS transport message and a report related to S-NSSAI obtained from a lower layer of the terminal.
[0015] As an example of the present disclosure, a communication device includes at least one processor, and at least one computer memory connected to the at least one processor and storing instructions that direct operations when executed by the at least one processor, the operations including: initiating a non-access stratum (NAS) transport procedure, detecting a transmission failure of an uplink (UL) NAS transport message due to a change in a tracking area identifier (TAI), comparing the changed TAI with a TAI list, and determining whether to stop the NAS transport procedure based on a result of the comparison, wherein whether to stop the NAS transport procedure may be further determined based on at least one of whether a TA of the changed TAI supports single network slice selection assistance information (S-NSSAI) included in the UL NAS transport message and a report related to S-NSSAI obtained from a lower layer of the terminal.
[0016] As an example of the present disclosure, a non-transitory computer-readable medium storing at least one instruction includes at least one instruction executable by a processor, wherein the at least one instruction causes a device to initiate a non-access stratum (NAS) transport procedure, detect a transmission failure of an uplink (UL) NAS transport message due to a change in a tracking area identifier (TAI), compare the changed TAI with a TAI list, and determine whether to stop the NAS transport procedure based on a comparison result, wherein whether to stop the NAS transport procedure may be further determined based on at least one of whether a TA of the changed TAI supports single network slice selection assistance information (S-NSSAI) included in the UL NAS transport message and a report related to S-NSSAI obtained from a lower layer of the terminal.
[0017] The above-described aspects of the present disclosure are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description of the present disclosure to be described below.
[0018] The following effects may be achieved by embodiments based on the present disclosure.
[0019] The present disclosure can effectively process NAS messages in a wireless communication system.
[0020] The effects that can be obtained from the embodiments of the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly derived and understood by those skilled in the art to which the technical configuration of the present disclosure is applied, from the description of the embodiments of the present disclosure below. In other words, unintended effects that result from implementing the configuration described in the present disclosure can also be derived by those skilled in the art from the embodiments of the present disclosure.
[0021] The accompanying drawings are intended to aid in understanding the present disclosure and, together with detailed descriptions, may provide embodiments of the present disclosure. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing may indicate structural elements.
[0022] Figure 1 illustrates an example of a communication system applicable to the present disclosure.
[0023] FIG. 2 illustrates an example of a user equipment (UE) applicable to the present disclosure.
[0024] FIG. 3 illustrates an example of functional separation of a next generation radio access network (NG-RAN) and a 5th generation core (5GC) applicable to the present disclosure.
[0025] FIG. 4 illustrates an example of a general architecture of a 5G (5th generation) system applicable to the present disclosure.
[0026] FIG. 5 is a diagram illustrating a case where service continuity is not guaranteed due to a lack of slice resources applicable to the present disclosure.
[0027] FIG. 6 illustrates an example of a NAS message processing procedure according to an embodiment of the present disclosure.
[0028] FIG. 7 illustrates an example of a specific procedure for processing NAS messages based on specified conditions according to one embodiment of the present disclosure.
[0029] FIG. 8 illustrates an example of a procedure for processing NAS messages by lower layer reporting according to one embodiment of the present disclosure.
[0030] FIG. 9 illustrates an example of a specific procedure for processing a NAS message based on an alternative S-NSSAI according to one embodiment of the present disclosure.
[0031] The following embodiments combine components and features of the present disclosure in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, some components and / or features may be combined to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
[0032] In the description of the drawings, procedures or steps that may obscure the gist of the present disclosure are not described, and procedures or steps that can be understood by a person skilled in the art are also not described.
[0033] Throughout the specification, when a part is said to "comprising" or "including" a component, this does not mean that other components may be included, but rather that other components may be excluded, unless otherwise specifically stated. In addition, terms such as "...part," "...unit," and "module" described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software. In addition, the words "a" or "an," "one," "the," and similar related words may be used in the context of describing the present disclosure (especially in the context of the claims below) to include both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context.
[0034] Embodiments of the present disclosure described herein focus on the data transmission and reception relationship between a base station and a mobile station. Here, the base station is understood as a terminal node of a network that directly communicates with the mobile station. Certain operations described herein as being performed by the base station may, in some cases, be performed by an upper node of the base station.
[0035] That is, in a network consisting of multiple network nodes including a base station, various operations performed for communication with a mobile station may be performed by the base station or other network nodes other than the base station. In this case, the term 'base station' may be replaced by terms such as fixed station, Node B, eNB (eNode B), gNB (gNode B), ng-eNB, advanced base station (ABS), or access point.
[0036] Additionally, in embodiments of the present disclosure, the term terminal may be replaced with terms such as user equipment (UE), mobile station (MS), subscriber station (SS), mobile subscriber station (MSS), mobile terminal, or advanced mobile station (AMS).
[0037] Additionally, a transmitter refers to a fixed and / or mobile node that provides data or voice services, and a receiver refers to a fixed and / or mobile node that receives data or voice services. Therefore, for uplink, a mobile station can be the transmitter, and a base station can be the receiver. Similarly, for downlink, a mobile station can be the receiver, and a base station can be the transmitter.
[0038] Embodiments of the present disclosure are wireless access systems such as IEEE 802.xx system, 3rd Generation Partnership Project (3GPP) system, 3GPP Long Term Evolution (LTE) system, 3GPP 5G (5 th generation) NR (New Radio) system and 3GPP2 system, and in particular, embodiments of the present disclosure may be supported by 3GPP TS (technical specification) 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321 and 3GPP TS 38.331 documents.
[0039] Furthermore, the embodiments of the present disclosure can be applied to other wireless access systems and are not limited to the aforementioned systems. For example, they can also be applied to systems implemented after the 3GPP 5G NR system, and are not limited to a specific system.
[0040] That is, obvious steps or parts not described in the embodiments of the present disclosure can be explained by referring to the above documents. In addition, all terms disclosed in this document can be explained by the above standard documents.
[0041] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the technical configurations of the present disclosure may be implemented.
[0042] Additionally, specific terms used in the embodiments of the present disclosure are provided to aid in understanding the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.
[0043] The following technology can be applied to various wireless access systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access).
[0044] For clarity, the following description is based on a 3GPP communication system (e.g., LTE, NR, etc.), but the technical spirit of the present invention is not limited thereto. LTE may refer to technology after 3GPP TS 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 may be referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 may be referred to as LTE-A pro. 3GPP NR may refer to technology after TS 38.xxx Release 15. 3GPP 6G may refer to technology after TS Release 17 and / or Release 18. "xxx" refers to a standard document detail number. LTE / NR / 6G may be collectively referred to as a 3GPP system.
[0045] For background information, terms, abbreviations, etc. used in this disclosure, reference may be made to standard documents published prior to the present invention. For example, reference may be made to the 36.xxx and 38.xxx standard documents.
[0046] For terms, abbreviations, and other background technologies that may be used in this document, please refer to the following standard documents published prior to this document. In particular, terms, abbreviations, and other background technologies related to LTE / EPS (Evolved Packet System) can refer to the 36.xxx series, 23.xxx series, and 24.xxx series, and terms, abbreviations, and other background technologies related to NR (new radio) / 5GS (5G system) can refer to the 38.xxx series, 23.xxx series, and 24.xxx series.
[0047] Hereinafter, this specification is described based on the terms defined above.
[0048] The three key requirement areas for 5G include (1) Enhanced Mobile Broadband (eMBB), (2) Massive Machine Type Communication (mMTC), and (3) Ultra-reliable and Low Latency Communications (URLLC).
[0049] Some use cases may require optimization across multiple domains, while others may focus on just one Key Performance Indicator (KPI). 5G supports these diverse use cases in a flexible and reliable manner.
[0050] Communication system applicable to the present disclosure
[0051] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present disclosure disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.
[0052] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.
[0053] Figure 1 illustrates an example of a communication system applied to the present disclosure.
[0054] Referring to FIG. 1, a communication system (100) applied to the present disclosure includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR, LTE) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (extended reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI (artificial intelligence) device / server (100g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicles (100b-1, 100b-2) may include unmanned aerial vehicles (UAVs) (e.g., drones). The XR devices (100c) include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. The portable devices (100d) may include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.), etc. The home appliances (100e) may include TVs, refrigerators, washing machines, etc. The IoT devices (100f) may include sensors, smart meters, etc. For example, the base station (120) and the network (130) may also be implemented as wireless devices, and a specific wireless device (120a) may act as a base station / network node to other wireless devices.
[0055] Wireless devices (100a to 100f) can be connected to a network (130) via a base station (120). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (100g) via a network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (120) / network (130), but can also communicate directly (e.g., sidelink communication) without going through the base station (120) / network (130). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). In addition, IoT devices (100f) (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).
[0056] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) / base stations (120), and base stations (120) / base stations (120). Here, the wireless communication / connection can be established through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and base station-to-base station communication (150c) (e.g., relay, IAB (integrated access backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless device and base station / wireless device, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, the wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present disclosure, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.
[0057] Figure 2 illustrates an example of a UE applicable to the present disclosure.
[0058] Referring to FIG. 2, the UE (200) may include a processor (202), memory (204), a transceiver (206), one or more antennas (208), a power management module (241), a battery (242), a display (243), a keypad (244), a SIM (Subscriber Identification Module) card (245), a speaker (246), and a microphone (247).
[0059] The processor (202) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein. The processor (202) may be configured to control one or more other components of the UE (200) to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (202). The processor (202) may include an ASIC, other chipset, logic circuit, and / or data processing device. The processor (202) may be an application processor. The processor (202) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator).
[0060] Memory (204) is operatively coupled to the processor (202) and can store various information for operating the processor (202). Memory (204) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (204) and executed by the processor (202). Memory (204) may be implemented within the processor (202) or external to the processor (202), in which case it may be communicatively coupled to the processor (202) via various methods known in the art.
[0061] A transceiver (206) is operably coupled to the processor (202) and is capable of transmitting and / or receiving wireless signals. The transceiver (206) may include a transmitter and a receiver. The transceiver (206) may include baseband circuitry for processing radio frequency signals. The transceiver (206) may control one or more antennas (208) to transmit and / or receive wireless signals.
[0062] The power management module (241) can manage the power of the processor (202) and / or the transceiver (206). The battery (242) can supply power to the power management module (241).
[0063] The display (243) can output the results processed by the processor (202). The keypad (244) can receive input to be used by the processor (202). The keypad (244) can be displayed on the display (243).
[0064] A SIM card (245) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and can be used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.
[0065] The speaker (246) can output sound-related results processed by the processor (202). The microphone (247) can receive sound-related input to be used by the processor (202).
[0066] In implementations of this specification, a UE may operate as a transmitter in the uplink and as a receiver in the downlink. In implementations of this specification, a base station may operate as a receiver in the uplink and as a transmitter in the downlink. In this specification, a base station may be referred to as a Node B (Node B), an eNode B (eNB), or a gNB, and may not be limited to a specific form.
[0067] In addition, for example, the UE may be implemented in various forms depending on the use case / service. The UE may be composed of various components, devices / parts, and / or modules. For example, each UE may include a communication device, a control device, a memory device, and additional components. The communication device may include a communication circuit and a transceiver. For example, the communication circuit may include one or more processors and / or one or more memories. For example, the transceiver may include one or more transceivers and / or one or more antennas. The control device is electrically connected to the communication device, the memory device, and the additional components, and may control the overall operation of each UE. For example, the control device may control the electrical / mechanical operation of each UE based on a program / code / command / information stored in the memory device. The control device may transmit information stored in the memory device to an external device (e.g., another communication device) via the communication device via a wireless / wired interface, or may store information received from an external device (e.g., another communication device) via the communication device via a wireless / wired interface in the memory device.
[0068] Additional components may be configured in various ways depending on the type of UE. For example, the additional components may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. In addition, the UE is not limited thereto, and may be implemented in the form of a robot (100a in FIG. 1), a vehicle (100b-1 and 100b-2 in FIG. 1), an XR device (100c in FIG. 1), a portable device (100d in FIG. 1), a home appliance (100e in FIG. 1), an IoT device (100f in FIG. 1), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (100g in FIG. 1), a base station (120 in FIG. 1), or a network node. UE can be used in mobile or fixed locations depending on the use case / service.
[0069] The various components, devices / parts, and / or modules of the UE may all be connected to each other via a wired interface, or at least some of them may be connected wirelessly via a communication device. In addition, each component, device / part, and / or module of the UE may further include one or more elements. For example, the control device may be configured by a set of one or more processors. For example, the control device may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory device may be configured by a random access memory (RAM), a dynamic random access memory (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.
[0070] 5G system architecture applicable to the present disclosure
[0071] The 5G system is an advanced technology from the 4th generation LTE mobile communication technology. It supports new radio access technology (RAT: Radio Access Technology), extended LTE (eLTE) as an extended technology of LTE (Long Term Evolution), and non-3GPP (e.g., WLAN) access through the evolution or clean-state structure of the existing mobile communication network structure.
[0072] 5G systems are defined as service-based, and the interactions between network functions (NFs) within the architecture for 5G systems can be expressed in two ways as follows.
[0073] - Reference point representation: Represents the interaction between NF services within NFs described by a point-to-point reference point (e.g., N11) between two NFs (e.g., AMF and SMF).
[0074] Service-based representation: Network functions (e.g., AMF) within the control plane (CP) allow other authorized network functions to access their services. This representation also includes point-to-point reference points, if necessary.
[0075] 5GC (5G Core) can include various components, some of which include access and mobility management function (AMF), session management function (SMF), policy control function (PCF), user plane function (UPF), application function (AF), unified data management (UDM), and non-3GPP interworking function (N3IWF).
[0076] The UE connects to the data network via the UPF via the next-generation radio access network (NG-RAN) that includes the gNB. The UE can receive data services via untrusted non-3GPP access points, such as wireless local area networks (WLANs). To connect non-3GPP access points to the core network, an N3IWF may be deployed.
[0077] The N3IWF manages interworking between non-3GPP access and 5G systems. When a UE is connected to a non-3GPP access (e.g., WiFi, also known as IEEE 802.11), it can connect to a 5G system via the N3IWF. The N3IWF performs control signaling with the AMF and connects to the UPF via the N3 interface for data transmission.
[0078] AMF can manage access and mobility in 5G systems. It can also manage non-access stratum (NAS) security. It can also handle mobility in idle states.
[0079] The UPF functions as a gateway for transmitting and receiving user data. A UPF node can perform all or part of the user plane functions of a 4G mobile communications S-GW (serving gateway) and P-GW (packet data network gateway).
[0080] The UPF acts as a boundary point between the next generation RAN (NG-RAN) and the core network, and is an element that maintains the data path between the gNB and the SMF. In addition, the UPF acts as a mobility anchor point when the UE moves across the area served by the gNB. The UPF can perform the function of handling PDUs. For mobility within the NG-RAN (e.g., NG-RAN defined after 3GPP Release-15), the UPF can route packets. In addition, the UPF can also act as an anchor point for mobility with other 3GPP networks (e.g., RAN defined before 3GPP Release-15), such as UTRAN (UMTS (universal mobile telecommunications system) terrestrial radio access network), E-UTRAN (evolved-UTRAN), or GERAN (GSM (global system for mobile communication) / EDGE (enhanced data rates for global evolution) radio access network). A UPF may correspond to the termination point of a data interface toward a data network.
[0081] The PCF is a node that controls the operator's policies. The AF is a server that provides various services to UEs. The UDM is a server that manages subscriber information, similar to the HSS (home subscriber server) of 4G mobile communications. The UDM (460) stores and manages subscriber information in a unified data repository (UDR).
[0082] The SMF can perform the function of assigning an IP (Internet protocol) address to the UE. In addition, the SMF can control the PDU (protocol data unit) session.
[0083] For convenience of explanation below, the drawing symbols for AMF, SMF, PCF, UPF, AF, UDM, N3IWF, gNB, or UE may be omitted, and operation may be performed by referring to the matters described in standard documents published prior to this document.
[0084] Figure 3 illustrates an example of functional separation of NG-RAN and 5GC (5th generation core) applicable to the present disclosure.
[0085] Referring to Figure 3, the UE connects to a data network (DN) via a next-generation RAN. The control plane function (CPF) node performs all or part of the functions of the mobility management entity (MME) of 4G mobile communications, and all or part of the control plane functions of the serving gateway (S-GW) and the PDN gateway (P-GW). The CPF node includes the AMF and the SMF.
[0086] The UPF node functions as a gateway through which user data is transmitted and received.
[0087] The authentication server function (AUSF) authenticates and manages UEs. The Network Slice Selection Function (NSSF) is a node for network slicing, as described below.
[0088] The network exposure function (NEF) provides a mechanism to securely expose the services and functions of the 5G core.
[0089] The reference points shown in Fig. 3 are as follows. N1 represents a reference point between the UE and the AMF. N2 represents a reference point between the (R)AN and the AMF. N3 represents a reference point between the (R)AN and the UPF. N4 represents a reference point between the SMF and the UPF. N5 represents a reference point between the PCF and the AF. N6 represents a reference point between the UPF and the DN. N7 represents a reference point between the SMF and the PCF. N8 represents a reference point between the UDM and the AMF. N9 represents a reference point between the UPFs. N10 represents a reference point between the UDM and the SMF. N11 represents a reference point between the AMF and the SMF. N12 represents a reference point between the AMF and the AUSF. N13 represents a reference point between the UDM and the AUSF. N14 represents a reference point between the AMFs. N15 represents a reference point between a PCF and an AMF in a non-roaming scenario, and a reference point between an AMF and a PCF of a visited network in a roaming scenario. N16 represents a reference point between SMFs. N22 represents a reference point between an AMF and an NSSF. N30 represents a reference point between a PCF and an NEF. N33 may represent a reference point between an AF and an NEF, and the entities and interfaces described above may be configured with reference to those described in standard documents published before this document. N58 represents a reference point between an AMF and an NSSAAF. N59 represents a reference point between a UDM and an NSSAAF. N80 represents a reference point between an AMF and an NSACF. N81 represents a reference point between an SMF and an NSACF.
[0090] The radio interface protocol is based on the 3GPP radio access network standard. Horizontally, the radio interface protocol consists of the physical layer, data link layer, and network layer. Vertically, it is divided into the user plane for data information transmission and the control plane for control signaling.
[0091] Protocol layers can be divided into L1 (layer-1), L2 (layer-2), and L3 (layer-3) based on the three lower layers of the open systems interconnection (OSI) standard model, which is widely known in communication systems.
[0092] Below, the present disclosure describes each layer of the wireless protocol. Figure 4 illustrates an example of a general architecture of a 5G (5th generation) system applicable to the present disclosure.
[0093] Referring to FIG. 4, the AS (access stratum) layer may include a physical (PHY) layer, a medium access control layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a radio resource control (RRC) layer, and operations based on each layer may be performed by referring to matters described in standard documents published prior to this document.
[0094] Specific embodiments of the present disclosure
[0095] The present disclosure relates to a device and method for processing a non-access stratum (NAS) message in a wireless communication system. Specifically, the present disclosure relates to a device and method for processing an uplink (UL) NAS transport message based on whether a terminal supports partial network slices and / or network slice replacement when transmission of the NAS transport message fails due to a change in a tracking area identifier (TAI). The NAS transport message may be referred to as a UL NAS transport message or another term having a corresponding technical meaning.
[0096] Referring to 3GPP TR 23.700-41, research is being conducted on ways to improve the network slice architecture to address the problems inherent in the network slice architecture. Specifically, various scenarios are being discussed, such as when a network slice or network slice instance does not meet the requirements of a PDU session or application, when a service has a service area that does not overlap with an already deployed tracking area (TA) in a deployment scenario, or when a service is maintained for only a certain period of time, etc., whether these scenarios can be resolved with the current network slice architecture or whether new solutions are needed.
[0097] [Table 1] is the research scope that this disclosure focuses on among the various scopes that should be studied to improve network slicing.
[0098]
[0099] Key issues and their solutions for scopes 1 and 5, as shown in [Table 1], have been discussed. Key issue #1 (KI#1) for scope 1 concerns support for continuity of network slice services, and key issue #5 (KI#5) for scope 5 concerns improved support for RAs that include TAs supporting rejected single network slice selection assistance information (S-NSSAI). As solutions for KI#1 and KI#5, respectively, schemes using alternative S-NSSAI and schemes using partially rejected S-NSSAI and partially accepted S-NSSAI have been proposed.
[0100] Additionally, a change request (CR) related to KI#1, as shown in [Table 2], was approved at the TSG-SA2 #155 meeting. [Table 2] shows the network slice replacement support plan extracted from the CR of S2-2303882.
[0101]
[0102] As shown in [Table 2], AMF receives a notification containing an alternative S-NSSAI from local configuration, PCF, or NSSF, and determines the S-NSSAI to be replaced based on the received notification. At this time, the alternative S-NSSAI is supported within the registration area of the current terminal. AMF provides the alternative S-NSSAI within the allowed network slice selection assistance information (NSSAI) or the configured NSSAI.
[0103] [Table 3] shows the partial network slice support scheme within the registration area extracted from CR of S2-2303809 related to KI#5.
[0104]
[0105] According to [Table 3], when a terminal stores a partially allowed NSSAI, it considers that the terminal is registered with one S-NSSAI among the partially allowed NSSAIs within the entire registration area, and activates user plane resources only within the TA included in the TA list associated with the corresponding S-NSSAI within the partially allowed NSSAI. That is, the terminal allows the initiation of PDU session establishment for the corresponding S-NSSAI only if the terminal is present within the TA area associated with each S-NSSAI. If an established PDU session already exists, the terminal activates user plane resources only if the terminal is present in a TA within the TA list associated with each S-NSSAI. Meanwhile, if the terminal moves to a TA other than a part of the TA list associated with the corresponding S-NSSAI while the user plane resources are already activated, the user plane resources are deactivated, but the PDU session contexts of the terminal and the SMF are not released. User plane resources for a PDU session are not activated while the UE is in a TA within the TA list associated with the S-NSSAI. When the UE stores a partially rejected S-NSSAI in the registration area, the UE initiates a mobility registration update procedure to request registration with the S-NSSAI only if it is in a TA that supports the S-NSSAI.
[0106] [Table 4] is a network slice support scheme extracted from CR of S2-2303869.
[0107]
[0108] Referring to [Table 4], if the deployed TA and the area where network slicing is possible are different, OAM (operations, administration and management) can set whether to support the corresponding network slice based on the cell. The network slice area of service (NS-AoS) of the service is an area in the NG-RAN cell where 0 or more resources are allocated to a network slice, so that the UE can access a specific network slice and receive services. If a cause code and rejection allowing re-registration of the S-NSSAI are received, and the corresponding S-NSSAI is available in the cell where the UE camped, the UE requests the S-NSSAI only if it has received S-NSSAI location availability information. If the corresponding S-NSSAI is a partially allowed NSSAI, and the UE is located in the RA of the cell but outside the area corresponding to the S-NSSAI location availability information, the UE does not activate the user plane of the PDU session of the corresponding S-NSSAI. If the S-NSSAI is a partially allowed NSSAI and the terminal in idle mode moves to a cell outside the area corresponding to the S-NSSAI location availability information, the terminal maintains the PDU session as is.
[0109] In particular, in KI#1, continuity of PDU sessions may not be provided due to overload control in the NG-RAN in inter-RA mobility scenarios or no mobility scenarios. Therefore, handling of PDU sessions in the NG-RAN has been discussed in TR 38.832.
[0110] FIG. 5 is a diagram illustrating a case where service continuity is not guaranteed due to a lack of slice resources applicable to the present disclosure. Referring to FIG. 5, a terminal (510) may attempt a handover from a source RAN node (520) to a target RAN node (530). At this time, although the slice used by the terminal (510) is supported by the target RAN node (530), the target RAN node (530) may not be able to use the slice due to overload. In this case, the terminal (510) may not be able to successfully perform a slice-based handover to the target RAN node (530), which may result in service interruption.
[0111]
[0112] According to the current eNS_Ph3 (enhancement of network slicing phase 3) WID (world inequality database), the terminal does not release the corresponding PDU session even if a congestion situation occurs. That is, when a congestion situation currently occurs, the terminal transmits the PDU session through another available S-NSSAI instead of the S-NSSAI that caused the congestion, and when the congestion situation is resolved, the PDU session is transmitted through the previously used S-NSSAI, thereby transmitting the terminal's user data. This is to ensure service continuity of the PDU session when a congestion situation occurs. To this end, the 3GPP TSG CT (technical specification group core network and terminals) WG (working group) defined an alternative S-NSSAI. The alternative S-NSSAI is configured through the registration procedure and the UE configuration update procedure as described above. Additionally, when establishing a PDU session or modifying a PDU session, the PDU session may be created and / or modified through one of the newly allocated alternative S-NSSAIs, and the user's data may be transmitted through the PDU session.
[0113] Also, referring to eNS_Ph3 WID, a method for processing a specific S-NSSAI even if the specific S-NSSAI is not supported by a specific TA in the TA list within the registration area is proposed. According to the conventional standard, a registration area is defined to facilitate mobility management and paging management of a terminal in AMF, and for this purpose, if the S-NSSAI requested by the terminal supports the TA list of the registration area associated with the S-NSSAI, i.e., all TAs deployed in the registration area, the S-NSSAI is determined to correspond to the registration area. That is, according to the conventional standard, even if the processing of the S-NSSAI is impossible only in the location where the specific TA is deployed among the registration areas, the S-NSSAI is rejected. However, according to KI#5, the registration area is managed based on a partially allowed NSSAI that is possible only in the area of a specific TA or a partially rejected NSSAI that is rejected only in the area of a specific TA among the TA list including TAs within one registration area.
[0114] As mentioned above, new concepts, terminology, or procedures are being studied to address key issues, such as alternative S-NSSAI to address current KI#1, partially accepted NSSAI to address KI#5, and partially rejected S-NSSAI, and new standardization work is underway for these.
[0115] However, there is no discussion on the problems arising from the procedures using the current alternative S-NSSAI, partially accepted NSSAI and / or partially rejected NSSAI, and on the handling of abnormal cases.
[0116] That is, if the TAI of the terminal changes to an unsupported TAI while transmitting a PDU session using an alternative S-NSSAI, or the terminal's cell changes to a cell that does not support the service, and the PDU session cannot be processed, a handling method for the ongoing PDU session needs to be discussed. For example, a discussion needs to be made on how to handle the PDU session establishment procedure, the PDU session modification procedure, and the UL / DL NAS transmission procedure for sending and receiving 5GSM (5GS Session Management) messages.
[0117] Accordingly, the present disclosure defines error situations that may occur in procedures related to newly defined alternative S-NSSAI, partially accepted NSSAI, and partially rejected NSSAI, and proposes a method to resolve them.
[0118] Specifically, the present disclosure proposes a method for processing a UL NAS transmission message when transmission of a UL NAS transmission message fails due to a change in a TA of a terminal that belongs to a registration area but does not support S-NSSAI. In this case, S-NSSAI refers to an S-NSSAI included in the UL NAS transmission message or an S-NSSAI related to the UL NAS transmission message. In other words, when a terminal transmits a UL NAS transmission message to a network, if the terminal moves out of the registration area and into a new TA, the transmission of the UL NAS transmission message may fail. In this case, the existing terminal decides whether to abort the NAS transmission procedure initiated by the terminal or re-execute the ongoing NAS transmission procedure based solely on whether the new TA belongs to the registration area. For example, if the TAI of the new TA is included in the TAI list of the registration area, the existing terminal re-executes the ongoing procedure that triggered the NAS transmission procedure initiated by the terminal, depending on the implementation of the terminal. On the other hand, if the TAI of the new TA is not included in the TAI list of the registration area, the existing terminal stops the NAS transmission procedure and initiates the registration procedure and periodic registration update for mobility.
[0119] However, the terminal of the present disclosure does not determine processing for the NAS transmission procedure based solely on the registration area, but determines processing for the NAS transmission procedure by further considering whether the new TA supports S-NSSAI and at least one of the reports of lower layers related to S-NSSAI. For example, if the new TA is a TA that does not support S-NSSAI related to the UL NAS transmission message whose transmission has failed, the terminal stops processing the UL NAS transmission message. In another example, if the AS layer notifies the NAS layer that the new cell cannot process S-NSSAI related to the UL NAS transmission message, the terminal stops processing the UL NAS transmission message. At this time, the terminal may report the transmission failure of the UL NAS transmission message and the cause of the transmission failure to the network.
[0120]
[0121] Figure 6 illustrates an example of a NAS message processing procedure according to an embodiment of the present disclosure. Figure 6 illustrates a method performed by a terminal.
[0122] Referring to FIG. 6, in step S601, the terminal initiates an NAS transmission procedure. The terminal initiates the NAS transmission procedure to transmit a single 5GSM message, a short message service (SMS), an LTE positioning protocol (LPP) message, a sidelink positioning protocol (SLPP) message, a steering of roaming (SOR) transparent container, a UE policy container, a terminal parameter update transparent container, a location service message, a cellular internet of things (CIoT) user data container, a service-level-AA (SLA) container, or a user plane positioning connection management information (UPP-CMI) container. According to one embodiment, the terminal may initiate the NAS transmission procedure by transmitting an UL NAS transmission message to the AMF in a connected mode. The terminal may transmit control plane user data to the network using the UL NAS transmission message.
[0123] In step S603, the terminal detects a failure in transmitting a NAS transmission message due to a TAI change. In other words, the terminal detects that transmission of a UL NAS transmission message has failed due to the terminal's current TA changing to a new TA.
[0124] In step S605, the terminal compares the changed TAI with the TAI list. That is, the terminal compares the changed TAI with the TAI list indicating the TAs within the terminal's registration area. In other words, by comparing the changed TAI with the TAI list, the terminal determines whether the changed TAI exists within the TAI list.
[0125] In step S607, the terminal determines whether to abort the NAS transmission procedure. In other words, the terminal determines whether to abort the NAS transmission procedure based on whether a changed TAI exists in the TAI list. If the changed TAI does not exist in the TAI list, the terminal may decide to abort the NAS transmission procedure. On the other hand, if the changed TAI exists in the TAI list, the terminal may additionally decide to abort or re-execute the UL NAS transmission procedure based on whether the aforementioned conditions are satisfied. According to one embodiment, the terminal may further consider at least one of whether the new TA supports S-NSSAI and a report from a lower layer related to S-NSSAI to determine processing of the NAS transmission procedure.
[0126]
[0127] In the present disclosure below, specific embodiments of how a terminal processes a UL NAS transmission message when transmission of the UL NAS transmission message fails are described.
[0128] Example 1
[0129] If transmission of a UL NAS transport message fails due to a change in the TAI of the terminal, the terminal determines whether the changed current TAI is included in the TAI list indicating TAIs in the registration area of the terminal, and additionally considers whether the following conditions are satisfied to suspend or restart processing of the UL NAS transport message.
[0130] Condition 1: If the UE supports partial network slices.
[0131] Condition 2: If the S-NSSAI included in the UL NAS transmission message is included in the partially accepted S-NSSAI or the partially rejected S-NSSAI.
[0132] Condition 3: If the current TAI is not in the list of TAs that support the S-NSSAI included in the UL NAS transport message.
[0133] If the conditions described above are satisfied, the terminal determines that it cannot process the UL NAS transmission message in the current TAI and stops processing the UL NAS transmission message.
[0134] FIG. 7 illustrates a specific procedure for processing NAS messages based on specified conditions according to one embodiment of the present disclosure. FIG. 7 illustrates a method performed by a terminal. At least some of the operations in FIG. 7 can be understood as specific embodiments of steps S603, S605, and S607 of FIG. 6.
[0135] Referring to FIG. 7, at step S701, the terminal determines that a transmission failure of a NAS transmission message has occurred. In other words, the terminal detects a transmission failure of a UL NAS transmission message due to a change in the current TAI.
[0136] In step S703, the terminal checks whether the current TAI is included in the TAI list. The TAI list includes TAIs corresponding to TAs included in the terminal's registration area, and the current TAI may be a TAI corresponding to a TA that has changed due to the terminal's movement.
[0137] If the current TAI is not included in the TAI list, in step S717, the terminal aborts the NAS transport procedure and initiates the registration procedure and periodic registration update. That is, the terminal may abort the UE-initiated NAS transport procedure and initiate the registration procedure and periodic registration update for mobility. The UL NAS transport message may be transmitted as needed after the procedures for mobility and periodic registration update are successfully completed.
[0138] If the current TAI is included in the TAI list, in step S705, the terminal determines whether it supports partial network slicing. For example, the terminal can determine whether it supports partial network slicing based on preset capability information.
[0139] If the terminal supports partial network slicing, in step S707, the terminal checks whether the S-NSSAI is included in the partially allowed NSSAI or the partially rejected NSSAI. That is, the terminal checks whether the S-NSSAI included in the UL NAS transmission message is included in the partially allowed NSSAI or the partially rejected NSSAI. According to one embodiment, the partially allowed NSSAI or the partially rejected NSSAI can be obtained through a registration accept message or a UE configuration update command message received from the network.
[0140] If the terminal does not support partial network slicing, or if the terminal supports partial network slicing but the S-NSSAI is not included in the partially allowed NSSAI or partially rejected NSSAI, the terminal re-executes the NAS transmission procedure at step S709. For example, the terminal may re-execute an ongoing procedure, i.e., an ongoing procedure that triggered the NAS transmission procedure initiated by the terminal. In this case, the method for re-executing the ongoing procedure may be determined depending on the implementation of the terminal.
[0141] If the terminal supports partial network slicing and the S-NSSAI is included in the partially allowed NSSAI or partially rejected NSSAI, in step S711, the terminal checks whether the current TAI is included in the list of TAIs supporting S-NSSAI. The list of TAIs supporting S-NSSAI may include TAIs supporting S-NSSAI included in the UL NAS transport message.
[0142] If the current TAI is included in the list of TAIs supporting S-NSSAI, the terminal re-executes the NAS transmission procedure at step S713. For example, the terminal may re-execute an ongoing procedure, i.e., a procedure that triggered the NAS transmission procedure initiated by the terminal. The method for re-executing the ongoing procedure may be determined by the terminal implementation.
[0143] If the current TAI is not included in the list of TAIs supporting S-NSSAI, the terminal aborts the NAS transmission procedure at step S715. At this time, the terminal does not initiate the registration procedure or periodic registration update. In other words, the terminal can abort the NAS transmission procedure initiated by the terminal and control the initiation of the registration procedure and periodic registration update for mobility.
[0144] The processing procedure for the NAS transmission procedure of the terminal described with reference to Fig. 7 can be defined as in [Table 5].
[0145]
[0146]
[0147] Example 2
[0148] The terminal detects that the transmission of the UL NAS transport message has failed due to a lower layer report and aborts the UL NAS transport procedure. Specifically, if the transmission of the NAS transport message has failed due to or regardless of a TA change, the NAS layer of the terminal can obtain a report related to S-NSSAI from the AS layer. The report related to S-NSSAI can indicate the cause of the failure in the transmission of the UL NAS transport message. In other words, the AS layer of the terminal can transmit information to the NAS layer indicating that the changed cell is a cell that does not support S-NSSAI included in the UL NAS transport message. At this time, the NAS layer of the terminal can determine that the ongoing procedure cannot be continued through the changed cell and abort the UL NAS transport procedure. Thereafter, the terminal can report the cause of the failure in the transmission of the UL NAS transport message to the network.
[0149] Figure 8 illustrates an example of a procedure for processing NAS messages by lower layer reporting according to one embodiment of the present disclosure. Figure 8 illustrates a method performed by a terminal.
[0150] Referring to FIG. 8, in step S801, the terminal initiates an NAS transmission procedure. The terminal initiates the NAS transmission procedure to transmit a single 5GSM message, a short message service (SMS), an LTE positioning protocol (LPP) message, a sidelink positioning protocol (SLPP) message, a steering of roaming (SOR) transparent container, a UE policy container, a terminal parameter update transparent container, a location service message, a cellular internet of things (CIoT) user data container, a service-level-AA (SLA) container, or a user plane positioning connection management information (UPP-CMI) container. According to one embodiment, the terminal may initiate the NAS transmission procedure by transmitting an UL NAS transmission message to the AMF in a connected mode. The terminal may transmit control plane user data to the network using the UL NAS transmission message.
[0151] In step S803, the terminal detects a transmission failure of the NAS transmission message by the lower layer. In other words, the NAS layer of the terminal can obtain information indicating the cause of the transmission failure of the UL NAS transmission message from the lower layer, the AS layer, and detect the transmission failure for the NAS transmission based on the obtained information. The information indicating the cause of the transmission failure of the UL NAS transmission message can indicate that the changed cell, i.e., the current serving cell, does not support the S-NSSAI included in the UL NAS transmission message.
[0152] At step S805, the terminal aborts the NAS transmission procedure. In other words, the terminal may abort the processing of the NAS transmission procedure initiated by the terminal. That is, the terminal may determine that the ongoing procedure, i.e., the procedure that triggered the NAS transmission procedure, cannot proceed through the current serving cell and may abort the NAS transmission procedure.
[0153] In step S807, the terminal reports the cause of the transmission failure to the network. That is, the terminal can report the cause of the failure in transmission of the UL NAS transmission message to the network. For example, the terminal can report that the transmission of the UL NAS transmission message containing the S-NSSAI failed because the changed cell does not support the S-NSSAI included in the UL NAS transmission message.
[0154] The processing procedure for the NAS transmission procedure of the terminal described with reference to Fig. 8 can be defined as in [Table 6].
[0155]
[0156]
[0157] Example 3
[0158] If transmission of a UL NAS transport message fails due to a TAI change, the terminal suspends or re-executes processing of the UL NAS transport message based on whether the S-NSSAI included in the UL NAS transport message is included in the IE of an alternative NSSAI for PDU session continuity and whether the changed TAI supports the alternative S-NSSAI. For example, if the S-NSSAI included in the UL NAS transport message is included in the IE of an alternative NSSAI for PDU session continuity and the changed TAI does not support the alternative S-NSSAI, which is the S-NSSAI included in the UL NAS transport message, the terminal may determine that the ongoing procedure cannot be continued and may suspend the UL NAS transport procedure.
[0159] FIG. 9 illustrates an example of a specific procedure for processing a NAS message based on an alternative S-NSSAI according to one embodiment of the present disclosure. FIG. 9 illustrates a method performed by a terminal.
[0160] Referring to FIG. 9, at step S901, the terminal determines that the NAS transmission message has failed to be transmitted. In other words, the terminal detects that the UL NAS transmission message has failed to be transmitted due to a change in the current TAI.
[0161] In step S903, the terminal checks whether the current TAI is included in the TAI list. The TAI list includes TAIs corresponding to TAs included in the terminal's registration area, and the current TAI may be a TAI corresponding to a TA that has changed due to the terminal's movement.
[0162] If the current TAI is not included in the TAI list, in step S913, the terminal aborts the NAS transmission procedure and initiates the registration procedure and periodic registration update. That is, the terminal may abort the NAS transmission procedure initiated by the terminal and initiate the registration procedure and periodic registration update for mobility. The UL NAS transmission message may be transmitted as needed after the procedures for mobility and periodic registration update are successfully completed.
[0163] If the current TAI is included in the TAI list, in step S905, the UE checks whether the S-NSSAI is included in the replacement NSSAI IE. The S-NSSAI refers to the S-NSSAI included in the UL NAS transmission message whose transmission failed or the S-NSSAI related to the UL NAS transmission message whose transmission failed. In other words, the UE checks whether the UL NAS transmission message whose transmission failed includes the replacement S-NSSAI. Here, the NSSAI IE can be configured through the previously performed registration procedure and / or the UE configuration update procedure.
[0164] If the S-NSSAI is not included in the replacement NSSAI IE, then in step S911, the terminal re-executes the NAS transmission procedure. In other words, if the replacement S-NSSAI is not included in the UL NAS transmission message whose transmission failed, the terminal may re-execute the ongoing procedure, i.e., the ongoing procedure that triggered the NAS transmission procedure initiated by the terminal, depending on the implementation of the terminal.
[0165] If S-NSSAI is included in the replacement NSSAI IE, at step S907, the terminal determines whether the changed TAI supports the replacement S-NSSAI. The terminal can determine whether the changed TAI supports the replacement S-NSSAI by checking whether the changed TA is included in the TA list indicating TAs that support the replacement S-NSSAI. If the changed TA is included in the TA list indicating TAs that support the replacement S-NSSAI, the terminal determines that the changed TAI supports the replacement S-NSSAI. On the other hand, if the changed TA is not included in the TA list indicating TAs that support the replacement S-NSSAI, the terminal determines that the changed TAI does not support the replacement S-NSSAI.
[0166] If the changed TAI supports the alternative S-NSSAI, the terminal re-executes the NAS transmission procedure at step S911. For example, the terminal may re-execute an ongoing procedure, i.e., a NAS transmission procedure initiated by the terminal that triggered the procedure. The method for re-executing the ongoing procedure may be determined by the terminal implementation.
[0167] If the changed TAI does not support the alternative S-NSSAI, the terminal aborts the NAS transmission procedure at step S909. At this time, the terminal does not initiate the registration procedure and periodic registration updates. In other words, the terminal can abort the NAS transmission procedure initiated by the terminal and control the initiation of the registration procedure and periodic registration updates for mobility.
[0168]
[0169] The processing procedure for the NAS transmission procedure of the terminal described with reference to Fig. 9 can be defined as in [Table 7].
[0170]
[0171]
[0172] As described above, the terminal determines whether to abort the NSA transmission procedure by additionally considering whether the TA of the changed TAI supports the S-NSSAI included in the UL NAS transmission message and at least one report related to the S-NSSAI obtained from the lower layer. This can minimize errors that occur when a terminal supporting partial network slices fails to transmit a NAS transmission message.
[0173] It is clear that the examples of the proposed methods described above can also be considered as a type of proposed methods, as they can be included as one of the implementation methods of the present disclosure. Furthermore, the proposed methods described above can be implemented independently, but they can also be implemented in the form of a combination (or merge) of some of the proposed methods. Information regarding the applicability of the proposed methods (or information regarding the rules of the proposed methods) can be defined by a rule such that the base station notifies the terminal of the application of the proposed methods through a predefined signal (e.g., a physical layer signal or a higher layer signal).
[0174] The present disclosure may be embodied in other specific forms without departing from the technical ideas and essential features described herein. Therefore, the above detailed description should not be construed as limiting in all respects but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are intended to be included within the scope of the present disclosure. Furthermore, claims that do not explicitly cite each other in the claims may be combined to form embodiments or incorporated into new claims through post-filing amendments.
[0175] Embodiments of the present disclosure can be applied to various wireless access systems. Examples of various wireless access systems include the 3rd Generation Partnership Project (3GPP) or 3GPP2 systems.
[0176] The embodiments of the present disclosure can be applied not only to the various wireless access systems described above, but also to all technical fields that utilize these various wireless access systems. Furthermore, the proposed method can also be applied to mmWave and THz communication systems utilizing ultra-high frequency bands.
[0177] Additionally, embodiments of the present disclosure can be applied to various applications such as autonomous vehicles and drones.
Claims
1. In a method performed by a terminal in a wireless communication system, A step for initiating a NAS (non-access stratum) transport procedure; A step for detecting a transmission failure of an UL (uplink) NAS transmission message due to a change in a TAI (tracking area identifier); Step of comparing the changed TAI with the TAI list; and A step of determining whether to stop the NAS transmission procedure based on the comparison result is included. A method in which whether to stop the NAS transmission procedure is determined based on at least one of whether the TA of the changed TAI supports S-NSSAI (single network slice selection assistance information) included in the UL NAS transmission message and a report related to S-NSSAI obtained from a lower layer of the terminal.
2. In claim 1, A method in which the NAS transmission procedure is interrupted when the changed TAI is included in the TAI list, the terminal supports partial network slicing, the S-NSSAI is included in partially allowed NSSAI or partially denied NSSAI, and the changed TA does not exist in the TA list supporting the S-NSSAI.
3. In claim 2, A method for controlling the initiation of a registration procedure and periodic registration update for mobility with the interruption of the above NAS transmission procedure.
4. In claim 1, The above NAS transmission procedure is a method in which the changed TAI is included in the TAI list and the terminal does not support partial network slices, and is re-executed based on the implementation of the terminal.
5. In claim 1, A method in which the NAS transmission procedure is re-executed based on the implementation of the terminal when the changed TAI is included in the TAI list, the terminal supports partial network slicing, and the S-NSSAI is not included in the partially allowed NSSAI or the partially rejected NSSAI.
6. In claim 1, A method in which the NAS transmission procedure is re-executed based on the implementation of the terminal when the changed TAI is included in the TAI list, the terminal supports partial network slicing, the S-NSSAI is included in a partially allowed NSSAI or a partially denied NSSAI, and the changed TA exists in a TA list supporting the S-NSSAI.
7. In claim 1, The above NAS transmission procedure is aborted when information indicating that the changed cell does not support the S-NSSAI is obtained from the AS layer.
8. In claim 8, A method further comprising the step of reporting that transmission of the UL NAS transmission message has failed due to non-support of the S-NSSAI of the changed cell.
9. In claim 1, A method in which the NAS transmission procedure is interrupted when the changed TAI is included in the TAI list, the S-NSSAI is included in the replacement NSSAI IE, and the TA of the changed TAI does not support the S-NSSAI, which is the replacement NSSAI.
10. In claim 1, A method in which the NAS transmission procedure is re-executed based on the implementation of the terminal when the changed TAI is included in the TAI list, the S-NSSAI is included in the replacement NSSAI IE, and the TA of the changed TAI supports the S-NSSAI, which is the replacement NSSAI.
11. In claim 1, The above NAS transmission procedure is re-executed based on the implementation of the terminal when the changed TAI is included in the TAI list and the S-NSSAI is not included in the replacement NSSAI IE.
12. In claim 1, The above NAS transmission procedure is interrupted if the changed TAI is not included in the TAI list.
13. In a wireless communication system, at a terminal, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Initiate the NAS (non-access stratum) transport procedure, Detects transmission failure of UL (uplink) NAS transmission message due to change of TAI (tracking area identifier), Compare the changed TAI with the TAI list, Based on the comparison results, it is decided whether to stop the NAS transmission process. A terminal in which whether to stop the NAS transmission procedure is further determined based on at least one of whether the TA of the changed TAI supports S-NSSAI (single network slice selection assistance information) included in the UL NAS transmission message and a report related to S-NSSAI obtained from a lower layer of the terminal.
14. In communication devices, At least one processor; At least one computer memory connected to said at least one processor and storing instructions that direct operations when executed by said at least one processor, The above actions are, A step for initiating a NAS (non-access stratum) transport procedure; A step for detecting a transmission failure of an UL (uplink) NAS transmission message due to a change in a TAI (tracking area identifier); Step of comparing the changed TAI with the TAI list; and A step of determining whether to stop the NAS transmission procedure based on the comparison result is included. A communication device in which whether to stop the NAS transmission procedure is determined based on at least one of whether the TA of the changed TAI supports S-NSSAI (single network slice selection assistance information) included in the UL NAS transmission message and a report related to S-NSSAI obtained from a lower layer of the terminal.
15. In a non-transitory computer-readable medium storing at least one instruction, comprising at least one instruction executable by the processor, At least one of the above commands causes the device to: Initiate the NAS (non-access stratum) transport procedure, Detects transmission failure of UL (uplink) NAS transmission message due to change of TAI (tracking area identifier), Compare the changed TAI with the TAI list, Based on the comparison results, it is decided whether to stop the NAS transmission process. A computer-readable medium in which whether to stop the NAS transmission procedure is determined based on at least one of whether the TA of the changed TAI supports S-NSSAI (single network slice selection assistance information) included in the UL NAS transmission message and a report related to S-NSSAI obtained from a lower layer of the terminal.
Citation Information
Patent Citations
Communication method, core network node, and wireless device
US20220279430A1
Method and UE for handling UL NAS transport message failure in wireless communication network
WO2020167041A1
Efficient registration in an area where a slice service is supported partially
WO2022234458A1
Cited By
Non-access stratum protocol header optimization regarding transport failure in mobile communications
WO2026108913A1
