Network Slice Traffic Descriptor Encoding

Abstract

Methods, systems, and apparatus for wireless communications are described. A user equipment (UE) may receive a traffic descriptor including a string corresponding to an application of the UE. In some cases, the string may be encoded to represent a sequence of characters in the string to index or match the application to different network slices for communication of the UE. For example, the string may be encoded using American Standard Code for Information Interchange (ASCII) encoding. After receiving and decoding the encoded traffic descriptor, the UE may identify a matching network slice for the application corresponding to the string of the traffic descriptor. The UE may then attempt to establish a connection with the matching network slice for communication for the application, and may communicate with the matching network slice for the application based on successful establishment of the connection.

Description

Technical Field

[0001] The following relates generally to wireless communications, and more particularly to network slice traffic descriptor encoding.

[0002] background

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ various technologies, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0004] A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication for multiple communication devices, which may be further referred to as user equipment (UE). In some wireless communication systems, a UE may access a network slice for communicating with a base station. Improved techniques for managing communication between a base station and a UE via a network slice are desirable.

[0005] Overview

[0006] The described technology relates to improved methods, systems, devices, and apparatuses that support network slice traffic descriptor encoding. In general, the described technology provides for a user equipment (UE) to receive a traffic descriptor that includes a string corresponding to an application of the UE (e.g., an operating system application identifier field). In some cases, a base station (e.g., a network entity) may encode the string to represent a sequence of characters in the string to index or match the application to different network slices for communication of the UE. For example, the base station may encode the string using American Standard Code for Information Interchange (ASCII) encoding to index the application using the string. After receiving and decoding the encoded traffic descriptor, the UE may identify a matching network slice for the application corresponding to the string of the traffic descriptor.

[0007] Subsequently, the UE may attempt to establish a connection with the matching network slice for communication for the application, and may communicate with the matching network slice for the application based on the successful establishment of the connection. For example, when the connection is established, the UE may transmit a registration request including a string to request registration of the application with the matching network slice. Additionally, once the connection is established, the UE may use the connection to transmit a data service request with a string to request a data service for the application.

[0008] A method for wireless communication by a UE is described. The method may include: receiving a traffic descriptor including a string corresponding to a first application of the UE; identifying a first application identifier of the first application based on the string; establishing a connection with a first network slice in a set of available network slices based on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0009] An apparatus for wireless communication by a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a traffic descriptor including a string corresponding to a first application of the UE; identify a first application identifier of the first application based on the string; establish a connection with a first network slice in a set of available network slices based on the first application identifier; and communicate data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0010] Another apparatus for wireless communication by a UE is described. The apparatus may include means for receiving a traffic descriptor including a string corresponding to a first application of the UE; identifying a first application identifier of the first application based on the string; establishing a connection with a first network slice in a set of available network slices based on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0011] A non-transitory computer-readable medium storing code for wireless communication by a UE is described. The code may include instructions executable by a processor for the following operations: receiving a traffic descriptor including a string corresponding to a first application of the UE; identifying a first application identifier of the first application based on the string; establishing a connection with a first network slice in a set of available network slices based on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0012] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: transmitting, via the connection, a data service request requesting data service for the first application and including the string, wherein communication of the data service traffic may be based on the data service request.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, establishing a connection with a first network slice may include operations, features, apparatuses, or instructions for the following actions: transmitting a registration request including a string requesting to register a first application with a first network slice in a set of available network slices, wherein communication of data service traffic may be based on the registration request.

[0014] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving control signaling indicating a set of strings for a set of applications listed in an application table.

[0015] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, receiving a traffic descriptor may include operations, features, apparatus, or instructions for the following actions: receiving a traffic descriptor comprising a string comprising a set of bits encoded to represent a sequence of characters in the string.

[0016] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for decoding a set of bits to obtain a string.

[0017] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, receiving a traffic descriptor may include operations, features, apparatus, or instructions for the following actions: receiving a traffic descriptor comprising a string comprising a set of bits encoded using ASCII encoding to represent a sequence of characters in the string.

[0018] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, receiving a traffic descriptor may include operations, features, apparatus, or instructions for the following actions: receiving a traffic descriptor that may be a network slice selection policy (NSSP) traffic descriptor.

[0019] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, receiving a traffic descriptor may include operations, features, apparatus, or instructions for the following actions: receiving a traffic descriptor including a string, which may be a field having an octet length.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying the first application identifier may include operations, features, apparatus, or instructions for indexing an application table based on a string to identify the first application identifier.

[0021] A method for wireless communication by a base station is described. The method may include: transmitting a traffic descriptor including a string corresponding to a first application identifier of a first application to a UE; establishing a connection between the UE and a first network slice in a set of available network slices based on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0022] An apparatus for wireless communication by a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: transmit a traffic descriptor including a string corresponding to a first application identifier of a first application to a UE; establish a connection between the UE and a first network slice in a set of available network slices based on the first application identifier; and communicate data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0023] Another apparatus for wireless communication by a base station is described. The apparatus may include means for: transmitting to a UE a traffic descriptor including a string corresponding to a first application identifier of a first application; establishing a connection between the UE and a first network slice in a set of available network slices based on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0024] A non-transitory computer-readable medium storing code for wireless communication by a base station is described. The code may include instructions executable by a processor for the following operations: transmitting a traffic descriptor including a string corresponding to a first application identifier of a first application to a UE; establishing a connection between the UE and a first network slice in a set of available network slices based on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0025] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: receiving, via the connection, a data service request requesting data service for the first application and including the string, wherein communication of the data service traffic may be based on the data service request.

[0026] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, establishing a connection with a first network slice may include operations, features, apparatuses, or instructions for the following actions: receiving a registration request including a string requesting to register a first application with a first network slice in a set of available network slices, wherein communication of data service traffic may be based on the registration request.

[0027] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting control signaling indicating a set of strings for a set of applications listed in an application table.

[0028] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, transmitting a traffic descriptor may include operations, features, apparatus, or instructions for the following actions: transmitting a traffic descriptor comprising a string comprising a set of bits encoded to represent a sequence of characters in the string.

[0029] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for encoding a set of bits to obtain a string.

[0030] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, transmitting a traffic descriptor may include operations, features, apparatus, or instructions for the following actions: transmitting a traffic descriptor comprising a string comprising a set of bits encoded using ASCII encoding to represent a sequence of characters in the string.

[0031] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, transmitting a traffic descriptor may include operations, features, means, or instructions for transmitting a traffic descriptor, which may be a NSSP traffic descriptor.

[0032] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, transmitting a traffic descriptor may include operations, features, apparatus, or instructions for the following actions: transmitting a traffic descriptor including a string, which may be a field having an octet length.

[0033] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the first application identifier may be an operating system application identifier. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 An example of a wireless communication system for supporting network slicing traffic descriptor encoding according to various aspects of the present disclosure is illustrated.

[0036] Figure 2 An example of a wireless communication system supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is illustrated.

[0037] Figure 3 An example of a network slice mapping configuration supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is illustrated.

[0038] Figure 4 An example of a process flow supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is illustrated.

[0039] Figure 5 and Figure 6 A block diagram of a device supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is shown.

[0040] Figure 7 A block diagram of a user equipment (UE) communications manager supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is shown.

[0041] Figure 8 A diagram of a system including devices supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is shown.

[0042] Fig. 9 and Fig.10 A block diagram of a device supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is shown.

[0043] Fig.11 A block diagram of a base station communication manager supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is shown.

[0044] Fig.12 A diagram of a system including devices supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is shown.

[0045] Figures 13 to 18 A flowchart illustrating a method for supporting network slice traffic descriptor encoding according to various aspects of the present disclosure is shown.

[0046] Detailed Description

[0047] Some wireless communication systems may support the use of network slicing to support additional features and network function optimization. A network slice may be a logical end-to-end network that can be created dynamically. For example, a user equipment (UE) may establish a protocol data unit (PDU) session for a logical data network, where the logical data network may be referred to as a network slice. In some cases, the UE may select a network slice based on an application or subscription service. For example, the UE may have an application that is an Internet Protocol (IP) Multimedia System (IMS) voice application, and the UE may select a network slice configured to support the mobile broadband application. Additionally or alternatively, the UE may have an application configured as an Internet of Things (IoT) application; for example, an IoT application may configure the UE to operate as an IoT gateway device that periodically compiles data and transmits the data to a remote server. In this way, the UE may select a network slice configured to support large-scale IoT data traffic. By enabling different network slices to serve different applications, subscriptions, etc., the UE may improve its resource utilization in the network while also meeting the performance requirements of the UE's individual applications.

[0048] The network slice may be served by different network functions (e.g., access and mobility management function (AMF), session management function (SMF), etc.). In some cases, the network may provide network slice selection assistance information (NSSAI) or a set of allowed NSSAI (S-NSSAI) to the UE. NSSAI may include information indicating allowed or supported network slices for use by the UE and other information. The data network may be associated with the S-NSSAI. In some cases, the network operator may provide a network slice selection policy (NSSP) to the UE. The NSSP may include one or more NSSP rules, each rule associating an application with a specific S-NSSAI. In some cases, the default rule may match all applications to the S-NSSAI. In some cases, a UE application associated with the S-NSSAI may request data transfer.

[0049] Additionally, the NSSP may include a traffic descriptor that includes a string corresponding to an application of the UE (e.g., an operating system application identifier field). The NSSP may enable the UE to index an application to a specific network slice instance. The UE may use the traffic descriptor to search for traffic and match it to an application running in the operating system of the UE. A public land mobile network (PLMN) may provide the UE with a list of traffic descriptors associated with each application of the UE, wherein each traffic descriptor indicates a network slice (e.g., from a set of available network slices) used to provide data services to the corresponding application. Each traffic descriptor may include an application identifier indicating the corresponding application (e.g., an operating system application identifier field). Thus, when an application requests a new data service, the UE may match the application identifier of the requesting application with the application identifier within the traffic descriptor. The UE may then transmit a data service request associated with the network slice indicated by the traffic descriptor. However, the traffic descriptor may not be encoded.

[0050] As described herein, a network entity (e.g., a base station) may encode a string (e.g., an operating system application identifier field) in a traffic descriptor using American Standard Code for Information Interchange (ASCII) encoding. In some cases, the UE may store a table that maps strings to application identifiers of different applications. The UE may receive a NSSP traffic descriptor including a string (e.g., an encoded string), identify (e.g., using a table) an application identifier of the application based on the received string, establish a connection with the network slice based on the identified application identifier, and communicate data service traffic of the application using the established connection.

[0051] Various aspects of the present disclosure are initially described in the context of a wireless communication system. Additionally, various aspects of the present disclosure are illustrated by additional wireless communication systems, network slice mapping configurations, and process flows. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to network slice traffic descriptor encoding.

[0052] Figure 1 An example of a wireless communication system 100 supporting network slicing traffic descriptor encoding according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0053] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be different forms of devices or devices with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.

[0054] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), such as Figure 1 as shown in .

[0055] Each base station 105 may communicate with the core network 130, or communicate with each other, or both. For example, the base station 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3 or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105), or indirectly (e.g., via the core network 130), or directly and indirectly on the backhaul link 120 (e.g., via X2, Xn or other interfaces). In some examples, the backhaul link 120 may be or include one or more wireless links.

[0056] One or more of the base stations 105 described herein may include or may be referred to by a person of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a B node, an evolved B node (eNB), a next generation B node or a gigabit B node (any of which may be referred to as a gNB), a home B node, a home evolved B node, or other suitable terminology.

[0057] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0058] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .

[0059] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0060] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by UE 115. A carrier may operate in a standalone mode in which initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode in which a connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0061] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in a TDD mode).

[0062] A carrier may be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) of a carrier of a particular radio access technology. Devices (e.g., base stations 105, UEs 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communications on a particular carrier bandwidth, or may be configurable to support communications on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., subband, BWP) or all of a carrier bandwidth.

[0063] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may include a code element period (e.g., the duration of a modulation code element) and a subcarrier, where the code element period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the code rate of the modulation scheme, or both). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further improve the data rate or data integrity of communication with UE 115.

[0064] One or more parameter designs for a carrier may be supported, where the parameter designs may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter designs. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to the one or more active BWPs.

[0065] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit, and the basic time unit can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0066] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of code element periods (e.g., depending on the length of the cyclic prefix added before each code element period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots containing one or more code elements. Excluding the cyclic prefix, each code element period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0067] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0068] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0069] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with a base station 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. The range of such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area depending on various factors (such as the capabilities of the base station 105). For example, a cell may be or include a building, a subset of a building, or an external space between or overlapping a geographic coverage area 110, as well as other examples.

[0070] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power base station 105 (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A base station 105 may support one or more cells and may also support communications on one or more cells using one or more component carriers.

[0071] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0072] In some examples, base stations 105 may be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0073] The wireless communication system 100 may be configured to support ultra-reliable communication or low latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency communication (URLLC) or mission-critical communication. UE 115 may be designed to support ultra-reliable, low latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private communication or group communication, and may be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, critical mission, and ultra-reliable low latency may be used interchangeably herein.

[0074] In some examples, UE 115 may also be able to communicate directly with other UE 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of a base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105, or may not be able to receive transmissions from the base station 105 for other reasons. In some examples, each group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between each UE 115 without involving the base station 105.

[0075] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a base station 105 associated with the core network 130. User IP packets may be delivered via a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. Operator IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0076] Some network devices (such as base stations 105) may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or merged into a single network device (e.g., base station 105).

[0077] The wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the 300 MHz to 3 GHz region is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about 1 decimeter to 1 meter long. UHF waves may be blocked or redirected by buildings and environmental features, but these waves may penetrate various structures sufficiently for macro cells to provide service to UEs 115 located indoors. Transmissions using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0078] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in coordination with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0079] The base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having antenna ports of several rows and columns that the base station 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0080] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0081] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly to communicate on a logical channel. The media access control (MAC) layer may perform priority handling and multiplex logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission of the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer of user plane data between a UE 115 and a base station 105 or a core network 130. In the physical layer, transport channels may be mapped to physical channels.

[0082] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received on communication link 125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve the throughput of the MAC layer in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0083] In a wireless communication system 100 (e.g., a 5G system), the functions of the core network 130 may be virtualized to allow for a more flexible architecture. Specifically, the core network 130 may include several entities (or functions), such as an authentication server function (AUSF), AMF, SMF, etc. implemented in software. The wireless communication system 100 may also support the use of network slicing to support additional features and network function optimization. A network slice (e.g., a network portion, a subnetwork, etc.) may be a logical end-to-end network that can be created dynamically.

[0084] For example, UE 115 may establish a PDU session for a logical data network, where the logical data network may be referred to as a network slice. In some cases, UE 115 may select a network slice based on an application or a subscription service. For example, UE 115 may have an application that is an IMS voice application, and UE 115 may select a network slice configured to support the mobile broadband application. Additionally or alternatively, UE 115 may have an application configured as an IoT application; for example, the IoT application may configure UE 115 to operate as an IoT gateway device that periodically compiles data and transmits the data to a remote server. In this way, UE 115 may use a network slice configured to support large-scale IoT data traffic. Additionally or alternatively, network slices may provide different levels of service. For example, UE 115 may use different types of communications with different latency and reliability requirements, so that a first type of communication (e.g., URLLC) may be communicated on a first network slice with a higher service level, while a second type of communication (e.g., eMBB traffic) may be communicated on a second network slice with a lower service level. By having different network slices serve different applications, subscriptions, etc., UE 115 can improve its resource utilization in the network while also meeting the performance requirements (e.g., Quality of Service (QoS) requirements) of each application of UE 115.

[0085] The use of network slicing enables virtualization and multiplexing of independent logical networks on the same physical network infrastructure. Each network slice may include an isolated end-to-end network customized to meet different requirements (e.g., QoS, different application profiles, usage, etc.) requested by a specific application. For example, different applications of UE 115 may include services with different service level requirements. In this way, network slicing can achieve flexible and scalable configuration on top of a common network infrastructure to meet different service level requirements of different applications. In some cases, different network slices may be managed by separate operators (e.g., mobile virtual network operators), where the infrastructure provider leases physical resources to these operators that share the underlying physical network of the infrastructure provider. Subsequently, the operator can deploy multiple network slices customized for different applications provided to users associated with the operator.

[0086] Additionally, network slicing can enable mobile operators to create specific virtual networks that cater to specific clients and use cases. For example, certain applications (e.g., such as eMBB communications, machine-to-machine (M2M) communications in manufacturing or logistics, smart cars, etc.) can benefit from utilizing different aspects of wireless communications. The first application can use higher speeds, the second application can use low latency, the third application can use edge computing resources, etc. By creating separate slices that prioritize specific resources, mobile operators can provide customized solutions to specific industries. For example, different industries (e.g., marketing, augmented reality, mobile gaming, etc.) can use these network slices to meet the corresponding requirements of these industries. Additionally, network slicing can also enhance service continuity through improved roaming across networks by creating virtual networks running on physical infrastructure spanning multiple local or national networks, by allowing the host network to create an optimized virtual network that replicates the virtual network provided by the home network for roaming devices (e.g., UE 115), etc.

[0087] The network slices may be provided by different network functions (e.g., AMF, SMF, etc.). In some cases, the network may provide NSSAI or S-NSSAI to UE 115. NSSAI may include information indicating the allowed or supported network slices for use by UE 115 and other information. The data network may be associated with S-NSSAI. In some cases, the network operator may provide NSSP to UE 115. NSSP may include one or more NSSP rules, each rule associating an application with a specific S-NSSAI. In some cases, the default rule may match all applications to S-NSSAI. In some cases, UE applications associated with S-NSSAI may request data transfer.

[0088] Additionally, the NSSP may include a traffic descriptor that includes a string corresponding to an application of the UE 115 (e.g., an operating system application identifier field). The NSSP may enable the UE 115 to index an application to a specific network slice instance. The UE 115 may use the traffic descriptor to search for traffic and match it to an application running in the operating system of the UE 115. The PLMN may provide the UE 115 with a list of traffic descriptors associated with each application of the UE 115, wherein each traffic descriptor indicates a network slice (e.g., from a set of available network slices) for providing data services to the corresponding application. Each traffic descriptor may include an application identifier indicating the corresponding application (e.g., an operating system application identifier field). Thus, when an application requests a new data service, the UE 115 may match the application identifier of the requesting application with the application identifier within the traffic descriptor. The UE 115 may then transmit a data service request associated with the network slice indicated by the traffic descriptor. However, the traffic descriptor may not be encoded.

[0089] The NSSP traffic descriptor (e.g., traffic descriptor) of an operating system application identifier field (e.g., which corresponds to an application) may be a core component that enables the UE 115 to index an application to a network slice instance. The UE 115 may use the operating system application identifier field to search for a detailed application in a running operating system and match it to a corresponding network slice. In some cases, the NSSP traffic descriptor may include one (1) octet length field and an operating system identifier field. Conventional techniques do not provide for encoding the operating system application identifier. Encoding of the operating system application identifier may be desirable and may be utilized by UE vendors, application vendors, operating system vendors, operators, governments, etc. The techniques discussed herein provide for efficiently encoding the operating system application identifier field and provide how to encode or index a large collection of different applications using a single operating system application identifier in a traffic description.

[0090] The wireless communication system 100 may support efficient techniques for encoding operating system application identifiers. For example, a network entity (e.g., base station 105) may encode an application identifier using ASCII encoding to generate a string (e.g., an operating system application identifier field) to include in an NSSP traffic descriptor. In some cases, the UE may store a table that maps strings to application identifiers of a set of different applications. The UE may receive an NSSP traffic descriptor including a string (e.g., an encoded string indicating an operating system application identifier field), identify (e.g., using a table) an application identifier of the application based on the received string, establish a connection with the network slice based on the identified application identifier, and use the established connection to communicate data service traffic of the application.

[0091] Figure 2 An example of a wireless communication system 200 that supports network slicing traffic descriptor encoding according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a base station 105-a and a UE 115-a, which may be respectively as described above with reference to Figure 1 1 and 115. Additionally, the UE 115-a may use one or more network slices as part of communicating with the base station 105-a. In some cases, the UE 115-a may include multiple applications, where different applications in the multiple applications correspond to network slices in the one or more network slices (e.g., different applications may correspond to the same network slice or different network slices).

[0092] As described herein, the base station 105-a may transmit a traffic description including an application identifier field 210 to the UE 115-a on resources of the carrier 205. For example, the application identifier field 210 may be included in an NSSP traffic descriptor (e.g., a one (1) octet length field with an operating system identifier field) for an application of the UE 115-a. The NSSP traffic descriptor may include an operating system application identifier field for the application of the UE 115-a. Additionally, the base station 105-a may encode the application identifier field 210. For example, the base station 105-a may encode the application identifier field 210 using ASCII to index or match one or more applications of the UE 115-a to corresponding identifiers. That is, the encoding of the application identifier field 210 may directly use a string to index the application of the UE 115-a. In some cases, the application vendor may submit an application identifier field 210 (e.g., an operating system application identifier field) to an operator (e.g., base station 105-a) using ASCII, and the operator may update the application identifier field 210 to UE 115-a. Subsequently, UE 115-a may use the ASCII string (e.g., the encoded application identifier field 210) to match the application unique identifier in its operating system to the corresponding application and identify the corresponding network slice for the application.

[0093] For example, a fitness application (e.g., a first application) of UE 115-a may include an encoded string (e.g., com.apple.fitness.2020pro) to indicate a fitness application corresponding to a network slice. Accordingly, application identifier field 210 may include the encoded string, wherein UE 115-a may then decode bits of the string included in application identifier field 215 as part of application identification 215 to identify the corresponding fitness application. UE 115-a may then identify the network slice corresponding to the fitness application. UE 115-a may then establish a connection with the corresponding network slice as part of network slice establishment 220.

[0094] In some cases, UE 115-a may establish a connection with the corresponding network slice based on transmitting a registration request using the decoded application identifier field 210 to register the application with the corresponding network slice. Additionally, after the connection with the network slice is established, UE 115-a may transmit a data service request to the network slice via the connection using the decoded application identifier field 210, wherein the data service request includes a request for a data service for the application. Subsequently, UE 115-a may then communicate data service traffic for the application with the corresponding network slice on resources of carrier 225.

[0095] Additionally, UE 115-a may receive an indication of an application table that includes a set of strings for matching to a set of application identifiers for each application stored by UE 115-a. Accordingly, after decoding the application identifier field 210 to identify the string, UE 115-a may use the application table to determine which application corresponds to the string (e.g., as part of application identification 215). For example, UE 115-a may index the application table using the string received in the traffic descriptor to identify the corresponding application identifier of the application. Subsequently, UE 115-a may use the application determined from the application table to determine the corresponding network slice for the application and establish a connection with the determined corresponding network slice.

[0096] In some operating systems, applications corresponding to a particular operating system may use a single unique bundle identifier during the lifecycle for those applications (e.g., up to 10 years or more).For example, Table 1 below may illustrate unique bundle identifiers shared by different applications on UE 115-a.

[0097] Table 1 - Bundle identifiers for different applications

[0098] Application Name Bundle Identifier Activity com.apple.Fitness App Store com.apple.AppStore books com.apple.iBooks

[0099] The unique bundle identifier may include a partial string "com.apple" that is common to each application, followed by a corresponding identifier of the application (e.g., "Fitness", "AppStore", "iBooks", etc.). The application identifier field 210 may include an encoded set of bits (e.g., via ASCII) to represent the bundle identifier (e.g., a string) of the application. The UE 115-a may then identify the application corresponding to the bundle identifier (e.g., based on Table 1 or a similar application table). Additionally, the UE 115-a may identify a network slice to be used for communicating data service traffic for the identified application and establish a connection with the network slice to subsequently communicate data service traffic for the application.

[0100] Figure 3 An example of an application routing configuration 300 supporting network slice traffic descriptor encoding according to aspects of the present disclosure is illustrated. In some instances, the application routing configuration 300 can implement aspects of the wireless communication systems 100 and 200. For example, the UE 115 and the base station 105 can use the application routing configuration 300 to determine which applications 305 are mapped to different network slices 315.

[0101] In some cases, the routing component 310 can be used to determine the mapping or routing between the applications 305 to the network slices 315. For example, each application 305 can include a unique identifier of the application 305 (e.g., a bundle identifier, an application identifier field, etc.). The routing component 310 can use information about each application 305 together with the NSSP traffic descriptor (e.g., for each application 305, common to all applications 305, etc.) to identify which applications 305 correspond to which network slice 315. As an example, a first application 305-a and a second application 305-b can use a first network slice 315-a, while a third application 305-c and a fourth application 305-d can use a second network slice 315-b. The first network slice 315-a can provide different service level requirements (e.g., QoS, latency, reliability, resource location, etc.) than the second network slice 315-b, wherein the applications 305 are matched to different network slices 315 based in part on these different service level requirements.

[0102] After the routing component 310 is used to identify which applications 305 are mapped to which network slice, this information can be included in the control signaling transmitted to the UE 115. Additionally, the control signaling can include an application table that maps different applications of the UE 115 to their corresponding unique identifiers (e.g., an operating system application identifier field, an application identifier field, and a string, etc.). As described herein, the base station 105 can then encode the unique identifier of the application (e.g., via ASCII) into a set of encoded bits that form a string and transmit the string to the UE 115 within the NSSP traffic descriptor of the application. Accordingly, after decoding the set of encoded bits to obtain the string, the UE 115 can identify the unique identifier of the application corresponding to the string (e.g., based on the application table). Additionally, the UE 115 can then identify the corresponding network slice for the application based on the control signaling, and can establish a connection with the corresponding network slice for communicating traffic (e.g., data service traffic) for the application.

[0103] Figure 4 An example of a process flow 400 for supporting network slicing traffic descriptor encoding according to aspects of the present disclosure is illustrated. In some examples, the process flow 400 can implement aspects of the wireless communication systems 100 and 200. For example, the process flow 400 may include a base station 105-b and a UE 115-b, which may be respectively as described above with reference to Figure 1-3 Examples of corresponding base stations 105 and UEs 115 are described.

[0104] In the following description of process flow 400, operations between UE 115-b and base station 105-b may be transmitted in an order different from the exemplary order shown, or operations performed by UE 115-b and base station 105-b may be performed in a different order or at a different time. Certain operations may also be excluded from process flow 400, or other operations may be added to process flow 400. It will be understood that although UE 115-b and base station 105-b are shown as performing several operations of process flow 400, any wireless device may perform the operations shown.

[0105] At 405, UE 115-b may receive (e.g., from base station 105-b) a traffic descriptor including a string corresponding to a first application of UE 115-b. In some cases, UE 115-b may receive a traffic descriptor including a string having a set of bits encoded to represent a sequence of characters in the string. For example, UE 115-b may receive a traffic descriptor including a string having a set of bits encoded using ASCII encoding to represent a sequence of characters in the string. Additionally, UE 115-b may receive a traffic descriptor that is an NSSP traffic descriptor, a field having an octet length, or a combination thereof.

[0106] At 410 , UE 115 - b may receive control signaling (eg, from base station 105 - b ) indicating a set of strings for a set of applications listed in an application table.

[0107] At 415, UE 115-b may identify a first application identifier of the first application based on the string. For example, UE 115-b may decode the set of bits to obtain the string (e.g., and then identify the first application identifier). In some cases, the first application identifier may be an operating system application identifier.

[0108] At 420, UE 115-b may index an application table based on the string to identify the first application identifier.

[0109] At 425, UE 115-b may establish a connection with a first network slice in the set of available network slices based on the first application identifier (e.g., via base station 105-b). In some cases, UE 115-b may transmit a registration request including the string to request registration of the first application with the first network slice in the set of available network slices.

[0110] At 430, UE 115-b may transmit, via the connection, a data service request requesting data service for a first application and including a string for the application. For example, the requesting application may provide its application identifier to the modem of UE 115-b. The modem of UE 115-b may use the application identifier to index an application table to identify a string corresponding to the application identifier of the requesting application. The modem of UE 115-b may transmit a data service request requesting data service for a first application and including a string for the application.

[0111] At 435, UE 115-b may communicate data service traffic for a first application corresponding to a first application identifier via a connection to a first network slice. In some cases, the communication of the data service traffic may be based on a registration request. The data service traffic may include a string of a requesting application. In the downlink direction, the modem of UE 115-b may index an application table using the string received in the data service traffic to identify the application identifier corresponding to the string. The modem of UE 115-b may then route the downlink data service traffic to the application corresponding to the application identifier retrieved from the application table. In the uplink direction, the application may provide data service traffic with its application identifier to the modem of UE 115-b. The modem may index the application table using the application identifier to identify the string corresponding to the application. The modem of UE 115-b may transmit uplink data service traffic together with the string to base station 105-b for routing to the corresponding network slice. Beneficially, in some examples, a string (e.g., an ASCII string) in an application identifier field (e.g., an “OS App Id field”) of a traffic descriptor can be uniquely matched to an application identifier of an application of the operating system of UE 115-b.

[0112] Figure 5 A block diagram 500 of a device 505 supporting network slice traffic descriptor encoding according to aspects of the present disclosure is shown. The device 505 may be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a UE communication manager 515, and a transmitter 520. The device 505 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0113] The receiver 510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to network slice traffic descriptor encoding, etc.). The information may be passed to other components of the device 505. The receiver 510 may be a reference Figure 8Examples of aspects of the described transceiver 820. The receiver 510 may utilize a single antenna or a collection of antennas.

[0114] The UE communication manager 515 may receive a traffic descriptor including a string corresponding to a first application of the UE. In some cases, the UE communication manager 515 may identify a first application identifier of the first application based on the string. Additionally, the UE communication manager 515 may establish a connection with a first network slice in the set of available network slices based on the first application identifier. Subsequently, the UE communication manager 515 may communicate data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice. The UE communication manager 515 may be an example of various aspects of the UE communication manager 810 described herein.

[0115] The actions performed by the communication manager 515 as described herein may support improvements in communications. In one or more aspects, the UE communication manager 515 may enable the UE to identify an identifier based on a string representing an identifier of an application. For example, the identifier may be encoded (e.g., using ASCII encoding) that is common to multiple applications. Additionally, the encoding may enable different applications to use the same type of operating system application identifier field to indicate the corresponding application, thereby reducing computational complexity at the UE.

[0116] The UE communication manager 515 or its subcomponents may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the UE communication manager 515 or its subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0117] The UE communication manager 515 or its subcomponents may be physically located in various locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the UE communication manager 515 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the UE communication manager 515 or its subcomponents may be combined with one or more other hardware components (including, but not limited to, input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

[0118] The transmitter 520 may transmit signals generated by other components of the device 505. In some examples, the transmitter 520 may be co-located with the receiver 510 in a transceiver module. For example, the transmitter 520 may be a reference Figure 8 Examples of aspects of the described transceiver 820. The transmitter 520 may utilize a single antenna or a collection of antennas.

[0119] Figure 6 A block diagram 600 of a device 605 supporting network slice traffic descriptor encoding according to aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a UE communication manager 615, and a transmitter 640. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0120] The receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to network slice traffic descriptor encoding, etc.). The information may be passed to other components of the device 605. The receiver 610 may be a reference Figure 8 Examples of aspects of the described transceiver 820. The receiver 610 may utilize a single antenna or a collection of antennas.

[0121] UE communications manager 615 may be an example of aspects of UE communications manager 515 as described herein. UE communications manager 615 may include a traffic description component 620, an application identification component 625, a connection establishment component 630, and a data service communications component 635. UE communications manager 615 may be an example of aspects of UE communications manager 810 as described herein.

[0122] The traffic description component 620 can receive a traffic descriptor including a string corresponding to a first application of the UE.

[0123] The application identification component 625 can identify a first application identifier of the first application based on the string.

[0124] The connection establishing component 630 may establish a connection with a first network slice in the set of available network slices based on the first application identifier.

[0125] The data service communication component 635 can communicate data service traffic of a first application corresponding to a first application identifier via a connection with a first network slice.

[0126] According to the application identifier that identifies the application based on the encoded string, regardless of the application, the processor of the UE (e.g., the control receiver 610, the UE communication manager 615, the transmitter 640, the reference Figure 8 The transceiver 820 described, or a processor of a combination thereof) can decode the encoded string in the same manner. As a result, when the same type of encoding / decoding is used to determine the application identifier, the processor of the UE can reduce battery power consumption and processing power, resulting in more efficient communication.

[0127] The transmitter 640 may transmit signals generated by other components of the device 605. In some examples, the transmitter 640 may be co-located with the receiver 610 in a transceiver module. For example, the transmitter 640 may be a reference Figure 8 Examples of aspects of the described transceiver 820. The transmitter 640 may utilize a single antenna or a collection of antennas.

[0128] Figure 7 A block diagram 700 of a UE communication manager 705 supporting network slice traffic descriptor encoding according to aspects of the present disclosure is shown. The UE communication manager 705 may be an example of aspects of the UE communication manager 515, the UE communication manager 615, or the UE communication manager 810 described herein. The UE communication manager 705 may include a traffic description component 710, an application identification component 715, a connection establishment component 720, a data service communication component 725, a data service request indicator 730, an application table component 735, and a traffic description decoder 740. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0129] The traffic description component 710 may receive a traffic descriptor including a string corresponding to a first application of the UE. In some examples, the traffic description component 710 may receive a traffic descriptor that is an NSSP traffic descriptor. Additionally, the traffic description component 710 may receive a traffic descriptor including a string that is a field having an octet length.

[0130] The application identification component 715 can identify a first application identifier of the first application based on the string.

[0131] The connection establishment component 720 may establish a connection with a first network slice in the set of available network slices based on the first application identifier. In some examples, the connection establishment component 720 may transmit a registration request including a string requesting registration of the first application with the first network slice in the set of available network slices, wherein the communication of the data service traffic is based on the registration request.

[0132] The data service communication component 725 can communicate data service traffic of a first application corresponding to a first application identifier via a connection with a first network slice.

[0133] The data service request indicator 730 may transmit, via the connection, a data service request requesting a data service for the first application and including the string, wherein the communication of the data service traffic is based on the data service request.

[0134] The application table component 735 can receive control signaling indicating a set of strings for a set of applications listed in the application table. Additionally, the application table component 735 can index the application table based on the string to identify the first application identifier.

[0135] The traffic description decoder 740 may receive a traffic descriptor including a string of characters including a set of bits encoded to represent a sequence of characters in the string of characters. In some examples, the traffic description decoder 740 may decode the set of bits to obtain the string of characters. Additionally or alternatively, the traffic description decoder 740 may receive a traffic descriptor including a string of characters including a set of bits encoded using ASCII encoding to represent a sequence of characters in the string of characters.

[0136] Figure 8 A diagram of a system 800 including a device 805 supporting network slicing traffic descriptor encoding according to aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein or include components of these devices. The device 805 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a UE communication manager 810, an I / O controller 815, a transceiver 820, an antenna 825, a memory 830, and a processor 840. These components may be in electronic communication via one or more buses (e.g., a bus 845).

[0137] The UE communication manager 810 may receive a traffic descriptor including a string corresponding to a first application of the UE. In some cases, the UE communication manager 810 may identify a first application identifier of the first application based on the string. Additionally, the UE communication manager 810 may establish a connection with a first network slice in the set of available network slices based on the first application identifier. Subsequently, the UE communication manager 810 may communicate data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0138] I / O controller 815 can manage input and output signals of device 805. I / O controller 815 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 815 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 815 can utilize an operating system, such as Or another known operating system. In other cases, I / O controller 815 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 815 may be implemented as part of a processor. In some cases, a user may interact with device 805 via I / O controller 815 or via hardware components controlled by I / O controller 815.

[0139] The transceiver 820 may communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 820 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 820 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0140] In some cases, a wireless device may include a single antenna 825. However, in some cases, the device may have more than one antenna 825, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0141] The memory 830 may include random access memory (RAM) and read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 830 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0142] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks that support network slice traffic descriptor encoding).

[0143] The code 835 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 835 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 835 may not be directly executed by the processor 840, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0144] Fig. 9 A block diagram 900 of a device 905 supporting network slice traffic descriptor encoding according to aspects of the present disclosure is shown. The device 905 may be an example of aspects of a base station 105 as described herein. The device 905 may include a receiver 910, a base station communication manager 915, and a transmitter 920. The device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0145] The receiver 910 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to network slice traffic descriptor encoding, etc.). The information may be passed to other components of the device 905. The receiver 910 may be a reference Fig.12 Examples of various aspects of the described transceiver 1220. The receiver 910 may utilize a single antenna or a collection of antennas.

[0146] The base station communication manager 915 may transmit a traffic descriptor including a string corresponding to a first application identifier of a first application to the UE. In some cases, the base station communication manager 915 may establish a connection between the UE and a first network slice in the set of available network slices based on the first application identifier. Additionally, the base station communication manager 915 may communicate data service traffic of the first application corresponding to the first application identifier via a connection with the first network slice. The base station communication manager 915 may be an example of various aspects of the base station communication manager 1210 described herein.

[0147] The base station communication manager 915 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the base station communication manager 915 or its subcomponents may be performed by a general purpose processor, DSP, ASIC, FPGA or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0148] The base station communication manager 915 or its subcomponents may be physically located at various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the base station communication manager 915 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the base station communication manager 915 or its subcomponents may be combined with one or more other hardware components (including, but not limited to, I / O components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

[0149] The transmitter 920 may transmit signals generated by other components of the device 905. In some examples, the transmitter 920 may be co-located with the receiver 910 in a transceiver module. For example, the transmitter 920 may be a reference Fig.12 Examples of various aspects of the described transceiver 1220. The transmitter 920 may utilize a single antenna or a collection of antennas.

[0150] Fig.10 A block diagram 1000 of a device 1005 supporting network slicing traffic descriptor encoding according to aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or base station 105 as described herein. The device 1005 may include a receiver 1010, a base station communication manager 1015, and a transmitter 1035. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0151] The receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to network slice traffic descriptor encoding, etc.). The information may be passed to other components of the device 1005. The receiver 1010 may be a reference Fig.12 Examples of various aspects of the described transceiver 1220. The receiver 1010 may utilize a single antenna or a collection of antennas.

[0152] The base station communication manager 1015 may be an example of aspects of the base station communication manager 915 as described herein. The base station communication manager 1015 may include a traffic descriptor indicator 1020, a network slice connection component 1025, and a network slice communication component 1030. The base station communication manager 1015 may be an example of aspects of the base station communication manager 1210 described herein.

[0153] The traffic descriptor pointer 1020 may transmit a traffic descriptor including a character string corresponding to the first application identifier of the first application to the UE.

[0154] The network slice connection component 1025 can establish a connection between the UE and a first network slice in the set of available network slices based on the first application identifier.

[0155] The network slice communication component 1030 can communicate data service traffic of a first application corresponding to a first application identifier via a connection with the first network slice.

[0156] The transmitter 1035 can transmit signals generated by other components of the device 1005. In some examples, the transmitter 1035 can be co-located with the receiver 1010 in a transceiver module. For example, the transmitter 1035 can be a reference Fig.12 Examples of various aspects of the described transceiver 1220. The transmitter 1035 may utilize a single antenna or a collection of antennas.

[0157] Fig.11 A block diagram 1100 of a base station communication manager 1105 supporting network slice traffic descriptor encoding in accordance with aspects of the present disclosure is shown. The base station communication manager 1105 may be an example of aspects of the base station communication manager 915, the base station communication manager 1015, or the base station communication manager 1210 described herein. The base station communication manager 1105 may include a traffic descriptor indicator 1110, a network slice connection component 1115, a network slice communication component 1120, a data service request component 1125, and a traffic descriptor encoder 1130. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0158] The traffic descriptor indicator 1110 may transmit to the UE a traffic descriptor including a string corresponding to a first application identifier of the first application. In some cases, the first application identifier may be an operating system application identifier. In some examples, the traffic descriptor indicator 1110 may transmit control signaling indicating a set of strings for a set of applications listed in the application table. Additionally or alternatively, the traffic descriptor indicator 1110 may transmit a traffic descriptor that is an NSSP traffic descriptor. In some examples, the traffic descriptor indicator 1110 may transmit a traffic descriptor including a string that is a field having an octet length.

[0159] The network slice connection component 1115 may establish a connection between the UE and a first network slice in the set of available network slices based on the first application identifier. In some examples, the network slice connection component 720 may receive a registration request including a string requesting registration of a first application with a first network slice in the set of available network slices, wherein communication of data service traffic is based on the registration request.

[0160] The network slice communication component 1120 can communicate data service traffic of a first application corresponding to a first application identifier via a connection with the first network slice.

[0161] The data service request component 1125 can receive, via the connection, a data service request requesting a data service for the first application and including the string, wherein communication of the data service traffic is based on the data service request.

[0162] Traffic descriptor encoder 1130 may transmit a traffic descriptor including a string of characters including a set of bits encoded to represent a sequence of characters in the string of characters. In some examples, traffic descriptor encoder 1130 may encode the set of bits to obtain the string of characters. Additionally or alternatively, traffic descriptor encoder 1130 may transmit a traffic descriptor including a string of characters including a set of bits encoded using ASCII encoding to represent a sequence of characters in the string of characters.

[0163] Fig.12 A diagram of a system 1200 including a device 1205 supporting network slicing traffic descriptor encoding according to aspects of the present disclosure is shown. The device 1205 may be an example of or include components of a device 905, a device 1005, or a base station 105 as described herein. The device 1205 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a base station communication manager 1210, a network communication manager 1215, a transceiver 1220, an antenna 1225, a memory 1230, a processor 1240, and an inter-station communication manager 1245. These components may be in electronic communication via one or more buses (e.g., a bus 1250).

[0164] The base station communication manager 1210 may transmit a traffic descriptor including a string corresponding to a first application identifier of a first application to the UE. In some cases, the base station communication manager 1210 may establish a connection between the UE and a first network slice in the set of available network slices based on the first application identifier. Additionally, the base station communication manager 1210 may communicate data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0165] The network communications manager 1215 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1215 may manage the delivery of data communications for client devices, such as one or more UEs 115.

[0166] The transceiver 1220 may communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1220 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1220 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0167] In some cases, a wireless device may include a single antenna 1225. However, in some cases, the device may have more than one antenna 1225, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0168] Memory 1230 may include RAM, ROM, or a combination thereof. Memory 1230 may store computer readable code 1235 including instructions that, when executed by a processor (e.g., processor 1240), cause the device to perform various functions described herein. In some cases, memory 1230 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0169] Processor 1240 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks that support network slice traffic descriptor encoding).

[0170] The inter-site communication manager 1245 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with UE 115 in cooperation with other base stations 105. For example, the inter-site communication manager 1245 may coordinate scheduling of transmissions to UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-site communication manager 1245 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105.

[0171] The code 1235 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1235 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 1235 may not be directly executed by the processor 1240, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0172] Fig.13 1 is a flow chart illustrating a method 1300 for supporting network slice traffic descriptor encoding according to aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE 115 or a component thereof as described herein. Figures 5 to 8 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0173] At 1305, the UE may receive a traffic descriptor including a string corresponding to a first application of the UE. The operations of 1305 may be performed according to the methods described herein. In some examples, aspects of the operations of 1305 may be performed as described with reference to Figures 5 to 8 The described traffic description component is executed.

[0174] At 1310, the UE may identify a first application identifier of the first application based on the string. The operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be performed as described with reference to Figures 5 to 8 The described application identifies the component to be executed.

[0175] At 1315, the UE may establish a connection with a first network slice in the set of available network slices based on the first application identifier. The operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be as described with reference to Figures 5 to 8 The connection establishment component described is performed.

[0176] At 1320, the UE may communicate data service traffic for a first application corresponding to a first application identifier via a connection to the first network slice. The operations of 1320 may be performed according to the methods described herein. In some examples, aspects of the operations of 1320 may be performed as described with reference to Figures 5 to 8 The described data service communication components are implemented.

[0177] Fig.14A flow chart illustrating a method 1400 for supporting network slice traffic descriptor encoding according to aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by reference to Figures 5 to 8 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0178] At 1405, the UE may receive a traffic descriptor including a string corresponding to a first application of the UE. The operations of 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be performed as described with reference to Figures 5 to 8 The described traffic description component is executed.

[0179] At 1410, the UE may identify a first application identifier of the first application based on the string. The operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figures 5 to 8 The described application identifies the component to be executed.

[0180] At 1415, the UE may establish a connection with a first network slice in the set of available network slices based on the first application identifier. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be as described with reference to Figures 5 to 8 The connection establishment component described is performed.

[0181] At 1420, the UE may communicate data service traffic for a first application corresponding to a first application identifier via a connection to the first network slice. The operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operations of 1420 may be performed as described with reference to Figures 5 to 8 The described data service communication components are implemented.

[0182] At 1425, the UE may transmit, via the connection, a data service request requesting a data service for the first application and including the string, wherein the communication of the data service traffic is based on the data service request. The operations of 1425 may be performed according to the methods described herein. In some examples, aspects of the operations of 1425 may be performed as described with reference to Figures 5 to 8 The described data service requests the indicator to be executed.

[0183] Fig.151 is a flow chart illustrating a method 1500 for supporting network slice traffic descriptor encoding according to aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE 115 or a component thereof as described herein. Figures 5 to 8 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0184] At 1505, the UE may receive a traffic descriptor including a string corresponding to a first application of the UE. The operations of 1505 may be performed according to the methods described herein. In some examples, aspects of the operations of 1505 may be performed as described with reference to Figures 5 to 8 The described traffic description component is executed.

[0185] At 1510, the UE may identify a first application identifier of the first application based on the string. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be performed as described with reference to Figures 5 to 8 The described application identifies the component to be executed.

[0186] At 1515, the UE may establish a connection with a first network slice in the set of available network slices based on the first application identifier. The operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operations of 1515 may be as described with reference to Figures 5 to 8 The connection establishment component described is performed.

[0187] At 1520, the UE may transmit a registration request including a string requesting registration of a first application with a first network slice in a set of available network slices, wherein communication of data service traffic is based on the registration request. The operations of 1520 may be performed according to the methods described herein. In some examples, aspects of the operations of 1520 may be performed as described with reference to Figures 5 to 8 The connection establishment component described is performed.

[0188] At 1525, the UE may communicate data service traffic for a first application corresponding to a first application identifier via a connection to the first network slice. The operations of 1525 may be performed according to the methods described herein. In some examples, aspects of the operations of 1525 may be performed as described with reference to Figures 5 to 8 The described data service communication components are implemented.

[0189] Fig.16A flow chart illustrating a method 1600 for supporting network slicing traffic descriptor encoding according to aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 1600 may be implemented by reference to Figures 9 to 12 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0190] At 1605, the base station may transmit to the UE a traffic descriptor including a string corresponding to a first application identifier of the first application. The operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figures 9 to 12 The traffic descriptor pointer described is used to perform the operation.

[0191] At 1610, the base station may establish a connection between the UE and a first network slice in the set of available network slices based on the first application identifier. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be as described with reference to Figures 9 to 12 The described network slicing is performed by connecting components.

[0192] At 1615, the base station may communicate data service traffic for a first application corresponding to a first application identifier via a connection with the first network slice. The operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Figures 9 to 12 The described network slice communication components are performed.

[0193] Fig.17 A flow chart illustrating a method 1700 for supporting network slicing traffic descriptor encoding according to aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 1700 may be implemented by reference to Figures 9 to 12 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0194] At 1705, the base station may transmit to the UE a traffic descriptor including a string corresponding to a first application identifier of the first application. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figures 9 to 12 The traffic descriptor pointer described is used to perform the operation.

[0195] At 1710, the base station may transmit a traffic descriptor including a string of characters, the string including a set of bits encoded to represent a sequence of characters in the string. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figures 9 to 12 The traffic descriptor encoder described is used to perform the operation.

[0196] At 1715, the base station may establish a connection between the UE and a first network slice in the set of available network slices based on the first application identifier. The operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be as described with reference to Figures 9 to 12 The described network slicing is performed by connecting components.

[0197] At 1720, the base station may communicate data service traffic for a first application corresponding to a first application identifier via a connection with the first network slice. The operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be performed as described with reference to Figures 9 to 12 The described network slice communication components are performed.

[0198] Fig.18 A flow chart illustrating a method 1800 for supporting network slicing traffic descriptor encoding according to aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 1800 may be implemented by reference to Figures 9 to 12 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0199] At 1805, the base station may transmit to the UE a traffic descriptor including a string corresponding to a first application identifier of the first application. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figures 9 to 12 The traffic descriptor pointer described is used to perform the operation.

[0200] At 1810, the base station may transmit a traffic descriptor including a string including a set of bits encoded using ASCII encoding to represent a sequence of characters in the string. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Figures 9 to 12 The traffic descriptor encoder described is used to perform the operation.

[0201] At 1815, the base station may establish a connection between the UE and a first network slice in the set of available network slices based on the first application identifier. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Figures 9 to 12 The described network slicing is performed by connecting components.

[0202] At 1820, the base station may communicate data service traffic for a first application corresponding to a first application identifier via a connection with the first network slice. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figures 9 to 12 The described network slice communication components are performed.

[0203] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0204] The following provides an overview of further embodiments of the invention:

[0205] Embodiment 1: A method for wireless communication by a user equipment (UE), comprising: receiving a traffic descriptor including a string corresponding to a first application of the UE; identifying a first application identifier of the first application based at least in part on the string; establishing a connection with a first network slice of a plurality of available network slices based at least in part on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0206] Embodiment 2: The method of embodiment 1 further comprises: transmitting, via the connection, a data service request requesting a data service for the first application and comprising the string, wherein the communication of the data service traffic is based at least in part on the data service request.

[0207] Embodiment 3: A method as described in any one of Embodiments 1 to 2, wherein establishing a connection with a first network slice comprises: transmitting a registration request including a string requesting to register a first application to a first network slice among a plurality of available network slices, wherein communication of data service traffic is based at least in part on the registration request.

[0208] Embodiment 4: The method as in any one of embodiments 1 to 3 further comprises: receiving control signaling indicating a plurality of character strings for a plurality of applications listed in the application table.

[0209] Embodiment 5: A method as in any one of embodiments 1 to 4, wherein receiving a traffic descriptor comprises: receiving a traffic descriptor comprising a character string, the character string comprising a plurality of bits encoded to represent a sequence of characters in the character string.

[0210] Embodiment 6: The method of embodiment 5 further comprises decoding a plurality of bits to obtain a character string.

[0211] Embodiment 7: A method as in any one of embodiments 1 to 6, wherein receiving a traffic descriptor comprises: receiving a traffic descriptor comprising a character string, the character string comprising a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the character string.

[0212] Embodiment 8: A method as described in any one of Embodiments 1 to 7, wherein receiving a traffic descriptor comprises: receiving a traffic descriptor which is a network slice selection policy traffic descriptor.

[0213] Embodiment 9: A method as in any one of embodiments 1 to 8, wherein receiving a traffic descriptor comprises: receiving a traffic descriptor comprising a character string, the character string being a field having an octet length.

[0214] Embodiment 10: The method of any one of Embodiments 1 to 9, wherein identifying the first application identifier comprises: indexing an application table based at least in part on the string to identify the first application identifier.

[0215] Embodiment 11: A method for wireless communication by a base station, comprising: transmitting a traffic descriptor including a string corresponding to a first application identifier of a first application to a user equipment (UE); establishing a connection between the UE and a first network slice among a plurality of available network slices based at least in part on the first application identifier; and communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

[0216] Embodiment 12: The method of embodiment 11 further comprises: receiving via the connection a data service request requesting a data service for the first application and comprising the string, wherein the communication of the data service traffic is based at least in part on the data service request.

[0217] Embodiment 13: A method as described in any one of Aspects 11 to 12, wherein establishing a connection with a first network slice comprises: receiving a registration request including a string requesting to register a first application with a first network slice among a plurality of available network slices, wherein communication of data service traffic is based at least in part on the registration request.

[0218] Embodiment 14: The method as in any one of embodiments 11 to 13 further comprises: transmitting control signaling indicating a plurality of character strings for a plurality of applications listed in the application table.

[0219] Embodiment 15: A method as in any one of embodiments 11 to 14, wherein transmitting a traffic descriptor comprises: transmitting a traffic descriptor comprising a character string, the character string comprising a plurality of bits encoded to represent a sequence of characters in the character string.

[0220] Embodiment 16: The method of embodiment 15 further comprises encoding a plurality of bits to obtain a character string.

[0221] Embodiment 17: A method as in any one of embodiments 11 to 16, wherein transmitting the traffic descriptor comprises: transmitting the traffic descriptor comprising a character string comprising a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the character string.

[0222] Embodiment 18: A method as described in any one of Embodiments 11 to 17, wherein transmitting a traffic descriptor comprises: transmitting a traffic descriptor which is a network slice selection policy traffic descriptor.

[0223] Embodiment 19: A method as in any one of embodiments 11 to 18, wherein transmitting a traffic descriptor comprises: transmitting a traffic descriptor comprising a character string, the character string being a field having an octet length.

[0224] Embodiment 20: A method as described in any one of embodiments 11 to 19, wherein the first application identifier is an operating system application identifier.

[0225] Embodiment 21: A device for wireless communication by a UE, comprising at least one device for executing the method of any one of embodiments 1 to 10.

[0226] Embodiment 22: A device for wireless communication by a UE, comprising: a processor; a memory in electronic communication with the processor; and instructions, which are stored in the memory and can be executed by the processor to cause the device to perform a method as described in any one of Embodiments 1 to 10.

[0227] Embodiment 23: A non-transitory computer-readable medium storing code for wireless communication by a UE, comprising: a processor; a memory in electronic communication with the processor; and instructions, which are stored in the memory and can be executed by the processor to cause the device to perform a method as described in any one of embodiments 1 to 10.

[0228] Embodiment 24: An apparatus for wireless communication by a base station includes at least one means for performing the method of any one of Embodiments 11 to 20.

[0229] Embodiment 25: A device for wireless communication by a base station, comprising: a processor; a memory in electronic communication with the processor; and instructions, which are stored in the memory and can be executed by the processor to cause the device to perform a method as described in any one of Embodiments 11 to 20.

[0230] Embodiment 26: A non-transitory computer-readable medium storing code for wireless communication by a base station, comprising: a processor; a memory in electronic communication with the processor; and instructions stored in the memory and executable by the processor to cause the device to perform a method as described in any one of Embodiments 11 to 20.

[0231] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applied to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0232] The information and signals described herein may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0233] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0234] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0235] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to carry or store instruction or data structure form of desired program code means and can be accessed by general or special-purpose computer or general or special-purpose processor any other non-transient medium.Similarly, any connection is also properly referred to as computer-readable medium.For example, if software is transmitted from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then this coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are just included in the definition of computer-readable medium. Disk and disc as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0236] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of 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 the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0237] In the accompanying drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number regardless of the second reference number, or other subsequent reference numbers.

[0238] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that can be implemented or fall within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0239] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the universal principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: receiving a traffic descriptor including a character string, wherein the character string is generated by encoding a first application identifier of a first application of the UE; identifying the first application identifier of the first application based at least in part on the string; establishing a connection with a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Communication of data service traffic of the first application corresponding to the first application identifier is performed via the connection with the first network slice.

2. The method of claim 1, further comprising: A data service request requesting data service for the first application and including the string is transmitted via the connection, wherein communication of the data service traffic is based at least in part on the data service request.

3. The method of any one of claims 1 or 2, wherein establishing the connection with the first network slice comprises: Transmitting a registration request including the string requesting registration of the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

4. The method according to any one of claims 1 or 2, further comprising: Control signaling indicating a plurality of character strings for a plurality of applications listed in an application table is received.

5. The method of any one of claims 1 or 2, wherein receiving the traffic descriptor comprises: The traffic descriptor is received including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

6. The method of claim 5, further comprising: The plurality of bits are decoded to obtain the string.

7. The method of any one of claims 1 or 2, wherein receiving the traffic descriptor comprises: The traffic descriptor is received including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

8. The method of any one of claims 1 or 2, wherein receiving the traffic descriptor comprises: The traffic descriptor received is a network slice selection policy traffic descriptor.

9. The method of any one of claims 1 or 2, wherein receiving the traffic descriptor comprises: The traffic descriptor is received including the string of characters, the string of characters being a field having an octet length.

10. The method of any one of claims 1 or 2, wherein identifying the first application identifier comprises: An application table is indexed based at least in part on the string to identify the first application identifier.

11. A method for wireless communication by a network access node, comprising: encoding a first application identifier of the first application to generate a character string; transmitting a traffic descriptor including the string corresponding to the first application identifier of the first application; establishing a connection between a user equipment (UE) and a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Communication of data service traffic of the first application corresponding to the first application identifier is performed via the connection with the first network slice.

12. The method of claim 11, further comprising: A data service request requesting data service for the first application and including the string is received via the connection, wherein communication of the data service traffic is based at least in part on the data service request.

13. The method of any one of claims 11 or 12, wherein establishing the connection with the first network slice comprises: A registration request including the string is received to register the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

14. The method of any one of claims 11 or 12, further comprising: Control signaling indicating a plurality of character strings for a plurality of applications listed in the application table is transmitted.

15. The method of any one of claims 11 or 12, wherein transmitting the traffic descriptor comprises: The traffic descriptor is transmitted including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

16. The method of claim 15, further comprising: The plurality of bits are encoded to obtain the string.

17. The method of any one of claims 11 or 12, wherein transmitting the traffic descriptor comprises: The traffic descriptor is transmitted including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

18. The method of any one of claims 11 or 12, wherein transmitting the traffic descriptor comprises: The traffic descriptor transmitted is the network slice selection policy traffic descriptor.

19. The method of any one of claims 11 or 12, wherein transmitting the traffic descriptor comprises: The traffic descriptor is transmitted including the character string, the character string being a field having an octet length.

20. The method of any one of claims 11 or 12, wherein the first application identifier is an operating system application identifier.

21. An apparatus for wireless communication by a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to: receiving a traffic descriptor including a character string, wherein the character string is generated by encoding a first application identifier of a first application of the UE; identifying the first application identifier of the first application based at least in part on the string; establishing a connection with a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Communication of data service traffic of the first application corresponding to the first application identifier is performed via the connection with the first network slice.

22. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: A data service request requesting data service for the first application and including the string is transmitted via the connection, wherein communication of the data service traffic is based at least in part on the data service request.

23. The apparatus of claim 21, wherein the instructions for establishing the connection with the first network slice are executable by the processor to cause the apparatus to: Transmitting a registration request including the string requesting registration of the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

24. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling indicating a plurality of character strings for a plurality of applications listed in an application table is received.

25. The apparatus of claim 21, wherein the instructions for receiving the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor is received including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

26. The apparatus of claim 25, wherein the instructions are further executable by the processor to cause the apparatus to: The plurality of bits are decoded to obtain the string.

27. The apparatus of claim 21, wherein the instructions for receiving the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor is received including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

28. The apparatus of claim 21, wherein the instructions for receiving the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor received is a network slice selection policy traffic descriptor.

29. The apparatus of claim 21, wherein the instructions for receiving the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor is received including the string of characters, the string of characters being a field having an octet length.

30. The apparatus of claim 21, wherein the instructions for identifying the first application identifier are executable by the processor to cause the apparatus to: An application table is indexed based at least in part on the string to identify the first application identifier.

31. An apparatus for wireless communication by a network access node, comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to: encoding a first application identifier of the first application to generate a character string; transmitting a traffic descriptor including the string corresponding to the first application identifier of the first application; establishing a connection between a user equipment (UE) and a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Communication of data service traffic of the first application corresponding to the first application identifier is performed via the connection with the first network slice.

32. The apparatus of claim 31 , wherein the instructions are further executable by the processor to cause the apparatus to: A data service request requesting data service for the first application and including the string is received via the connection, wherein communication of the data service traffic is based at least in part on the data service request.

33. The apparatus of claim 31 , wherein the instructions for establishing the connection with the first network slice are executable by the processor to cause the apparatus to: A registration request including the string is received to register the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

34. The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling indicating a plurality of character strings for a plurality of applications listed in the application table is transmitted.

35. The apparatus of claim 31 , wherein the instructions for transmitting the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor is transmitted including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

36. The apparatus of claim 35, wherein the instructions are further executable by the processor to cause the apparatus to: The plurality of bits are encoded to obtain the string.

37. The apparatus of claim 31 , wherein the instructions for transmitting the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor is transmitted including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

38. The apparatus of claim 31, wherein the instructions for transmitting the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor transmitted is the network slice selection policy traffic descriptor.

39. The apparatus of claim 31 , wherein the instructions for transmitting the traffic descriptor are executable by the processor to cause the apparatus to: The traffic descriptor is transmitted including the character string, the character string being a field having an octet length.

40. The apparatus of claim 31, wherein the first application identifier is an operating system application identifier.

41. An apparatus for wireless communication by a user equipment (UE), comprising: means for receiving a traffic descriptor comprising a character string, wherein the character string is generated by encoding a first application identifier of a first application of the UE; means for identifying the first application identifier of the first application based at least in part on the string; means for establishing a connection with a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Means for communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

42. The apparatus of claim 41, further comprising: Means for transmitting, via the connection, a data service request requesting data service for the first application and including the string, wherein communication of the data service traffic is based at least in part on the data service request.

43. The apparatus of claim 41 , wherein the means for establishing the connection with the first network slice comprises: A device for transmitting a registration request including the string requesting registration of the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

44. The apparatus of claim 41, further comprising: Means for receiving control signaling indicating a plurality of character strings for a plurality of applications listed in an application table.

45. The apparatus of claim 41, wherein the means for receiving the traffic descriptor comprises: Means for receiving the traffic descriptor including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

46. ​​The apparatus of claim 45, further comprising: Means for decoding the plurality of bits to obtain the string of characters.

47. The apparatus of claim 41, wherein the means for receiving the traffic descriptor comprises: Means for receiving the traffic descriptor including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

48. The apparatus of claim 41, wherein the means for receiving the traffic descriptor comprises: Means for receiving the traffic descriptor which is a network slice selection policy traffic descriptor.

49. The apparatus of claim 41, wherein the means for receiving the traffic descriptor comprises: Means for receiving the traffic descriptor including the string of characters, the string of characters being a field having a length of octets.

50. The apparatus of claim 41, wherein the means for identifying the first application identifier comprises: Means for indexing an application table based at least in part on the string to identify the first application identifier.

51. An apparatus for wireless communication by a network access node, comprising: means for encoding a first application identifier of a first application to generate a string; means for transmitting a traffic descriptor comprising said string corresponding to said first application identifier of said first application; means for establishing a connection between a user equipment (UE) and a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Means for communicating data service traffic of the first application corresponding to the first application identifier via the connection with the first network slice.

52. The apparatus of claim 51 , further comprising: Means for receiving, via the connection, a data service request requesting data service for the first application and including the string, wherein communication of the data service traffic is based at least in part on the data service request.

53. The apparatus of claim 51 , wherein the means for establishing the connection with the first network slice comprises: A device for receiving a registration request including the string requesting registration of the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

54. The apparatus of claim 51, further comprising: Means for transmitting control signaling indicating a plurality of character strings for a plurality of applications listed in an application table.

55. The apparatus of claim 51, wherein the means for transmitting the traffic descriptor comprises: Means for transmitting the traffic descriptor including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

56. The apparatus of claim 55, further comprising: means for encoding the plurality of bits to obtain the string of characters.

57. The apparatus of claim 51, wherein the means for transmitting the traffic descriptor comprises: Means for transmitting the traffic descriptor including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

58. The apparatus of claim 51, wherein the means for transmitting the traffic descriptor comprises: Means for transmitting the traffic descriptor which is a network slice selection policy traffic descriptor.

59. The apparatus of claim 51, wherein the means for transmitting the traffic descriptor comprises: Means for transmitting the traffic descriptor including the string of characters, the string of characters being a field having a length of octets.

60. The device of claim 51, wherein the first application identifier is an operating system application identifier.

61. A non-transitory computer-readable medium storing code for wireless communication by a user equipment (UE), the code comprising instructions executable by a processor to: receiving a traffic descriptor including a character string, wherein the character string is generated by encoding a first application identifier of a first application of the UE; identifying the first application identifier of the first application based at least in part on the string; establishing a connection with a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Communication of data service traffic of the first application corresponding to the first application identifier is performed via the connection with the first network slice.

62. The non-transitory computer readable medium of claim 61, wherein the instructions are further executable to: A data service request requesting data service for the first application and including the string is transmitted via the connection, wherein communication of the data service traffic is based at least in part on the data service request.

63. The non-transitory computer readable medium of claim 61, wherein the instructions for establishing the connection with the first network slice are executable to: Transmitting a registration request including the string requesting registration of the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

64. The non-transitory computer readable medium of claim 61, wherein the instructions are further executable to: Control signaling indicating a plurality of character strings for a plurality of applications listed in an application table is received.

65. The non-transitory computer readable medium of claim 61, wherein the instructions for receiving the traffic descriptor are executable to: The traffic descriptor is received including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

66. The non-transitory computer readable medium of claim 65, wherein the instructions are further executable to: The plurality of bits are decoded to obtain the string.

67. The non-transitory computer readable medium of claim 61, wherein the instructions for receiving the traffic descriptor are executable to: The traffic descriptor is received including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

68. The non-transitory computer readable medium of claim 61, wherein the instructions for receiving the traffic descriptor are executable to: The traffic descriptor received is a network slice selection policy traffic descriptor.

69. The non-transitory computer readable medium of claim 61, wherein the instructions for receiving the traffic descriptor are executable to: The traffic descriptor is received including the string of characters, the string of characters being a field having an octet length.

70. The non-transitory computer readable medium of claim 61, wherein the instructions for identifying the first application identifier are executable to: An application table is indexed based at least in part on the string to identify the first application identifier.

71. A non-transitory computer readable medium storing code for wireless communications by a network access node, the code comprising instructions executable by a processor to: encoding a first application identifier of the first application to generate a character string; transmitting a traffic descriptor including the string corresponding to the first application identifier of the first application; establishing a connection between a user equipment (UE) and a first network slice of a plurality of available network slices based at least in part on the first application identifier; as well as Communication of data service traffic of the first application corresponding to the first application identifier is performed via the connection with the first network slice.

72. The non-transitory computer readable medium of claim 71, wherein the instructions are further executable to: A data service request requesting data service for the first application and including the string is received via the connection, wherein communication of the data service traffic is based at least in part on the data service request.

73. The non-transitory computer readable medium of claim 71, wherein the instructions for establishing the connection with the first network slice are executable to: A registration request including the string is received to register the first application with the first network slice among the plurality of available network slices, wherein communication of the data service traffic is based at least in part on the registration request.

74. The non-transitory computer readable medium of claim 71, wherein the instructions are further executable to: Control signaling indicating a plurality of character strings for a plurality of applications listed in the application table is transmitted.

75. The non-transitory computer readable medium of claim 71, wherein the instructions for transmitting the traffic descriptor are executable to: The traffic descriptor is transmitted including the string of characters, the string of characters including a plurality of bits encoded to represent a sequence of characters in the string of characters.

76. The non-transitory computer readable medium of claim 75, wherein the instructions are further executable to: The plurality of bits are encoded to obtain the string.

77. The non-transitory computer readable medium of claim 71, wherein the instructions for transmitting the traffic descriptor are executable to: The traffic descriptor is transmitted including the string of characters, the string of characters including a plurality of bits encoded using American Standard Code for Information Interchange (ASCII) encoding to represent a sequence of characters in the string of characters.

78. The non-transitory computer readable medium of claim 71, wherein the instructions for transmitting the traffic descriptor are executable to: The traffic descriptor transmitted is the network slice selection policy traffic descriptor.

79. The non-transitory computer readable medium of claim 71, wherein the instructions for transmitting the traffic descriptor are executable to: The traffic descriptor is transmitted including the character string, the character string being a field having an octet length.

80. The non-transitory computer readable medium of claim 71, wherein the first application identifier is an operating system application identifier.

Images