Retrieving a data network name of a data session in a wireless communication network

Abstract

Various aspects of the disclosure relate to a first network entity comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to receive a first indication for a data session of a user equipment (UE), wherein the first indication indicates to replace a first network slice with a second network slice; select an assigned data network name for the data session, wherein the assigned data network name is applicable to the second network slice; and transmit, to a second network entity, a request for a data session establishment comprising the assigned data network name.

Description

Technical Field

[0001] The subject matter disclosed herein generally pertains to the field of retrieving data network names for data sessions within wireless communication networks. This document defines a first network entity and a second network entity, as well as methods thereof. Background Technology

[0002] A wireless communication system may include one or more network communication devices (e.g., base stations) that support wireless communication for one or more user communication devices, which may otherwise be referred to as user equipment (UE) or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Furthermore, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a” preceding an element is unrestricted and is understood to refer to “at least one” or “one or more” of the elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, “or” as used in the claims, such as in a list of items (e.g., a list of items preceded by phrases such as “at least one of…”, “one or more of…”, or “one or both of…”), indicates a list of inclusions, such 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 (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a set of closed conditions. For example, an example step described as “based on condition A” may 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 understood in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, the term "group" may include one or more elements as contained in the claims.

[0004] This document provides a first network entity comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the first network entity: receives a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a first network slice be replaced with a second network slice; selects an assigned data network name for the data session, wherein the assigned data network name is applicable to the second network slice; and transmits a request to a second network entity for the establishment of a data session including the assigned data network name.

[0005] This document provides a method performed by a first network entity, the method comprising: receiving a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a first network slice is to be replaced with a second network slice; selecting an assigned data network name for the data session, wherein the assigned data network name is applicable to the second network slice; and transmitting a request to a second network entity for the establishment of a data session including the assigned data network name.

[0006] This document provides a third network entity comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the third network entity to: receive a second instruction from a first network entity, wherein the second instruction indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice; and transmit an instruction to the first network entity for the second data network name, wherein the second data network name is applicable to the second network slice.

[0007] This document provides a method performed by a third network entity, the method comprising: receiving a second indication from a first network entity, wherein the second indication indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice; and transmitting an indication of the second data network name to the first network entity, wherein the second data network name is applicable to the second network slice. Attached Figure Description

[0008] Figure 1 Examples of wireless communication systems according to aspects of this disclosure are described.

[0009] Figure 2 Describe the architecture used for a communication network that includes two network slices.

[0010] Figure 3a and 3b This section describes a signaling diagram illustrating the process between nodes in a communication network that includes two network slices.

[0011] Figure 4 An example of a user equipment (UE) 400 according to aspects of this disclosure is described.

[0012] Figure 5 An example of processor 500 according to aspects of this disclosure is described.

[0013] Figure 6 An example of a network equipment (NE) 600 according to aspects of this disclosure is described.

[0014] Figure 7 A flowchart illustrating the method performed by NE according to aspects of this disclosure.

[0015] Figure 8 A flowchart illustrating the method performed by NE according to aspects of this disclosure. Detailed Implementation

[0016] The examples described herein relate to providing a data network name for a data session of a UE registered on a first network slice, and specifically, selecting an assigned data network when the first network slice is replaced by a second network slice. Selecting an assigned data network name that is applicable to the second network slice tends to avoid rejecting data session establishment requests between network entities.

[0017] Aspects of this disclosure are described in the context of wireless communication systems.

[0018] Figure 1 This section describes an example of a wireless communication system 100 according to aspects of this 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-A network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0019] One or more NEs 102 may be distributed 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, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be wireless or wired. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

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

[0021] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some embodiments, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally, or alternatively, 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, and other instances thereof.

[0022] UE 104 may be able to support direct wireless communication with other UE 104 via a communication link. For example, UE 104 may support direct wireless communication 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 may be referred to as a side link. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0023] NE 102 may support communication with CN 106, or with another NE 102, or both. For example, NE 102 may interface with other NE 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 NE 102 may include sub-components, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0024] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN106 can 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), access and mobility management functions (AMF)) and user plane entities that route or interconnect packets 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 bearers, signaling bearers, etc.) of one or more UEs 104 served by one or more NEs 102 associated with CN106.

[0025] CN 106 can 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 contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session or the like) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, and the like) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

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

[0027] The wireless communication system 100 may support one or more parameter sets, 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 regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular 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 regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0028] Time intervals for organizing resources (e.g., communication resources) can be based on frames (also called radio frames). Each frame may have a duration, such as 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, such as 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.

[0029] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain 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, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals 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 contain a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot for both the regular and extended cyclic prefixes, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

[0030] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, 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 names 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, NE 102 and UE 104 can perform wireless communication through one or more of the operating frequency bands. In some embodiments, FR1 can be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.

[0031] 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) containing a 15 kHz subcarrier spacing; a second parameter set (e.g., μ=1) containing a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ=2) containing 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) containing a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ=3) containing a 120 kHz subcarrier spacing.

[0032] The wireless communication system 100 may be an example of a 5G network system (also known as 5GS) that supports network slicing, which enables network operators to divide the network into (“slices”) at a more granular level, called a customized full network, in order to provide customized network connectivity (or network characteristics) to network customers or application service providers.

[0033] A network slice is a logical network consisting of a set of network functions and corresponding resources (e.g., computing, storage, networking) used to provide certain network capabilities and characteristics. A network slice may include a core network (5G core network, 5GC) control plane and user plane, as well as access networks (e.g., 5G radio access network or fixed access network). The 5GC control plane and user plane may consist of network functions (NFs).

[0034] When UE 104 registers with a network (e.g., with 5GS), UE 104 may be configured to use one or more network slices of the network. UE 104 may be configured with network slice-related information, which may be referred to as Network Slice Selection Assistance Information (NSSAI). NSSAI may consist of one or more Single Network Slice Selection Assistance (S-NSSAI) messages. In other words, S-NSSAI may be referred to as the identifier of a network slice in a given network.

[0035] UE 104 may request registration with one or more network slices by outputting (e.g., transmitting) a NAS registration request message containing a requested NSSAI to the network (e.g., AMF), wherein the requested NSSAI may contain a list of one or more S-NSSAIs that UE 104 wishes to register with. 5GC (e.g., AMF) may output (e.g., transmit) one or more of the following elements related to UE 104's network slice configuration in a registration acceptance message or in a UE 104 configuration update command message: allowed NSSAIs, configured NSSAIs, rejected NSSAIs, or pending NSSAIs. The NSSAI may be a list of one or more S-NSSAIs.

[0036] Figure 2 This describes the architecture 200 for a communication network that includes two network slices.

[0037] Architecture 200 includes User Equipment (UE) 210 and a (radio) access network 220 shared between a first network slice 230 (identified as S-NSSAI#1) and a second network slice 240 (identified as S-NSSAI#2). The first network slice 230 and the second network slice 240 include common control plane network functions 222. The first network slice 230 includes a first control plane (C plane) 232, which includes a first SMF 234 and other network functions (NFs) 236. The first SMF 234 is accessible through a first user plane function (UPF) 238. Similarly, the second network slice 240 includes a second C plane 242, which includes a second SMF 244 and other NFs 246. The second SMF 244 is accessible through a second UPF 248.

[0038] Architecture 200 can be an example 5GS architecture, in which the UE can register with a first network slice 230 and a second network slice 240 (identified by S-NSSAI#1 and S-NSSAI#2). Network slices 230 and 240 can be deployed accordingly on the first network slice example depicted by solid lines and the second network slice example depicted by dashed lines. According to this example architecture 200, the (radio)access network "(R)AN" is a part of both slices and is shared. The CN portion of the network slice (or network slice example) has CCNF 222 and dedicated CN network functions. In some instances, CCNF 222 may include Access and Mobility Management Function (AMF), Network Slice Selection Function (NSSF), Unified Data Management (UDM), Unified Data Repository (UDR), Authentication Server Function (AUSF), and Network Slice Assisted Authentication and Authorization Function (NSSAAF) or one or more of other NFs. In another instance, the dedicated CN NF can be the first SMF 234, the first UPF 238, the first PCF and other NFs belonging to the first network slice 230 (S-NSSAI#1) and the second SMF 244, the second UPF 248, the second PCF and other NFs belonging to the second network slice 240 (S-NSSAI#2).

[0039] The support for network slice service continuity during UE 210 mobility has been studied in 3GPP TR 23.700-41, V1.1.0, 2022-10, “Study on enhancement of network slicing, Phase 3, (Revision 18)”, attributing to the lack of support for network slicing or resource limitations on network slicing in the target RAN node. The scenario described in 3GPP TR 23.700-41, V1.1.0, 2022-10 may occur due to the fact that network slices do not need to be available in all tracking areas (TAs) of the network. A common idea is to implement network slice replacement with alternative network slices (e.g., referred to as alternative S-NSSAI); for example, replacing the first network slice 230 with a second network slice. Network slice replacement is expected to occur at certain time intervals.

[0040] The following scenarios (or events) may occur in the network that necessitate changes to network slices. For example, the first network slice 230 (S-NSSAI-1) may need to be swapped with the second network slice 240 (S-NSSAI-2).

[0041] Some of the instances described in this document may involve no-mobility scenarios. In no-mobility scenarios, a network slice or network slice instance may become overloaded or undergo planned maintenance in the CN (e.g., network slice termination). In some instances, no-mobility scenarios may cause the network performance of a network slice to fail to meet the Service Level Agreement (SLA) agreed with the network slice customer, and therefore UE 210 should use another network slice that better meets the SLA.

[0042] Some of the examples described in this article may involve mobility scenarios. Mobility scenarios, especially those involving inter-Region (RA) mobility where network slices or network slice examples may become overloaded in the target CN.

[0043] If an existing network slice or network slice example cannot serve a Protocol Data Unit (PDU) session, or if an existing network slice example cannot meet the performance requirements of an application, then the network operator may wish to (e.g., temporarily) replace this network slice (e.g., identified by the old S-NSSAI) with an alternative network slice (e.g., identified by the alternative S-NSSAI).

[0044] In some instances, when UE 210 roams in a visited PLMN (e.g., VPLMN), UE 210 can use a home route PDU session, where the PDU session is anchored in the home PLMN (e.g., HPLMN). The PDU session is set on the S-NSSAI in the VPLMN (e.g., VPLMN S-NSSAI) and the S-NSSAI in the HPLMN (e.g., HPLMN S-NSSAI). UE 210's allowed NSSAI contains the VPLMN S-NSSAI and a mapping from the VPLMN S-NSSAI to the HPLMN S-NSSAI. There are scenarios where the HPLMN should be able to replace the S-NSSAI used in the HPLMN, where the alternative HPLMN S-NSSAI is configured within the HPLMN and sent to the VPLMN that will be configured in the UE.

[0045] In some of the examples described herein, according to the 3GPP standard, the first network entity may be the Access and Mobility Management Function (AMF), the second network entity may be the Session Management Function (SMF), the third network entity may be the Policy Control Function, and the data session may be a Packet Data Unit session.

[0046] UE 210 may provide UE Routing Policy (URSP) rules. UE 210 uses URSP rules to determine how to route outgoing services. For example, services can be routed to an established PDU session. In some instances, services can be routed through a new PDU session. In some instances, services can be offloaded to non-3GPP access outside the PDU session. In some instances, services can be routed to a network trunk via a ProSe Layer-3 UE outside the PDU session.

[0047] In some instances, during PDU session establishment on S-NSSAI#1 and when network slice replacement features are supported, UE 210 may transmit to the AMF 1) S-NSSAI#1, which is typically determined by the URSP policy, 2) an alternative S-NSSAI#2, if UE 210 is configured with network slice replacement information, and 3) the requested DNN, which is typically determined from the URSP policy. If an alternative S-NSSAI#2 is not included and the AMF determines that the requested S-NSSAI#1 should be replaced, then the AMF may select an alternative S-NSSAI#2. It should be noted that the AMF determines the alternative S-NSSAI#2 based on notifications from the Network Slice Selection Function (NSSF), PCF, or Operation, Management and Maintenance (OAM) system.

[0048] In some instances, the AMF sends an alternative S-NSSAI, an associated replacement S-NSSAI, and a DNN requested by the UE 210 to the first SMF 234. The first SMF 234 can download the SM subscription data to be applied to this PDU session from the UDM. The subscription information for each S-NSSAI may contain a list of subscribed DNNs and a default DNN. The UE 210 may be configured with URSP rules describing how to establish a PDU session. The URSP rules may further contain the HPLMN S-NSSAI and one or more corresponding DNNs to be used. The HPLMN S-NSSAI and DNN configured in the URSP rules in the UE 210 may correspond to the S-NSSAI and DNN stored in the SM subscription data stored in the UDM / UDR.

[0049] In some instances, the second SMF 244 establishes a PDU session on the alternative S-NSSAI#2 and using the requested DNN. Additionally, the second SMF 244 stores in the SM context and sends to the UE 210 information that the alternative S-NSSAI#2 is mapped to the replaced S-NSSAI#1.

[0050] In some instances, when network slice replacement is in place, during the PDU session establishment or modification procedure, the AMF receives alternative S-NSSIA#1 from UE210, or the AMF determines to use alternative S-NSSAI#2 to replace S-NSSAI#1.

[0051] In some instances, the URSP rules configured in UE 210 are up-to-date, and therefore the DNN requested by UE 210 may be up-to-date for the first network slice (S-NSSAI#1). In some instances, UE 210 does not have any DNN configured for use with the alternative S-NSSAI#2. Therefore, the DNN requested by UE 210 is considered applicable to S-NSSAI#1, but may not be applicable to the alternative S-NSSAI#2. The DNN requested by UE 210 may be the first data network name (first DNN). Since the PDU is built on S-NSSAI#2, the requested DNN may not be available on S-NSSAI#2. In some instances, a method is provided for determining and providing an assigned DNN suitable for use with S-NSSAI#2. The assigned DNN may be an alternative DNN to the DNN requested by UE 210. The assigned DNN may be the second data network name (second DNN).

[0052] In some instances, multiple SMFs can be configured to serve an alternative S-NSSAI#2, such as a first set of SMFs for the first DNN used in S-NSSAI#2 and a second set of SMFs for the second DNN used in S-NSSAI#2. In this case, the AMF may not be able to select a serving SMF for a PDU session on the alternative S-NSSAI#2 because the DNN requested by UE 210 may be different from both the first and second DNNs.

[0053] In some instances, the 5GS system supports a feature called DNN replacement. DNN replacement can be applied in scenarios where UE 210 operates using local configuration, or in scenarios where operator policies can be used to replace the DNN requested by UE 210 with another DNN used only within the network. To apply the DNN replacement feature, during the UE 210 registration procedure, the PCF indicates to the AMF the operator policy for DNN replacement of the DNN requested by UE 210 to be used at the PDU session establishment. The PCF may indicate a policy for DNN replacement of the DNN requested by UE 210 that is not supported by the network, and / or the PCF may indicate a list of DNNs requested by UE 210 that are valid for the serving network and require replacement per S-NSSAI. In other words, the PCF provides a policy to the AMF, causing the AMF to contact the PCF to perform DNN replacement for a specific DNN.

[0054] In some instances, suppose UE 210 is subscribed to use a network slice, for example, identified as S-NSSAI#1, and due to some of the reasons mentioned above, S-NSSAI#1 must be replaced. In other words, a network slice replacement feature occurs. The network (e.g., AMF, or together with NSSF or PCF) determines an alternative S-NSSAI, for example, called S-NSSAI#2, which replaces S-NSSAI#1. S-NSSAI#1 is a portion of the S-NSSAI subscribed to by the UE, while the alternative S-NSSAI#2 may be a portion of the S-NSSAI subscribed to by the UE, but not necessarily.

[0055] In some instances, during PDU session establishment, when the AMF determines to replace S-NSSAI#1 with an alternative S-NSSAI#2, the AMF sends a PDU session establishment or modification request to the SMF. This request message contains both the S-NSSAI#1 to be replaced and the alternative S-NSSAI#2. Assume S-NSSAI#1 is the HPLMN S-NSSAI, or in other words, S-NSSAI#1 is the subscribed S-NSSAI.

[0056] In some instances, if the alternative S-NSSAI#2 is part of the UE's subscribed S-NSSAI, then the UE's subscription data stored in the UDM (and UDR) will have entries containing S-NSSAI#2. The SMF can retrieve the SM subscription data from the UDM using the alternative S-NSSAI.

[0057] In some instances, if the alternative S-NSSAI#2 is not part of the UE's subscribed S-NSSAI, then the UE's subscription data stored in the UDM (and UDR) will not have an entry containing S-NSSAI#2, but rather an entry containing the replaced S-NSSAI#2. If the SMF uses the alternative S-NSSAI#2 when requesting SM subscription data from the UDM, the UDM will respond with an empty entry or an error code. In this case, the SMF may include the replaced S-NSSAI#1 in the request for SM subscription data from the UDM; however, the received SM subscription data will contain parameters applicable to S-NSSAI#1, but the PDU session is established on S-NSSAI#2.

[0058] In some instances, the SMF uses the subscribed network slice, i.e., the HPLMN S-NSSAI, when retrieving subscription information. In other words, when the S-NSSAI to be replaced is a network slice of the visited network, i.e., it is a VPLMN S-NSSAI, the SMF does not consider the replaced VPLMN S-NSSAI or the alternative VPLMN S-NSSAI when retrieving SM subscription data for the UE.

[0059] In some instances, the AMF and / or, together with the PCF, may determine the appropriate DNN to be used with S-NSSAI#2. The AMF may determine to replace the DNN requested by the UE and associated with S-NSSAI#1 (e.g., referred to as DNN#1) with a selected DNN available in S-NSSAI#2 (e.g., referred to as DNN#2). (See below and in...) Figure 3a Step 382 describes more details.

[0060] In some instances, when the UE does not provide a DNN in the NAS message containing an S-NSSAI#1 PDU session establishment request and a network slice with an alternative S-NSSAI#2 is used instead, the AMF determines the DNN of the requested PDU session by applying one of the following:

[0061] In some instances, if the alternative S-NSSAI#2 is part of the S-NSSAI subscribed to by the UE, and a default DNN exists in the UE's subscription data for S-NSSAI#2, then the AMF selects the default DNN for S-NSSAI#2.

[0062] In some instances, if the alternative S-NSSAI#2 is not part of the S-NSSAI subscribed to by the UE, or if the default DNN is not present in the UE's subscription data for S-NSSAI#2, then the AMF selects a locally configured DNN for S-NSSAI#2.

[0063] In some instances, when a UE provides a DNN (e.g., the requested DNN or DNN#1) in a NAS message containing a PDU session establishment request for S-NSSAI#1, and a network slice replacement using an alternative S-NSSAI#2 is in place, the AMF first determines whether the requested DNN#1 can be applied to S-NSSAI#2. This determination may be based on the UE's subscription data for S-NSSAI#2 (if the alternative S-NSSAI#2 is part of the UE's subscribed S-NSSAI), or on local configuration in the AMF.

[0064] In some instances, if the requested DNN of the PDU session is applicable to S-NSSAI#2, then the AMF uses the requested DNN as the selected DNN and uses the DNN in additional signaling to the SMF.

[0065] In some instances, if the requested DNN for a PDU session is not applicable to S-NSSAI#2, then the AMF applies an alternative S-NSSA DNN replacement procedure.

[0066] In some instances, the AMF determines that the requesting PCF (e.g., AM-PCF) requests assistance in determining the appropriate DNN for S-NSSAI#2. The AMF sends a request message to the PCF containing a) an alternative S-NSSAI#2, b) the requested DNN#1, and c) an indication of the appropriate DNN for S-NSSAI#2.

[0067] In some instances, the PCF appropriately determines the selected DNN (e.g., DNN#2) to be used with S-NSSAI#2, and the PCF responds to the AMF with the selected DNN.

[0068] In some instances, the AMF may send one of the following messages to the SMF:

[0069] - A single selected DNN (as determined above), S-NSSAI#1 (as the S-NSSAI to be replaced or the S-NSSAI mapped to S-NSSAI#2), and S-NSSAI#2 (as an alternative S-NSSAI).

[0070] - A first combination of DNN#1 and its corresponding S-NSSAI#1 (as the S-NSSAI to be replaced or the S-NSSAI mapped to S-NSSAI#2), and a second combination of DNN#2 and its corresponding S-NSSAI#2 (as an alternative S-NSSAI).

[0071] In some instances, the network slice replacement feature (which includes an "alternative" S-NSSAI or a "compatibility" S-NSSAI) can be a functionality supported by the network and the UE, enabling the first S-NSSAI of a PDU session to be exchanged with another (second) S-NSSAI. Alternative S-NSSAI#2 can be a portion of the UE's configured NSSAI. Alternative S-NSSAI#2 may not be a portion of the UE's configured NSSAI. In some instances, the alternative S-NSSAI is represented as S-NSSAI#2, while the S-NSSAI to be replaced is represented as S-NSSAI#1. In roaming scenarios, the concepts HPLMN S-NSSAI#1 and HPLMN Alternative S-NSSAI#2 are used to illustrate that both are network slices in the HPLMN.

[0072] Some of the examples described in this article involve PLMNs as public networks. Other examples described in this article involve non-public networks, such as Standalone Non-Public Networks (SNPNs).

[0073] Figure 3a The description is typically indicated by reference numeral 300 as a signaling diagram of the process between nodes in a communication network comprising two network slices.

[0074] Process 300 includes User Equipment (UE) 310, (Radio) Access Network ((R)AN) 320, Access and Mobility Management Function (AMF) 350, Session Management Function (SMF) 355, Unified Data Management (UDM) / Unified Data Repository (UDR) 360 and Policy Control Function (PCF) 370.

[0075] Process 300 may involve processing the requested DNN and determining the selected DNN applicable to S-NSSAI#2 during PDU session establishment on the alternative S-NSSAI#2. Process 300 primarily includes 1) information exchange between UE 310 and AMF 350 on one side, 2) between AMF 350 and SMF 355, and 3) between SMF 355 and UDM / UDR 360.

[0076] Process 300 begins at step 380a. UE 310 registers with the network for S-NSSAI#1. To some extent, the network can determine to replace S-NSSAI#1 with an alternative S-NSSAI#2.

[0077] At step 380b, during the registration procedure, or during the UE 310 configuration update procedure, or at any time when the AMF 350 establishes or updates Access and Mobility (AM) policy associations, the AMF 350 may include at least one of the following in the establishment or update request: Subscription Persistent Identifier (SUPI), Subscribed S-NSSAI, or a new indication to support Network Slice Replacement (NSR). The AMF 350 may determine whether to include the indication to support Network Slice Replacement (NSR) based on the 5GMM capability of Network Slice Replacement indicated by the UE 310 during the registration procedure in step 380a and the support for the same feature in the AMF 350.

[0078] PCF 370 may send an AM policy association establishment response message containing a new instruction that may notify (or request) PCF 370 to resolve the DNN of an alternative network slice (e.g., an alternative S-NSSAI). This new instruction configures AMF 350 to contact (or request) PCF 370 regarding a suitable (or appropriate) DNN for the alternative S-NSSAI when network slice replacement is in place. In other words, in order to replace the DNN requested by UE 310 for S-NSSAI#1 (when using network slice replacement) with another selected DNN that is more suitable for the alternative S-NSSAI, PCF 370 may indicate to AMF 350 the operator policy that will be used for DNN resolution of the alternative S-NSSAI when the PDU session is established. When network slice replacement is in use, PCF 370 may indicate a policy referred to as, for example, "DNN resolution for alternative network slice" (or "DNN selection for alternative S-NSSAI").

[0079] When PCF 370 is configured with a policy to configure AMF 350, AMF 350 can perform step 383 when network slice replacement is in place.

[0080] In step 381, AMF 350 determines that Network Slice Replacement (NSR) will be applied to the PDU sessions on S-NSSAI#1. Several alternatives exist regarding how and when to trigger NSR.

[0081] In step 381a, in the first alternative, UE 310 requests the establishment of a PDU session. UE 310 sends a NAS Packet Data Unit (PDU) message to AMF 350, the message containing at least one of the following: S-NSSAI, alternative S-NSSAI, requested DNN, PDU session ID, N1 SM container (PDU session establishment request), etc. The NAS PDU message is encapsulated by (R)AN entity 320 in an N2 message directed to AMF 350, wherein the N2 message may contain UE 310 location information and access type information. UE 310 may or may not include the requested DNN in the NAS PDU message. If the requested DNN is included (e.g., referred to as DNN#1), then according to the URSP rule configuration in UE 310, this means that the requested DNN is associated with S-NSSAI#1: UE 310 associates the requested PDU session with S-NSSAI#1 and the requested DNN#1.

[0082] UE 310 contains the S-NSSAI from the permitted NSSAI (or partially permitted NSSAI, if configured in UE 310) of the current access type. If mapping information for the S-NSSAI replaced by alternative S-NSSAI#1 has been provided to UE 310, then UE 310 should provide both the replaced S-NSSAI#1 and the alternative S-NSSAI#2. The alternative S-NSSAI may replace 1) VPLMN S-NSSAI or 2) HPLMN S-NSSAI, or both.

[0083] The “S-NSSAI” described above may refer to a single S-NSSAI in a non-roaming context, or to both the VPLMN S-NSSAI and the HPLMN S-NSSAI in a roaming context. If the UE 310 is already configured with a mapping of allowed NSSAIs (or a mapping of partially allowed NSSAIs), then the UE 310 should provide the corresponding HPLMN S-NSSAI for the VPLMN S-NSSAI (i.e., from an allowed or partially allowed NSSAI) and the mapping of the allowed NSSAI (or the mapping of the partially allowed NSSAI).

[0084] A PDU session establishment request contained in an N1 SM container may include at least one of the following: PDU session ID, requested PDU session type, requested SSC mode, 5GSM capability, Protocol Configuration Options (PCO), etc. SSC mode refers to Session and Service Continuity mode, which can be SSC mode 1, SSC mode 2, or SSC mode 3.

[0085] In step 381b, in the second alternative, AMF 350 may determine the NSR that triggers an existing PDU session established on S-NSSAI#1 and DNN#1.

[0086] In either step 381a or 381b, AMF 350 may first trigger a configuration update procedure for UE 310 to configure UE 310 with alternative S-NSSAI and a mapping from alternative S-NSSAI#2 to the replaced S-NSSAI#1.

[0087] In step 382, ​​AMF 350 determines either 1) the NAS PDU is a request to establish a new PDU session, or 2) the NSR applies to an existing PDU session established on S-NSSAI#1. In either case 1 or 2, AMF 350 should apply the NSR procedure to replace the PDU session's S-NSSAI#1 with an alternative S-NSSAI#2. In some instances, the NAS message may contain both an alternative S-NSSAI#2 and S-NSSAI#1 for the serving PLMN. In some instances, the NAS PDU contains S-NSSAI#1 for the serving PLMN or HPLMN, and AMF 350 determines that the alternative S-NSSAI#2 should apply to S-NSSAI#1. In some instances, the NAS PDU message may or may not contain the requested DNN (e.g., DNN#1). The AMF 350 can be internally configured to determine the appropriate DNN for the alternative S-NSSAI#2, or, according to step 380b, the AMF 350 can be configured with a strategy associated with the PCF 370.

[0088] In some instances, UE 310 does not provide the requested DNN in the NAS message containing the PDU session establishment request with S-NSSAI#1, and instead uses a network slice with alternative S-NSSAI#2 instead. AMF 350 can then determine the DNN for the requested PDU session by applying one of the following:

[0089] - If the alternative S-NSSAI#2 is part of the S-NSSAI subscribed to by UE 310, and a default DNN exists in the subscription data of UE 310 for S-NSSAI#2 (assuming AMF 350 has downloaded and stored the UE's subscription data), then AMF350 selects the default DNN for S-NSSAI#2.

[0090] - If the alternative S-NSSAI#2 is not part of the S-NSSAI subscribed to by UE 310, or if a default DNN does not exist in UE 310's subscription data for S-NSSAI#2, then AMF 350 selects a locally configured DNN for S-NSSAI#2. Alternatively, if AMF 350 is configured to always request the appropriate DNN for S-NSSAI#2 from PCF 370, for example, as described in step 380b, then AMF 350 sends a request for DNN resolution of S-NSSAI#2, as described in step 383.

[0091] When UE 310 provides the requested DNN (e.g., DNN#1) in a NAS message containing a PDU session establishment request for S-NSSAI#1, and a network slice replacement with alternative S-NSSAI#2 is in place, AMF 350 first determines whether the requested DNN#1 can be applied to S-NSSAI#2. This determination may be based on UE 310's subscription data for S-NSSAI#2 (e.g., if alternative S-NSSAI#2 is part of UE 310's subscribed S-NSSAI), or on local configuration in AMF 350.

[0092] If the requested DNN#1 of the PDU session is applicable to S-NSSAI#2 (i.e., DNN#1 is also part of the subscribed DNN of S-NSSAI#2), then AMF 350 uses the requested DNN#1 as the selected DNN and uses the selected DNN in additional signaling to SMF 355. In this case, the requested DNN#1 will be the same as the selected DNN (i.e., DNN#1 is the same as DNN#2).

[0093] If the requested DNN#1 of the PDU session is not applicable to S-NSSAI#2, then the AMF 350 may use one of the following methods to determine the applicable DNN for the representation of S-NSSAI#2 as DNN#2:

[0094] - The AMF 350 may store internal (or local) configuration information (e.g., mapping information) which is used in conjunction with the input information for the requested DNN#1 and the alternative S-NSSAI#2 to determine the applicable / appropriate DNN for S-NSSAI#2, such as the applicable DNN with the value of DNN#2. In some instances, the internal or local configuration may be provided to the AMF 350 by the OAM system. The local configuration data may include one or more DNNs applicable to S-NSSAI#2 and / or the mapping information, which may define how the DNN associated with S-NSSAI#1 corresponds to the DNN associated with S-NSSAI#2. The AMF may select DNN#2 from 1) the list of one or more DNNs or 2) the mapping information.

[0095] - If the AMF 350 cannot determine the appropriate DNN#2 to be used for the requested PDU session, or if the AMF 350 is configured to always request the appropriate DNN for S-NSSAI#2 from the PCF 370, then the AMF 350 performs step 383.

[0096] In some instances, the AMF 350 configuration for requesting the appropriate DNN for S-NSSAI#2 from the PCF 370 may be 1) an internal or local configuration within the AMF 350, or 2) the AMF 350 may be configured by the PCF 370, for example, during the registration procedure shown in step 380b.

[0097] In step 383, the AMF 350 may consider selecting a DNN that can be used with the alternative S-NSSAI#2. In other words, the AMF 350 may modify the DNN#1 requested by the UE 310 (in the case of a new PDU session establishment), or the AMF 350 may select another DNN#2 that is different from the currently stored DNN#1 (in the case of network slice replacement for an existing PDU session). During the PDU session establishment or modification procedure, the AMF 350 interacts with the PCF 370 to perform a DNN#1 replacement, or to perform an action with the PCF 370 to check whether the DNN#1 associated with S-NSSAI#1 can also be used with S-NSSAI#2. The AMF 350 may be internally configured to do so, or the AMF 350 may be configured by the PCF 370 as described in step 380b. In one instance, the AMF 350 includes the following parameters in its request message to the PCF 370: SUPI, an indication of the association between S-SNSSAI#1 and DNN#1 (e.g., as a combination of the two parameters, or as individual parameters), an indication of an alternative S-NSSAI#2, and / or an indication of a request for an appropriate DNN for S-NSSAI#2.

[0098] As a result of the request to PCF 370, PCF 370 provides the selected DNN for S-NSSAI#2 to AMF 350 in its response message. AMF 350 uses the selected DNN (e.g., DNN#2) with S-NSSAI#2 in its query to NRF for selection of SMF 355. The selected DNN may be 1) determined locally in AMF 350 based on local configuration in AMF 350, or 2) determined by PCF 370 based on network operator preferences. The selected DNN#2 for S-NSSAI#2 may also differ from the subscribed DNN from the UE subscription data.

[0099] The AMF 350 provides the selected SMF 355 with 1) S-NSSAI#1 associated with the DNN requested by the UE 310, and 2) S-NSSAI#2 and the selected DNN. The matching of the selected DNN with the S-NSSAI is assumed to be based on network configuration. Alternatively, DNN#1 and DNN#2 may have the same value, meaning S-NSSAI#1 and S-NSSAI#2 may use the same DNN.

[0100] For PDU sessions with home route roaming, whether to perform DNN replacement on the alternative HPLMN S-NSSAI is based on operator agreement.

[0101] In step 384, AMF 350 selects SMF 355 based on the alternative S-NSSAI#2 and the selected DNN#2. In some instances, multiple SMFs may be configured to serve the alternative S-NSSAI#2, for example, a first set of SMFs for the first DNN used in S-NSSAI#2 and a second set of SMFs for the second DNN used in S-NSSAI#2. In such cases, AMF 350 may need to select an appropriate DNN#2, which will be used to select the serving SMF 355 for the PDU session on the alternative S-NSSAI#2. If AMF 350 does not use an appropriate DNN#2, then AMF 350 may select an inappropriate (or incorrect) SMF that may not be able to serve the PDU session.

[0102] AMF 350 sends a request for PDU session establishment to the selected SMF 355 using a service request operation, such as Nsmf_PDUSession_CreateSMContext, which may include at least one of the following: SUPI, the selected DNN (e.g., DNN#2, which is not associated with any S-NSSAI), the replaced S-NSSAI#1 (and may have DNN#1), the alternative S-NSSAI#2 (and may have DNN#2), the N1 SM container, and other parameters. If a PDU session modification procedure is applied, the AMF may also use the Nsmf_PDUSession_UpdateSMContext service request operation.

[0103] SMF 355 can use the indicated selected DNN (e.g., DNN#2) together with alternative S-NSSAI#2 or the replaced S-NSSAI#1 in an additional PDU session establishment step.

[0104] In step 385a, SMF 355 may retrieve the SM subscription data applicable to this PDU session. SMF 355 sends a request message to UDM 360 to retrieve the SM subscription data for the PDU session. If SMF 355 has received an indication that Alternative S-NSSAI#2 is part of the subscribed S-NSSAI, then SMF uses Alternative S-NSSAI to retrieve the SM subscription data for the PDU session. If SMF 355 has not yet received an indication that Alternative S-NSSAI#2 is part of the subscribed S-NSSAI, then SMF 355 uses both Alternative S-NSSAI#1 (and possibly DNN#1, if available) and Alternative S-NSSAI#2 (and possibly DNN#2, if available) to retrieve the SM subscription data for the PDU session.

[0105] The SMF 355 can use the service operation Nudm_SDM_Get, which includes at least one of the following parameters: SUPI (e.g., data key), SM subscription data indication (data subset), selected DNN#2, S-NSSAI#1 (marked as the S-NSSAI to be replaced), and S-NSSAI#2 (marked as the alternative S-NSSAI). The latter parameters S-NSSAI#1 (and DNN#1), S-NSSAI#2 (and DNN#2) can be referred to as the data subkey. In other words, the format of the current data subkey can be enhanced to include multiple S-NSSAIs and corresponding one or more DNNs. Alternatively, the SMF 355 can also use the Nudm_SDM_Subscribe service operation.

[0106] In step 385b, based on the received S-NSSAI#1, alternative S-NSSAI#2, and DNN#2, UDM 360 determines the SM subscription data to be sent to SMF 355. The SM subscription data should preferably be associated with alternative S-NSSAI#2 and DNN#2, but if these are unavailable, the SM subscription data may be associated with S-NSSAI#1 and DNN#1.

[0107] If UDM f360 locally stores the SM subscription data associated with the alternative S-NSSAI#2 and DNN#2, then UDM 360 can reply to SMF 355 in step 385 without requesting UDR 360.

[0108] Figure 3b This section describes a signaling diagram, typically indicated by reference numeral 300, illustrating the process between nodes in a communication network comprising two network slices. Process 300 follows from the preceding text regarding... Figure 3a The process described is 300 afterward.

[0109] Process 300 includes User Equipment (UE) 310, (Radio) Access Network ((R)AN) 320, Access and Mobility Management Function (AMF) 350, Session Management Function (SMF) 355, Unified Data Management (UDM) / Unified Data Repository (UDR) 360, Policy Control Function (PCF) 370, and User Plane Function (UPF) 375.

[0110] In step 386a, SMF 355 creates an SM context for the PDU session. SMF 355 uses the SM subscription data parameters received from UDM 360 in step 385b. If SMF 355 receives a single set of SM subscription parameters, it applies these parameters to the PDU session. If SMF 355 receives two sets of SM subscription parameters, it processes both sets and determines the last set of parameters to be applied to the PDU session.

[0111] The SMF 355 applies the received parameters in the following steps.

[0112] In step 386b, if the SMF 355 is able to process the PDU session establishment request from step 382, ​​then the SMF 355 responds to the AMF 350 by providing the UE 310 with the SM context ID associated with the UE's SUPI. The SMF 355 uses the Nsmf_PDUSession_CreateSMContext service operation by sending a response message containing the SUPI and the SM context ID.

[0113] In step 387, if Dynamic Policy and Charging Control (PCC) will be used for the PDU session, then SMF 355 performs PCF 370 selection. SMF 355 establishes a Session Management (SM) policy association with the selected PCF 370 by sending a request message to the PCF 370.

[0114] SMF 355 sends a request to PCF 370 to establish an SM policy association. SMF 355 can use the service operation Npcf_SMPolicyControl_Create and send a request message containing at least the following parameters: UE 310's SUPI, the replaced S-NSSAI#1 (and optionally associated DNN#1, if available in SMF 355), the alternative S-NSSAI#2 (and optionally associated DNN#2), the selected DNN (e.g., DNN#2), and others. PCF 370 responds with the default PCC rule of the PDU session. The PCC rule is determined based on the input in the request message.

[0115] The PCF 370 derives the strategy for PDU sessions based on the alternative S-NSSAI#2 and the selected DNN#2. The PCF 370 may also consider strategies from the replaced S-NSSAI#1 and the associated DNN#1.

[0116] In step 388, if the request type indicates "Initial Request," then the SMF 355 initiates the N4 session establishment procedure with the selected UPF 375; otherwise, it initiates the N4 session modification procedure with the selected UPF 375. The SMF 355 sends an N4 session establishment / modification request to the UPF 375, and the SMF 355 provides packet detection, enforcement, and reporting rules to be installed on the UPF 375 for this PDU session. The SMF 355 may indicate an alternative S-NSSAI#2 and / or the selected DNN#2 to the UPF. The UPF 375 responds accordingly to the SMF 355.

[0117] In step 389a, SMF 355 transmits a message to AMF 350, which includes information to be received by RAN 350 (i.e., N2 SM information) and information to be received by UE 310 (i.e., N1 SM container). SMF 355 may use the service operation Namf_Communication_N1N2MessageTransfer, and includes at least one of the following: UE 310's SUPI, N2 SM information, N1 SM container, etc. The N1 SM container may be enhanced to include the selected DNN#2 associated with the alternative S-NSSAI#2. Upon receiving the N1 SM container, UE 310 stores the DNN#2 in the PDU session context.

[0118] In step 389b, AMF 350 sends an N2 PDU session request to the RAN. The N2 PDU session request contains 1) N2SM information and 2) a NAS PDU message to UE 310, which includes a PDU session establishment reply.

[0119] In some of the examples described herein, with network slice replacements in place, the AMF 350 is able to select and use a suitable DNN for use with the alternative S-NSSAI#2. For this purpose, the AMF 350 can determine the selected DNN locally, or can request assistance from the PCF 370 to select a suitable DNN for use with the S-NSSAI#2.

[0120] In some instances, the network may determine that the original S-NSSAI#1 is reusable and that a PDU session can be established on S-NSSAI#1, which is currently established on the alternative S-NSSAI#2. When this is determined, the AMF 350 triggers the UE 310 to reconfigure to reuse S-NSSAI#1, and the AMF 350 requests the SMF 355 to relocate the existing PDU session to S-NSSAI#1, indicating the DNN to be used (e.g., DNN#1). The SMF 355 may determine whether it can serve the PDU session on S-NSSAI#1 and apply the PDU session modification procedure, or the SMF 355 may determine to release the PDU conversation with the re-establishment indication. In this case, if the SMF 355 can remain the same, then the SMF 355 may send a new request message to the UDM for SM subscription data, where the request message includes S-NSSAI#1 and the corresponding DNN#1. In other words, SMF 355 will send a request for SM subscription data that does not include S-NSSAI#2. Based on this request message, UDM 360 can determine a new set of SM subscription data parameters associated with S-NSSAI#1 and DNN#1, and transmit the new set of SM subscription data parameters to SMF 355.

[0121] This document provides a first network entity comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the first network entity: receives a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a first network slice is to be replaced with a second network slice; selects an assigned data network name for the data session, wherein the assigned data network name is applicable to the second network slice; and transmits a request to the second network entity for the establishment of a data session including the assigned data network name.

[0122] Failure to project the assigned data network name, which is applicable to the second network slice, to the second network entity often results in the rejection of the data session establishment request.

[0123] The assigned data network name may be a first data network name included in a request message from the user equipment to the first network entity. The first data network name may not be applicable to the second network slice. The first network entity may determine to replace the first data network name of the data session with a second data network name. The assigned data network name may be applicable to the second network slice. The assigned data network name may be assigned by a network entity. The assigned data network name may be assigned by the first network entity. The assigned data network name may be assigned by the access and mobility management function. The assigned data network name may be assigned by the policy control function.

[0124] The request message from the user equipment to the first network entity may not include the first data network name. The first network entity may select the assigned data network name applicable to the second network slice.

[0125] The first network entity can be a first network function. The first network entity can be an access and mobility management function.

[0126] A data session can be associated with a first network slice. A data session can be requested on the first network slice.

[0127] The first data network name can be assigned to the first network slice. The first data network name can be applied to the first network slice. The first network name can be applied to the first network slice.

[0128] User equipment (UE) can be configured with UE routing policy rules. From the UE configuration perspective, a data session can be associated with a first network slice. The network can determine to replace the first network slice with a second network slice. The data session can be established on the second network slice. The data session can be logically associated with the first network slice.

[0129] The replacement of the first network slice with the second network slice may already be configured in the user equipment. The user equipment can send instructions for both the first and second network slices to the first network entity in a request message.

[0130] User equipment can send an instruction for a first network slice to a first network entity in a request message. The first network entity can then decide to replace the first network slice with a second network slice.

[0131] The first network entity can receive the first data network name from a list of locally configured data network names.

[0132] A data session can be a grouped data unit session.

[0133] The first network entity can be a part of a communication network. The second network entity can be a part of a communication network. The communication network can be a wireless communication network. The communication network can be a public terrestrial mobile network. The communication network can be an independent, non-public network.

[0134] The second network entity can be a second network function. The second network entity can be a session management function.

[0135] At least one processor coupled to at least one memory may be further configured to cause the first network entity to: receive an indication of a first data network name associated with a first network slice, and determine whether the first data network name is applicable to a second network slice.

[0136] Instructions for the first data network can be received from the user equipment in the request message.

[0137] The first network entity may receive non-access stratum messages from the user equipment. The first network entity may receive non-access stratum packet data unit (PaDN) messages from the user equipment. The non-access stratum messages may include a packet data unit session establishment request. The packet data unit session establishment request may include a first data network name.

[0138] The first network entity may receive the first data network name from the user equipment via an access network. The access network may provide the first network entity with an indication of the first data network name in an N2 message. The access network may be a radio access network. The access network may be a fixed-line network. The access network may be based on 3rd Generation Partnership Project (3GP) access technology. The access network may be based on Long Term Evolution (LTE) technology. The access network may be based on New Radio (NR) technology. The access network may be based on non-3GP access technology. The access network may be based on Radio Fidelity (RF) technology.

[0139] At least one processor coupled to at least one memory may be further configured such that the first network entity: when it is determined that the first data network name is not applicable to the second network slice, selects a second data network name for an assigned data network name for a data session, wherein the second data network name is different from the first data network name.

[0140] The second data network name can be applied to the second network slice.

[0141] At least one processor coupled to at least one memory may be further configured to enable a first network entity to receive subscription data associated with the UE, wherein the subscription data includes an indication of a second data network name.

[0142] The user equipment's subscription data can be used to create a list of auxiliary information for selecting the subscription network slice that identifies the user equipment's subscription network slice.

[0143] The user equipment's subscription data may include an identifier for a first network slice. The user equipment's subscription data may include a first data network name. The user equipment's subscription data may include an identifier for a second network slice.

[0144] The second data network name can be the default data network name of the second network slice in the user's subscribed data.

[0145] At least one processor coupled to at least one memory is further configured such that the first network entity determines the name of the second data network based at least in part on local data at the first network entity.

[0146] The first network entity may include locally configured data. The locally configured data may include one of the following: a list or mapping information of one or more data network names applicable to the second network slice. The mapping information may define how the data network names associated with the first network slice correspond to the second data network names. The first network entity may select the second data network name from the list of one or more data network names. The first network entity may select the second data network name from the mapping information.

[0147] At least one processor coupled to at least one memory may be further configured to cause the first network entity to transmit a second instruction to the third network entity, indicating a request for a second data network name.

[0148] A third network entity can be a third network function. A third network entity can be a policy control function. A third network entity can be a part of a communication network.

[0149] The second instruction includes one or more of the following: the identifier of the second network slice, the identifier of the first network slice, or the name of the first data network.

[0150] The identifier for the second network slice can select auxiliary information for the individual network slice used in the second network slice.

[0151] At least one processor coupled to at least one memory may be further configured to enable a first network entity to receive an indication of a second data network name from a third network entity.

[0152] At least one processor coupled to at least one memory may be further configured to cause the first network entity to: transmit a third indication to the third network entity, the third indication indicating at least one of the following: the first network entity's ability to replace the first data network name with the second data network name of the data session, the UE's ability to support network slice replacement, or the first network entity's ability to support network slice replacement.

[0153] A third indication may be transmitted during the establishment of a data session on a second network slice. The third indication may be transmitted during the establishment procedure for associating access and mobility management policies with a third network entity. The third indication may also be transmitted during the update procedure for associating access and mobility management policies with a third network entity.

[0154] At least one processor coupled to at least one memory may be further configured to cause the first network entity to receive a fourth instruction from the third network entity in response to a third instruction, the fourth instruction indicating to the first network entity an instruction to provide an instruction indicating a request for a second data network name for a data session.

[0155] The fourth instruction may provide the first network entity with a strategy for providing an instruction to request a second data network name for the data session.

[0156] At least one processor coupled to at least one memory may be further configured such that the first network entity: selects a first data network name for the assigned data network name of a data session when it is determined that a first data network name is applicable to a second network slice.

[0157] This document provides a method performed by a first network entity, the method comprising: receiving a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a first network slice is to be replaced by a second network slice; selecting an assigned data network name for the data session, wherein the assigned data network name is applicable to the second network slice; and transmitting a request to the second network entity for the establishment of a data session including the assigned data network name.

[0158] Failure to project the assigned data network name, which is applicable to the second network slice, to the second network entity often results in the rejection of the data session establishment request.

[0159] The method may further include receiving an indication of a first data network name associated with a first network slice, and determining whether the first data network name is applicable to a second network slice.

[0160] Instructions for the first data network can be received from the user equipment in the request message.

[0161] The first network entity may receive non-access stratum messages from the user equipment. The first network entity may receive non-access stratum packet data unit (PaDN) messages from the user equipment. The non-access stratum messages may include a packet data unit session establishment request. The packet data unit session establishment request may include a first data network name.

[0162] The first network entity may receive the first data network name from the user equipment via an access network. The access network may provide the first network entity with an indication of the first data network name in an N2 message. The access network may be a radio access network. The access network may be a fixed-line network. The access network may be based on 3rd Generation Partnership Project (3GP) access technology. The access network may be based on Long Term Evolution (LTE) technology. The access network may be based on New Radio (NR) technology. The access network may be based on non-3GP access technology. The access network may be based on Radio Fidelity (RF) technology.

[0163] The method may further include, when it is determined that the first data network name is not applicable to the second network slice, selecting a second data network name for the assigned data network name used for the data session, wherein the second data network name is different from the first data network name.

[0164] The second data network name can be applied to the second network slice.

[0165] The method may further include receiving subscription data associated with the UE, wherein the subscription data includes an indication of a second data network name.

[0166] The user equipment's subscription data can be used to create a list of auxiliary information for selecting the subscription network slice that identifies the user equipment's subscription network slice.

[0167] The user equipment's subscription data may include an identifier for a first network slice. The user equipment's subscription data may include a first data network name. The user equipment's subscription data may include an identifier for a second network slice.

[0168] The second data network name can be the default data network name of the second network slice in the user's subscribed data.

[0169] The method may further include determining the name of the second data network based at least in part on local data at the first network entity.

[0170] The first network entity may include locally configured data. The locally configured data may include one of the following: a list or mapping information of one or more data network names applicable to the second network slice. The mapping information may define how the data network names associated with the first network slice correspond to the second data network names. The first network entity may select the second data network name from the list of one or more data network names. The first network entity may select the second data network name from the mapping information.

[0171] The method may further include sending a second instruction to a third network entity, indicating a request for a second data network name.

[0172] A third network entity can be a third network function. A third network entity can be a policy control function. A third network entity can be a part of a communication network.

[0173] The second instruction may include one or more of the following: the identifier of the second network slice, the identifier of the first network slice, or the name of the first data network.

[0174] The identifier for the second network slice can select auxiliary information for the individual network slice used in the second network slice.

[0175] The method may further include receiving an indication of a second data network name from a third network entity.

[0176] The method may further include transmitting a third indication to a third network entity, the third indication indicating at least one of the following: the ability of the first network entity to replace the first data network name with the second data network name of the data session, the ability of the UE to support network slice replacement, or the ability of the first network entity to support network slice replacement.

[0177] A third indication may be transmitted during the establishment of a data session on a second network slice. The third indication may be transmitted during the establishment procedure for associating access and mobility management policies with a third network entity. The third indication may also be transmitted during the update procedure for associating access and mobility management policies with a third network entity.

[0178] The method may further include receiving a fourth instruction from a third network entity in response to a third instruction, the fourth instruction indicating to the first network entity an instruction to provide an instruction indicating a request for a second data network name for a data session.

[0179] The fourth instruction may provide the first network entity with a strategy for providing an instruction to request a second data network name for the data session.

[0180] The method may further include selecting a first data network name for the referred data network name used for the data session when it is determined that the first data network name is not applicable to the second network slice.

[0181] This document provides a third network entity comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the third network entity to: receive a second instruction from a first network entity, wherein the second instruction indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice; and transmit an instruction to the first network entity for the second data network name, wherein the second data network name is applicable to the second network slice.

[0182] Providing the first network entity with a second data network name that is applicable to the second network slice enables the first network entity to use the second data network name as the assigned data network name of the second network slice, thereby preventing the first network entity from rejecting the data session establishment request for the second network entity.

[0183] A third network entity can be a third network function. A third network entity can be a policy control function. A third network entity can be a part of a communication network.

[0184] The third network entity can create user equipment routing policies. The third network entity can send user equipment routing policies to user equipment within the container via the first network entity. The container is transparent to the first network entity.

[0185] The second instruction may include one or more of the following: the identifier of the second network slice, the identifier of the first network slice, or the name of the first data network.

[0186] At least one processor coupled to at least one memory may be further configured to enable a third network entity to receive a third indication from a first network entity, the third indication indicating at least one of the following: the first network entity's ability to replace the first data network name with a second data network name of the data session, the UE's ability to support network slice replacement, or the first network entity's ability to support network slice replacement.

[0187] At least one processor coupled to at least one memory may be further configured to cause a third network entity to: in response to a third instruction, transmit a fourth instruction to a first network entity, the fourth instruction indicating to the first network entity an instruction to provide an instruction indicating a request for a second data network name for a data session.

[0188] At least one processor coupled to at least one memory may be further configured to enable a third network entity to store locally configured data at the third network function, the data including one or more of the following: a list or mapping information of one or more data network names applicable to a second network slice, wherein the mapping information defines how the data network names associated with the first network slice correspond to the second data network names.

[0189] This document provides a method performed by a third network entity, the method comprising: receiving a second indication from a first network entity, wherein the second indication indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice; and transmitting an indication of the second data network name to the first network entity, wherein the second data network name is applicable to the second network slice.

[0190] Providing the first network entity with a second data network name that is applicable to the second network slice enables the first network entity to use the second data network name as the assigned data network name of the second network slice, thereby preventing the first network entity from rejecting the data session establishment request for the second network entity.

[0191] A third network entity can be a third network function. A third network entity can be a policy control function. A third network entity can be a part of a communication network.

[0192] The third network entity can create user equipment routing policies. The third network entity can send user equipment routing policies to user equipment within the container via the first network entity. The container is transparent to the first network entity.

[0193] The second instruction may include one or more of the following: the identifier of the second network slice, the identifier of the first network slice, or the name of the first data network.

[0194] The method may further include receiving a third indication from a first network entity, the third indication indicating at least one of the following: the first network entity's ability to replace the first data network name with a second data network name of the data session, the UE's ability to support network slice replacement, or the first network entity's ability to support network slice replacement.

[0195] In some instances, in the case of network slice replacement, the AMF 350 can determine whether the DNN (e.g., DNN#1) requested by the UE 310 for PDU session establishment (or stored in the AMF 350 in the SM context for an existing PDU session) should be changed, so that a potentially new and suitable DNN (e.g., DNN#2) can be used with the alternative S-NSSAI#2.

[0196] In some instances, the AMF 350 can determine the assistance of the PCF 370 request (e.g., AM-PCF) to determine the appropriate DNN for S-NSSAI#2.

[0197] In some instances, the AMF 350 may have received a policy from the PCF 370 (e.g., AM-PCF) that always requests the PCF 370 when selecting an alternative S-NSSAI DNN.

[0198] In some instances, AMF 305 sends a request message to PCF 370 containing a) an alternative S-NSSAI#2, b) the requested DNN#1 and c) an indication of the appropriate DNN for S-NSSAI#2.

[0199] In some instances, the AMF 350 sends a request message to the SMF 355 for PDU session establishment, which includes at least one of the following indications:

[0200] - The selected DNNs are excluded, except for S-NSSAI#2 and S-NSSAI#1.

[0201] - A first combination of DNN#1 and its corresponding S-NSSAI#1 (as the S-NSSAI to be replaced or the S-NSSAI mapped to S-NSSAI#2), and a second combination of DNN#2 and its corresponding S-NSSAI#2 (as an alternative S-NSSAI).

[0202] In some instances, during AM policy association establishment or modification, PCF 370 may receive indications from AMF 350 that UE 310 and / or AMF 350 support network slice replacement features. Based on these indications, PCF 370 may create a policy that should resolve the appropriate DNN for the alternative S-NSSAI via PCF 370 and send it to AMF 350.

[0203] In some instances, PCF 370 may receive (e.g., from AMF 350) at least one of the following indications: a) alternative S-NSSAI#2, b) requested DNN#1, c) the replaced S-NSSAI#1 and d) an indication to request the appropriate DNN for S-NSSAI#2.

[0204] In some instances, the PCF 370 can determine the selected DNN (e.g., DNN#2) to be used with S-NSSAI#2 and transmit it to the AMF 350.

[0205] This document provides a method for enabling a first network function (NF, e.g., AMF) to determine a selected data network name (e.g., a selected service network name (SNN)). The method includes: determining a network slice replacement that must be applied to an existing or new data session, wherein the data session is associated with a network slice as an alternative S-NSSAI and another network slice as the replaced S-NSSAI, and a requested data network name (e.g., a requested DNN); determining at least one of the following: the requested DNN cannot be used with the alternative S-NSSAI#2, or the requested DNN is lost, and a potentially new selected DNN (e.g., DNN#2) can be used with the alternative S-NSSAI#2; and transmitting a second request message for data session establishment to a second NF (e.g., SMF), wherein the second request message includes at least one of the following: the selected DNN, DNN#1, and a corresponding S-NSSAI#1. The first combination is (as the S-NSSAI to be replaced or the S-NSSAI mapped to S-NSSAII#2), and the second combination is DNN#2 and the corresponding S-NSSAI#2 (as an alternative S-NSSAI).

[0206] The method may further include receiving a strategy for requesting the PCF when an alternative S-NSSAI DNN must be selected (e.g., from the PCF).

[0207] The determined steps may further include sending a third request message to a third NF (e.g., PCF), wherein the request message contains at least: an alternative S-NSSAI#2, a requested DNN#1, and an indication of the appropriate DNN for requesting S-NSSAI#2.

[0208] The first NF may (e.g., from the PCF) receive a response to a third request message, which contains the selected DNN (e.g., DNN#2).

[0209] Figure 4 An example of a UE 400 according to aspects of this disclosure is described. UE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, memory 404, controller 406, and transceiver 408, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0210] Processor 402, memory 404, controller 406, or transceiver 408, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or other programmable logic devices, or any combination thereof, configured to or otherwise support components for performing the functions described in this disclosure.

[0211] Processor 402 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 402 may be configured to operate memory 404. In some other embodiments, memory 404 may be integrated into processor 402. Processor 402 may be configured to execute computer-readable instructions stored in memory 404 to cause UE 400 to perform various functions of this disclosure.

[0212] Memory 404 may include volatile or non-volatile memory. Memory 404 may store computer-readable, computer-executable code containing instructions that, when executed by processor 402, cause UE 400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 404 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, which includes any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available medium accessible by a general-purpose or special-purpose computer.

[0213] In some implementations, processor 402 and memory 404 coupled to processor 402 may be configured to cause UE 400 to perform one or more of the functions described herein (e.g., instructions stored in memory 404 are executed by processor 402). For example, processor 402 may support wireless communication at UE 400 according to the examples disclosed herein.

[0214] Controller 406 manages the input and output signals of UE 400. Controller 406 can also manage peripheral devices not integrated into UE 400. In some embodiments, controller 406 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 406 may be implemented as part of processor 402.

[0215] In some embodiments, UE 400 may include at least one transceiver 408. In other embodiments, UE 400 may have more than one transceiver 408. Transceiver 408 may represent a wireless transceiver. Transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

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

[0217] Transmitter chain 412 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 412 may include at least one modulator for modulating data onto 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 412 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. Transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0218] Figure 5 An example of a processor 500 according to aspects of this disclosure is described. Processor 500 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 500 may include a controller 502 configured to perform various operations according to the examples described herein. Processor 500 may optionally include at least one memory 504, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 500 may optionally include one or more arithmetic logic units (ALUs) 506. One or more of these components may be electronically communicateable or otherwise coupled via one or more interfaces (e.g., buses) (e.g., operatively, communicatively, functionally, electronically, electrically).

[0219] Processor 500 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 500) or contained within the processor chipset) 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.).

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

[0221] Controller 502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 504 and determine subsequent instructions to be executed to enable processor 500 to support various operations according to the examples described herein. Controller 502 may be configured to track the memory addresses of instructions associated with memory 504. Controller 502 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 502 may be configured to interpret instructions and determine control signals to be output to other components of processor 500 to enable processor 500 to support various operations according to the examples described herein. Alternatively or additionally, controller 502 may be configured to manage data flow within processor 500. Controller 502 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 500.

[0222] Memory 504 may include one or more caches (e.g., memory local to processor 500 or included in processor 500) or other memories, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some embodiments, memory 504 may reside within or on the processor chipset (e.g., locally to processor 500). In some other embodiments, memory 504 may reside external to the processor chipset (e.g., remote from processor 500).

[0223] Memory 504 may store computer-readable, computer-executable code containing instructions that, when executed by processor 500, cause processor 500 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. Controller 502 and / or processor 500 may be configured to execute the computer-readable instructions stored in memory 504 to cause processor 500 to perform various functions. For example, processor 500 and / or controller 502 may be coupled to memory 504, and processor 500, controller 502, and memory 504 may be configured to perform the various functions described herein. In some instances, processor 500 may include multiple processors and memory 504 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, and the multiple processors may be individually or collectively configured to perform the various functions described herein.

[0224] One or more ALUs 506 may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALUs 506 may reside within or on a processor chipset (e.g., processor 500). In some other embodiments, one or more ALUs 506 may reside outside the processor chipset (e.g., processor 500). One or more ALUs 506 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 506 may receive input operands and opcodes, which determine the operation to be performed. One or more ALUs 506 may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 506s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 506s to handle conditional operations, comparisons, and bitwise operations.

[0225] Processor 500 can support wireless communication according to the examples disclosed herein.

[0226] Figure 6An example of NE 600 according to aspects of this disclosure is described. NE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, memory 604, controller 606, and transceiver 608, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0227] Processor 602, memory 604, controller 606, or transceiver 608, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or other programmable logic devices, or any combination thereof, configured to or otherwise support components for performing the functions described in this disclosure.

[0228] Processor 602 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 602 may be configured to operate memory 604. In some other embodiments, memory 604 may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory 604 to cause NE 600 to perform various functions of this disclosure.

[0229] Memory 604 may include volatile or non-volatile memory. Memory 604 may store computer-readable, computer-executable code containing instructions that, when executed by processor 602, cause NE 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 memory. Computer-readable media includes both non-transitory computer storage media and communication media, which includes any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available medium accessible by a general-purpose or special-purpose computer. In some embodiments, processor 602 and memory 604 coupled to processor 602 may be configured to cause NE 600 to perform one or more of the functions described herein (e.g., processor 602 executing instructions stored in memory 604). For example, processor 602 may support wireless communication at NE 600 according to the examples disclosed herein. The NE 600 can be configured to support components for receiving a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a second network slice is used to replace a first network slice; selecting an assigned data network name for the data session, wherein the assigned data network name is applicable to the second network slice; and transmitting a request to a second network entity for the establishment of a data session including the assigned data network name.

[0230] Alternatively, the NE 600 may be configured to support components for receiving a second indication from a first network entity, wherein the second indication indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice; and to transmit an indication of the second data network name to the first network entity, wherein the second data network name may be applicable to the second network slice.

[0231] Controller 606 manages the input and output signals of NE 600. Controller 606 can also manage peripheral devices not integrated into NE 600. In some embodiments, controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 606 may be implemented as part of processor 602.

[0232] In some embodiments, NE 600 may include at least one transceiver 608. In other embodiments, NE 600 may have more than one transceiver 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.

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

[0234] Transmitter chain 612 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 612 may include at least one modulator for modulating data onto 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). 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. Transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0235] Figure 7 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by an NE as described herein. In some embodiments, the NE can execute a set of instructions to control the functional elements of the NE to perform the described functions.

[0236] At 702, the method may include receiving a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a second network slice be replaced with a second network slice. The operation of 702 may be performed according to the examples described herein. In some embodiments, it may be performed by reference to... Figure 6 The described NE is used to perform the operation of 702.

[0237] At 704, the method may include selecting an assigned data network name for a data session, wherein the assigned data network name may be applicable to a second network slice. The operation at 704 may be performed according to the examples described herein. In some embodiments, it may be performed by, as referenced... Figure 6 The described NE is used to perform the 704 operation.

[0238] At 706, the method may include sending a request to a second network entity to establish a data session including the assigned data network name. The operation of 706 may be performed according to the examples described herein. In some embodiments, it may be performed by, as referenced... Figure 6 The described NE is used to perform the operation of 706.

[0239] It should be noted that the method described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0240] Figure 8 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by an NE as described herein. In some embodiments, the NE can execute a set of instructions to control the functional elements of the NE to perform the described functions.

[0241] At 802, the method may include receiving a second indication from a first network entity, wherein the second indication indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice. The operation of 802 may be performed according to the examples described herein. In some embodiments, it may be performed by reference to... Figure 6 The described NE is used to perform the operations of 802.

[0242] At 804, the method may include an instruction to transmit a second data network name to a first network entity, wherein the second data network name may be applicable to a second network slice. The operation of 804 may be performed according to the examples described herein. In some embodiments, it may be performed by reference to... Figure 6 The described NE is used to perform the operations of 804.

[0243] It should be noted that the method described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0244] The description herein is provided to enable those skilled in the art to make or use this disclosure. Those skilled in the art will understand that various modifications to this disclosure are possible, and that other variations can be applied to the general principles defined herein without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but is consistent with the widest scope of the principles and novel features disclosed herein.

[0245] The following abbreviations are relevant to the areas covered in this document: 5GS / 5GC - Fifth Generation System / Fifth Generation Core Network; AMF - Access and Mobility Management Functions; AS - Access Layer; BS - Base Station; DSCP - Differential Service Code Point; eNB - Evolved Node-B; EPC / EPS - Evolved Packet Core / Evolved Packet System; FQDN - Fully Qualified Domain Name; gNB - 5G Node-B; ID - Identity; IE - Information Element; LTE - Long Term Evolution; NAS - Non-Access Stratum; MM - Mobility Management; MO - Mobile Initiation; MT - Mobile Termination; NAS - Non-Access Stratum; NEF - Network Exposure Function; NR - New Radio; NRF - Network Repository Function; NSSF - Network Slice Selection Function; PCF - Policy Control Function; P DU - Protocol Data Unit; PLMN - Public Terrestrial Mobile Network; RA - Registration Area; RAN - Radio Access Network; RAT - Radio Access Technology / Type; SM - Session Management; SMF - Session Management Function; SMS - Short Message Service; SUCI - Subscription Hidden Identifier; SUPI - Subscription Permanent Identifier; TA - Tracking Area; UDM - Unified Data Management; UDR - Unified Data Repository; UCU - UE Configuration Update; UE - User Equipment; UICC - Universal Integrated Circuit Card; UMTS - Universal Mobile Telecommunications System; URL - Uniform Resource Locator; URSP - UE Routing Policy; USIM - Universal Subscriber Identification Module; (E) - UTRAN - (Evolved) Universal Terrestrial Radio Access Network.

Claims

1. A first network entity, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the first network entity to: Receive a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a first network slice be replaced with a second network slice; Select an assigned data network name for the data session, wherein the assigned data network name may be applicable to the second network slice; and Send a request to the second network entity to establish a data session including the assigned data network name.

2. The first network entity of claim 1, wherein the at least one processor coupled to the at least one memory is further configured to cause the first network entity to: receive an indication of a first data network name associated with the first network slice, and determine whether the first data network name is applicable to the second network slice.

3. The first network entity of claim 2, wherein the at least one processor coupled to the at least one memory is further configured such that the first network entity: when it is determined that the first data network name is not applicable to the second network slice, selects a second data network name for the assigned data network name for the data session, wherein the second data network name is different from the first data network name.

4. The first network entity of claim 3, wherein the at least one processor coupled to the at least one memory is further configured to cause the first network entity to: receive subscription data associated with the UE, wherein the subscription data includes an indication of the second data network name.

5. The first network entity according to claim 3 or claim 4, wherein the at least one processor coupled to the at least one memory is further configured such that the first network entity: determines the second data network name based at least in part on local data at the first network entity.

6. The first network entity according to any one of claims 3 to 5, wherein the at least one processor coupled to the at least one memory is further configured to cause the first network entity to: transmit a second indication to the third network entity indicating a request for the second data network name.

7. The first network entity of claim 6, wherein the second indication includes one or more of the following: an identifier of the second network slice, an identifier of the first network slice, or the name of the first data network.

8. The first network entity according to claim 6 or 7, wherein the at least one processor coupled to the at least one memory is further configured to cause the first network entity to: receive an indication of the second data network name from the third network entity.

9. The first network entity according to any one of claims 6 to 8, wherein the at least one processor coupled to the at least one memory is further configured to cause the first network entity to: transmit a third indication to the third network entity, the third indication indicating at least one of the following: the capability of the first network entity to replace the first data network name with the second data network name of the data session, the capability of the UE to support network slice replacement, or the capability of the first network entity to support network slice replacement.

10. The first network entity of claim 9, wherein the at least one processor coupled to the at least one memory is further configured to cause the first network entity to: receive a fourth indication from the third network entity in response to the third indication, the fourth indication indicating to the first network entity an instruction to provide an indication of a request for the second data network name of the data session.

11. The first network entity according to any one of claims 2 to 10, wherein the at least one processor coupled to the at least one memory is further configured such that the first network entity: when determining that the first data network name is applicable to the second network slice, selects the first data network name for the assigned data network name of the data session.

12. A method performed by a first network entity, the method comprising: Receive a first indication for a data session for a user equipment (UE), wherein the first indication indicates that a first network slice be replaced with a second network slice; Select an assigned data network name for the data session, wherein the assigned data network name may be applicable to the second network slice; and Send a request to the second network entity to establish a data session including the assigned data network name.

13. A third network entity, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the third network entity to: Receive a second instruction from a first network entity, wherein the second instruction indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice; and The first network entity is given an indication of the second data network name, wherein the second data network name may be applicable to the second network slice.

14. The third network entity of claim 13, wherein the second indication includes one or more of the following: an identifier of the second network slice, an identifier of the first network slice, or the name of the first data network.

15. The third network entity of claim 13 or 14, wherein the at least one processor coupled to the at least one memory is further configured to cause the third network entity to: receive a third indication from the first network entity, the third indication indicating at least one of the following: the first network entity's ability to replace the first data network name with the second data network name of the data session, the UE's ability to support network slice replacement, or the first network entity's ability to support network slice replacement.

16. The third network entity of claim 15, wherein the at least one processor coupled to the at least one memory is further configured to cause the third network entity to: transmit a fourth indication to the first network entity in response to the third indication, the fourth indication indicating to the first network entity an instruction to provide an indication of a request for the second data network name of the data session.

17. The third network entity according to any one of claims 13 to 16, wherein the at least one processor coupled to the at least one memory is further configured such that the third network entity: stores locally configured data at the third network function, the data including one or more of the following: a list or mapping information of one or more data network names applicable to the second network slice, wherein the mapping information defines how the data network names associated with the first network slice correspond to the second data network names.

18. A method performed by a third network entity, the method comprising: Receive a second instruction from a first network entity, wherein the second instruction indicates a request for a second data network name for a data session of a user equipment UE on a second network slice, wherein the first network slice will be replaced by the second network slice; The first network entity is given an indication of the second data network name, wherein the second data network name may be applicable to the second network slice.

19. The method of claim 18, wherein the second indication includes one or more of the following: an identifier of the second network slice, an identifier of the first network slice, or the name of the first data network.

20. The method of claim 18 or 19, further comprising receiving a third indication from the first network entity, the third indication indicating at least one of the following: the first network entity's ability to replace the first data network name with the second data network name of the data session, the UE's ability to support network slice replacement, or the first network entity's ability to support network slice replacement.

Images