Techniques for session management signaling supported by partial network slices in registration area

Abstract

Aspects of the present disclosure relate to techniques for session management signaling supported by partial network slices in a registration area. An apparatus (800) is configured to: receive a first session management (SM) message for a protocol data unit (PDU) session associated with a network slice and a user equipment (UE); determining that the network slice is not supported or unavailable in a location area of the UE; and transmitting a second SM message and an indication that the network slice is not supported or unavailable in the location area of the UE.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly, to techniques for session management signaling for partial network slice support in a registration area. Background Art

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE) or other appropriate terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system, such as time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other appropriate radio access technologies above 5G (e.g., sixth generation (6G)). Summary of the Invention

[0003] The article "a" before an element is not limited and should be understood to mean "at least one" of those elements or "one or more" of those elements. The terms "one", "at least one", "one or more" and "at least one of one or more" are interchangeable. As used herein (included in the claims), as used in a project list (for example, a project list preceded by phrases such as "at least one of..." or "one or more of..." or "one or both of..."), the "or" indicates an inclusive list, so that (for example) a list of at least one of A, B or C means A or B or C or AB or AC or BC or ABC (that is, A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a set of closed conditions. For example, the exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least in part based on". Furthermore, as used herein, including in the claims, a "set" may comprise one or more elements.

[0004] Some embodiments of the methods and apparatus described herein may include means for transmitting signaling of a session management (SM) procedure for an established protocol data unit (PDU) session associated with a network slice that is not supported or available in a location area of ​​the UE; receiving a non-access stratum (NAS) SM message as part of the SM procedure for the PDU session; and performing actions based on the NAS SM message without initiating activation of user plane resources for the PDU session.

[0005] In some embodiments of the methods and apparatus described herein, components may be included for receiving a first SM message for a PDU session associated with a network slice and a UE, components for determining that the network slice is not supported or is not available in a location area of ​​the UE, and components for transmitting a second SM message and an indication that the network slice is not supported or is not available in the location area of ​​the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 Illustrated is an example of a wireless communication system in accordance with aspects of the present disclosure.

[0007] Figure 2 The illustrations illustrate an example of a system setup for network slicing and specific UE requests according to various aspects of the present disclosure.

[0008] Figure 3 Illustrated are exemplary signal flows for a UE-initiated NAS SM signaling procedure for a PDU session in accordance with aspects of the present disclosure.

[0009] Figure 4 Illustrated is an exemplary signal flow for a network initiated NAS SM signaling procedure for a PDU session according to aspects of the present disclosure.

[0010] Figure 5 Illustrated are exemplary signal flows for rejecting activation of user plane (UP) resources for a PDU session when the UE is outside the support / availability of single network slice selection assistance information (S-NSSAI) in accordance with aspects of the present disclosure.

[0011] Figure 6 Illustrated is an example of a UE in accordance with aspects of the present disclosure.

[0012] Figure 7 An example of a processor according to aspects of the present disclosure is illustrated.

[0013] Figure 8 An example of network equipment (NE) according to aspects of the present disclosure is illustrated.

[0014] Figure 9 A flow chart illustrating a method performed by a UE according to aspects of the present disclosure is illustrated.

[0015] Figure 10 A flow chart illustrating a method performed by a NE according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0016] In 5G networks, network slices span the radio access network (RAN) and the core network (CN), such as the 5G core network (5GC). Generally speaking, network slices can be deployed on cells or tracking areas (TAs), which will meet the service requirements of network slice customers / users who request network slice deployment. With the development of 5G and various deployments (such as non-public networks (NPNs)), there is a need to deploy some network slices in a single TA or a limited set of TAs. A network may have 1) network slices supported in all tracking areas (e.g., throughout the network coverage area), 2) network slices supported in some tracking areas, or 3) network slices operating in a single TA.

[0017] Even if network slicing is supported in a single TA or a group of TAs, the network slice can be used as a single cell or a group of cells as part of the TA. As used herein, network slice "availability" may refer to the network resources (e.g., including radio resources, core network resources, and transport and computing resources) required to meet the service requirements of the network slice. In this embodiment, the network slice service area (NS-AoS) does not match the deployed TA that supports the network slice. In other words, the single network slice selection assistance information (S-NSSAI) location availability information defines additional restrictions on the use of S-NSSAI in TAs where the network slice availability does not match the TA boundaries.

[0018] According to the 5G specifications, such as in 3GPP TS 23.501 V18.1.0 and TS 23.502 V18.2.0 (both incorporated herein by reference), the 5GC creates and configures a set of allowed network slices (i.e., identified by allowed NSSAI) for the UE, which is described as the S-NSSAI in the allowed NSSAI being available in all TAs of the registration area (RA). Neighboring TAs that support the allowed NSSAI can be allocated to the same RA.

[0019] The UE may also be configured with a set of partially allowed network slices (e.g., partially allowed NSSAIs), which indicate the S-NSSAI values ​​that the UE can use in the serving public land mobile network (PLMN) or standalone non-public network (SNPN) in some TAs in the current RA. Each S-NSSAI in the partially allowed NSSAI is associated with a list of TAs that support the S-NSSAI.

[0020] This network slice configuration is sent to the UE using a NAS Registration Accept message or a NAS UE Configuration Update Command message. In addition to the partially allowed NSSAI, the Access and Mobility Management Function (AMF) may also include the corresponding mapping information of the S-NSSAI in the partially allowed NSSAI to the HPLMN S-NSSAI.

[0021] When the AMF creates a RA with one or more TAs, the S-NSSAI in the allowed NSSAI is supported in the TA of the RA. If the UE's requested NSSAI contains an S-NSSAI that is supported in the current TA but not supported in other TAs of the possible RA, the AMF may create an appropriate RA taking into account the expected paging load and the load due to mobility registration update (MRU) requests, and the AMF includes the S-NSSAI in the partially allowed NSSAI. Additional assistance information is associated with the S-NSSAI, which indicates a list of TAs that support the S-NSSAI.

[0022] The 5GC (e.g., AMF) may send one or more of the following elements related to the UE's network slice configuration to the UE in a Registration Accept message (in the case of a UE Registration procedure) or in a UE Configuration Update Command message (in the case of a UE Configuration Update procedure): Allowed NSSAI, Partially Allowed NSSAI, Configured NSSAI, Rejected NSSAI, or Pending NSSAI. NSSAI is a list of one or more S-NSSAIs. Each S-NSSAI in the partially allowed NSSAI may be associated with a list of TAs that support the S-NSSAI (which is a subset of the TAI list that forms the RA).

[0023] However, it may not be clear whether the UE or the network can release or modify the PDU Session. If the UE sends an UL NAS transfer message containing a 5G SM message associated with the S-NSSAI, the AMF may not know the type of SM message, for example, whether it activates UP resources or releases the PDU Session. The AMF does not know whether to reject the NAS transfer procedure (for example, reject the NAS Mobility Management (MM) Transfer message) or forward the NAS SM message to the Session Management Function (SMF).

[0024] The current specification may not allow activating UP resources in TAs outside the list of TAs supporting S-NSSAI. However, the behavior of the PDU session management procedures, such as the behavior of the SM signaling used to control the PDU session context in the UE and SMF (e.g., for PDU session release or modification), is not specified.

[0025] In other words, when a network slice is part of a partially allowed NSSAI, the UE may not activate UP resources for any PDU session associated with the S-NSSAI. However, there is no solution that describes the behavior of the UE and the network (e.g., AMF or SMF) when SM is to be performed for such a PDU session.

[0026] For the above situation, the following solution is proposed. In one embodiment, at the UE location in the RA, when the associated S-NSSAI is included in the partially allowed NSSAI or if the NS-AoS for the S-NSSAI is applicable (e.g., configured) so that the NAS SM procedure can be performed independently (whether 1) the UE is located in an area where the S-NSSAI is supported or available or 2) the UE is located in an RA in an area where the S-NSSAI is not supported or available), the UE or the network (e.g., AMF or SMF) may initiate and perform the SM procedure (e.g., 5G SM message transmission procedure) for the established PDU session. Various aspects of the present disclosure are described in the context of a wireless communication system.

[0027] Figure 1 The diagram illustrates an example of a wireless communication system 100 according to various aspects of the present disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, an Advanced 5G (5G-A) network, or a 5G Ultra-Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), or IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0028] One or more NEs 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, RAN, NodeB, eNodeB (eNB), next generation NodeB (gNB), or other appropriate terminology. The NEs 102 and the UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, the NEs 102 and the UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0029] NE 102 may provide a geographic coverage area, and NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, NE 102 and UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) based on one or more radio access technologies. In some embodiments, NE 102 may be mobile, such as a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas may be associated with different NE 102.

[0030] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, a UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally or alternatively, a UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples.

[0031] The UE 104 may be capable of supporting wireless communication directly with other UEs 104 via a communication link. For example, the UE 104 may support wireless communication directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communication directly with another UE 104 via a PC5 interface.

[0032] NE 102 may support communication with CN 106, with another NE 102, or with both. For example, NE 102 may interface with other NEs 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some embodiments, one or more NEs 102 may include subcomponents such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0033] The CN 106 may support user authentication, access authorization, tracking, connection, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and user plane entities that route packets or interconnections to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signaling bearer, etc.) for one or more UEs 104 served by one or more NEs 102 associated with the CN 106.

[0034] The CN 106 may communicate with a packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. The UE 104 may establish a session (e.g., a PDU session, etc.) with the CN 106 via the NE 102. The CN 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server. A PDU session may be an instance of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0035] In the wireless communication system 100, the NE 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the NE 102 and the UE 104 may support different resource structures. For example, the NE 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the NE 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the NE 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The NE 102 and the UE 104 may support various frame structures based on one or more numerologies.

[0036] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second parameter set (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third parameter set (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0037] The time intervals of resources (e.g., communication resources) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, such as a duration of 10 milliseconds (ms). In some embodiments, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, such as a duration of 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0038] Additionally or alternatively, time intervals of resources (e.g., communication resources) may be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first parameter set, the second parameter set, the third parameter set, the fourth parameter set, and the fifth parameter set (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on the parameter set. It should be understood that references to a first parameter set (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0039] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as the frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, the NE 102 and the UE 104 can perform wireless communications on one or more of the operating frequency bands. In some embodiments, FR1 can be used by the NE 102 and the UE 104, as well as other equipment or devices for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by NEs 102 and UEs 104, as well as other equipment or devices for short-range, high data rate capabilities.

[0040] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set (e.g., μ = 0) including a 15 kHz subcarrier spacing, a second parameter set (e.g., μ = 1) including a 30 kHz subcarrier spacing, and a third parameter set (e.g., μ = 2) including a 60 kHz subcarrier spacing. FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set (e.g., μ = 2) including a 60 kHz subcarrier spacing, and a fourth parameter set (e.g., μ = 3) including a 120 kHz subcarrier spacing.

[0041] Figure 2 Illustrated is an example of a system setup for network slicing and specific UE requests according to various aspects of the present disclosure. In particular, Figure 2 The diagram illustrates an example deployment using TA1 202, TA2 204, and TA3 206. TA1 202 supports S-NSSAI #1, TA2 204 supports S-NSSAI #1 and S-NSSAI #2, and TA3 206 supports S-NSSAI #1. UE 208 is located in TA2 204 and sends a requested NSSAI containing S-NSSAI #1 and S-NSSAI #2. The 5GC (e.g., AMF and / or NSSF) assumes that UE 208 is currently located in TA2 204 and that TA2 204 supports S-NSSAI #1 and S-NSSAI #2, while the neighbors TA1 202 and TA3 206 only support S-NSSAI #1. Therefore, the AMF may assign RA 210 including TA1 202, TA2 204, and TA3 206, and the AMF may send a Registration Accept message to UE 208, wherein the Registration Accept message includes: RA 210, TA1 202, TA2 204, TA3 206; allowed NSSAI, which includes S-NSSAI #1; partially allowed NSSAI, which includes S-NSSAI #2, the associated list of TAs that support the S-NSSAI #2 and only includes TA2 204; and rejected NSSAI, which does not include anything.

[0042] When UE 208 has established a PDU session with the S-NSSAI portion of the partially allowed NSSAI, UE 208 is allowed to activate UP resources for the PDU session only when UE 208 is in the TA portion of the TA list associated with each S-NSSAI where S-NSSAI is supported.

[0043] However, if the UE is outside the TA list (where S-NSSAI is supported) or if the UE is outside the S-NSSAI availability area (e.g., network slice service area), it is unclear whether the UE or the network can initiate and perform session management procedures (e.g., release or modification procedures) for the established PDU session. If the UE sends an UL NAS transfer message containing a 5GSM message associated with S-NSSAI, the AMF does not know the type of SM message, i.e., whether to activate UP resources or release the PDU session. The AMF does not know whether to reject the NAS transfer procedure (e.g., reject the NAS MM transfer message) or forward the NAS SM message to the SMF.

[0044] The following describes a solution to the aforementioned problem of the current state of the art. For the solution described herein, please note that in this disclosure, the term 'support' of S-NSSAI means that S-NSSAI is deployed in an area, such as a tracking area (TA), which is related to the network slicing feature known as "partial network slicing support in a registration area." On the other hand, the term 'available' S-NSSAI means that sufficient resources are allocated for S-NSSAI in a given area, such as a set of cells, which is related to the network slicing feature known as "network slice service area does not match the deployed tracking area." In other words, network slicing (e.g., S-NSSAI and network slicing are used interchangeably) may be supported in a TA (e.g., in all cells of the TA), but S-NSSAI may only be available in one or more cells of the TA where sufficient network resources are allocated to meet the service requirements of the network slice. This S-NSSAI availability area is referred to as the NS-AoS. Outside the NS-AoS and in other cells within the TA that supports S-NSSAI, zero or limited network (e.g., radio) resources may be allocated for S-NSSAI. When network slice availability does not match the TA boundary, the AMF provides S-NSSAI location availability information, which defines the restrictions on where to use the S-NSSAI in the TA. In this disclosure, NS-AoS and S-NSSAI location availability information (which is sent to the UE) are used interchangeably and for each applicable S-NSSAI in the configured NSSAI, location information of cells indicating the S-NSSAI of the TA in the RA is available is included.

[0045] It can be assumed that when the UE moves to an area outside the support of S-NSSAI, the established PDU Session associated with the S-NSSAI that is part of the partially allowed NSSAI is not released (i.e., not removed in the control plane), but the user plane connection / resources are deactivated. In other words, the data radio bearer and the N3 (and or N9) transport tunnel are deactivated, but the PDU session context in the UE, AMF and SMF remains established. The UE is allowed to initiate PDU session establishment for the S-NSSAI only when it is in a TA that supports S-NSSAI. When the UE has established a PDU session with the S-NSSAI part of the partially allowed NSSAI, the UE is allowed to activate the user plane resources for the PDU session only when it is in the TA part of the TA list associated with each S-NSSAI, as described in more detail below.

[0046] In order to cover the two network slicing features, namely “partial network slicing support in registration area” and “network slice service area does not match deployed tracking area”, the present disclosure uses the phrases outside / within the support or availability area of ​​S-NSSAI, where inside the support area of ​​S-NSSAI means that the UE’s current TA is part of the list of TAs that support S-NSSAI, outside the support area of ​​S-NSSAI means that the UE’s current TA is not part of the list of TAs that support S-NSSAI, inside the availability area of ​​S-NSSAI means that the current UE location is part of the NS-AoS associated with the S-NSSAI, and outside the availability area of ​​S-NSSAI means that the current UE location is outside the NS-AoS associated with the S-NSSAI.

[0047] From the UE's perspective, if the UE is registered with an S-NSSAI with limited support or availability area and the UE has established a PDU session associated with the S-NSSAI (e.g., assuming that the PDU session UP resources are currently deactivated), then when the UE is outside the support or availability area of ​​the S-NSSAI, the UE may initiate an SM signaling procedure to modify or release the SM context of the PDU session. The UE may send an UL NAS transfer message containing a 5GSM message associated with the S-NSSAI even in the following situations: (1) when the S-NSSAI is part of a partially allowed NSSAI and the current TAI is not in the list of TAs that support the S-NSSAI, or (2) when the S-NSSAI is associated with location availability information and the current cell (in which the UE resides) is outside the location information of the S-NSSAI. Accordingly, for network-initiated SM procedures, the UE may receive and process NAS SM (or 5GSM) messages outside the support or availability area of ​​the S-NSSAI.

[0048] From the perspective of the network (e.g., AMF, SMF), when the AMF receives a UL NAS Transfer message, the AMF terminates the message and, if the payload is an N1 SM container (i.e., a NAS SM message), the AMF may transmit the NAS SM message to the SMF and include an indication that S-NSSAI is not supported in the current UE location (i.e., in the current TA). The SMF determines that the NAS SM message (e.g., N1 SM container) requires modification or release of the SM context, but based on the included indication that S-NSSAI is not supported in the current UE location, the SMF determines not to activate UP resources. The SMF processes the SM message, such as releasing a PDU session or modifying a PDU session, but the SMF does not initiate UP resource (or connection) activation.

[0049] Please note that the terms "N1 SM message", "N1 SM container" or "NAS SM message" are used interchangeably herein. Similarly, the terms "N2 SM message" and "N2 SM container" are used interchangeably.

[0050] In a first embodiment, a scenario is considered where a UE may request a NAS SM procedure for an established PDU session, where the UE may happen to be located in an area where the S-NSSAI for the PDU session is not supported or is not available.

[0051] Figure 3 The present disclosure illustrates an exemplary signal flow for a UE-initiated NAS SM signaling procedure for a PDU session in accordance with various aspects of the present disclosure. In particular, Figure 3 The call flow for the scenario in which the UE initiates the NAS SM procedure for a PDU Session associated with an S-NSSAI, where the UE is outside the support or availability area of ​​the S-NSSAI.

[0052] At 0 (see messaging 302), a PDU session is established between UE 301 and SMF 307. The PDU session is associated with an S-NSSAI that is either: (1) partially supported in the RA (e.g., A-NSSAI is part of the partially allowed NSSAI) or (2) associated with location availability information or NS-AoS information (e.g., the S-NSSAI serving area does not match the deployed tracking area).

[0053] At 1a (see block 304), upper layers or the NAS session management sublayer in the UE 301 may trigger an SM action for an established PDU session. For example, an existing PDU may need to be released (e.g., a UE-initiated PDU session release) or modified (e.g., a multi-access PDU session (MA PDU session) may need to be modified to release or establish a branch on a specific access).

[0054] UE 301 considers (e.g., evaluates) its current location, which means whether UE 301 is currently 1) located in a TA that supports the S-NSSAI associated with the PDU session or 2) located in a cell outside or inside the NS-AoS. UE 301 can be in a connected state or in an idle state and camped in a cell. Even when UE 301 is located in an area where the S-NSSAI associated with the PDU session (for which the SM procedure was triggered) is not supported or is unavailable, UE 301 can continue the SM procedure for the PDU session.

[0055] At 1b (see messaging 306), UE 301 initiates an SM procedure (e.g., a 5GSM procedure) for the established PDU session. If the PDU session is associated with an S-NSSAI and UE 301 is currently located in an area where S-NSSAI is not supported or available, UE 301 should not block the SM procedure and UE 301 (i.e., the NAS MM sublayer) should continue to send SM signaling to SMF 307. If there is stored or pending UL data in UE 301, UE 301 should not use a service request procedure to include the PDU session in the list of PDU sessions to be activated. Instead, UE 301 should trigger a NAS transfer procedure to transmit a NASSM message. For example, UE 301 may create an UL NAS transfer message containing a payload container type IE indicating a single 5GSM message. In addition, the UL NAS transfer message may contain PDU session information, such as PDU session ID, S-NSSAI, etc.

[0056] UE 301 sends a UL NAS transfer message encapsulated in a radio resource control (RRC) message to 5G-AN 303. 5G-AN 303 receives the UL NAS transfer message and encapsulates it in an N2 NG-AP message sent to AMF 305. The NG-AP message includes AN parameters and the UL NAS transfer message. The AN parameters include parameters from the access network to AMF 305, such as the RRC establishment cause, 5G-S-TMSI or GUAMI, and the cell ID or TAI (from which UE 301 initiated NAS signaling).

[0057] At step 2 (see block 308), the AMF 305 receives the NG-AP message. If the UL NAS transport message contains an N1 SM container (or a NAS SM message), the AMF 305 may need to evaluate whether the S-NSSAI associated with the relevant PDU session is part of a partially allowed NSSAI or whether the S-NSSAI is associated with NS-AoS information. If so, the AMF 305 considers the location of the UE 301 (e.g., current TA or cell ID) and determines whether 1) the current TA of the UE 301 supports S-NSSAI, or 2) the current cell of the UE 301 is included in the NS-AoS. If the support / validity criteria for the S-NSSAI are met, the AMF 305 continues to transmit the NAS SM message to the corresponding SMF 307 as usual. If the support / validity criteria for the S-NSSAI are not met, the AMF 305 decides to transmit a NAS SM message to the corresponding SMF 307 and additionally includes an indication that the UE 301 is outside the support or availability area of ​​the S-NSSAI. The latter indication may be referred to as, for example, "S-NSSAI is outside the support / availability area".

[0058] At 3a (see messaging 310), the AMF 305 creates and sends an N11 message to the SMF 307, and the NAS SM message is encapsulated within the N11 message. For example, the AMF 305 may use Nsmf_PDUSession_UpdateSMContext to request a service operation and include at least one of the SM context ID, the N1 SM container, and an indication that "S-NSSAI is outside the support / availability zone" in the message.

[0059] The indication "S-NSSAI outside support / availability area" is included to indicate to the SMF 307 that the UP resources of the PDU session cannot be activated in the current UE 301 location. For example, if the SMF or UPF stores downlink (DL) data for transmission, the SMF does not initiate UP resource (or connection) activation, but only processes the SM procedure.

[0060] At 3b (see messaging 312), the SMF 307 processes the received N1 SM container (e.g., NAS SM signaling message). The SMF 307 creates and sends a NAS SM signaling message encapsulated in an N11 message to the AMF 305. For example, the SMF may respond to the service operation with Nsmf_PDUSession_UpdateSMContext, including at least one of the SM context ID, PDU session ID, and N1 SM container.

[0061] At 4 (see messaging 314), AMF 305 receives the N11 message containing the N1 SM container. AMF 305 creates and sends a DL NAS Transport message to UE 301. The DL NAS Transport message is encapsulated in an NG-AP message sent to 5G-AN 303. The DL NAS Transport message contains the N1 SM container containing the NAS SM message sent to UE 301.

[0062] At step 5 (see block 316), UE 301 receives the DL NAS Transport message and extracts the NAS SM message. The NAS SM message is processed in the NAS SM instance of the NAS SM sublayer. Generally, UE 301 performs actions based on the N1 SM container instructions, such as releasing / modifying the PDU session context. UE 301 processes the SM message without initiating UP resource (or connection) activation. For example, if the NAS SM message indicates the release of a PDU session, the UE NAS layer internally deletes the PDU session context.

[0063] In one embodiment, Figure 3 The benefit of the solution illustrated in is that when the UE 301 is located in an area where the S-NSSAI of the PDU session is not supported or is not available, the UE 301 and the network (e.g., AMF 305, SMF 307) can perform the SM procedure for the PDU session. In particular, in the case of a PDU session release, this mechanism allows the PDU session context to be cleared in both the UE 301 and the network, which allows for an effective reduction in consumed resources (e.g., storage of the PDU session context and associated possible signaling during the mobility of the UE 301).

[0064] In a second embodiment, the network (e.g., SMF) may request a NAS SM procedure for a PDU session where the UE may happen to be in an area where the S-NSSAI for the PDU session is not supported or available. It is assumed that the UP resources / connections for the PDU session are not activated.

[0065] Figure 4 Illustrate an exemplary signal flow for a network initiated NAS SM signaling procedure for a PDU session according to aspects of the present disclosure. Figure 4 As shown in , it is recommended that the network (e.g., SMF 407) initiates NAS SM signaling to UE 401 and AMF 405 determines to utilize NAS transport procedures to deliver / transmit NAS SM messages, although UE 401 is outside the support or availability area of ​​S-NSSAI.

[0066] At 0 (see message reception and reception 402), a PDU session is established between UE 401 and SMF 407. In one embodiment, SMF 407 may not be aware that the S-NSSAI of the PDU session has limited support or limited availability in the RA (i.e., the S-NSSAI is associated with NS-AoS). In this embodiment, SMF 407 may initiate N1 SM signaling to UE 401 or initiate N2 SM signaling to 5G-AN403 (e.g., for activating UP resources). Then, when SMF 407 sends a request containing N1 SM signaling or N2 SM signaling to AMF 405, AMF 405 decides whether to forward or reject the request of SMF 407. This will be described in 2 below.

[0067] In another embodiment, the SMF 407 is aware that the S-NSSAI of the PDU session has limited support or limited availability in the RA (i.e., the S-NSSAI is associated with NS-AoS). In this embodiment, the SMF 407 may subscribe to the AMF 405 to be notified whether the UE 401 is inside or outside the area of ​​interest, where the area of ​​interest is 1) a list of TAs supporting S-NSSAI in the RA, or 2) NS-AoS.

[0068] At 1a (see block 404), SMF 407 determines to initiate a SM for the established PDU session. It is assumed that UP resources are not currently activated. The SM procedure may be to modify the PDU session or to release the PDU session. SMF 407 may determine to modify the PDU session, for example, by configuring new ATSSS rules for the MAPDU session, or by notifying UE 401 of an alternative S-NSSAI to exchange updated Quality of Service (QoS) parameters and / or sending updated ECS address configuration information to UE 401, etc.

[0069] The SMF 407 may decide to release the PDU session based on various scenarios, such as locally configured policies (e.g., the release procedure may be related to UPF reallocation for SSC Mode 2 / Mode 3), expiration of a timer for inactivity of the PDU session, expiration of a timer for a temporarily available network slice, or a combination thereof. In one embodiment, the SMF 407 creates an N1SM containing a PDU Session Modify Command message ( ) or a PDU Session Release Command message (PDU Session ID, cause).

[0070] At 1b (see message reception and reception 406), the SMF 407 sends an N1 SM message to the UE 401. The N1 SM message can be a PDU session modification command message (PDU session ID, QoS rule, QoS rule operation and QoSfFlow level QoS parameter operation, session-AMBR, PCO information, etc.) or a PDU session release command message (PDU session ID, cause). The SMF 407 encapsulates the N1SM message in an N11 message and sends it to the AMF 405.

[0071] For example, the SMF 407 may use the Namf_Communication_N1N2MessageTransfer service operation to include an N1 SM container containing a PDU Session Release command or a PDU Session Modify command. Since the UP connection of the PDU Session is not activated, the message sent by the SMF 407 to the AMF 405 should not include an N2 SM resource release request.

[0072] The "Skip Indicator" (or "Allow N1 SM Delivery Skip Indication") informs the AMF 405 whether it can skip sending the N1 SM container to the UE 401 (for example, when the UE 401 is in the CM Idle state). The AMF 405 processes the "Skip Indicator" for the UE 401 as described in 3GPP TS 23.502 (incorporated herein by reference). The SMF 407 may also provide the N2 SM information to the AMF 405 in the N11 message. This is possible if the SMF 407 decides to activate UP resources / connections for the PDU session.

[0073] At 2 (see block 408), the AMF 405 may determine to deliver the N1 SM message even if the S-NSSAI portion of the partially allowed NSSAI is associated with the NS-AoS information. In other words, if the AMF 405 receives the N1 SM message from the SMF 407, the AMF 405 delivers the message to the UE 401 regardless of whether the UE 401 location is within or outside the support or availability area of ​​the S-NSSAI for the PDU session.

[0074] If the AMF 405 receives an N2 SM message from the SMF 407 (e.g., for activating UP resources), the AMF 405 needs to first determine whether the location of the UE 401 is within or outside the support or availability area of ​​the S-NSSAI of the PDU session. If the location of the UE 401 is within the support or availability area of ​​the S-NSSAI of the PDU session, the AMF 405 decides to transmit the N2 SM message to the 5G-AN 403. If the location of the UE 401 is outside the support or availability area of ​​the S-NSSAI of the PDU session, the AMF 405 decides to reject the transmission of the N2 SM message to the 5G-AN 403. The AMF 405 sends a response to the SMF 407 indicating the transmission failure and an additional indication of an appropriate reason for the rejection, such as because the UE 401 is outside the support or availability area of ​​the S-NSSAI of the PDU session.

[0075] At 3a (see messaging 410), if UE 401 is in CM Idle state (and “N1 SM delivery can be skipped” is not indicated), AMF 405 may initiate a network-triggered service request procedure to transmit a NAS message (PDU Session ID, N1 SM container) to UE 401. For this purpose, AMF 405 initiates a paging procedure towards UE 401.

[0076] At 3B (see messaging 412), UE 401 responds to the paging procedure with a Service Request message. The RAN includes the current UE 401 location (e.g., TA, cell ID) in the NG-AP message from the 5G-AN that carries the Service Request message.

[0077] If the UE 401 is in CM connected state, the AMF 405 may skip 3a and 3b and proceed to 4a.

[0078] At 4a (see block 414), when the UE 401 state in the AMF 405 is connected (e.g., after the AMF 405 receives the service request message), the AMF 405 determines whether to deliver the N2 SM message to the 5G-AN 403. If the AMF 405 has received the N2 SM message (and the current UP resources for the PDU session are not activated), the AMF 405 may determine that the SMF 407 wishes to activate the UP resources.

[0079] If UE 401 is outside the support or availability area of ​​the S-NSSAI of the PDU session, AMF 405 may determine to reject the N2 SM message. If UE 401 is within the support or availability area of ​​the S-NSSAI of the PDU session, AMF 405 determines to transmit the N2 SM information to 5G-AN 403.

[0080] At 4b (see messaging 416), the AMF 405 may send an Nsmf_PDUSession_UpdateSMContext service operation to the SMF 407, including an indication that the N2 SM information was rejected (i.e., not transmitted / delivered to the 5G-AN 403), and a corresponding rejection cause indicating the reason for the rejection (or non-delivery). For example, the rejection cause may indicate that the UE 401 is currently located in an area where S-NSSAI is not supported or is not available.

[0081] Alternatively, if the UE 401 is within the support or availability area of ​​the S-NSSAI of the PDU session, the AMF 405 includes the N2 SM information in addition to the N1 SM container in the NG-AP message sent to the 5G-AN 403, as described in 4c.

[0082] At 4c (see messaging 418), AMF 405 creates and sends a DL NAS Transfer message to UE 401. The DL NAS Transfer message is encapsulated in an NG-AP message sent to 5G-AN 403. The DL NAS Transfer message includes an N1 SM container containing a NAS SM message sent to UE 401. For example, the DL NAS Transfer message sent to UE 401 contains PDU session information (PDU Session ID) in the PDU Session ID information element (IE); the Payload Container Type IE is set to "N1 SM Information"; the Payload Container IE is set to 5GSM Message; or a combination thereof.

[0083] At step 5 (see block 420), UE 401 receives the DL NAS Transport message and extracts the NAS SM message and forwards it to the correct PDU Session entity in UE 401. The NAS SM message is processed in the NAS SM instance of the NAS SM sublayer. Generally, UE 401 performs actions based on the N1 SM container instructions, such as releasing / modifying the PDU Session context. UE 401 processes the SM message without initiating UP resource (or connection) activation. For example, if the NAS SM message indicates the release of the PDU Session, the UE NAS layer internally deletes the PDU Session context.

[0084] At 6a (see messaging 424), UE 401 may send an N1 SM Reply message to SMF 407. UE 401 may encapsulate the N1 SM Reply message in a UL NAS Transport message sent to AMF 405. For example, the N1 SM Reply message is an acknowledgment of the N1 SM message received at 4c. In one example, the N1 SM Reply message may be a PDU Session Modify Command Acknowledgement or a PDU Session Release Command Acknowledgement message.

[0085] At 6b (see messaging 426), the AMF 405 forwards the N1 SM container (PDU Session Modification Command Ack) received from the AN and the user location information to the SMF 407 via the Nsmf_PDUSession_UpdateSMContext service operation. The SMF 407 replies with a Nsmf_PDUSession_UpdateSMContext response.

[0086] In one embodiment, Figure 4 The benefit of the solution in is that the network AMF 405 can determine whether to allow activation of UP resources for the PDU session, that is, whether to transmit N2 SM information to the 5G-AN 403, based on the current location of the UE 401 (whether it is within or outside the support or availability area of ​​the S-NSSAI of the PDU session). In addition, the AMF 405 determines to transmit the N1 SM message to the UE 401 even though the UE 401 is outside the support or availability area of ​​the S-NSSAI.

[0087] In a third embodiment, when the UE is located in an area where the S-NSSAI associated with the PDU session is not supported or is not available, the UE may initiate 1) a PDU session establishment procedure for a new connection or 2) a service request procedure for an established PDU session. This scenario may be an error situation where (1) the UE supports the feature of partial support or availability of S-NSSAI, or (2) the UE does not support the feature of partial support or availability of S-NSSAI.

[0088] Generally, when a UE that supports the network slicing features "partial network slicing support in the registration area" and / or "network slice service area does not match the deployed tracking area" is located outside the support or availability area of ​​the S-NSSAI of the PDU session, the UE should not initiate UP resource / connection activation for the PDU session. However, if the UE does not support the feature or supports the feature but requests activation of UP resources / connection for the PDU session for another reason, the network (e.g., AMF or SMF) should reject the UE's request.

[0089] If the UE initiates a Service Request procedure to activate a UP connection for a PDU session associated with an S-NSSAI (which is not supported in the current TA), the UE includes the PDU session ID in the list of PDU sessions to be activated in the Service Request message. The AMF determines whether 1) the current TA (in which the UE is located) is part of the list of TAs that support S-NSSAI, and / or 2) the current cell ID is part of the NS-AoS for S-NSSAI. If conditions 1) and 2) are not met, the AMF refuses to activate the UP resources for the PDU session. For example, the AMF sends a Service Request message.

[0090] Figure 5 Illustrated are exemplary signal flows to reject activation of UP resources for a PDU session when the UE is out of support / availability of S-NSSAI in accordance with aspects of the present disclosure.

[0091] At 0 (see messaging 502), it is assumed that a PDU session is established between UE 501 and SMF 507. The PDU session is associated with an S-NSSAI that is partially supported in the RA (e.g., the A-NSSAI is part of the partially allowed NSSAI), or the S-NSSAI is associated with NS-AoS information (e.g., the S-NSSAI service area does not match the deployed tracking area). In another embodiment, UE 501 may only be registered with the S-NSSAI, but a PDU session has not yet been established.

[0092] At 1 (see messaging 504), UE 501 initiates a service request procedure to activate a UP connection for a PDU session associated with S-NSSAI (which is not supported in the current TA), UE 501 includes the PDU session ID in the PDU session list to be activated in the service request message.

[0093] UE 501 sends a service request message encapsulated in an RRC message to 5G-AN 503. 5G-AN 503 receives the service request message and encapsulates it in an N2 NG-AP message sent to AMF 505. The NG-AP message includes AN parameters along with the service request message. The AN parameters include parameters from the access network to AMF 505, such as the RRC establishment cause, 5G-S-TMSI or GUAMI, and the cell ID or TAI (from which UE 501 initiated NAS signaling).

[0094] In another scenario, UE 501 may initiate a PDU Session Establishment Request for an S-NSSAI with partial support or availability, e.g., assuming that UE 501 has previously registered with the S-NSSAI. In this scenario, UE 501 sends an UL NAS Transfer message containing an N1 SM container containing a PDU Session Establishment Request message. Figure 5 In the further description, the use case of a service request message is assumed, but the solution can also be applied to the case of a PDU session establishment request.

[0095] At 2 (see block 506), the AMF 505 determines that the S-NSSAI associated with the PDU session to be activated has limited support in the RA (i.e., the S-NSSAI is included in the partially allowed NSSAI and is associated with the TA list in the TA) or limited availability (i.e., the S-NSSAI is associated with NS-AoS). The AMF 505 then needs to determine whether the UE 501 is within or outside the support / availability region of the S-NSSAI for the PDU session.

[0096] In one embodiment, if the S-NSSAI is included in the partially allowed NSSAI and is associated with the TA list in the TA, and the current TA (in which the UE 501 is located) is part of the TA list that supports S-NSSAI, then the AMF 505 proceeds with the service request procedure for activating UP resources for the PDU session.

[0097] In one embodiment, if the S-NSSAI is included in the partially allowed NSSAI and is associated with the TA list in the TA, and the current TA (in which the UE 501 is located) is not part of the TA list that supports S-NSSAI, the AMF 505 determines to reject the service request procedure for UP resources for activating the PDU session. The AMF 505 proceeds to step 3.

[0098] In one embodiment, if the S-NSSAI is associated with NS-AoS and the current cell ID is part of the NS-AoS of the S-NSSAI, the AMF 505 proceeds with the service request procedure for activating UP resources for the PDU session.

[0099] In one embodiment, if the S-NSSAI is associated with the NS-AoS and the current cell ID is not part of the NS-AoS of the S-NSSAI, the AMF 505 determines to reject the service request procedure for UP resources for activating the PDU session. The AMF 505 proceeds to step 3.

[0100] At 3 (see messaging 508), which is alternative 1 for AMF-initiated UP resource activation rejection, the AMF 505 sends a Service Accept or Service Reject message containing an indication that the requested activation of UP resources / connections for the PDU session is rejected. The AMF 505 may include an appropriate rejection cause indicating the reason for the rejection, such as due to network slice resources not being available in the current location.

[0101] At 4a (see messaging 510), which is alternative 2 in which the AMF 505 indicates to the SMF 407 that the UP resource activation is initially rejected, the AMF 505 may decide to inform the SMF 507 that the UE 501 requests PDU session activation, and in addition the AMF 505 includes an indication that the S-NSSAI is outside the support / availability region. For example, the AMF 505 may send an Nsmf_PDUSession_UpdateSMContext request message to the SMF 507 including the PDU session ID, an indication that "S-NSSAI is outside the support / availability region", or a combination thereof.

[0102] Upon receiving an indication that UE 501 is in an area outside of S-NSSAI support / availability, SMF 507 creates and transmits an N1 SM container to UE 501, the N1 SM container containing an SM message indicating that PDU session activation is rejected because S-NSSAI is not supported or available.

[0103] At 4b (see messaging 512), which is part of alternative 2, the AMF 505 receives an N1 SM container from the SMF 507, the N1 SM container containing, for example, an SM message that rejects the PDU session activation due to unsupported / unavailable S-NSSAI. The AMF 505 creates and transmits a DL NAS transport message containing the PDU session ID, an N1 SM container containing an SM message indicating that the PDU session activation is rejected due to unsupported or unavailable S-NSSAI in the current location area, or a combination thereof.

[0104] At step 5 (see block 514), the UE NAS SM sublayer receives the N1 SM container based on the notification in step 3 or 4b. Based on the indication that the PDU session activation is rejected because the S-NSSAI is not supported or available in the current location area, the UE 501 blocks the transmission of user plane data (i.e., blocks UP resource activation). In other words, the UE 501 considers that the PDU session is not available for data transmission and that the UE 501 may need to determine an alternative PDU session (e.g., associated with another S-NSSAI) to transmit data for the application associated with this PDU session.

[0105] In one embodiment, Figure 5 The benefit of the solution in is that the network can determine and perform (see 2, 3 and 4) a rejection of the request for UE initiated PDU session resource activation based on the current UE 501 being located in an area where S-NSSAI is not supported or is not available.

[0106] Figure 6 An example of a UE 600 according to various aspects of the present disclosure is illustrated. The UE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0107] The processor 602, memory 604, controller 606, or transceiver 608, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure.

[0108] The processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604, thereby causing the UE 600 to perform various functions of the present disclosure.

[0109] Memory 604 may include volatile or non-volatile memory. Memory 604 may store computer-readable, computer-executable code including instructions that, when executed by processor 602, cause UE 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 604 or another type of storage. Computer-readable media includes both non-transitory computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-transitory storage media may be any available media that can be accessed by a general-purpose or special-purpose computer.

[0110] In some embodiments, the processor 602 and the memory 604 coupled to the processor 602 may be configured to cause the UE 600 to perform one or more of the functions described herein (e.g., execution of instructions stored in the memory 604 by the processor 602). For example, according to the examples disclosed herein, the processor 602 may support wireless communications at the UE 600. The UE 600 may be configured to support means for: transmitting signaling of a SM procedure for an established PDU session associated with a network slice, wherein the network slice is not supported or is not available in the location area of ​​the UE; receiving a NAS SM message as part of the SM procedure for the PDU session; and performing an action based on the NAS SM message without initiating activation of user plane resources for the PDU session.

[0111] In one embodiment, the UE 600 may be configured or operable to support means for continuing SM procedures for a PDU session even if the UE is located in an area where a single S-NSSAI is not supported or is unavailable. In some embodiments, the UE 600 may be configured or operable to support means for transmitting signaling to the SMF as part of a PDU session even if the UE is located in an area where an S-NSSAI is not supported or is unavailable.

[0112] The controller 606 may manage input and output signals of the UE 600. The controller 606 may also manage peripheral devices that are not integrated into the UE 600. In some implementations, the controller 606 may utilize, for example, In some embodiments, the controller 606 may be implemented as part of the processor 602 .

[0113] In some implementations, the UE 600 may include at least one transceiver 608. In some other implementations, the UE 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0114] The receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain 610 may include one or more antennas for receiving signals over the air or via a wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by inverting the modulation technique applied during transmission of the signal. The receiver chain 610 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0115] The transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, thereby preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level for transmission over a wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0116] Figure 7 An example of a processor 700 according to aspects of the present disclosure is illustrated. The processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. The processor 700 may optionally include at least one memory 704, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, the processor 700 may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0117] The processor 700 may be a processor chipset and include a protocol stack (e.g., a software stack) that is executed by the processor chipset to perform various operations according to the examples described herein (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading). The processor chipset may include one or more cores, one or more cache memories (e.g., memory local to or included in the processor chipset (e.g., processor 700), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others)).

[0118] The controller 702 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 700 to cause the processor 700 to support various operations according to the examples described herein. For example, the controller 702 may operate as a control unit for the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating operation timing.

[0119] The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instructions to be executed to cause the processor 700 to support various operations according to the examples described herein. The controller 702 may be configured to track the memory addresses of instructions associated with the memory 704. The controller 702 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, the controller 702 may be configured to interpret instructions and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations according to the examples described herein. Additionally or alternatively, the controller 702 may be configured to manage data flow within the processor 700. The controller 702 may be configured to control data transfers between registers, an arithmetic logic unit (ALU), and other functional units of the processor 700.

[0120] The memory 704 may include one or more cache memories (e.g., memory local to or included in the processor 700 or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some embodiments, the memory 704 may reside within or on the processor chipset (e.g., local to the processor 700). In some other embodiments, the memory 704 may reside external to the processor chipset (e.g., remote from the processor 700).

[0121] The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 702 and / or the processor 700 may be configured to execute the computer-readable instructions stored in the memory 704, thereby causing the processor 700 to perform the various functions. For example, the processor 700 and / or the controller 702 may be coupled together with or coupled to the memory 704, and the processor 700, the controller 702, and the memory 704 may be configured to perform the various functions described herein. In some examples, the processor 700 may include multiple processors and the memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0122] The one or more ALUs 706 can be configured to support various operations according to the examples described herein. In some embodiments, the one or more ALUs 706 can reside within or on a processor chipset (e.g., processor 700). In some other embodiments, the one or more ALUs 706 can reside external to a processor chipset (e.g., processor 700). The one or more ALUs 706 can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, the one or more ALUs 706 can receive input operands and an opcode, which determines the operation to be performed. The one or more ALUs 706 are configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, the one or more ALUs 706 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling the one or more ALUs 706 to handle conditional operations, comparisons, and bitwise operations.

[0123] According to examples disclosed herein, processor 700 may support wireless communications. Processor 700 may be configured or operable to support means for receiving a first SM message for a PDU session associated with a network slice and a UE, means for determining that the network slice is not supported or available in a location area of ​​the UE, and means for transmitting a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE.

[0124] In some embodiments, the first SM message is an N1 SM message received from the UE and encapsulated in an uplink NAS transfer message. In one embodiment, the second SM message is transmitted to the SMF and encapsulated in a PDU Session Update Request message.

[0125] In some embodiments, the second SM message is an N2 SM message intended for the AN.In one embodiment, the processor 700 is configured to cause the NE to avoid delivering the N2 SM message to the AN in response to determining that the network slice is not supported or available in the location area of ​​the UE.

[0126] In some embodiments, the processor 700 is configured to indicate to the sender of the first SM message that the N2 SM message was not delivered to the AN because the network slice is not supported or is not available in the location area of ​​the UE. In one embodiment, the processor 700 includes an AMF.

[0127] In one embodiment, the processor 700 may be configured or operable to support components for: transmitting signaling for an SM procedure for an established PDU session associated with a network slice, where the network slice is not supported or available in the location area of ​​the UE; receiving a NAS SM message as part of the SM procedure for the PDU session; and performing actions based on the NAS SM message without initiating activation of user plane resources for the PDU session.

[0128] In one embodiment, the processor 700 may be configured or operable to support means for continuing the SM procedure for a PDU session even if the UE is located in an area where a single S-NSSAI is not supported or is unavailable. In some embodiments, the processor 700 may be configured or operable to support means for transmitting signaling to the SMF as part of a PDU session even if the UE is located in an area where an S-NSSAI is not supported or is unavailable.

[0129] Figure 8An example of an NE 800 according to various aspects of the present disclosure is illustrated. NE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. Processor 802, memory 804, controller 806, or transceiver 808, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0130] The processor 802, memory 804, controller 806, or transceiver 808, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure.

[0131] The processor 802 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some embodiments, the processor 802 may be configured to operate the memory 804. In some other embodiments, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804, thereby causing the NE 800 to perform various functions of the present disclosure.

[0132] Memory 804 may include volatile or nonvolatile memory. Memory 804 may store computer-readable, computer-executable code including instructions that, when executed by processor 802, cause NE 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 804 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-transitory storage media may be any available media that can be accessed by a general-purpose or special-purpose computer.

[0133] In some embodiments, the processor 802 and the memory 804 coupled to the processor 802 may be configured to cause the NE 800 to perform one or more of the functions described herein (e.g., execution of instructions stored in the memory 804 by the processor 802). For example, according to the examples disclosed herein, the processor 802 may support wireless communications at the NE 800. The NE 800 may be configured to support means for receiving a first SM message for a PDU session associated with a network slice and a UE, means for determining that the network slice is not supported or is not available in the location area of ​​the UE, and means for transmitting a second SM message and an indication that the network slice is not supported or is not available in the location area of ​​the UE.

[0134] In some embodiments, the first SM message is an N1 SM message received from the UE and encapsulated in an uplink NAS transfer message. In one embodiment, the second SM message is transmitted to the SMF and encapsulated in a PDU Session Update Request message.

[0135] In some embodiments, the second SM message is an N2 SM message intended for the AN.In one embodiment, the NE 800 is configured to cause the NE to avoid delivering the N2 SM message to the AN in response to determining that network slicing is not supported or unavailable in the location area of ​​the UE.

[0136] In some embodiments, the NE 800 is configured to indicate to the sender of the first SM message that the N2 SM message was not delivered to the AN because the network slice is not supported or is not available in the location area of ​​the UE. In one embodiment, the NE 800 includes an AMF.

[0137] The controller 806 may manage the input and output signals of the NE 800. The controller 806 may also manage peripheral devices that are not integrated into the NE 800. In some embodiments, the controller 806 may utilize, for example, In some embodiments, the controller 806 may be implemented as part of the processor 802 .

[0138] In some embodiments, NE 800 may include at least one transceiver 808. In some other embodiments, NE 800 may have more than one transceiver 808. Transceiver 808 may represent a wireless transceiver. Transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0139] The receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain 810 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 810 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during transmission of the signal. The receiver chain 810 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0140] The transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, thereby preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level for transmission over a wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0141] Figure 9 The flowchart of the method according to various aspects of the present disclosure is illustrated. The operation of the method can be implemented by a UE as described herein. In some embodiments, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions.

[0142] At 902, the method may include triggering an SM action for a PDU session associated with a network slice that is not supported or available in the location area of ​​the UE. The operations of 902 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 902 may be performed as described in reference to Figure 6 The UE described is used to perform.

[0143] At 904, the method may include receiving a NAS SM message during a PDU session. The operations of 904 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 904 may be performed as described in reference to Figure 6 The UE described is used to perform.

[0144] At 906, the method may include performing actions according to the NAS SM message without initiating user plane resources. The operations of 906 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 906 may be as described in reference to Figure 6 The UE described is used to perform.

[0145] It should be noted that the methods described herein describe one possible implementation and that the operations and steps may be rearranged or otherwise modified and other implementations are possible.

[0146] Figure 10 A flowchart illustrating a method according to various aspects of the present disclosure is provided. The operations of the method may be performed by an NE as described herein. In some embodiments, the NE may execute a set of instructions to control functional elements of the NE to perform the described functions.

[0147] At 1002, the method may include receiving a first SM message for a PDU session associated with a network slice and a UE. The operations of 1002 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 1002 may be performed as described in reference to Figure 8 The NE described is executed.

[0148] At 1004, the method may include determining that the network slice is not supported or is not available in the location area of ​​the UE. The operations of 1004 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 1004 may be as described in reference to Figure 8 The NE described is executed.

[0149] At 1006, the method may include transmitting a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE. The operations of 1006 may be performed according to the examples described herein. In some embodiments, aspects of the operations of 1006 may be as described in reference to Figure 8 The NE described is executed.

[0150] It should be noted that the methods described above describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible.

[0151] The description herein is provided to enable one skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A network entity (NE), comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the NE to: receiving a first session management (SM) message for a protocol data unit (PDU) session associated with a network slice and a user equipment (UE); determining that the network slice is not supported or is unavailable in a location area of ​​the UE; and Transmitting a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE.

2. The NE according to claim 1, wherein: The first SM message is an N1SM message received from the UE and encapsulated in an uplink non-access stratum (NAS) transmission message.

3. The NE according to claim 2, wherein: The second SM message is transmitted to the session management function SMF and encapsulated in a PDU session update request message.

4. The NE according to claim 1, wherein: The second SM message is an N2 SM message intended to be sent to the access network AN.

5. The NE according to claim 4, wherein: The at least one processor is configured to cause the NE to avoid delivering the N2 SM message to the AN in response to determining that the network slice is not supported or unavailable in the location area of ​​the UE.

6. The NE according to claim 5, wherein: The at least one processor is configured to cause the NE to indicate to a sender of the first SM message that the N2 SM message was not delivered to the AN because the network slice was not supported or was not available in the location area of ​​the UE.

7. The NE according to claim 1, wherein: The NE includes an access and mobility management function AMF.

8. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving a first session management (SM) message for a protocol data unit (PDU) session associated with a network slice and a user equipment (UE); determining that the network slice is not supported or is unavailable in a location area of ​​the UE; and Transmitting a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE.

9. The processor of claim 8, wherein: The first SM message is an N1SM message received from the UE and encapsulated in an uplink non-access stratum (NAS) transmission message.

10. The processor of claim 9, wherein: The second SM message is transmitted to the session management function SMF and encapsulated in a PDU session update request message.

11. The processor of claim 8, wherein: The second SM message is an N2 SM message intended to be sent to the access network AN.

12. The processor of claim 11, wherein: The at least one controller is configured to cause the processor to avoid delivering the N2 SM message to the AN in response to determining that the network slice is not supported or unavailable in the location area of ​​the UE.

13. The processor of claim 12, wherein: The at least one controller is configured to cause the processor to indicate to a sender of the first SM message that the N2 SM message was not delivered to the AN because the network slice was not supported or was not available in the location area of ​​the UE.

14. The processor of claim 8, wherein: The processor includes an access and mobility management function AMF.

15. A method performed by a network function, the method comprising: receiving a first session management (SM) message for a protocol data unit (PDU) session associated with a network slice and a user equipment (UE); determining that the network slice is not supported or is unavailable in a location area of ​​the UE; and Transmitting a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE.

16. The method according to claim 15, wherein: The first SM message is an N1SM message received from the UE and encapsulated in an uplink non-access stratum (NAS) transmission message.

17. The method according to claim 16, wherein: The second SM message is transmitted to the session management function SMF and encapsulated in a PDU session update request message.

18. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor coupled with the at least one memory and configured to cause the UE to: signalling of a session management (SM) procedure for an established protocol data unit (PDU) session associated with a network slice that is not supported or available in the location area of ​​the UE; receiving a non-access stratum (NAS) SM message as part of the SM procedure for the PDU session; and Actions are performed according to the NAS SM message without initiating activation of user plane resources for the PDU session.

19. The UE according to claim 18, wherein: The at least one processor is configured to cause the UE to continue the SM procedure for the PDU session even if the UE is located in an area where single network slice selection assistance information S-NSSAI is not supported or is unavailable.

20. The UE according to claim 19, wherein: The at least one processor is configured to cause the UE to transmit the signaling to a session management function (SMF) as part of the PDU session even if the UE is located in an area where S-NSSAI is not supported or is unavailable.

Images