Method and apparatus for blocking control plane data for partially allocated nssai and NS-aos in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Methods and systems are provided in which control plane data is blocked for partially allowed network slice selection assistance information (NSSAI) and network slice service area (NS-AoS) when a user equipment (UE) is in an S-NSSAI unavailable / unsupported area / cell / tracking area (TA). The UE initiates an NAS transmission procedure for a cellular Internet of Things (CIoT) user data container when the UE is in an area / cell / TA that is an S-NSSAI unavailable / supports an NS-AoS area. The UE initiates an NAS transmission procedure for a CIoT user data container when the UE is in an area / cell / TA that is S-NSSAI unavailable / supports an S-NSSAI support area.

Description

Technical Field

[0001] The embodiments disclosed herein generally relate to wireless communication networks, and more specifically, to blocking control plane data for partially enabled NSSAI and Network Slice Service Area (NS-AoS) when a user equipment (UE) is in an area, cell, or tracking area (TA) in which a single Network Slice Selection Assistance Information (NSSAI) (a single NSSAI is S-NSSAI) (e.g., S-NSSAI-A) is unavailable or unsupported. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in the "Sub 6GHz" band, such as 3.5GHz, but also in the "Above 6GHz" band, including 28GHz and 39GHz, known as mmWave. Furthermore, 6G mobile communication technology (referred to as Beyond 5G systems) is being considered in terahertz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] At the outset of the development of 5G mobile communication technology, in order to support services and meet the performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization was underway for the following: beamforming and massive MIMO to mitigate radio wave path loss in millimeter waves and increase radio wave transmission distance; parameter sets supporting dynamic operation for efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings); initial access technologies to support multi-beam transmission and broadband; the definition and operation of BWP (bandwidth portion); new channel coding methods (such as LDPC (low-density parity-check) codes for large data transmissions and polar codes for highly reliable transmission of control information); L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization already exists for the following technologies: such as V2X (Vehicle-to-Everything) for assisting autonomous vehicles in driving decisions based on information about the vehicle's location and status transmitted by the vehicle and for enhancing user convenience; NR-U (New Radio Unlicensed) for system operation aimed at complying with various regulatory requirements in unlicensed frequency bands; NR UE power saving; non-terrestrial networks (NTN) for direct satellite communication between UEs; non-terrestrial networks (NTN) for providing coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] Furthermore, standardization has been ongoing in air interface architecture / protocols for technologies such as: Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries; IAB (Integrated Access and Backhaul) for nodes to provide network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and two-step random access (two-step RACH for NR) to simplify the random access process. Standardization has also been ongoing in system architecture / services for: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and mobile edge computing (MEC) for UE location-based reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices will increase exponentially, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of connected devices. To this end, new research has been organized in conjunction with: Extended Reality (XR) for effectively supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; improving 5G performance and reducing complexity by leveraging Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will serve not only as a foundation for developing new waveforms to provide coverage in the terahertz band of 6G mobile communication technology, such as multi-antenna transmission technologies like full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas to improve the coverage of terahertz band signals; high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum); and RIS (reconfigurable smart surfaces), but also as a foundation for developing full-duplex technologies to improve the frequency efficiency of 6G mobile communication technology and enhance system networks; AI-based communication technologies to achieve system optimization by leveraging satellites and AI (artificial intelligence) from the design phase and internalizing end-to-end AI support capabilities; and next-generation distributed computing technologies to achieve services with complexity levels exceeding the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues This disclosure relates to wireless communication systems, and more specifically, to partially permitted NSSAI and NS-AoS within wireless communication systems.

[0009] Solution to the problem The present invention has been made to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Therefore, one aspect of the invention provides a system and method for blocking control plane data for partially / partially permitted NSSAI and NS-AoS when the UE is in an area / cell / TA in which S-NSSAI (e.g., S-NSSAI-A) is unavailable / unsupported.

[0010] Another aspect of the present invention provides a system and method for managing NAS transmission processes over a network.

[0011] Another aspect of the present invention provides a system and method for enabling a UE to initiate a NAS transmission process for a CIoT user data container when the UE is in a region / cell / TA in which S-NSSAI (e.g., S-NSSAI-A) is unavailable / NS-AoS supported regions.

[0012] Another aspect of the present invention provides a system and method for enabling a UE to initiate a NAS transmission process for a CIoT user data container when the UE is in a region / cell / TA in which S-NSSAI (e.g., S-NSSAI-A) is unavailable or supports an S-NSSAI-supported region.

[0013] Therefore, embodiments provide a method for managing control plane (CP) data for partially permitted NSSAIs and NS-AoS. The UE receives at least one of a partially permitted NSSAI list and NS-AoS information from the network. The partially permitted NSSAI list indicates one or more TAIs that support or do not support at least one S-NSSAI, and the NS-AoS information indicates one or more cells that support or do not support an S-NSSAI. The UE identifies whether a desired S-NSSAI on the current cell and / or current TAI is supported based on at least one of the partially permitted NSSAI list and NS-AoS information. Upon identifying whether a desired S-NSSAI is supported on the current cell or current TAI, the UE determines whether to initiate a UL NAS message to the network, the UL NAS message being used to send CP data to the network via the current cell or current TAI.

[0014] Therefore, embodiments provide a UE including a processor and a memory module. The processor is coupled to the memory module. The processor is configured to receive at least one of a partially allowed NSSAI list and NS-AoS information from the network. The partially allowed NSSAI list indicates one or more TAIs that support or do not support at least one S-NSSAI, and the NS-AoS information indicates one or more cells that support or do not support S-NSSAI. The processor is configured to identify whether a desired S-NSSAI on the current cell and / or the current TAI is supported based on at least one of the partially allowed NSSAI list and the NS-AoS information. The processor is configured to determine whether to initiate a UL NAS message to the network when it is identified whether the desired S-NSSAI on the current cell or the current TAI is supported. The UL NAS message is used to send CP data to the network via the current cell or the current TAI.

[0015] Therefore, this embodiment provides a method for managing CP data for partially permitted NSSAI and NS-AoS. The UE receives at least one of a partially permitted NSSAI list and NS-AoS information from the network. The partially permitted NSSAI list indicates one or more TAIs that support or do not support at least one S-NSSAI, and the NS-AoS information indicates one or more cells that support or do not support S-NSSAI. The UE identifies whether the desired S-NSSAI on the current cell and / or current TAI is supported based on at least one of the partially permitted NSSAI list and NS-AoS information. When it is identified based on at least one of the partially permitted NSSAI list and NS-AoS information that S-NSSAI is not supported / allowed on the current cell or current TAI, the UE prohibits the transmission of a UL NAS message. The UL NAS message is used to transmit CP data to the network via the current cell or current TAI. In response to the UL NAS transmission message indicating that the UE is located on a current cell that does not support S-NSSAI, the UE receives a rejection response from the network indicating that CP data transmission on the current cell is not permitted. When the UE receives a rejection response, it terminates the transmission of CP data for the current cell.

[0016] Therefore, this embodiment provides a method for managing CP data for partially permitted NSSAI and NS-AoS. The UE receives at least one of a partially permitted NSSAI list and NS-AoS information from the network. The UE identifies whether a desired S-NSSAI on the current cell and / or the current TAI is supported based on at least one of the partially permitted NSSAI list and NS-AoS information. When S-NSSAI on the current cell is identified as supported based on the NS-AoS information, the UE initiates a UL NAS message to send CP data to the network through the current cell. When S-NSSAI-A on the current TAI is identified as supported based on the partially permitted NSSAI list, the UE initiates a UL NAS message to send CP data to the network through the current TAI.

[0017] Therefore, this embodiment provides a method for managing CP data for partially permitted NSSAI and NS-AoS. The network sends at least one of a partially permitted NSSAI list and NS-AoS information to the UE. Based on determining, according to at least one of the partially permitted NSSAI list and NS-AoS information, that at least one of the current cell and the current TAI does not support S-NSSAI, the network prohibits sending CP data for at least one S-NSSAI to the UE. When the UE identifies, based on at least one of the partially permitted NSSAI list and NS-AoS information, whether a desired S-NSSAI on the current cell or the current TAI is supported, the network receives a UL NAS message from the UE via the current cell and / or the current TAI. The UL NAS message carries CP data on the current cell or the current TAI.

[0018] Therefore, the embodiment provides a network including a processor and a memory module. The processor is coupled to the memory module. The processor is configured to send at least one of a partially allowed NSSAI list and NS-AoS information to the UE. The processor is configured to prohibit the transmission of at least one S-NSSAI CP data to the UE based on determining, according to at least one of the partially allowed NSSAI list and NS-AoS information, that at least one of the current cell and the current TAI does not support S-NSSAI. The processor is configured to receive a UL NAS message from the UE via the current cell and / or the current TAI when the UE identifies, based on at least one of the partially allowed NSSAI list and NS-AoS information, whether the desired S-NSSAI on the current cell or the current TAI is supported. The UL NAS message carries CP data on the current cell or the current TAI.

[0019] Therefore, embodiments provide a method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving location availability information associated with single network slice selection assistance information (S-NSSAI) from an access management function (AMF) entity, the location availability information indicating at least one cell in a tracking area (TA) in which the S-NSSAI is available; and identifying, based on the location availability information associated with the S-NSSAI, whether the UE is located in at least one cell in a TA in which the S-NSSAI is available; and determining, if the UE's location is outside at least one cell in the TA, not to transmit a non-access stratum (NAS) message for user data.

[0020] Therefore, embodiments provide a method performed by an Access Management Function (AMF) in a wireless communication system, the method comprising: sending to a User Equipment (UE) location information associated with Single Network Slice Selection Assistance Information (S-NSSAI), the location information indicating at least one cell of a Tracking Area (TA), the TA including a first cell supporting S-NSSAI in the TA and a second cell not supporting S-NSSAI in the TA; wherein the location of the UE is identified based on the location information associated with S-NSSAI, and wherein, if the location of the UE is within the second cell, it is determined that a Non-Access Stratum (NAS) message for user data will not be sent.

[0021] Therefore, embodiments provide a user equipment (UE) in a wireless communication system, the UE including: a transceiver; and a controller coupled to the transceiver, the controller being configured to: receive location information associated with Single Network Slice Selection Assist Information (S-NSSAI) from an Access Management Function (AMF) entity, the location information indicating at least one cell of a Tracking Area (TA), the TA including a first cell supporting S-NSSAI in the TA and a second cell not supporting S-NSSAI in the TA; identify the location of the UE based on the location information associated with S-NSSAI; and, if the UE's location is within the second cell, determine not to transmit Non-Access Stratum (NAS) messages for user data.

[0022] Therefore, an embodiment provides an access management function (AMF) in a wireless communication system, the AMF including: a transceiver; and a controller coupled to the transceiver, the controller being configured to: send location information associated with Single Network Slice Selection Assist Information (S-NSSAI) to a user equipment (UE), the location information indicating at least one cell of a tracking area (TA), the TA including a first cell supporting S-NSSAI in the TA and a second cell not supporting S-NSSAI in the TA, wherein the location of the UE is identified based on the location information associated with S-NSSAI, and wherein, if the location of the UE is within the second cell, it is determined that a non-access stratum (NAS) message for user data will not be sent.

[0023] Beneficial effects of the present invention According to embodiments of this disclosure, wireless communication can be effectively implemented. Attached Figure Description

[0024] The above and other aspects, features and advantages of the present invention will become clearer from the following detailed description taken in conjunction with the accompanying drawings.

[0025] Figure 1This diagram illustrates a method by which a UE initiates a NAS transfer procedure for a CIoT user data container when it is in an area (cell / TA) where S-NSSAI is unavailable / unsupported.

[0026] Figure 2 This is a diagram illustrating a system for managing control plane (CP) data for partially permitted NSSAI and NS-AoS, according to an embodiment.

[0027] Figure 3 This is a diagram illustrating multiple modules of a processor for a UE that manages CP data according to an embodiment.

[0028] Figure 4 This is a diagram illustrating a method for managing CP data for partially permitted NSSAI and NS-AoS according to an embodiment.

[0029] Figure 5 This is a diagram illustrating a method for managing CP data for partially permitted NSSAI and NS-AoS when S-NSSAI-A does not support at least one cell, according to an embodiment.

[0030] Figure 6 This is a diagram illustrating a method for managing CP data for partially permitted NSSAI and NS-AoS when S-NSSAI-A does not support at least one cell, according to another embodiment.

[0031] Figure 7 This is a diagram illustrating a method for network-managed CP data for partially permitted NSSAI and NS-AoS, according to an embodiment.

[0032] Figure 8 This is a diagram illustrating a message sequence diagram of a network rejecting a UE NAS transmission with an appropriate rejection reason according to an embodiment.

[0033] Figure 9 This is a diagram illustrating the message sequence diagram of a UE not initiating a NAS transmission procedure for a CIoT user data container when the UE is in an area / cell / TA where S-NSSAI is unavailable / unsupported according to NS-AoS area or S-NSSAI location availability information, according to an embodiment.

[0034] Figure 10 This is a diagram illustrating the message sequence diagram of a UE being allowed to initiate a NAS transmission procedure for a CIoT user data container when the UE is in an area / cell / TA where S-NSSAI is unavailable / unsupported according to NS-AoS area or S-NSSAI location availability information. Detailed Implementation

[0035] Partially permitted NSSAI indicates the S-NSSAI value that a UE can use in a serving Public Land Mobile Network (PLMN) or Independent Non-Public Network (SNPN) within some TAs in the currently registered area. Each S-NSSAI in partially permitted NSSAI is associated with a list of TAs that support the S-NSSAI.

[0036] NS-AoS is an area where a UE can access and receive services from a specific network slice because more than zero resources are allocated to network slices in a Next Generation Radio Access Network (NG-RAN) cell.

[0037] For each applicable S-NSSAI in the configured NSSAI, the S-NSSAI location availability information sent to the UE includes the location information of the cell in the Radio Access RA (RA) indicating the availability of the relevant S-NSSAI (if the S-NSSAI is not available in all cells of the TA).

[0038] The UE-initiated non-access stratum (NAS) transmission process includes sending a cellular Internet of Things (CIoT) user data container. The UE may include a Protocol Data Unit (PDU) session ID and a release assist indicator (if available), set the payload container type information element (IE) to "CIoT user data container", and set the payload container IE to the user data container.

[0039] If the S-NSSAI is in a partially / partially permitted NSSAI list, then if the UE is in a cell within the RA but outside the S-NSSAI's location information, the UE may not activate the user plane for a PDU session already established with that S-NSSAI. When the UE is in a cell within the RA but outside the S-NSSAI's location information, it is uncertain whether the UE can send a UE-initiated NAS transport message to send a CIoT user data container, which does not require user plane resources, and it is unclear what the behavior of network functions (e.g., Access and Mobility Management Function (AMF) and Session Management Function (SMF)) should be.

[0040] Figure 1This diagram illustrates an existing method for a UE to initiate a NAS transfer procedure for a CIoT user data container when the UE is in an area (cell / TA) where S-NSSAI is unavailable / unsupported. As described in step 1, the network does not support / allows S-NSSAI-A across the entire TA or registered area (e.g., TA Identifier Set (TAI)). A network function (e.g., AMF) sends S-NSSAI location availability information or partially allowed NSSAI to the UE, indicating the area, cell, or TAI where S-NSSAI-A is supported / not supported in the TA or registered area (e.g., TAI set).

[0041] In step 2, the UE moves to a new cell / TA where S-NSSAI-A is not supported / allowed according to a partially allowed NSSAI list, S-NSSAI location availability information, or NS-AoS information. In step 3, the UE initiates a NAS transmission message to send the CIoT user data container of the PDU for the S-NSSAI-A PDU session at the Radio Access Network (RAN).

[0042] At step 4, when the UE is in an area (TAI / cell) where the corresponding S-NSSAI is not supported based on the partially / partially allowed NSSAI list or S-NSSAI location availability information, the AMF may accept / reject uplink (UL) NAS transmission messages.

[0043] Therefore, known mobility management signaling messages are permitted, but it is not described whether the UE can use these signaling messages to send control plane data to the network.

[0044] Embodiments of the invention are described in detail with reference to the accompanying drawings. The same or similar components may be denoted by the same or similar reference numerals, although they are shown in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the invention. The examples used herein are intended only to facilitate an understanding of how the embodiments described herein can be practiced, and further to enable those skilled in the art to practice the embodiments described herein. Therefore, the examples should not be construed as limiting the scope of the embodiments described herein.

[0045] For the purposes of interpreting this specification, definitions (as defined herein) will apply, and terms used in the singular will include the plural, and vice versa, where appropriate. It should be understood that the terminology used herein is for the purpose of describing particular embodiments only and not for limitation. Unless otherwise stated, the terms “comprising,” “having,” and “including” should be interpreted as open-ended terms.

[0046] The words / phrases “exemplary,” “example,” “illustration,” “in instance,” “etc.,” “for example,” and “i.e.” are used herein only to mean “served as an example, instance, or illustration.” Any embodiment or implementation of the subject matter described herein using the words / phrases “exemplary,” “example,” “illustration,” “in instance,” “etc.,” “for example,” and “i.e.” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0047] The embodiments described herein can be illustrated and explained according to blocks that perform one or more of the described functions. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., are physically implemented by analog and / or digital circuitry, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and may optionally be driven by firmware. For example, the circuitry may be embodied in one or more semiconductor chips, or on a substrate support such as a printed circuit board. The circuitry constituting a block may be implemented by dedicated hardware or by a processor (e.g., one or more programmed microprocessors and associated circuitry) or by a combination of dedicated hardware performing some functions of the block and a processor performing other functions of the block. Each block of an embodiment may be physically divided into two or more interactive and discrete blocks without departing from the scope of this disclosure. Similarly, the blocks of an embodiment may be physically combined into more complex blocks without departing from the scope of this disclosure.

[0048] It should be noted that the elements in the accompanying drawings are shown for the purposes of this specification and for ease of understanding, and may not necessarily be drawn to scale. For example, flowcharts / sequence diagrams illustrate the method according to the steps required to understand the aspects of the embodiments disclosed herein. Furthermore, regarding the construction of the device, one or more components of the device may already be represented by conventional symbols in the drawings, and the drawings may only show those specific details relevant to understanding the embodiments, so as not to obscure the drawings with details that would be readily apparent to those skilled in the art benefiting from the description herein. Similarly, regarding the system, one or more components / modules constituting the system may already be represented by conventional symbols in the drawings, and the drawings may only show those specific details relevant to understanding the embodiments, so as not to obscure the drawings with details that would be readily apparent to those skilled in the art benefiting from the description herein.

[0049] The accompanying drawings are provided to aid in the easy understanding of the various technical features, and it should be understood that the embodiments presented herein are not limited to the drawings. Therefore, this disclosure should be construed as extending to any modifications, equivalents, and substitutions other than those specifically set forth in the drawings and corresponding descriptions. The use of terms such as first, second, third, etc., to describe components / elements / steps is for the purposes of this specification and should not be construed as a sequential order / placement / occurrence unless otherwise stated.

[0050] The embodiments provide systems and methods for blocking control plane data for partially enabled NSSAI and NS-AoS when the UE is in an area / cell / TA in which S-NSSAI (e.g., S-NSSAI-A) is unavailable / unsupported. Referring now to the accompanying drawings, and more specifically to… Figures 2 to 10 An embodiment is shown, wherein similar reference numerals are consistently used to denote corresponding features throughout the figures.

[0051] Figure 2 This is a diagram illustrating a system for managing CP data for partially permitted NSSAI and NS-AoS according to an embodiment. System 200 includes UE 202 and network 204. UE 202 includes processor 206, communication module 208, and memory module 210.

[0052] In one embodiment, processor 206 is coupled to memory module 210 and configured to manage CP data for at least one cell based on a partially permitted NSSAI list and NS-AoS information. Figure 3 As shown, the processor 206 includes an NSSAI module 302, a NAS management module 304, and a storage module 306.

[0053] In an embodiment, the NSSAI module 302 can receive at least one of a partially allowed NSSAI list and NS-AoS information from network 204. The partially allowed NSSAI list may indicate one or more TAIs that support or do not support at least one S-NSSAI. The NS-AoS information may indicate one or more cells that support or do not support S-NSSAI. In an embodiment, after receiving a rejection response from network 204, the NSSAI module 302 can receive an updated configuration of at least one of the partially allowed NSSAI list and NS-AoS information from network 204 via a downlink (DL) NAS message.

[0054] In this embodiment, the NAS management module 304 can identify whether a desired S-NSSAI (e.g., S-NSSAI-A) on the current cell and / or current TAI is supported based on at least one of a partially allowed NSSAI list and NS-AoS information. After identifying whether S-NSSAI-A is supported for the current cell or current TAI, the NAS management module 304 can decide whether to initiate a UL NAS message to the network 204. The UL NAS message is used to send CP data to the network 204 via the current cell or current TAI.

[0055] In this embodiment, the current TAI is one of the currently camped TAI and the selected TAI. The current cell is one of the currently camped cell and the selected cell.

[0056] In this embodiment, the NAS management module 304 can prohibit / suppress / restrict the transmission of UL NAS messages to network 204 for sending CP data through the current cell or current TAI when it identifies that S-NSSAI-A is not supported. The NAS management module 304 can identify S-NSSAI-A that is not supported on the current cell or current TAI based on at least one of a partially allowed NSSAI list and NS-AoS information. The NAS management module 304 can initiate a UL NAS message to send CP data to network 204 through the current cell when it identifies that S-NSSAI-A is supported on the current cell. The NAS management module 304 can identify S-NSSAI-A supported on the current cell based on NS-AoS information. The NAS management module 304 can initiate a UL NAS message for sending CP data to network 204 through the current TAI when it identifies that S-NSSAI-A is supported on the current TAI. The NAS management module 304 can identify S-NSSAI-A supported on the current TAI based on a partially allowed NSSAI list.

[0057] In this embodiment, the NAS management module 304 can initiate a ULNAS message to send CP data to the network 204 through the current cell when it identifies S-NSSAI-A supported on the current cell based on NS-AoS information and when it identifies S-NSSAI-A not supported on the current TAI based on a partially allowed NSSAI list. The NAS management module 304 can also initiate a UL NAS message to send CP data to the network 204 through the current TAI when it identifies S-NSSAI-A supported on the current TAI based on a partially allowed NSSAI list and when it identifies S-NSSAI-A not supported on the current cell based on NS-AoS information.

[0058] In this embodiment, the NAS management module 304 can, based on NS-AoS identification indicating that S-NSSAI-A is not supported on the current cell, and based on a partially allowed NSSAI list indicating that S-NSSAI-A is supported on the current TAI, prohibit / suppress / restrict UL NAS messages from sending CP data to network 204 through the current cell. The NAS management module 304 can also, based on NS-AoS information, prohibit / suppress / restrict UL NAS messages from sending CP data to network 204 through the current TAI when it identifies that S-NSSAI-A is not supported on the current TAI.

[0059] In this embodiment, the NAS management module 304 can terminate the transmission of CP data for the current cell when it receives a rejection response from the network 204.

[0060] In an embodiment, when a rejection response is received from network 204, storage module 306 can store the current cell as not supporting S-NSSAI-A.

[0061] In this embodiment, network 204 includes a processor and a memory module. The processor is coupled to the memory module. Network 204 may be at least one of Session Management Function (SMF) and AMF. The processor of network 204 may send a partially allowed NSSAI list and NS-AoS information to UE 202. The partially allowed NSSAI list may indicate one or more TAIs that support or do not support at least one S-NSSAI, and the NS-AoS information may indicate one or more cells that support or do not support S-NSSAI. Based on the determination that at least one of the current cell and the current TAI does not support S-NSSAI according to at least one of the partially allowed NSSAI list and NS-AoS information, the processor of network 204 may prohibit the transmission of CP data for at least one S-NSSAI to UE 202 in the Mobile Termination (MT) direction. The processor of network 204 can receive a UL NAS message from UE 202 via the current cell and / or current TAI when UE 202 identifies whether the desired S-NSSAI (e.g., S-NSSAI-A) is supported or not supported on the current cell or current TAI based on at least one of a partially allowed NSSAI list and NS-AoS information. The UL NAS message carries CP data on the current cell or current TAI. The processor of network 204 can send a rejection response to UE 202 indicating that CP data transmission on the current cell is not allowed / supported. The processor of network 204 can send a rejection response in response to an instruction to UE 202 to transmit a UL NAS message on a current cell that does not support S-NSSAI-A. The processor of network 204 can send a DL NAS message to UE 202 to allow UE 202 to transmit CP data on the current cell. After receiving a UL NAS transmission message instructing UE 202 to transmit on the current cell that does not support S-NSSAI-A, the processor of network 204 may send a DL NAS message to UE 202.

[0062] In an embodiment, processor 206 can process and execute data from multiple modules of UE 202. Processor 206 can be configured to execute instructions stored in memory module 210. Processor 206 may include one or more of a microprocessor, circuitry, and other hardware configured for processing. Processor 206 may be at least one of a single processor, multiple processors, multiple homogeneous or heterogeneous cores, multiple central processing units (CPUs) of different types, a microcontroller, special media, and other accelerators. Processor 206 may be an application processor (AP), a graphics processing unit only (e.g., a graphics processing unit (GPU), a visual processing unit (VPU)), and / or an artificial intelligence (AI) dedicated processor (e.g., a neural processing unit (NPU)).

[0063] In this embodiment, multiple modules of the processor 206 of the UE 202 can communicate via the communication module 208. The communication module 208 can be in the form of a wired network or a wireless communication network module. The wireless communication network can include, but is not limited to, Global Positioning System (GPS), Global System for Mobile Communications (GSM), Wi-Fi, Bluetooth Low Energy, Near Field Communication (NFC), etc. Depending on the usage environment, the wireless communication can also include one or more of the following: Bluetooth, ZigBee, short-range wireless communication (e.g., Ultra Wideband (UWB) and medium-range wireless communication (e.g., Wi-Fi) or long-range wireless communication (e.g., 3G / 4G / 5G / 6G and non-3GPP technologies or WiMAX).

[0064] In embodiments, memory module 210 may include one or more volatile and non-volatile memory components capable of storing data and instructions of the module of UE 202 to be executed. Examples of memory module 210 may be, but are not limited to, NAND, embedded multimedia card (eMMC), secure digital card (SD), universal serial bus (USB), serial advanced technology accessory (SATA), and solid-state drive (SSD). Memory module 210 may also include one or more computer-readable storage media. Examples of non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Additionally, in some examples, memory module 210 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be construed as meaning that memory module 210 is non-removable. In some examples, non-transitory storage media may store (e.g., in random access memory (RAM) or cache) data that may change over time.

[0065] Figure 2 Example modules of UE 202 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, UE 202 may include fewer or more modules. Furthermore, the labels or names of modules are for illustrative purposes only and do not limit the scope of the invention. One or more modules may be combined together to perform the same or substantially similar functions in UE 202.

[0066] Figure 4This is a diagram illustrating a method for managing CP data for partially permitted NSSAI and NS-AoS according to an embodiment. Method 400 includes receiving at least one of a partially permitted NSSAI list and NS-AoS information from network 204 by processor 206 of UE 202, as shown at 402. The partially permitted NSSAI list indicates one or more TAIs in which at least one S-NSSAI is supported or not supported, and the NS-AoS information indicates one or more cells in which at least one S-NSSAI is supported or not supported.

[0067] The method includes having the processor 206 of UE 202 identify, based on at least one of a partially allowed NSSAI list and NS-AoS information, whether a desired S-NSSAI (e.g., S-NSSAI-A) is supported on the current cell and / or the current TAI, as shown at 404. Thereafter, method 400 includes, upon identifying whether S-NSSAI-A is supported on the current cell or the current TAI, having the processor 206 of UE 202 decide whether to initiate a UL NAS message to network 204, as shown at 406. The UL NAS message is used to send CP data to network 204 via the current cell or the current TAI.

[0068] The steps of method 400 can be performed in the presented order, in different orders, or simultaneously. Furthermore, steps can be omitted. Figure 4 Method 400 lists some of the steps.

[0069] Figure 5 This is a diagram illustrating a method for managing CP data for partially permitted NSSAI and NS-AoS when S-NSSAI-A does not support at least one cell / TAI, according to an embodiment. Method 500 includes UE 202 receiving at least one of a partially permitted NSSAI list and NS-AoS information from network 204, as shown at 502. The partially permitted NSSAI list may indicate one or more TAIs in which at least one S-NSSAI is supported or not supported, and the NS-AoS information may indicate one or more cells in which at least one S-NSSAI is supported or not supported.

[0070] Method 500 includes UE 202 identifying, based on at least one of a partially allowed NSSAI list and NS-AoS information, whether a desired S-NSSAI (e.g., S-NSSAI-A) is supported on the current cell and / or the current TAI, as shown at 504. Method 500 also includes UE 202 prohibiting the transmission of UL NAS messages when it identifies, based on at least one of the partially allowed NSSAI list and NS-AoS information, that S-NSSAI-A is not supported on the current cell and / or the current TAI, as shown at 506.

[0071] Method 500 includes receiving a rejection response from network 204 by UE 202 in response to a UL NAS transmission message, the rejection response indicating that CP data transmission is not permitted on the current cell, as shown at 508. The UL NAS transmission message indicates that UE 202 is on a current cell that does not support S-NSSAI-A. Method 500 includes UE 202 terminating the transmission of CP data in the current cell upon receiving the rejection response, as shown at 510.

[0072] The steps in method 500 can be performed in the order presented, in a different order, or simultaneously. Furthermore, steps can be omitted. Figure 5 Some steps in Method 500.

[0073] Figure 6 This is a diagram illustrating a method for managing CP data for partially permitted NSSAI and NS-AoS when S-NSSAI-A of at least one cell is not supported, according to another embodiment. Method 600 includes receiving at least one of a partially permitted NSSAI list and NS-AoS information from network 204 by UE 202, as shown at 602. Method 600 includes identifying by UE 202 whether a desired S-NSSAI (e.g., S-NSSAI-A) on the current cell and / or the current TAI is supported based on at least one of the partially permitted NSSAI list and NS-AoS information, as shown at 604.

[0074] Method 600 includes UE 202 initiating a UL NAS message to send CP data to network 204 through the current cell when it identifies S-NSSAI-A support on the current cell based on NS-AoS information, as shown at 606. Method 600 also includes UE 202 initiating a UL NAS message to send CP data to network 204 through the current TAI when it identifies S-NSSAI-A support on the current TAI based on a partially allowed NSSAI list, as shown at 608.

[0075] The steps in method 600 can be performed in the presented order, in a different order, or simultaneously. Furthermore, steps can be omitted. Figure 6 Method 600 lists some of the steps.

[0076] Figure 7 This is a diagram illustrating a method by which network 204 manages CP data for partially permitted NSSAI and NS-AoS according to an embodiment. Method 700 includes network 204 sending at least one of a partially permitted NSSAI list and NS-AoS information to UE 202, as shown at 702. The partially permitted NSSAI list may indicate one or more TAIs that support or do not support at least one S-NSSAI, and the NS-AoS information may indicate one or more cells that support or do not support S-NSSAI. Method 700 includes network 204 determining, based on at least one of the partially permitted NSSAI list and NS-AoS information, that at least one of the current cell and the current TAI does not support S-NSSAI, and prohibiting the transmission of CP data for at least one S-NSSAI to UE 202 in the MT direction, as shown at 704.

[0077] Method 700 includes receiving a UL NAS message from network 204 via the current cell and / or current TAI when UE 202 identifies, based on at least one of a partially permitted NSSAI list and NS-AoS information, whether a desired S-NSSAI (e.g., S-NSSAI-A) is supported or not supported on the current cell or current TAI, as shown at 706. The UL NAS message carries CP data on the current cell or current TAI. Method 700 also includes sending a rejection response from network 204 to UE 202 if the UL NAS transmission message indicates that UE 202 on the current cell does not support S-NSSAI-A, indicating that CP data transmission on the current cell is not permitted, as shown at 708.

[0078] The steps in method 700 can be performed in the presented order, in different orders, or simultaneously. Furthermore, steps can be omitted. Figure 7 Method 700 lists some of the steps.

[0079] Figure 8This is a diagram illustrating a message sequence diagram of a network rejecting UE NAS transmissions with appropriate rejection reasons according to an embodiment. At step 8-2, S-NSSAI-A is not supported in the TA or serving cell at UE 202. A network function (e.g., AMF804) sends S-NSSAI location availability information to the UE, indicating partially allowed or partially rejected NSSAI information, which indicates the area / cell / TAI in which S-NSSAI is supported / not supported within the TA. At step 8-4, UE 202 moves to a new cell / TA in which S-NSSAI-A is not supported according to the partially / partially allowed NSSAI list or NS-AoS information or S-NSSAI location availability information. In steps 8-6, UE 202 initiates a NAS transmission message at RAN 802, described as sending a CIoT user data container. In steps 8-8, a network function (e.g., AMF 804) sends a NAS message (e.g., a downlink (DL) NAS transmission or a NAS message) to UE 202 to send a rejection and includes an appropriate rejection reason indicating that CP data transmission is not permitted in the current TAI / cell. Individual rejection reasons may exist, which helps the UE identify whether the current TAI or cell is not permitted / supported for the desired S-NSSAI. UE 202 may include (store) corresponding TA / cells not supported for that S-NSSAI-A, and UE 202 may not attempt to transmit CP data in the corresponding TAI / cell for that S-NSSAI. However, when UE 202 changes the TAI / cell, UE 202 may attempt to retransmit CP data based on a partially / partially permitted NSSAI list / S-NSSAI location availability information or NS-AoS information.

[0080] Optionally, AMF 804 may assume that UE 202 does not have the correct partially / partially permitted NSSAI list, NS-AoS information, or S-NSSAI location availability information, and therefore update them by sending a DL NAS message (e.g., a UE configuration update message). The UE acts based on the newly received information.

[0081] If the request type IE is set to "Initial Request", "Existing PDU Session", "Modification Request", or "MA PDU Request", optionally, if UE 202 is not configured for high-priority access in the selected PLMN or SNPN, and UE 202 is in a TAI / cell that does not support S-NSSAI-A, AMF 804 may send back to UE 202 a 5GSM message that was not forwarded and a 5GMM reason, such as #28 "Restricted Service Area" or any other reason indicating that area (e.g., TAI / cell) or a separate rejection reason to indicate that S-NSSAI-A does not support TAI or the cell. UE 202 then transmits to the 5GSM sublayer an indication that the 5GSM message was not forwarded because UE 202 is in a TAI / cell that does not support S-NSSAI-A, as well as the 5GSM message from the payload container IE of the DL NAS transmission message. Upon receiving an indication that 5GSM messages will not be forwarded due to disallowed restriction-NSSAI, and a PDU session establishment request / 5GSM message with a PDU session ID IE set to the same value as the PDU session ID sent by UE 202, UE 202 may stop timer T3580 and abort the process.

[0082] Furthermore, UE 202 is restricted from retransmitting requests until it moves to an area / cell / TAI that supports S-NSSAI, or outside the current cell or TAI. If the rejection reason indicates that the TAI is not supported, the UE stores this information and will not attempt to transmit a NAS message with CP data on that TAI when the UE moves out of that TAI, but the UE may attempt to retransmit the CP data (if any pending data exists). If the rejection reason indicates that the cell is not supported, the UE stores this information and will not attempt to transmit a NAS message with CP data on that cell when the UE moves out of that cell, but the UE may attempt to retransmit the CP data (if any pending data exists).

[0083] Figure 9This is a diagram illustrating the message sequence diagram of a UE not initiating a NAS transmission procedure for a CIoT user data container when, according to an embodiment, the UE is in an area / cell / TA where S-NSSAI (e.g., S-NSSAI-A) is unavailable / unsupported based on NS-AoS area or S-NSSAI location availability information. In step 9-2, S-NSSAI-A is not supported in the TA or serving cell. A network function (e.g., AMF 804) sends S-NSSAI location availability information to the UE, indicating an area / cell where S-NSSAI-A is supported / not supported within the TA. In step 9-4, the UE 202 moves to a new cell / TA where S-NSSAI-A is not supported based on a partially / partially allowed NSSAI list or NS-AoS information or S-NSSAI location availability information.

[0084] In steps 9-6, when UE 202 identifies that it is in an area (TAI / cell) that does not support the corresponding S-NSSAI based on a partially / partially permitted NSSAI list or S-NSSAI location availability information, it may not initiate a NAS message transmission procedure, such as using UL NAS transmission for sending CIoT user data containers (control plane data). For example, when network 204 provides a partially / partially permitted NSSAI list or S-NSSAI location availability information, UE 202 understands that it is not allowed to send CP data in areas where S-NSSAI is not supported, and further requests for user plane resources are not allowed or restricted for UE 202. Similarly, on the network side (i.e., network functions), for example, if it is determined based on a partially permitted NSSAI list or NS-AoS that the current cell and / or the current TAI does not support the corresponding S-NSSAI, the SMF / AMF should not send control plane (CP) data (i.e., data in the DL / MT direction) belonging to the S-NSSAI PDU session to the UE. In areas where S-NSSAI is not supported / disallowed / rejected, the UE and SMF may not exchange user data as the payload of NAS messages in both the UL and DL directions. Conversely, in areas where S-NSSAI is supported / allowed / not rejected, the UE and SMF may exchange user data as the payload of NAS messages in both the UL and DL directions. The SMF uses information received from the AMF to determine the area to which the UE belongs. After blocking CP data, a network function (AMF or SMF) may instruct another network function (e.g., User Plane Function (UPF) / Network Open Function (NEF)) that sends CP data to the AMF / SMF to prevent CP data from being sent to the UE, and that the UE is unreachable for that PDU session.

[0085] Figure 10 This is a diagram illustrating a message sequence diagram, according to an embodiment, that allows a UE to initiate a NAS transmission procedure for a CIoT user data container when the UE is in an area / cell / TA where S-NSSAI (e.g., S-NSSAI-A) is unavailable / unsupported based on NS-AoS area or S-NSSAI location availability information. As shown in step 10-2, S-NSSAI-A is not supported in the TA or serving cell. A network function (e.g., AMF 804) sends S-NSSAI location availability information to the UE, indicating areas / cells within the TA where S-NSSAI-A is supported / not supported. At step 10-4, the UE 202 moves to a new cell / TA where S-NSSAI-A is not supported based on a partially allowed NSSAI list or NS-AoS information or S-NSSAI location availability information. At step 10-6, the UE 202 initiates a NAS transmission message to send the CIoT user data container at RAN 802.

[0086] In steps 10-8, when UE 202 is in a cell / TA where S-NSSAI-A is not supported according to a partially permitted NSSAI list, NS-AoS information, or S-NSSAI location availability information, UE 202 is allowed to initiate a NAS transmission message for sending CIoT user data containers. Network functions (e.g., AMF / SMF / UPF) process UL / DL NAS transmission messages to send or receive CIoT user data containers without any restrictions, even though UE 202 is in a cell / TA where S-NSSAI is not supported according to a partially permitted NSSAI list, NS-AoS information, or S-NSSAI location availability information. Furthermore, only user plane resource establishment is restricted.

[0087] In one embodiment, UE 202 can switch from a user plane (UP) PDU session to a CP PDU session to transmit data in areas (TAI / cells) that do not support S-NSSAI based on a partially allowed NSSAI list or S-NSSAI location availability information.

[0088] The terms S-NSSAI (Location Availability Information), NS-AoS (Network Address System), and partially allowed or partially denied NSSAI are used interchangeably to indicate whether S-NSSAI is supported / allowed or not supported / disallowed in the area they indicate. Based on this determination, UE and network actions in the corresponding area are described in this embodiment. This area can be any element, such as a TAI (Target Area), cell, TAI set, cell set, CAG cell, etc.

[0089] UL NAS messages used to send CP data (i.e., control plane data) can be UL NAS transport messages.

[0090] The terms "CP data" or "control plane data" or "CIoT user data" or "control plane user data" sent using the control plane CIoT 5GS optimization are used interchangeably and have the same meaning as indicating control plane user data sent by means of NAS signaling messages carried by signaling, and no user plane resources are established for this purpose.

[0091] The terms support, allow, and do not deny are used interchangeably and have the same meaning.

[0092] The terms resident cell, serving cell, and selected cell are used interchangeably and have the same meaning. Similarly, the terms resident TAI, serving TAI, and selected TAI are used interchangeably and have the same meaning.

[0093] The terms prohibit, suppress, block, or not transmit are used interchangeably and have the same meaning. The terms indicate that although a trigger for transmitting CP data exists, the sending entity will not transmit the CP data; instead, the sending entity blocks / does not transmit the CP data.

[0094] In an embodiment, UE 202 can switch from a CP PDU session to an UP PDU session (i.e., UE 202 can use uplink data state IE in NAS messages (such as service request / registration request messages) to request user plane resources) to send data in areas (TAIs / cells) that support S-NSSAI based on a partially allowed NSSAI list or S-NSSAI location availability information.

[0095] The implementation can be achieved by running at least one software program on at least one hardware device and performing network management functions to control network elements. Figure 2 The module shown includes a block that may be at least one of a hardware device or a combination of a hardware device and a software module.

[0096] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that those skilled in the art can readily modify and / or adapt such specific embodiments for various applications using present knowledge without departing from the general concept, and therefore, such adaptations and modifications should and will be understood to be within the meaning and scope of equivalent forms of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes and not for limitation. Therefore, although embodiments herein have been described with reference to examples and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modifications within the scope of the embodiments described herein.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive location availability information associated with Single Network Slice Selection Assistance Information (S-NSSAI) from the Access Management Function (AMF) entity, the location availability information indicating at least one cell of the Tracking Area (TA) available for the S-NSSAI; and Based on the location availability information associated with the S-NSSAI, identify whether the UE is located in at least one cell of the TA where the S-NSSAI is available; If the UE's location is outside the at least one cell of the TA, it is determined that no Non-Access Stratum (NAS) message for user data will be sent.

2. The method according to claim 1, further comprising: Receive from the AMF the network slice service area (NS-AoS) information of the at least one cell that indicates the TA.

3. The method according to claim 1, further comprising: Receive from the AMF a partial list of NSSAIs allowed for the at least one cell of the TA.

4. The method according to claim 1, further comprising: Receive a rejection message from the AMF indicating that the transmission of the user data is not permitted.

5. A method performed by an Access Management Function (AMF) in a wireless communication system, the method comprising: Send location information associated with Single Network Slice Selection Assistance Information (S-NSSAI) to User Equipment (UE), the location information indicating at least one cell of Tracking Area (TA), the TA including a first cell that supports the S-NSSAI in the TA and a second cell that does not support the S-NSSAI in the TA; The location of the UE is identified based on the location information associated with the S-NSSAI, and Specifically, if the UE is located within the second cell, it is determined that no Non-Access Stratum (NAS) message for user data will be sent.

6. The method according to claim 5, further comprising: Send the Network Slice Service Area (NS-AoS) information of the at least one cell of the TA to the UE.

7. The method according to claim 5, further comprising: Send the UE a partial list of NSSAIs allowed for the at least one cell of the TA.

8. The method according to claim 5, further comprising: Send a rejection message to the UE indicating that the transmission of the user data is not permitted.

9. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as A controller, coupled to the transceiver, is configured to: The Access Management Function (AMF) entity receives location information associated with Single Network Slice Selection Assistance Information (S-NSSAI), the location information indicating at least one cell in a Tracking Area (TA), the TA including a first cell supporting the S-NSSAI in the TA and a second cell not supporting the S-NSSAI in the TA. The location of the UE is identified based on the location information associated with the S-NSSAI; as well as If the UE is located within the second cell, it is determined that no Non-Access Stratum (NAS) message for user data will be sent.

10. The UE according to claim 9, wherein, The controller is also configured to: Receive from the AMF the network slice service area (NS-AoS) information of the at least one cell that indicates the TA.

11. The UE according to claim 9, wherein, The controller is also configured to: Receive from the AMF a partial list of NSSAIs allowed for the at least one cell of the TA.

12. The UE according to claim 9, wherein, The controller is also configured to: Receive a rejection message from the AMF indicating that the transmission of the user data is not permitted.

13. An access management function (AMF) in a wireless communication system, the AMF comprising: transceiver; as well as A controller, coupled to the transceiver, is configured to: The system sends location information associated with Single Network Slice Selection Assistance Information (S-NSSAI) to the User Equipment (UE), the location information indicating at least one cell in a Tracking Area (TA), the TA including a first cell that supports the S-NSSAI in the TA and a second cell that does not support the S-NSSAI in the TA. The location of the UE is identified based on the location information associated with the S-NSSAI, and Specifically, if the UE is located within the second cell, it is determined that no Non-Access Stratum (NAS) message for user data will be sent.

14. The AMF according to claim 13, wherein, The controller is also configured to: Send the Network Slice Service Area (NS-AoS) information of the at least one cell of the TA to the UE.

15. The AMF according to claim 13, wherein, The controller is also configured to: Send the UE a partially allowed NSSAI list of at least one cell of the TA, and Send a rejection message to the UE indicating that the transmission of the user data is not permitted.

Images