Method and apparatus for handling pdu session based on slice location availability in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose method for handling PDU session by SMF entity (300). The method includes receiving an indication that PDU Session is subject to area restriction for a S-NSSAI and the S-NSSAI that is related to at least one of: a partially allowed NSSAI and a NS-AoS from an AMF entity (200). Further, the method includes subscribing to the AMF entity to obtain a notification whether location of a UE (100) is inside or outside of a slice support area where the slice is not supported. Further, the method includes performing one of: at least one of: enable or disable downlink data notification and at least one of: disable or enable send a downlink user plane packet to the UE corresponding to the PDU session based on the notification received from the AMF entity about an exact location from the UE with respect to the slice support area.

Description

METHOD AND APPARATUS FOR HANDLING PDU SESSION BASED ON SLICE LOCATION AVAILABILITY IN A WIRELESS COMMUNICATION SYSTEM

[0001] The disclosure relates to a wireless communication, and more specifically related to a method and a wireless network for handling a Protocol Data Unit (PDU) session based on a slice location availability.

[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] Generally, 3rdGeneration Partnership Project (3GPP) Release 18 introduced a concept of a “Partially Network Slice Support” which means a slice is not supported in all Tracking Areas (TAs) of a Registration Area (RA), rather only supported in the few TAs of the RA. In this case, the 3GPP has provided the provision for an Access and Mobility Management Function (AMF) entity to provide a Partially Allowed Single - Network Slice Selection Assistance Information (NSSAI) along with an Allowed NSSAI during registration and a User Equipment (UE) configuration update procedure. The Partially Allowed NSSAI contains the S-NSSAIs with information of the TAs where these slices are supported. The UE directly triggers a PDU when the UE moves to the TA where the slice is supported. For the established the PDU session of an S-NSSAI part of the Partially Allowed NSSAI and the UE moves to a TA which is not part of the list of TAs associated with the S-NSSAI, the User Plane Resources for the PDU Session shall be deactivated, but the PDU session context in the UE and the SMF entity is not released. The UE and the network do not exchange any uplink and downlink data when the UE moves to a TA which is not part of a list of TAs associated with the S-NSSAI part of Partially Allowed NSSAI.

[0009] Similarly another concept of a Network Slice Area of Service (NS-AoS) has been introduced. In NS-AoS case, an operator configures resources for the Network Slices in the cells of the TAs where the Network Slices are to be available. Further, the operator configures resources for the network slices in the areas of the TAs where the network slice is defined to be not available the cells are configured with zero resources. The AMF entity receives, from an Operations, Administration, and Maintenance (OAM) entity, an information on availability of the network slice. The information when the granularity is smaller than the TA, i.e. if the NS-AoS includes the TAs where the network slice is not available in cells of the TA. During registration and the UE configuration update procedure, the AMF entity provides the slice location availability information (NS-AoS) information to the UE. When the UE moves out of the NS-AoS which means moved to a cell outside the location information of the S-NSSAI then an existing PDU session is kept and all the resources of the PDU sessions are deactivated. The UE and the network do not exchange any uplink and downlink data (both user plane and Control plane (CP) data as part of Non-access stratum (NAS) message) if the UE is out of the NS-AoS, which means moved to a cell outside the location information of the S-NSSAI.

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

[0011] The principal object of the embodiments herein is to provide a method and a wireless network for handling a PDU session based on a slice location availability.

[0012] Another objective of the embodiment herein is to provide that during the PDU session establishment associated with a Partially Allowed NSSAI and / or a NS-AoS, an AMF entity indicates to a SMF entity that the slice in the PDU session is associated with the Partially Allowed NSSAI and / or the NS-AoS.

[0013] Yet another objective of the embodiment herein is to provide that the SMF entity subscribes to a "UE mobility event notification" service provided by the AMF entity for reporting of the UE presence in an Area of Interest.

[0014] Yet another objective of the embodiment herein is to provide a notification from the AMF entity that whether the status of the UE is IN or OUT or UNKNOWN to the Partially Allowed NSSAI and / or the NS-AoS.

[0015] Yet another objective of the embodiment herein is to provide a method where the SMF entity takes action on a downlink packet that is present for the UE based on the location status of the UE.

[0016] Yet another objective of the embodiment herein is to provide the method for the SMF entity to be aware of the slices which are related to Partially Allowed NSSAI and NS-AoS. Also, the SMF entity be made aware of the exact UE's location with respect slice support area so that it can take desired action.

[0017] Accordingly, the embodiment herein discloses a method for handling a PDU session based on slice location availability in a wireless network. The method includes receiving, by a SMF entity, an indication that PDU Session is subject to area restriction for the S-NSSAI and the S-NSSAI that is related to at least one of: a partially allowed Network Slice　Selection Assistance Information (NSSAI) and a Network Slice Area of Service (NS-AoS) from an AMF entity. Further, the method includes subscribing, by the SMF entity, to the AMF entity to obtain a notification whether location of a UE is inside or outside of a slice support area where the slice is not supported. Further, the method includes performing, by the SMF entity, at least one of: enabling or disabling downlink data notification and at least one of: disabling or enabling send a downlink user plane packet to the UE corresponding to the PDU session based on the notification received from the AMF entity about an exact location of the UE with respect to the slice support area.

[0018] In various embodiments, the AMF entity provides the indication to the SMF entity, whenever AMF entity determines that the S-NSSAI of the PDU session is restricted to at least one of an NS-AoS or the S-NSSAI present in Partially Allowed NSSAI.

[0019] In various embodiments, the SMF entity subscribes to a "UE mobility event notification" event for reporting UE presence in area of interest by providing S-NSSAI to the AMF entity.

[0020] In various embodiments, when the SMF entity is notified, by the AMF entity, that a status of the location of the UE is outside the slice support area, the SMF entity does not invoke the AMF entity, if the downlink data is available for the UE and the SMF entity disables the data notification.

[0021] In various embodiments, when the SMF entity is notified, by the AMF entity, that a status of the location of the UE is inside the slice support area, the SMF entity invokes the AMF entity, if the downlink data is available for the UE and the SMF entity enables the data notification.

[0022] In various embodiments, when the SMF entity is notified, by the AMF entity, that the location of the UE status is unknown, the SMF entity activates the AMF entity based on an operator policy, wherein the whenever the SMF entity enables the data notification when a downlink data is available for the UE. The SMF entity triggers a network triggered service request procedure to activate the UP connection or send user data.

[0023] Accordingly, the embodiment herein discloses a method for handling PDU session based on slice location availability in a wireless network. The method includes receiving, by an AMF entity, an PDU session establishment request associated with at least one of: a partially allowed NSSAI and a NS-AoS from a UE. Further, the method includes sending, by the AMF entity, an indication that a PDU session is subject to area restriction for the S-NSSAI, where the S-NSSAI is related to at least one of: the partially allowed NSSAI and the NS-AoS to a SMF entity. Further, the method includes receiving, by the AMF entity, a subscribe request from the SMF entity to notify whether the UE is inside or outside of a slice support area where the slice is not supported based on the indication. Further, the method includes sending, by the AMF entity, a notify to the SMF entity to inform whether the UE is inside or outside of the slice support area where the slice is not supported based on a subscribe request.

[0024] Accordingly, the embodiment herein discloses an SMF entity for handling PDU session based on slice location availability in a wireless network. The SMF entity includes a PDU session handling controller communicatively coupled to a memory and a processor. The PDU session handling controller is configured to receive an indication that a PDU Session is subject to area restriction for a S-NSSAI and the S-NSSAI that is related to at least one of: a partially allowed NSSAI and a NS-AoS from an AMF entity. Further, the PDU session handling controller is configured to subscribe to the AMF entity to obtain a notification whether location of a UE is inside or outside of a slice support area where the slice is not supported. Further, the PDU session handling controller is configured to perform one of: at least one of: enable or disable downlink data notification and at least one of: disable or enable send a downlink user plane packet to the UE corresponding to the PDU session based on the notification received from the AMF entity about an exact location of the UE with respect to the slice support area.

[0025] Accordingly, the embodiment herein discloses an AMF entity for handling a PDU session based on slice location availability in a wireless network. The AMF entity includes a PDU session handling controller communicatively coupled to a memory and a processor. The PDU session handling controller is configured to receive a PDU session establishment request associated with at least one of: a partially allowed NSSAI and a NS-AoS from a UE. Further, the PDU session handling controller is configured to send an indication that a PDU session is subject to area restriction for the S-NSSAI, where the S-NSSAI is related to at least one of: the partially allowed NSSAI and the NS-AoS to a SMF entity. Further, the PDU session handling controller is configured to receive a subscribe request from the SMF entity to notify whether the UE is inside or outside of a slice support area where the slice is not supported based on the indication. Further, the PDU session handling controller is configured to send a notify to the SMF entity to inform whether the UE is inside or outside of the slice support area where the slice is not supported based on a subscribe request.

[0026] 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 may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

[0027] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide efficient communication methods in a wireless communication system.

[0028] These and other features, aspects, and advantages of the disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

[0029] FIG. 1 illustrates a conventional flow chart where a SMF entity is triggering service request procedure even if a UE is outside of the partially allowed NSSAI which means moves to a TA which is not part of the list of the TAs associated with the S-NSSAI part of the partially allowed NSSAI and / or the NS-AoS which means moved to a cell outside the location information of a S-NSSAI, according to the prior art;

[0030] FIG. 2 illustrates a flow chart of the SMF entity triggering a service request procedure based on a status of the UE, according to the embodiments as disclosed herein;

[0031] FIG. 3 shows various hardware components of an AMF entity, according to the embodiments as disclosed herein.;

[0032] FIG. 4 shows various hardware components of the SMF entity, according to the embodiments as disclosed herein.;

[0033] FIG. 5 is a flow chart illustrating a method, implemented by the AMF entity, for handling PDU session based on slice location availability in a wireless network, according to the embodiments as disclosed herein; and

[0034] FIG. 6 is a flow chart illustrating a method, implemented by the SMF entity, for handling PDU session based on slice location availability in the wireless network, according to the embodiments as disclosed herein.

[0035] FIG. 7 illustrates a block diagram of a user equipment that illustrates various hardware components.

[0036] FIG. 8 illustrates a block diagram of a network entity that illustrates various hardware components.

[0037] 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 one or more 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.

[0038] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a terminal and a communication method thereof in a wireless communication system.

[0039] 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 should not be construed as limiting the scope of the embodiments herein.

[0040] As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be 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 may optionally be driven by firmware and software. The circuits may, 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 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 to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0041] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be 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. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

[0042] Accordingly, the embodiment herein a method for handling a PDU session based on slice location availability in a wireless network. The method includes receiving, by a SMF entity, an indication that a PDU Session is subject to area restriction for a S-NSSAI and the S-NSSAI that is related to at least one of: a partially allowed NSSAI and a NS-AoS from an AMF entity. Further, the method includes subscribing, by the SMF entity, to the AMF entity to obtain a notification whether location of a UE is inside or outside of a slice support area where the slice is not supported. Further, the method includes performing, by the SMF entity, at least one of: enable or disable downlink data notification and at least one of: disable or enable send a downlink user plane packet to the UE corresponding to the PDU session based on the notification received from the AMF entity about an exact location of the UE with respect to the slice support area.

[0043] In various embodiments, the SMF entity needs to know whether the UE is inside or outside of the partially allowed NSSAI and / or the NS-AoS to take any decision, whenever there is any downlink packet for the UE. Hence, the SMF entity shall subscribe to a "UE mobility event notification" service provided by an AMF entity for reporting of the UE presence in an area of interest by providing the S-NSSAI associated with / present in the partial allowed NSSAI and / or NS-AoS. As the SMF entity does not know which of the S-NSSAI is associated with / present in the partially allowed NSSAI and / or the NS-AoS. The method proposes that during the PDU session establishment associated with the partially allowed NSSAI and / or the NS-AoS, the AMF entity indicates to the SMF entity that the slice in the PDU is associated with the partially allowed NSSAI and / or the NS-AoS. Based on the indication from the AMF entity, the SMF entity comes to know that the S-NSSAI associated with the partially allowed NSSAI and / or the NS-AoS and subscribes with the AMF entity. Based on the UE mobility the AMF entity notifies to the SMF entity, whether the status of the UE is IN or OUT or UNKNOWN of the partially allowed NSSAI and / or the NS-AoS, the SMF entity is proposed to take action on the downlink packet that is present for the UE for the PDU session which is deactivated that means the resources of the PDU session is released and only the PDU session is kept. If the SMF entity is notified that the UE is IN then the SMF entity stores the status and invokes the AMF entity, whenever any downlink packet is present for the UE and also to enable the data notification. If the SMF entity is notified that the UE is OUT then the SMF entity stores the status and does not invoke the AMF entity, whenever any downlink packet for the UE and also disable the data notification. If the SMF entity is notified that the UE status is UNKNOWN. Then, the SMF entity stores the status and based on operator policy the SMF entity may or may not invoke the AMF entity, whenever any downlink packet is present for UE. Also, the SMF entity may enable the data notification.

[0044] In various embodiments, if the AMF entity determines that a PDU session is associated with S-NSSAI present in the Partially Allowed NSSAI, the AMF entity indicates to the SMF entity that the PDU Session is subject to area restrictions for the S-NSSAI. As a result, the SMF entity subscribes to "UE mobility event notification" for reporting UE presence in Area of Interest by providing S-NSSAI to the AMF entity.

[0045] In various embodiments, when the SMF entity is notified by the AMF entity that the UE location is outside of the area of interest, the SMF entity shall not send user data as payload of NAS message in downlink directions and disable data notification. When the SMF entity is notified by the AMF entity that the UE location is UNKNOWN as defined in TS 23.502, then based on operator policy, the SMF entity may enable downlink data notification and trigger the Network triggered Service Request procedure to active the UP connection or send user data as payload of a NAS message when the SMF entity receives downlink data or data notification from a user plane function　(UPF) entity.

[0046] In various embodiments, when the AMF entity determines that the S-NSSAI of the PDU Session is restricted to an NS-AoS in the PDU session, the AMF entity indicates to the SMF entity that the PDU session is subject to area restriction for the S-NSSAI. As a result, the SMF entity subscribes to "UE mobility event notification" for reporting UE presence in Area of Interest by providing S-NSSAI to the AMF entity as described in clauses 5.6.11 and 5.3.4.4. When the SMF entity is notified that the UE location is outside of Area of Interest, the SMF entity shall not send user data as payload of NAS message (see clause 5.31.4.1) in downlink directions and disable data notification.

[0047] In various embodiments, when the SMF entity is notified by the AMF entity that the UE location is UNKNOWN as defined in TS 23.502, then based on the operator policy, the SMF entity may enable downlink data notification and trigger the network triggered service request procedure to active the UP connection or send user data as payload of a NAS message when the SMF entity receives downlink data or data notification from the UPF entity.

[0048] The proposed method ensures that the AMF entity and the SMF entity are correctly handling and correctly notified for any downlink data for the UE based on the slice location availability for the UE in the wireless network (e.g., fourth generation (4G) network, a fifth generation (5G) network, an Open Radio Access Network (ORAN) or the like).

[0049] Referring now to the drawings and more particularly to FIGS. 2 through 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0050] FIG. 1 illustrates a conventional flow chart where the SMF entity (300) is triggering a service request procedure even if a UE (100) is outside of a partially allowed NSSAI which means moves to a TA which is not part of a list of TAs associated with the S-NSSAI part of the partially allowed NSSAI and / or the NS-AoS which means moved to the cell outside the location information of the S-NSSAI, according to the prior art. The UE (100) may be but not limited to a laptop, 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), an Augmented reality (AR) glass, a foldable device, a flexible device, a display device and an immersive system.

[0051] FIG. 1 illustrates the call flow based on the existing TS 23.502 clause 4.2.3.3 network triggered service request procedure. The flow illustrates that the network resource and the radio resource are wasted as the UE (100) is out of the partially allocated NSSAI and / or the NS-AoS. The SMF entity (300) should not have triggered the service request procedure when the UE (100) is out of the partially allocated NSSAI and / or the NS-AoS.

[0052] Further, when the UE (100) moves out of the partially allowed NSSAI or the NS-AoS, the PDU session is kept but only the resources of the PDU sessions is deactivated. During the PDU session, there is no exchange of the uplink and the downlink data both in user plane and control plane (CP-DATA). But, the SMF entity (300) is not aware whether the UE (100) is inside or outside of the partially allowed NSSAI and / or the NS-AoS, when the downlink date is received for the UE (100). Hence, the SMF entity (300) invokes the AMF entity (200) to indicate the downlink packet for the UE (100) and subsequently the AMF entity (200) needs to trigger a paging for the UE (100) when the UE (100) is in the CM-IDLE state. But, in the end, the UE (100) cannot activate the PDU as the UE (100) determines that the UE (100) is out of the partially allowed NSSAI and / or the NS-AoS. Thus, the network resources and radio resources are completely wasted, that is repeated whenever any downlink packet comes for the UE (100). Similarly, if the SMF entity (300) blocks the downlink packet without knowing whether the UE (100) is inside or outside of the partially allowed NSSAI and / or the NS-AoS. Then, blocking the downlink packet is wrong as the UE (100) need to receive the downlink packet, if the UE (100) is inside the partially allowed NSSAI and / or the NS-AoS.

[0053] At step 1, the UE (100) is already registered and the AMF entity (200) has already provided partially allowed NSSAI and / or NS-AoS information to the UE (100). At step 2, the UE (100) is having one PDU session associated with the partially allowed NSSAI and / or NS-AoS and presently the PDU session is deactivated. At step 3, the UPF entity (400) receives the downlink data. At step 4a, the UPF entity (400) sends the data notification to the SMF entity (300). At step 4b, the SMF entity (300) sends the data notification acknowledgment to the UPF entity (400). At step 4c, the UPF entity (400) sends the downlink data to the SMF entity (300). At step 5a, the SMF entity (300) sends a Namf_Communication_N1N2MessageTransfer to the AMF entity (200). At step 5b, the AMF entity (200) sends the Namf_Communication_N1N2Message transfer response SMF entity (300). At step 5c, the SMF entity (300) sends the failure indication to the UPF entity (400).

[0054] At step 6, the AMF entity (200) pages (if the UE (100) is in the CM-IDLE) or sends the message (if the UE (100) is CM-CONNECTED in the access associated with the PDU session ID received from the SMF entity (300) to the UE (100). At step 7, the UE (100) wont trigger the service request procedure if the UE (100) is OUT of partially allowed NSSAI and / or NS-AoS.

[0055] FIG. 2 illustrates a flow chart of the SMF entity (300) triggering the service request procedure based on the status of the UE (100) in a wireless network (1000), according to the embodiments as disclosed herein.

[0056] Referring to the FIG. 2, illustrates the call flow based on the existing TS 23.502 clause 4.2.3.3 network triggered service request procedure. At step 1, the UE (100) is already registered and the AMF entity (200) has already provided the partially allowed NSSAI and / or the NS-AoS information to the UE (100). Then, at step 2, the UE (100) sends the PDU session establishment request associated with the partially allowed NSSAI and / or the NS-AoS to the AMF entity (200). At step 3, the AMF entity (200) sends a Nsmf_PDU Session_createSMContext Request to the SMF entity (300)with an indication that the S-NSSAI is associated with the Partially Allowed NSSAI and / or the NS-AoS. At step 4, based on the indication, the SMF entity (300) sends a Namf_EventExposure_subscribe to subscribe "UE mobility event notification" that reports the UE presence in the area of interest to the AMF entity (200) by providing the S-NSSAI associated with / present in the Partial Allowed NSSAI and / or the NS-AoS.

[0057] At step 5, when the UE (100) moves out of the partially NSSAI and / or the NS-AoS then as per the existing procedure the PDU session is deactivated. Further, at step 6 and step 7a, whenever the UPF entity (400) receives a downlink data, and sends data notification to the SMF entity (300). At step 7b, the UPF entity (400) receives the data notification ACK and the SMF entity (300) receives the downlink data that was previously received by the UPF entity (400) at step 7c.

[0058] In various embodiments, at step 8, when the SMF entity (300) is notified that the status of the UE (100) is IN, then the SMF entity (300) stores the status and invoke the AMF entity (200), if any downlink data is available for the UE (100). In various embodiments, when the SMF entity (300) is notified that the status of the UE (100) is OUT, then the SMF entity (300) stores the status and does not invoke the AMF entity (200), if any downlink data is available for the UE (100). Also, the SMF entity (300) disables the data notification.

[0059] In various embodiments, when the SMF entity (300) is notified that the UE status is UNKNOWN, then the SMF entity (300) stores the status and based on the operator's policy the SMF entity (300) may / may not invoke the AMF entity (200), whenever any downlink data is available for the UE (100). Also, the SMF entity (300) enables the data notification.

[0060] In various embodiments, during the PDU session establishment if the S-NSSAI associated with / present in the Allowed NSSAI and / or the NS-AoS, the AMF entity (200) indicates to the SMF entity (300) associated with the partially allowed and / or the NS-AoS.

[0061] In various embodiments, the SMF entity (300) subscribes to the "UE mobility event notification" for reporting the UE presence in the area of interest by providing the S-NSSAI associated with the partially allowed NSSAI and / or the NS-AoS to the AMF entity (200). The SMF entity (300) may decide to subscribe when the PDU session gets deactivated instead of the PDU session establishment.

[0062] In various embodiments, the AMF entity (200) shall notify with the UE status as "IN" or "OUT" or "UNKNOWN" to the SMF entity (300) based on the UE's mobility.

[0063] In various embodiments, if the SMF entity (300) is notified that the UE (100) is IN then the SMF entity (300) stores the status and invokes the AMF entity (200), if there is any downlink packet for the UE (100) and also enable the data notification.

[0064] In various embodiments, if the SMF entity (300) is notified that the UE (100) is OUT then the SMF entity (300) stores the status and will not invoke the AMF entity (200), if there is any downlink packet and also disable the data notification. Also, the SMF entity (300) may notify the UPF entity (400) (that originate the Data Notification) to discard the downlink data for the PDU Sessions and / or to not provide further data notification messages.

[0065] In various embodiments, if the SMF entity (300) is notified that the UE status is UNKNOWN then the SMF entity (300) stores the status and based on operator policy the SMF entity (300) may or may not invoke the AMF entity (200), whenever there is any downlink packet. Also, the SMF entity (300) enables the data notification.

[0066] In various embodiments, the AMF entity (200) checks the S-NSSAI of the PDU if the AMF entity (200) receives messages that there is downlink packet for the UE (100) from the SMF entity (300). If the S-NSSAI is associated with the partially allowed and / or the NS-AoS and the AMF entity (200) finds that the UE (100) is OUTSIDE of the TA. Then, the AMF entity (200) does not trigger paging if the UE (100) is in the CM-IDLE, or the AMF entity (200) does not forward the message if the UE (100) is in the CM-CONNECTED. The AMF entity (200) informs back to the SMF entity (300) saying that the message can't be forwarded to the UE (100). The AMF entity (200) includes the error cause as the UE (100) is OUTSIDE of the partially allowed NSSAI and / or the NS-AoS.

[0067] FIG. 3 shows various hardware components of the AMF entity (200), according to the embodiments as disclosed herein. In various embodiments, the AMF entity (200) includes a processor (210), a communicator (220), a memory (230) and a PDU session handling controller (240). The processor (210) is coupled with the communicator (220), the memory (230) and the PDU session handling controller (240).

[0068] The PDU session handling controller (240) receive the PDU session establishment request associated with at least one of: the partially allowed NSSAI and the NS-AoS from the UE (100). Further, the PDU session handling controller (240) sends the indication that the PDU session is subject to area restriction for the S-NSSAI, where the S-NSSAI is related to at least one of: the partially allowed NSSAI and the NS-AoS to the SMF entity (300). Further, the PDU session handling controller (240) receives the subscribe request from the SMF entity (300) to notify whether the UE (100) is inside or outside of the slice support area where the slice is not supported based on the indication. Further, the PDU session handling controller (240) sends the notify to the SMF entity (300) to inform whether the UE (100) is inside or outside of the slice support area where the slice is not supported based on the subscribe request.

[0069] The PDU session handling controller (240) is 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 may optionally be driven by firmware.

[0070] The processor (210) may include one or a plurality of processors. The one or the plurality of processors may 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (210) may include multiple cores and is configured to execute the instructions stored in the memory (230).

[0071] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator (220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (230) may, in some examples, 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 a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0072] In various embodiments, the communicator (220) includes an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (220) is configured to communicate internally between internal hardware components of the UE (100) and with external devices via one or more networks.

[0073] Although the FIG. 3 shows various hardware components of the AMF entity (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the AMF entity (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the AMF entity (200).

[0074] FIG. 4 shows various hardware components of the SMF entity (300), according to the embodiments as disclosed herein. In various embodiments, the SMF entity (300) includes a processor (310), a communicator (320), a memory (330) and a PDU session handling controller (340). The processor (310) is coupled with the communicator (320), the memory (330) and the PDU session handling controller (340).

[0075] The PDU session handling controller (340) receives the indication that the PDU session is subject to area restriction for the S-NSSAI. The S-NSSAI is related to at least one of: the partially allowed NSSAI and the NS-AoS from the AMF entity (200). Further, the PDU session handling controller (340) subscribes to the AMF entity (200) to obtain the notification whether the location of the UE (100) is inside or outside of the slice support area where the slice is not supported. Further, the PDU session handling controller (340) performs at least one of: enables or disables the downlink data notification and at least one of: disables or enables send a downlink user plane packet to the UE (100) corresponding to the PDU session based on the notification received from the AMF entity (200) about an exact location from the UE (100) with respect to the slice support area.

[0076] In various embodiments, the AMF entity (200) provides the indication to the SMF entity (300), whenever the AMF entity (200) determines that the S-NSSAI of the PDU session is restricted to at least one of the NS-AoS or the S-NSSAI present in partially allowed NSSAI.

[0077] Further, the PDU session handling controller (340) subscribes to a "UE mobility event notification" event for reporting UE presence in area of interest by providing S-NSSAI to the AMF entity (200).

[0078] In various embodiments, when the SMF entity (300) is notified, by the AMF entity (200), that the status of the location of the UE (100) is outside the slice support area, the PDU session handling controller (340) does not invoke the AMF entity (200), if the downlink data is available for the UE (100) and the SMF entity (300) disables the data notification.

[0079] In various embodiments, when the SMF entity (300) is notified, by the AMF entity (200), that the status of the UE (100) is inside the slice support area, the PDU session handling controller (340) invokes the AMF entity (200), if the downlink data is available for the UE (100) and the SMF entity (300) enables the data notification.

[0080] In various embodiments, when the SMF entity (300) is notified, by the AMF entity (200), that the UE status is unknown, the PDU session handling controller (340) activates the AMF entity (200) based on the operator policy. Whenever the SMF entity (300) enables the data notification when the downlink data is available for the UE (100). Further, the PDU session handling controller (340) triggers the network triggered service request procedure to activate the UP connection or send user data.

[0081] The PDU session handling controller (340) is 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 may optionally be driven by firmware.

[0082] The processor (310) may include one or a plurality of processors. The one or the plurality of processors may 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (310) may include multiple cores and is configured to execute the instructions stored in the memory (330).

[0083] Further, the processor (310) is configured to execute instructions stored in the memory (330) and to perform various processes. The communicator (320) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (330) also stores instructions to be executed by the processor (310). The memory (330) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (330) may, in some examples, 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 a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (330) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0084] In various embodiments, the communicator (320) includes an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (320) is configured to communicate internally between internal hardware components of the UE (100) and with external devices via one or more networks.

[0085] Although the FIG. 4 shows various hardware components of the SMF entity (300) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the SMF entity (300) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the SMF entity (300).

[0086] FIG. 5 is a flow chart (S500) illustrating a method, implemented by the AMF entity (200), for handling the PDU session based on the slice location availability in the wireless network (1000), according to the embodiments as disclosed herein. The operations (S502- S508) are handled by the PDU session handling controller (240).

[0087] At S502, the method includes receiving the PDU session establishment request associated with at least one of: the partially allowed NSSAI and the NS-AoS from the UE (100). At S504, the method includes sending the indication that the PDU session is subject to area restriction for the S-NSSAI where the S-NSSAI is related to at least one of: the partially allowed NSSAI and the NS-AoS to the SMF entity (300). At S506, the method includes receiving the subscribe request from the SMF entity (300) to notify whether the UE (100) is inside or outside of the slice support area where the slice is not supported based on the indication. At S508, the method includes sending the notify to the SMF entity (300) to inform whether the UE (100) is inside or outside of the slice support area where the slice is not supported based on a subscribe request.

[0088] FIG. 6 is a flow chart (S600) illustrating a method, implemented by the SMF entity (300), for handling PDU session based on the slice location availability in the wireless network (1000), according to the embodiments as disclosed herein. The operations (S602-S606) are handled by the PDU session handling controller (340).

[0089] At S602, the method includes receiving the indication that a PDU Session is subject to area restriction for a S-NSSAI and the S-NSSAI that is related to at least one of: the partially allowed NSSAI and the NS-AoS from the AMF entity (200). At S604, the method includes subscribing to the AMF entity (200) to obtain the notification whether the location of the UE (100) is inside or outside of the slice support area where the slice is not supported. At S606, the method includes performing at least one of: enabling or disabling the downlink data notification and at least one of: disabling or enabling send the downlink user plane packet to the UE (100) corresponding to the PDU session based on the notification received from the AMF entity (200) about the exact location from the UE (100) with respect to the slice support area.

[0090] FIG. 7 illustrates a block diagram of a user equipment (UE) that illustrates various hardware components.

[0091] 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. Furthermore, the UE of FIG. 7 corresponds to the UE of the FIG. 1 or the FIG.2.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] FIG. 8 illustrates a block diagram of a network entity that illustrates various hardware components.

[0097] Referring to FIG. 8, the network entity includes a transceiver (810), a memory (820), and a processor (830). The transceiver (810), the memory (820), and the processor (830) 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 fewer or a greater number of 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.

[0098] The network entity includes at least one entity of a core network. For example, the network entity includes a base station (BS), an Access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a network repository function (NRF), a user plane function (UPF), a network slicing selection function (NSSF), an authentication server function (AUSF), a unified data management (UDM) and a network exposure function (NEF), but the network entity is not limited thereto. the network entity may correspond to a network apparatus of FIG. 3 or FIG.4.

[0099] The transceiver (810) collectively refers to a network entity receiver and a network entity transmitter, and may transmit / receive a signal to / from a base station or a UE. The signal transmitted or received to or from the base station or the UE may include control information and data. In this regard, the transceiver (810) may include an RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and an 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.

[0100] 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.

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

[0102] The processor (830) may control a series of processes such that the network entity operates as described above. For example, the transceiver (810) may receive a data signal including a control signal, and the processor (830) may determine a result of receiving the data signal.

[0103] The various actions, acts, blocks, steps, or the like in the flow charts (S500 and S600) may be 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 may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0104] In various embodiments, a method for handling Protocol Data Unit (PDU) session based on slice location availability in a wireless network (1000), comprising: receiving, by a Session Management Function (SMF) entity (300), an indication that the PDU session is subject to area restriction for a Single - Network Slice Selection Assistance Information (S-NSSAI) wherein the S-NSSAI is related to at least one of: a partially allowed Network Slice Selection Assistance Information (NSSAI) and a Network Slice Area of Service (NS-AoS) from an Access and Mobility Management Function (AMF) entity (200); subscribing, by the SMF entity (300), to the AMF entity (200) to obtain a notification whether location of a User Equipment (UE) (100) is inside or outside of a slice support area where the slice is not supported; and performing, by the SMF entity (300), at least one of: enable or disable downlink data notification and at least one of: disable or enable send a downlink user plane packet to the UE (100) corresponding to the PDU session based on the notification received from the AMF entity (200) about the exact location of the UE (100) with respect to the slice support area.

[0105] In various embodiments, the AMF entity (200) provides the indication to the SMF entity (300), whenever the AMF entity (200) determines that the S-NSSAI of the PDU session is restricted to at least one of an NS-AoS or the S-NSSAI present in Partially Allowed NSSAI.

[0106] In various embodiments, the SMF entity (300) subscribes to a "UE mobility event notification" event for reporting UE presence in area of interest by providing S-NSSAI to the AMF entity (200).

[0107] In various embodiments, when the SMF entity (300) is notified, by the AMF entity (200), that a status of the location of the UE (100) is outside in the slice support area, the SMF entity (300) does not invoke the AMF entity (200), if the downlink data is available for the UE (100) and the SMF entity (300) disables the data notification.

[0108] In various embodiments, when the SMF entity (300) is notified, by the AMF entity (200), that a status of the location of the UE (100) is inside the slice support area, the SMF entity (300) invokes the AMF entity (200), if the downlink data is available for the UE (100) and the SMF entity (300) enables the data notification.

[0109] In various embodiments, when the SMF entity (300) is notified, by the AMF entity (200), that the location of the UE status is unknown, the SMF entity (300) activates the AMF entity (200) based on an operator policy, wherein whenever the SMF entity (300) enables the data notification when a downlink data is available for the UE (100), and wherein SMF entity (300) triggers a network triggered service request procedure to activate the UP connection or send user data.

[0110] In various embodiments, A method for handling Protocol Data Unit (PDU) session based on slice location availability in a wireless network (1000), comprising: receiving, by Access and Mobility Management Function (AMF) entity (200), a PDU session establishment request associated with at least one of: a partially allowed Network Slice Selection Assistance Information (NSSAI) and a Network Slice Area of Service (NS-AoS) from a User Equipment (UE) (100); sending, by the AMF entity (200), an indication that the PDU Session is subject to area restriction for the S-NSSAI and the S-NSSAI that is related to at least one of: the partially allowed NSSAI and the NS-AoS to a Session Management Function (SMF) entity (300); receiving, by the AMF entity (200), a subscribe request from the SMF entity (300) to notify whether the UE (100) is inside or outside of a slice support area where the slice is not supported based on the indication; and sending, by the AMF entity (200), a notify to the SMF entity (300) to inform whether the UE (100) is inside or outside of the slice support area where the slice is not supported based on the subscribe request.

[0111] In various embodiments, the notification is a UE mobility event notification.

[0112] In various embodiments, A Session Management Function (SMF) entity (300) for handling Protocol Data Unit (PDU) session based on slice location availability in a wireless network (1000), comprising: a memory (330); a processor (310); and a PDU session handling controller (340), communicatively coupled to the memory (330) and the processor (310), configured to: receive an indication that a PDU Session is subject to area restriction for a Single - Network Slice Selection Assistance Information (S-NSSAI) and the S-NSSAI that is related to at least one of: a partially allowed Network Slice Selection Assistance Information (NSSAI) and a Network Slice Area of Service (NS-AoS) from an Access and Mobility Management Function (AMF) entity (200); subscribe to the AMF entity (200) to obtain a notification whether location of a User Equipment (UE) (100) is inside or outside of a slice support area where the slice is not supported; and perform one of: at least one of: enable or disable downlink data notification and at least one of: disable or enable send a downlink user plane packet to the UE (100) corresponding to the PDU session based on the notification received from the AMF entity (200) about an exact location of the UE (100) with respect to the slice support area.

[0113] In various embodiments, An Access and Mobility Management Function (AMF) entity (200) for handling Protocol Data Unit (PDU) session based on slice location availability in a wireless network (1000), comprising: a memory (230); a processor (210); and a PDU session handling controller (240), communicatively coupled to the memory (230) and the processor (210), configured to: receive a PDU session establishment request associated with at least one of: a partially allowed Network Slice Selection Assistance Information (NSSAI) and a Network Slice Area of Service (NS-AoS) from a User Equipment (UE) (100); send an indication that PDU Session is subject to area restriction for the S-NSSAI and the S-NSSAI that is related to at least one of: the partially allowed NSSAI and the NS-AoS to a Session Management Function (SMF) entity (300); receive a subscribe request from the SMF entity (300) to notify whether the UE (100) is inside or outside of a slice support area where the slice is not supported based on the indication; and send a notify to the SMF entity (300) to inform whether the UE (100) is inside or outside of the slice support area where the slice is not supported based on the subscribe request.

[0114] 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 should and 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 a session management function (SMF) entity in a wireless communication system, the method comprising:receiving, from an access and mobility management function (AMF) entity, an indication that a protocol data unit (PDU) session is subject to an area restriction for single network slice selection assistance information (S-NSSAI);transmitting, to the AMF entity, the S-NSSAI to subscribe a user equipment (UE) mobility event notification for reporting UE presence in area of interest; andreceiving, from the AMF entity, a notification associated with a location of the UE for the area of interest,enabling or disabling a data notification, based on the notification.2.The method of claim 1,wherein, in case that the notification indicates that the location of the UE is outside of the area of interest, the data notification is disabled.3.The method of claim 1,wherein, in case that the notification indicates that the location of the UE is unknown, the data notification is enabled.4.The method of claim 1,wherein the S-NSSAI is related to at least one of a partial allowed NSSAI and a network slice area of service (NS-AoS).5.A method performed by an access and mobility management function (AMF) entity in a wireless communication system, the method comprising:transmitting, to a session management function (SMF) entity, an indication that a protocol data unit (PDU) session is subject to an area restriction for single network slice selection assistance information (S-NSSAI);receiving, from the SMF entity, the S-NSSAI for subscribing a user equipment (UE) mobility event notification for reporting UE presence in area of interest; andtransmitting, to the SMF entity, a notification associated with a location of the UE for the area of interest,wherein, based on the notification, a data notification is enabled or disabled.6.The method of claim 5,wherein, in case that the notification indicates that the location of the UE is outside of the area of interest, the data notification is disabled.7.The method of claim 5,wherein, in case that the notification indicates that the location of the UE is unknown, the data notification is enabled.8.The method of claim 5,wherein the S-NSSAI is related to at least one of a partial allowed NSSAI and a network slice area of service (NS-AoS).9.A session management function (SMF) entity in a wireless communication system, the SMF entity comprising:a transceiver; anda controller coupled with the transceiver and configured to:receive, from an access and mobility management function (AMF) entity, an indication that a protocol data unit (PDU) session is subject to an area restriction for single network slice selection assistance information (S-NSSAI);transmit, to the AMF entity, the S-NSSAI to subscribe a user equipment (UE) mobility event notification for reporting UE presence in area of interest; andreceive, from the AMF entity, a notification associated with a location of the UE for the area of interest,enable or disable a data notification, based on the notification.10.The SMF entity of claim 9,wherein, in case that the notification indicates that the location of the UE is outside of the area of interest, the data notification is disabled.11.The SMF entity of claim 9,wherein, in case that the notification indicates that the location of the UE is unknown, the data notification is enabled.12.The SMF entity of claim 9,wherein the S-NSSAI is related to at least one of a partial allowed NSSAI and a network slice area of service (NS-AoS).13.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 session management function (SMF) entity, an indication that a protocol data unit (PDU) session is subject to an area restriction for single network slice selection assistance information (S-NSSAI);receive, from the SMF entity, the S-NSSAI for subscribing a user equipment (UE) mobility event notification for reporting UE presence in area of interest; andtransmit, to the SMF entity, a notification associated with a location of the UE for the area of interest,wherein, based on the notification, a data notification is enabled or disabled.14.The AMF entity of claim 13,wherein, in case that the notification indicates that the location of the UE is outside of the area of interest, the data notification is disabled, andwherein, in case that the notification indicates that the location of the UE is unknown, the data notification is enabled.15.The AMF entity of claim 13,wherein the S-NSSAI is related to at least one of a partial allowed NSSAI and a network slice area of service (NS-AoS).

Images