Data transmission on multi-subscriber identity module device based on data path link metrics

Abstract

Certain aspects of the present disclosure provide techniques for communication at a user equipment (UE). In one exemplary embodiment, a method includes collecting data path link metrics for a plurality of links associated with at least a first subscriber identity module (SIM) and a second SIM at a first logical layer of the UE; providing information about the collected data path link metrics to a second logical layer of the UE; and selecting, at the second logical layer, a data transfer mode based on information about the collected data path link metrics.

Description

Technical Field

[0001] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for data transmission on a Multiple Subscriber Identity Module (MSIM) device based on data path link metrics. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast or other similar types of services.These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing the available wireless communication system resources with those users.

[0003] Although wireless communication systems have achieved tremendous technical advances over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continued desire to improve the technical performance of wireless communication systems, including, for example: increasing the speed and data carrying capacity of communications, improving the efficiency of the use of shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need for further improvements in wireless communication systems to overcome the aforementioned technical challenges and other challenges. Summary of the invention

[0004] One aspect provides a method for wireless communication at a user equipment (UE). The method includes: collecting data path link metrics for multiple links associated with at least a first subscriber identity module (SIM) and a second SIM at a first logical layer of the UE; providing information about the collected data path link metrics to a second logical layer of the UE; and selecting a data transmission mode at the second logical layer based on the information about the collected data path link metrics.

[0005] Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the foregoing methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the foregoing methods and those described elsewhere herein; and / or an apparatus comprising means for performing the foregoing methods and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating on one or more networks.

[0006] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of the disclosure.

[0008] Figure 1 An example wireless communication network is depicted.

[0009] Figure 2 An example disaggregated base station architecture is depicted.

[0010] Figure 3 Aspects of an example base station and example user equipment are depicted.

[0011] Figure 4A , 4B , 4C and 4D depict various example aspects of data structures for a wireless communication network.

[0012] Figure 5 Depicted are example multi-SIM deployments for a UE in accordance with certain aspects of the present disclosure.

[0013] Figure 6 Depicted is a timing diagram showing different users (SUB) in different states.

[0014] Figure 7 An example of a data path for a DSDA device is depicted.

[0015] Fig. 8A and 8B Depicted is a schematic diagram showing different data path metrics for different SUBs.

[0016] Fig. 9 Depicted are timing diagrams comparing metrics on different data paths for different SUBs.

[0017] Fig.10 A diagram showing a data transfer mode for an MSIM device is depicted.

[0018] Fig.11 Depicted are example data path metrics that may be monitored for an MSIM device in accordance with aspects of the present disclosure.

[0019] Fig.12 Depicted is a flow chart showing data transmission mode selection based on data path metrics according to aspects of the present disclosure.

[0020] Fig.13 Depicted are graphics showing possible games that perform data transfer mode selection based on data path metrics in accordance with aspects of the present disclosure.

[0021] Fig.14 A method for wireless communication is described.

[0022] Fig.15 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0023] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for techniques for data transmission on a Multi-Subscriber Identity Module (MSIM) device based on data path link metrics.

[0024] Concurrent Radio Access Technology (RAT) operation generally refers to operating multiple simultaneously active connections. Multi-SIM devices are able to connect to multiple networks independently without the network being aware. Different UE behaviors may occur based on different implementations such as Dual SIM Dual Active (DSDA) or Dual SIM Dual Standby (DSDS). DSDS generally refers to a dual SIM deployment where both SIM cards of a UE may not be able to generate traffic at the same time.

[0025] On the other hand, DSDA refers to a dual SIM deployment in which both SIM cards of a UE can be active simultaneously. The two SIMs can use independent radio frequency (RF) resources or shared RF resources, and during DSDA, both may be subject to RF limitations in transmit (Tx) and receive (Rx) capabilities. The SIMs may be connected to different base stations of different networks or the same network. Thus, when operating in DSDA mode, there may be two possible data paths available for upper layer traffic (e.g., traffic to / from the application layer).

[0026] Different services have different transmission requirements (e.g., in terms of packet delay, packet error rate, and data rate). Conventional channel condition metrics that indicate general channel conditions may not directly reflect data transmission performance. Data transmission performance more dynamically depends on the instantaneous network configuration, scheduling rate, bandwidth, dedicated channel quality, etc.

[0027] On DSDA devices, two independent stacks and data paths are available. This provides the opportunity for flexible data transmission, for example, by dynamically selecting a better data transmission path based on immediate conditions (e.g., type of RAT, frequency, configuration, etc.).

[0028] A challenge in DSDA scenarios is how to select one or more optimal data paths for a particular service. However, aspects of the present disclosure provide a mechanism for monitoring metrics or key performance indicators (KPIs) for different data paths. A transmission mode involving one or more multiple data paths can be selected based on the monitored data path metrics. By considering the path link metrics for different data paths, data throughput can be significantly improved when selecting a data transmission mode.

[0029] Introduction to wireless communication networks

[0030] The techniques and methods described herein can be used in various wireless communication networks. Although terms generally associated with 3G, 4G and / or 5G wireless technologies may be used herein to describe aspects, aspects of the present disclosure may also be applied to other communication systems and standards not explicitly mentioned herein.

[0031] Figure 1 An example of a wireless communication network 100 is depicted in which aspects described herein may be implemented.

[0032] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network can be considered network entities. In addition, the wireless communication network 100 includes: terrestrial aspects, such as ground-based network entities (e.g., BS 102); and non-terrestrial aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0033] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks, such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190, which interoperate to provide communication services over various communication links (including wired and wireless links).

[0034] Figure 1 Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electrical meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an always-on (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a user station, a mobile user station, a mobile unit, a user unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0035] BS 102 communicates wirelessly with UE 104 (e.g., sends signals to or receives signals from UE 104) via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0036] BS 102 may generally include: a Node B, an enhanced Node B (eNB), a next generation enhanced Node B (ng-eNB), a next generation Node B (gNB or gNodeB), an access point, a base transceiver, a radio base station, a radio transceiver, a transceiver function, a transmission and reception point, and / or the like. Each of BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell and may overlap in some cases (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell 110). A BS may, for example, provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area (e.g., a home), and / or other types of cells.

[0037] Although BS102 is depicted as a unit communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of the base station can be deaggregated, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, to name a few. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS102) can include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, each component can perform a function so that each component collectively implements a function similar to that of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a deaggregated radio access network architecture, such as an open RAN (O-RAN) or a virtualized RAN (VRAN) architecture. Figure 2 An example disaggregated base station architecture is depicted and described.

[0038] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0039] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, frequency channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz-7125 MHz, which is often (interchangeably) referred to as "sub-6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS180) configured to communicate using mmWave / near mmWave radio frequency bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0040] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0041] Communications using higher frequency bands can have higher path loss and shorter range than communications using lower frequencies. Therefore, some base stations (e.g. Figure 1180) can utilize beamforming 182 with UE 104 to improve path loss and range. For example, BS 180 and UE 104 can each include multiple antennas, such as antenna elements, antenna panels and / or antenna arrays to facilitate beamforming. In some cases, BS 180 can send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 can receive beamformed signals from BS 180 in one or more receive directions 182". UE 104 can also send beamformed signals to BS 180 in one or more transmit directions 182". BS 180 can also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 can then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receive directions for BS 180 may be the same, or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.

[0042] Wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0043] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0044] The EPC 160 may include various functional components, including: a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management.

[0045] Typically, user Internet Protocol (IP) packets are transmitted through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a packet switched (PS) streaming service, and / or other IP services.

[0046] The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and / or may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0047] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0048] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0049] Internet Protocol (IP) packets are transmitted through UPF 195, which is connected to IP services 197 and provides UE IP address allocation and other functions for 5GC 190. IP services 197 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0050] In various aspects, a network entity or network node may be implemented as a converged base station, a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few.

[0051] Figure 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with a core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 (via an E2 link), or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 240 simultaneously.

[0052] Each of the units, for example, CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205, may include one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium or may be coupled to the one or more interfaces. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive a signal on a wired transmission medium or to send a signal to one or more of the other units on a wired transmission medium. Additionally or alternatively, a unit may include a wireless interface configured to receive a signal on a wireless transmission medium or to send a signal to one or more of the other units on a wireless transmission medium, or to perform both signal reception and transmission on a wireless transmission medium, which wireless interface may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver).

[0053] In some aspects, CU 210 may be responsible for one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to transmit signals to other control functions hosted by CU 210. CU210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-PU)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface, when implemented in an O-RAN configuration). CU 210 may be implemented to communicate with DU230 (when necessary) for network control and signaling.

[0054] The DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240. In some aspects, depending at least in part on the functional split (such as, the functional split defined by the 3rd Generation Partnership Project (3GPP)), the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as, modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to transmit signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0055] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RU 240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU 230 and the CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0056] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O cloud) 290) via a cloud computing platform interface (such as an O2 interface) to perform network element lifecycle management (such as to instantiate virtualized network elements). Such virtualized network elements may include, but are not limited to: CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. In addition, in some implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RTRIC 215 configured to support the functionality of the SMO framework 205 .

[0057] The non-RT RIC 215 may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (e.g., via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface that connects one or more CUs 210, one or more DUs 230, or both, and O-eNBs to the near-RT RIC 225 (e.g., via an E2 interface).

[0058] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as, via reconfiguration of O1) or via the creation of a RAN management policy (such as, an A1 policy).

[0059] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0060] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively 334), transceivers 332a-t (collectively 332) (which include modulators and demodulators), and other aspects that implement wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can send and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340, which can be configured to implement various functions related to wireless communication described herein.

[0061] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-r (collectively, 352), transceivers 354a-r (collectively, 354) (which include modulators and demodulators), and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that may be configured to implement various functions described herein related to wireless communications.

[0062] With respect to example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0063] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0064] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable), and may provide an output symbol stream to a modulator (MOD) in a transceiver 332a-332t. Each modulator in the transceiver 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0065] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0066] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0067] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 (if applicable), further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0068] At BS 102, uplink signals from UE 104 may be received by antennas 334a-t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 (if applicable), and further processed by receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340.

[0069] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0070] A scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0071] In various aspects, the BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-t, an antenna 334a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-t, a transceiver 332a-t, an RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0072] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-t, an antenna 352a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-t, a transceiver 354a-t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0073] In some aspects, the processor may be configured to perform various operations, such as those associated with the methods described herein, and to send (output) or receive (obtain) data to or from another interface configured to send or receive data, respectively.

[0074] Figure 4A , 4B , 4C and 4D depict a wireless communication network (such as Figure 1 Aspects of the data structure of the wireless communication network 100).

[0075] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a schematic diagram 430 showing an example of DL channels within a 5G subframe, Figure 4C is a schematic diagram 450 showing an example of a second subframe within a 5G frame structure, and Figure 4D is a schematic diagram 480 showing an example of UL channels within a 5G subframe.

[0076] Wireless communication systems can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and 4D ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. The modulation symbols can be sent in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0077] The wireless communication frame structure may be frequency division duplex (FDD), where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0078] exist Figure 4A and 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X can be used flexibly between DL / UL. The UE can be configured with a slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). In the depicted example, a 10ms frame is divided into 10 1ms subframes of equal size. Each subframe may include one or more slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. A subframe may also include a microslot, which generally has fewer symbols than a whole slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0079] In certain aspects, the number of time slots within a subframe is based on the time slot configuration and the digital scheme. For example, for time slot configuration 0, different digital schemes (μ) 0 to 5 allow 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 time slots per subframe, respectively. Therefore, for time slot configuration 0 and digital scheme μ, there are 14 symbols / time slot and 2μ time slots / subframe. The subcarrier spacing and symbol length / duration are functions of the digital scheme. The subcarrier spacing can be equal to 2 μ × 15kHz, where μ is the digital scheme 0 to 5. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , 4B 4C and 4D provide examples of slot configuration 0 with 14 symbols per slot and a digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0080] like Figure 4A , 4B, 4C and 4D, a resource grid may be used to represent a frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending, for example, 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0081] like Figure 4A As shown in , some of the REs carry data for UEs (e.g., Figure 1 and 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0082] Figure 4B Examples of various DL channels within a subframe of a frame are shown.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0083] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and 3 104) is used to determine subframe / symbol timing and physical layer identity.

[0084] The Secondary Synchronization Signal (SSS) may be in symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0085] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0086] like Figure 4CAs shown in , some of the REs carry DMRS for channel estimation at the base station (indicated as R for one specific configuration, but other DMRS configurations are possible). The UE may send DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent, and depending on the specific PUCCH format used, the PUCCH DMRS may be sent in different configurations. UE 104 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0087] Figure 4D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0088] Overview of MSIM Operations

[0089] Figure 5 An example multi-SIM (MSIM) deployment is depicted, where the UE supports multiple SIMs (SIM1 and SIM2), which may support the same or different radio access technologies (RATs). At any given time, multiple SIMs may be idle at the same time and may support different operating modes. For example, a UE with a single receiver may support a single-receive dual-SIM dual-standby (SR-DSDS) mode, in which only one RAT is received at a time. In dual-receive (DR)-DSDS mode, an MSIM UE may receive multiple RATs at the same time.

[0090] NR concurrent radio access technology (RAT) operation generally refers to operating multiple simultaneously active connections, at least one of which is connected on NR. For example, two connections may involve LTE and NR connections or two NR connections. Multi-SIM devices are able to connect to multiple networks independently without network awareness. Different UE behaviors may occur based on different implementations, such as dual SIM dual activity (DSDA) or dual SIM dual standby (DSDS). DSDS generally refers to a dual SIM deployment in which the two SIM cards of the UE may not be able to generate services at the same time. On the other hand, DSDA refers to a dual SIM deployment in which the two SIM cards of the UE can be active at the same time. As used herein, SIM generally refers to both virtual and hardware implementations of SIM. In other words, each SIM can be implemented on a multi-SIM device using hardware (e.g., a physical SIM card) or virtually implemented using a remote database.

[0091] Dual SIM receivers allow different SIMs to support a variety of different combination options. For example, a dual SIM (DSIM) device can support the following:

[0092] SA-NR+SA-NR: Both SIMs can support standalone (SR) NR (SA-NR);

[0093] NSA-NR+LTE: one SIM supports non-standalone (NSA) and the other SIM supports LTE;

[0094] LTE+LTE: Both SIMs support LTE;

[0095] LTE+W: one SIM supports LTE and the other supports Wideband CDMA; or any other combination (X RAT+X RAT, both SIMs support the same RAT; or X RAT+Y RAT, SIMs support different RATs).

[0096] In some cases, in a multi-SIM deployment, each SIM of a UE may belong to the same network carrier. For example, two or more SIMs (also referred to herein as users or SUBs) belonging to the same operator may be in the following modes:

[0097] (1) Idle+Idle: Two or more idle SUBs reside in the same cell

[0098] (2) Connected+Idle: One SUB in idle state and one SUB in connected state reside in the same cell.

[0099] Aspects related to data transmission on a multi-user identity module device based on data path link metrics

[0100] like Figure 6As shown in , in DSDA mode, two SIMs (SIM1 and SIM2) can be in a connected state at the same time, where Tx is active. As shown, the duration and periodicity of the RRC connected state for each SIM can be different. Also between connected states, when the SIM is in a radio resource control (RRC) idle or inactive state, each SIM can wake up during the open duration to monitor for paging.

[0101] The two SIMs may use independent RF resources or share RF resources, and both may be subject to RF limitations in Tx and Rx capabilities during DSDA. Figure 7 As shown in , the SIM can be connected to different networks or different base stations of the same network. Thus, when operating in DSDA mode, there may be two possible data paths available for upper layer services. Figure 7 In the example shown in , SIM1 is connected to the network (the core network CN of the network) via cell A, while SIM2 is connected via cell B.

[0102] As mentioned above, one challenge in the DSDA scenario is how to select one or more optimal data paths for a particular service. Conventional channel condition metrics such as reference signal (RS) received power (RSRP), RS received quality (RSRQ), and signal-to-noise ratio (SNR) can indicate general channel conditions, but may not directly reflect data transmission performance. The actual data transmission performance depends more dynamically on metrics that indicate the instantaneous network configuration, such as scheduling rate, bandwidth, and dedicated channel quality.

[0103] On DSDA devices, two independent stacks / data paths are available. As a result, there may be greater flexibility and potentially better data transmission can be provided by dynamically / statically selecting a better data transmission path based on current conditions (type of RAT, frequency, configuration, etc.). In some cases, the UE may choose to aggregate the two data paths to achieve greater transmission bandwidth.

[0104] Fig. 8A and 8B It shows how different SIM data paths can have different metrics that may affect data throughput. In the example shown, cell A (BW-A) has a significantly larger bandwidth than cell B (BW-A). On the other hand, for cell A, the scheduling request (SR) period is 40ms, and for cell B, the scheduling request (SR) period is only 10ms. The amount of Tx power headroom (PHR) on each data path may also be considered when deciding which path(s) to select.

[0105] By considering such path link metrics for different data paths, aspects of the present disclosure can help improve data throughput when selecting a data transmission mode. As will be described in more detail below, the UE may have a module configured to monitor and collect data path link metrics for multiple links associated with at least a first subscriber identity module (SIM) and a second SIM at a first logical layer (e.g., a physical / PHY layer) of the UE. The module may provide information about the collected data path link metrics to a second logical layer (e.g., an application / APP layer) of the UE, which may select a data transmission mode based on the information about the collected data path link metrics.

[0106] Fig. 9 It is shown how various metrics (such as the ratio of RSRP to SNR) can change over time. According to aspects of the present disclosure, short-term (or instantaneous) values ​​of various such data path (KPI) metrics can be considered to select a data path (dynamically or statically). In some cases, a KPI for each traffic type (such as round-trip time (RTT) delay or data throughput) can be considered to determine which path(s) to select (e.g., SIM1 through cell A or SIM2 through cell B or both).

[0107] Reference Fig. 9 , at the first time (@t1), SIM1 on cell A has much better RSRP / SNR and better RTT than cell B. Therefore, in this case, the data path of SIM1-cell A can be selected.

[0108] At the second time (@t2), SIM1 on cell A and SIM2 on cell B have comparable RSRP / SNR. However, since the SR cycle of cell B is much shorter than that of cell A, the data path SIM2-cell B can be selected for delay-sensitive services. The BW of cell A is much wider than that of cell B, so two data paths can be selected for services with high throughput.

[0109] At the third time (@t3), SIM2 on cell B has a much better RSRP / SNR ratio and a better RTT than cell A. Therefore, in this case, the data path for SIM2-cell B may be selected.

[0110] Fig.10An overview of different DSDA device data transmission modes that may be selected is given. The first mode (No.1) may correspond to concurrent transmissions through both SIM1 and SIM2. For example, this mode may be used for services that may benefit from increased BW and throughput aggregation by using independent resources. This mode may also be selected to provide redundant transmissions for latency and / or security sensitive packets or for operator dependent service support. The second mode (No.2) may correspond to an intelligent selection of one of the data paths, which may provide seamless application (APP) data switching. Generally, on each SUB, the selection of the most appropriate cell (RAT, frequency, BWP) to perform the transmission may be based on the type of service (e.g., delay sensitive or small / large data volumes), and whether the two SUBs share a hardware (HW) resource sharing mode.

[0111] like Fig.11 As shown in the flowchart 1100 of , according to certain aspects of the present disclosure, a link KPI monitoring module 1115 can be defined to collect data path link metrics (SIM1 KPI 1125 and SIM2 KPI 1130) for each SIM. As shown, the KPIs can include cell-specific metrics such as RSRP, SNR, RAT (e.g., RAT type or capability) and frequency. The KPIs can also include real-time service KPI metrics such as average RTT, block error rate (BLER), scheduling rate, and data rate. In some cases, periodic link KPI collection of service KPI metrics can be triggered, for example, by triggering a connection to a specific server. As shown, the link KPI monitoring module can provide information about the monitored link KPI to an upper layer (e.g., application / APP layer).

[0112] Link KPI monitoring can provide the current HW sharing status and can also link the KPI to upper layers. In the case where SIM1 and SIM2 are in deep resource sharing (e.g., with a shared power amplifier (PA) that only allows one SUB to be sent at a time), upper layers may suggest a SUB change (e.g., RAT / band) to the modem to use independent resources as much as possible and trigger link KPI updates accordingly.

[0113] In some cases, an upper layer (eg, APP layer) may decide whether the data transmission mode should be concurrent data transmission or (single) selected data path transmission based on the link KPI module update.

[0114] Fig.12 1200 shows how the link KPI monitoring module 1115 can provide updates about the link KPI to the APP layer. The APP layer can then decide on one of the DSDA data transmission modes (e.g., Fig.10listed in the table).

[0115] like Fig.12 As shown in , at 1205, the APP layer can divide (split) a large block of data into multiple segments, and then create / allocate different streams (sockets) to transmit different segments. Based on the KPI update, different streams with independent data packets or redundant data packets can be bound to SIM1 and SIM2, respectively, as shown in paths 1210 and 1215. As shown, at 1220, the APP layer can merge data from different streams on the DSDA channel.

[0116] like Fig.12 As shown in , the link KPI monitoring module 1115 can provide application layer information about the collected data path link metrics. The APP layer can also notify the PHY layer with a signal. For example, the APP layer can notify the PHY layer (link KPI monitoring module 1115) with a signal to change the RAT or frequency resources of at least one of the first SIM or the second SIM (to use independent hardware resources), and / or modify the hardware sharing status of the first SIM and the second SIM.

[0117] By monitoring KPIs on different data paths, aspects of the present disclosure may be able to better adapt to different businesses and different services with different requirements. Some businesses may be defined by business delay, packet error rate, or data rate, and throughput-sensitive businesses, delay-sensitive businesses, and different channel conditions may affect data transmission. Monitoring data path KPIs can help select one or more optimal data paths for transmission. Compared with conventional (traditional) channel condition metrics, monitoring data path KPIs can provide a better indication of which path(s) are better for transmission.

[0118] Fig.13 1300 illustrates an example of possible improvements in data throughput that can be achieved by selecting a data transmission mode based on a data path metric according to aspects of the present disclosure. As shown, assuming that a dedicated data SUB (DDS) has a downlink (DL) throughput of 200 Mbps and a non-dedicated data SUB (nDDS) has a DL throughput of 300 Mbps, then the download splitting on DDS and nDDS based on the data path metric can represent a significant gain (e.g., a 150% gain compared to DDS alone, or a 70% gain compared to nDDS alone).

[0119] Example Operations of User Equipment

[0120] Fig.14 A method for UE (such as, Figure 1 and 3 An example of a method 1400 for wireless communication at a UE 104).

[0121] Method 1400 begins at step 1405 by collecting data path link metrics for a plurality of links associated with at least a first SIM and a second SIM at a first logical layer of a UE. In some cases, the operation of this step refers to referring to Fig.15 The circuit system for collecting and / or the code for collecting described, or can be referred to Fig.15 The described circuit system for collecting and / or code for collecting are executed.

[0122] Then, method 1400 proceeds to step 1410, where information about the collected data path link metrics is provided to the second logical layer of the UE. In some cases, the operation of this step refers to referring to Fig.15 The circuit system and / or code described for providing, or can be referred to by Fig.15 The described circuit systems for providing and / or the described codes for providing are implemented.

[0123] Then, method 1400 proceeds to step 1415, where a data transmission mode is selected at the second logical layer based on the information about the collected data path link metrics. In some cases, the operation of this step refers to referring to Fig.15 The circuit system for selecting and / or the code for selecting described herein may be referred to in conjunction with Fig.15 The described circuit system for selecting and / or code for selecting are implemented.

[0124] In some aspects, selecting a data transfer mode includes: selecting one of: a single path mode involving a link associated with the first SIM; a single path mode involving a link associated with the second SIM; or a concurrent path mode involving both a link associated with the first SIM and a link associated with the second SIM.

[0125] In some aspects, the data path link metrics include: cell-specific data path link metrics; and service-related data path link metrics.

[0126] In some aspects, the cell-specific data path link metric comprises at least one of: RSRP, SNR, type of RAT, or available bandwidth.

[0127] In some aspects, the traffic-related data path link metric includes at least one of an RTT, a BLER, a scheduling rate, or a data rate metric.

[0128] In some aspects, selecting the data transmission mode is further based on UE battery power.

[0129] In some aspects, collecting data path link metrics is periodic and triggered by at least one event.

[0130] In some aspects, at least one event involves connection to a server.

[0131] In some aspects, the method 1400 further includes: providing information about the hardware sharing status of the first SIM and the second SIM to the second logical layer. In some cases, the operation of this step refers to referring to Fig.15 The circuit system and / or code described for providing, or can be referred to by Fig.15 The described circuit systems for providing and / or the described codes for providing are implemented.

[0132] In some aspects, the method 1400 further includes: providing, by the second logical layer, signaling to the first logical layer to perform at least one of: changing the RAT or frequency resources of at least one of the first SIM or the second SIM to use independent hardware resources; or modifying the hardware sharing state of the first SIM and the second SIM. In some cases, the operation of this step refers to referring to Fig.15 The circuit system and / or code described for providing, or can be referred to by Fig.15 The described circuit systems for providing and / or the described codes for providing are implemented.

[0133] In some aspects, the method 1400 further includes: providing, by the second logical layer, signaling to the first logical layer to update the data path link metric. In some cases, the operation of this step refers to referring to Fig.15 The circuit system and / or code described for providing, or can be referred to by Fig.15 The described circuit systems for providing and / or the described codes for providing are implemented.

[0134] In some aspects, a data transmission mode is selected to segment data into multiple segments, wherein the multiple segments are sent as different streams.

[0135] In some aspects, different flows having independent data packets or redundant data packets are mapped to a first link associated with a first SIM or a second link associated with a second SIM.

[0136] In some aspects, the data transmission mode is selected to consolidate data from different flows over multiple links associated with the first SIM and the second SIM.

[0137] In one aspect, method 1400 or any aspect related thereto may be performed by, for example, Fig.15The method 1400 is performed by an apparatus of a communication device 1500, which includes various components operable, configured or adapted to perform the method 1400. The communication device 1500 is described in more detail below.

[0138] Notice, Fig.14 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0139] Example Communication Device

[0140] Fig.15 Aspects of an example communication device 1500 are depicted. In some aspects, the communication device 1500 is a user device, such as described above with respect to Figure 1 and 3 UE 104 is described.

[0141] The communication device 1500 includes a processing system 1505 coupled to a transceiver 1555 (e.g., a transmitter and / or a receiver). The transceiver 1555 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1500 via an antenna 1560. The processing system 1505 may be configured to perform processing functions for the communication device 1500, including processing signals received and / or to be transmitted by the communication device 1500.

[0142] Processing system 1505 includes one or more processors 1510. In various aspects, one or more processors 1510 may represent Figure 3 One or more of the receive processor 358, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380 described herein. The one or more processors 1510 are coupled to the computer readable medium / memory 1530 via bus 1550. In certain aspects, the computer readable medium / memory 1530 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1510, cause the one or more processors 1510 to perform operations related to the processing of the computer readable medium / memory 1530. Fig.14 The described method 1400, or any aspect related thereto. Note that references to a processor performing a function of the communication device 1500 may include one or more processors 1510 performing that function of the communication device 1500.

[0143] In the depicted example, the computer readable medium / memory 1530 stores code (e.g., executable instructions) such as code for collecting 1535, code for providing 1540, and code for selecting 1545. Processing of the code for collecting 1535, the code for providing 1540, and the code for selecting 1545 may cause the communication device 1500 to perform operations related to the communication device 1500. Fig.14 The described method 1400, or any aspect related thereto.

[0144] The one or more processors 1510 include circuitry configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1530, including circuitry such as circuitry for collecting 1515, circuitry for providing 1520, and circuitry for selecting 1525. Processing using the circuitry for collecting 1515, the circuitry for providing 1520, and the circuitry for selecting 1525 may enable the communication device 1500 to perform operations related to Fig.14 The described method 1400, or any aspect related thereto.

[0145] The various components of the communication device 1500 may provide for performing Fig.14 The described means of method 1400 or any aspect thereof. For example, the means for transmitting, sending, or outputting for transmission may include Figure 3 The transceiver 354 and / or antenna 352 of the UE 104 shown in FIG. Fig.15 The transceiver 1555 and antenna 1560 of the communication device 1500 in FIG. 1 may include Figure 3 The transceiver 354 and / or antenna 352 of the UE 104 shown in FIG. Fig.15 The transceiver 1555 and antenna 1560 of the communication device 1500.

[0146] Sample Clauses

[0147] Examples of implementations are described in the following numbered clauses:

[0148] Clause 1: A method for wireless communication at a UE, comprising: collecting data path link metrics for multiple links associated with at least a first SIM and a second SIM at a first logical layer of the UE; providing information about the collected data path link metrics to a second logical layer of the UE; and selecting a data transmission mode at the second logical layer based on the information about the collected data path link metrics.

[0149] Clause 2: A method according to clause 1, wherein selecting the data transmission mode includes: selecting one of the following: a single path mode involving a link associated with the first SIM; a single path mode involving a link associated with the second SIM; or a concurrent path mode involving both the link associated with the first SIM and the link associated with the second SIM.

[0150] Clause 3: A method according to any one of clauses 1 and 2, wherein the data path link metrics include: cell-specific data path link metrics; and service-related data path link metrics.

[0151] Clause 4: A method as described in clause 3, wherein the cell-specific data path link metric includes at least one of the following: RSRP, SNR, type of RAT, or available bandwidth.

[0152] Clause 5: The method of clause 3, wherein the service-related data path link metric comprises at least one of an RTT, a BLER, a scheduling rate, or a data rate metric.

[0153] Clause 6: A method as described in any of clauses 1-5, wherein selecting the data transmission mode is further based on UE battery power.

[0154] Clause 7: The method of any of clauses 1-6, wherein collecting data path link metrics is periodic and triggered by at least one event.

[0155] Clause 8: The method of clause 7, wherein the at least one event relates to connection to a server.

[0156] Clause 9: The method of any one of clauses 1-8, further comprising: providing information about a hardware sharing status of the first SIM and the second SIM to the second logic layer.

[0157] Clause 10: The method according to Clause 9 further includes: providing signaling by the second logical layer to the first logical layer to perform at least one of the following: changing the RAT or frequency resources of at least one of the first SIM or the second SIM to use independent hardware resources; or modifying the hardware sharing state of the first SIM and the second SIM.

[0158] Clause 11: The method of clause 10, further comprising: providing signaling, by the second logical layer to the first logical layer, to update a data path link metric.

[0159] Clause 12: The method of any of clauses 1-11, wherein the data transmission mode is selected to segment the data into a plurality of segments, wherein the plurality of segments are sent as different streams.

[0160] Clause 13: The method of clause 12, wherein different flows having independent data packets or redundant data packets are mapped to a first link associated with the first SIM or a second link associated with the second SIM.

[0161] Clause 14: The method of any of clauses 1-13, wherein a data transmission mode is selected to merge data from different flows on the multiple links associated with the first SIM and the second SIM.

[0162] Clause 15: An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method of any of clauses 1-14.

[0163] Clause 16: An apparatus comprising means for performing the method according to any of clauses 1-14.

[0164] Clause 17: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1-14.

[0165] Clause 18: A computer program product embodied on a computer-readable storage medium, comprising code for performing the method according to any of clauses 1-14.

[0166] Additional considerations

[0167] The previous description is provided to enable those skilled in the art to practice the various aspects described herein. The examples described herein are not limitations of the scope, applicability or aspects set forth in the claims. For those skilled in the art, various modifications to these aspects will be readily apparent, and the general principles defined herein can be applied to other aspects. For example, without departing from the scope of the present disclosure, changes may be made to the functions and arrangements of the elements discussed. Each example may ignore, replace or add each process or component as appropriate. For example, the described method may be performed in an order different from that described, and each action may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functions or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.

[0168] The various schematic logic blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors and a DSP core, a system on a chip (SoC), or any other such configuration.

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

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

[0171] The method disclosed herein includes one or more actions for implementing the method. Without departing from the scope of the claims, the method actions can be interchangeable with each other. In other words, unless a specific order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. In addition, the various operations of the above-mentioned method can be performed by any suitable unit that can perform the corresponding function. These units may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0172] The following claims are not intended to be limited to the aspects shown herein, but should be granted the full scope consistent with the language of the claims. Within the claims, references to singular elements are not intended to mean "there is and only one" (unless specifically stated), but "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. No claim element should be interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly recorded using the phrase "unit for...". All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, none of the contents disclosed herein are intended to be donated to the public, regardless of whether such disclosures are explicitly recorded in the claims.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: collecting data path link metrics for a plurality of links associated with at least a first subscriber identity module (SIM) and a second SIM at a first logical layer of the UE; providing information about the collected data path link metrics to a second logical layer of the UE; as well as A data transmission mode is selected at the second logical layer based on the information about the collected data path link metrics.

2. The method according to claim 1, wherein: Selecting the data transmission mode includes: selecting one of the following: a single path mode involving a link associated with said first SIM; a single path mode involving a link associated with the second SIM; or A concurrent path pattern involving both the link associated with the first SIM and the link associated with the second SIM.

3. The method according to claim 1, wherein: The data path link metrics include: cell-specific data path link metrics; and Business-related data path link metrics.

4. The method according to claim 3, wherein: The cell-specific data path link metric includes at least one of: a reference signal received power (RSRP), a signal-to-noise ratio (SNR), a type of radio access technology (RAT), or an available bandwidth.

5. The method according to claim 3, wherein: The service-related data path link metric includes at least one of a round trip time (RTT), a block error rate (BLER), a scheduling rate, or a data rate metric.

6. The method according to claim 1, wherein: The data transmission mode is also selected based on the UE battery power.

7. The method according to claim 1, wherein: Collecting data path link metrics is periodic and triggered by at least one event.

8. The method according to claim 7, wherein: The at least one event relates to connection to a server.

9. The method according to claim 1, further comprising: The second logic layer is provided with information about a hardware sharing status of the first SIM and the second SIM.

10. The method according to claim 9, further comprising: The second logical layer provides signaling to the first logical layer to perform at least one of the following: changing the RAT or frequency resource of at least one of the first SIM or the second SIM to use independent hardware resources; or The hardware sharing state of the first SIM and the second SIM is modified.

11. The method according to claim 10, further comprising: Signaling is provided by the second logical layer to the first logical layer to update the data path link metric.

12. The method according to claim 1, wherein: The data transmission mode is selected to segment the data into multiple segments, wherein the multiple segments are sent as different streams.

13. The method according to claim 12, wherein: Different flows having independent data packets or redundant data packets are mapped to a first link associated with the first SIM or a second link associated with the second SIM.

14. The method according to claim 1, wherein: A data transmission mode is selected to merge data from different streams on the plurality of links associated with the first SIM and the second SIM.

15. An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the following operations: collecting data path link metrics for a plurality of links associated with at least a first subscriber identity module (SIM) and a second SIM at a first logical layer of a user equipment (UE); providing information about the collected data path link metrics to a second logical layer of the UE; as well as A data transmission mode is selected at the second logical layer based on the information about the collected data path link metrics.

16. The device according to claim 15, wherein: Selecting the data transmission mode includes selecting one of the following: a single path mode involving a link associated with said first SIM; a single path mode involving a link associated with the second SIM; or A concurrent path pattern involving both the link associated with the first SIM and the link associated with the second SIM.

17. The device according to claim 15, wherein: The data path link metrics include: cell-specific data path link metrics; and Business-related data path link metrics.

18. The device according to claim 17, wherein: The cell-specific data path link metric includes at least one of: a reference signal received power (RSRP), a signal-to-noise ratio (SNR), a type of radio access technology (RAT), or an available bandwidth.

19. The device according to claim 17, wherein: The service-related data path link metric includes at least one of a round trip time (RTT), a block error rate (BLER), a scheduling rate, or a data rate metric.

20. The device according to claim 15, wherein: The data transmission mode is also selected based on the UE battery power.

21. The device according to claim 15, wherein: Collecting data path link metrics is periodic and triggered by at least one event.

22. The device according to claim 21, wherein The at least one event relates to connection to a server.

23. The device according to claim 15, wherein: The processor is further configured to execute the executable instructions and cause the apparatus to provide information about a hardware sharing status of the first SIM and the second SIM to the second logical layer.

24. The device according to claim 23, wherein: The processor is further configured to execute the executable instructions and cause the apparatus to provide signaling to the first logical layer through the second logical layer to perform at least one of the following: changing the RAT or frequency resource of at least one of the first SIM or the second SIM to use independent hardware resources; or The hardware sharing state of the first SIM and the second SIM is modified.

25. The device according to claim 24, wherein: The processor is further configured to execute the executable instructions and cause the apparatus to provide signaling to the first logical layer through the second logical layer to update a data path link metric.

26. The device according to claim 15, wherein: The data transmission mode is selected to segment the data into multiple segments, wherein the multiple segments are sent as different streams.

27. The device according to claim 26, wherein: Different flows having independent data packets or redundant data packets are mapped to a first link associated with the first SIM or a second link associated with the second SIM.

28. The device according to claim 15, wherein: A data transmission mode is selected to merge data from different streams on the plurality of links associated with the first SIM and the second SIM.

29. An apparatus comprising means for performing the method according to any one of claims 1-14.

30. A non-transitory computer-readable medium comprising executable instructions, which, when executed by a processor of a device, cause the device to perform the method according to any one of claims 1-14.

Images