Network-centric network slicing selection

Abstract

Various aspects of the present disclosure relate to a UE for wireless communication, comprising: at least one memory configured for storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit a connectivity request message to the network to request a data session, the connectivity request message comprising the service descriptor; and receive a connectivity response message from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network slice identifier identifies a first network slice of the network.

Description

NETWORK-CENTRIC NETWORK SLICING SELECTIONTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to establishment of a data session on a communication network including a plurality of network slices.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0003] A feature of 5G network systems (abbreviated as 5GS) is network slicing. Network slicing enables the network operators to divide (“slice”) the network in finer granularity of complete networks in order to provide customized network connectivity, features, or both to customers and / or external service providers.

[0004] A network slice is a logical network that comprises of a set of network functions and corresponding resources (e.g., computing, storage, and networking resources, among others) necessary to provide certain network capabilities and network characteristics. A network slice can include one or more core network (e.g. 5G core network, 5GC) control plane and user plane network functions (NFs), and one or more Access Networks (e.g., a 5G radio access network, a fixed access network, or a combination thereof).

[0005] A UE in a communication network can be configured with network slice relevant information, referred as Network Slice Selection Assistance information (NSSAI). The NSSAI may consist of one or more single Network Slice Selection Assistance information (S-NSSAIs). Data sessions of the UE, such as Protocol Data Unit (PDU) sessions, may be established on one or more of the Network Slices of the communication network in accordance with the NSSAI.SUMMARY

[0006] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list 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). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0007] Some implementations of the method and apparatuses described herein may include a UE for wireless communication, comprising: at least one memory configured for storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit a connectivity request message to the network to request a data session, the connectivity request message comprising the service descriptor; and receive a connectivity response message from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network slice identifier identifies a first network slice of the network.

[0008] The at least one processor may be further configured to cause the UE to: detect a request for network connectivity from an application associated with the first configuration information, and in response, transmit the connectivity request message based on absence of a network slice identifier in the configuration information.

[0009] The connectivity response message may comprise validity information indicating the validity of the first network slice identifier.

[0010] The validity information may define at least one of: (i) a geographical area for which the first network slice is valid; or (ii) a time period during which the first network slice is valid.

[0011] The first configuration information may additionally comprise a traffic descriptor which is not associated with a network slice of the network. Alternatively, the first configuration information may comprise a traffic descriptor which is not associated with a network slice of the network, and the service descriptor corresponds to at least part of the traffic descriptor.

[0012] The service descriptor may comprise one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

[0013] The service descriptor may comprise an anonymized identifier associated with one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

[0014] The at least one processor may be further configured to cause the UE to: update the first configuration information to associate the first configuration information with the first network slice identifier.

[0015] The at least one processor may be further configured to cause the UE to: receive a session establishment response message as part of a network-initiated session establishment procedure, the session establishment response message comprising the first network slice identifier.

[0016] The at least one processor may be further configured to cause the UE to: transmit a session establishment request message to the network, in response to reception of the connectivity response message, the session establishment response message comprising the first network slice identifier.

[0017] The at least one memory may be configured for storing second configuration information relating to a second traffic descriptor, the second configuration information comprising a second network slice identifier which identifies a second network slice of the network, and the first configuration information comprises a first set of session parameters, and the second configuration information comprises a second set of session parameters.

[0018] The first configuration information may comprise validity information indicating the validity of the first set of session parameters.

[0019] The second configuration information may comprise validity information indicating the validity of the second set of session parameters.

[0020] Some implementations of the method and apparatuses described herein may further include a processor for wireless communication, comprising: at least one controller, coupled with at least one memory storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; the at least one controller configured to cause the processor to: output a connectivity request message for transmission to a network to request a data session, the connectivity request message comprising the service descriptor; and obtain a connectivity response message transmitted from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network slice identifier identifies a first network slice of the network.

[0021] Some implementations of the method and apparatuses described herein may further include a method performed by a user equipment (UE), the method comprising: storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; transmitting a connectivity request message to the network to request a data session, the connectivity request message comprising the service descriptor; and receiving a connectivity response message from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network identifier identifies a first network slice of the network.

[0022] Some implementations of the method and apparatuses described herein may further include a network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured tocause the network entity to: receive, from a user equipment (UE), a connectivity request message, the connectivity request message comprising a service descriptor; determine, using the service descriptor, a network slice identifier of a network slice of a network to establish a data session with the UE; and transmit a connectivity response message to the UE, the connectivity response message including the network slice identifier in association with the service descriptor.

[0023] The at least one processor may be configured to cause the network entity to determine the network slice identifier based on at least one of: subscription data of the UE; or availability of supported network slices in a current location of the UE.

[0024] The service descriptor may comprise one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

[0025] The service descriptor may comprise an anonymized identifier associated with one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

[0026] The at least one processor may be further configured to cause the network entity to: transmit a session establishment request message to a session management network function, the session establishment request message comprising the network slice identifier.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0028] Figure 2 shows an example 5GS architecture for a UE that is associated with two network slices in a communication system.

[0029] Figure 3 shows an example URSP rule 300 which may be configured in the UE in accordance with aspects of the present disclosure.

[0030] Figure 4 shows an example URSP rule 400 before on-demand network slice configuration with a network slice identifier in accordance with aspects of the present disclosure.

[0031] Figure 5 shows an example URSP rule 500 after on-demand network slice configuration with a network slice identifier in accordance with aspects of the present disclosure.

[0032] Figure 6a and 6b illustrates a method 600 of configuring a UE 104 with network slice information in a communication network, in accordance with aspects of the present disclosure.

[0033] Figure 7 illustrates an example of a user equipment (UE) 700 in accordance with aspects of the present disclosure.

[0034] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure.

[0035] Figure 9 illustrates an example of a network equipment (NE) 900 in accordance with aspects of the present disclosure.

[0036] Figure 10 illustrate a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0037] Figure 11 illustrate a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0038] Network slicing is a complex feature, and in 5G the network slicing requires extensive configuration in the UE.

[0039] This disclosure proposes a method to configure which network slice(s), e.g. beside a default network slices(s), to use for a specific application or service. In one example, the application may contain a traffic or data exchanged between an application client on the UE and an application server in the network and the service may contain a service data / traffic flow between the UE and network (wherein the service data flow may be a part of the application flow). This configuration is performed on demand by the core network. The UE may not need to be provided with Configured NS SAI. The UE may be configured with one or more allowed network slices (e.g. identified by an “Allowed NSSAI” parameter) which may include the default S-NSSAI(s) (e.g. S-NSSAI#!). For any application or service notmapping to the default S-NSSAI, the UE is configured with a service descriptor (SD). Whenever the UE wants to use an application / service of the SD, the UE sends a connectivity request message including an identifier for the SD to a control plane network function (NF) in the core network. This control plane network function may be an access and mobility NF (e.g. AMF). The AMF, alone or together with one or more further control plane NFs (e.g. a PCF and / or a NSSF), decides and / or selects on-demand which network slice to assign to the requested SD and the AMF provides the S-NSSAI as allowed network slice to the UE. In one example, the AMF may determine this alone (which network slice to assign to the requested SD) if the AMF maintains a local configuration (e.g. configured by the operation and management system of the network) how a requested service descriptor maps to a network slice. The selected network slice (e.g. S-NSSAI#2) for the SD may be stored with validity criteria in the UE and can be removed upon inactivity of the data session (e.g. a PDU session) on this network slice. The UE can request connectivity by using the same SD when the S- NSSAI#2 has been removed, and the UE wants to again use an application / service of the SD.

[0040] Aspects of the present disclosure can advantageously simplify the configuration of a UE that is needed for the UE to establish a data session with a sliced communication network.

[0041] Aspects of the present disclosure are described in the context of a wireless communications system.

[0042] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LIE -Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0043] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0044] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0045] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0046] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over 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 sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0047] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0048] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects 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 entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

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

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

[0051] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0052] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, forexample, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

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

[0054] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In someimplementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0055] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0056] The wireless communications system 100 may support network slicing. A network slice is virtualized and independent logical portion of a network that is deployed on the same physical network infrastructure as other network slices.

[0057] Figure 2 shows an example 5GS architecture for a UE 204 associated with two network slices in a communication system 200, wherein the network slices are deployed correspondingly over a first network slice instance 210 (e.g. “NSI-1”) and a second network slice instance 220 (e.g., “NSI-2”). The communication system 200 may correspond to the wireless communication system 100 of FIG. 1, and the UE 204 may correspond to the UE 104 of FIG. 1. Although the communication system 200 is shown with two network slices, embodiments are not limited thereto.

[0058] In the illustrative embodiment of Figure 2, a (radio) access network (R)AN 232 (that is, an access network that may include but is not limited to a Radio Access Network) is part of the both the first and second network slices instances 210 and 220 and is shared, however, embodiment are not limited thereto. The (R)AN 232 may correspond to the network entities 102 of Figure 1. The control plane (C-plane) part of the network slices has Common Control-plane Network Functions (CCNFs) 234 and one or more dedicated C-plane Network (CN) Functions for each network slice. For example, in the illustrative embodiment of FIG., the first network slice instance 210 includes a first Session Management Function SMF1 212, and the second network slice instance 220 includes a second Session Management Function SMF2 222.

[0059] In addition, each the network slice instance may include one or more dedicated User-plane Functions; accordingly, in the illustrative embodiment of Figure 2, the first network slice instance 210 includes a first User Plane Function (UPF1) 214, and the second network slice instance 220 includes second User Plane Function (UPF2) 224.

[0060] Components of the communication system 200 are shown coupled through 5G reference points N2, N3, N4, Ni l. In Fig. 2, the (R)AN 232 is coupled to the CCNFs 234 using an N2 reference point and to the first and second UPFs 214 and 224 using respective N3 reference points. The CCNFs 234 may be coupled to the first and second SMFs 212 and 222 using respective N11 reference points. The first SMF 212 is coupled to the first UPF 214 using an N4 reference point, and the second SMF 222 is coupled to the second UPF 224 using an N4 reference point.

[0061] Figure 2 does not include all NFs and all reference points of the communication system 200. More information about the functionality of NFs (e.g. AMF, NSSF, SMF, UPF, etc.), about reference points, and about the 5GS can be found in the 3rdGeneration Partnership Project (3GPP) Technical Specification (TS) 23.501, V17.4.0, 2022-06, “System Architecture for the 5G System” (hereinafter, TS 23.501) and the 3GPP TS 23.502, V17.4.0, 2022-06, “Procedures for the 5G System” (hereinafter, TS 23.501).

[0062] The UE and the core network (CN) communicate via a non-access stratum (NAS) protocol. The messages of the NAS protocol are transmitted via the control plane between the UE and CN. Typically, every generation of mobile technology introduces a new generation of NAS protocol. One end of the NAS protocol is terminated at the UE and the other end of the NAS protocol is terminated at a mobility management entity in the CN, wherein the latter can be termed an MME in case of Evolved Packet System (EPS) or Access and Mobility Management Function (AMF) in case of 5GS.

[0063] The network slice configuration is sent to the UE via the NAS protocol, more specifically via mobility management messages. In 5GS the UE is configured with various network slicing information, e.g.• Information sent from the AMF to the UE: a. to the Configured NS SAI; b. Allowed NS SAI and Partially Allowed NS SAI; c. Rej ected NS SAI and partially Rej ected NS SAI; d. Target NSSAI; e. Pending NSSAI;• UE sends to the network Requested NSSAI.

[0064] Each NSSAI (Network Slice Selection Assistance Information) contain a list of one or more Single Network Slice Selection Assistance Information (S-NSSAIs).

[0065] In addition, for the network slicing to work properly, User Equipment Routing Selection Policy (URSP) is configured in the UE. The URSP allows the UE to dynamically select the most suitable network slice for each application or service which the user of the UE wants to use. In particular, when a UE requests a network connection, it evaluates stored URSP rules in an attempt to find a match. If a match is found, the UE forwards the traffic via a network slice identified in the matching URSP rule. The UE uses the route selection descriptor in the matching URSP rule to determine PDU Session connectivity parameters (RSD parameters).

[0066] Figure 3 shows an example URSP rule 300 which may be configured in the UE. As shown in Figure 3, a URSP rule 300 may comprise a traffic descriptor (TD) 302 and one or more route selection descriptor (RSD). For example, the TD 302 identifies (e.g. to the UE) traffic which has to be routed via a specific session (e.g. PDU Session), wherein the traffic identification can be based on different criteria like destination address, source application client, destination network identity (e.g. data network name, DNN) and others. As a mere example, USRP 300 is shown as having a first RSD 304 associated with a first network slice identifier S-NSSAI#1, and a second RSD 306 associated with a second network slice identifier S-NSSAI#2.

[0067] The TD 302 may comprise one or more of:• One or more application descriptors: each comprising of an operating system ID (e.g. OSId) and an operating system application ID (e.g. OSAppId).• One or more IP descriptors: for example, destination IP 3 tuple(s) (IP address or IPv6 network prefix, port number, protocol ID of the protocol above IP).• One or more domain descriptors: FQDN(s) or a regular expression which are used as a domain name matching criteria.• One or more non-IP descriptors: descriptor(s) for destination information of non-IP traffic (e.g. ethernet traffic).• A Data Network Name (DNN): it is matched against the DNN information provided by the application.• Connection Capabilities: this is matched against the information provided by a UE application when it requests a network connection with certain capabilities or traffic categories. A connection capability may be: IMS, Internet, Operator specific connection capabilities, loT delay-tolerant, loT non-delay-tolerant, Downlink (or uplink) streaming service, real time interactive service, etc.

[0068] An RSD 304,306 may include one or more sets of RSD parameters. Each set of RSD parameters may include comprise one or more of:• Session and Service Continuity (SSC) Mode: Indicates that the traffic of the matching application or Personal loT Network (PIN) traffic shall be routed via a PDU Session supporting the included SSC Mode.• Network Slice Selection: Indicates that the traffic of the matching application / PIN shall be routed via a PDU Session supporting any of the included S-NSSAIs. It includes one or more S-NSSAI(s). It may include one or more default S-NSSAI(s) (e.g. S-NSSAI#1).• DNN Selection: Indicates that the traffic of the matching application / PIN shall be routed via a PDU Session supporting any of the included DNNs. It includes one or more DNN(s). If a DNN Selection component is provided in the Route Selection Descriptor then the UE shall use any of the DNNs of the DNN Selection component, instead of the DNN requested by the application for the PDU Sessionthat is used to route the traffic of the matching application. If there is no DNN Selection component in the Route Selection Descriptor, then the UE shall use the DNN requested by the application for the PDU Session that is used to route the traffic of the matching application.• PDU Session Type Selection: Indicates that the traffic of a matching application shall be routed via a PDU Session supporting the included PDU Session Type (e.g. IP type like IPv6 or IPv4 or Ethernet type).• Non-seamless offload indication: Indicates that traffic of the matching application is to be offloaded to non-3GPP access outside of a PDU Session when the rule is applied.

[0069] As shown by the first RSD 304, an RSD may include validity information 308 which defines criteria that must be met in order for the RSD parameters to be used by the UE. In particular, the validity information 308 may define a geographical area for which the network slice identifier (included in RSD) is valid; and / or (ii) a time period during which the network slice identifier (included in RSD) is valid. The geographical area may comprise a cell ID, tracking area ID or other network area identification (e.g. topological location information).

[0070] As shown in Figure 3, the URSP rule 300 may include a mapping of a TD 302 to an RSD 304 which includes the default S-NSSAI (e.g. S-NSSAI#1). The TD 302 of the URSP rule 300 may be a “match all” descriptor to indicate that any data traffic from an application or service which doesn’t map to another TD should be routed using this URSP rule 300. The TD 302 of the URSP rule 300 corresponds to an RSD 304 which includes the default S- NSSAI (e.g. S-NSSAI#1) and other RSD parameters e.g. DNN, SSC mode, etc.

[0071] Figure 4 shows an example URSP rule 400 which may be configured in the UE before on-demand network slice configuration. As shown in Figure 4, the URSP rule 400 may comprise a TD 402, examples of which have been provided above. The TD 402 is for an additional application or service which does not map onto a default S-NSSAI. The TD 402 of URSP rule 400 is not associated with a network slice.

[0072] The URSP rule 400 may comprise a RSD 404 including a set of one or more RSD parameters, examples of which have been provided above. The URSP rule 400 may comprise a service descriptor SD 406. In one example, the SD 406 may comprise an identifier for oneor any combination of: application traffic, service traffic or a destination identifier / address of the traffic, or destination network name. The SD 406 may contain one or more parameters which may include: application name (or application identity), application category, traffic identity, traffic category, or target domain of the traffic (e.g. FQDN or DNN). In one example, the SD 406 may be anonymized in order not to expose the user ID or the actual application ID to a network operator. For example, the SD 406 may be a predetermined value that is associated with one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain. The predetermined value, may be a scalar value (e.g. “99”) which may be assigned by the network operator to have a predefined meaning for the network operator.

[0073] Whilst Figure 4 shows the RSD 404 as including a set of one or more RSD parameters in the RSD 404 in addition to the service descriptor SD 406, this is merely an example, and the RSD 404 may not include any RSD parameters in the RSD 404 in addition to the service descriptor SD 406.

[0074] Furthermore, whilst Figure 4 shows the URSP rule 400 comprising both the ID 402 and the SD 406, this is merely an example. In other examples, the TD 402, or a part of the TD 402, may function as the SD 406.

[0075] In contrast to the USRP rule 300, the URSP rule 400 is not associated with a network slice. In particular, the URSP rule 400 is devoid of a network slice identifier (S- NSSAI). The absence of a network slice identifier may be explicitly identified in the RSD 404 by way of an identifier 410 as shown in Figure 4, however in other embodiments the RSD 404 may not include any such identifier 410.

[0076] The RSD 404 may include validity information 408 which defines criteria that must be met in order for the RSD parameters to be used by the UE, examples of which have been provided above.

[0077] Figure 5 shows an example URSP rule 500 (which corresponds to the URSP rule 400 and is thus not mapped onto a default S -NS SAI) after on-demand network slice configuration. As shown in Figure 5, the URSP rule 500 comprises a network slice identifier 502 (e.g. S-NSSAI#2) in association with the SD 406. The network slice identifier 502 identifies a non-default network slice in the network. The URSP rule 500, in particular the RSD 404 may further include validity information 504 which defines criteria that must bemet in order for the RSD parameters to be used by the UE 104. In particular, the validity information 504 may define a geographical area for which the network slice identifier (S- NSSAI#2) is valid; and / or (ii) a time period during which the network slice identifier (S- NSSAI#2) is valid. The geographical area may comprise a cell ID, tracking area ID or other network area identification (e.g. topological location information). Upon expiration of any of the validity information 504, the UE should remove the S-NSSAI#2 from the URSP rule 500.

[0078] Figure 6a and 6b illustrates a method 600 of configuring a UE 104 with network slice information in a communication network. The communication network may include an access network 232 which may correspond to the (R)AN 232 of Figure 2. The communication network may include a plurality of control plane network functions in a CN 106. In particular, the CN 106 may include (i) an access and mobility management function, shown as AM-NF 602; (ii) a policy control function, shown as PCF 604; (iii) a network slice selection function, shown as NSSF 606; and a user plane function 612 which may correspond to the UPF2 224 shown in Figure 2.

[0079] Furthermore, the CN 106 may include a first session management function, shown as SM-NF1 212 which may correspond to the first Session Management Function SMF1 shown in Figure 2; and a second session management function, shown as SM-NF2222 which may correspond to the second Session Management Function SMF2 shown in Figure 2.

[0080] Any network function shown in Figures 6a and 6b is considered as a general representation of a network function of a given type and is not limited to a particular generation of radio access technology. For example, the access and mobility management function “AM-NF” 602 represents any network function which manages the UE mobility management functionality and may perform tasks such as determining temporary UE ID, determining a registration area and allowed (or rejected) network slices for the UE. The AMF-NF can also be represented by “6G-AMF” or “AMF”. Similarly, the session management function “SMF-NF1” 212 and “SMF-NF2” 222 represent any network function which manages a session (e.g. a PDU session or PDN connection) for the UE 104 and may perform tasks such as determining an IP address, session IP address continuity, assigning of a user plane function “UPF” etc. The SMF-NFs can also be represented by “6G-SMF” or “SMF”. Similarly, the PCF 604 can be any network function which creates and manages UE- related policy, mobility management policy or session management policy.

[0081] The CN 106 may further include a data repository 610, denoted as UDM / UDR. In particular, the data repository 610 may be a Unified Data Repository (UDR). The UDR may be managed by a Unified Data Management (UDM) component.

[0082] At step S602, the CN106 stores UE subscription data. In particular, the data repository 610 may store the UE subscription data (e.g. including subscription data associated with the UE 104). The UE subscription data may include a list of subscribed network slices (e.g. each identified by a network slice identifier NS-ID or S-NSSAI) and one or more network slices are assumed (or may be marked) to be default network slices. A default network slice is assumed to be supported mostly uniformly in the network. It is expected that the traffic of the default applications or services, or most used applications of the UE 104, is routed on the default network slice.

[0083] At step S604, the UE 104 initiates a registration procedure with the network system, e.g. 5GS or 6GS. It is assumed that the UE may not store network slice configuration at this point, or in general the UE may not store a Configured NS SAI. As part of the registration procedure, the UE 104 may transmit a registration request message to the AM- NF 602 which does not include information about a network slice which the UE 104 wants to use. During the registration procedure, the network (e.g. the AM-NF 602) may perform a UE authentication & authorization procedure. After a successful authentication & authorization procedure, the AM-NF 602 may learn a permanent identifier of the UE 104 e.g. a Subscription Permanent Identifier (SUPI).

[0084] At step S606, the AM-NF 602 may transmit a request for subscription data associated with the UE 104 to the data repository 610. The AM-NF 602 may include a permanent identifier of the UE 104 (e.g. SUPI) in the request to identify the UE.

[0085] At step S608, data repository 610 transmits a response message to the AM-NF 602 containing the UE subscription data as described above with reference to step S602. The data repository 610 can send a list of subscribed network slice identifiers (e.g. a list of subscribed S-NSSAIs) in the response message, wherein one or more of the S-NSSAIs may be marked as default S-NSSAI(s).

[0086] At step S610, the UE 104 receives a registration accept message as a response to the registration request message transmitted at step S604. The registration accept messagemay be an N1 or NAS protocol message. The registration accept message may contain a list of one or more allowed network slices which are assumed to be default network slices for the UE 104. In one example, the allowed NSSAI contains a single network slice identifier, S- NSSAI#1.

[0087] At step S612, the AM-NF 602 may send a request message to the PCF 604 to request configuration information for the UE 104. In particular, the AM-NF 602 may trigger a policy association establishment with the PCF 604. In response to receiving this request message, the PCF 604 may create configuration information which identifies how the UE 104 can internally associate (or route) traffic on the default S-NSSAI(s). This configuration information may take the form of URSP rule 300 described above.

[0088] The PCF 604 creates additional configuration information which may be in the form of additional URSP rule(s). Each additional URSP rule contains a TD 402 for an additional application or service which does not map onto the default S-NSSAI. The TD 402 of this additional URSP rule is not associated with a network slice. This additional configuration information may take the form of URSP rule 400 described above.

[0089] The configuration information (e.g. URSP rule 300) and additional configuration information (e.g. URSP rule 400) created by the PCF 604 is sent to the UE 104, and may be sent to the UE 104 as a policy container included in a N1 message. The N1 message can be sent to the UE 104 over the control plane via the AM-NF 602 as shown in steps 614a and 614b or via the user plane.

[0090] At step S616, the UE 104 may establish a user plane connectivity for any applications or services which map to the default network service. In other words, the UE 104 may initiate the establishment of a user plane connect! on / session (e.g. PDU Session #1) e.g. by initiating a PDU Session establishment procedure. The UE 104 sends a request message (e.g. PDU Session establishment request) which may include at least one of: a DNN (e.g. using a specific DNN name), and a S-NSSAI.In case of a new PDU Session establishment, the AM-NF 602 may select an SM-NF, e.g. SM-NF1 212. The AM-NF 602 forwards the request message to the selected SM-NF1 212.

[0091] At step S617, the UE 104 may determine that an application or traffic which is part of TD 402 requests connectivity (i.e. the application or traffic requires a data connection to the network to transmit data traffic). In particular, the UE may determine that thecorresponding RSD (e.g. of the TD 402) doesn’t include network slice selection information, and determine to first send a connectivity request message to the network including the SD 406.

[0092] At step S618, the UE 104 transmits a connectivity request message to the CN 106 to request a data session, the connectivity request message comprising the SD 406. In particular, the UE 104 transmits the connectivity request message to the AM-NF 602. The connectivity request message may be a NAS connectivity request message (e.g. a PDU Session establishment request). In addition to the SD 406, the connectivity request message may comprise one or any combination of: a temporary UE ID of the UE 104, a PDU Session ID, and a DNN.

[0093] The AM-NF 602 then determines, using the SD 406, a network slice identifier of a non-default network slice of the CN 106 network to establish a data session with the UE. In one example, the AMF-NF 602 may determine alone the network slice identifier if the AMF-NF 602 maintains a local configuration (e.g. configured by the operation and management system of the network) how a requested SD 406 maps to a network slice.

[0094] To determine this network slice identifier, at step S620 the AM-NF 602 may send a request to the PCF to check for a network slice selection policy for the SD 406. The PCF 604 may select an appropriate network slice identifier (e.g. S-NSSAI#2) for the requested SD 406 and the PCF 604 may send a response message to the AM-NF 602 including the selected network slice identifier for the SD 406. In addition or alternatively, the PCF 604 may create a new (i.e. updated) URSP rule for the UE including the network slice selection information containing a network slice identifier S-NSSAI#2 associated with the SD 406, and transmit the new (i.e. updated) URSP rule to the AM-NF 602 for further transmission to the UE 104. For example, the PCF 604 may update the URSP rule 300 to generate the URSP rule 400. As noted above, the URSP rule 400 may include validity criteria for the S-NSSAI#2 or other parameters to be used by the UE to determine the validity of the S -NS SAI in case of PDU Session inactivity (i.e. when all PDU Sessions are released) as described in more detail below.

[0095] Alternatively, or additionally, to determine this network slice identifier, at step S622 the AM-NF 602 may send a request for available network slices to the NSSF 606. The NSSF 606 may check for available network slices in the UE’s current registration area orlocation area, consider the load conditions of the available network slices, and / or check for alternative network slices (S-NSSAIs) to the network slice determined at step S620, and provide a response indicating a suitable available network slice. If step S620 is performed and the output of this step is that the network slice identifier S-NSSAI#2 has to be used for the requested SD 406 but the S-NSSAI#2 is not available (e.g. at this time or at this UE location or overloaded), the NSSF 606may suggest to use an alternative network slice e.g. S- NSSAI#3. Then the AM-NF 602 would assign the S-NSSAI#3 to the UE at step S622.

[0096] The CN 106 (e.g. AM-NF) then sends a connectivity response message to the UE 104. The connectivity response message may be a UE configuration update (UCU) command. The connectivity response message may include the S-NSSAI#2 included in the allowed NSSAI (e.g. as determined by the AMF-NF 602 alone or sent by the PCF 604), and in addition the updated URSP rule 500 including network slice selection information of S- NSSAI#2. The sending of the connectivity response message may be achieved via alternative methods 650,660. Please note that the sending of the URSP rule 500 to the UE 104 including network slice selection information of S-NSSAI#2 may be performed as independent procedure after the UCU command is transmitted to the UE 104.

[0097] As shown in Figure 6b, the 600 may proceed to a first method 650 to send the connectivity response message. In the first method 650 the data session establishment (e.g. PDU Session establishment) and the UE access management (AM) or mobility management (MM) configuration are performed in parallel as an optimization mechanism.

[0098] In the first method 650, at step S624 the AM-NF 602 selects the SM-NF2222 and transmits a session establishment request message to the SM-NF2 222, the session establishment request message comprising the network slice identifier S-NSSAI#2. In particular, the AM-NF 602 may send a session establishment request for a PDU Session on S-NSSAI#2.

[0099] At step S626, the SM-NF 222 may retrieve Session Management (SM) subscription data by transmitting a request to the SM-NF 222. The request may comprise an ID of the UE 104 (e.g. SUPI), S-NSSAI, or DNN. The SM-NF 222 may include the SD 406 (e.g. the list of one or more service IDs / names) in a request transmitted to the data repository 610. The data repository 610 may use the SD 406 to create SM subscription data by considering the SD 406 information indicated by the SM-NF (and originally indicated by theUE). For example, the data repository 610 may check whether the UE 104 is authorized or subscribed to use the indicated service IDs / names and or corresponding information about the candidate NF / AF.

[0100] At step S628, the AM-NF 602transmits a connectivity response message to the UE 104, which may be a UCU command. The connectivity response message may include an Allowed NSSAI containing S -NS S Al# 1 and / or the non-default network slice identifier, S- NSSAI#2. Alternatively or additionally, the connectivity response message may include configuration information including at least the updated URSP rule 500 including an RSD 404 with network slice selection information containing the S-NSSAI#2 502. The S- NSSAI#2 502 may be associated with validity parameters like time validity or location validity (e.g. a list of one or more network topology information like cell ID or tracking area ID). This means that the UE can use the S-NSSAI only during the validity criteria and if at least one of the validity parameters expires or declares that the S-NSSAI is not valid, the UE 104 may consider the S-NSSAI#2 as not valid. If the UE consider S-NSSAI#2 not valid, the UE may use the SD 406 when requesting a new session to the network. Alternatively or additionally, the connectivity response message may include an indication that the CN 106 will establish the data connection, i.e. the UE doesn’t need to perform a session establishment procedure (e.g. a PDU Session establishment procedure).

[0101] At step S630, the SM-NF2 222 selects and configures a user plane function (e.g. UPF2) to serve the user plane data transmission of the UE 104in the uplink and the downlink. The SM-NF2 sends a session management response message (e.g. PDU Session establishment response message) to the UE 104 which may be carried via the AM-NF 602 or directly via the RAN 232. The PDU Session establishment response message may include a session identifier (e.g. PDU Session ID), the S-NSSAI#2, DNN and / or other parameters for configuring the data connection. After the UE 104 receives the session management response indicating successful establishment of the data connection, the UE may transmit uplink and downlink data packets as shown in step S638.

[0102] As shown in Figure 6b, the 600 may alternatively to proceed to a second method 660 to send the connectivity response message. In the second method 660, the UE AM / MM configuration is performed first, and afterwards the UE 104 initiates the data session establishment (e.g. PDU Session establishment).

[0103] At step S632, the AM-NF S628 transmits a connectivity response message to the UE 104, which may be a UCU command. The connectivity response message may include the S-NSSAI#2 as part of the allowed NSSAI and the configuration information including at least the updated URSP rule 500 including an RSD 404 with network slice selection containing the S-NSSAI#2. The connectivity response message may include an indication that the UE 104 has to establish the data connection by itself, i.e. the UE 104 needs to perform a session establishment procedure (e.g. a PDU Session establishment procedure).

[0104] At step S634, the UE 104 transmits a session management establishment request message (e.g. PDU Session establishment request) including a session identifier (e.g. PDU Session ID), the network slice identifier S-NSSAI#2, DNN and / or other parameters. The UE 104 may send the session management establishment request message encapsulated in a NAS mobility management message to the AM-NF 602 for transmission to the SM-NF2 222.

[0105] At step S636 (similar to step S630), the SM-NF2 222 selects and configures a user plane function (e.g. UPF2 612) to serve the user plane data transmission of the UE 104 in the uplink and the downlink. The SM-NF2 222 sends a session management response message (e.g. PDU Session establishment response message) including a PDU Session ID, the S-NSSAI#2, DNN and / or other parameters for configuring the data connection.

[0106] After the UE 104 receives the session management response indicating successful establishment of the data connection / session (e.g. PDU Session #2), the UE 104 may transmit uplink and downlink data packets as shown in step S638.

[0107] After method 650 or 660 have been performed, the process 600 proceeds to stepS638. At step S638, after successful configuration of the data connection (e.g. IP configuration), the UE 104 may transmit uplink and downlink data packets via the UPF2612.

[0108] At step S640, if the data connection / session (e.g. PDU Session #2) on the network slice identified by the non-default network slice identifier S-NSSAI#2 is released, at step S640 the UE 104 is configured to remove S-NSSAI#2 from stored Allowed NSSAI information (e.g. after a configuration time).

[0109] The validity information 504 associated with the network slice identifier S-NSSAI#2 may be flexible (e.g. adaptable) by the UE 104. In particular, the validity information 504 may be adapted in the UE 104 using an Al model. The Al model may define how the UE is to store and use the configuration information for the S-NSSAI#2 included inthe connectivity response message received at step S628 and S632. The Al model may be provided by the CN 106 to the UE 104 to enable the UE 104 adjust and / or determine the validity information 504 for the S-NSSAI#2 based on various internal input parameters. In other words, the UE 104 may store and maintain an Al model for the validity information 504 of network slice information (e.g. for the network slice identifier S-NSSAI#2).

[0110] After some time or other criteria of inactivity of any PDU Session on S-NSSAI#2, the S-NSSAI#2 can be removed from the URSP rule 500, i.e. the network slice selection information would be empty.

[0111] After the S-NSSAI#2 has been removed from the RSD 404 or the S-NSSAI#2 is considered as not valid and the UE 104 wants to use an application or service of the TD 402 or URSP rule 500, the UE 104 sends a connectivity request message to the CN 106 (e.g. AM-NF) including the SD 406, as described above with reference to step S618. The CN 106 then performs the steps S620, S622 and one of the methods 650,660 again.

[0112] Referring back to step S617, if the UE 104 determines that an application or traffic which is part of TD 402 requests connectivity, and determines that the corresponding RSD (e.g. of the TD 402) does include network slice selection information (e.g. S-NSSAI#2), the UE 104 may determine to perform step S634, i.e. to send the session management establishment request message e.g. including the S-NSSAI#2 and DNN.

[0113] The process 600 advantageously means that the UE is configured on demand with the appropriate network slice to be used when a connectivity should be established for traffic which matches to a URSP rule which does not contain network slice information. This “on demand” network slice configuration may be associated with certain validity criteria and can be removed (or invalidated) when the validity criteria is no longer valid.

[0114] Embodiment of the present disclosure (in particular the process 600) can be applied for public networks, i.e. a Public Land Mobile Network (PLMN), or for private network, i.e. Non-Public Network (NPN) or Standalone NPN (SNPN).

[0115] Furthermore, whilst the process 600 has been described with reference to the URSP rule 400 not being associated with a network slice (i.e. the URSP rule 400 is devoid of a network slice identifier), the process 600 can be also applied to another RSD parameter like DNN. It means that the RSD parameter (e.g. DNN) may be missing in the RSD 404 and the network may assign the DNN parameter on demand to the UE 104. That is, the UE maystore configuration information (e.g. URSP rule 400) that is devoid of an RSD parameter (e.g. DNN), and receive a connectivity response message including the RSD parameter in association with the SD 402.

[0116] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0117] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

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

[0119] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.

[0120] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein. The UE 700 may be configured to support a means for storing (e.g. in memory 704) first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; transmitting a connectivity request message to the network to request a data session, the connectivity request message comprising the service descriptor; and receiving a connectivity response message from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network identifier identifies a first network slice of the network.

[0121] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0122] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

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

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

[0125] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

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

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

[0128] The controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein. The controller 802 may be configured to track memory address of instructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 802 may be configured to manage flow of data within the processor 800. The controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.

[0129] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).

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

[0131] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800). In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800). One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

[0132] The processor 800 may support wireless communication in accordance with examples as disclosed herein. The memory 804 may store first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor The processor 800 may be configured to or operable to support a means for outputting a connectivity request message for transmission to a network to request a data session, the connectivity request message comprising the service descriptor; and obtaining a connectivity response message transmitted from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network slice identifier identifies a first network slice of the network.

[0133] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0134] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

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

[0136] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.

[0137] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in thememory 904). For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein. The NE 900 may be configured to support a means for receiving from a user equipment (UE), a connectivity request message, the connectivity request message comprising a service descriptor; determining, using the service descriptor, a network slice identifier of a network slice of a network to establish a data session with the UE; and transmit a connectivity response message to the UE, the connectivity response message including the network slice identifier in association with the service descriptor.

[0138] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripherals not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0139] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

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

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

[0142] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0143] At 1002, the method may include storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a UE as described with reference to Figure 7.

[0144] At 1004, the method may include transmitting a connectivity request message to the network to request a data session, the connectivity request message comprising the service descriptor. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a UE as described with reference to Figure 7.

[0145] At 1006, the method may include receiving a connectivity response message from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network identifier identifies a first network slice of the network. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed a UE as described with reference to Figure 7.

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

[0147] Figure 11 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as describedherein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0148] At 1102, the method may include receiving, from a user equipment (UE), a connectivity request message, the connectivity request message comprising a service descriptor. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 9.

[0149] At 1104, the method may include determining, using the service descriptor, a network slice identifier of a network slice of a network to establish a data session with the UE. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a NE as described with reference to Figure 9.

[0150] At 1106, the method may include transmitting a connectivity response message to the UE, the connectivity response message including the network slice identifier in association with the service descriptor. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed a NE as described with reference to Figure 9.

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

[0152] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A UE for wireless communication, comprising: at least one memory configured for storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit a connectivity request message to the network to request a data session, the connectivity request message comprising the service descriptor; and receive a connectivity response message from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network slice identifier identifies a first network slice of the network.

2. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: detect a request for network connectivity from an application associated with the first configuration information, and in response, transmit the connectivity request message based on absence of a network slice identifier in the configuration information.

3. The UE of claim 1 or 2, wherein the connectivity response message comprises validity information indicating the validity of the first network slice identifier.

4. The UE of claim 3, wherein the validity information defines at least one of: (i) a geographical area for which the first network slice is valid; or (ii) a time period during which the first network slice is valid.

5. The UE of any preceding claim, wherein the first configuration information additionally comprises a traffic descriptor which is not associated with a network slice of the network.

6. The UE of any of claims 1 to 4, wherein the first configuration information comprises a traffic descriptor which is not associated with a network slice of the network, and the service descriptor corresponds to at least part of the traffic descriptor.

7. The UE of any preceding claim, wherein the service descriptor comprises one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

8. The UE of any of claims 1 to 6, wherein the service descriptor comprises an anonymized identifier associated with one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

9. The UE of any preceding claim, wherein the at least one processor is further configured to cause the UE to: update the first configuration information to associate the first configuration information with the first network slice identifier.

10. The UE of any preceding claim, wherein the at least one processor is further configured to cause the UE to: receive a session establishment response message as part of a network-initiated session establishment procedure, the session establishment response message comprising the first network slice identifier.

11. The UE of any of claims 1 to 9, wherein the at least one processor is further configured to cause the UE to: transmit a session establishment request message to the network, in response to reception of the connectivity response message, the session establishment response message comprising the first network slice identifier.

12. The UE of any preceding claim, wherein the at least one memory is configured for storing second configuration information relating to a second traffic descriptor, the second configuration information comprising a second network slice identifier which identifies a second network slice of the network, and the first configuration information comprises a first set of session parameters, and the second configuration information comprises a second set of session parameters.

13. The UE of claim 12, wherein at least one of: the first configuration information comprises validity information indicating the validity of the first set of session parameters; or the second configuration information comprises validity information indicating the validity of the second set of session parameters.

14. A processor for wireless communication, comprising: at least one controller, coupled with at least one memory storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; the at least one controller configured to cause the processor to: output a connectivity request message for transmission to a network to request a data session, the connectivity request message comprising the service descriptor; and obtain a connectivity response message transmitted from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network slice identifier identifies a first network slice of the network.

15. A method performed by a user equipment (UE), the method comprising: storing first configuration information which is not associated with a network slice of a network, the first configuration information comprising a service descriptor; transmitting a connectivity request message to the network to request a data session, the connectivity request message comprising the service descriptor; andreceiving a connectivity response message from the network, the connectivity response message including a first network slice identifier in association with the service descriptor, wherein the first network identifier identifies a first network slice of the network.

16. A network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive, from a user equipment (UE), a connectivity request message, the connectivity request message comprising a service descriptor; determine, using the service descriptor, a network slice identifier of a network slice of a network to establish a data session with the UE; and transmit a connectivity response message to the UE, the connectivity response message including the network slice identifier in association with the service descriptor.

17. The network entity of claim 16, wherein the at least one processor is configured to cause the network entity to determine the network slice identifier based on at least one of: subscription data of the UE; or availability of supported network slices in a current location of the UE.

18. The network entity of claim 16 or 17, wherein the service descriptor comprises one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

19. The network entity of claim 16 or 17, wherein the service descriptor comprises an anonymized identifier associated with one or more of: an application identifier, an application category, a traffic identifier, a traffic category, or a target traffic domain.

20. The network entity of any of claims 16 to 19, wherein the at least one processor is further configured to cause the network entity to:transmit a session establishment request message to a session management network function, the session establishment request message comprising the network slice identifier.

Images