Techniques for session management signaling to support partial network slicing in registration areas

Abstract

Various aspects of this disclosure relate to techniques for session management signaling for supporting partial network slices in a registration area. The device (800) is configured to receive a first session management (SM) message relating to a network slice and a protocol data unit (PDU) session associated with a user device (UE), to determine that the network slice is not supported or available in the area where the UE is located, and to transmit a second SM message and an indication that the network slice is not supported or available in the area where the UE is located.

Description

Technical Field

[0001] The present disclosure relates to wireless communication, and more particularly, to techniques for session management signaling for supporting partial network slices in a registered area.

Background Art

[0002] A wireless communication system may include one or more network communication devices such as a base station, and the network communication device may support wireless communication for one or more user communication devices, which may be known by an alias user equipment (UE) or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Further, the wireless communication system may support wireless communication spanning various wireless access technologies including third generation (3G) wireless access technology, fourth generation (4G) wireless access technology, fifth generation (5G) wireless access technology, and other suitable wireless access technologies after 5G (e.g., sixth generation (6G)).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Summary of the Invention

Means for Solving the Problems

[0004] The article “a” preceding an element is understood to mean “at least one” or “one or more” of those elements, without limitation. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. When used herein, including in claims, “or” in a list of items (for example, a list of items followed by a phrase such as “at least one of” or “one or more of” or “one or both of”) indicates an inclusive list, for example, such that the list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, when used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing the scope of this disclosure. In other words, as used herein, the phrase "based on" shall be interpreted as equivalent to the phrase "based at least in part on." Furthermore, as used herein, including in claims, "set" may include one or more elements.

[0005] Some implementations of the methods and apparatus described herein may include means for transmitting signaling relating to session management (SM) procedures for established protocol data unit (PDU) sessions associated with a network slice, where the network slice is not supported or available in the location area of ​​the UE, receiving non-accessible layer (NAS) SM messages as part of the SM procedures for the PDU session, and taking action in accordance with the NAS SM messages without initiating the activation of user plane resources for the PDU session.

[0006] Some implementations of the methods and apparatus described herein may include means for receiving a first SM message relating to a network slice and a PDU session associated with the UE, means for determining that the network slice is not supported or available in the area where the UE is located, a second SM message, and means for transmitting an indication that the network slice is not supported or available in the area where the UE is located. [Brief explanation of the drawing]

[0007] [Figure 1] This figure shows an example of a wireless communication system according to the embodiments of this disclosure. [Figure 2] This figure shows an example of a system setup for network slicing and a specific UE requirement according to an aspect of this disclosure. [Figure 3] This figure shows an exemplary signal flow of a NAS SM signaling procedure initiated by a UE for a PDU session, according to an aspect of this disclosure. [Figure 4] This figure shows an exemplary signal flow of a network-initiated NAS SM signaling procedure for a PDU session according to an aspect of the present disclosure. [Figure 5]This figure shows an exemplary signaling flow for refusing to activate a user plane (UP) resource for a PDU session when the UE is outside the support / availability of single network slice selection assistance information (S-NSSAI), according to an aspect of this disclosure. [Figure 6] This figure shows an example of a UE according to the aspects of this disclosure. [Figure 7] This figure shows an example of a processor according to the embodiments of this disclosure. [Figure 8] This figure shows an example of network equipment (NE) according to the embodiments of this disclosure. [Figure 9] This is a flowchart of a method performed by NE according to the aspects of this disclosure. [Figure 10] This is a flowchart of a method performed by NE according to the aspects of this disclosure. [Modes for carrying out the invention]

[0008] In a 5G network, network slices extend across the Radio Access Network (RAN) and the Core Network (CN), such as the 5G Core Network (5GC). Generally, network slices that meet the service requirements from the customer / user of the network slice requesting its deployment may be deployed in cells or tracking areas (TAs). With the evolution 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., across the entire network coverage), 2) network slices supported in some tracking areas, or 3) network slices operating in a single TA.

[0009] Even if a network slice is supported in a single TA or set of TAs, the network slice may be available as a single cell or set of cells as part of the TA. As used herein, "availability" of a network slice may refer to the network resources required to meet the service requirements of the network slice (e.g., including wireless resources, core network resources, and transport and compute resources). In such embodiments, the network slice service area (NS-AoS) does not coincide with the deployed TA on which the network slice is supported. In other words, Single Network Slice Selection Assistance Information (S-NSSAI) location availability information defines additional limitations on the use of S-NSSAI in TAs where the network slice availability does not coincide with the TA boundaries.

[0010] For example, according to the 5G specifications of 3GPP TS 23.501 V18.1.0 and TS 23.502 V18.2.0 (both incorporated herein by reference), 5GC creates and configures a UE with an allowed network slice, i.e., a set of allowed network slices identified by an allowed NSSAI, when the S-NSSAI of an allowed NSSAI is available at all TAs in a registered area (RA). Neighboring TAs supporting an allowed NSSAI may be assigned to the same RA.

[0011] A UE may also be configured with partially allowed NSSAIs that indicate S-NSSAI values ​​that the UE might use within a set of partially allowed network slices, for example, within a portion of the TAs in the current RA, in a serving public land mobile network (PLMN) or a standalone non-public network (SNPN). Each S-NSSAI in a partially allowed NSSAI is associated with a list of TAs that support the S-NSSAI.

[0012] Such network slice configurations are sent to the UE using NAS registration acceptance messages or NAS UE configuration update command messages. The Access and Mobility Management Function (AMF) may include, in addition to the partial authorization NSSAI, the corresponding mapping information of the S-NSSAI of the partial authorization NSSAI to the HPLMN S-NSSAI.

[0013] When an AMF creates a RA with one or more TAs, S-NSSAIs of authorized NSSAIs are supported in the RA's TAs. If a UE's requested NSSAI includes an S-NSSAI that is supported in the current TA but not in other possible TAs of the RA, the AMF may create an appropriate RA that takes into account the expected paging load versus the load caused by mobility registration update (MRU) requests, and the AMF will include the S-NSSAI in the partially authorized NSSAI. Additional supporting information indicating the list of TAs that support the S-NSSAI is associated with the S-NSSAI.

[0014] 5GC (e.g., AMF) may send one or more of the following elements related to the UE's network slice configuration - permitted NSSAI, partially permitted NSSAI, configured NSSAI, rejected NSSAI, or pending NSSAI - to the UE within a registration acceptance message (in the case of UE registration procedure) or a UE configuration update command message (in the case of UE configuration update procedure). NSSAI is a list of one or more S-NSSAIs. Each S-NSSAI of the partially permitted NSSAI may be associated with a list of TAs where the S-NSSAI is supported (which is a subset of the list of TAIs forming the RA).

[0015] However, it may not be clear whether the UE or the network may release or modify a PDU session. When the UE sends a UL NAS TRANSPORT message containing a 5G SM message associated with an S-NSSAI, the AMF may not know the type of the SM message, e.g., it may not know whether to activate UP resources or release the PDU session. The AMF may not know whether it should reject the NAS transport procedure (e.g., reject the NAS mobility management (MM) transport message) or forward the NAS SM message to the session management function (SMF).

[0016] The current specification may not allow the activation of UP resources in a TA outside the list of TAs where the S-NSSAI is supported. However, the behavior of the SM signaling for controlling the PDU session context of the UE and the SMF (e.g., for releasing or modifying the PDU session) is not defined.

[0017] In other words, when a network slice is part of a partially permitted NSSAI, the UE may not activate any UP resources for any PDU sessions associated with the S-NSSAI. However, there is no solution to explain the behavior of the UE and the network (e.g., AMF or SMF) when the SM should be running for such PDU sessions.

[0018] In response to the above, the following solution is proposed. In one embodiment, at the location of the UE in the RA, the UE or network (e.g., AMF or SMF) may initiate and execute an SM procedure (e.g., a "5G SM message transmission procedure") for an established PDU session when the relevant S-NSSAI is included in a partially authorized NSSAI or when NS-AoS relating to the S-NSSAI applies (e.g., is configured), so that the NAS SM procedure can be executed independently regardless of whether 1) the UE is in an area where S-NSSAI is supported or available, or 2) the UE is in an area where S-NSSAI is not supported or available. Aspects of this disclosure will be described in the context of wireless communication systems.

[0019] FIG. 1 shows an example of a wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 may include one or more network elements (NE) 102, one or more user equipments (UE) 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, 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 implementations, the wireless communication system 100 may be a New Radio (NR) network such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, 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), and IEEE 802.20. The wireless communication system 100 may support radio access technologies later than 5G, such as 6G. Further, 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).

[0020] One or more NEs 102 may be distributed across a geographical 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 network nodes, base stations, network elements, network functions, network entities, RAN, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other appropriate terms. The NEs 102 and UEs 104 may communicate via a communication link, which may be wireless or wired. For example, the NEs 102 and UEs 104 may perform wireless communication via a Uu interface (e.g., receiving signaling, transmitting signaling).

[0021] NE 102 may provide a geographical coverage area in which NE 102 may support services for one or more UE 104 within the geographical 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.) according to one or more radio access technologies. In some implementations, NE 102, for example, a satellite associated with a non-terrestrial network (NTN), may be mobile. In some implementations, different geographical coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographical coverage areas may be associated with different NE 102.

[0022] One or more UEs 104 may be distributed across the geographical area of ​​the wireless communication system 100. UEs 104 may include, or be referred to as, remote units, mobile devices, wireless devices, remote devices, subscriber devices, transmitter devices, receiver devices, or any other appropriate term. In some implementations, UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, UEs 104 may be referred to as Internet-of-Things (IoT) devices, Internet-of-Everything (IoE) devices, or machine-type communication (MTC) devices, among other examples.

[0023] UE 104 may support direct wireless communication with other UE 104s via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-devic (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 side link. UE 104 may support direct wireless communication with another UE 104 via the PC5 interface.

[0024] An NE 102 may support communication with a CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102s or CN 106s through one or more backhaul links (e.g., S1, N2, N2, or a network interface). In some implementations, NE 102s may communicate directly with each other. In some other implementations, NE 102s may communicate indirectly with each other (e.g., via a CN 106). In some implementations, one or more NE 102s may include subcomponents such as access network entities, which may be examples of access node controllers (ANCs). An ANC may communicate with one or more UEs 104s through one or more other access network transmission entities, which may be called radioheads, smart radioheads, or transmission-reception points (TRPs).

[0025] CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 may be an evolved packet core (EPC) or 5G core (5GC) that includes control plane entities that manage access and mobility (e.g., mobility management entities (MMEs), access and mobility management functions (AMFs)) and user plane entities that route packets or interconnect to external networks (e.g., serving gateways (S-GWs), packet data network (PDN) gateways (P-GWs), or user plane functions (UPFs)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for one or more UEs 104 that are serviced by one or more NEs 102 associated with the CN 106.

[0026] CN 106 may communicate with the 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. UE 104 may establish a session with CN 106 via NE 102 (e.g., a PDU session). CN 106 may use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and the application server. The PDU session may be an example of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0027] In the wireless communication system 100, the NE 102 and UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, 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 UE 104 may support different resource structures. For example, the NE 102 and UE 104 may support different frame structures. In some implementations, such as 4G, the NE 102 and UE 104 may support a single frame structure. In some other implementations, such as 5G, among other suitable radio access technologies, the NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). The NE 102 and UE 104 may support various frame structures based on one or more numerologies.

[0028] One or more numerologies may be supported in the wireless communication system 100, and the numerologies may include subcarrier intervals and cyclic prefixes. A first numerology (e.g., μ=0) may be associated with a first subcarrier interval (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier interval (e.g., 15 kHz) may occupy one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier interval (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier interval (e.g., 60 kHz) and a normal or extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth carrier interval (e.g., 120 kHz) and a typical cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier interval (e.g., 240 kHz) and a typical cyclic prefix.

[0029] The time intervals of a resource (for example, a communication resource) may be organized by frames (also called wireless frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, each subframe may have a duration, for example, 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

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

[0031] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands such as 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 implementations, the NE 102 and UE 104 may perform wireless communication on one or more of these operating frequency bands. In some implementations, FR1 may be used by the NE 102 and UE 104, among other things, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by equipment or devices, particularly NE 102 and UE 104, for short-range, high-data-rate capabilities.

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

[0033] Figure 2 shows an example of a system setup and a specific UE request for network slicing according to the embodiments of this disclosure. In particular, Figure 2 shows an example of a 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 within TA2 204 and sends a request NSSAI including S-NSSAI#1 and S-NSSAI#2. 5GC (e.g., AMF and / or NSSF) considers that UE 208 is currently located within TA2 204, which supports S-NSSAI#1 and S-NSSAI#2, while the neighboring TA1 202 and TA3 206 support only S-NSSAI#1. Therefore, AMF may assign RA 210 including TA1 202, TA2 204, and TA3 206, and AMF sends a registration acceptance message to UE 208 including RA 210, TA1 202, TA2 204, TA3 206, an authorized NSSAI including S-NSSAI#1, a partially authorized NSSAI including S-NSSAI#2, an associated list of TAs that support S-NSSAI#2 including only TA2 204, and a denied NSSAI that includes nothing.

[0034] If UE 208 has already established a PDU session using the S-NSSAI portion of a partially permitted NSSAI, UE 208 is only allowed to activate the UP resource for the PDU session when UE 208 is in the TA portion of the list of TAs associated with each S-NSSAI (where the S-NSSAI is supported).

[0035] However, if the UE is outside the list of TAs (where S-NSSAI is supported) or outside the S-NSSAI availability area (e.g., the network slice service area), it is unclear whether the UE or network may initiate and execute session management procedures (e.g., release or correction procedures) for an established PDU session. If the UE sends a UL NAS TRANSPORT message containing a 5GSM message related to S-NSSAI, the AMF does not know the type of SM message, i.e., whether to activate the UP resource or release the PDU session. The AMF does not know whether to reject the NAS transport procedure (e.g., reject the NAS MM transport message) or forward the NAS SM message to the SMF.

[0036] The following describes the solutions to the aforementioned problems using current cutting-edge technologies. With regard to the solutions described herein, it should be noted that the term "support" for S-NSSAI means that S-NSSAI is deployed in an area such as a Tracking Area (TA), which relates to a network slicing feature called "support for partial network slices in registration areas." 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 relates to a network slicing feature called "Network Slice Area of ​​Service not matching deployed Tracking Areas." In other words, a network slice (e.g., S-NSSAI is used interchangeably with a network slice) 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. Such areas of S-NSSAI availability are referred to as NS-AoS. Outside of NS-AoS and in other cells within a TA where S-NSSAI is supported, there may be no network (e.g., wireless) resources allocated for S-NSSAI at all, or there may be limited network (e.g., wireless) resources allocated for S-NSSAI. When network slice availability does not coincide with the TA boundaries, the AMF provides S-NSSAI location availability information that defines restrictions on where within the TA S-NSSAI should be used. In this disclosure, the NS-AoS and S-NSSAI location availability information (transmitted to the UE) are used interchangeably and include location information indicating the cells in the TA within the RA where S-NSSAI is available, for each applicable S-NSSAI of the configured NSSAI.

[0037] An established PDU session associated with an S-NSSAI that is part of a partially authorized NSSAI is not released (i.e., not deleted in the control plane) when the UE moves to an area outside the support of the S-NSSAI, but the user plane connectivity / resources may be assumed to be deactivated. In other words, the data radio bearer and N3 (and / or N9) transport tunnel are deactivated, but the PDU session contexts of the UE, AMF, and SMF remain established. The UE is only allowed to initiate the establishment of an S-NSSAI PDU session when the S-NSSAI is within a supported TA. If the UE has already established a PDU session using the S-NSSAI portion of a partially authorized NSSAI, the UE is only allowed to activate the user plane resources of the PDU session when the UE is in the TA portion of the list of TAs associated with each S-NSSAI, as described in more detail below.

[0038] To cover both network slicing characteristics, namely "support for partial network slices in the registration area" and "network slice service area that does not coincide with the deployed tracking area," this disclosure uses the terms "inside / outside the S-NSSAI support or availability area," where "inside the S-NSSAI support area" means that the UE's current TA is part of the TA list for which S-NSSAI is supported, "outside the S-NSSAI support area" means that the UE's current TA is not included in the TA list for which S-NSSAI is supported, "inside the S-NSSAI availability area" means that the current UE's location is part of the NS-AoS associated with S-NSSAI, and "outside the S-NSSAI availability area" means that the current UE's location is outside the NS-AoS associated with S-NSSAI.

[0039] From the UE's perspective, if the UE is registered with an S-NSSAI that has a limited area of ​​support or availability, and the UE has already established a PDU session associated with the S-NSSAI (for example, suppose the UP resource for the PDU session is currently deactivated), the UE may initiate an SM signaling procedure to correct or release the SM context of the PDU session when the UE is outside the area of ​​support or availability of the S-NSSAI. The UE may also send a UL NAS transport message containing a 5GSM message associated with the S-NSSAI if: (1) the S-NSSAI is part of a partially authorized NSSAI and the current TAI is not on the list of TAs supported by the S-NSSAI; or (2) the S-NSSAI is associated with location availability information and the current cell (where the UE is camping) is outside the location information of the S-NSSAI. Correspondingly, for an SM procedure initiated by the network, the UE may receive and process NAS SM (or 5GSM) messages outside the area of ​​support or availability of the S-NSSAI.

[0040] From a network perspective (e.g., AMF, SMF), when AMF receives a UL NAS TRANSPORT message, AMF terminates the message, and if the payload is an N1 SM container (i.e., a NAS SM message), AMF sends the NAS SM message to SMF, which may include an indication that S-NSSAI is not supported at the current UE location (i.e., at the current TA). SMF determines that the NAS SM message (e.g., an N1 SM container) requires modification or release of the SM context, but based on the included indication that S-NSSAI is not supported at the current UE location, SMF decides not to activate the UP resource. SMF processes the SM message and, for example, releases or modifies the PDU session, but SMF does not initiate the activation of the UP resource (or connection).

[0041] Note that the terms “N1 SM message,” “N1 SM container,” or “NAS SM message” are used interchangeably in this specification. Similarly, the terms “N2 SM message” and “N2 SM container” are used interchangeably.

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

[0043] Figure 3 shows an exemplary signaling flow of a NAS SM signaling procedure initiated by a UE for a PDU session according to aspects of this disclosure. In particular, Figure 3 shows the call flow in a scenario where the UE initiates a NAS SM procedure for a PDU session related to S-NSSAI, and the UE is outside the area of ​​S-NSSAI support or availability.

[0044] In case 0 (see messaging 302), a PDU session exists between UE 301 and SMF 307. The PDU session is associated with an S-NSSAI that is (1) partially supported in RA (e.g., S-NSSAI is part of a partially authorized NSSAI), or (2) associated with location availability information or NS-AoS information (e.g., S-NSSAI Area of ​​Service not matching deployed Tracking Areas).

[0045] In 1a (see block 304), a higher layer of UE 301, or the NAS session management sublayer, may trigger an SM action for an established PDU session. For example, an existing PDU may need to be released (e.g., a PDU session initiated by the UE) or modified (e.g., a multi-access PDU session, or an MA PDU session may need to be modified to release or establish a leg on a particular access).

[0046] UE 301 considers its current location (e.g., evaluate) which means 1) is in a TA that supports the S-NSSAI associated with the PDU session, or 2) is in a cell outside or within the NS-AoS. UE 301 may be in either a Connected or Idle state and may be camped in a cell. UE 301 may proceed with the SM procedure for the PDU session even if it is in an area where the S-NSSAI associated with the PDU session (which triggers the SM procedure) is not supported or available.

[0047] In 1b (see messaging 306), UE 301 initiates an SM procedure (e.g., a 5GSM procedure) for an already established PDU session. If the PDU session is associated with S-NSSAI and UE 301 is currently 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 proceed to send SM signaling to SMF 307. If there is stored or pending UL data in UE 301, UE 301 should not use a request for service procedure to include the PDU session in the list of PDU sessions to be activated. Rather, UE 301 should trigger a NAS transport procedure to send a NAS SM message. For example, UE 301 may create a UL NAS TRANSPORT message containing an IE of payload container type indicating a single 5GSM message. Furthermore, the UL NAS TRANSPORT message may include PDU session information such as the PDU session ID and S-NSSAI.

[0048] UE 301 sends a UL NAS TRANSPORT message encapsulated in a Radio Resource Control (RRC) message to 5G-AN 303. 5G-AN 303 receives the UL NAS TRANSPORT message and encapsulates it in an N2 NG-AP message to AMF 305. The NG-AP message includes AN parameters and the UL NAS TRANSPORT 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 (which initiates NAS signaling on UE 301).

[0049] In step 2 (see block 308), AMF 305 receives an NG-AP message. If the UL NAS TRANSPORT message contains an N1 SM container (or NAS SM message), AMF 305 may need to evaluate whether the S-NSSAI associated with the relevant PDU session is part of a partially authorized NSSAI or whether the S-NSSAI is associated with NS-AoS information. If so, AMF 305 takes into account the location of UE 301 (e.g., current TA or cell ID) and determines whether 1) the current TA of UE 301 supports S-NSSAI, or 2) the current cell of UE 301 is included in NS-AoS. If the criteria for S-NSSAI support / validity are met, AMF 305 proceeds as usual to send the NAS SM message to the corresponding SMF 307. If the S-NSSAI support / availability criteria are not met, AMF 305 decides to send a NAS SM message to the corresponding SMF 307, which will also include an indication that UE 301 is outside the S-NSSAI support or availability area. The latter indication may be called, for example, "S-NSSAI out of support / availability area".

[0050] In 3a (see messaging 310), AMF 305 creates an N11 message and sends it to SMF 307, while the NAS SM message is encapsulated within the N11 message. For example, AMF305 may use the Nsmf_PDUSession_UpdateSMContext request service operation and include at least one of the following in the message: the SM context ID, the N1 SM container, and the indication "Out of Support / Availability Area S-NSSAI".

[0051] The indication "Out of Support / Availability Area S-NSSAI" is included to indicate to SMF 307 that the UP resource for the PDU session cannot be activated at the current location of UE 301. For example, if SMF or UPF stores downlink (DL) data for transmission, SMF will not initiate the activation of the UP resource (or connection) and will only process the SM procedure.

[0052] In 3b (see messaging 312), SMF 307 processes the received N1 SM container (e.g., a NAS SM signaling message). SMF 307 creates a NAS SM signaling message encapsulated in an N11 message and sends it to AMF 305. For example, SMF may use the Nsmf_PDUSession_UpdateSMContext response service operation, which includes at least one of the following: an SM context ID, a PDU session ID, or an N1 SM container.

[0053] In step 4 (see message 314), AMF 305 receives an N11 message containing an N1 SM container. AMF 305 creates a DL NAS transport message and sends it to UE 301. The DL NAS transport message is encapsulated in an NG-AP message to 5G-AN 303. The DL NAS transport message contains an N1 SM container containing a NAS SM message to UE 301.

[0054] In 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 takes action according to N1 SM container instructions, such as release / modify PDU session context. UE 301 processes the SM message without initiating the activation of the UP resource (or connection). For example, if the NAS SM message indicates the release of a PDU session, the UE NAS layer internally deletes the PDU session context.

[0055] In one embodiment, the advantage of the solution shown in Figure 3 is that when UE 301 is in an area where S-NSSAI for the PDU session is not supported or available, the UE 301 and the network (e.g., AMF 305, SMF 307) are able to perform SM procedures for the PDU session. In particular, in the case of releasing the PDU session, such a mechanism allows for the cleanup of the PDU session context in both the UE 301 and the network, which effectively reduces the resources consumed (e.g., storage of the PDU session context and associated possible signaling during the mobility of the UE 301).

[0056] In a second embodiment, a network (e.g., SMF) may request a NAS SM procedure for the PDU session, and the UE may happen to be in an area where S-NSSAI for the PDU session is not supported or available. The UP resource / connection for the PDU session is assumed to be unactivated.

[0057] Figure 4 shows an exemplary signal flow of a network-initiated NAS SM signaling procedure for a PDU session according to an aspect of this disclosure. As shown in Figure 4, it is proposed that a network (e.g., SMF 407) initiates NAS SM signaling to UE 401, and AMF 405 decides that UE 401 is outside the area of ​​S-NSSAI support or availability, but will deliver / transmit NAS SM messages in the NAS transport procedure.

[0058] In 0 (see messaging 402), a PDU session is established between UE 401 and SMF 407. In one embodiment, SMF 407 may not know that the S-NSSAI of the PDU session has limited support or limited availability in RA (i.e., S-NSSAI is associated with NS-AoS). In such an embodiment, SMF 407 may initiate N1 SM signaling to UE 401 or N2 SM signaling to 5G-AN 403 (for example, to activate UP resources). When SMF 407 sends a request to AMF 405 that includes N1 SM signaling or N2 SM signaling, it is left to AMF 405 to determine whether to forward or reject SMF 407's request. This is explained in 2 below.

[0059] In another embodiment, SMF 407 knows that the S-NSSAI for a PDU session has limited support or limited availability in the RA (i.e., the S-NSSAI is associated with NS-AoS). In such an embodiment, SMF 407 may request AMF 405 to inform it whether UE 401 is in or out of an area of ​​interest, which is either 1) a list of TAs in the RA where the S-NSSAI is supported, or 2) NS-AoS.

[0060] In 1a (see block 404), SMF 407 decides to initiate an SM for the established PDU session. It is assumed that the UP resource is not currently activated. The SM procedure may be to modify the PDU session or to release the PDU session. SMF 407 may decide to modify the PDU session, for example, by configuring a new ATSSS rule for the MA PDU session, informing UE 401 of an Alternative S-NSSAI, exchanging update quality of service (QoS) parameters, and / or sending updated ECS address configuration information to UE 401.

[0061] The SMF 407 may decide to release a PDU session based on various scenarios, such as locally configured policies (for example, the release procedure may be associated with UPF reassignment for SSC mode 2 / mode 3), the expiration of a timer related to the inactive state of the PDU session, the expiration of a timer for a temporary available network slice, or a combination thereof. In one embodiment, the SMF 407 creates an N1 SM that includes either a PDU session modification command message () or a PDU session release command message (PDU session ID, cause).

[0062] In step 1b (see message 406), SMF 407 sends an N1 SM message to UE 401. The N1 SM message may be either 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). SMF 407 encapsulates the N1 SM message in an N11 message and sends the N11 message to AMF 405.

[0063] For example, SMF 407 may use the Namf_Communication_N1N2MessageTransfer service operation, which includes an N1 SM container containing a PDU session release command or a PDU session modification command. Since the UP connection of the PDU session is not activated, the message sent by SMF 407 to AMF 405 does not include an N2 SM resource release request.

[0064] The “skip indicator” (or “N1 SM delivery skip allowed indication”) tells the AMF 405 whether it is permissible to 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 handles the “skip indicator” for the UE 401 as described in 3GPP TS 23.502 (incorporated herein by reference). The SMF 407 may also provide N2 SM information to the AMF 405 within the N11 message. This may occur if the SMF 407 decides to activate the UP resource / connection for the PDU session.

[0065] In section 2 (see block 408), AMF 405 may decide to deliver an N1 SM message even if the S-NSSAI is part of a partially authorized NSSAI or associated with NS-AoS information. In other words, if AMF 405 receives an N1 SM message from SMF 407, AMF 405 will deliver the message to UE 401 regardless of whether UE 401's location is within or outside the area of ​​support or availability for the PDU session's S-NSSAI.

[0066] When AMF 405 receives an N2 SM message from SMF 407 (for example, for activating a UP resource), AMF 405 must first determine whether the location of UE 401 is within or outside the S-NSSAI support or availability area for the PDU session. If the location of UE 401 is within the S-NSSAI support or availability area for the PDU session, AMF 405 decides to send the N2 SM message to 5G-AN 403. If the location of UE 401 is outside the S-NSSAI support or availability area for the PDU session, AMF 405 decides to refuse to send the N2 SM message to 5G-AN 403. AMF 405 sends a response to SMF 407 indicating the failure to send and providing additional indication of the appropriate reason for the refusal, for example, that the UE 401 is outside the S-NSSAI support or availability area for the PDU session.

[0067] In 3a (see messaging 410), if UE 401 is in the CM-IDLE state (and does not indicate "N1 SM delivery can be skipped"), AMF 405 may initiate a network-triggered request for service procedure to send a NAS message (PDU session ID, N1 SM container) to UE 401. For this purpose, AMF 405 initiates a paging procedure to UE 401.

[0068] In 3B (see messaging 412), UE 401 responds to the paging procedure with a request for service message. The RAN includes the current location of UE 401 (e.g., TA, cell ID) in the NG-AP message from 5G-AN carrying the request for service message.

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

[0070] In 4a (see block 414), if the state of UE 401 in AMF 405 is connected (for example, after AMF 405 receives a service request message), AMF 405 determines whether it should deliver the N2 SM message to 5G-AN 403. If AMF 405 has received the N2 SM message (and the current UP resource for the PDU session is not activated), AMF 405 may determine that SMF 407 wants to activate the UP resource.

[0071] If UE 401 is outside the area of ​​S-NSSAI support or availability for the PDU session, AMF 405 may decide to reject the N2 SM message. If UE 401 is within the area of ​​S-NSSAI support or availability for the PDU session, AMF 405 decides to send the N2 SM information to 5G-AN 403.

[0072] In 4b (see messaging 416), AMF 405 may send an Nsmf_PDUSession_UpdateSMContext service operation to SMF 407 that includes an indication that the N2 SM information is rejected (i.e., will not be sent / delivered to 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 UE 401 is currently in an area where S-NSSAI is not supported or available.

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

[0074] In 4c (see messaging 418), the AMF 405 creates a DL NAS transport message and sends it to the UE 401. The DL NAS transport message is encapsulated in an NG-AP message to the 5G-AN 403. The DL NAS transport message contains an N1 SM container that includes the NAS SM message to the UE 401. For example, the DL NAS transport message to the UE 401 includes 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 of these.

[0075] In step 5 (see block 420), UE 401 receives the DL NAS transport message, extracts the NAS SM message, and forwards the NAS SM message 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 takes action according to N1 SM container instructions, such as PDU session context release / modification. UE 401 processes SM messages without initiating the activation of UP resources (or connections). For example, if the NAS SM message indicates the release of a PDU session, the UE NAS layer internally deletes the PDU session context.

[0076] In 6a (see message 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 in 4c. In one example, the N1 SM reply message may be a PDU session modification command ACK or a PDU session release command ACK message.

[0077] In 6b (see messaging 426), AMF 405 forwards the N1 SM container (PDU session correction command ACK) and user location information received from AN to SMF 407 via the Nsmf_PDUSession_UpdateSMContext service operation. SMF 407 responds with an Nsmf_PDUSession_UpdateSMContext response.

[0078] In one embodiment, the advantage of the solution in Figure 4 is that the network AMF 405 can determine whether to allow the activation of the UP resource for the PDU session, i.e., whether to send N2 SM information to the 5G-AN 403, based on the current location of the UE 401, which is inside or outside the area of ​​S-NSSAI support or availability for the PDU session. Furthermore, the AMF 405 decides to send an N1 SM message to the UE 401 even though the UE 401 is outside the area of ​​S-NSSAI support or availability.

[0079] In a third embodiment, when the UE is in an area where S-NSSAI related to a PDU session is not supported or available, the UE may initiate either 1) a PDU session establishment procedure for a new connection, or 2) a service request procedure for an already established PDU session. Such a scenario may be either (1) an error on the part of the UE that does not support the partial support or availability features of S-NSSAI, or (2) the UE does not support the partial support or availability features of S-NSSAI.

[0080] Typically, a UE that supports the network slice features "partial network slice support in the registration area" and / or "network slice service area that does not coincide with the deployed tracking area" should not initiate activation of UP resources / connections for a PDU session when the UE is outside the area of ​​S-NSSAI support or availability for the PDU session. However, if the UE does not support the features, or if it supports the features but requests activation of UP resources / connections for a PDU session for other reasons, the network (e.g., AMF or SMF) should reject the UE's request.

[0081] When a UE initiates a service request procedure to activate an UP connection for a PDU session related to 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 (where 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 of S-NSSAI. If conditions 1) and 2) are not met, the AMF refuses to activate the UP resource for the PDU session. For example, the AMF sends a service request message.

[0082] Figure 5 shows an exemplary signaling flow for refusing to activate the UP resource for a PDU session when the UE is outside of S-NSSAI support / availability, according to an aspect of this disclosure.

[0083] In case 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 RA (for example, the S-NSSAI is part of a partially authorized NSSAI), or the S-NSSAI is associated with NS-AoS information (for example, an S-NSSAI service area that does not match the deployed tracking area). In another embodiment, UE 501 may have only registered with the S-NSSAI and has not yet established a PDU session.

[0084] In step 1 (see messaging 504), UE 501 initiates a request for service procedure to activate the UP connection of a PDU session related to S-NSSAI (which is not supported in the current TA), and UE 501 includes the PDU session ID in the list of PDU sessions to be activated in the request for service message.

[0085] UE 501 sends a request for service message to 5G-AN 503, encapsulated in an RRC message. 5G-AN 503 receives the request for service message and encapsulates it in an N2 NG-AP message to AMF 505. The NG-AP message includes AN parameters and the request for service 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 (which initiates NAS signaling on UE 501).

[0086] In another scenario, UE 501 might initiate a PDU session establishment request for an S-NSSAI with partial support or availability, assuming that UE 501 has previously registered with S-NSSAI. In such a scenario, UE 501 sends a UL NAS transport message containing an N1 SM container with the PDU session establishment request message. While the use case for a service request message is assumed in the further explanation in Figure 5, the solution may also apply to the case of a PDU session establishment request.

[0087] In step 2 (see block 506), AMF 505 determines whether 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 a partially authorized NSSAI and associated with a list of TAs in the RA) or has limited availability (i.e., the S-NSSAI is associated with an NS-AoS). Then, AMF 505 needs to determine whether UE 501 is inside / outside the area of ​​support / availability of the S-NSSAI for the PDU session.

[0088] In one embodiment, if S-NSSAI is included in a partially authorized NSSAI and associated with a list of TAs in the RA, and the current TA (where UE 501 is located) is part of the list of TAs for which S-NSSAI is supported, AMF 505 proceeds with the service request procedure for activating the UP resource for the PDU session.

[0089] In one embodiment, if S-NSSAI is included in a partially authorized NSSAI and associated with a list of TAs in the RA, and the current TA (where UE 501 is located) is not part of the list of TAs for which S-NSSAI is supported, AMF 505 decides to reject the service request procedure for activating the UP resource for the PDU session. AMF 505 proceeds to step 3.

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

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

[0092] In option 3 for AMF-initiated denial of UP resource activation (see messaging 508), AMF 505 sends either an accept or deny service message indicating that the requested activation of the UP resource / connection for the PDU session is denied. AMF 505 may also include a suitable cause for denial, for example, that the network slice resource is unavailable at the current location.

[0093] In Option 2 4a (see messaging 510), where AMF 505 indicates to SMF 507 that it is initiating the denial of activating the UP resource, AMF 505 may decide to notify SMF 507 that UE 501 is requesting activation of the PDU session, and further, AMF 505 may include an indication that S-NSSAI is outside the Support / Availability Area. For example, AMF 505 may send an Nsmf_PDUSession_UpdateSMContext request message to SMF 507 that includes the PDU session ID, the indication "S-NSSAI outside Support / Availability Area", or a combination thereof.

[0094] When UE 501 receives an indication that it is outside the S-NSSAI support / availability area, SMF 507 creates an N1 SM container containing an SM message indicating that activation of the PDU session is denied because S-NSSAI is not supported or available, and sends it to UE 501.

[0095] In part of option 2, in 4b (see messaging 512), AMF 505 receives an N1 SM container from SMF 507 containing an SM message rejecting activation of the PDU session due to an unsupported / unavailable S-NSSAI. AMF 505 creates and sends a DL NAS transport message containing the PDU session ID, an N1 SM container containing an SM message indicating that activation of the PDU session is rejected because the S-NSSAI is unsupported or unavailable in the current location area, or a combination thereof.

[0096] In step 5 (see block 514), upon receiving notification of 3 or 4b, the UE NAS SM sublayer receives the N1 SM container. Based on the indication that activation of the PDU session is denied because the S-NSSAI is not supported or available in the current location area, UE 501 blocks the transmission of user plane data (i.e., blocks the activation of the UP resource). In other words, UE 501 considers the PDU session to be unavailable for data transmission and 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.

[0097] In one embodiment, the advantage of the solution in Figure 5 is that the network can decide and execute to reject a request from a UE to initiate activation of a PDU session resource based on the current UE 501 being in an area where S-NSSAI is not supported or available (see 2, 3, and 4).

[0098] Figure 6 shows an example of a UE 600 according to an aspect of this disclosure. The UE 600 may include a processor 602, memory 604, controller 606, and transceiver 608. The processor 602, memory 604, controller 606, or transceiver 608, or various combinations thereof or various components thereof, may be examples of means for performing various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (for example, operationally, communicatively, functionally, electronically, or electrically).

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

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

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

[0102] In some implementations, 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 (for example, by having the processor 602 execute instructions stored in the memory 604). For example, the processor 602 may support wireless communication in the UE 600 according to the examples disclosed herein. The UE 600 may be configured to support means for transmitting signaling relating to SM procedures for established PDU sessions associated with a network slice, where the network slice is not supported or available in the UE's location area, receiving NAS SM messages as part of the SM procedures for the PDU session, and taking action in accordance with the NAS SM messages without initiating the activation of user plane resources for the PDU session.

[0103] In one implementation, the UE 600 may be configured or operable to support means for advancing SM procedures for a PDU session, even if the UE is in an area where a single S-NSSAI is not supported or available. In some implementations, the UE 600 may be configured or operable to support means for sending signaling to the SMF as part of a PDU session, even if the UE is in an area where S-NSSAI is not supported or available.

[0104] Controller 606 may manage input and output signals for the UE 600. Controller 606 may also manage peripherals not integrated with the UE 600. In some implementations, Controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, Controller 606 may be implemented as part of Processor 602.

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

[0106] 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 via radio or 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 by inverting the modulation technique applied during the transmission of the signal to obtain the transmit data. The receiver chain 610 may include at least one decoder for decoding the processing of the demodulated signal to receive the transmit data.

[0107] 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 into a carrier signal, preparing the signal for transmission over a wireless medium. 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 suitable for transmission over a wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal wirelessly or to a wireless medium.

[0108] Figure 7 shows an example of a processor 700 according to an aspect of the present disclosure. 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 communicate electronically via one or more interfaces (e.g., buses) or otherwise be coupled (e.g., operationally, communicatively, functionally, electronically, electrically).

[0109] The processor 700 is a processor chipset and may include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, transfer, store, determine, identify, access, write, read) in accordance with the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., local memory of the processor chipset (e.g., processor 700) or memory contained within 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), etc.).

[0110] The controller 702 may be configured to manage and coordinate various operations of the processor 700 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, transferring, storing, determining, identifying, accessing, writing, and reading) in order to enable the processor 700 to support various operations as described herein. For example, the controller 702 may act as a control unit for the processor 700 and generate 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 the timing of operations.

[0111] The controller 702 may be configured to fetch (e.g., acquire, retrieve, receive) instructions from memory 704 and determine subsequent instructions to be executed to enable 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 related to memory 704. The controller 702 may be configured to decode instructions and 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 enable the processor 700 to support various operations, according to the examples described herein. Additionally or alternatively, the controller 702 may be configured to manage the flow of data within the processor 700. The controller 702 may be configured to control the transfer of data between the registers of the processor 700, the arithmetic logic unit (ALU), and other functional units.

[0112] Memory 704 may include one or more caches (for example, local to or contained within the processor 700), or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, or flash memory. In some implementations, memory 704 may reside within or on the processor chipset (for example, locally with the processor 700). In some other implementations, memory 704 may reside outside the processor chipset (for example, remotely with the processor 700).

[0113] Memory 704 may store computer-readable and computer-executable code, which includes instructions that cause the processor 700 to perform various functions described herein when executed by the processor 700. The code may be stored in a non-temporary 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 computer-readable instructions stored in memory 704 to cause the processor 700 to perform various functions. For example, the processor 700 and / or the controller 702 may be coupled to or with memory 704, and the processor 700, controller 702, and memory 704 may be configured to perform various functions described herein. In some examples, the processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, and they may be configured individually or collectively to perform various functions described herein.

[0114] One or more ALUs 706 may be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs 706 may reside within or on a processor chipset (e.g., processor 700). In some other implementations, one or more ALUs 706 may reside outside of a processor chipset (e.g., processor 700). One or more ALUs 706 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 706 may receive input operands and an operation code that determines the operation to be performed. One or more ALUs 706 may consist of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, for processing and manipulating data by the calculations. Additionally or alternatively, one or more ALU 706s may support logical operations such as AND, OR, exclusive OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALU 706s to handle conditional operations, comparisons, and bitwise operations.

[0115] The processor 700 may support wireless communication in accordance with the examples disclosed herein. The processor 700 may be configured or operable to support means for receiving a first SM message relating to a network slice and a PDU session associated with the UE, means for determining that the network slice is not supported or available in the UE's location area, a second SM message, and means for transmitting an indication that the network slice is not supported or available in the UE's location area.

[0116] In some implementations, the first SM message is an N1 SM message received from the UE and encapsulated in an uplink NAS transport message. In one implementation, the second SM message is sent to the SMF and encapsulated in a PDU session update request message.

[0117] In some implementations, the second SM message is an N2 SM message directed to the AN. In one implementation, the processor 700 is configured to instruct the NE to refrain from delivering an N2 SM message to the AN in response to a determination that the network slice is not supported or available in the UE's location area.

[0118] In some implementations, 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 available in the UE's location area. In one implementation, the processor 700 includes an AMF.

[0119] In one implementation, the processor 700 may be configured or operable to support means of transmitting signaling relating to an SM procedure for an established PDU session associated with a network slice, and transmitting, receiving NAS SM messages as part of the SM procedure for the PDU session, and taking action in accordance with the NAS SM messages without initiating the activation of user plane resources for the PDU session.

[0120] In one implementation, the processor 700 may be configured or operable to support means for advancing SM procedures for a PDU session, even if the UE is in an area where a single S-NSSAI is not supported or available. In some implementations, the processor 700 may be configured or operable to support means for sending signaling to the SMF as part of a PDU session, even if the UE is in an area where S-NSSAI is not supported or available.

[0121] Figure 8 shows an example of an NE 800 according to an aspect of the present disclosure. The NE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations thereof or various components thereof, may be examples of means for performing various aspects of the present disclosure described herein. These components may be coupled via one or more interfaces (for example, operationally, communicatively, functionally, electronically, or electrically).

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

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

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

[0125] In some implementations, 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 (for example, by executing instructions stored in the memory 804 by the processor 802). For example, the processor 802 may support wireless communication in the NE 800 according to the examples disclosed herein. The NE 800 may be configured to support means for receiving a first SM message relating to a network slice and a PDU session associated with the UE, means for determining that the network slice is not supported or available in the UE's location area, a second SM message, and means for transmitting an indication that the network slice is not supported or available in the UE's location area.

[0126] In some implementations, the first SM message is an N1 SM message received from the UE and encapsulated in an uplink NAS transport message. In one implementation, the second SM message is sent to the SMF and encapsulated in a PDU session update request message.

[0127] In some implementations, the second SM message is an N2 SM message directed to the AN. In one implementation, the NE 800 is configured to instruct the NE to refrain from delivering an N2 SM message to the AN in response to a determination that the network slice is not supported or available in the UE's location area.

[0128] In some implementations, 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 available in the UE's location area. In one implementation, the NE 800 includes an AMF.

[0129] Controller 806 may manage input and output signals for the NE 800. Controller 806 may also manage peripherals not integrated with the NE 800. In some implementations, Controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, Controller 806 may be implemented as part of Processor 802.

[0130] In some implementations, the NE 800 may include at least one transceiver 808. In some other implementations, the NE 800 may have two or more transceivers 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.

[0131] 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 via radio or a 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 by inverting the modulation technique applied during the transmission of the signal to obtain the transmit data. The receiver chain 810 may include at least one decoder for decoding and processing the demodulated signal to receive the transmit data.

[0132] 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 into a carrier signal, 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 suitable for transmission over a wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal wirelessly or to a wireless medium.

[0133] Figure 9 shows a flowchart of a method according to an aspect of the present disclosure. The operation of the method may be performed by a UE as described herein. In some implementations, the UE may execute a set of instructions for controlling functional elements of the UE to perform the described function.

[0134] In 902, the method may include the step of triggering an SM action for a PDU session associated with a network slice that is not supported or available in the UE's location area. The operation of 902 may be performed according to the examples described herein. In some implementations, the operation of 902 may be performed by the UE as described with reference to Figure 6.

[0135] In 904, the method may include the step of receiving a NAS SM message during a PDU session. The operation of 904 may be performed according to the examples described herein. In some implementations, the operation of 904 may be performed by the UE as described with reference to Figure 6.

[0136] In 906, the method may include the step of performing an action in accordance with a NAS SM message without starting a user plane resource. The operation of 906 may be performed according to the examples described herein. In some implementations, the mode of operation of 906 may be performed by the UE as described with reference to Figure 6.

[0137] Note that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations may exist.

[0138] Figure 10 shows a flowchart of a method according to an aspect of the present disclosure. The operation of the method may be carried out by an NE as described herein. In some implementations, the NE may execute a set of instructions for controlling the functional elements of the NE in order to perform the function described.

[0139] In 1002, the method may include the step of receiving a first SM message relating to a network slice and a PDU session associated with the UE. The operation of 1002 may be performed according to the examples described herein. In some implementations, the operation of 1002 may be performed by the NE as described with reference to Figure 8.

[0140] In 1004, the method may include the step of determining that a network slice is not supported or available in the location area of ​​the UE. The operation of 1004 may be performed according to the examples described herein. In some implementations, the operation of 1004 may be performed by the NE as described with reference to Figure 8.

[0141] In 1006, the method may include the step of sending a second SM message and an indication that the network slice is not supported or available in the UE's location area. The operation of 1006 may be performed according to the examples described herein. In some implementations, the operation of 1006 may be performed by the NE as described with reference to Figure 8.

[0142] Note that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations may exist.

[0143] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the comprehensive principles defined herein may be applied to other modified forms without departing from the scope of this disclosure. Accordingly, this disclosure is not limited to the examples and designs described herein and should be given the broadest scope that conforms to the principles and novel features disclosed herein. [Explanation of Symbols]

[0144] 100 Wireless Communication Systems 102 NE 104 UE 106 CN 112 Geographic Coverage Area 114 Communication Link 202 TA1 204 TA2 206 TA3 208 UE 301 UE 303 5G-AN 305 AMF 307 SMF 401 UE 403 5G-AN 405 AMF 407 SMF 501 UE 503 5G-AN 505 AMF 507 SMF 600 UE 602 Processors 604 memory 606 Controller 608 Transceiver 610 Receiver Chain 612 Transmitter Chain 700 processor 702 Controller 704 memory 706 ALU 800 NE 802 Processor 804 memory 806 Controller 808 Transceiver 810 Receiver Chain 812 Transmitter Chain

Claims

1. Network entities (NEs) At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor is connected to the NE, Receiving a first session management (SM) message relating to protocol data unit (PDU) sessions associated with network slices and user equipment (UE), Determining that the network slice is not supported or available in the area where the UE is located, Sending a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE. NE is configured to perform the following action.

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

3. The NE according to claim 2, wherein the second SM message is sent 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 targeting an access network (AN).

5. The NE according to claim 4, wherein the at least one processor is configured to cause the NE to refrain from delivering the N2 SM message to the AN in response to a determination that the network slice is not supported or available 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 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 available in the location area of ​​the UE.

7. The NE according to claim 1, including access and mobility management functions (AMF).

8. A processor for wireless communication, It comprises at least one controller coupled to at least one memory, and the at least one controller controls the processor, Receiving a first session management (SM) message relating to protocol data unit (PDU) sessions associated with network slices and user equipment (UE), Determining that the network slice is not supported or available in the area where the UE is located, Sending a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE. A processor configured to perform the following task.

9. The processor according to claim 8, wherein the first SM message is an N1 SM message received from the UE and encapsulated in an uplink non-access layer (NAS) transport message.

10. The processor according to claim 9, wherein the second SM message is sent to the Session Management Function (SMF) and encapsulated in a PDU session update request message.

11. The processor according to claim 8, wherein the second SM message is an N2 SM message targeting an access network (AN).

12. The processor according to claim 11, wherein the at least one controller is configured to cause the processor to refrain from delivering the N2 SM message to the AN in response to a determination that the network slice is not supported or available in the location area of ​​the UE.

13. The processor according to claim 12, wherein the at least one controller is configured to cause the processor 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 available in the location area of ​​the UE.

14. The processor according to claim 8, including access and mobility management functions (AMF).

15. A method performed by network functions, The steps include receiving a first session management (SM) message relating to a protocol data unit (PDU) session associated with a network slice and user equipment (UE), The steps include determining that the network slice is not supported or available in the location area of ​​the UE, The steps include sending a second SM message and an indication that the network slice is not supported or available in the location area of ​​the UE, Methods that include...

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

17. The method according to claim 16, wherein the second SM message is sent to the Session Management Function (SMF) and encapsulated in a PDU session update request message.

18. User equipment (UE) for wireless communication, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, Transmitting signaling relating to session management (SM) procedures for established protocol data unit (PDU) sessions associated with a network slice, wherein the network slice is not supported or available in the area where the UE is located. Receiving a Non-Access Layer (NAS) SM message as part of the SM procedure for the PDU session, To perform an action in accordance with the NAS SM message without initiating the activation of user plane resources for the PDU session. A UE configured to perform the following actions.

19. The UE according to claim 18, wherein the at least one processor is configured to cause the UE to proceed with the SM procedure for the PDU session, even if the UE is in an area where Single Network Slice Selection Assistance Information (S-NSSAI) is not supported or available.

20. The UE according to claim 19, wherein the at least one processor is configured to cause the UE to send the signaling to the Session Management Function (SMF) as part of the PDU session, even if the UE is in an area where S-NSSAI is not supported or available.

Images