WO2022052037A1

WO2022052037A1 - Configuring route selection policies

Info

Publication number: WO2022052037A1
Application number: PCT/CN2020/114780
Authority: WO
Inventors: Nan Zhang; Yongjun XU
Original assignee: Qualcomm Incorporated
Priority date: 2020-09-11
Filing date: 2020-09-11
Publication date: 2022-03-17

Abstract

Methods, systems, and devices for wireless communications are described. In some wireless communications systems, a user equipment (UE) may identify an application at the UE that is configured to participate in data communications with a network in accordance with a route selection policy. In order to establish a data connection associated with the application, the UE may transmit a request to the network for the route selection policy associated with the application. The UE may transmit the request as part of a registration procedure, as part of a UE configuration update procedure, in accordance with a periodicity for route selection policy requests, or a combination thereof. In response to the request, the UE may receive an indication of the route selection policy associated with the application and may establish the data connection in accordance with the route selection policy.

Description

CONFIGURING ROUTE SELECTION POLICIES

FIELD OF TECHNOLOGY

The following relates to wireless communications, including configuring route selection policies.

BACKGROUND

Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the 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, LTE-Advanced (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 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) . A wireless multiple-access communications system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .

In some wireless communications system, a UE may have one or more applications that may each involve communications with a network. The UE may connect to the network in order to allow the application to communicate with the network, where the network connection is governed by a UE route selection policy (URSP) that is indicated to the UE by the network. Improved techniques for indicating URSPs associated with applications may be desirable.

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support configuring route selection policies. Generally, the described techniques relate to a network providing user equipment (UE) route selection policies (URSPs) to UEs. That is, a UE may communicate data for an application according to a URSP that is associated with that application. In examples described herein, the UE may identify applications at the UE that are configured to participate in data communications with the network in accordance with a URSP and may transmit requests for the URSP to the network. For example, the UE may transmit a request for the URSP as part of a registration procedure, as part of a UE configuration update procedure, or according to a defined periodicity for requesting URSPs. In response to the URSP request, the network may transmit an indication of the URSP associated with the application to the UE. The UE may then establish a data connection with the network in accordance with the indicated URSP.

A method of wireless communication at a UE is described. The method may include identifying that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy, transmitting, to the network, a request for the route selection policy associated with the application, receiving, in response to the request, an indication of the route selection policy associated with the application, and establishing a data connection in accordance with the route selection policy.

An apparatus for wireless communication at a UE is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy, transmit, to the network, a request for the route selection policy associated with the application, receive, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection in accordance with the route selection policy.

Another apparatus for wireless communication at a UE is described. The apparatus may include means for identifying that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy, transmitting, to the network, a request for the route selection policy associated with the application, receiving, in response to the request, an indication of the route selection policy associated with the application, and establishing a data connection in accordance with the route selection policy.

A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy, transmit, to the network, a request for the route selection policy associated with the application, receive, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection in accordance with the route selection policy.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the request further may include operations, features, means, or instructions for transmitting the request as part of a registration procedure to obtain one or more network slicing instances on which the UE may be allowed to communicate.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the request further may include operations, features, means, or instructions for transmitting the request as part of a UE configuration update procedure.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the request further may include operations, features, means, or instructions for transmitting the request in accordance with a periodicity for route selection policy requests.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the request further may include operations, features, means, or instructions for including an identifier of the application within the request for the route selection policy associated with the application.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the request further may include operations, features, means, or instructions for including, in the request for the route selection policy, a set of additional identifiers corresponding to additional applications present at the UE.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for storing, at the UE, the indication of the route selection policy associated with the application, where establishing the data connection may be based on the storing.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, establishing the data connection with the network further may include operations, features, means, or instructions for establishing a protocol data unit session with the network in accordance with the route selection policy.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the route selection policy may be associated with a network slicing instance.

A method of wireless communication at a wireless network device is described. The method may include receiving, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy, transmitting, in response to the request, an indication of the route selection policy associated with the application, and establishing a data connection with the UE in accordance with the route selection policy.

An apparatus for wireless communication at a wireless network device is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy, transmit, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection with the UE in accordance with the route selection policy.

Another apparatus for wireless communication at a wireless network device is described. The apparatus may include means for receiving, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy, transmitting, in response to the request, an indication of the route selection policy associated with the application, and establishing a data connection with the UE in accordance with the route selection policy.

A non-transitory computer-readable medium storing code for wireless communication at a wireless network device is described. The code may include instructions executable by a processor to receive, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy, transmit, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection with the UE in accordance with the route selection policy.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the request further may include operations, features, means, or instructions for receiving the request as part of a registration procedure to obtain one or more network slicing instances on which the UE may be allowed to communicate.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the request further may include operations, features, means, or instructions for receiving the request as part of a UE configuration update procedure.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the request further may include operations, features, means, or instructions for receiving the request according to in accordance with a periodicity for route selection policy requests.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the request further may include operations, features, means, or instructions for receiving an identifier of the application within the request for the route selection policy associated with the application.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the request further may include operations, features, means, or instructions for receiving, in the request for the route selection policy, a set of additional identifiers corresponding to additional applications present at the UE.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, establishing the data connection with the UE further may include operations, features, means, or instructions for establishing a protocol data unit session with the network in accordance with the route selection policy.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system for wireless communications that supports configuring route selection policies in accordance with aspects of the present disclosure.

FIG. 2 illustrates an example of a wireless communications system that supports configuring route selection policies in accordance with aspects of the present disclosure.

FIG. 3 illustrates an example of a process flow that supports configuring route selection policies in accordance with aspects of the present disclosure.

FIGs. 4 and 5 show block diagrams of devices that support configuring route selection policies in accordance with aspects of the present disclosure.

FIG. 6 shows a block diagram of a UE coding manager that supports configuring route selection policies in accordance with aspects of the present disclosure.

FIG. 7 shows a diagram of a system including a device that supports configuring route selection policies in accordance with aspects of the present disclosure.

FIGs. 8 and 9 show block diagrams of devices that support configuring route selection policies in accordance with aspects of the present disclosure.

FIG. 10 shows a block diagram of a communications manager that supports configuring route selection policies in accordance with aspects of the present disclosure.

FIG. 11 shows a diagram of a system including a device that supports configuring route selection policies in accordance with aspects of the present disclosure.

FIGs. 12 and 13 show flowcharts illustrating methods that support configuring route selection policies in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

In some wireless communication systems, a user equipment (UE) may communicate application data with a network according to a UE route selection policy (URSP) . That is, the URSP may govern access policies for communicating with the network for that application. Prior to a UE establishing a data connection associated with an application (e.g., for communicating application data with the network) , the UE may receive an indication of a URSP to use for that application from the network. In some cases, the network may indicate URSPs to each UE being served by the network (e.g., hundreds or thousands of UEs) and may indicate URSPs for each application at each UE (e.g., hundreds or thousands of applications at each UE) . Although the network may track and manage the URSPs for each application of each UE being served by the network, doing so may be impractical.

In the example of wireless communication systems as disclosed herein, the network may indicate URSPs to a UE in response to receiving a request for the URSP. That is, each UE may identify applications at the UE that are configured for data communications with the network in accordance with a URSP and may transmit requests to the network for URSPs associated with the identified applications. In response to a request for a URSP, the network may indicate a URSP associated with the application to the UE. The UE may then establish a data connection with the network in accordance with the indicated URSP.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described in the context of a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to configuring route selection policies.

FIG. 1 illustrates an example of a wireless communications system 100 that supports configuring route selection policies in accordance with aspects of the present disclosure. The wireless communications 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 communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communications 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.

The base stations 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may be devices in different forms or having different capabilities. The base stations 105 and the UEs 115 may wirelessly communicate 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 station 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a base station 105 and a UE 115 may support the communication of signals according to one or more radio access technologies.

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

The base stations 105 may communicate with the core network 130, or with one another, or both. For example, the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an S1, N2, N3, or other interface) . The base stations 105 may communicate with one another over the backhaul links 120 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations 105) , or indirectly (e.g., via core network 130) , or both. In some examples, the backhaul links 120 may be or include one or more wireless links.

One or more of the base stations 105 described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a Home NodeB, a Home eNodeB, or other suitable terminology.

A 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 terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A 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, a 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 communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

The UEs 115 and the base stations 105 may wirelessly communicate with one another via one or more communication links 125 over 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 links 125. For example, a carrier used for a communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP) ) that is operated 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 that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.

Signal waveforms transmitted over a carrier may be made up of 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 employing MCM techniques, a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and 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 coding rate of the modulation scheme, or both) . Thus, the more resource elements that a UE 115 receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE 115. A wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams) , and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE 115.

The time intervals for the base stations 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of T _s=1/ (Δf _max·N _f) seconds, where Δf _max may represent the maximum supported subcarrier spacing, and N _f may represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource 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) .

Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems 100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N _f) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications 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 communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .

Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. 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 the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple 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 a number of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.

In some examples, a base station 105 may be movable and therefore provide communication coverage for a moving geographic coverage area 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, the overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications. The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions) . Ultra-reliable communications 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, mission critical, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE 115 may also be able to communicate directly with other UEs 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 communications may be within the 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 a base station 105 or be otherwise unable to receive transmissions from a base station 105. In some examples, groups of the UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group. In some examples, a base station 105 facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs 115 without the involvement of a base station 105.

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 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to the network operators IP services 150. The network operators IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service. The core network 130 may additionally include a point coordination function (PCF) that indicates, to each UE 115 being served by the core network 130, which URSP to use for routing traffic associated with an application at the UE 115.

Some of the network devices, such as a base station 105, may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC) . Each access network entity 140 may communicate with the UEs 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs) . Each access network transmission entity 145 may include one or more antenna panels. In some configurations, 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 consolidated into a single network device (e.g., a base station 105) .

The wireless communications system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communications system 100 may employ License 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 unlicensed radio frequency spectrum bands, devices such as the base stations 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA) . Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A base station 105 or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may 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, antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations. A base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.

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 the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .

In wireless communications system 100, a UE 115 may communicate application data with the core network 130 (e.g., via a base station 105) according to a URSP. Prior to a UE 115 establishing a data connection associated with an application (e.g., for communicating application data with the core network 130) , the UE 115 may receive an indication of a URSP to use for that application from the PCF of the core network 130. In some cases, the PCF may indicate URSPs to each UE 115 being served by the core network 130 (e.g., hundreds or thousands of UEs 115) and may indicate URSPs for each application at each UE 115 (e.g., hundreds or thousands of applications at each UE) . Although the PCF may track and manage the URSPs for each application of each UE 115 being served by the core network 130, doing so may be impractical. For example, it may be impractical for the PCF to track applications at a UE 115 that are installed, removed, or updated while the UE 115 is communicating with the core network 130 via one or more base stations 105.

In the example of wireless communications system 100, the PCF of the core network 130 may indicate URSPs to a UE 115 in response to receiving a request for the URSP. That is, each UE 115 may identify applications at the UE 115 that are configured for data communications with the core network 130 in accordance with a URSP and may transmit requests to the core network 130 for URSPs associated with the identified applications. In response to a request for a URSP, the core network 130 may indicate a URSP associated with the application to the UE 115. The UE 115 may then establish a data connection with the core network 130 in accordance with the indicated URSP.

FIG. 2 illustrates an example of a wireless communications system 200 that supports configuring route selection policies in accordance with aspects of the present disclosure. In some examples, the wireless communications system 200 may implement aspects of wireless communications system 100. The wireless communications system 200 may include a UE 115-a and a base station 105-a, which may be examples of a UE 115 and a base station 105, respectively, as described with reference to FIG. 1.

The UE 115-a may be in communication with the base station 105-a via the communication link 205. In some cases, the base station 105-a may provide a link to a network (e.g., a core network as described with reference to FIG. 1) to the UE 115-a. The UE 115-a may include one or more applications 225 that are configured to participate in data communications with the network via the base station 105-a in accordance with a URSP. For example, the application 225-a may be configured to participate in data communications with the network via the base station 105-a in accordance with a first URSP and the application 225-b may be configured to participate in data communications with the network via the base station 105-a in accordance with a second URSP.

The UE 115-a may perform a registration procedure (e.g., a network slicing registration procedure) with the base station 105-a. That is, the wireless communications system 200 may support one or multiple network slices over one or multiple radio access technologies. Each network slice may provide specific network capabilities and network characteristics. For example, a network slice may include dedicated or shared resources of a wireless communications system 200 in terms of processing power, storage, and bandwidth for a particular service or application. A network slice may also span across multiple network devices, for example, a base station 105-a, a network function of a core network, etc. A network function may be a logical node, which may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof, to support network slices in the wireless communications system 200. During the registration procedure, the network may indicate, via the base station 105-a, one or more network slicing instances that the UE 115-a may utilize to communicate with the network (e.g., via single-network slice selection assistance information (S-NSSAI) ) .

Prior to establishing a data connection for an application 225 (e.g., via one of the network slicing instances that are useable or allowable by the UE 115-a) , the UE 115-a may determine which URSP to use for the application 225. The UE 115-a may transmit a URSP request 210 to the base station 105-a requesting an indication of which URSP to use for an application 225 at the UE 115-a. In some cases, the UE 115-a may transmit the URSP request 210 as part of the registration procedure. In some other cases, the UE 115-a may transmit the URSP request 210 as part of a UE 115-a configuration updating procedure (e.g., during which a configuration of the UE 115-a may be updated by the network via the base station 105-a) .

For example, the UE 115-a may transmit the URSP request 210 requesting an indication (e.g., from the network) of which URSP to use for the application 225-b. In some cases, the UE 115-a may transmit a single URSP request 210 requesting an indication of which URSPs to use for more than one application 225 (e.g., for two applications 225, for three applications 225, for four applications 225) . For example, the URSP request 210 may request an indication of which URSP to use for the application 225-a and the application 225-b.

The UE 115-a may include an application identifier in the URSP request 210 indicating which application 225 the URSP request 210 is associated with. For example, if the UE 115-a transmits the URSP request 210 for the application 225-a, the UE 115-a may include an application identifier associated with the application 225-a within the URSP request 210. Additionally, if the UE 115-a transmits the URSP request 210 requesting an indication of which URSP to use for the application 225-a and the application 225-b, the URSP request 210 may include application identifiers associated with both the application 225-a and the application 225-b. The UE 115-a may additionally include an indication of a precedence value (e.g., a rule precedence value) associated with each application and a traffic descriptor (e.g., indicating that the requested URSP is associated with application traffic) within the URSP request 210.

In response to the URSP indication 215, the network may transmit a URSP indication 215 to the UE 115-a via the base station 105-a. The URSP indication 215 may indicate a URSP that the UE 115-a is to use for each of the applications 225 indicated within the URSP request 210. For example, if the URSP request 210 indicated a request for a URSP associated with the application 225-a, the URSP indication 215 may indicate a URSP for the same application 225-a. If the URSP request 210 indicated more than one application 225, the URSP indication 215 may also indicate more than one URSP (e.g., for each of the more than one applications 225) . In some cases, the URSP indication 215 may include additional information associated with the indicated URSP. For example, the URSP indication 215 may include one or more of an indication of a route selection descriptor precedence, a network slicing instance, an indication of a session and service continuity, an indication of the data network name selection, and an access type preference.

The UE 115-a may store, at the UE 115-a, an indication of the URSP indicated by the URSP indication 215. For example, the UE 115-a may store the indication of the URSP within a cache at the UE 115-a. Thus, the UE 115-a may utilize the URSP to route data associated with the application 225 in the future without having to transmit an additional URSP request 210 any time the application 225-a communicates with the network via the base station 105-a. In some cases, the UE 115-a may be configured to periodically request an updated URSP for application 225 (e.g., even in a case that the UE 115-a has stored an indicated URSP associated with the application 225 at the UE 115-a) . For example, the UE 115-a may be configured to transmit a request for an update to the URSP associated with application 225-a according to a first periodicity.

After the UE 115-a receives the URSP indication 215 indicating a URSP associated with at least one of the applications 225 at the UE 115-a, the UE 115-a ay establish a data connection with the base station 105-a in accordance with the URSP. That is, the UE 115-a may establish a protocol data unit (PDU) session with the network (e.g., via the base station 105-a) for routing data between the network and the application 225. The UE 115-a may then route communications 220 associated with the application 225 between the base station 105-a and the application 225 in accordance with the URSP.

FIG. 3 illustrates an example of a process flow 300 that supports configuring route selection policies in accordance with aspects of the present disclosure. In some examples, process flow 300 may implement aspects of

wireless communication systems

100 and 200. For example, the UE 115-b may be an example of the UEs 115 as described with respect to FIGs. 1 and 2. Additionally, the base station 105-b may be an example of the base stations 15 as described with respect to FIGs. 1 and 2.

At 305, the UE 115-b may identify that the UE 115-b includes an application which is configured to participate in data communications with a network (e.g., via the base station 105-b or another similar network node) in accordance with a route selection policy (e.g., a URSP) .

At 310, the UE 115-b may transmit, to the network via the base station 105-b, a request for the route selection policy (e.g., a URSP request) associated with the application. In some cases, the UE 115-b may transmit the URSP request as part of a registration procedure to obtain one or more network slicing instances on which the UE 115-b is allowed to communicate. In some other cases, the UE 115-b may transmit the URSP request as part of a UE 115-b configuration update procedure. Additionally or alternatively, the UE 115-b may transmit the URSP request in accordance with a periodicity for URSP requests.

At 315, the base station 105-b may transmit, in response to the request, an indication of the route selection policy (e.g., a URSP indication) associated with the application. For example, a PCF at the network may identify the route selection policy associated with the application and may transmit an indication of the identified route selection policy to the UE 115-b via the base station 105-b.

At 320, the UE 115-b may store the indication of the route selection policy associated with the application (e.g., at a cache of the UE 115-b) .

At 325, the UE 115-b may establish a data connection in accordance with the route selection policy. For example, the UE 115-b may establish a PDU session with the network via the base station 105-a in accordance with the URSP.

At 33, the UE 115-b may transmit, after establishing the data connection at 325, a request for an update to the route selection policy associated with the application in accordance with the periodicity. In some cases, the periodicity may be associated with the application (e.g., defined for the application) . Additionally or alternatively, the periodicity may be based on the URSP associated with the application, based on the network slicing instance associated with the established data connection, or a combination thereof.

FIG. 4 shows a block diagram 400 of a device 405 that supports configuring route selection policies in accordance with aspects of the present disclosure. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a UE coding manager 415, and a transmitter 420. The device 405 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 410 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 configuring route selection policies, etc. ) . Information may be passed on to other components of the device 405. The receiver 410 may be an example of aspects of the transceiver 720 described with reference to FIG. 7. The receiver 410 may utilize a single antenna or a set of antennas.

The UE coding manager 415 may identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy, transmit, to the network, a request for the route selection policy associated with the application, receive, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection in accordance with the route selection policy. The UE coding manager 415 may be an example of aspects of the UE coding manager 710 described herein.

The UE coding manager 415, or its sub-components, may be implemented in hardware, 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 UE coding manager 415, or its sub-components may be executed 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The UE coding manager 415, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the UE coding manager 415, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the UE coding manager 415, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

The transmitter 420 may transmit signals generated by other components of the device 405. In some examples, the transmitter 420 may be collocated with a receiver 410 in a transceiver module. For example, the transmitter 420 may be an example of aspects of the transceiver 720 described with reference to FIG. 7. The transmitter 420 may utilize a single antenna or a set of antennas.

FIG. 5 shows a block diagram 500 of a device 505 that supports configuring route selection policies in accordance with aspects of the present disclosure. The device 505 may be an example of aspects of a device 405, or a UE 115 as described herein. The device 505 may include a receiver 510, a UE coding manager 515, and a transmitter 540. The device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

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 configuring route selection policies, etc. ) . Information may be passed on to other components of the device 505. The receiver 510 may be an example of aspects of the transceiver 720 described with reference to FIG. 7. The receiver 510 may utilize a single antenna or a set of antennas.

The UE coding manager 515 may be an example of aspects of the UE coding manager 415 as described herein. The UE coding manager 515 may include an application identifier 520, a request transmitter 525, an indication manager 530, and a data connection manager 535. The UE coding manager 515 may be an example of aspects of the UE coding manager 710 described herein.

The application identifier 520 may identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy.

The request transmitter 525 may transmit, to the network, a request for the route selection policy associated with the application.

The indication manager 530 may receive, in response to the request, an indication of the route selection policy associated with the application.

The data connection manager 535 may establish a data connection in accordance with the route selection policy.

The transmitter 540 may transmit signals generated by other components of the device 505. In some examples, the transmitter 540 may be collocated with a receiver 510 in a transceiver module. For example, the transmitter 540 may be an example of aspects of the transceiver 720 described with reference to FIG. 7. The transmitter 540 may utilize a single antenna or a set of antennas.

FIG. 6 shows a block diagram 600 of a UE coding manager 605 that supports configuring route selection policies in accordance with aspects of the present disclosure. The UE coding manager 605 may be an example of aspects of a UE coding manager 415, a UE coding manager 515, or a UE coding manager 710 described herein. The UE coding manager 605 may include an application identifier 610, a request transmitter 615, an indication manager 620, and a data connection manager 625. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The application identifier 610 may identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy. In some cases, the route selection policy is associated with a network slicing instance.

The request transmitter 615 may transmit, to the network, a request for the route selection policy associated with the application. In some examples, the request transmitter 615 may transmit the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate. In some cases, the request transmitter 615 may transmit the request as part of a UE configuration update procedure. In some instances, the request transmitter 615 may transmit the request in accordance with a periodicity for route selection policy requests. In some examples, the request transmitter 615 may transmit, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity. In some cases, the request transmitter 615 may include an identifier of the application within the request for the route selection policy associated with the application. In some instances, the request transmitter 615 may include, in the request for the route selection policy, a set of additional identifiers corresponding to additional applications present at the UE.

The indication manager 620 may receive, in response to the request, an indication of the route selection policy associated with the application. In some examples, the indication manager 620 may store, at the UE, the indication of the route selection policy associated with the application, where establishing the data connection is based on the storing.

The data connection manager 625 may establish a data connection in accordance with the route selection policy. In some examples, the data connection manager 625 may establish a protocol data unit session with the network in accordance with the route selection policy.

FIG. 7 shows a diagram of a system 700 including a device 705 that supports configuring route selection policies in accordance with aspects of the present disclosure. The device 705 may be an example of or include the components of device 405, device 505, or a UE 115 as described herein. The device 705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a UE coding manager 710, an I/O controller 715, a transceiver 720, an antenna 725, memory 730, and a processor 740. These components may be in electronic communication via one or more buses (e.g., bus 745) .

The UE coding manager 710 may identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy, transmit, to the network, a request for the route selection policy associated with the application, receive, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection in accordance with the route selection policy.

The I/O controller 715 may manage input and output signals for the device 705. The I/O controller 715 may also manage peripherals not integrated into the device 705. In some cases, the I/O controller 715 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 715 may utilize an operating system such as

or another known operating system. In other cases, the I/O controller 715 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 715 may be implemented as part of a processor. In some cases, a user may interact with the device 705 via the I/O controller 715 or via hardware components controlled by the I/O controller 715.

The transceiver 720 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver 720 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 720 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

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

The memory 730 may include random-access memory (RAM) and read-only memory (ROM) . The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 730 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor 740 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, the processor 740 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting configuring route selection policies) .

The code 735 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code 735 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 735 may not be directly executable by the processor 740 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

FIG. 8 shows a block diagram 800 of a device 805 that supports configuring route selection policies in accordance with aspects of the present disclosure. The device 805 may be an example of aspects of a base station 105 as described herein. The device 805 may include a receiver 810, a communications manager 815, and a transmitter 820. The device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 810 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 configuring route selection policies, etc. ) . Information may be passed on to other components of the device 805. The receiver 810 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11. The receiver 810 may utilize a single antenna or a set of antennas.

The communications manager 815 may receive, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy, transmit, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection with the UE in accordance with the route selection policy. The communications manager 815 may be an example of aspects of the communications manager 1110 described herein.

The communications manager 815, or its sub-components, may be implemented in hardware, 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 communications manager 815, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC) , a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The communications manager 815, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the communications manager 815, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the communications manager 815, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

The transmitter 820 may transmit signals generated by other components of the device 805. In some examples, the transmitter 820 may be collocated with a receiver 810 in a transceiver module. For example, the transmitter 820 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11. The transmitter 820 may utilize a single antenna or a set of antennas.

FIG. 9 shows a block diagram 900 of a device 905 that supports configuring route selection policies in accordance with aspects of the present disclosure. The device 905 may be an example of aspects of a device 805, or a base station 105 as described herein. The device 905 may include a receiver 910, a communications manager 915, and a transmitter 935. The device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

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 configuring route selection policies, etc. ) . Information may be passed on to other components of the device 905. The receiver 910 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11. The receiver 910 may utilize a single antenna or a set of antennas.

The communications manager 915 may be an example of aspects of the communications manager 815 as described herein. The communications manager 915 may include a request receiver 920, an indication transmitter 925, and a data connection manager 930. The communications manager 915 may be an example of aspects of the communications manager 1110 described herein.

The request receiver 920 may receive, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy.

The indication transmitter 925 may transmit, in response to the request, an indication of the route selection policy associated with the application.

The data connection manager 930 may establish a data connection with the UE in accordance with the route selection policy.

The transmitter 935 may transmit signals generated by other components of the device 905. In some examples, the transmitter 935 may be collocated with a receiver 910 in a transceiver module. For example, the transmitter 935 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11. The transmitter 935 may utilize a single antenna or a set of antennas.

FIG. 10 shows a block diagram 1000 of a communications manager 1005 that supports configuring route selection policies in accordance with aspects of the present disclosure. The communications manager 1005 may be an example of aspects of a communications manager 815, a communications manager 915, or a communications manager 1110 described herein. The communications manager 1005 may include a request receiver 1010, an indication transmitter 1015, and a data connection manager 1020. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The request receiver 1010 may receive, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy. In some examples, the request receiver 1010 may receive the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate. In some cases, the request receiver 1010 may receive the request as part of a UE configuration update procedure. In some instances, the request receiver 1010 may receive the request according to in accordance with a periodicity for route selection policy requests.

In some examples, the request receiver 1010 may receive, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity. In some cases, the request receiver 1010 may receive an identifier of the application within the request for the route selection policy associated with the application. In some instances, the request receiver 1010 may receive, in the request for the route selection policy, a set of additional identifiers corresponding to additional applications present at the UE. In some examples, the route selection policy is associated with a network slicing instance.

The indication transmitter 1015 may transmit, in response to the request, an indication of the route selection policy associated with the application.

The data connection manager 1020 may establish a data connection with the UE in accordance with the route selection policy. In some examples, the data connection manager 1020 may establish a protocol data unit session with the network in accordance with the route selection policy.

FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports configuring route selection policies in accordance with aspects of the present disclosure. The device 1105 may be an example of or include the components of device 805, device 905, or a base station 105 as described herein. The device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 1110, a network communications manager 1115, a transceiver 1120, an antenna 1125, memory 1130, a processor 1140, and an inter-station communications manager 1145. These components may be in electronic communication via one or more buses (e.g., bus 1150) .

The communications manager 1110 may receive, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy, transmit, in response to the request, an indication of the route selection policy associated with the application, and establish a data connection with the UE in accordance with the route selection policy.

The network communications manager 1115 may manage communications with the core network (e.g., via one or more wired backhaul links) . For example, the network communications manager 1115 may manage the transfer of data communications for client devices, such as one or more UEs 115.

The transceiver 1120 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver 1120 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1120 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

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

The memory 1130 may include RAM, ROM, or a combination thereof. The memory 1130 may store computer-readable code 1135 including instructions that, when executed by a processor (e.g., the processor 1140) cause the device to perform various functions described herein. In some cases, the memory 1130 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor 1140 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, the processor 1140 may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting configuring route selection policies) .

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

The code 1135 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code 1135 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

FIG. 12 shows a flowchart illustrating a method 1200 that supports configuring route selection policies in accordance with aspects of the present disclosure. The operations of method 1200 may be implemented by a UE 115 or its components as described herein. For example, the operations of method 1200 may be performed by a UE coding manager as described with reference to FIGs. 4 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.

At 1205, the UE may identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy. The operations of 1205 may be performed according to the methods described herein. In some examples, aspects of the operations of 1205 may be performed by an application identifier as described with reference to FIGs. 4 through 7.

At 1210, the UE may transmit, to the network, a request for the route selection policy associated with the application. The operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operations of 1210 may be performed by a request transmitter as described with reference to FIGs. 4 through 7.

At 1215, the UE may receive, in response to the request, an indication of the route selection policy associated with the application. The operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operations of 1215 may be performed by an indication manager as described with reference to FIGs. 4 through 7.

At 1220, the UE may establish a data connection in accordance with the route selection policy. The operations of 1220 may be performed according to the methods described herein. In some examples, aspects of the operations of 1220 may be performed by a data connection manager as described with reference to FIGs. 4 through 7.

FIG. 13 shows a flowchart illustrating a method 1300 that supports configuring route selection policies in accordance with aspects of the present disclosure. The operations of method 1300 may be implemented by a base station 105 or its components as described herein. For example, the operations of method 1300 may be performed by a communications manager as described with reference to FIGs. 8 through 11. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.

At 1305, the base station may receive, from a UE, a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy. 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 by a request receiver as described with reference to FIGs. 8 through 11.

At 1310, the base station may transmit, in response to the request, an indication of the route selection policy associated with the application. 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 by an indication transmitter as described with reference to FIGs. 8 through 11.

At 1315, the base station may establish a data connection with the UE in accordance with the route selection policy. The operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be performed by a data connection manager as described with reference to FIGs. 8 through 11.

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

Example 1: A method for wireless communication at a UE, comprising: identifying that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy; transmitting, to the network, a request for the route selection policy associated with the application; receiving, in response to the request, an indication of the route selection policy associated with the application; and establishing a data connection in accordance with the route selection policy.

Example 2: The method of example 1, wherein transmitting the request further comprises: transmitting the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.

Example 3: The method any of examples 1 or 2, wherein transmitting the request further comprises: transmitting the request as part of a UE configuration update procedure.

Example 4: The method of examples 1 to 3, wherein transmitting the request further comprises: transmitting the request in accordance with a periodicity for route selection policy requests.

Example 5: The method of any of examples 1 to 4, further comprising: transmitting, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.

Example 6: The method of any of examples 1 to 5, wherein transmitting the request further comprises: including an identifier of the application within the request for the route selection policy associated with the application.

Example 7: The method of any of examples 1 to 6, wherein transmitting the request further comprises: including, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.

Example 8: The method of any of claims 1 to 7, further comprising: storing, at the UE, the indication of the route selection policy associated with the application, wherein establishing the data connection is based at least in part on the storing.

Example 9: The method of any of claims 1 to 8, wherein establishing the data connection with the network further comprises: establishing a protocol data unit session with the network in accordance with the route selection policy.

Example 10: The method of any of claims 1 to 9, wherein the route selection policy is associated with a network slicing instance.

Example 11: An apparatus for wireless communications comprising a processor; memory in electronic communication with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of examples 1 to 10.

Example 12: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of examples 1 to 10.

Example 13: An apparatus, comprising means for performing the method of any of examples 1 to 10.

Example 14: A method for wireless communication at a wireless network device, comprising: receiving, from a user equipment (UE) , a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy; transmitting, in response to the request, an indication of the route selection policy associated with the application; and establishing a data connection with the UE in accordance with the route selection policy.

Example 15: The method of example 14, wherein receiving the request further comprises: receiving the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.

Example 16: The method of examples 14 and 15, wherein receiving the request further comprises: receiving the request as part of a UE configuration update procedure.

Example 17: The method of examples 14 to 16, wherein receiving the request further comprises: receiving the request according to in accordance with a periodicity for route selection policy requests.

Example 18: The method of examples 14 to 17, further comprising: receiving, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.

Example 19: The method of examples 14 to 18, wherein receiving the request further comprises: receiving an identifier of the application within the request for the route selection policy associated with the application.

Example 20: The method of examples 14 to 19, wherein receiving the request further comprises: receiving, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.

Example 21: The method of examples 14 to 20, wherein establishing the data connection with the UE further comprises: establishing a protocol data unit session with the network in accordance with the route selection policy.

Example 22: The method of examples 14 to 21, wherein the route selection policy is associated with a network slicing instance.

Example 23: An apparatus for wireless communications comprising a processor; memory in electronic communication with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of examples 14 to 22.

Example 24: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of examples 14 to 22.

Example 25: An apparatus, comprising means for performing the method of any of examples 14 to 22.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications 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, as well as other systems and radio technologies not explicitly mentioned herein.

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

The various illustrative blocks and components described in connection 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. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .

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 over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc 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.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration, ” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

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

Claims

A method for wireless communication at a user equipment (UE) , comprising:

identifying that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy;

transmitting, to the network, a request for the route selection policy associated with the application;

receiving, in response to the request, an indication of the route selection policy associated with the application; and

establishing a data connection in accordance with the route selection policy.
The method of claim 1, wherein transmitting the request further comprises:

transmitting the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The method of claim 1, wherein transmitting the request further comprises:

transmitting the request as part of a UE configuration update procedure.
The method of claim 1, wherein transmitting the request further comprises:

transmitting the request in accordance with a periodicity for route selection policy requests.
The method of claim 4, further comprising:

transmitting, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The method of claim 1, wherein transmitting the request further comprises:

including an identifier of the application within the request for the route selection policy associated with the application.
The method of claim 6, wherein transmitting the request further comprises:

including, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The method of claim 1, further comprising:

storing, at the UE, the indication of the route selection policy associated with the application, wherein establishing the data connection is based at least in part on the storing.
The method of claim 1, wherein establishing the data connection with the network further comprises:

establishing a protocol data unit session with the network in accordance with the route selection policy.
The method of claim 1, wherein the route selection policy is associated with a network slicing instance.
A method for wireless communication at a wireless network device, comprising:

receiving, from a user equipment (UE) , a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy;

transmitting, in response to the request, an indication of the route selection policy associated with the application; and

establishing a data connection with the UE in accordance with the route selection policy.
The method of claim 11, wherein receiving the request further comprises:

receiving the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The method of claim 11, wherein receiving the request further comprises:

receiving the request as part of a UE configuration update procedure.
The method of claim 11, wherein receiving the request further comprises:

receiving the request according to in accordance with a periodicity for route selection policy requests.
The method of claim 14, further comprising:

receiving, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The method of claim 11, wherein receiving the request further comprises:

receiving an identifier of the application within the request for the route selection policy associated with the application.
The method of claim 16, wherein receiving the request further comprises:

receiving, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The method of claim 11, wherein establishing the data connection with the user equipment (UE) further comprises:

establishing a protocol data unit session with the network in accordance with the route selection policy.
The method of claim 11, wherein the route selection policy is associated with a network slicing instance.
An apparatus for wireless communication at a user equipment (UE) , comprising:

a processor,

memory coupled with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy;

transmit, to the network, a request for the route selection policy associated with the application;

receive, in response to the request, an indication of the route selection policy associated with the application; and

establish a data connection in accordance with the route selection policy.
The apparatus of claim 20, wherein the instructions to transmit the request further are executable by the processor to cause the apparatus to:

transmit the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The apparatus of claim 20, wherein the instructions to transmit the request further are executable by the processor to cause the apparatus to:

transmit the request as part of a UE configuration update procedure.
The apparatus of claim 20, wherein the instructions to transmit the request further are executable by the processor to cause the apparatus to:

transmit the request in accordance with a periodicity for route selection policy requests.
The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to:

transmit, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The apparatus of claim 20, wherein the instructions to transmit the request further are executable by the processor to cause the apparatus to:

include an identifier of the application within the request for the route selection policy associated with the application.
The apparatus of claim 25, wherein the instructions to transmit the request further are executable by the processor to cause the apparatus to:

include, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to:

store, at the UE, the indication of the route selection policy associated with the application, wherein establishing the data connection is based at least in part on the storing.
The apparatus of claim 20, wherein the instructions to establish the data connection with the network further are executable by the processor to cause the apparatus to:

establish a protocol data unit session with the network in accordance with the route selection policy.
The apparatus of claim 20, wherein the route selection policy is associated with a network slicing instance.
An apparatus for wireless communication at a wireless network device, comprising:

a processor,

memory coupled with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

receive, from a user equipment (UE) , a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy;

transmit, in response to the request, an indication of the route selection policy associated with the application; and

establish a data connection with the UE in accordance with the route selection policy.
The apparatus of claim 30, wherein the instructions to receive the request further are executable by the processor to cause the apparatus to:

receive the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The apparatus of claim 30, wherein the instructions to receive the request further are executable by the processor to cause the apparatus to:

receive the request as part of a UE configuration update procedure.
The apparatus of claim 30, wherein the instructions to receive the request further are executable by the processor to cause the apparatus to:

receive the request according to in accordance with a periodicity for route selection policy requests.
The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to:

receive, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The apparatus of claim 30, wherein the instructions to receive the request further are executable by the processor to cause the apparatus to:

receive an identifier of the application within the request for the route selection policy associated with the application.
The apparatus of claim 35, wherein the instructions to receive the request further are executable by the processor to cause the apparatus to:

receive, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The apparatus of claim 30, wherein the instructions to establish the data connection with the user equipment (UE) further are executable by the processor to cause the apparatus to:

establish a protocol data unit session with the network in accordance with the route selection policy.
The apparatus of claim 30, wherein the route selection policy is associated with a network slicing instance.
An apparatus for wireless communication at a user equipment (UE) , comprising:

means for identifying that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy;

means for transmitting, to the network, a request for the route selection policy associated with the application;

means for receiving, in response to the request, an indication of the route selection policy associated with the application; and

means for establishing a data connection in accordance with the route selection policy.
The apparatus of claim 39, wherein the means for transmitting the request further comprises:

means for transmitting the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The apparatus of claim 39, wherein the means for transmitting the request further comprises:

means for transmitting the request as part of a UE configuration update procedure.
The apparatus of claim 39, wherein the means for transmitting the request further comprises:

means for transmitting the request in accordance with a periodicity for route selection policy requests.
The apparatus of claim 42, further comprising:

means for transmitting, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The apparatus of claim 39, wherein the means for transmitting the request further comprises:

means for including an identifier of the application within the request for the route selection policy associated with the application.
The apparatus of claim 44, wherein the means for transmitting the request further comprises:

means for including, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The apparatus of claim 39, further comprising:

means for storing, at the UE, the indication of the route selection policy associated with the application, wherein establishing the data connection is based at least in part on the storing.
The apparatus of claim 39, wherein the means for establishing the data connection with the network further comprises:

means for establishing a protocol data unit session with the network in accordance with the route selection policy.
The apparatus of claim 39, wherein the route selection policy is associated with a network slicing instance.
An apparatus for wireless communication at a wireless network device, comprising:

means for receiving, from a user equipment (UE) , a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy;

means for transmitting, in response to the request, an indication of the route selection policy associated with the application; and

means for establishing a data connection with the UE in accordance with the route selection policy.
The apparatus of claim 49, wherein the means for receiving the request further comprises:

means for receiving the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The apparatus of claim 49, wherein the means for receiving the request further comprises:

means for receiving the request as part of a UE configuration update procedure.
The apparatus of claim 49, wherein the means for receiving the request further comprises:

means for receiving the request according to in accordance with a periodicity for route selection policy requests.
The apparatus of claim 52, further comprising:

means for receiving, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The apparatus of claim 49, wherein the means for receiving the request further comprises:

means for receiving an identifier of the application within the request for the route selection policy associated with the application.
The apparatus of claim 54, wherein the means for receiving the request further comprises:

means for receiving, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The apparatus of claim 49, wherein the means for establishing the data connection with the user equipment (UE) further comprises:

means for establishing a protocol data unit session with the network in accordance with the route selection policy.
The apparatus of claim 49, wherein the route selection policy is associated with a network slicing instance.
A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE) , the code comprising instructions executable by a processor to:

identify that the UE includes an application which is configured to participate in data communications with a network in accordance with a route selection policy;

transmit, to the network, a request for the route selection policy associated with the application;

receive, in response to the request, an indication of the route selection policy associated with the application; and

establish a data connection in accordance with the route selection policy.
The non-transitory computer-readable medium of claim 58, wherein the instructions to transmit the request further are executable to:

transmit the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The non-transitory computer-readable medium of claim 58, wherein the instructions to transmit the request further are executable to:

transmit the request as part of a UE configuration update procedure.
The non-transitory computer-readable medium of claim 58, wherein the instructions to transmit the request further are executable to:

transmit the request in accordance with a periodicity for route selection policy requests.
The non-transitory computer-readable medium of claim 61, wherein the instructions are further executable to:

transmit, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The non-transitory computer-readable medium of claim 58, wherein the instructions to transmit the request further are executable to:

include an identifier of the application within the request for the route selection policy associated with the application.
The non-transitory computer-readable medium of claim 63, wherein the instructions to transmit the request further are executable to:

include, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The non-transitory computer-readable medium of claim 58, wherein the instructions are further executable to:

store, at the UE, the indication of the route selection policy associated with the application, wherein establishing the data connection is based at least in part on the storing.
The non-transitory computer-readable medium of claim 58, wherein the instructions to establish the data connection with the network further are executable to:

establish a protocol data unit session with the network in accordance with the route selection policy.
The non-transitory computer-readable medium of claim 58, wherein the route selection policy is associated with a network slicing instance.
A non-transitory computer-readable medium storing code for wireless communication at a wireless network device, the code comprising instructions executable by a processor to:

receive, from a user equipment (UE) , a request for a route selection policy associated with an application included at the UE, the application configured to participate in data communications in accordance with the route selection policy;

transmit, in response to the request, an indication of the route selection policy associated with the application; and

establish a data connection with the UE in accordance with the route selection policy.
The non-transitory computer-readable medium of claim 68, wherein the instructions to receive the request further are executable to:

receive the request as part of a registration procedure to obtain one or more network slicing instances on which the UE is allowed to communicate.
The non-transitory computer-readable medium of claim 68, wherein the instructions to receive the request further are executable to:

receive the request as part of a UE configuration update procedure.
The non-transitory computer-readable medium of claim 68, wherein the instructions to receive the request further are executable to:

receive the request according to in accordance with a periodicity for route selection policy requests.
The non-transitory computer-readable medium of claim 71, wherein the instructions are further executable to:

receive, after establishing the data connection, a request for an update to the route selection policy associated with the application in accordance with the periodicity.
The non-transitory computer-readable medium of claim 68, wherein the instructions to receive the request further are executable to:

receive an identifier of the application within the request for the route selection policy associated with the application.
The non-transitory computer-readable medium of claim 73, wherein the instructions to receive the request further are executable to:

receive, in the request for the route selection policy, a plurality of additional identifiers corresponding to additional applications present at the UE.
The non-transitory computer-readable medium of claim 68, wherein the instructions to establish the data connection with the user equipment (UE) further are executable to:

establish a protocol data unit session with the network in accordance with the route selection policy.
The non-transitory computer-readable medium of claim 68, wherein the route selection policy is associated with a network slicing instance.