CN117083982A - Techniques for subscription-based or network slice-based traffic differentiation and routing - Google Patents

Abstract

Various aspects of the present disclosure relate generally to wireless communications. In some aspects, a User Equipment (UE) may establish a first communication connection associated with a first subscription or with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE. The UE may establish a second communication connection associated with a second subscription or with a second network slice. The UE may receive data traffic packets associated with one or more parameters from the device via a wireless local area network provided by the UE or via a wired connection. The UE may route the data traffic packet to the second communication connection based at least in part on the one or more parameters. The UE may transmit the data traffic packet using the second communication connection. Numerous other aspects are described.

Description

Techniques for subscription-based or network slice-based traffic differentiation and routing

Cross Reference to Related Applications

This patent application claims priority from U.S. provisional patent application No.63/164,373 entitled "TECHNIQUES FOR SUBSCRIPTION BASED OR NETWORK SLICE BASED TRAFFIC DIFFERENTIATION AND ROUTING (technique for subscription-based or network slice-based traffic differentiation and routing)" filed on month 22 of 2021, and U.S. non-provisional patent application No.17/651,271 entitled "TECHNIQUES FOR SUBSCRIPTION BASED OR NETWORK SLICE BASED TRAFFIC DIFFERENTIATION AND ROUTING (technique for subscription-based or network slice-based traffic differentiation and routing)" filed on month 16 of 2022, both of which are hereby expressly incorporated herein by reference.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for subscription-based or network slice-based traffic differentiation and routing.

Description of related Art

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-advanced is an enhancement set to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the third generation partnership project (3 GPP).

A wireless network may include several Base Stations (BSs) capable of supporting several User Equipment (UE) communications. The UE may communicate with the base station via the downlink and uplink. The downlink (or forward link) refers to the communication link from the base stations to the UEs, and the uplink (or reverse link) refers to the communication link from the UEs to the base stations. As will be described in more detail herein, a base station may be referred to as a node B, a gNB, an Access Point (AP), a radio head, a transmission-reception point (TRP), a New Radio (NR) base station, a 5G B node, and so on.

The above multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the urban, national, regional, and even global level. NR (which may also be referred to as 5G) is an enhanced set of LTE mobile standards promulgated by 3 GPP. NR is designed to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the Downlink (DL) (CP-OFDM), CP-OFDM and/or SC-FDM on the Uplink (UL) (e.g., also known as discrete fourier transform spread OFDM (DFT-s-OFDM)), and supporting beamforming, multiple Input Multiple Output (MIMO) antenna technology and carrier aggregation to improve spectral efficiency, reduce cost, improve service, utilize new spectrum, and integrate better with other open standards. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR and other radio access technologies remain useful.

SUMMARY

In some aspects, a method of wireless communication performed by a User Equipment (UE) includes: establishing a first communication connection associated with a first subscription of the UE or with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE; establishing a second communication connection associated with a second subscription of the UE or with a second network slice; receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection; routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and transmitting the data traffic packet using the second communication connection.

In some aspects, a wireless communication method performed by a UE includes: establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point; establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point; transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and receiving a connection establishment request from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request for establishing a tethered connection for the device using the first communication connection or the second communication connection.

In some aspects, a UE for wireless communication, comprises: a memory and one or more processors coupled to the memory configured to: establishing a first communication connection associated with a first subscription of the UE or with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE; establishing a second communication connection associated with a second subscription of the UE or with a second network slice; receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection; routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and transmitting the data traffic packet using the second communication connection.

In some aspects, a UE for wireless communication, comprises: a memory and one or more processors coupled to the memory configured to: establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point; establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point; transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and receiving a connection establishment request from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request for establishing a tethered connection for the device using the first communication connection or the second communication connection.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: establishing a first communication connection associated with a first subscription of the UE or with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE; establishing a second communication connection associated with a second subscription of the UE or with a second network slice; receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection; routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and transmitting the data traffic packet using the second communication connection.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point; establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point; transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and receiving a connection establishment request from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request for establishing a tethered connection for the device using the first communication connection or the second communication connection.

In some aspects, an apparatus for wireless communication comprises: means for establishing a first communication connection associated with a first subscription of the apparatus or with a first network slice, wherein the first communication connection is a default connection for data traffic for the apparatus; means for establishing a second communication connection associated with a second subscription of the apparatus or associated with a second network slice; means for receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the apparatus or via a wired connection; means for routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and means for transmitting the data traffic packet using the second communication connection.

In some aspects, an apparatus for wireless communication comprises: means for establishing a first communication connection for a first subscription of the equipment, wherein the first communication connection is associated with a first access point; means for establishing a second communication connection for a second subscription of the apparatus, wherein the second communication connection is associated with a second access point; means for transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and means for receiving a connection establishment request from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request for establishing a tethered connection for the device using the first communication connection or the second communication connection.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, both as to their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended to be limiting of the claims.

Brief Description of Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a diagram illustrating an example in which a base station is in communication with a User Equipment (UE) in a wireless network according to the present disclosure.

Fig. 3 is a diagram illustrating an example in which a UE provides wireless connectivity for a device in accordance with the present disclosure.

Fig. 4 is a diagram illustrating an example of a multi-subscriber identity module (multi-SIM) UE according to the present disclosure.

Fig. 5 is a diagram illustrating an example associated with subscription-based or network slice-based traffic differentiation and routing in accordance with the present disclosure.

Fig. 6 is a diagram illustrating an example associated with subscription-based or network slice-based traffic differentiation and routing in the case of multiple access points, in accordance with the present disclosure.

Fig. 7 and 8 are diagrams illustrating example processes associated with subscription-based or network slice-based traffic differentiation and routing, according to this disclosure.

Fig. 9 is a block diagram of an example apparatus for wireless communication according to the present disclosure.

Detailed Description

Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art will appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method practiced using any number of the aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using such structure, functionality, or both as a complement to, or in addition to, the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

Several aspects of a telecommunications system will now be presented with reference to various apparatus and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

It should be noted that although aspects may be described herein using terms commonly associated with 5G or NR Radio Access Technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or RATs after 5G (e.g., 6G).

Fig. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (NR) network and/or an LTE network, etc. or may include elements thereof. Wireless network 100 may include several base stations 110 (shown as BS110a, BS110b, BS110c, and BS110 d) and other network entities. A Base Station (BS) is an entity that communicates with User Equipment (UE) and may also be referred to as an NR base station, a node B, a gNB, a 5G B Node (NB), an access point, a transmission-reception point (TRP), and so forth. Each base station may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a base station and/or a base station subsystem serving the coverage area, depending on the context in which the term is used.

A base station may provide communication coverage for a macrocell, a picocell, a femtocell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG)). The base station of a macro cell may be referred to as a macro base station. A base station for a pico cell may be referred to as a pico base station. The base station for a femto cell may be referred to as a femto base station or a home base station. In the example shown in fig. 1, base station 110a may be a macro base station for macro cell 102a, base station 110b may be a pico base station for pico cell 102b, and BS110c may be a femto base station for femto cell 102 c. A base station may support one or more (e.g., three) cells. The terms "eNB," base station, "" NR base station, "" gNB, "" TRP, "" AP, "" node B, "" 5G NB, and "cell" may be used interchangeably herein.

In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to an aggregated base station, a decomposed base station, an Integrated Access and Backhaul (IAB) node, a relay node, and/or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a near real-time (near RT) RAN Intelligent Controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. . In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions, such as those described herein in connection with base station 110. In some aspects, the term "base station" or "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or different geographic locations) may be configured to perform, or repeat the performance of, at least a portion of the functionality, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and/or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions, but not the other. In this way, a single device may include more than one base station.

In some aspects, a cell may not necessarily be stationary and the geographic area of the cell may move according to the location of a mobile base station. In some aspects, base stations may be interconnected with each other and/or to one or more other base stations or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

The wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station or UE) and send the transmission of the data to a downstream station (e.g., a UE or base station). The relay station may also be a UE that can relay transmissions for other UEs. In the example shown in fig. 1, relay base station 110d may communicate with macro base station 110a and UE 120d to facilitate communications between base station 110a and UE 120 d. The relay base station may also be referred to as a relay station, a relay base station, a relay, etc.

The wireless network 100 may be a heterogeneous network including different types of base stations (such as macro base stations, pico base stations, femto base stations, or relay base stations, etc.). These different types of base stations may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have a lower transmit power level (e.g., 0.1 to 2 watts).

The network controller 130 may be coupled to a set of base stations and may provide coordination and control for these base stations. The network controller 130 may communicate with the base stations via backhaul. These base stations may also communicate with each other directly or indirectly, e.g., via wireless or wired backhaul.

UEs 120 (e.g., 120a, 120b, 120 c) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be called an access terminal, mobile station, subscriber unit, station, etc. The UE may be a cellular telephone (e.g., a smart phone), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, a super book, a medical device or equipment, a biometric sensor/device, a wearable device (smart watch, smart garment, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., music or video device, or satellite radio), a vehicle component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

Some UEs may be considered Machine Type Communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. The wireless node may provide connectivity to or to a network (e.g., a wide area network such as the internet or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered internet of things (IoT) devices and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered Customer Premise Equipment (CPE). UE 120 may be included within a housing that houses components of UE 120, such as processor components and/or memory components. In some aspects, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. RATs may also be referred to as radio technologies, air interfaces, etc. Frequencies may also be referred to as carriers, frequency channels, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120 e) may communicate directly (e.g., without the base station 110 as an intermediary) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-vehicle (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol or a vehicle-to-infrastructure (V2I) protocol), and/or a mesh network. In this case, UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by base station 110.

Devices of the wireless network 100 may communicate using electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of the wireless network 100 may communicate using an operating frequency band having a first frequency range (FR 1) and/or may communicate using an operating frequency band having a second frequency range (FR 2), the first frequency range (FR 1) may span 410MHz to 7.125GHz, and the second frequency range (FR 2) may span 24.25GHz to 52.6GHz. The frequency between FR1 and FR2 is sometimes referred to as the mid-band frequency. Although a portion of FR1 is greater than 6GHz, FR1 is commonly referred to as the "sub-6 GHz" band. Similarly, FR2 is commonly referred to as the "millimeter wave" frequency band, although it is different from the Extremely High Frequency (EHF) frequency band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" frequency band. Thus, unless specifically stated otherwise, it should be understood that, if used herein, the term "sub-6 GHz" and the like may broadly refer to frequencies less than 6GHz, frequencies within FR1, and/or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless specifically stated otherwise, it should be understood that, if used herein, the term "millimeter wave" or the like may broadly refer to frequencies within the EHF band, frequencies within FR2, and/or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

As indicated above, fig. 1 is provided as an example. Other examples may differ from the example described with respect to fig. 1.

Fig. 2 is a diagram illustrating an example 200 in which a base station 110 is in communication with a UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with T antennas 234a through 234T, and UE 120 may be equipped with R antennas 252a through 252R, where in general T is 1 and R is 1.

At base station 110, transmit processor 220 may receive data for one or more UEs from data source 212, select one or more Modulation and Coding Schemes (MCSs) for each UE based at least in part on a Channel Quality Indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary Synchronization Signals (PSS) or Secondary Synchronization Signals (SSS)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T Modulators (MODs) 232a through 232T. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232T may be transmitted via T antennas 234a through 234T, respectively.

At UE 120, antennas 252a through 252r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254R, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280. The term "controller/processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, and/or a CQI parameter, among others. In some aspects, one or more components of UE 120 may be included in housing 284.

The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may comprise, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via a communication unit 294.

Antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included in one or more antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays, etc. The antenna panel, antenna group, antenna element set, and/or antenna array may include one or more antenna elements. The antenna panel, antenna group, antenna element set, and/or antenna array may include a coplanar antenna element set and/or a non-coplanar antenna element set. The antenna panel, antenna group, antenna element set, and/or antenna array may include antenna elements within a single housing and/or antenna elements within multiple housings. The antenna panel, antenna group, antenna element set, and/or antenna array may include one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of fig. 2.

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information from controller/processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and/or CQI). Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and demodulator (e.g., MOD/DEMOD 254) of UE 120 may be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and/or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and/or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., as described with reference to fig. 5-9).

At base station 110, uplink signals from UE 120 as well as other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 to schedule UEs 120 for downlink and/or uplink communications. In some aspects, a modulator and demodulator (e.g., MOD/DEMOD 232) of base station 110 may be included in a modem of base station 110. In some aspects, the base station 110 comprises a transceiver. The transceiver may include any combination of antenna(s) 234, modulator and/or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and/or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller/processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., as described with reference to fig. 5-9).

The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other components of fig. 2 may perform one or more techniques associated with subscription-based or network slice-based traffic differentiation and routing, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of fig. 2 may perform or direct operations such as process 700 of fig. 7, process 800 of fig. 8, and/or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may include: a non-transitory computer readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and/or UE 120 (e.g., directly, or after compilation, conversion, and/or interpretation), may cause the one or more processors, UE 120, and/or base station 110 to perform or direct operations such as process 700 of fig. 7, process 800 of fig. 8, and/or other processes described herein. In some aspects, executing instructions may include executing instructions, converting instructions, compiling instructions, and/or interpreting instructions.

In some aspects, UE 120 includes: means for establishing a first communication connection associated with a first subscription of a UE or associated with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE; means for establishing a second communication connection associated with a second subscription of the UE or associated with a second network slice; means for receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection; means for routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and/or means for transmitting the data traffic packet using the second communication connection. Means for UE 120 to perform the operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller/processor 280, or memory 282.

In some aspects, UE 120 includes: means for establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point; means for establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point; means for transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and/or means for receiving a connection establishment request from a device, the connection establishment request to establish a tethered connection for the device using the first communication connection or the second communication connection based at least in part on the transmission of the first identifier and the second identifier. Means for UE 120 to perform the operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller/processor 280, or memory 282.

As indicated above, fig. 2 is provided as an example. Other examples may differ from the example described with respect to fig. 2.

Fig. 3 is a diagram illustrating an example 300 of a UE providing wireless connectivity for a device in accordance with the present disclosure. As shown in fig. 3, base station 110, UE 120, and device 310 may communicate with each other. UE 120 may provide a wireless (e.g., cellular) connection for device 310 to enable device 310 to access a wireless network associated with base station 110. For example, device 310 may establish a connection (shown as a tethered connection) with UE 120. "tethered connection," "tethered connection," or "tethered connection" may refer to a connection between a device and UE 120 where UE 120 acts as a routing device for the device to route traffic to the wireless (e.g., cellular) network of UE 120. UE 120 may establish a connection (shown as a wireless network connection) with base station 110. As used herein, "wireless network connection," "cellular network connection," or "communication connection" may refer to a connection between UE 120 and base station 110 through which UE 120 communicates or routes traffic associated with a tethered device (e.g., device 310). For example, in a tethered scenario, UE 120 can provide internet access to device 310 using a wireless network connection (e.g., using a connection between UE 120 and base station 110 to a wireless network associated with base station 110). For example, a wireless network connection may be used as a backhaul connection (e.g., a cellular backhaul connection) for device 310.

In some cases, device 310 may be a device capable of connecting to the internet but may not have cellular connectivity (e.g., with base station 110). For example, device 310 may be a laptop computer, tablet computer, desktop computer, game console, set-top box, wearable communication device (e.g., a smart watch, a pair of smart glasses, a head-mounted display, or a virtual reality head-mounted device), or similar type of device.

For example, UE 120 may share or provide internet access (e.g., provided through a wireless connection with base station 110) to device 310. As used herein, "tethered" may refer to UE 120 providing or sharing a wireless data connection (e.g., a data connection provided by a wireless connection with base station 110) to another device, such as device 310. The tethering may also be referred to as providing a mobile hotspot, providing a personal hotspot, providing a portable hotspot, providing a Wi-Fi hotspot, and/or telephone (PAM) technology as a modem, etc. Device 310 may be referred to as a "tethered device". In a tethered scenario, UE 120 may act as a routing device between device 310 and base station 110.

In some cases, the tethered connection may be a wireless connection. For example, UE 120 may broadcast an identifier of a Wireless Local Area Network (WLAN), such as a Wi-Fi network, provided by an access point of UE 120. The device 310 may connect to the access point using a WLAN connection (e.g., a Wi-Fi connection). In some cases, the tethered connection may be another wireless connection, such as a bluetooth connection. In some cases, the tethered connection may be a physical connection, such as a wired connection (e.g., using a Universal Serial Bus (USB) cable) between UE 120 and device 310.

The tethered connection and wireless network connection may enable communication of traffic from device 310 to UE 120 (e.g., via the tethered connection) and from UE 120 to base station 110 using a wireless (e.g., cellular) connection (e.g., wireless network connection) between UE 120 and base station 110. For example, in the uplink, device 310 may transmit traffic (e.g., data) to UE 120 using a tethered connection, as shown by reference numeral 320. UE 120 may receive the traffic and may route the traffic to an interface of UE 120 associated with the wireless network connection with base station 110. As indicated by reference numeral 330, UE 120 may transmit traffic (e.g., received from device 310) to base station 110 using a wireless network connection.

Similarly, in the downlink, as indicated by reference numeral 330, base station 110 may transmit traffic for device 310 to UE 120 (e.g., via a wireless network connection). UE 120 may route traffic to an interface (and/or access point) of UE 120 associated with the connection. As shown by reference numeral 320, UE 120 may transmit traffic (e.g., received from base station 110) to device 310 using the tethered connection. UE 120 may perform routing of traffic for the tethered device (e.g., for device 310) using one or more protocol stacks of UE 120 (e.g., an Internet Protocol (IP) layer and/or a transport layer). Additionally or alternatively, the hardware components of UE 120 may be configured to perform routing of traffic for tethered devices (e.g., through an Internet Packet Accelerator (IPA) of UE 120).

As a result, device 310 may access a data connection with a wireless network (e.g., associated with base station 110) via UE 120. Thus, internet access for device 310 is improved because device 310 is able to access data connections with wireless networks in environments where device 310 may not otherwise be able to establish an internet connection (e.g., in a vehicle, in a train, in a public area, and/or outside a home or office).

As indicated above, fig. 3 is provided as an example. Other examples may differ from the example described with respect to fig. 3.

Fig. 4 is a diagram illustrating an example 400 of a multi-Subscriber Identity Module (SIM) UE according to the present disclosure. As shown in fig. 4, UE 120 may be a multi-SIM (multi-SIM) UE including multiple SIMs (two or more SIMs), shown as a first SIM 405a and a second SIM 405b. The first SIM 405a may be associated with a first subscription (shown as SUB 1 (subscription 1)) and the second SIM 405b may be associated with a second subscription (shown as SUB 2 (subscription 2)). The subscription may be a subscription with a network operator (e.g., a Mobile Network Operator (MNO)) that enables UE 120 to access a wireless network (e.g., a Radio Access Network (RAN)) associated with the network operator. As used herein, "SIM" and "subscription" may be used interchangeably.

The SIMs 405 (e.g., the first SIM 405a and/or the second SIM 405 b) may be removable SIMs (e.g., SIM cards) or embedded SIMs. SIM 405 may include an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and a security key that are used to identify and authenticate a corresponding subscription associated with SIM 405. In some cases, SIM 405 may store a list of services, such as data services or voice services, etc., that UE 120 has permission to access using the subscription associated with SIM 405.

As further shown in fig. 4, UE 120 may communicate (e.g., in a connected mode, idle mode, or inactive mode) with first base station 410a via first cell 415a (shown as cell 1) using first SIM 405 a. In this case, the first subscription (SUB 1) of UE 120 may be used to access the first cell 415a (e.g., using the first IMSI for UE identification, the first security key for UE authentication, using a first list of services that UE 120 is permitted to access using the first subscription, or by counting data or voice usage on the first cell against the first subscription, etc.). Similarly, UE 120 may use second SIM 405b to communicate (e.g., in a connected mode, idle mode, or inactive mode) with second base station 410b via second cell 415b (shown as cell 2). In this case, a second subscription (SUB 2) of UE 120 may be used to access a second cell 415b (e.g., using a second IMSI for UE identification, a second security key for UE authentication, using a second list of services that UE 120 is permitted to access using the second subscription, or by counting data or voice usage on the second cell against the second subscription, etc.).

The first base station 410a and/or the second base station 410b may include one or more of the base stations 110 described above in connection with fig. 1. Although the first cell 415a and the second cell 415b are shown as being provided by different base stations, in some aspects, the first cell 415 and the second cell 415b may be provided by the same base station. Thus, in some aspects, the first base station 410a and the second base station 410b may be integrated into a single base station.

In some cases, one of the first SIM 405a (e.g., first subscription) or the second SIM 405b (e.g., second subscription) may be a default or dedicated data subscription for the UE 120. UE 120 may send and/or receive data (e.g., internet traffic) using a default or dedicated data subscription. For example, if the first SIM 405a (e.g., the first subscription) is a default or dedicated data subscription for the UE 120, the UE 120 may use the connection with the first base station 410a as a default connection for data traffic (e.g., internet traffic) communicated by the UE 120.

In some cases, UE 120 may be capable of operating in a multi-SIM multi-standby (MSMS) mode, such as a dual-SIM dual standby (DSDS) mode (e.g., when UE 120 is associated with two subscriptions). Additionally or alternatively, UE 120 may be capable of operating in a single receiver multi-SIM multi-active (SR-MSMA) mode, such as a dual-SIM dual-active (DSDA) mode (e.g., when UE 120 is associated with two subscriptions).

In DSDA mode, UE 120 is able to conduct concurrent active communications using both SIMs of UE 120. Thus, a UE 120 in DSDA mode is able to communicate using the first SIM 405a (and the first subscription) while communicating using the second SIM 405b (and the second subscription). For example, when UE 120 is in an active session (e.g., a voice call or another latency sensitive service such as an online game, stock exchange, or Over The Top (OTT) service) using first SIM 405a, UE 120 can receive notification of the voice call using second SIM 405b without interrupting communications using first SIM 405a and without having to tune or switch away from first cell 415a to tune to second cell 415b.

In DSDS mode, UE 120 is not able to conduct concurrent active communications using both SIMs of UE 120. Thus, the UE 120 in DSDS mode cannot communicate using the first SIM 405a (and the first subscription) while communicating using the second SIM 405b (and the second subscription). However, the UE 120 in DSDS mode may be capable of switching between two separate mobile network services, may include hardware for maintaining multiple connections (e.g., one connection per SIM) in a standby state, or may include hardware for maintaining multiple network connections simultaneously (e.g., multiple transceivers), and so on. However, UE 120 in DSDS mode may only be able to receive data on one connection at a time because radio frequency resources are shared between multiple subscriptions. For example, UE 120 in DSDS mode may be associated with multiple subscriptions, but may include only a single transceiver shared by the multiple subscriptions, a single transmit chain shared by the multiple subscriptions, or a single receive chain shared by the multiple subscriptions, and so on.

In some examples, UE 120 may be capable of operating in DSDA mode for a first RAT combination and may not be capable of operating in DSDA mode for a second RAT combination. For example, UE 120 may be capable of operating in DSDA mode for nr+nr, where first cell 415a (and first SIM 405a and first subscription) uses an NR RAT and second cell 415b (and second SIM 405b and second subscription) also uses an NR RAT. However, UE 120 may not be able to operate in DSDA mode for nr+lte, with one of the following: the first cell 415a (and the first SIM 405a and the first subscription) uses an NR RAT and the second cell 415b (and the second SIM 405b and the second subscription) uses an LTE RAT (or vice versa). In some aspects, UE 120 may not be capable of operating in DSDA mode for a second RAT combination (e.g., nr+lte), but may be capable of operating in DSDS mode for the second RAT combination. This UE design reduces design costs compared to enabling UE 120 to operate using DSDA modes for the second RAT combination.

As shown in fig. 4, UE 120 may provide device 420 with access to a wireless (e.g., cellular) network connection (e.g., in a similar manner as described above in connection with fig. 3). For example, UE 120 and device 420 may establish a tethered connection to enable UE 120 to provide a wireless (e.g., cellular) network connection for device 420. In some cases, when UE 120 provides a tethered connection for another device (e.g., device 420), the wireless (e.g., cellular) network connection of device 420 may be associated with (or fixed to) the default or dedicated data subscription of UE 120.

For example, device 420 may need to access a wireless (e.g., cellular) connection of UE 120 via a connection associated with a default or dedicated data subscription of UE 120. For example, if the first SIM 405a (e.g., the first subscription) is a default or dedicated data subscription for the UE 120, the UE 120 may always route traffic associated with the device 420 to a cellular connection (e.g., a connection with the first base station 410 a) associated with the first SIM 405 a. In some cases, however, traffic associated with device 420 may be better served by cellular connections other than the cellular connections associated with the default or dedicated data subscription of UE 120. For example, in some cases, the device 420 may access an application or service that receives an incentive (e.g., a billing incentive, a data rate incentive, and/or a charging incentive) from a network operator associated with the second SIM 405b (e.g., where the first SIM 405a is a default or dedicated data subscription for the UE 120). However, UE 120 may use only the connection associated with first SIM 405a for routing traffic associated with device 420. Thus, device 420 may not be able to receive the benefits provided by the incentive from the network operator associated with second SIM 405b (e.g., even when UE 120 is operating in DSDA mode, where the connection associated with second SIM 405b is available for use by UE 120).

As another example, traffic associated with device 420 may be associated with a high throughput level or a high data rate. In some cases, a network connection (e.g., a cellular connection or a communication connection) associated with the first SIM 405a may provide a lower data rate than a network connection (e.g., a cellular connection or a communication connection) associated with the second SIM 405 b. For example, the network connection associated with the first SIM 405a may be associated with a first RAT, such as a 3G RAT or a 4G RAT. The network connection associated with the second SIM 405b may be associated with a second RAT having a higher data rate or data capacity than the first RAT, such as a 5G RAT and/or a millimeter wave RAT. However, UE120 may use only the connection associated with first SIM 405a for routing traffic associated with device 420. Thus, high throughput levels or high data rate traffic of device 420 may be routed using lower data rates or lower data capacity RATs. As a result, communication performance and communication efficiency of traffic may be reduced.

Further, UE120 may route traffic of the tethered device (e.g., device 420) to the default network slice of the active or selected SIM. For example, when UE120 operates using a single SIM (e.g., in DSDS mode or single SIM mode), UE120 may route traffic of the tethered device to a default network slice of the single SIM. Network slicing involves implementing a logical network on top of a shared physical infrastructure, where each network slice may include end-to-end connections for functions deployed for a particular application, application type, traffic type, or use case, etc. Each network slice may be identified by a network slice identity. The network slice identity may include a slice identifier referred to as single network slice selection assistance information (S-nsai). UE120 may route only traffic of the tethered device to the default network slice (e.g., using a Packet Data Unit (PDU) session associated with the default network slice). In some cases, however, traffic associated with the tethered device may be better served by network slices other than the default network slice. For example, traffic associated with the tethered device can be associated with low latency requirements. However, a default network slice may be associated with a higher latency than another network slice. As a result, traffic associated with the tethered device may experience higher latency or degraded communication performance.

Some techniques and apparatuses described herein enable subscription-based and/or network slice-based traffic differentiation and routing for traffic associated with tethered devices. For example, UE 120 may receive traffic from the tethered device over the tethered connection. UE 120 may filter the traffic to determine whether the traffic meets or matches one or more rules. One or more rules may be configured at UE 120 (e.g., in an Original Equipment Manufacturer (OEM) configuration). UE 120 may use one or more rules to identify traffic from the tethered device that should be routed to a non-default data connection (e.g., a non-default data subscription) or a non-default network slice of the UE. For example, if the traffic (e.g., if one or more parameters associated with the traffic) meets or matches a rule (e.g., a rule of the one or more rules), UE 120 may route the traffic to a non-default data connection (e.g., a non-default data subscription) or a non-default network slice of UE 120.

As a result, UE 120 may be implemented as a subscription or network slice that routes traffic associated with the tethered device to best service traffic associated with the tethered device. For example, UE 120 may be implemented to use data connections or network slices other than default data connections or default network slices for traffic associated with tethered devices. By enabling UE 120 to filter traffic associated with the tethered device to data connections or network slices other than the default data connections or default network slices, communication performance of the traffic may be improved. For example, the tethered device can be implemented to achieve the benefits of incentives associated with using subscriptions that are not default data subscriptions for UE 120. Additionally or alternatively, the tethered device can experience improved data rates or reduced latency by using data connections or network slices that better service traffic associated with the tethered device in addition to default data connections or default network slices.

As indicated above, fig. 4 is provided as an example. Other examples may differ from the example described with respect to fig. 4.

Fig. 5 is a diagram illustrating an example 500 of subscription-based or network slice-based traffic differentiation and routing in accordance with the present disclosure. As shown in fig. 5, UE 120 may communicate with a first base station 505 and a second base station 510. For example, UE 120 may be a multi-SIM UE (e.g., in a similar manner as described above in connection with fig. 4). The first base station 505 may be associated with a first SIM (and/or a first subscription) of the UE 120. For example, the first base station 505 may provide a cell of a wireless network associated with a first network operator. The first network operator may be associated with a first SIM (and/or a first subscription) of UE 120. Similarly, second base station 510 may be associated with a second SIM (and/or a second subscription) of UE 120. For example, the second base station 510 may provide a cell of a wireless network associated with a second network operator. The second network operator may be associated with a second SIM (and/or a second subscription) of UE 120. Although fig. 5 depicts UE 120 as a multi-SIM UE, in some aspects UE 120 may be a single-SIM UE (e.g., UE 120 may use the techniques or operations described herein to route traffic associated with the tethered device to a network slice that is not a default network slice of data traffic, as described in more detail below). The first base station 505 and/or the second base station 510 may be a base station 110 and/or a network entity, such as a CU, DU, RU, and/or the like.

As shown in fig. 5, UE 120 may provide a tethered service and/or a hot spot service. For example, UE 120 may communicate with device 515. UE 120 may provide a wireless (e.g., cellular) network connection for device 515 to enable device 515 to access a wireless network associated with UE 120 (e.g., in a similar manner as described above in connection with fig. 3 and 4). For example, UE 120 may route traffic associated with device 515 to and/or from a wireless network (e.g., associated with first base station 505 or second base station 510).

For example, UE 120 may establish a first communication connection with first base station 505. The first communication connection may be associated with a first subscription and/or a first SIM of UE 120. Additionally or alternatively, the first communication connection may be associated with a first network slice. UE 120 may establish a second communication connection with second base station 510. The second communication connection may be associated with a second subscription and/or a second SIM of UE 120. Additionally or alternatively, the second communication connection may be associated with a second network slice.

The first communication connection may be a default connection for data traffic by UE 120. "default connection," "default data subscription," and/or "default network slice" may refer to a connection or interface of UE 120 that is configured or arranged to be associated with data traffic (e.g., internet traffic) communicated by UE 120. Connections or interfaces other than default connections may be used to communicate other traffic (e.g., other than data traffic or internet traffic), such as voice calls, etc. The default connection may also be referred to as a Default Data Subscription (DDS), a dedicated data subscription, a default data connection, and/or a default network slice, etc. The default connection may be indicated to UE 120 (e.g., via user input, for example) and/or may be dynamically determined by UE 120. In DSDS mode, the default connection may be associated with an active SIM of the first SIM and the second SIM. In DSDA mode, UE 120 may be able to maintain active sessions over both a default connection (e.g., over DDS) and other network connections (e.g., associated with non-DDS of UE 120). "non-DDS" or "not DDS" may refer to subscriptions of UE 120 that are not default subscriptions for use by UE 120 in communicating data traffic (e.g., internet traffic).

In some aspects, the first communication connection (e.g., associated with the first subscription and/or the first network slice) may be a default connection for data traffic by UE 120, as described above. The second communication connection (e.g., associated with the second subscription and/or the second network slice) may not be a default connection (e.g., may be a non-DDS connection) for data traffic by UE 120.

As described above, the first communication connection and the second communication connection may be used as wireless (e.g., cellular) connections associated with the tethered services and/or the hotspot services provided by UE 120. For example, in some aspects, UE 120 may be capable of communicating traffic (e.g., in DSDA mode) using both the first communication connection and the second communication connection. In some aspects, UE 120 may be capable of communicating traffic (e.g., in DSDS mode) using only one of the first communication connection or the second communication connection.

As shown in fig. 5, UE 120 and device 515 may establish a connection (e.g., a tethered connection) associated with UE 120 that provides a wireless connection (e.g., a connection to a wireless network) for device 515. In some aspects, the tethered connection can be a wireless connection (e.g., a WLAN connection, a Wi-Fi connection, and/or a bluetooth connection) or a wired connection. For example, UE 120 may be associated with one or more access points (e.g., WLAN access points or Wi-Fi access points). UE 120 may broadcast (e.g., advertise) information (e.g., network identification information, such as a Service Set Identifier (SSID) associated with a network provided by the access point) for one or more access points. Device 515 may transmit a request to establish a connection with the access point of UE 120. UE 120 and device 515 may use the access point to establish a tethered connection.

In some aspects, UE 120 may include a single access point associated with both the first subscription (and the first SIM) and the second subscription (and the second SIM). In some aspects, UE 120 may include separate access points (e.g., multiple separate access points) bridging to a single cellular network interface (e.g., and associated with both the first subscription and the second subscription). In some aspects, UE 120 may include separate access points (e.g., multiple separate access points) associated with separate cellular connections. For example, UE 120 may include a first access point associated with a first communication connection (e.g., with a first subscription/SIM) and a second access point associated with a second communication connection (e.g., with a second subscription/SIM).

As shown by reference numeral 520, UE 120 may receive traffic (e.g., data traffic packets) from device 515 to be routed by UE 120 to a wireless network (e.g., to first base station 505 or second base station 510) to which UE 120 is connected. For example, device 515 may transmit packets using a connection between UE 120 and device 515, and UE 120 may receive packets using a connection between UE 120 and device 515.

As shown by reference numeral 525, UE 120 may filter traffic (e.g., packets) received from device 515 to identify packets to be routed to a wireless network connection that is not a default network connection (e.g., packets to be routed to a second communication connection). For example, UE 120 may determine whether one or more parameters of the packet satisfy the rule. The rule may be indicated by the configuration of UE 120. For example, UE 120 may be configured with one or more rules (e.g., in an OEM configuration). One or more rules may be used to identify traffic associated with (e.g., received from or to be transmitted to) the tethered device to be routed (e.g., by UE 120) to a subscription that is not a DDS or a subscription that is not associated with a default network connection. For example, one or more rules may identify parameters of the packet that indicate that the packet is to be routed (e.g., by UE 120) to a subscription (e.g., and not simply routed to DDS, regardless of the type of traffic or parameters of the traffic).

One or more rules may be associated with the identifier of the subscription, such as a Mobile Country Code (MCC) and/or a Mobile Network Code (MNC). For example, one or more rules may indicate whether a packet meets or matches a rule, the packet to be routed to a subscription identified by the MCC and/or MNC associated with the rule. The one or more rules may indicate a service destination address, a service Fully Qualified Domain Name (FQDN), a port number of a service associated with the traffic, and/or a type of service (TOS) value indicated by the packet, etc. As a result, UE 120 can identify traffic associated with device 515 that may be better served by subscriptions (e.g., associated with rules) instead of routing traffic associated with device 515 to a default network connection (e.g., regardless of the type of traffic or the service or application associated with the traffic). For example, one or more rules may be used to identify traffic associated with incentives provided by subscriptions associated with the one or more rules (e.g., provided by a network operator associated with the subscription).

In some aspects, one or more rules may indicate a throughput threshold or a data rate threshold. For example, in some aspects, the first communication connection and the second communication connection may be associated with different RATs that support or provide different data rates or data capacities. For example, a first communication connection (e.g., a default network connection) may be associated with a lower data rate than a second communication connection. For example, the first communication connection may be associated with a 4G RAT or an LTE RAT, and the second communication connection may be associated with an NR RAT, a 5G RAT, and/or a mmwave RAT. The one or more rules may indicate that the packet or traffic should be routed to a network connection associated with a higher data rate (e.g., when the network connection associated with the higher data rate is not a default network connection) in the event that the throughput level of the packet or traffic meets the throughput threshold or data rate threshold.

For example, if the first communication connection is associated with a lower data rate (e.g., by a threshold margin) than the second communication connection, UE 120 may route traffic associated with device 515 having a throughput that meets the throughput threshold to the second communication connection (e.g., instead of the first communication connection). In some aspects, UE 120 may measure the data rate or throughput of the traffic stream from device 515 to dynamically determine when to implement the rules associated with the throughput threshold (e.g., such as when the data rate of the traffic stream from device 515 meets the throughput threshold). In some aspects, the configuration of the UE (e.g., OEM configuration) may indicate when the UE 120 is to implement rules associated with a throughput threshold. By routing traffic associated with device 515 to a network connection having a higher data rate, UE 120 may improve communication performance of the traffic when the traffic is associated with high throughput.

As shown by reference numeral 530, UE 120 may determine that a packet received from device 515 is to be routed to a default network connection (e.g., a first communication connection). For example, UE 120 may determine that one or more parameters of the packet do not satisfy or match the rule (e.g., as described above). Thus, as shown by reference numeral 535, UE 120 may route traffic to an interface associated with the first subscription and the first SIM of UE 120. As shown by reference numeral 540, UE 120 may communicate the packet using a first communication connection (e.g., associated with a first subscription and a first SIM). Thus, when a packet or traffic associated with device 515 (e.g., to be routed by UE 120) does not meet the rules indicated by the configuration of UE 120, then UE 120 may use the default network connection for communicating the packet or traffic with the wireless network.

As indicated by reference numeral 545, UE 120 may determine that packets received from device 515 are to be routed to a network connection that is not a default network connection. For example, UE 120 may determine that the packet is to be routed to a second communication connection associated with a second subscription and a second SIM of UE 120. For example, UE 120 may determine that one or more parameters of the packet (e.g., service destination address, service FQDN, port number of the service, TOS value, and/or throughput value) satisfy a rule (e.g., associated with the second subscription) indicated by the configuration of UE 120 (e.g., as described above).

Thus, as shown by reference numeral 550, UE 120 may route traffic to an interface associated with the second subscription and the second SIM of UE 120. UE 120 may route the traffic using one or more routing rules, such as rules indicated by an IP table, an extended berkeley packet filter (eBPF), and/or another routing protocol. In some aspects, UE 120 may route the traffic to an interface associated with the second subscription by performing Network Address Translation (NAT) on the data traffic packet to translate a local address associated with device 515 to a global address associated with the second subscription or the second SIM based at least in part on one or more parameter satisfaction or matching rules of the packet, as described above. For example, UE 120 may operate in DSDA mode. Additionally or alternatively, the tethered connection between UE 120 and device 515 may be an IP version 4 (IPv 4) connection, in which UE 120 performs NAT (e.g., using an IP table, an eBPF, and/or a hardware component, such as IPA) between the access point and an interface associated with the SIM of UE 120. For example, UE 120 may apply NAT rules to translate the local IP address indicated in the header of the packet to a global IP address associated with the second subscription (and/or the second SIM). In some aspects, routing may be performed by one or more protocol stacks of UE 120, such as an IP layer protocol stack and/or a transport layer protocol stack, and the like. For example, in some aspects, NAT may include performing source port translation to translate a source port indicated in a transport layer header of a packet to indicate a source port associated with a second subscription.

In some aspects, routing may be performed by hardware components of UE 120. For example, a hardware component (e.g., IPA) may be configured to filter traffic from the device 515 (e.g., as described above). The hardware component may be configured to multiplex traffic from the device 515 to a subscription or SIM associated with a rule (e.g., a rule that the traffic or packet satisfies or matches).

In some aspects, UE 120 may route traffic to an interface associated with the second subscription by performing a header translation (e.g., a full header translation) for a packet to be routed by UE 120 (e.g., a packet received from device 515). For example, UE 120 may operate in DSDA mode. Additionally or alternatively, the tethered connection between UE 120 and device 515 may be an IP version 6 (IPv 6) connection, where UE 120 does not perform NAT. For example, when using an IPv6 connection, an address (e.g., IP address) prefix may be common to all devices in the network. Thus, UE 120 may broadcast (e.g., advertise) to device 515 a prefix (e.g., via an access point of UE 120) for a default network connection (e.g., a first communication connection). Thus, when device 515 transmits a packet to UE 120 (e.g., to be routed or forwarded by UE 120), the address indicated in the header of the packet may be based at least in part on a prefix associated with a default network connection (e.g., a first communication connection). For example, an IPv6 address may include a prefix (e.g., for routing a packet to a destination) and an interface identifier (e.g., for identifying the source of the packet). Thus, each device may have a unique address, but may also include a prefix associated with the default network connection (e.g., the prefix is broadcast by UE 120). Thus, UE 120 may need to perform header translation of the packet to route the packet to a network connection that is not the default network connection (e.g., to route the packet to a second communication connection).

Thus, when the packet associated with device 515 does not meet or match the rules (e.g., as described above), UE 120 does not need to perform any header translation or NAT to route traffic to the default network connection. However, the first communication connection and the second communication connection may have different prefixes. Thus, to route traffic to an interface associated with the second subscription and/or the second SIM, UE 120 may modify the address indicated by the packet to indicate a prefix associated with the second communication connection.

For example, UE 120 may receive a packet from device 515 indicating a source address associated with the first subscription in a header of the packet (e.g., indicating a prefix associated with the first subscription and/or the first communication connection). UE 120 may perform header translation on the header of the packet to modify the source address associated with the first subscription to a source address for routing the data traffic packet to an interface (and/or to a second communication connection) associated with the second subscription. In some aspects, UE 120 may modify the header to indicate at least one of a source address associated with the second subscription (e.g., a source address for the second communication connection by UE 120) or a source address based at least in part on a prefix of the source address associated with the second subscription (e.g., the prefix associated with the second communication connection may be used by UE 120 to generate the new source address). In some aspects, if UE 120 generates a new source address using a prefix associated with the second communication connection, UE 120 may perform one or more actions to determine or ensure that the generated new source address is not a copy of an already existing source address. In some aspects, UE 120 may perform one or more transport layer header checksum updates based at least in part on modifying a packet source address in an IP header of the packet (e.g., as described above).

As described above, in some aspects, UE 120 may perform header translation of a packet associated with device 515 (e.g., routing the packet to a second communication connection) using a protocol stack of UE 120 and/or a hardware component of UE 120 (e.g., IPA). For example, the hardware components of UE 120 may be configured to filter traffic received from device 515, identify traffic to be routed to a non-default data connection (e.g., a second communication connection), perform header conversion, and route traffic to an interface associated with the non-default data connection.

In some aspects, UE 120 may route traffic to an interface associated with the second subscription by performing a DDS handoff. For example, UE 120 may operate in DSDS mode. As described above, the first subscription of UE 120 may be a DDS subscription such that the first communication connection is an active connection in DSDS mode. UE 120 may route traffic to an interface associated with the second subscription by performing a DDS handoff to modify the first subscription to be non-DDS for UE 120 and to modify the second subscription to be DDS for UE 120. The DDS handoff may be a permanent DDS handoff or a temporary DDS handoff. By performing DDS handoff, UE 120 may be able to establish an active (e.g., connected) session over the second communication connection and route traffic for the tethered device (e.g., device 515) using the second communication connection.

In some aspects, UE 120 may have tethered connections with multiple devices. Additionally or alternatively, the tethered device can communicate traffic over a tethered connection associated with multiple services and/or multiple applications. Thus, in some cases, UE 120 may receive first traffic that is better served by a non-default subscription (e.g., traffic that meets or matches the rules described above) and second traffic that may not be better served by a non-default subscription (e.g., traffic that does not meet or match the rules described above). However, in DSDS mode, only one subscription may be active at a time. Thus, to determine which subscription should be associated with an active network connection in the DSDS mode (e.g., which subscription will be the DDS of UE 120), UE 120 may determine the DDS of UE 120 from the first subscription or the second subscription based at least in part on the time that traffic arrives at UE 120 in a first-come-first-serve manner and/or a priority associated with traffic at UE 120, etc. For example, if the first traffic arrives at UE 120 before the second traffic, UE 120 may perform a DDS handoff to enable the first traffic to be routed to the second subscription and/or the second communication connection. Additionally or alternatively, if the first traffic is associated with a higher priority than the priority of the second traffic, UE 120 may perform a DDS handoff to enable the first traffic to be routed to the second subscription and/or the second communication connection.

In some aspects, UE 120 may determine whether to route traffic associated with the tethered device (e.g., device 515) to the non-default network connection based at least in part on the measurements of the non-default network connection. For example, UE 120 may perform measurements of measurement parameters (e.g., RSRP parameters, RSRQ parameters, and/or signal-to-noise ratio (SNR) parameters) of the second communication connection. UE 120 may determine whether the value of the measurement parameter meets a threshold (e.g., indicated by a configuration of UE 120 such as an OEM configuration). If the value of the measurement parameter meets the threshold, UE 120 may route traffic (e.g., packets) associated with device 515 to the second communication connection (e.g., in a similar manner as described herein). If the value of the measurement parameter does not satisfy the threshold, UE 120 may refrain from routing traffic associated with device 515 to the second communication connection according to the configuration based at least in part on a determination that the value of the measurement parameter does not satisfy the threshold. Thus, when a non-default network connection is associated with a bad service (e.g., a measurement parameter that does not meet a threshold), UE 120 may avoid routing traffic associated with device 515 to the non-default network connection. As a result, communication performance of traffic associated with device 515 may be improved.

Although the above aspects have been described in connection with routing traffic to a subscription or SIM that is not the default subscription or SIM for data traffic, similar techniques may be applied to route traffic received from device 515 to a network slice that is not the default network slice for data traffic. For example, as described above, network slicing may allow multiple virtual networks to run on a single physical network to support multiple services, applications, and/or entities (e.g., end users, customers, such as organizations providing services to end users of a wireless telecommunications system). Thus, a wireless network may be able to serve different industries and/or areas with different service requirements, which may be reflected by different quality of service (QoS) requirements for different aspects of service performance and/or quality represented by corresponding different QoS parameters. For example, UE 120 may be associated with multiple network slices for a single network connection, such as an enhanced mobile broadband (eMBB) service slice, an ultra-reliable low latency (URLLC) service slice, and/or a mobile internet of things (iot) service slice, among others.

As described above, the communication connection (e.g., the first communication connection and/or the second communication connection) may be associated with a default network slice for data traffic (e.g., for internet traffic). In a typical scenario, UE 120 may use a default network slice to route traffic for the tethered device (e.g., device 515). However, if the traffic (e.g., packets) from device 515 meets or matches the rules (e.g., in a similar manner as described above), UE 120 may route the traffic associated with device 515 to a different network slice (e.g., instead of the default network slice). This may enable traffic to experience improved performance provided by different network slices (e.g., such as incentives associated with services or applications of traffic provided by different network slices). For example, traffic associated with device 515 may be associated with a low-latency application or service (e.g., a gaming application or service, or another low-latency service). Thus, a low latency network slice (e.g., a URLLC network slice) may better service traffic than a default network slice (e.g., an eMBB network slice). Thus, UE 120 may route traffic associated with device 515 to a different network slice (e.g., a low latency network slice) to improve communication performance of traffic associated with device 515.

In some aspects, one or more rules for routing tethered traffic to a network slice that is not a default network slice may be indicated in a configuration (e.g., OEM configuration) of UE 120. Additionally or alternatively, one or more rules may be indicated in a UE routing policy (urs p). For example, UE 120 may receive an indication of one or more urs rules for identifying traffic to be routed to non-default network slices. UE 120 may route traffic associated with device 515 to a network slice that is not a default network slice based at least in part on determining that one or more parameters of the packet received from device 515 satisfy at least one of a rule indicated by a configuration (e.g., OEM configuration) and/or a urs rule of the one or more urs rules.

For example, in some cases, traffic associated with the tethered device (e.g., device 515) may be routed to a default network connection (e.g., a network connection associated with the first SIM and/or the first subscription) and to a network slice associated with a default network slice that is not associated with the default network connection. In some aspects, UE 120 may route traffic associated with the tethered device (e.g., device 515) to subscriptions that are not default subscriptions of UE 120 and/or to network slices that are not default network slices for network connections. For example, in some aspects, UE 120 may route the packet (e.g., received from device 515) to a second subscription of UE 120 (e.g., to an interface of the second subscription and/or to a second communication connection). Additionally or alternatively, UE 120 may route the packet to a network slice that is not the default network slice for data traffic (e.g., a network slice associated with the second communication connection). In this manner, UE 120 may ensure that traffic associated with the tethered device is routed to use subscriptions and/or network slices that provide optimal performance (e.g., stimulated performance, reduced latency performance, and/or improved data rate performance) for the traffic.

As indicated by reference numeral 555, UE 120 may communicate traffic (e.g., packets) associated with device 515 using a second communication connection (e.g., a non-default data connection for UE 120 and/or a network connection associated with a second subscription). For example, based at least in part on routing traffic associated with device 515 to an interface associated with a second subscription (e.g., as described above), UE 120 may use a second communication connection to transmit traffic associated with device 515 to second base station 510. Additionally or alternatively, UE 120 may use the non-default network slice to transmit traffic (e.g., packets) associated with device 515 based at least in part on routing the traffic to the non-default network slice (e.g., a network slice of the first communication connection or the second communication connection) as described above.

As a result, UE 120 may be implemented to route traffic associated with the tethered device (e.g., device 515) to a subscription or network slice that best services traffic associated with the tethered device. For example, UE 120 may be implemented to use data connections or network slices other than default data connections or default network slices for traffic associated with tethered devices. By enabling UE 120 to filter traffic associated with the tethered device to data connections or network slices other than the default data connections or default network slices, communication performance of the traffic may be improved. For example, the tethered device can be implemented to achieve the benefits of incentives associated with using subscriptions that are not default data subscriptions for UE 120. Additionally or alternatively, the tethered device can experience improved data rates or reduced latency by using data connections or network slices that better service traffic associated with the tethered device in addition to default data connections or default network slices.

As indicated above, fig. 5 is provided as an example. Other examples may differ from the example described with respect to fig. 5.

Fig. 6 is a diagram illustrating an example 600 of subscription-based or network slice-based traffic differentiation and routing with multiple access points in accordance with the present disclosure. As shown in fig. 6, UE 120 may communicate with a first base station 605 and a second base station 610. For example, UE 120 may be a multi-SIM UE (e.g., in a similar manner as described above in connection with fig. 4). The first base station 605 may be associated with a first SIM (and/or a first subscription) of the UE 120. For example, the first base station 605 may provide a cell of a wireless network associated with a first network operator. The first network operator may be associated with a first SIM (and/or a first subscription) of UE 120. Similarly, the second base station 610 may be associated with a second SIM (and/or a second subscription) of the UE 120. For example, the second base station 610 may provide a cell of a wireless network associated with a second network operator. The second network operator may be associated with a second SIM (and/or a second subscription) of UE 120. The first base station 605 and/or the second base station 610 may be a base station 110 and/or a network entity, such as a CU, DU, RU, and/or the like.

As shown in fig. 6, UE 120 may provide a tethered service and/or a hot spot service (e.g., in a similar manner as described above in connection with fig. 3, 4, and 5). For example, UE 120 may communicate with device 615. UE 120 may provide a wireless (e.g., cellular) network connection for device 615 to enable device 615 to access a wireless network associated with UE 120 (e.g., in a similar manner as described above in connection with fig. 3 and 4). For example, UE 120 may route traffic associated with device 615 to and/or from a wireless network (e.g., associated with first base station 605 or second base station 610).

For example, as shown by reference numeral 620, UE 120 may establish a first communication connection with a first base station 605. The first communication connection may be associated with a first subscription and/or a first SIM of UE 120. As indicated by reference numeral 625, UE 120 may establish a second communication connection with second base station 610. The second communication connection may be associated with a second subscription and/or a second SIM of UE 120.

As shown in fig. 6, UE 120 may include a first access point (e.g., a first WLAN access point and/or a first Wi-Fi access point) and a second access point (e.g., a second WLAN access point and/or a second Wi-Fi access point). The first access point and the second access point may be separate access points. For example, a first access point may provide a first WLAN associated with UE 120 and a second access point may provide a second WLAN associated with UE 120. As shown in fig. 6, the first access point and the second access point may be associated with separate communication connections (e.g., to a wireless network). For example, UE 120 may establish a connection of the first access point with the interface of the first subscription (e.g., such that the first access point is associated with the first communication connection and/or a network operator associated with the first communication connection). Similarly, UE 120 may establish a connection of the second access point with the interface of the second subscription (e.g., such that the second access point is associated with the second communication connection and/or a network operator associated with the second communication connection).

As shown by reference numeral 630, UE 120 may transmit (e.g., broadcast) an identifier associated with the first access point. The first identifier may be a network identifier associated with a WLAN or Wi-Fi network provided by the first access point. The first identifier may indicate that the first access point is associated with a first subscription. In some aspects, the first identifier may be an SSID of a first access point that indicates or identifies the first subscription.

As shown by reference numeral 635, UE 120 may transmit (e.g., broadcast) an identifier associated with the second access point. The second identifier may be a network identifier associated with a WLAN or Wi-Fi network provided by the second access point. The second identifier may indicate that the second access point is associated with a second subscription. In some aspects, the second identifier may be an SSID of a second access point that indicates or identifies the second subscription. Thus, the device 615 may be implemented to identify (based at least in part on the first identifier and the second identifier) that establishing a tethered connection using the first access point will result in the UE 120 routing traffic associated with the device 615 to the first subscription and/or the first communication connection. Similarly, the device 615 may be implemented to identify (based at least in part on the first identifier and the second identifier) that establishing a tethered connection using the second access point will result in the UE 120 routing traffic associated with the device 615 to the second subscription and/or the second communication connection.

As indicated by reference numeral 640, the device 615 can select an access point (e.g., WLAN or Wi-Fi network) to be used to establish a tethered connection with the UE 120. For example, the device 615 may select an access point based at least in part on the first identifier and the second identifier broadcast by the UE 120. In some aspects, the device 615 may select an access point based at least in part on user input. In some aspects, the device 615 may select an access point based at least in part on an application or service executing on the device 615. For example, device 615 may be capable of selecting an access point of UE 120 that is associated with a subscription that will provide improved services (e.g., stimulated services) for traffic associated with device 615.

As shown by reference numeral 645, the device 615 can transmit, and the UE 120 can receive a connection establishment request to establish a tethered connection with the UE 120. As shown in fig. 6, if the device 615 selects a first access point to establish a tethered connection, a request to establish a tethered connection may be associated with the first access point. UE 120 may establish a tethered connection with device 615 using a first access point (e.g., and a WLAN or Wi-Fi network provided by the first access point). UE 120 may route traffic associated with device 615 to the first subscription and/or the first communication connection.

Alternatively, if the device 615 selects a second access point to establish the tethered connection, the request to establish the tethered connection may be associated with the second access point. UE 120 may establish a tethered connection with device 615 using a second access point (e.g., and a WLAN or Wi-Fi network provided by the second access point). UE 120 may route traffic associated with device 615 to a second subscription and/or a second communication connection. As a result, by broadcasting the first identifier and the second identifier that indicate which subscription of UE 120 the access point is associated with, UE 120 may enable traffic for the tethered device to be routed to the subscription that provides the best service for that traffic.

As indicated above, fig. 6 is provided as an example. Other examples may differ from the example described with respect to fig. 6.

Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a UE, in accordance with the present disclosure. Example process 700 is an example in which a UE (e.g., UE 120) performs operations associated with subscription-based or network slice-based traffic differentiation and routing.

As shown in fig. 7, in some aspects, process 700 may include establishing a first communication connection associated with a first subscription of a UE or associated with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE (block 710). For example, the UE (e.g., using the communication connection establishment component 908 depicted in fig. 9) may establish a first communication connection associated with a first subscription of the UE or with a first network slice, where the first communication connection is a default connection for the UE for data traffic, as described above.

As further shown in fig. 7, in some aspects, process 700 may include establishing a second communication connection associated with a second subscription of the UE or associated with a second network slice (block 720). For example, the UE (e.g., using the communication connection establishment component 908 depicted in fig. 9) may establish a second communication connection associated with a second subscription of the UE or associated with a second network slice, as described above.

As further shown in fig. 7, in some aspects, process 700 may include receiving a data traffic packet associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection (block 730). For example, a UE (e.g., using the receiving component 902 depicted in fig. 9) may receive a data traffic packet associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection, as described above.

As further shown in fig. 7, in some aspects, process 700 may include routing the data traffic packet to the second communication connection based at least in part on the one or more parameters (block 740). For example, the UE (e.g., using traffic routing component 910 depicted in fig. 9) may route the data traffic packet to the second communication connection based at least in part on the one or more parameters, as described above.

As further shown in fig. 7, in some aspects, process 700 may include transmitting a data traffic packet using a second communication connection (block 750). For example, the UE (e.g., using the transmission component 904 depicted in fig. 9) may transmit the data traffic packet using the second communication connection, as described above.

Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in conjunction with one or more other processes described elsewhere herein.

In a first aspect, process 700 includes determining (e.g., using determining component 912 depicted in fig. 9) whether one or more parameters satisfy a rule indicated by a configuration of a UE, and determining (e.g., using determining component 912 depicted in fig. 9) whether to route the data traffic packet to the first communication connection or to the second communication connection based at least in part on the determination of whether the one or more parameters satisfy the rule indicated by the configuration.

In a second aspect, alone or in combination with the first aspect, routing the data traffic packet to the second communication connection comprises: the method may further include performing (e.g., using traffic routing component 910 depicted in fig. 9) NAT on the data traffic packet based at least in part on the one or more parameters satisfying a rule to translate a local address associated with the device to a global address associated with the second subscription, and routing (e.g., using traffic routing component 910 depicted in fig. 9) the data traffic packet to the second communication connection for the second subscription based at least in part on the performance of the NAT.

In a third aspect, alone or in combination with one or more of the first and second aspects, performing the NAT comprises: NAT rules are applied (e.g., using traffic routing component 910 depicted in fig. 9) to translate the local IP address indicated in the header of the data traffic packet to a global IP address associated with the second subscription based at least in part on the one or more parameter satisfaction rules.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the wireless local area network is an IPv4 network.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, receiving the data traffic packet includes receiving (e.g., using receiving component 902 depicted in fig. 9) the data traffic packet indicating a source address associated with the first subscription in a header of the data traffic packet, and routing the data traffic packet to the second communication connection includes performing (e.g., using traffic routing component 910 depicted in fig. 9) header translation on the header of the data traffic packet to modify the source address associated with the first subscription to a source address for routing the data traffic packet to the second subscription.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, performing the header conversion on the header of the data traffic packet includes at least one of modifying (e.g., using traffic routing component 910 depicted in fig. 9) the header to indicate a source address associated with the second subscription or a source address based at least in part on a prefix of the source address associated with the second subscription.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, performing the header conversion on the header of the data traffic packet includes updating (e.g., using traffic routing component 910 depicted in fig. 9) at least one of an internet protocol layer header of the data traffic packet or a transport layer header of the data traffic packet.

In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the wireless local area network is an Ipv6 network.

In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the configuration of the UE indicates one or more rules for identifying traffic to be routed to the UE for non-default data subscriptions.

In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the one or more rules indicate at least one of: a service destination address of traffic to be routed to the non-default data subscription, a service FQDN of traffic to be routed to the non-default data subscription, a port number of traffic to be routed to the non-default data subscription, or a service type value of traffic to be routed to the non-default data subscription.

In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the configuration of the UE indicates one or more rules specific to an identifier associated with the second subscription.

In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the identifier comprises at least one of a mobile country code or a mobile network code.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, routing the data traffic packet to the second communication connection comprises: determining (e.g., using the determining component 912 depicted in fig. 9) that the one or more parameters satisfy the rule indicated by the configuration, and routing (e.g., using the traffic routing component 910 depicted in fig. 9) the data traffic packet to the second network slice based at least in part on the determination that the one or more parameters satisfy the rule indicated by the configuration.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the process 700 includes receiving (e.g., using the receiving component 902 depicted in fig. 9) an indication of one or more urs rules for identifying traffic to be routed to a non-default network slice, and routing the data traffic packet to the second communication connection includes determining (e.g., using the determining component 912 depicted in fig. 9) that the one or more parameters satisfy at least one of the rules indicated by the configuration or the one or more urs rules.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, routing the data traffic packet to the second communication connection comprises: routing (e.g., using traffic routing component 910 depicted in fig. 9) the data traffic packet to the second subscription of the UE, and routing (e.g., using traffic routing component 910 depicted in fig. 9) the data traffic packet to the second network slice, wherein the second network slice is a non-default network slice associated with the second subscription.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the process 700 includes measuring (e.g., using the measurement component 914 depicted in fig. 9) a measurement parameter of the second communication connection.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, routing the data traffic packet to the second communication connection includes determining (e.g., using the determining component 912 depicted in fig. 9) that a value of the measurement parameter meets a threshold, and routing (e.g., using the traffic routing component 910 depicted in fig. 9) the data traffic packet to the second communication connection based at least in part on a determination that the value of the measurement parameter meets the threshold.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the process 700 includes determining (e.g., using the determining component 912 depicted in fig. 9) that the value of the measurement parameter does not satisfy a threshold, and suppressing (e.g., using the traffic routing component 910 depicted in fig. 9) routing traffic to the second communication connection based at least in part on a determination that the value of the measurement parameter does not satisfy the threshold.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the first subscription is a DDS and the second subscription is not a DDS, and routing the data traffic packet to the second communication connection includes performing (e.g., using traffic routing component 910 depicted in fig. 9) a DDS handoff to modify the first subscription to be not a DDS and to modify the second subscription to be a DDS.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the UE operates in a DSDS mode and routing the data traffic packet to the second communication connection includes determining (e.g., using the determining component 912 depicted in fig. 9) a default data subscription from the first subscription or the second subscription based at least in part on a time at which traffic in a first-come-first-service manner arrives at the UE or a priority associated with the traffic at the UE.

In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the one or more parameters indicate a throughput level associated with the data traffic packet, and routing the data traffic packet to the second communication connection comprises: determining (e.g., using the determining component 912 depicted in fig. 9) that the throughput level associated with the data traffic packet meets a throughput threshold, and routing (e.g., using the traffic routing component 910 depicted in fig. 9) the data traffic packet to the second communication connection based at least in part on a determination that the throughput level associated with the data traffic packet meets the throughput threshold.

In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the first communication connection is associated with a first RAT and the second communication connection is associated with a second RAT.

In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the second RAT is at least one of a 5G RAT, a new radio RAT, or a millimeter wave RAT.

In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the process 700 includes measuring (e.g., using the measurement component 914 depicted in fig. 9) a data rate associated with a traffic flow received from the device, and routing (e.g., using the traffic routing component 910 depicted in fig. 9) the data traffic packet to the second communication connection based at least in part on the measurement of the data rate meeting the throughput threshold.

In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, the UE operates in DSDS mode and routing the data traffic packet to the second communication connection includes performing (e.g., using traffic routing component 910 depicted in fig. 9) a DDS to switch the DDS of the UE from the first subscription to the second subscription.

In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the UE is operating in a multi-subscriber identity module mode.

In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, the UE is operating in a dual subscriber identity module dual active mode.

In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, the UE is operating in a single subscriber identity module mode.

In a twenty-ninth aspect, alone or in combination with one or more of the first through twenty-eighth aspects, routing the data traffic packet to the second communication connection includes routing the data traffic packet to the second communication via a hardware component of the UE (e.g., using traffic routing component 910 depicted in fig. 9).

While fig. 7 shows example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 7. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

Fig. 8 is a diagram illustrating an example process 800 performed, for example, by a UE, in accordance with the present disclosure. The example process 800 is an example in which a UE (e.g., the UE 120) performs operations associated with subscription-based or network slice-based traffic differentiation and routing.

As shown in fig. 8, in some aspects, process 800 may include establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point (block 810). For example, the UE (e.g., using the communication connection establishment component 908 depicted in fig. 9) can establish a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point, as described above.

As further shown in fig. 8, in some aspects, process 800 may include establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point (block 820). For example, the UE (e.g., using the communication connection establishment component 908 depicted in fig. 9) can establish a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point, as described above.

As further shown in fig. 8, in some aspects, process 800 may include transmitting a first identifier associated with a first access point and a second identifier associated with a second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription (block 830). For example, the UE (e.g., using the transmission component 904 depicted in fig. 9) may transmit a first identifier associated with a first access point and a second identifier associated with a second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription, as described above.

As further shown in fig. 8, in some aspects, process 800 may include receiving a connection establishment request from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request for establishing a coherent connection for the device using the first communication connection or the second communication connection (block 840). For example, the UE (e.g., using the receiving component 902 depicted in fig. 9) may receive a connection establishment request from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request to establish a tethered connection for the device using the first communication connection or the second communication connection, as described above.

Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in conjunction with one or more other processes described elsewhere herein.

In a first aspect, the process 800 includes establishing (e.g., using the communication connection establishment component 908 depicted in fig. 9) a tethered connection for a device using either the first communication connection or the second communication connection based at least in part on receipt of the connection establishment request.

In a second aspect, either alone or in combination with the first aspect, the first communication connection and the second communication connection are separate communication connections.

In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting the first identifier associated with the first access point and the second identifier associated with the second access point comprises: a first SSID of the first access point indicating the first subscription is transmitted (e.g., using the transmission component 904 depicted in fig. 9), and a second SSID of the second access point indicating the second subscription is transmitted (e.g., using the transmission component 904 depicted in fig. 9).

In a fourth aspect, alone or in combination with one or more of the first to third aspects, receiving the connection establishment request is based at least in part on traffic to be routed by the UE from the device being associated with a subscription of the first subscription or the second subscription.

While fig. 8 shows example blocks of the process 800, in some aspects, the process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 8. Additionally or alternatively, two or more blocks of process 800 may be performed in parallel.

Fig. 9 is a block diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a UE or the UE may include the apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that can be in communication with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 900 may use a receiving component 902 and a transmitting component 904 to communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device). As further shown, the apparatus 900 can include one or more of a communication connection establishment component 908, a traffic routing component 910, a determination component 912, and/or a measurement component 914, among others.

In some aspects, apparatus 900 may be configured to perform one or more operations described herein in connection with fig. 5 and 6. Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein (such as process 700 of fig. 7, process 800 of fig. 8, or a combination thereof). In some aspects, apparatus 900 and/or one or more components shown in fig. 9 may include one or more components of the UE described above in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 9 may be implemented within one or more of the components described above in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executed by a controller or processor to perform the functions or operations of the component.

The receiving component 902 can receive a communication (such as a reference signal, control information, data communication, or a combination thereof) from a device 906. The receiving component 902 can provide the received communication to one or more other components of the apparatus 900. In some aspects, the receiving component 902 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memories, or a combination thereof for a UE as described above in connection with fig. 2.

The transmission component 904 can transmit a communication (such as a reference signal, control information, data communication, or a combination thereof) to the device 906. In some aspects, one or more other components of apparatus 900 may generate a communication and may provide the generated communication to transmission component 904 for transmission to apparatus 906. In some aspects, the transmission component 904 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, etc.) on the generated communication and can transmit the processed signal to the device 906. In some aspects, the transmission component 904 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the UE described above in connection with fig. 2. In some aspects, the transmission component 904 can be co-located with the reception component 902 in a transceiver.

The communication connection establishment component 908 can establish a first communication connection associated with a first subscription of a UE or associated with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE. The communication connection establishment component 908 can establish a second communication connection associated with a second subscription of the UE or associated with a second network slice. The receiving component 902 may receive a data traffic packet associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection. The traffic routing component 910 may route the data traffic packet to the second communication connection based at least in part on the one or more parameters. The transmission component 904 can transmit the data traffic packet using the second communication connection.

The determining component 912 may determine whether one or more parameters satisfy a rule indicated by a configuration of the UE. The determining component 912 may determine whether to route the data traffic packet to the first communication connection or to the second communication connection based at least in part on a determination of whether one or more parameters satisfy a rule indicated by the configuration.

The receiving component 902 may receive an indication of one or more urs rules for identifying traffic to be routed to a non-default network slice.

The measurement component 914 can measure a measurement parameter of the second communication connection. The determination component 912 may determine that the value of the measurement parameter does not satisfy the threshold. The traffic routing component 910 may refrain from routing traffic to the second communication connection according to the configuration of the UE based at least in part on a determination that the value of the measured parameter does not satisfy the threshold.

The measurement component 914 can measure a data rate associated with a traffic stream received from a device. Traffic routing component 910 may route data traffic packets to a second communication connection based at least in part on the measurement of the data rate meeting a throughput threshold.

The communication connection establishment component 908 can establish a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point. The communication connection establishment component 908 can establish a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point. The transmission component 904 can transmit a first identifier associated with a first access point and a second identifier associated with a second access point, wherein the first identifier indicates that the first access point is associated with a first subscription and the second identifier indicates that the second access point is associated with a second subscription. The receiving component 902 can receive a connection establishment request from a device based at least in part on transmission of the first identifier and the second identifier, the connection establishment request for establishing a tethered connection for the device using the first communication connection or the second communication connection.

The communication connection establishment component 908 can establish a tethered connection for the device using the first communication connection or the second communication connection based at least in part upon receipt of the connection establishment request.

The number and arrangement of components shown in fig. 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in fig. 9. Further, two or more components shown in fig. 9 may be implemented within a single component, or a single component shown in fig. 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (e.g., one or more components) shown in fig. 9 may perform one or more functions described as being performed by another set of components shown in fig. 9.

The following provides an overview of some aspects of the disclosure:

aspect 1: a wireless communication method performed by a User Equipment (UE), comprising: establishing a first communication connection associated with a first subscription of the UE or with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE; establishing a second communication connection associated with a second subscription of the UE or with a second network slice; receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection; routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and transmitting the data traffic packet using the second communication connection.

Aspect 2: the method of aspect 1, further comprising: determining whether the one or more parameters satisfy a rule indicated by a configuration of the UE; and determining whether to route the data traffic packet to the first communication connection or to the second communication connection based at least in part on a determination of whether the one or more parameters satisfy the rule indicated by the configuration.

Aspect 3: the method of any of aspects 1-2, wherein routing the data traffic packet to the second communication connection comprises: performing Network Address Translation (NAT) on the data traffic packet based at least in part on the one or more parameters satisfying a rule to translate a local address associated with the device to a global address associated with the second subscription; and routing the data traffic packet to the second communication connection for the second subscription based at least in part on execution of the NAT.

Aspect 4: the method of aspect 3, wherein performing the NAT comprises: NAT rules are applied to translate a local Internet Protocol (IP) address indicated in the header of the data traffic packet to a global IP address associated with the second subscription based at least in part on the one or more parameter satisfaction rules.

Aspect 5: the method of any of aspects 3-4, wherein the wireless local area network is an Internet Protocol (IP) version 4 (IPv 4) network.

Aspect 6: the method of any of aspects 1-2, wherein receiving the data traffic packet comprises: receiving the data traffic packet indicating a source address associated with the first subscription in a header of the data traffic packet; and wherein routing the data traffic packet to the second communication connection comprises: header translation is performed on the header of the data traffic packet to modify a source address associated with the first subscription to a source address for routing the data traffic packet to the second subscription.

Aspect 7: the method of aspect 6, wherein performing the header conversion on the header of the data traffic packet comprises: the header is modified to indicate at least one of the source address associated with the second subscription or a source address based at least in part on a prefix of the source address associated with the second subscription.

Aspect 8: the method of any of aspects 6-7, wherein performing the header conversion on the header of the data traffic packet comprises: at least one of an internet protocol layer header of the data traffic packet or a transport layer header of the data traffic packet is updated.

Aspect 9: the method of any of aspects 6-8, wherein the wireless local area network is an Internet Protocol (IP) version 6 (IPv 6) network.

Aspect 10: the method of any of aspects 1-9, wherein the configuration of the UE indicates one or more rules for identifying traffic to be routed to the UE for non-default data subscriptions.

Aspect 11: the method of aspect 10, wherein the one or more rules indicate at least one of: a service destination address of traffic to be routed to the non-default data subscription, a service Fully Qualified Domain Name (FQDN) of traffic to be routed to the non-default data subscription, a port number of traffic to be routed to the non-default data subscription, or a service type value of traffic to be routed to the non-default data subscription.

Aspect 12: the method of any of aspects 1-11, wherein the configuration of the UE indicates one or more rules specific to an identifier associated with the second subscription.

Aspect 13: the method of aspect 12, wherein the identifier comprises at least one of a mobile country code or a mobile network code.

Aspect 14: the method of any of aspects 1-13, wherein routing the data traffic packet to the second communication connection comprises: determining that the one or more parameters satisfy a rule indicated by the configuration; and route the data traffic packet to the second network slice based at least in part on a determination that the one or more parameters satisfy the rule indicated by the configuration.

Aspect 15: the method of any one of aspects 1-14, further comprising: receive an indication of one or more UE routing policy (urs) rules for identifying traffic to be routed to a non-default network slice; and wherein routing the data traffic packet to the second communication connection comprises: the one or more parameters are determined to satisfy at least one of a rule indicated by the configuration or a urs rule of the one or more urs rules.

Aspect 16: the method of any of aspects 1-15, wherein routing the data traffic packet to the second communication connection comprises: routing the data traffic packet to the second subscription of the UE; and routing the data traffic packet to the second network slice, wherein the second network slice is a non-default network slice associated with the second subscription.

Aspect 17: the method of any one of aspects 1-16, further comprising: a measurement parameter of the second communication connection is measured.

Aspect 18: the method of aspect 17, wherein routing the data traffic packet to the second communication connection comprises: determining that the value of the measured parameter meets a threshold; and route the data traffic packet to the second communication connection based at least in part on a determination that the value of the measurement parameter meets the threshold.

Aspect 19: the method of aspect 17, further comprising: determining that the value of the measured parameter does not meet a threshold; and refrain from routing traffic to the second communication connection according to the configuration of the UE based at least in part on a determination that the value of the measurement parameter does not satisfy the threshold.

Aspect 20: the method of any of aspects 1-19, wherein the first subscription is a Default Data Subscription (DDS) and the second subscription is a non-DDS, and wherein routing the data traffic packet to the second communication connection comprises: a DDS switch is performed to modify the first subscription to not be DDS and the second subscription to be DDS.

Aspect 21: the method of any of aspects 1-20, wherein the UE is operating in a dual Subscriber Identity Module (SIM) dual standby (DSDS) mode, and wherein routing the data traffic packet to the second communication connection comprises: a default data subscription is determined from the first subscription or the second subscription based at least in part on a time of arrival of traffic at the UE in a first-come-first-serve manner or a priority associated with the traffic at the UE.

Aspect 22: the method of any of aspects 1-21, wherein the one or more parameters indicate a throughput level associated with the data traffic packet, and wherein routing the data traffic packet to the second communication connection comprises: determining that the throughput level associated with the data traffic packet meets a throughput threshold; and route the data traffic packet to the second communication connection based at least in part on a determination that the throughput level associated with the data traffic packet meets the throughput threshold.

Aspect 23: the method of aspect 22, wherein the first communication connection is associated with a first Radio Access Technology (RAT) and the second communication connection is associated with a second RAT.

Aspect 24: the method of aspect 23, wherein the second RAT is at least one of a 5G RAT, a new radio RAT, or a millimeter wave RAT.

Aspect 25: the method of any of aspects 22-24, further comprising: measuring a data rate associated with a traffic pattern received from the device; and route the data traffic packet to the second communication connection based at least in part on the measurement of the data rate meeting the throughput threshold.

Aspect 26: the method of any of aspects 22-25, wherein the UE is operating in a dual Subscriber Identity Module (SIM) dual standby (DSDS) mode, and wherein routing the data traffic packet to the second communication connection comprises: a Default Data Subscription (DDS) switch is performed to switch the DDS of the UE from the first subscription to the second subscription.

Aspect 27: the method of any of aspects 1-26, wherein the UE is operating in a multi-subscriber identity module mode.

Aspect 28: the method of any of aspects 1-27, wherein the UE is operating in a dual subscriber identity module dual active mode.

Aspect 29: the method of any of aspects 1-26, wherein the UE is operating in a single subscriber identity module mode.

Aspect 30: the method of any of aspects 1-29, wherein routing the data traffic packet to the second communication connection comprises: the data traffic packet is routed to the second communication via a hardware component of the UE.

Aspect 31: a wireless communication method performed by a User Equipment (UE), comprising: establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point; establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point; transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and receiving a connection establishment request from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request for establishing a tethered connection for the device using the first communication connection or the second communication connection.

Aspect 32: the method of aspect 31, further comprising: the tethered connection is established for the device using the first communication connection or the second communication connection based at least in part on the receipt of the connection establishment request.

Aspect 33: the method of any of aspects 31-32, wherein the first communication connection and the second communication connection are separate communication connections.

Aspect 34: the method of any of aspects 31-33, wherein transmitting the first identifier associated with the first access point and the second identifier associated with the second access point comprises: transmitting a first Service Set Identifier (SSID) of the first access point indicating the first subscription; and transmitting a second SSID of the second access point indicating the second subscription.

Aspect 35: the method of any of aspects 31-34, wherein receiving the connection establishment request is based at least in part on traffic to be routed by the UE from the device being associated with a subscription of the first subscription or the second subscription.

Aspect 36: an apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1-30 and/or 31-35.

Aspect 37: an apparatus for wireless communication comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more of aspects 1-30 and/or 31-35.

Aspect 38: an apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1-30 and/or 31-35.

Aspect 39: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method as in one or more of aspects 1-30 and/or 31-35.

Aspect 40: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 1-30 and/or 31-35.

The foregoing disclosure provides insight and description, but is not intended to be exhaustive or to limit aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and/or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and/or a combination of hardware and software. It will be apparent that the systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to the specific software code-it being understood that software and hardware can be designed to implement the systems and/or methods based at least in part on the description herein.

As used herein, satisfying a threshold may refer to a value greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, etc., depending on the context.

Although specific combinations of features are recited in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Indeed, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each of the dependent claims listed below may depend directly on only one claim, disclosure of various aspects includes each dependent claim in combination with each other claim of the set of claims. As used herein, a phrase referring to a list of items "at least one of" refers to any combination of these items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a. b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having multiple identical elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Moreover, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more items referenced in conjunction with the article "the" and may be used interchangeably with "one or more". Furthermore, as used herein, the terms "set (collection)" and "group" are intended to include one or more items (e.g., related items, non-related items, or a combination of related and non-related items), and may be used interchangeably with "one or more. Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "having," "containing," "including," and the like are intended to be open ended terms. Furthermore, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Also, as used herein, the term "or" when used in a sequence is intended to be inclusive and may be used interchangeably with "and/or" unless otherwise specifically stated (e.g., where used in conjunction with "any one of" or "only one of").

Claims (30)

1. A wireless communication method performed by a User Equipment (UE), comprising:

establishing a first communication connection associated with a first subscription of the UE or with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE;

establishing a second communication connection associated with a second subscription of the UE or with a second network slice;

receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection;

routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and

the data traffic packet is transmitted using the second communication connection.

2. The method of claim 1, further comprising:

determining whether the one or more parameters satisfy a rule indicated by a configuration of the UE; and

determining whether to route the data traffic packet to the first communication connection or to the second communication connection based at least in part on a determination of whether the one or more parameters satisfy the rule indicated by the configuration.

3. The method of claim 1, wherein routing the data traffic packet to the second communication connection comprises:

performing Network Address Translation (NAT) on the data traffic packet based at least in part on the one or more parameters satisfying a rule to translate a local address associated with the device to a global address associated with the second subscription; and

the data traffic packet is routed to the second communication connection for the second subscription based at least in part on execution of the NAT.

4. The method of claim 1, wherein receiving the data traffic packet comprises:

receiving the data traffic packet indicating a source address associated with the first subscription in a header of the data traffic packet; and is also provided with

Wherein routing the data traffic packet to the second communication connection comprises:

header translation is performed on the header of the data traffic packet to modify a source address associated with the first subscription to a source address for routing the data traffic packet to the second subscription.

5. The method of claim 4, wherein performing the header conversion on the header of the data traffic packet comprises:

The header is modified to indicate at least one of a source address associated with the second subscription or a source address based at least in part on a prefix of the source address associated with the second subscription.

6. The method of claim 1, wherein the configuration of the UE indicates one or more rules for identifying traffic to be routed to the UE for non-default data subscriptions.

7. The method of claim 6, wherein the one or more rules indicate at least one of:

a service destination address of traffic to be routed to the non-default data subscription,

a Fully Qualified Domain Name (FQDN) for service to be routed to traffic of the non-default data subscription,

port number of traffic to be routed to the non-default data subscription, or

A service type value of traffic to be routed to the non-default data subscription.

8. The method of claim 1, wherein the configuration of the UE indicates one or more rules specific to an identifier associated with the second subscription.

9. The method of claim 1, wherein routing the data traffic packet to the second communication connection comprises:

determining that the one or more parameters satisfy a rule indicated by a configuration; and

The data traffic packet is routed to the second network slice based at least in part on a determination that the one or more parameters satisfy the rule indicated by the configuration.

10. The method of claim 1, further comprising:

receive an indication of one or more UE routing policy (urs) rules for identifying traffic to be routed to a non-default network slice; and is also provided with

Wherein routing the data traffic packet to the second communication connection comprises:

determining that the one or more parameters satisfy at least one of a rule indicated by a configuration or a urs rule of the one or more urs rules.

11. The method of claim 1, wherein routing the data traffic packet to the second communication connection comprises:

routing the data traffic packet to the second subscription of the UE; and

the data traffic packet is routed to the second network slice, wherein the second network slice is a non-default network slice associated with the second subscription.

12. The method of claim 1, further comprising:

measuring a measurement parameter of the second communication connection, and

wherein routing the data traffic packet to the second communication connection comprises:

Determining that the value of the measured parameter meets a threshold; and

the data traffic packet is routed to the second communication connection based at least in part on a determination that the value of the measurement parameter satisfies the threshold.

13. The method of claim 1, wherein the one or more parameters indicate a throughput level associated with the data traffic packet, and wherein routing the data traffic packet to the second communication connection comprises:

determining that the throughput level associated with the data traffic packet meets a throughput threshold; and

the data traffic packet is routed to the second communication connection based at least in part on a determination that the throughput level associated with the data traffic packet meets the throughput threshold.

14. A wireless communication method performed by a User Equipment (UE), comprising:

establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point;

establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point;

transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and

A connection establishment request is received from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request being for establishing a tethered connection for the device using the first communication connection or the second communication connection.

15. The method of claim 14, further comprising:

the tethered connection is established for the device using the first communication connection or the second communication connection based at least in part on receipt of the connection establishment request.

16. A User Equipment (UE) for wireless communication, comprising:

a memory; and

one or more processors coupled to the memory and configured to:

establishing a first communication connection associated with a first subscription of the UE or with a first network slice, wherein the first communication connection is a default connection for data traffic by the UE;

establishing a second communication connection associated with a second subscription of the UE or with a second network slice;

receiving data traffic packets associated with one or more parameters from a device via a wireless local area network provided by the UE or via a wired connection;

Routing the data traffic packet to the second communication connection based at least in part on the one or more parameters; and

the data traffic packet is transmitted using the second communication connection.

17. The UE of claim 16, wherein the one or more processors are further configured to:

determining whether the one or more parameters satisfy a rule indicated by a configuration of the UE; and

determining whether to route the data traffic packet to the first communication connection or to the second communication connection based at least in part on a determination of whether the one or more parameters satisfy the rule indicated by the configuration.

18. The UE of claim 16, wherein the one or more processors to route the data traffic packet to the second communication connection are configured to:

performing Network Address Translation (NAT) on the data traffic packet based at least in part on the one or more parameters satisfying a rule to translate a local address associated with the device to a global address associated with the second subscription; and

the data traffic packet is routed to the second communication connection for the second subscription based at least in part on execution of the NAT.

19. The UE of claim 16, wherein the one or more processors to receive the data traffic packet are configured to:

receiving the data traffic packet indicating a source address associated with the first subscription in a header of the data traffic packet; and is also provided with

Wherein the one or more processors are configured to, for routing the data traffic packet to the second communication connection:

header translation is performed on the header of the data traffic packet to modify a source address associated with the first subscription to a source address for routing the data traffic packet to the second subscription.

20. The UE of claim 19, wherein the one or more processors to perform the header conversion on the header of the data traffic packet are configured to:

the header is modified to indicate at least one of a source address associated with the second subscription or a source address based at least in part on a prefix of the source address associated with the second subscription.

21. The UE of claim 16, wherein the configuration of the UE indicates one or more rules for identifying traffic to be routed to the UE for non-default data subscriptions.

22. The UE of claim 21, wherein the one or more rules indicate at least one of:

a service destination address of traffic to be routed to the non-default data subscription,

a Fully Qualified Domain Name (FQDN) for service to be routed to traffic of the non-default data subscription,

port number of traffic to be routed to the non-default data subscription, or

A service type value of traffic to be routed to the non-default data subscription.

23. The UE of claim 16, wherein the configuration of the UE indicates one or more rules specific to an identifier associated with the second subscription.

24. The UE of claim 16, wherein the one or more processors to route the data traffic packet to the second communication connection are configured to:

determining that the one or more parameters satisfy a rule indicated by a configuration; and

the data traffic packet is routed to the second network slice based at least in part on a determination that the one or more parameters satisfy the rule indicated by the configuration.

25. The UE of claim 16, wherein the one or more processors are further configured to:

Receive an indication of one or more UE routing policy (urs) rules for identifying traffic to be routed to a non-default network slice; and is also provided with

Wherein the one or more processors are configured to, for routing the data traffic packet to the second communication connection:

determining that the one or more parameters satisfy at least one of a rule indicated by a configuration or a urs rule of the one or more urs rules.

26. The UE of claim 16, wherein the one or more processors to route the data traffic packet to the second communication connection are configured to:

routing the data traffic packet to the second subscription of the UE; and

the data traffic packet is routed to the second network slice, wherein the second network slice is a non-default network slice associated with the second subscription.

27. The UE of claim 16, wherein the one or more processors are further configured to:

measuring a measurement parameter of the second communication connection, and

wherein the one or more processors are configured to, for routing the data traffic packet to the second communication connection:

Determining that the value of the measured parameter meets a threshold; and

the data traffic packet is routed to the second communication connection based at least in part on a determination that the value of the measurement parameter satisfies the threshold.

28. The UE of claim 16, wherein the one or more processors to route the data traffic packet to the second communication connection are configured to:

the data traffic packet is routed to the second communication connection via a hardware component of the UE.

29. A UE for wireless communication, comprising:

a memory; and

one or more processors coupled to the memory and configured to:

establishing a first communication connection for a first subscription of the UE, wherein the first communication connection is associated with a first access point;

establishing a second communication connection for a second subscription of the UE, wherein the second communication connection is associated with a second access point;

transmitting a first identifier associated with the first access point and a second identifier associated with the second access point, wherein the first identifier indicates that the first access point is associated with the first subscription and the second identifier indicates that the second access point is associated with the second subscription; and

A connection establishment request is received from a device based at least in part on the transmission of the first identifier and the second identifier, the connection establishment request being for establishing a tethered connection for the device using the first communication connection or the second communication connection.

30. The UE of claim 29, wherein the one or more processors are further configured to:

the tethered connection is established for the device using the first communication connection or the second communication connection based at least in part on receipt of the connection establishment request.