Network slicing enhancements

Abstract

Various aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancement utilizing randomly generated application identifiers. For example, by handling a request for an application, a user equipment (UE) may be able to forward such a request to a network entity to receive an encoded random number token corresponding to the application, thereby providing improved indexing of applications on the UE.

Description

Technical Field

[0001] Various aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancements. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include, by way of example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) system, the Advanced LTE (LTE-A) system, the Code Division Multiple Access (CDMA) system, the Time Division Multiple Access (TDMA) system, the Frequency Division Multiple Access (FDMA) system, the Orthogonal Frequency Division Multiple Access (OFDMA) system, the Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and the Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system.

[0003] In some examples, a wireless multiple access communication system may include several base stations (BS), each of which is capable of supporting several communication devices (also referred to as user equipment (UE)) to communicate simultaneously. In an LTE or LTE-A network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation, new radio (NR) or 5G network), a wireless multiple access communication system may include several distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit receive points (TRPs), etc.) communicating with several central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more DUs communicating with a CU may define an access node (e.g., which may be referred to as a BS, a 5G NB, a next generation NodeB (gNB or gNodeB), a transmit receive point (TRP), etc.). A BS or DU may communicate with a set of UEs on downlink channels (eg, for transmissions from the BS or DU to the UEs) and uplink channels (eg, for transmissions from the UEs to the BS or DU).

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a municipal, national, regional, and even global level. NR (e.g., New Radio or 5G) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] However, as the demand for mobile broadband access continues to increase, further improvements to NR and LTE technologies are needed. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ them.

[0006] In some cases, wireless networks (such as NR and LTE networks) may deploy edge computing devices, so named because they reside at the "edge" of the network. Edge computing devices may support dynamic distribution of processing of data and / or content between edge computing devices and wireless devices (such as UEs). Summary of the invention

[0007] The systems, methods, and devices of the present disclosure each have several aspects, no single aspect of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide advantages including improved communication between a user equipment (UE) and a wireless network.

[0008] Certain aspects provide a method for wireless communication by a network entity. The method generally includes determining a network slicing instance, encoding an application identification (ID) field within a traffic descriptor bit sequence with a random number corresponding to at least one of an application or the network slicing instance, and sending the traffic descriptor bit sequence to a user equipment (UE).

[0009] Certain aspects provide a method for wireless communications by a user equipment (UE) operating system. The method generally includes sending a sliced ​​service request to a network entity, receiving a service descriptor bit sequence including an application identification (ID) field from the network entity in a network sliced ​​instance, decoding the service descriptor bit sequence to determine an encoded random number within the application ID field, determining an application ID based on the random number, and determining an application having data to be routed to the network sliced ​​instance based on the application ID.

[0010] Certain aspects provide a network entity that generally includes a processing system and a transmitter. The processing system is configured to determine a network slice instance and encode an application identification (ID) field within a service descriptor bit sequence with a random number corresponding to at least one of an application or a network slice instance; and the transmitter is configured to send the service descriptor bit sequence to a user equipment (UE).

[0011] Certain aspects provide a user equipment (UE), which generally includes a transmitter and a receiver and a processing system. The transmitter is configured to send a sliced ​​service request to a network entity; the receiver is configured to receive a service descriptor bit sequence including an application identification (ID) field from the network entity in the network slicing instance; the processing system is configured to decode the service descriptor bit sequence to determine an encoded random number in the application ID field, determine the application ID based on the random number, and determine the application having data to be routed to the network slicing instance based on the application identification.

[0012] Certain aspects provide a network entity that generally includes a component for determining a network slicing instance, a component for encoding an application identification (ID) field within a service descriptor bit sequence with a random number corresponding to at least one of an application or a network slicing instance, and a component for sending the service descriptor bit sequence to a user equipment (UE).

[0013] Certain aspects provide a user equipment (UE). The UE generally includes a component for sending a sliced ​​service request to a network entity, a component for receiving a service descriptor bit sequence including an application identification (ID) field from the network entity in the network sliced ​​instance, a component for determining an application ID based on a random number, and a component for determining an application having data to be routed to the network sliced ​​instance based on the application ID.

[0014] Certain aspects provide a computer-readable medium for wireless communication by a network entity. The computer-readable medium generally includes code executable to determine a network slicing instance, encode an application identification (ID) field within a traffic descriptor bit sequence with a random number corresponding to at least one of an application or the network slicing instance, and send the traffic descriptor bit sequence to a user equipment (UE).

[0015] Certain aspects provide a computer-readable medium for wireless communication by a user equipment (UE). The computer-readable medium generally includes code executable to send a sliced ​​service request to a network entity, receive a service descriptor bit sequence including an application identification (ID) field from the network entity in a network sliced ​​instance, decode the service descriptor bit sequence to determine an encoded random number within the application ID field, determine an application ID based on the random number, and determine an application having data to be routed to the network sliced ​​instance based on the application ID.

[0016] Certain aspects provide an apparatus for wireless communication by a network entity. The apparatus generally includes a processing system and an interface. The processing system is configured to determine a network slicing instance and encode an application identification (ID) field within a service descriptor bit sequence with a random number corresponding to at least one of an application or a network slicing instance; the interface is configured to output the service descriptor bit sequence for transmission to a user equipment (UE).

[0017] Certain aspects provide an apparatus for wireless communication by a user equipment. The UE generally includes an interface and a processor system. The interface is configured to output a sliced ​​service request for transmission to a network entity, and the processing system is configured to decode a service descriptor bit sequence to determine an encoded random number within an application ID field, determine an application ID based on the random number, and determine an application having data to be routed to a network sliced ​​instance based on the application identification.

[0018] Aspects generally include methods, apparatus, systems, computer-readable media, and processing systems as substantially described herein with reference to and as illustrated in the accompanying drawings.

[0019] To achieve the above and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to understand in detail the manner in which the above-mentioned features of the present disclosure are achieved, a more particular description briefly summarized above may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0021] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0022] Figure 2 is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in accordance with certain aspects of the present disclosure.

[0023] Figure 3 Figure illustrates example data service component type identifiers in accordance with certain aspects of the present disclosure.

[0024] Figure 4 The diagram illustrates example operations for wireless communications by a network entity in accordance with some aspects of the present disclosure.

[0025] Figure 5 The diagram illustrates example operations for wireless communications by a UE in accordance with some aspects of the present disclosure.

[0026] Figure 6 The figure illustrates an example call flow diagram for network slicing enhancements according to some aspects of the present disclosure.

[0027] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation. DETAILED DESCRIPTION

[0028] Various aspects of the present disclosure relate to wireless communications and, more particularly, to network slicing enhancement utilizing randomly generated application identifiers.

[0029] The following description provides examples, but does not limit the scope, applicability or examples set forth in the claims. Without departing from the scope of the present disclosure, changes may be made to the functions and arrangements of the elements discussed. Various examples may omit, replace or add various procedures or components as appropriate. For example, the method described may be performed in an order different from the order described, and various steps may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method, which is practiced using other structures, functions or structures and functions other than or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" used herein means "used as an example, instance or illustration". Any aspect described herein as "exemplary" is not necessarily to be understood as preferred or superior to other aspects.

[0030] The technology described herein can be used for various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. Cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (e-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS).

[0031] New Radio (NR) is an emerging wireless communication technology developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP). Cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe various aspects, various aspects of the present disclosure may be applied to communication systems based on other generations (such as 5G and later including NR technology).

[0032] New Radio (NR) access (e.g., 5G technology) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting broadband (e.g., 80 MHz or higher), millimeter wave (mmW) targeting high carrier frequencies (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmit time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0033] Example Wireless Communication System

[0034] Figure 1 FIG. 1 shows an example wireless communication network 100 in which aspects of the present disclosure may be implemented. For example, BS 110 may be configured to implement Figure 4 The operation 400 of UE 120 may be configured to perform Figure 5 Operation 500 to achieve network slicing enhancement using randomly generated application identifiers.

[0035] The detailed description set forth below in conjunction with the accompanying drawings is intended to describe various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid confusion with such concepts.

[0036] The technology described in this article can be used in various wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, etc. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE802.16, IEEE 802.20, , GSM, UMTS and LTE are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known in the art. For clarity, certain aspects of these technologies are described below for LTE, and LTE terminology is used in most of the description below.

[0037] Single carrier frequency division multiple access (SC-FDMA) is a technique that utilizes single carrier modulation and frequency domain equalization. SC-FDMA has similar performance and essentially the same overall complexity as those of OFDMA systems. SC-FDMA signals have lower peak-to-average power ratio (PAPR) due to their inherent single carrier structure. SC-FDMA has attracted great attention, especially in uplink communications, where lower PAPR greatly benefits mobile terminals in terms of transmit power efficiency. It is currently the working assumption for uplink multiple access schemes in 3GPP Long Term Evolution (LTE) or Evolved UTRA.

[0038] Figure 1 A wireless communication network 100 is shown in which aspects of the present disclosure may be practiced. For example, an evolved Node B 110 may cache content and send the cached content to a user equipment (UE) 120, as described herein.

[0039] The wireless communication network 100 may be an LTE network. The wireless network 100 may include several evolved Node Bs (eNBs) 110 and other network entities. An eNB may be a station that communicates with a UE and may also be referred to as a base station, access point, etc. A Node B is another example of a station that communicates with a UE.

[0040] Each eNB 110 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​an eNB and / or an eNB subsystem serving that coverage area, depending on the context in which the term is used.

[0041] An eNB may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a pico cell may be referred to as a pico eNB. An eNB for a femto cell may be referred to as a femto eNB or a home eNB. In Figure 1In the example shown, eNBs 110a, 110b, and 110c may be macro eNBs for macro cells 102a, 102b, and 102c, respectively. eNB 110x may be a pico eNB for pico cell 102x. eNBs 110y and 110z may be femto eNBs for femto cells 102y and 102z, respectively. An eNB may support one or more (e.g., three) cells.

[0042] The wireless network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., an eNB or UE) and sends transmissions of data and / or other information to a downstream station (e.g., a UE or eNB). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay station 110r may communicate with the eNB 110a and the UE 120r to facilitate communication between the eNB 110b and the UE 120r. A relay station may also be referred to as a relay eNB, a relay, etc.

[0043] The wireless network 100 may be a heterogeneous network including different types of eNBs, such as macro eNBs, pico eNBs, femto eNBs, repeaters, etc. These different types of eNBs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro eNB may have a high transmit power level (e.g., 20 Watts), while a pico eNB, a femto eNB, and a repeater may have a low transmit power level (e.g., 1 Watt).

[0044] The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the eNBs may have similar frame timing, and transmissions from different eNBs may be approximately aligned in time. For asynchronous operation, the eNBs may have different frame timing, and transmissions from different eNBs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0045] A network controller 130 may couple to a set of eNBs and provide coordination and control for these eNBs. Network controller 130 may communicate with eNBs 110 via a backhaul. eNBs 110 may also communicate with each other, directly or indirectly, for example, via a wireless or wired backhaul.

[0046] UE 120 may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc. UE may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a notebook computer, a cordless phone, a wireless local loop (WLL) station, etc. UE may be able to communicate with macro eNBs, pico eNBs, femto eNBs, and repeaters, etc. In Figure 1 In FIG. 1 , a solid line with double arrows indicates desired transmissions between a UE and a serving eNB, which is an eNB designated to serve the UE on the downlink and / or uplink. A dashed line with double arrows indicates interfering transmissions between a UE and an eNB.

[0047] LTE utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are sent in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.8 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0048] The wireless network 100 may also include a UE 120 capable of communicating with a core network via one or more radio access networks (RANs) implementing one or more radio access technologies (RATs). For example, according to certain aspects provided herein, the wireless network 100 may include collocated access points (APs) and / or base stations that provide communications via a first RAN implementing a first RAT and a second RAN implementing a second RAT. According to certain aspects, the first RAN may be a wide area wireless access network (WWAN) and the second RAN may be a wireless local area network (WLAN). Examples of WWANs may include, but are not limited to, for example, radio access technologies (RATs) such as LTE, UMTS, cdma2000, GSM, and the like. Examples of WLANs may include, but are not limited to, for example, RATs such as technologies based on Wi-Fi or IEEE 802.11, and the like.

[0049] According to certain aspects provided herein, wireless network 100 may include collocated Wi-Fi access points (APs) and femto eNBs that provide communications via Wi-Fi and cellular radio links. As used herein, the term "collocated" generally refers to "in close proximity to," and applies to Wi-Fi APs or femto eNBs within the same device housing or within separate devices in close proximity to each other. According to certain aspects of the present disclosure, as used herein, the term "femto AP" may refer to collocated Wi-Fi APs and femto eNBs.

[0050] Figure 2 1 is a block diagram of an example embodiment of a base station 110 (also referred to as an access point (AP)) and a UE 120 in which aspects of the present disclosure may be practiced. For example, various processors of the BS 110 may be configured to perform (or cause the UE 120 to perform) Figure 4 Operation 400 of the UE 120 and / or various processors of the UE 120 may be configured to implement Figure 5 Operation 500.

[0051] At base station 110, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214. In one aspect, each data stream is transmitted through a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for that data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0052] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a specific modulation scheme (e.g., BPSK, QSPK, M-PSK, or M QAM) selected for the data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by processor 230.

[0053] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then sends the modulation symbols to the N T The transmitters (TMTR) 222a to 222t provide N T In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0054] Each receiver 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. T The modulation signals are respectively T The antennas 224a to 224t are transmitted.

[0055] At UE 120, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

[0056] The RX data processor 260 then receives and processes the N R N of receivers 254 R received symbol streams to provide N T The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the base station 110.

[0057] The processor 270 periodically determines which precoding matrix to use. The processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0058] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238, which also receives traffic data for a number of data streams from the data source 236, modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the base station 110.

[0059] At the base station 110, the modulated signal from the UE 120 is received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reservation link message sent by the UE. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0060] According to certain aspects, controllers / processors 230 and 270 may direct operations at base station 110 and UE 120, respectively. According to one aspect, processor 230, TX data processor 214, and / or other processors and modules at base station 110 may perform or direct processes for the techniques described herein. According to another aspect, processor 270, RX data processor 260, and / or other processors and modules at UE 120 may perform or direct processes for the techniques described herein. For example, processor 230, TX data processor 214, and / or other processors and modules at base station 110 may perform or direct processes for the techniques described herein. Figure 4 Operations 400 of the UE 120 and / or other processors and components at the UE 120 may perform or direct Figure 5 Operation 500.

[0061] Example Network Slicing Enhancement

[0062] As described above, aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancements utilizing randomly generated application identifiers. For example, by handling a request of an application, a user equipment (UE) may be able to forward such a request to a network entity to receive an encoded random number token corresponding to the application, thereby providing improved indexing of applications on the UE.

[0063] In a traditional scenario, when an application that does not require special processing (as identified by their application ID) requests a wireless network connection, the HLOS sends an Internet connection setup request to the modem to establish a default Internet PDU session. The requesting application and other regular applications share this default Internet PDU session.

[0064] On the other hand, URSP applications may require special handling, such as special connection capabilities provided on special network slices. In this context, a URSP application may refer to any application with data services that can be sent according to one or more URSP rules (e.g., specifying a routing descriptor (RSD)). Therefore, URSP applications may not be able to share the default Internet PDU session. Network slicing generally refers to a set of resources that effectively establishes a logical network running on a shared physical infrastructure and is capable of providing a negotiated quality of service. The technologies that support network slicing are typically transparent to users (e.g., business customers / subscribers).

[0065] PDU Session Establishment is a procedure that allows data transfer to a Data Network (DN) in a network slice. A PDU Session is associated with a Single Network Slice Selection Assistance Information (S-NSSAI) and a Data Network Name (DNN). A UE registered in a PLMN and having obtained an allowed NSSAI indicates the S-NSSAI in the PDU Session Establishment procedure according to the Network Slice Selection Policy (NSSP) in the URSP, and if available, the DNN will be associated with the PDU Session.

[0066] Currently, the Network Slice Selection Policy (NSSP) service descriptor "OS App Id field" is the basic component for the UE to index the application to a specific network slicing instance. Figure 3 As shown, Figure 3 is an example data service component type identifier, and the "OSApp Id Type" can be eight bits (as defined by current wireless standards) to provide information to the UE to search and match the application corresponding to the application ID in the running OS. However, current implementations do not provide for encoding the "OS App Id field" by UE vendors, application vendors, OS vendors, operators and / or governments. In other words, there is currently no solution to encode and / or index multiple different applications using the "OS App Id field".

[0067] Thus, certain aspects provide enhanced network slicing. For example, certain aspects provide encoding / decoding an application identification (ID) field using a random number corresponding to an application and / or network slicing instance.

[0068] Figure 4 The diagram illustrates example operations 400 for wireless communications by a network entity. For example, operations 400 may be performed by a network entity (e.g., such as Figure 1 or Figure 2 The BS 110 in the wireless communication network 100 is used to enhance network slicing.

[0069] Operations 400 begin at 402 by determining a network slicing instance. At 404, the network entity encodes an application identification (ID) field within a traffic descriptor bit sequence with a random number corresponding to at least one of an application or a network slicing instance. At 406, the network entity sends the traffic descriptor bit sequence to the UE.

[0070] Figure 5 FIG. 5 illustrates example operations 500 of wireless communication by a UE, which may be considered as Figure 4 The operation 500 is complementary to the operation 400. For example, the operation 500 may be performed by a UE (eg, Figure 1 or Figure 2 UE 120) to participate in a communication with a network entity (e.g., Figure 4 Enhanced network slicing of BS 110 of operation 400).

[0071] Operations 500 begin at 502 by sending a sliced ​​service request to a network entity. At 504, the UE receives a traffic descriptor bit sequence including an application ID field from a network entity in a network sliced ​​instance. At 506, the UE decodes the traffic descriptor bit sequence to determine an encoded random number within the application ID field. At 508, the UE determines an application ID based on the random number. At 510, the UE determines an application having data to be routed to the network sliced ​​instance based on the application ID.

[0072] Figure 4 and Figure 5 The operations shown in can refer to Figure 6 In other words, Figure 6 The network entities shown in FIG. 1 (eg, base stations of an operator network) may perform Figure 4 Operation 400, and the UE may perform Figure 5 Operation 500.

[0073] As shown, the UE may determine that an application has requested a sliced ​​instance. For example, an application on the UE may indicate that the application desires an ultra-reliable low-latency connection (uRLLC) network sliced ​​service.

[0074] The UE may send a request to a remote server (e.g., operated by a vendor of the requested application), and the remote server may forward the request to the network (operator). In some cases, the request received by the network may include public land mobile network (PLMN) information and / or information about the application. In some aspects, the request may be sent via the UE's default data service (DDS).

[0075] As shown, the network (operator) can generate a random number token (e.g., a hexadecimal random number). The network can use the service descriptor bit sequence to encode the application ID field about the application with a randomly generated number. The network can send the service descriptor bit sequence to a remote server, and the remote server can forward the service descriptor bit sequence to the UE at 618 to configure the UE to update the UE routing policy (USRP).

[0076] As shown, the UE can update the USRP based on the receipt of the random number token. In some cases, the application ID corresponding to the random number token is the same as the random number token "OS App Id" held by the application instance. For example, the UE can match the random number token with the application ID of the application. If the match is successful, the UE can route the application to the network slicing instance (e.g., uRLLC network slicing instance).

[0077] The method disclosed herein includes one or more steps or actions for implementing the method. Without departing from the scope of the claims, the method steps and / or actions can be interchangeable with each other. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.

[0078] As used herein, a phrase referring to "at least one" of a series of items refers to any combination of those items (including single members). As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0079] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), discovering, etc. In addition, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determining" may include solving, selecting, choosing, establishing, etc.

[0080] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope of the language of the claims, wherein, unless otherwise specified, the elements mentioned in the singular are not intended to represent "one and only one", but to represent "one or more". Unless otherwise expressly stated, the term "some" refers to one or more. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure are known or will be known to those of ordinary skill in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. The elements of the claims should not be interpreted according to the terms of 35 U.S.C. § 112 (f), unless the element is explicitly stated using the phrase "a component for...", or in the case of a method claim, the element is stated using the phrase "a step for...".

[0081] The various operations of the above methods may be performed by any suitable means capable of performing the corresponding functions. These means may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the figures, those operations may have corresponding like numbered counterparts plus functional components. For example, Figure 2 The processors 258, 264, and 266 of the UE 120a and / or the controller / processor 280 and / or the processors 220, 230, 238 and / or the controller / processor 240 of the BS 110a shown in FIG. 1 may be configured to perform Figure 4 Operation 400 and Figure 5 operation.

[0082] The components for receiving may include Figure 2 The transceiver, receiver or at least one antenna and at least one receiving processor shown in the figure. The component for transmitting, the component for sending or the component for outputting may include Figure 2 The transceiver, transmitter or at least one antenna and at least one transmit processor shown in the figure, the means for determining, the means for encoding, the means for generating and the means for decoding may include a processing system, which may include one or more processors, such as Figure 2The processors 258, 264, and 266 and / or the controller / processor 280 of the UE 120a and / or the processors 220, 230, 238 and / or the controller / processor 240 of the BS 110a are shown.

[0083] In some cases, a device may have an interface (components for outputting) a frame for transmission. For example, a processor may output a frame to a radio frequency (RF) front end via a bus interface for transmission. Similarly, a device may have an interface (components for obtaining) for obtaining a frame received from another device, as opposed to actually receiving the frame. For example, a processor may obtain (or receive) a frame from an RF front end via a bus interface for reception.

[0084] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed with 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 (PLD), 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 alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, 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.

[0085] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. The bus may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus may link various circuits (including processors, machine-readable media, and bus interfaces) together. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement signal processing functions at the physical (PHY) layer. In the case of a user terminal 120 (see Figure 1 ), a user interface (e.g., keyboard, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits (such as timing sources, peripherals, voltage regulators, power management circuits, etc.), which are well known in the art and therefore will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can execute software. Those skilled in the art will recognize how best to implement the described functions of the processing system based on the specific application and the overall design constraints imposed on the entire system.

[0086] If implemented in software, the function may be stored on a computer-readable medium as one or more instructions or codes or transmitted as one or more instructions or codes. Whether referred to as software, firmware, middleware, microcode, hardware description language or other, software should be broadly interpreted as representing instructions, data or any combination thereof. Computer-readable media include both computer storage media and communication media, and the communication media include any media that helps to transfer a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions separated from a wireless node stored thereon, all of which may be accessed by the processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor (such as a case where a cache and / or a general register file may be provided). Examples of machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media or any combination thereof. The machine-readable medium may be implemented in a computer program product.

[0087] A software module may include a single instruction or multiple instructions, and may be distributed over several different code segments, between different programs, and across multiple storage media. A computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may reside in a single storage device or be distributed in multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard drive into a RAM. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by a processor. When the functions of a software module are mentioned below, it will be understood that such functions are implemented by a processor when executing instructions from the software module.

[0088] Additionally, any connection is properly termed a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave) is used, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray Optical disks, where magnetic disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include temporary computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0089] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium with instructions stored (and / or encoded) thereon, which instructions may be executed by one or more processors to perform the operations described herein, such as for performing the operations described herein and Figure 4 and Figure 5 The operations shown in the instructions.

[0090] It should also be understood that the modules and / or other appropriate components for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by a user terminal and / or base station (if applicable). For example, such a device can be coupled to a server to facilitate the delivery of components for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage component (e.g., RAM, ROM, physical storage media such as compact optical disks (CDs) or floppy disks) so that the user terminal and / or base station can obtain the various methods when the storage component is coupled to or provided to the device. In addition, any other suitable technology for providing the methods and techniques described herein to the device can be used.

[0091] It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for performing wireless communication by a network entity, comprising: Determine network slicing instances; encoding an application identification (ID) field within a service descriptor bit sequence with a random number corresponding to at least one of an application or the network slicing instance; as well as The traffic descriptor bit sequence is sent to a user equipment (UE).

2. The method according to claim 1, further comprising: receiving a sliced ​​service request from the UE; as well as In response to receiving the sliced ​​service request from the UE, the random number is generated.

3. The method according to claim 2, wherein: The sliced ​​service request indicates at least one of public land mobile network (PLMN) information or information about the application.

4. The method according to claim 2, wherein: The sliced ​​service request is received via a default data service (DDS) of the UE.

5. The method according to claim 1, wherein: The slicing instance provides ultra-reliable low-latency communication (uRLLC) service.

6. The method according to claim 1, wherein: The traffic descriptor bit sequence configures the UE to update a UE routing policy (USRP).

7. A method for performing wireless communication by a user equipment (UE), comprising: Sending a sliced ​​service request to a network entity; Receiving a traffic descriptor bit sequence including an application identification (ID) field from the network entity in the network slicing instance; decoding the traffic descriptor bit sequence to determine a random number encoded in the application ID field corresponding to at least one of an application or the network slicing instance; determining an application ID based on the random number; as well as Based on the application ID, determine the application that has data to be routed to the network sliced ​​instance.

8. The method according to claim 7, wherein: The sliced ​​service request is sent based on a request from the application.

9. The method according to claim 7, wherein: The sliced ​​service request indicates at least one of public land mobile network (PLMN) information or information about the application.

10. The method according to claim 9, wherein: The sliced ​​service request is sent via the default data service (DDS) of the UE.

11. The method according to claim 7, wherein: The slicing instance provides ultra-reliable low-latency communication (uRLLC) service.

12. The method of claim 7, further comprising updating a UE Routing Policy (USRP) based on the traffic descriptor bit sequence.

13. A network entity, comprising: A processing system configured to: Determine network slicing instances; as well as encoding an application identification (ID) field within a traffic descriptor bit sequence with a random number corresponding to at least one of an application or a network slicing instance; as well as A transmitter is configured to send the traffic descriptor bit sequence to a user equipment (UE).

14. The network entity according to claim 13, further comprising: A receiver configured to receive a sliced ​​service request from the UE, wherein: The processing system is also configured to generate the random number in response to receiving the sliced ​​service request from the UE.

15. The network entity according to claim 14, wherein: The sliced ​​service request indicates at least one of public land mobile network (PLMN) information or information about the application.

16. The network entity according to claim 14, wherein: The sliced ​​service request is received via a default data service (DDS) of the UE.

17. The network entity according to claim 13, wherein: The slicing instance provides ultra-reliable low-latency communication (uRLLC) service.

18. The network entity according to claim 13, wherein: The traffic descriptor bit sequence configures the UE to update a UE routing policy (USRP).

19. A user equipment (UE), comprising: A transmitter configured to send a sliced ​​service request to a network entity; A receiver configured to receive a traffic descriptor bit sequence including an application identification (ID) field from said network entity in a network slicing instance; and A processing system configured to: decoding the traffic descriptor bit sequence to determine a random number encoded within the application ID field corresponding to at least one of an application or the network slicing instance; determining an application ID based on the random number; as well as Based on the application ID, determine the application that has data to be routed to the network sliced ​​instance.

20. The UE according to claim 19, wherein: The sliced ​​service request is sent based on a request from the application.

21. The UE according to claim 19, wherein: The sliced ​​service request indicates at least one of public land mobile network (PLMN) information or information about the application.

22. The UE according to claim 21, wherein: The sliced ​​service request is sent via the default data service (DDS) of the UE.

23. The UE according to claim 19, wherein: The slicing instance provides ultra-reliable low-latency communication (uRLLC) service.

24. The UE of claim 19, further comprising updating a UE routing policy (USRP) based on the traffic descriptor bit sequence.

25. A network entity, comprising: A component for determining a network slicing instance; means for encoding an application identification (ID) field within a traffic descriptor bit sequence with a random number corresponding to at least one of an application or said network slicing instance; as well as Means for sending the traffic descriptor bit sequence to a user equipment (UE).

26. The network entity according to claim 25, further comprising: A component for receiving a sliced ​​service request from the UE; as well as A component for generating the random number in response to receiving the sliced ​​service request from the UE.

27. The network entity according to claim 26, wherein: The sliced ​​service request indicates at least one of public land mobile network (PLMN) information or information about the application.

28. The network entity according to claim 26, wherein: The sliced ​​service request is received via a default data service (DDS) of the UE.

29. The network entity according to claim 25, wherein: The slicing instance provides ultra-reliable low-latency communication (uRLLC) service.

30. The network entity according to claim 25, wherein: The traffic descriptor bit sequence configures the UE to update a UE routing policy (USRP).

31. A user equipment (UE), comprising: A component for sending a sliced ​​service request to a network entity; means for receiving, from said network entity in a network slicing instance, a traffic descriptor bit sequence comprising an application identification (ID) field; means for decoding the traffic descriptor bit sequence to determine a random number encoded within the application ID field corresponding to at least one of an application or the network slicing instance; means for determining an application ID based on the random number; as well as A component for determining an application having data to be routed to the network sliced ​​instance based on the application ID.

32. The UE according to claim 31, wherein: The sliced ​​service request is sent based on a request from the application.

33. The UE according to claim 31, wherein: The sliced ​​service request indicates at least one of public land mobile network (PLMN) information or information about the application.

34. The UE according to claim 33, wherein: The sliced ​​service request is sent via the default data service (DDS) of the UE.

35. The UE according to claim 31, wherein: The slicing instance provides ultra-reliable low-latency communication (uRLLC) service.

36. The UE of claim 31, further comprising updating a UE routing policy (USRP) based on the traffic descriptor bit sequence.

37. A computer-readable medium for performing wireless communications by a network entity, comprising code for performing the following steps: Determine network slicing instances; encoding an application identification (ID) field within a traffic descriptor bit sequence with a random number corresponding to at least one of an application or a network slicing instance; and The traffic descriptor bit sequence is sent to a user equipment (UE).

38. A computer-readable medium for performing wireless communications by a user equipment (UE), comprising code that can perform the following steps: Sending a sliced ​​service request to a network entity; receiving a traffic descriptor bit sequence including an application identification (ID) field from a network entity in the network slicing instance; decoding the traffic descriptor bit sequence to determine a random number encoded within the application ID field corresponding to at least one of an application or the network slicing instance; determining an application ID based on the random number; as well as Based on the application ID, determine the application that has data to be routed to the network sliced ​​instance.

39. An apparatus for wireless communication performed by a network entity, comprising: A processing system configured to: Determine network slicing instances; as well as encoding an application identification (ID) field within a traffic descriptor bit sequence with a random number corresponding to at least one of an application or a network slicing instance; as well as An interface is configured to output the traffic descriptor bit sequence for sending to a user equipment (UE).

40. An apparatus for performing wireless communications by a user equipment (UE), comprising: interface, which is configured as: Output a sliced ​​service request for sending to a network entity; as well as Obtaining a service descriptor bit sequence including an application identification (ID) field from the network entity in the network slicing instance; as well as A processing system configured to: decoding the traffic descriptor bit sequence to determine a random number encoded within the application ID field corresponding to at least one of an application or the network slicing instance; determining an application ID based on the random number; as well as Based on the application ID, determine the application that has data to be routed to the network sliced ​​instance.

Images