Method and apparatus for handling of network slice selection assistance information lists in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the disclosure related to a method and system for handling of NSSAI lists in a wireless network. The method includes receiving one of a partially allowed NSSAI list of a primary S-NSSAI, a partially rejected NSSAI list of the primary S-NSSAI, NS-AoS indicating areas where the primary S-NSSAI is supported or not supported within a primary area. The UE is registered for the primary S-NSSAI. Further, receiving a message from the network apparatus to replace the primary S-NSSAI with an alternate S-NSSAI. Further, detecting, that the UE has moved to an alternate area where the primary S-NSSAI is not supported or supported based on at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI. Further, applying the characteristics of the primary S-NSSAI instead of the alternate S-NSSAI.

Description

METHOD AND APPARATUS FOR HANDLING OF NETWORK SLICE SELECTION ASSISTANCE INFORMATION LISTS IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates generally to a wireless communication system, more particularly, the present disclosure relates to method and apparatus for handling of a Network Slice Selection Assistance Information (NSSAI) lists in the wireless communication system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to a method and system for handling of NSSAI lists in a wireless communication network system.

[0009] In one embodiment, a method for handling NSSAI lists in a wireless communication network system is provided. The method includes receiving, by a UE, at least one of a partially allowed NSSAI list of a primary S-NSSAI, a partially rejected NSSAI list of the primary S-NSSAI, and NS-AoS indicating areas where the primary S-NSSAI is supported or not supported within a primary area from a network apparatus. The UE is registered for the primary S-NSSAI. Further, the method includes receiving, by the UE, a message from the network apparatus to replace the primary S-NSSAI with an alternate S-NSSAI. Further, the method includes detecting, by the UE, that the UE has moved to an alternate area where the primary S-NSSAI is not supported or supported based on at least one of the partially allowed NSSAI lists of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI. Further, the method includes applying, by the UE, characteristics of the primary S-NSSAI instead of the alternate S-NSSAI based on at least one of the partially allowed NSSAI lists of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI.

[0010] In an embodiment, the message is at least one of a downlink non-access stratum (DL NAS) transport message, a UE Configuration Update message, and a Registration Accept message.

[0011] In an embodiment, the area is at least one of a TA or a cell.

[0012] In an embodiment, the characteristics of the primary S-NSSAI and involves determining, by the UE, whether the primary S-NSSAI is supported in the area or is allowed in the area. Further, the method includes determining, by the UE, whether to transmit request for user plane resources of a PDU session of primary S-NSSAI or whether to establish the PDU session belonging to primary S-NSSAI based on the determination to the network apparatus.

[0013] In an embodiment, a method for handling NSSAI lists in a wireless communication network system comprises establishing, by a network apparatus, a PDU session with a UE over a primary S-NSSAI. Further, the method includes detecting, by a network apparatus, whether the primary S-NSSAI is replaced with an alternate S-NSSAI. Further, the method includes replacing, by the network apparatus, the primary S-NSSAI with the alternate S-NSSAI. Further, the method includes transmitting, by the network apparatus, a message to a UE to replace the primary S-NSSAI with the alternate S-NSSAI. Further, the method includes determining, by the network apparatus, whether the primary S-NSSAI that is replaced for the PDU session is subject to area restrictions. In addition, the method includes applying, by the network apparatus, the area restrictions for the primary S-NSSAI that is replaced for the PDU session.

[0014] In an embodiment, the method includes allocating, by the network apparatus, NS-AoS of the alternate S-NSSAI at least as much as NS-AoS of primary S-NSSAI.

[0015] In an embodiment, applying, by the network apparatus, the area restrictions and determining, by the network apparatus, whether the S-NSSAI is allowed or supported in the area instead of the alternate S-NSSAI. Further, the method includes allowing, by the network apparatus, the UE to establish the user plane resources or the PDU session establishment of the primary S-NSSAI in response to determining whether the primary S-NSSAI is allowed or supported in the area. In addition, the method includes denying, by the network apparatus, the UE to establish the user plane resources or the PDU session establishment of the primary S-NSSAI in response to determining whether the primary S-NSSAI is not allowed or not supported in the area.

[0016] In an embodiment, the method includes replacing, by the network apparatus, the primary S-NSSAI with the alternate S-NSSAI includes increasing, by the network apparatus, a count of the alternate S-NSSAI when the alternate S-NSSAI is subject to NSACF and reducing the count of the primary S-NSSAI when the primary S-NSSAI is subject to the NSACF to apply a network slice admission control.

[0017] In an embodiment, the method includes sending or invoking a service operation, by the SMF apparatus, with an increase flag for the alternate S-NSSAI to increase the count and a decrease flag for the primary S-NSSAI to the NSACF to reduce the count, when alternative S-NSSAI is assigned to the replaced S-NSSAI e.g. for its PDU session. In otherwords when the alternative S-NSSAI is assigned, the AMF / SMF entity will indicate to increase the count of PDU session of the alternative S-NSSAI and request check the threshold if its allowed to be established from the NSACF using a service operation, NSACF will do the check and confirm if its allowed or not allowed to SMF using a service operation, then SMF based on this information will decide whether to allow establishment of the PDU session on the alternative S-NSSAI. Similarly, the AMF entity will request to increase the count of the alternative S-NSSAI to NSACF using a service operation and the NSACF will check the threshold if its allowed, NSACF will confirm if its allowed or not allowed then AMF based on this information will decide to whether to allow the alternative S-NSSAI or not allow the alternative S-NSSAI. The AMF / SMF will request to reduce the count of original / replaced S-NSSAI to NSACF. The NSACF will reduce the count of the original / replaced / actual S-NSSAI. The count in this embodiment is at least one of the UE counts and PDU session count.

[0018] IN this embodiment the terms replaced S-NSSAI or original S-NSSAI or Actual S-NSSAI are used interchangeably and have same meaning.

[0019] In an embodiment, the message is at least one of a DL NAS transport message, a UE Configuration Update message, or a Registration Accept message.

[0020] Accordingly, the embodiment herein is to provide a UE for handling NSSAI lists for an alternative S-NSSAI in a wireless communication network system. The UE comprises a memory comprising information about a network apparatus in the wireless network system, a processor, a communicator and a first NSSAI controller. The first NSSAI controller receive from a network apparatus at least one of a partially allowed NSSAI list of a primary S-NSSAI, a partially rejected NSSAI list of the primary S-NSSAI, and NS-AoS indicating areas where the primary S-NSSAI is supported or not supported within a primary area. The UE is registered for the primary S-NSSAI. Further, the first NSSAI controller receive a message from the network apparatus to replace the primary S-NSSAI with an alternate S-NSSAI. Further, the first NSSAI controller detect that the UE has moved to an alternate area where the primary S-NSSAI is not supported or supported based on at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI. Furthermore, the first NSSAI controller to apply characteristics of the primary S-NSSAI instead of the alternate S-NSSAI based on at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI.

[0021] In an embodiment, the message is at least one of a DL NAS transport message, a UE Configuration Update message, and a Registration Accept message. The area is at least one of a TA or a cell. Further, the characteristics of the primary S-NSSAI determine whether the primary S-NSSAI is supported in the area or is allowed in the area, and based on the determinations, whether to request user-plan resources of a PDU session of primary S-NSSAI or whether to establish the PDU session belonging to primary S-NSSAI based on the determination to the network apparatus.

[0022] Accordingly, the embodiment herein is to provide a network apparatus for handling NSSAI lists in a wireless communication network system. The network apparatus comprises a memory comprising information about the network apparatus in the wireless network system, a processor, a communicator and a second NSSAI controller. The second NSSAI controller establish a PDU session with a UE over a primary S-NSSAI. Further, the second NSSAI to detect whether the primary S-NSSAI is replaced with an alternate S-NSSAI. Further, the second NSSAI controller replace the primary S-NSSAI with the alternate S-NSSAI. Further, the second NSSAI controller to transmit a message to a UE to replace the primary S-NSSAI with the alternate S-NSSAI. Further, the second NSSAI controller determine whether the primary S-NSSAI that is replaced for the PDU session is subject to area restrictions. Furthermore, the second NSSAI controller apply the area restrictions for the primary S-NSSAI that is replaced for the PDU session.

[0023] In an embodiment, the second NSSAI Controller allocate a NS-AoS of the alternate S-NSSAI at least as much as NS-AoS of primary S-NSSAI.

[0024] In an embodiment, the second NSSAI Controller is to determine whether the primary S-NSSAI is allowed or supported in the area instead of the alternate S-NSSAI. Further the second NSSAI controller allow the UE to establish the user plane resources or the PDU session establishment of the primary S-NSSAI in response to determine the primary S-NSSAI is allowed or supported in the area and denies the UE to establish the user plane resources or the PDU session establishment of the primary S-NSSAI in response to determining that the primary S-NSSAI is not allowed or not supported in the area.

[0025] In an embodiment, the second NSSAI controller is to increase a count of the alternate S-NSSAI when the alternate S-NSSAI is subject to NSACF and reducing the count of the primary S-NSSAI when the primary S-NSSAI is subject to NSACF to apply a network slice admission control when alternative S-NSSAI is applied to a primary S-NSSAI.

[0026] In an embodiment, the second NSSAI controller is configured to send, an increase flag for the alternate S-NSSAI to increase the count and decrease the flag for the primary S-NSSAI to the NSACF to reduce the count.

[0027] In an embodiment, the message is at least one of a DL NAS transport message, a UE Configuration Update message, or a Registration Accept message.

[0028] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications can be made within the scope of the embodiments.

[0029] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0030] These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0031] FIG. 1 illustrates a sequence diagram that initiates a Non access Stratum (NAS) transport procedure for a 5GS session management (5GSM) message or for establishing user plane resources according to the embodiments as disclosed herein.

[0032] FIG. 2 illustrates a block diagram that illustrates a schematic of a UE implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein.

[0033] FIG. 3 illustrates a block diagram that illustrates a schematic of a network apparatus implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein.

[0034] FIG. 4 is a flow chart that illustrates a method for handling of NSSAI lists in the wireless network system according to the embodiments disclosed herein.

[0035] FIG. 5 is a flow chart that illustrates a method for handling of NSSAI lists in the wireless network system based on area restrictions according to the embodiments disclosed herein.

[0036] FIG. 6 illustrates a sequence diagram where the UE applies an actual S-NSSAI list of rules for accessing the network according to the embodiments as disclosed herein.

[0037] FIG. 7 illustrates a block diagram of a terminal (or a user equipment (UE), according to embodiments of the present disclosure;

[0038] FIG. 8 illustrates a block diagram of a base station, according to embodiments of the present disclosure; and

[0039] FIG. 9 illustrates a block diagram of a network entity, according to embodiments of the present disclosure.

[0040] It may be noted that to the extent possible, like reference numerals have been used to represent like elements in the drawing. Further, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the dimension of some of the elements in the drawing may be exaggerated relative to other elements to help to improve the understanding of aspects of the invention. Furthermore, the elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to the understanding the embodiments of the invention so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

[0041] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

[0042] As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block 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 to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0043] The accompanying drawings are used to help easily understand various technical features and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. used herein to describe various elements, these elements are not be limited by these terms. These terms are generally used to distinguish one element from another.

[0044] In general, under Third Generation Partnership Project (3GPP) TS 24.501, a network must provide the user equipment (UE) with an alternative NSSAI if the UE has indicated that it supports the network slice replacement feature and an Access and Mobility Management Function (AMF) decides to provide the mapping information between the Single- NSSAI (S-NSSAI) that needs to be replaced. The alternative NSSAI is managed per access type independently (for example, 3GPP access or non-3GPP access), and is applicable for the registration area.

[0045] Network slice Area of service (NS-AoS) is an area which determines whether a resource for a slice is allowed for the UE or not allowed for the UE. If the UE is in the area where it's not allowed, UE and network (for example, AMF or Session Management Function (SMF)) does not establish the user plane resources otherwise the user plane resources are established. When the original S-NSSAI is congested / not available the network may assign alternative S-NSSAI to the UE by replacing it with original or replaced S-NSSAI.

[0046] When the UE encounters a situation like this, it should utilize the NS-AoS characteristics of the original or Replaced or modified S-NSSAI, or an alternative S-NSSAI that hasn't been covered or revealed previously work. For example, the original or replaced S-NSSAI (S1) may be indicated by the NS-Aos as authorized in cell-1, while the alternative S-NSSAI (S-A) may be shown as NOT allowed. In this situation, it must be decided if the user should construct plane resources in cell1 based on the UE and AMF / SMF, establishment. The original or replaced S-NSSAI(S1) may be indicated by the NS-Aos as NOT permitted in cell-1, but the alternative S-NSSAI (S-A) may be allowed. It must be decided in such a situation whether the user plane resources in cell1 should be established by the UE and AMF / SMF. In order to govern network slice admittance, the NF e.g. SMF / AMF should tell Network Slice Admission Control Function (NSACF) which Protocol Data Unit (PDU) session slice it belongs to. In this instance, it must be decided which slice SMF should notify NSACF about and which slice (original / replaced S-NSSAI or replaced S-NSSAI) NSACF should impose admission control on. One reason may be that the PDU session belongs to the original slice. As a result, the original slice ought to raise the count and be rejected if the threshold is met. Another argument would be that even if it comes from the original slice, the PDU session is now utilizing the resource of another S-NSSAI (i.e. Alternative S-NSSAI). Therefore, it is necessary to count the alternative S-NSSAI and reject it if its value exceeds a certain threshold.

[0047] Thus, it is desired to address the above-mentioned disadvantages or other shortcomings to provide a useful alternative.

[0048] The embodiment herein is to provide the UE with the means with the means to apply the alternative S-NSSAI list of rules for accessing the network.

[0049] The embodiment herein is to provide the UE with the ability with the ability to apply the actual S-NSSAI list of rules for accessing the network.

[0050] The embodiment herein is to provide the UE with the ability to apply the partially allowed or partially rejected NSSAI list and the NS_AoS information of the S-NSSAI-A (ex: alternative S-NSSAI).

[0051] The embodiment herein is to provide the network functions; for example, SMF, Point Coordination function (PCF), and User Plane Function (UPF) shall apply the same Quality of Service (QOS) characteristics and rules.

[0052] The embodiment herein is to provide the network functions, (for example, AMF, SMF, PCF, UPF, and NSACF), that applies the UE count or PDU session as per the combination of S-NSSAI and alternative S-NSSAI. This may reduce the count of replaced S-NSSAI or the alternative S-NSSAI.

[0053] The embodiment herein is to provide the network and the UE to use the NS-AoS of the original S-NSSAI when the alternative S-NSSAI is assigned to the UE. The NS-AoS of the alternative S-NSSAI is maintained same as the alternate S-NSSAI.

[0054] If the AMF finds the replaced S-NSSAI available, it updates the UE with the alternative NSSAI and corresponding S-NSSAI during configuration or registration. Further, if all the S-NSSAI(s) that were replaced in the alternative NSSAI are available, the AMF provides the alternative NSSAI with the length of the alternative NSSAI contents set to 0 in the UE configuration update procedure or registration procedure. The AMF also provides the updated, allowed, and configured NSSAI to the UE.

[0055] In an embodiment, if the UE has indicated that it supports the partial network slice feature and includes the S-NSSAI(s) in the requested NSSAI, the AMF determines whether the S-NSSAI(s) are to be included in the partially allowed NSSAI or the partially rejected NSSAI. When the AMF provides both the partially allowed NSSAI and the partially rejected NSSAI to the UE, each S-NSSAI shall be either in the partially allowed NSSAI or in the partially rejected NSSAI, but not both.

[0056] Further, a specific policy of S-NSSAI (slice) illustrates the support for network slices with network slice areas of service not matching deployed tracking areas. Where the network support for a network slice is defined on a per-tracking area (TA) granularity. It may be beneficial to deploy some network slices such that the network slice has limited geographical availability that does not match existing TA boundaries. The operator can in this case decide to change the topology of the tracking areas so they match the boundaries of the network slice, or the operator may configure resources for the network slices in the cells of TAs where the network slices are to be available, and in areas of the TAs where the network slice is defined to not be available, the cells are configured with zero resources.

[0057] In an embodiment, the AMF receives from an Operations, Administration, and Maintenance (OAM) the information on the availability of a network slice when the granularity is smaller than TA, i.e., if a NS-AoS includes TAs where the network slice is not available in some cells of the TA. In order to optimize the end-to-end behavior, the AMF can, based on the NS-AoS information received from the OAM, configure supporting the UEs with the S-NSSAI location availability information, and the 5GCore (5GC) network may need to monitor the S-NSSAI usage and enforce the NS-AoS, e.g., if the UE does not support the S-NSSAI location availability information.

[0058] A UE that receives S-NSSAI location availability information applies the information as follows first if the S-NSSAI is rejected in the RA, rejected partially in the RA, or rejected with a cause code that allows attempting to register the S-NSSAI again, the UE can request the S-NSSAI only if the S-NSSAI location availability information indicates that the S-NSSAI is available at the cell where the UE is camping. Further, if the S-NSSAI is in the partially allowed NSSAI, the UE shall not activate the user plane for any already established PDU session with that S-NSSAI if the UE is in a cell within the RA but outside the location information of the S-NSSAI. If the S-NSSAI is in the partially allowed NSSAI and the UE in the Connection Mode-IDLE (CM-IDLE) mode is moved to a cell outside the location information of the S-NSSAI and the UE has an established PDU session with that S-NSSAI, the PDU session is kept.

[0059] In an embodiment, user-plane resources are resources that is established between the UE and a UPF. The user plane resources include radio bearers via a Uu reference point, a tunnel via a N3 reference point and a tunnel via the N9 reference point (if any) for the 3GPP access. Further, the user place resources include an Internet Protocol Security (IPsec) that tunnels via the NWu reference point, the N3 reference point, and the N9 reference point (if any) for untrusted non-3GPP access.

[0060] In an embodiment, there is a layer-2 connection via the Yt reference point, a layer-2 or layer-3 connection via the Yw reference point, a tunnel via the N3 reference point, and a tunnel via the N9 reference point (if any) for the trusted non-3GPP access used by a non-5G-capable over Wireless Local area Network (WLAN) (for e.g, N5CW) device. A W-UP resources via Y4 reference point, a tunnel via the N3 reference point, and a tunnel via the N9 reference point (if any) for wireline access used by a 5thGeneration Residential Gateway (5G-RG), and a Legacy Wireline access User Plane protocol (L-W-UP) resources via Y5 reference point, a tunnel via the N3 reference point, and a tunnel via the N9 reference point (if any) for wireline access used by a Fixed Network Residential Gateway (FN-RG).

[0061] In an embodiment, a partially allowed NSSAI is indicating the S-NSSAIs values. Where the S-NSSAIs values are used by the UE in serving a public land mobile network (PLMN) or a standalone NPN (SNPN) in some of the TAs in the current registration area, Each of the S-NSSAIs in the partially allowed NSSAI is associated with a list of TAs where the S-NSSAI is supported.

[0062] In an embodiment, a Network Slice Area of Service is an area where a UE can access and get service for a particular network slice, as more than zero resources are allocated to the network slice in the NG-RAN cells.

[0063] In an embodiment, S-NSSAI location availability information is sent to the UE for each applicable S-NSSAI of the configured NSSAI. The location information indicates the cells of the TAs in the RA where the related S-NSSAI is available if the S-NSSAI is not available in all the cells of the TA.

[0064] In an embodiment, the alternative NSSAI is where a list of mapping information between the S-NSSAI is to be replaced.

[0065] In an embodiment, a partially rejected NSSAI　that is indicates the S-NSSAI(s) is rejected by the network in some of the TAs but not all the TAs of the registration area. Each of the S-NSSAI in the partially rejected NSSAI is associated with the list of TAs where the S-NSSAI is rejected.

[0066] In an embodiment, an on-demand S-NSSAI is an S-NSSAI that is allowed by the UE to be registered with the network only when this S-NSSAI is used by the UE to establish the PDU session for the user data transmission.

[0067] In an embodiment, S-NSSAI-1 andS1 are considered examples of the S-NSSAI to be replaced by the AMF, and S-NSSAI-A and S2 are considered alternative S-NSSAIs for S-NSSAI-1 and S1, respectively.

[0068] In an embodiment, the actual or original S-NSSAI and the term S-NSSAI to be replaced are used interchangeably.

[0069] Accordingly, the problem faced by the conventional method is that when the S-NSSAI is not supported in the entire registration area, the entire TA, or some parts of the cells in the TA, the network will notify the UE in one of the NSSAI lists, the partially allowed NSSAI, the partially rejected NSSAI, or the network slice area of service. If the S-NSSAI is replaced by an alternative S-NSSAI, whether the UE is allowed to consider the S-NSSAI as per the NSSAI lists that correspond to the alternative S-NSSAI or the one that is being replaced (for example: S-NSSAI-1 or S1) is not clear.

[0070] Accordingly, the proposed solution discloses a method and system for handling NSSAI lists for an alternative S-NSSAI, where the S-NSSAI-1 shall be replaced by the S-NSSAI-A. The UE applies either one or all of the partially allowed or partially rejected NSSAI list or the NS_AoS information of the S-NSSAI-A. The UE requests the user plane resources over the S-NSSAI-1, even though it is outside of the partially allowed TA for the S-NSSAI-1 but in the allowed area of the S-NSSAI-A. The UE requests for the user plane resources over the S-NSSAI-1 when it is inside the partially rejected TA for the S-NSSAI-1 but in the allowed area of the S-NSSAI-A. The UE requests for the user plane resources over the S-NSSAI-1 when it is outside the allowed area or the slice is not supporting the cell as per the NS-AoS information for the S-NSSAI-1 but in the allowed area of the S-NSSAI-A.

[0071] Accordingly, the embodiment is when the S-NSSAI, for example, the S-NSSAI-1, is the original or actual S-NSSAI (to be replaced by the S-NSSAI), for which the UE is registered and has established one or more PDU sessions over this S-NSSAI.

[0072] Further, the Network function (for example, the AMF) has replaced the S-NSSAI-1 using the alternative S-NSSAI, for example, the S-NSSAI-A, by sending a DL NAS transport message such as, for example, Registration Accept / UE Configuration Update Command by including the Alternative NSSAI IE. The S-NSSAI-1 is not allowed in the entire tracking area or registration area; for example, the S-NSSAI-1 is allowed only in the tracking area identifier (TAI-1), TAI-2, and some cells of the TAI-3 (cell id 1 and cellid2, but not on cell id 3), but not supported in the TAI-4 and the TAI-5. All of these TAs can belong to the same or different RAs. As per the S-NSSAI-1 configuration received by the UE from the network function, for example, the AMF, The S-NSSAI-A is allowed in the entire TAs of TAI-1, TAI-2, TAI-3, and TAI-4 but not supported in TAI-5. As per the S-NSSAI-A configuration received by the UE from the network function, for example, the AMF, The S-NSSAI-1 and the S-NSSAI-A are part of the UE-allowed NSSAI list, the partially allowed NSSAI list, or any other NSSAI lists that are available and configured on the UE.

[0073] In an embodiment, in scenario 1, the UE moved to the TA, where the S-NSSAI-1 is not allowed as per the partially allowed NSSAI list. The UE is under the TAI-1 and registered for the S-NSSAI-1. Further, the AMF determines to provide the mapping information between the S-NSSAI-1 to be replaced and the alternative S-NSSAI-A to the UE. Since the S-NSSAI-1 is now replaced by the S-NSSAI-A, the UE is utilizing the S-NSSAI-A network resources, such as, for example, SMF, UPF, and NF. The UE is moved to the TAI-4, where the S-NSSAI-1 is not allowed as per the partially allowed or partially rejected NSSAI lists.

[0074] The problem in scenario 1 is that the UE is unaware whether the UE shall consider the TAI-4 as allowed or not allowed, since, as per the NSSAI lists configuration, it is allowed for the S-NSSAI-A but not allowed for the S-NSSAI-1.

[0075] In an embodiment, the solution provided for scenario 1 is that the UE shall apply the partially allowed or partially rejected NSSAI list or the NS_AoS information of the S-NSSAI-A, i.e., the UE shall apply all properties of the alternative S-NSSAI, i.e., the S-NSSAI-A, instead of the original or actual S-NSSAI-1. The UE shall consider the Alternative S-NSSAI-A related lists, and if Alternative S-NSSAI is allowed in the current TA, the UE is allowed to establish the new PDU sessions and request user plane resources for the existing PDU sessions of S-NSSAI-A. Further, the AMF, on determining that UE is in the NOT supported TAI of S-NSSAI-A, i.e., TAI-5, will not establish the user plane resources for PDU session- ID 1.

[0076] In another embodiment, the solution provided for scenario 1 is that the UE shall apply the partially allowed or partially rejected NSSAI list and the NS_AoS information of the S-NSSAI-1, i.e., the UE shall apply all properties of the original or actual S-NSSAI instead of Alternative S-NSSAI-A. The UE shall not establish new PDU sessions over this S-NSSAI-1, or the UE is not allowed to request user plane resources for the PDU sessions that are already established over this S-NSSAI-1. S-NSSAI-1 is not allowed in this area as per the partially allowed NSSAI list. Though S-NSSAI-A is allowed, Further, the AMF, on determining that UE is in the NOT supported TAI of S-NSSAI-1, i.e., TAI-4, will not establish the user plane resources for PDU session ID-1.

[0077] In an embodiment, in scenario 2, the UE moved to the TA where the S-NSSAI-1 is not permitted according to the partially rejected NSSAI list. The UE is under the TAI-1 and registered for the S-NSSAI-1. The AMF determines to provide the mapping information between the S-NSSAI-1 to be replaced and the alternative S-NSSAI-A to the UE. Since the S-NSSAI-1 has now been replaced by the S-NSSAI-A. The UE is utilizing the S-NSSAI-A network resources, such as the the SMF / UPF / NF. The UE is moved to the TAI-4, where the S-NSSAI-1 is not allowed according to the partially rejected NSSAI lists.

[0078] The issue with scenario 2 is that the UE (100) does not know if it should treat the TAI-4 as allowed or not, as it is allowed for the S-NSSAI-A but not for the S-NSSAI-1 according to the NSSAI lists (e.g., partially rejected NSSAI list) configuration.

[0079] In another embodiment, the solution provided for scenario 2 is that the UE shall apply the partially allowed or partially rejected NSSAI list or the NS_AoS information of the S-NSSAI-A for example, the UE shall apply all properties of the alternative S-NSSAI for example, the S-NSSAI-A instead of original / actual S-NSSAI-1. The UE shall consider the Alternative S-NSSAI-A related lists (for example, partially rejected NSSAI list) and if alternative S-NSSAI is allowed in the current TA, the UE is allowed to establish the new PDU sessions / request for the user plane resources for the existing PDU sessions over that the S-NSSAI. Further, the AMF / SMF on determining that the UE is in NOT supported TAI of the S-NSSAI-A, i.e. TAI-5, the AMF / SMF will not establish the user plane resources for the PDU session-ID-1.

[0080] In an embodiment, the solution provided for scenario 2 is that the UE shall apply the partially allowed or partially rejected NSSAI list and the NS_AoS information on the S-NSSAI-1 is that the UE shall apply all properties of the original or actual or replaced S-NSSAI instead of the alternative S-NSSAI-A. The UE shall not establish the new PDU sessions over this S-NSSAI-1, or the UE is not allowed to request the user plane resources for the PDU sessions that are already established over this S-NSSAI-1. As the S-NSSAI-1 is not allowed in this area as per the partially rejected NSSAI list or partially allowed NSSAI list. Though, the S-NSSAI-A is allowed. Further, the AMF / SMF, on determining that the UE is in NOT supported TAI of the S-NSSAI-1, that is TAI-4, the AMF / SMF will not establish the user plane resources for the PDU session-ID-1.

[0081] In an embodiment, in scenario 3, the UE moved to a cell, area, or location where the S-NSSAI-1 is not allowed as per the NS-AoS Information, or the S-NSSAI location availability information. The UE is under TAI-3 and cell ID1 and registered for S-NSSAI-1. The AMF determines to provide mapping information between the S-NSSAI-1 to be replaced and the alternative S-NSSAI-A to the UE. Since the S-NSSAI-1 is now replaced by the S-NSSAI-A, the UE is utilizing the S-NSSAI-A network resources, such as, for example, the SMF / UPF. The UE is moved to the TAI-3 and the cell ID3, where the S-NSSAI-1 is not allowed as per the NS-AoS information or the S-NSSAI location availability information.

[0082] The problem in scenario 3 is that the UE is unaware whether the UE shall consider the TAI-3 and the cell ID3 as allowed or not allowed, since as per the NSSAI lists (for example, NS-AoS information, or S-NSSAI location availability information) configuration, it is allowed for the S-NSSAI-A but not allowed for the S-NSSAI-1.

[0083] In an embodiment, the solution provided for scenario 3 is that the UE shall apply the partially allowed or partially rejected NSSAI list and NS_AoS information of S-NSSAI-A, that is the UE shall apply all properties of the alternative S-NSSAI i.e the S-NSSAI-A, instead of the original or actual S-NSSAI-1. The UE shall consider the alternative S-NSSAI-A related lists (for example, NS-AoS information or the S-NSSAI location availability information), and if alternative S-NSSAI is allowed in the current TA, the UE is allowed to establish the new PDU sessions or request for user plane resources for the existing PDU sessions over the S-NSSAI. Further, if the AMF / SMF determines that the UE is in the NOT supported cell of the S-NSSAI-A, that is for example, cell ID x, the AMF / SMF will not establish the user plane resources for the PDU session-ID 1.

[0084] Further, the example for the partially allowed or partially rejected NSSAI list. The Registration Area is TAI-1, TAI-2, and TAI-3; a supported TAI for the S-NSSAI-1 is TAI-1; the supported TAI for the S-NSSAI-A is TAI-2 (S-NSSAI-A is an alternative S-NSSAI for S-NSSAI-1); and the PDU session-ID-1 is a PDU session of the DNN-1+S-NSSAI-1.

[0085] In an embodiment herein, the solution is to apply the same solution as the S-NSSAI-A. Where the given TAI-1 is not supported for the S-NSSAI-A. (for example, the UE shall consider or apply the NSSAI lists associated with S-NSSAI-A for establishing the PDU session over S-NSSAI-1 or while requesting access to the network resources (i.e. user plane resources) for PDU session ID-1).

[0086] When not in the supported TAI for the S-NSSAI-A. The UE is on TAI-1; the UE is not allowed to trigger the NAS procedure, for example, a service request to request user plane resources using uplink data status IE by setting the PDU session ID-1 or sending the SM message. The UE is on the TAI-1; the UE is not allowed to send the PDU session establishment request or trigger a Session Management (SM) procedure for the PDU session of S-NSSAI-1. Further, the AMF / SMF on determining that the UE is in NOT supported TAI of the S-NSSAI-A, for example, TAI-1, and the AMF / SMF will not establish the user plane resources for PDU session ID-1.

[0087] Where the TAI is supported for S-NSSAI-A, the UE is on TAI-2, is allowed to trigger the NAS procedure, for example, a service request to request user plane resources using the uplink data status information element (IE), by setting the PDU session ID-1. The UE is on TAI-2, and the UE is allowed to send the PDU session establishment request or trigger the SM procedure for the PDU session of the S-NSSAI-1. Further, the AMF / SMF, on determining that the UE is in the supported TAI of the S-NSSAI-A, for example, TAI-2, will establish the user plane resources for the PDU session-ID-1

[0088] Further, the example for the NS-AOS or slice location availability information. The Registration Area is TAI-1, TAI-2, and TAI-3; the supported TAI for S-NSSAI-1 is TAI-1; the supported TAI for S-NSSAI-A is TAI-2 (S-NSSAI-A is an alternative S-NSSAI for S-NSSAI-1); and the PDU session ID-1 is a PDU session of DNN-1+S-NSSAI-1.

[0089] In an embodiment, the solution is to apply the same solution as the S-NSSAI-1. The given TAI-2 is not supported for the S-NSSAI-1. (for example, the UE shall consider or apply the NSSAI lists associated with S-NSSAI-1 for establishing the PDU session over S-NSSAI-1 or while requesting or accessing the network resources for PDU session ID-1).

[0090] When we do not support TAI for S-NSSAI-1, the UE is on TAI-2; the UE is not allowed to trigger a NAS procedure, for example, a service request to request user plane resources using uplink data status IE by setting the PDU session ID-1. The UE is on TAI-2; the UE is not allowed to send the PDU session establishment request or trigger the SM procedure for the PDU session of the S-NSSAI-1. Further, the AMF / SMF, on determining that the UE is in the NOT supported TAI of the S-NSSAI-1, for example, the TAI-2 will not establish the user plane resources for the PDU session ID-1.

[0091] When TAI is supported for S-NSSAI-1. The UE is on TAI-1, UE is allowed to trigger a NAS procedure, for example, a service request to request for user plane resources using uplink data status IE by setting the PDU session ID-1 and the UE is on TAI-1, UE is allowed to send the PDU session establishment request or trigger the SM procedure for the PDU session of S-NSSAI-1. Further, the AMF / SMF, on determining that the UE is in supported TAI of the S-NSSAI-1, for example, the TAI-1, will establish the user plane resources for the PDU session ID-1.

[0092] Furthermore, for example, the Ns-Aos / slice location availability information. The registration area is TAI-1, TAI-2, and TAI-3, the supported TAI or cell for the S-NSSAI-1 is Cell1 of (TAI-1); the supported TAI / cell for the S-NSSAI-A is Cell2 of (TAI-1) (S-NSSAI-A is an alternative S-NSSAI for S-NSSAI-1), and the PDU session ID-1 is the PDU session of DNN-1+S-NSSAI-1.

[0093] In an embodiment, the solution is to apply, the same as S-NSSAI-A. Given Cell1 of (TAI-1) is not supported for S-NSSAI-A. (for example, the UE shall consider / apply the NSSAI lists / NS-AoS information associating with S-NSSAI-A for the establishing the PDU Session over S-NSSAI-1 or while requesting / accessing the network resources for PDU Session ID-1)

[0094] When the cell is NOT supported for the S-NSSAI-A. Then the UE is on the cell1 of (TAI1), and the UE is not allowed to trigger a NAS procedure, for example, a service request to request user plane resources using uplink data status IE by setting the PDU session ID-1. The UE is on cell1 of (TAI1), and the UE is not allowed to send the PDU session establishment request or trigger the SM procedure for the PDU session of the S-NSSAI-1. Further, the AMF / SMF, on determining that the UE is in the NOT supported cell of the S-NSSAI-A, that is cell1 of TAI-1, the AMF / SMF, will not establish the user plane resources for the PDU session ID-1.

[0095] When the cell is supported for the S-NSSAI-A. Then the UE is on cell 2 of (TAI1), and the UE is allowed to trigger the NAS procedure, for example, a service request to request user plane resources using uplink data status IE by setting the PDU session ID-1. The UE is on cell 2 of (TAI1). The UE is allowed to send a PDU session establishment request or trigger a SM procedure for the PDU session of the S-NSSAI-1. Further, the AMF / SMF on determines that the UE is in supported TAI of the S-NSSAI-A, for example, cell 2 of TAI-1, the AMF / SMF can establish the user plane resources for the PDU session-ID-1.

[0096] In an embodiment, the solution is to apply the same as S-NSSAI-1. Given cell 2 of (TAI1), it is not supported for S-NSSAI-1, (for example, the UE shall consider or apply the NSSAI lists associated with S-NSSAI-1 for establishing the PDU session over S-NSSAI-1 or while requesting or accessing the network resources for PDU session ID-1).

[0097] When the cell is NOT supported for S-NSSAI-1. Then the UE is on cell 2 TAI-1 the, UE is not allowed to trigger a NAS procedure, for example, a service request to request user plane resources using uplink data status IE by setting the PDU session ID-1. The UE is on cell 2 of TAI-1, the UE is not allowed to send the PDU session establishment request or trigger the SM procedure for the PDU session of the S-NSSAI-1. Further, the AMF / SMF, on determining that the UE is in the NOT supported cell of the S-NSSAI-1, for example, cell2 of TAI-1, will not establish the user plane resources for the PDU session ID-1.

[0098] When the cell is supported for the S-NSSAI-1, then the UE is on cell 1 of TAI-1, and the UE is allowed to trigger a NAS procedure, for example, a service request to request user plane resources using uplink data status IE, by setting the PDU session ID-1. The UE is on cell 1 of TAI-1. The UE is allowed to send a PDU session establishment request or trigger a SM procedure for the PDU session of the S-NSSAI-1. Further, the AMF / SMF, on determining that the UE is in a supported cell of the S-NSSAI-1, for example, cell1 of TAI-1, will not establish the user plane resources for the PDU session ID-1.

[0099] Additionally, in an embodiment, the solution is that the alternative S-NSSAI (example, S-NSSAI-A) applies the same supported tracking area (Tas) or Cells as the original or actual S-NSSAI that has been replaced (for example, S-NSSAI-1). If the S-NSSAI-1 is supported in TAI1 and not in TAI2, then the alternative S-NSSAI will also be supported in TAI1 and not in TAI2. If S-NSSAI-1 is supported in Cell1 of TAI1 but not supported in Cell 2 of TAI1, then the alternative S-NSSAI will also be supported in Cell1 of TAI1 but not in cell2 of TAI.

[0100] Further, in the Network Function example, the AMF can update the NSSAI lists (for example, Allowed NSSAI, Partially Allowed NSSAI, Partially Rejected NSSAI, Ns-AOS, time validity of the S-NSSAI) of the alternative S-NSSAI to be same as that the same original / actual S-NSSAI.

[0101] S-NSSAI (slice) represents the support for network slices in the current scenario where the deployed tracking regions and the network slice area of service do not match. Therefore, it will be advantageous to modify the tracking areas' topology so that it matches the network slice's boundaries. Alternatively, the operator may set up resources for the network slices in TA cells where they are to be available and set up zero resources in TA cells where the network slice is defined as not being available.

[0102] FIG. 1 illustrates a sequence diagram that initiates a NAS transport procedure for a 5GSM message or for establishing user plane resources according to the embodiments as disclosed herein. As shown in the sequence diagram, the UE (200) establishes a communication with the network apparatus (300) via a RAN (105).

[0103] At step S101, the S-NSSAI to be replaced is part of the partially allowed or partially rejected NSSAI list or part of the NS_AOS information. The S-NSSAI-1 is not supported in the entire TA or RA. The network apparatus (300) sends the partially allowed or partially rejected NSSAI list or the S-NSSAI location availability information indicating the area or cells where the S-NSSAI-1 is supported or not supported in the TA to the UE (200). The UE (200) registered for S-NSSAI-1. The example is that the S-NSSAI-1 is allowed in the TA1 and not allowed in the TA2 and allowed in a few cells of the TA3, and the S-NSSAI-A may be allowed in the entire RA.

[0104] Further, at step S102, the network apparatus (300) sends a DL NAS transport message to the UE (200). For example, the DL NAS message may be a UE Configuration Update or Registration Accept message to replace the S-NSSAI-1 with the alternative S-NSSAI (for example, S-NSSAI-A). At step S103, the UE (200) is moved to a new cell or TA where S-NSSAI-1 is not supported as per the partially allowed or rejected NSSAI list or NS-AoS information.

[0105] At step S104, one of the following issues faced by the UE (200), since the UE (200) is registered for the S-NSSAI-1 and is replaced using the alternative the S-NSSAI, the S-NSSAI-A.

[0106] In an embodiment, whether the UE (200) shall apply the partially allowed or partially rejected NSSAI list or the NS_AoS information of the S-NSSAI-1 or the S-NSSAI-A is unknown, which will lead to wrong behavior.

[0107] In an embodiment, whether the UE (200) can request the user plane resources over the S-NSSAI-1 when it is outside of the partially allowed TA for the S-NSSAI-1 but in the allowed area of the S-NSSAI-A.

[0108] In an embodiment, whether the UE (200) can request for the user plane resources over the S-NSSAI-1 when it is inside of the partially rejected TA for the S-NSSAI-1 but in the allowed area of the S-NSSAI-A.

[0109] In an embodiment, whether the UE (200) can request for the user plane resources over the S-NSSAI-1 even if it is outside allowed as an area or inside the allowed area as per the Ns-AOS information for the S-NSSAI-1 but in the allowed area of the S-NSSAI-A. In the present solution, the- mentioned issues provide a solution for handling NSSAI lists in the wireless network communication system.

[0110] FIG. 2 illustrates a block diagram that illustrates a schematic of the UE (200) implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein.

[0111] As shown, the UE (200) includes a memory (201), a processor (202) a communicator (203), a first NSSAI controller (204). The UE (200) can be an end-user device that connects with a communication network to access services. The UE (200) may include, but is not limited to a laptop, a palmtop, a desktop, a mobile phone, a smart phone, Personal Digital Assistant (PDA), a tablet, a wearable device, an Internet of Things (IoT) device, a virtual reality device, Video see through (VST), AR glass, a foldable device, a flexible device, a display device, an immersive system, and the like. Further, the processor (202) communicates with the memory (201), the Communicator (203), and the first NSSAI controller (204). The processor (202) is configured to execute instructions stored in the memory (201) and to perform various processes. The processor (202) can include one or a plurality of processors, can be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU). Further, the memory (201) of the UE (200) includes storage locations to be addressable through the processor (202). The memory (201) is not limited to a volatile memory (201) and / or a non-volatile memory (201). Further, the memory (201) can include one or more computer-readable storage media. The memory (201) can include non-volatile storage elements. For example, non-volatile storage elements can include magnetic hard discs, optical discs, floppy discs, flash memories.

[0112] In an embodiment, the communicator (203) includes an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (203) is configured to communicate internally between internal hardware components and with external devices via one or more networks. The Communicator (203) is to transmit and receive data; however, the portion designated as the communicator (203) can also contain additional resources, such as voltage translators, registers, impedances, and buffers. For Example: A keyboard and mouse provide Input to the computer are called input devices while a monitor and printer that provide output to the computer are called output devices.

[0113] In an embodiment, the first NSSAI controller (204) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components. the first NSSAI controller (204) in the UE (200) is applies the partially allowed / partially rejected NSSAI list and the NS_AoS information of the S-NSSAI-A.

[0114] In an embodiment, the first NSSAI controller (204), connected to the memory (201) and the processor (202). Further, the First NSSAI controller (204) is configured to receive a message from the network apparatus (300) to replace the primary S-NSSAI with an alternate S-NSSAI. Further the First NSSAI controller (204) is configured to detects that the UE (200) has moved to an alternate area where the primary S-NSSAI is not supported or supported based on at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI. Furthermore, the First NSSAI controller (204) is configured to apply characteristics of the primary S-NSSAI instead of the alternate S-NSSAI based on at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI.

[0115] FIG. 3 illustrates a block diagram that illustrates a schematic of a network apparatus (300) implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein

[0116] As shown, the network apparatus (300) includes the processor (202), the memory (201), the communicator (203), and a second NSSAI controller (301). The network apparatus (300) may be electronic devices that are required for communication and interaction between devices on a computer network.　They are used to combine, split, switch, boost, or direct packets of information along the computer or telecommunications network. Further, the processor (202) communicates with the memory (201), communicator (203), the second NSSAI controller (301).

[0117] In an embodiment, the Second NSSAI controller (301) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components. Further the Second NSSAI controller (301) is configured to establishes a PDU session with the UE (200) over a primary S-NSSAI. Further, the Second NSSAI controller (301) is configured to detect whether the primary S-NSSAI is replaced with an alternate S-NSSAI. Further the Second NSSAI controller (301) is configured to replace the primary S-NSSAI with the alternate S-NSSAI. Furthermore, the Second NSSAI controller (301) is configured to transmit the message to the UE (200) to replace the primary S-NSSAI with alternate S-NSSAI. Further the Second NSSAI controller (301), determines whether the primary S-NSSAI that is replaced for the PDU session is subject to area restrictions and applies the area restrictions for the primary S-NSSAI that is replaced for the PDU session.

[0118] FIG. 4 is a flow chart that illustrates a method for handling of NSSAI lists in the wireless network system according to the embodiments disclosed herein.; The flow chart includes steps (402-408). Each step is explained in further detail below.

[0119] In step S402, at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and NS-AoS indicating areas where the primary S-NSSAI is supported or not supported within a primary area is received by the UE (200). The UE (200) is registered for the primary S-NSSAI.

[0120] In step S404, a message is received to replace the primary S-NSSAI with an alternate S-NSSAI. For example, the message is at least one of a down link non-access stratum (DL NAS) transport message, a UE Configuration Update message, and a Registration accept message.

[0121] The area is at least one of the TA or a cell. The characteristics of the primary S-NSSAI includes determining whether the primary S-NSSAI is supported in the area or is allowed in the area.

[0122] In step S406, it is detected whether the UE (200) has moved to an alternate area where the primary S-NSSAI is not supported or supported. This detection may be based on at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI.

[0123] In step S408, the characteristics of the primary S-NSSAI instead of the alternate S-NSSAI are applied. For instance, the characteristics may be applied based on at least one of the partially allowed NSSAI list of the primary S-NSSAI, the partially rejected NSSAI list of the primary S-NSSAI, and the NS-AoS of the primary S-NSSAI.

[0124] FIG. 5 is a flow chart that illustrates a method for handling of NSSAI lists in the wireless network system based on area restrictions according to the embodiments disclosed herein. The flow chart includes steps (502-510). Each step is explained in further detail below.

[0125] In an embodiment, at S502, establishing, by the network apparatus (300), the PDU session with the UE (200) over the primary S-NSSAI.

[0126] Further, at S504, the method includes, detecting, by the network apparatus (300), whether the primary S-NSSAI is replaced with an alternate S-NSSAI.

[0127] Further, at S506, the method includes, replacing, by the network apparatus (300), the primary S-NSSAI with the alternate S-NSSAI.

[0128] Further, at S508, the method includes, transmitting, by the network apparatus, a message to the UE (200) to replace the primary S-NSSAI with the alternate S-NSSAI. Replacing the primary S-NSSAI with the alternate S-NSSAI comprises increasing a count of the alternate S-NSSAI, when the alternate S-NSSAI is subject to NSACF and reduce the count of the primary S-NSSAI if it is subject to the NSACF to apply a network slice admission control. Furthermore, at S510, the method includes, determining, by the network apparatus (300), whether the primary S-NSSAI that is replaced for the PDU session is subject to area restrictions and ignoring the area restrictions information which may be available for alternative S-NSSAI and at S512, applying, by the network apparatus (300), the area restrictions for the primary S-NSSAI that is replaced for the PDU session. Determines whether the primary S-NSSAI is allowed or supported in the area instead of the alternate S-NSSAI. Allowing the user plane or the PDU session establishment of the primary S-NSSAI in response to determining the primary S-NSSAI is allowed or supported in the area. Denying, the UE to establish the user plane resources or the PDU session establishment of the primary S-NSSAI in response to determining that the primary S-NSSAI is not allowed or not supported in the area.

[0129] FIG. 6 illustrates a sequence diagram where the UE applies an actual S-NSSAI list of rules for accessing the network according to the embodiments as disclosed herein. As shown in the sequence diagram, the UE (200) establishes a communication with the network apparatus (300) via the RAN (105).

[0130] In an embodiment, the UE (200) and the network apparatus (300) (eg: AMF), that applies actual / replaced S-NSSAI list of the rules for accessing the network. At step S601, the S-NSSAI-1 is not supported in the entire TA / RA. The network apparatus (300) sends to the UE (200), the Partially allowed / partially rejected NSSAI list, or the S-NSSAI location availability information indicating area / cells where the S-NSSAI-1 is supported / not supported with in the TA. The UE registered for the S-NSSAI-1. For example, the S-NSSAI-1 is allowed in TA1 and not allowed in TA2 and allowed in few cells of TA3 and S-NSSAI-A may be allowed in entire RA.

[0131] Further, at step S602, the network apparatus (300) sends the DL NAS transport message to the UE (200). For example, the DL NAS message may be a UE Configuration Update or Registration accept message to replace the S-NSSAI-1 with alternative S-NSSAI for example the S-NSSAI-A.

[0132] At step S603, the UE (200) moved to a new cell / TA where the S-NSSAI-1 is not supported as per partially allowed / rejected NSSAI list or the NS-AoS information.

[0133] At step S604, the Solution applicable is though the S-NSSAI-1 is replaced by the S-NSSAI-A.

[0134] In an embodiment, the UE (200) shall apply the partially allowed / partially rejected NSSAI list and the NS_AoS information of the S-NSSAI-1 for example the UE (200) shall apply all properties of the original / actual S-NSSAI instead of the alternative S-NSSAI-A.

[0135] In an embodiment, the UE (200) shall not request for the user plane resources over the S-NSSAI-1 when it is outside of the partially allowed TA for the S-NSSAI-1 even though the UE is in the allowed area of the S-NSSAI-A.

[0136] In an embodiment, the UE (200) shall not request for the user plane resources over the S-NSSAI-1 when it is inside of the partially rejected TA for the S-NSSAI-1 even though the UE is in the allowed area of the S-NSSAI-A.

[0137] In an embodiment, the UE (200) shall not request for the user plane resources over the S-NSSAI-1 when it is outside allowed area as per Ns-AOS information for the S-NSSAI-1 even though the UE is in the allowed area of the S-NSSAI-A.

[0138] In an embodiment, when the network apparatus (300) determines that the UE (200) is in NOT supported TAI / cell of the S-NSSAI-1, the AMF and SMF will not establish the user plane resources for the PDU session-ID-1 for e.g. if there is any downlink data over the PDU session.

[0139] In an embodiment, when the network apparatus (300) determines that the UE (200) is in supported TAI / cell of the S-NSSAI-1, the AMF and SMF will establish the user plane resources for the PDU session-ID-1 for e.g. if there is any downlink data over the PDU session.

[0140] FIG. 7 illustrates a block diagram of a terminal (or a user equipment (UE)), according to embodiments of the present disclosure. FIG. 7 corresponds to the example of the UE of FIG. 2.

[0141] As shown in FIG. 7, the UE according to an embodiment may include a transceiver 710, a memory 720, and a processor 730. The transceiver 710, the memory 720, and the processor 730 of the UE may operate according to a communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 730, the transceiver 710, and the memory 720 may be implemented as a single chip. Also, the processor 730 may include at least one processor.

[0142] The transceiver 710 collectively refers to a UE receiver and a UE transmitter, and may transmit / receive a signal to / from a base station or a network entity. The signal transmitted or received to or from the base station or a network entity may include control information and data. The transceiver 710 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 710 and components of the transceiver 710 are not limited to the RF transmitter and the RF receiver.

[0143] Also, the transceiver 710 may receive and output, to the processor 730, a signal through a wireless channel, and transmit a signal output from the processor 730 through the wireless channel.

[0144] The memory 720 may store a program and data required for operations of the UE. Also, the memory 720 may store control information or data included in a signal obtained by the UE. The memory 720 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0145] The processor 730 may control a series of processes such that the UE operates as described above. For example, the transceiver 710 may receive a data signal including a control signal transmitted by the base station or the network entity, and the processor 730 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.

[0146] FIG. 8 illustrates a block diagram of a base station, according to embodiments of the present disclosure. FIG. 8 corresponds to the example of the RAN node of FIG. 1.

[0147] As shown in FIG. 8, the base station according to an embodiment may include a transceiver 810, a memory 820, and a processor 830. The transceiver 810, the memory 820, and the processor 830 of the base station may operate according to a communication method of the base station described above. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 830, the transceiver 810, and the memory 820 may be implemented as a single chip. Also, the processor 830 may include at least one processor.

[0148] The transceiver 810 collectively refers to a base station receiver and a base station transmitter, and may transmit / receive a signal to / from a terminal or a network entity. The signal transmitted or received to or from the terminal or a network entity may include control information and data. The transceiver 810 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 810 and components of the transceiver 810 are not limited to the RF transmitter and the RF receiver.

[0149] Also, the transceiver 810 may receive and output, to the processor 830, a signal through a wireless channel, and transmit a signal output from the processor 830 through the wireless channel.

[0150] The memory 820 may store a program and data required for operations of the base station. Also, the memory 820 may store control information or data included in a signal obtained by the base station. The memory 820 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0151] The processor 830 may control a series of processes such that the base station operates as described above. For example, the transceiver 810 may receive a data signal including a control signal transmitted by the terminal, and the processor 830 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

[0152] FIG. 9 illustrates a block diagram of a network entity, according to embodiments of the present disclosure. FIG. 9 corresponds to the example of the network apparatus of FIG. 3.

[0153] As shown in FIG. 9, the network entity according to an embodiment may include a transceiver 910, a memory 920, and a processor 930. The transceiver 910, the memory 920, and the processor 930 of the network entity may operate according to a communication method of the network entity described above. However, the components of the network entity are not limited thereto. For example, the network entity may include more or fewer components than those described above. In addition, the processor 930, the transceiver 910, and the memory 920 may be implemented as a single chip. Also, the processor 930 may include at least one processor.

[0154] The transceiver 910 collectively refers to a network entity receiver and a network entity transmitter, and may transmit / receive a signal to / from a terminal or other network entity. The signal transmitted or received to or from the terminal or other network entity may include control information and data. The transceiver 910 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 910 and components of the transceiver 910 are not limited to the RF transmitter and the RF receiver.

[0155] Also, the transceiver 910 may receive and output, to the processor 930, a signal through a wireless channel, and transmit a signal output from the processor 930 through the wireless channel.

[0156] The memory 920 may store a program and data required for operations of the network entity. Also, the memory 920 may store control information or data included in a signal obtained by the network entity. The memory 920 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0157] The processor 930 may control a series of processes such that the network entity operates as described above. For example, the transceiver 910 may receive a data signal including a control signal transmitted by the terminal, and the processor 930 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

[0158] In the afore-described embodiments of the present disclosure, elements included in the present disclosure are expressed in a singular or plural form according to the embodiments. However, the singular or plural form is appropriately selected for convenience of explanation and the present disclosure is not limited thereto. As such, an element expressed in a plural form may also be configured as a single element, and an element expressed in a singular form may also be configured as plural elements.

[0159] The various actions, acts, blocks, steps, or the like in the method is performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like are omitted, added, modified, skipped, or the like without departing from the scope of the proposed method. The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by an access and mobility management function (AMF) entity in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), first information for first single network slice selection assistance information (S-NSSAI);transmitting, to the UE, second information indicating a replacement of the first S-NSSAI with second S-NSSAI; andreceiving, from the UE, a protocol data unit (PDU) session request,wherein the second S-NSSAI has a covering area of service of the first S-NSSAI.2.The method of claim 1, further comprising:applying an area restriction for the first S-NSSAI based on the second information.3.The method of claim 1,wherein the area of service for the first S-NSSAI or the area of service for the second S-NSSAI includes at least one of a tracking area or a cell.4.The method of claim 1, further comprising:transmitting, to a session management function (SMF) entity, fourth information requesting replace the first S-NSSAI with the second S-NSSAI,wherein the fourth information is for updating flag set on a number of the PDU session associated with the first S- NSSAI or the second S-NSSAI.5.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving, from an access and mobility management function (AMF) entity, first information for first single network slice selection assistance information (S-NSSAI);receiving, from the AMF entity, second information indicating a replacement of the first S-NSSAI with second S-NSSAI; andtransmitting, to the AMF entity, a protocol data unit (PDU) session request,wherein the second S-NSSAI has a covering area of service of the first S-NSSAI.6.The method of claim 5,wherein an area restriction for the first S-NSSAI is associated with the second information.7.The method of claim 5,wherein the area of service for the first S-NSSAI or the area of service for the second S-NSSAI includes at least one of a tracking area or a cell.8.An access and mobility management function (AMF) entity in a wireless communication system, the AMF entity comprising:a transceiver, anda controller coupled with the transceiver and configured to:transmit, to a user equipment (UE), first information for first single network slice selection assistance information (S-NSSAI);transmit, to the UE, second information indicating a replacement of the first S-NSSAI with second S-NSSAI; andreceive, from the UE, a protocol data unit (PDU) session request,wherein the second S-NSSAI has a covering area of service of the first S-NSSAI.9.The AMF entity of claim 8, wherein the controller is further configured to:apply an area restriction for the first S-NSSAI based on the second information.10.The AMF entity of claim 8,wherein the area of service for the first S-NSSAI or the area of service for the second S-NSSAI includes at least one of a tracking area or a cell.11.The AMF entity of claim 8, wherein the controller is further configured to:transmit, to a session management function (SMF) entity, fourth information requesting replace the first S-NSSAI with the second S-NSSAI,wherein the fourth information is for updating flag set on a number of the PDU session associated with the first S- NSSAI or the second S-NSSAI.12.A user equipment (UE) in a wireless communication system, the UE comprising:a transceiver, anda controller coupled with the transceiver and configured to:receive, from an access and mobility management function (AMF) entity, first information for first single network slice selection assistance information (S-NSSAI);receive, from the AMF entity, second information indicating a replacement of the first S-NSSAI with second S-NSSAI; andtransmit, to the AMF entity, a protocol data unit (PDU) session request,wherein the second S-NSSAI has a covering area of service of the first S-NSSAI.13.The UE of claim 12,wherein an area restriction for the first S-NSSAI is associated with the second information.14.The UE of claim 12,wherein the area of service for the first S-NSSAI or the area of service for the second S-NSSAI includes at least one of a tracking area or a cell.

Images