Network-based location performance improvement using DSDA

Abstract

Aspects presented herein may improve positioning performance and latency for UEs with dual subscriber identity module (SIM) dual activity (DSDA) features. In one aspect, a UE establishes a connection with a first network entity and a second network entity based on DSDA. The UE selects (1) the first network entity or the second network entity for downloading data associated with calculating a location of the UE based on at least one criterion, or selects (2) a fix for calculating the location of the UE based on a set of available cache-based fixes associated with the first network entity and the second network entity. The UE calculates the location of the UE based on the downloaded data or the selected fixations.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 301,929, entitled “NETWORK BASED LOCATION PERFORMANCE IMPROVEMENT USING DSDA”, filed April 17, 2023, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to wireless communication relating to positioning. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus (e.g., a user equipment (UE)) establishes a connection with a first network entity and a second network entity based on Dual Subscriber Identity Module (SIM) Dual Activity (DSDA). The apparatus selects (1) the first network entity or the second network entity for downloading data associated with calculating the UE's location based on at least one criterion, or selects (2) fixing for calculating the UE's location based on a cache-based set of available fixings associated with the first and second network entities. The apparatus calculates the UE's location based on the downloaded data or the selected fixing.

[0008] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0011] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0012] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0013] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0014] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0015] Figure 4This is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0016] Figure 5A This is a diagram illustrating an example of a UE communicating with two networks based on the Dual Subscriber Identity Module (SIM) Dual Activity (DSDA) service, according to various aspects of this disclosure.

[0017] Figure 5B This is a diagram illustrating an example of a UE communicating with two networks based on DSDA services according to various aspects of this disclosure.

[0018] Figure 5C This is a diagram illustrating an example of a UE communicating with two networks based on DSDA services according to various aspects of this disclosure.

[0019] Figure 5D This is a diagram illustrating an example of a UE communicating with two networks based on DSDA services according to various aspects of this disclosure.

[0020] Figure 6 This is a flowchart illustrating examples of configuring a UE (e.g., a positioning device) to have DSDA capability to select a network / subnode for communicating positioning-related information, according to various aspects of this disclosure.

[0021] Figure 7 This is a flowchart illustrating examples of configuring a UE (e.g., a positioning device) to have DSDA capability to select a network / subnode for communicating positioning-related information, according to various aspects of this disclosure.

[0022] Figure 8 This is a flowchart of a wireless communication method.

[0023] Figure 9 This is a flowchart of a wireless communication method.

[0024] Figure 10 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities. Detailed Implementation

[0025] The aspects presented herein can improve the positioning / location performance and latency of devices with Dual Subscriber Identity Module (SIM) Dual Activity (DSDA) features. These aspects can provide faster download speeds and more accurate positioning for devices performing assisted positioning, such as Assisted Global Positioning System (AGPS) positioning and / or cell ID-based positioning. In one aspect of this disclosure, a device (e.g., a DSDA-enabled UE or positioning device) can be configured to assign weights to different networks / subnodes based on specific criteria (such as network resources), and the device can use networks / subnodes with higher weights to download positioning-related information (e.g., information associated with satellites, fixed locations, etc.) to achieve faster download speeds. In one example, the UE may provide different network / subnode weights based on: (1) Reference Signal Received Quality (RSRQ), exact signal strength, and / or signal-to-noise ratio (SNR); (2) Real-time transmit (Tx) / receive (Rx) speeds from lower layers (e.g., data transmission speed); (3) Cellular generation (e.g., 4G LTE, 5G NR, 6G, etc.); (4) Channel load (cell load) or channel traffic; (5) Client bandwidth (e.g., application occupancy on each network / subnode); or (6) a combination thereof. In another aspect of this disclosure, a device (e.g., a DSDA-enabled UE or a positioning device, etc.) may be configured to select (to pre-occupy) a cell ID for positioning (e.g., terrestrial positioning, cell ID-based wireless wide area network (WWAN) positioning, network-based positioning, etc.) based on the selection of the best or more suitable positioning fix derived from a set of cached information associated with multiple cell identifiers (IDs).

[0026] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0027] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0028] As an example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0029] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0030] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0031] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functionality can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0032] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU can be implemented within a RAN node, and one or more DUs can co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations advocated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0034] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0035] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or the associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive and / or transmit signals to one or more other units via wireless transmission media.

[0036] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling as needed.

[0037] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media 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.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0038] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that at least partially 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.) based on functional decomposition such as lower-layer functional decomposition, or both. In this architecture, the RU 140 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration allows the DU 130 and CU 110 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0039] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0040] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0041] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0042] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell) and the secondary component carrier can be referred to as the secondary cell (SCell).

[0043] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as Bluetooth. ® LTE, NR, or Wi-Fi based on the IEEE 802.11 standard ® .

[0044] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether a channel is available before communication.

[0045] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). Although a portion of FR1 is greater than 6GHz, it is generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0046] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands for these IF bands as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0047] In view of the above, unless otherwise specified, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0048] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0049] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0050] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional rate calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals can be based on Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth. ® One or more of the following: signal, terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) method, NR signal (e.g., multiple round trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA) and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0051] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0052] Refer again Figure 1 In some aspects, UE 104 may include a DSDA component 198, which may be configured to establish a connection with a first network entity and a second network entity based on DSDA; select (1) the first network entity or the second network entity for downloading data associated with calculating the UE's location based on at least one criterion, or select (2) fixing for calculating the UE's location based on a set of available cache-based fixings associated with the first network entity and the second network entity; and calculate the UE's location based on the downloaded data or the selected fixings. In some aspects, base station 102 may have a DSDA service component 199, which may be configured to provide DSDA services to devices / UEs with DSDA capabilities.

[0053] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2DFigure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0054] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0055]

[0056] Table 1: Parameter Set, SCS, and CP

[0057] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0058] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0059] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0060] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. 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 (also known as an SS block (SSB)). 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 not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0061] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0062] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0063] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0064] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream undergoes spatial pre-decoding to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine decoding and modulation schemes, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can utilize the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0065] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0066] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0067] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0068] The TX processor 368 can use the reference signal transmitted from the base station 310 or the channel estimate derived from feedback by the channel estimator 358 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0069] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0070] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0071] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 The DSDA component 198 is related to various aspects.

[0072] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform and Figure 1 The DSDA service component 199 is related to various aspects.

[0073] Figure 4 Figure 400 illustrates an example of UE positioning based on reference signal measurements (which may also be referred to as "network-based positioning") according to various aspects of this disclosure. UE 404 can [operate at time T]. SRS_TX Send UL-SRS 412 and at time T PRS_RX Receives the DL positioning reference signal (PRS) (DL-PRS) 410. TRP 406 can be used at time T. SRS_RX Receive UL-SRS 412 and at time T PRS_TX Send DL-PRS 410. UE 404 may receive DL-PRS 410 before sending UL-SRS 412, or may send UL-SRS 412 before receiving DL-PRS 410. In both cases, the location server (e.g., location server 168) or UE 404 may base its response on ||T SRS_RX – T PRS_TX | – |T SRS_TX – T PRS_RX || to determine RTT 414. Therefore, multi-RTT positioning can utilize the UE Rx-Tx time difference measurement (i.e., |T) of downlink signals received from multiple TRPs 402, 406 and measured by UE 404. SRS_TX – T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (i.e., |T) of the uplink signal transmitted from UE404 at multiple TRPs 402, 406. SRS_RX – T PRS_TX|) and UL-SRS-RSRP. UE 404 uses auxiliary data received from the positioning server to measure the UE Rx-Tx time difference (and / or the DL-PRS-RSRP of the received signal), and TRPs 402 and 406 use auxiliary data received from the positioning server to measure the gNB Rx-Tx time difference (and / or the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or at UE 404 to determine the RTT, which is used to estimate the location of UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0074] PRS can be defined for network-based positioning (e.g., NR positioning) to enable the UE to detect and measure more neighboring transmit and receive points (TRPs), supporting various configurations for diverse deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). Beam scanning can also be configured for PRS to support PRS beam operation. The UL positioning reference signal can be based on an enhanced / adjusted probe reference signal (SRS) for positioning purposes. In some examples, the UL-PRS may be referred to as "SRS for Positioning," and new information elements (IEs) can be configured for the SRS for positioning in RRC signaling.

[0075] DL PRS-RSRP can be defined as the linear average of the power contribution (in [W]) of a resource element carrying a DL PRS reference signal configured for RSRP measurement at an antenna port within the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for DL ​​PRS-RSRP can be the UE's antenna connector. For FR2, DL PRS-RSRP can be measured based on a combined signal from an antenna element corresponding to a given receiver branch. For FR1 and FR2, if the UE uses receiver diversity, the reported DL PRS-RSRP value can be no less than the corresponding DL PRS-RSRP of any individual receiver branch within the individual receiver branch. Similarly, UL SRS-RSRP can be defined as the linear average of the power contribution (in [W]) of a resource element carrying a probe reference signal (SRS). UL SRS-RSRP can be measured by a configured resource element within the considered measurement frequency bandwidth at a configured measurement time. In some examples, for FR1, the reference point for UL SRS-RSRP can be the antenna connector of a base station (e.g., gNB). For FR2, the UL SRS-RSRP can be measured based on the combined signal from the antenna element corresponding to a given receiver branch. For FR1 and FR2, if the base station uses receiver diversity, the reported UL SRS-RSRP value may not be lower than the corresponding UL SRS-RSRP of any individual receiver branch within the individual receiver branch.

[0076] PRS-Path RSRP (PRS-RSRPP) can be defined as the power of the linear average of the channel response at the i-th path delay carrying the resource element configured for measurement of the DL PRS signal, where the DL PRS-RSRPP at the first path delay is the power contribution corresponding to the first detected path in time. In some examples, the PRS path phase measurement may refer to the phase associated with the i-th path of the channel derived using the PRS resource.

[0077] DL-AoD positioning utilizes the measured DL-PRS-RSRP of downlink signals received at UE 404 from multiple TRPs 402, 406. UE 404 uses auxiliary data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurement, along with the azimuth departure (A-AoD), zenith departure (Z-AoD), and other configuration information, is used to position UE 404 relative to adjacent TRPs 402, 406.

[0078] DL-TDOA positioning utilizes the DL Reference Signal Time Difference (RSTD) (and / or DL-PRS-RSRP) of downlink signals received at UE 404 from multiple TRPs 402, 406. UE 404 uses auxiliary data received from the positioning server to measure the DL RSTD (and / or DL-PRS-RSRP) of the received signals, and the resulting measurement, along with other configuration information, is used to position UE 404 relative to adjacent TRPs 402, 406.

[0079] UL-TDOA positioning utilizes the UL relative time of arrival (RTOA) (and / or UL-SRS-RSRP) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use auxiliary data received from the positioning server to measure the UL-RTOA (and / or UL-SRS-RSRP) of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the location of UE 404.

[0080] UL-AoA positioning utilizes the measured azimuth (A-AoA) and zenith (Z-AoA) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use auxiliary data received from a positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the position of UE 404. For the purposes of this disclosure, a positioning operation in which the UE provides measurements to a base station / positioning entity / server for calculating the UE's position can be described as "UE-assisted," "UE-assisted positioning," and / or "UE-assisted positioning calculation," while a positioning operation in which the UE measures and calculates its own position can be described as "UE-based," "UE-based positioning," and / or "UE-based positioning calculation."

[0081] Additional positioning methods can be used to estimate the location of UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various technologies can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / improve measurements, and / or replace / provide missing information.

[0082] It should be noted that the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish the types of PRS, downlink positioning reference signals may be referred to as "DL PRS," and uplink positioning reference signals (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS." Additionally, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS."

[0083] Recently, various types of UEs (e.g., mobile phones) have been equipped with the ability to support more than one Subscriber Identity Module (SIM) card (including embedded SIM (eSIM)) (such as two SIM cards). Many mobile operators have also opted to provide support for Dual SIM Dual Activity (DSDA), where a UE can connect to multiple mobile networks via corresponding SIM cards, and the UE can be allowed to communicate simultaneously using different / multiple subscriber accounts and / or networks. For example, each SIM card may be associated with a different subscriber account, a different network, and / or a Radio Access Technology (RAT). For the purposes of this disclosure, the SIM / operator, subscriber account, network, and / or RAT associated with or accessible by the SIM card can be collectively referred to as a “sub-node.” In other words, a sub-node may refer to a SIM / operator.

[0084] Figure 5A , Figure 5B , Figure 5C and Figure 5D Figures 500A, 500B, 500C, and 500D illustrate examples of a UE communicating with two networks based on dual-SIM dual-activity service according to various aspects of this disclosure. The UE 502 may have the capability to support dual / two SIM cards, wherein a first SIM card (SIM#1) enables the UE 502 to communicate with a first network 504 (e.g., a first sub-node operated by a first network operator), and a second SIM card (SIM#2) enables the UE 502 to communicate with a second network 506 (e.g., a second sub-node operated by a second network operator).

[0085] like Figure 5A As shown in Figure 500A, when UE 502 is in standby mode, UE 502 can monitor communication from both the first network 504 and the second network 506. Figure 5B As shown in Figure 500B, when the first SIM card of UE 502 is active (and the second SIM card is in standby mode), UE 502 can use the first SIM card to communicate with the first network 504, and UE 502 can also monitor communication from the second network 506. Similarly, as Figure 5C As shown in Figure 500C, when the second SIM card of UE 502 is active (and the first SIM card is in standby mode), UE 502 can use the second SIM card to communicate with the second network 506, and UE 502 can also monitor communications from the first network 504. Figure 5D As shown in Figure 500D, when both the first SIM card and the second SIM card of UE 502 are active, UE 502 can use their respective SIM cards to communicate with both the first network 504 and the second network 506 simultaneously.

[0086] In some scenarios, certain applications running on UEs supporting dual SIM / DSDA can be configured to use data services based on a first sub-node (sub0) selection and a second sub-node (sub1) selection. In other words, these applications can be configured to select either a first sub-node (associated with the first SIM) or a second sub-node (associated with the second SIM) for data services (e.g., sending data, receiving data, etc.). For example, applications using Assisted Global Positioning System (AGPS or A-GPS) technology (which may also be referred to as GPS-assisted technology or GNSS-assisted services) may not have the ability to select a better / faster network among available networks for faster downloads and / or Global Navigation Satellite System (GNSS) fixing.

[0087] Global Positioning System (GPS) is a technology that enables a UE (e.g., a GPS device) to communicate with multiple (e.g., four or more) satellites to determine its exact location coordinates (e.g., latitude and longitude coordinates) on Earth. While AGPS works on the same principle as GPS, it also allows the UE to obtain satellite-related information by using network resources (e.g., using a mobile network, which can also be called an auxiliary server). In some scenarios, AGPS allows the UE to determine its location coordinates faster because the UE's connectivity with a cell site can be better than direct connectivity with satellites. GNSS fixed (or positioning fixed) can be a term used in navigation to describe positioning derived from measuring an external reference point. For example, fixed can be the location where two positioning lines intersect.

[0088] In another example, for certain applications associated with terrestrial positioning (e.g., cell ID-based wireless wide area network (WWAN) positioning), when a UE pre-occupies a current cell ID while contacting a positioning server (e.g., a cell ID-based WWAN positioning server) to obtain positioning-related information, the UE may be designated to establish a connection with the positioning server based on the current cell ID (e.g., cell ID-based positioning connection) if the positioning accuracy stored in the device file system exceeds a threshold. In other words, the UE may be configured to use the currently occupied cell ID in a session with the positioning server (e.g., a cell ID-based positioning session), regardless of the positioning accuracy stored in the UE file system, and / or the UE may be configured to establish a session with the positioning server on the current network / subnode, regardless of its data link quality. For the purposes of this disclosure, when a UE pre-occupies a cell or cell ID, it may refer to the following process: the UE searches for a suitable cell / cell ID in a selected Public Land Mobile Network (PLMN) (e.g., during / using cell / cell ID selection), selects that cell / cell ID to provide available service, and monitors its control channels. Cell ID-based positioning can be a positioning technique in which one or more base stations continuously broadcast their cell ID messages to UEs within their signal range. In some examples, cell ID-based positioning may also include configuring the UE to download location fixes from a server (e.g., a location server) based on the cell ID.

[0089] The aspects presented herein can improve the positioning performance and latency of devices with DSDA features. These aspects can provide faster download speeds and more accurate positioning for devices performing assisted positioning (such as AGPS positioning and / or cell ID-based positioning). In one aspect of this disclosure, a device (e.g., a DSDA-enabled UE or positioning device) can be configured to assign weights to different networks / subnodes based on specific criteria (such as network resources), and the device can use networks / subnodes with higher weights to download positioning-related information (e.g., information associated with satellites, fixed locations, etc.) to achieve faster download speeds. In one example, the UE may provide different network / subnode weights based on: (1) Reference Signal Received Quality (RSRQ), exact signal strength, and / or signal-to-noise ratio (SNR); (2) Real-time transmit (Tx) / receive (Rx) speeds from lower layers (e.g., data transmission speed); (3) Cellular generation (e.g., 4G LTE, 5G NR, 6G, etc.); (4) Channel load (cell load) or channel traffic; (5) Client bandwidth (e.g., application occupancy on each network / subnode); or (6) a combination thereof. In another aspect of this disclosure, the device (e.g., a DSDA-enabled UE or a positioning device, etc.) may be configured to select (to pre-occupy) a cell ID for positioning (e.g., terrestrial positioning, cell ID-based WWAN positioning, network-based positioning, etc.) based on the selection of the best or more suitable positioning fix derived from a set of cached information associated with multiple cell IDs.

[0090] Figure 6 This is a flowchart 600 illustrating an example of configuring a UE (e.g., a positioning device) with DSDA capability to select a network / subnode for communicating (e.g., downloading) positioning-related information according to various aspects of this disclosure. The aspects presented herein can improve positioning performance and latency by enabling a UE with DSDA capability to select the most suitable network / subnode for assisted positioning (e.g., AGPS positioning, GNSS assisted services, etc.) and / or cell ID-based positioning (e.g., network-based positioning, WWAN positioning, Wi-Fi positioning, etc.) based on one or more criteria.

[0091] Such as combination Figures 5A to 5D As described, UE 602 may include DSDA capability, wherein UE 602 may simultaneously communicate with (and / or monitor communications from) at least a first network / sub-node (e.g., via a first SIM) and a second network / sub-node (e.g., via a second SIM).

[0092] At 604, UE 602 may receive a location download request based on AGPS or cell ID, such as from an application running on UE 602 specifying a location or related service based on AGPS or cell ID (e.g., a navigation application, a map application, etc.). As described above, GPS provides a means of determining location, rate, and time globally. The signal of each satellite may be modulated by a navigation message, which includes the accurate time and coefficients (ephemeris) of a formula describing the satellite's location as a function of time. Receiver (e.g., UE 602) location determination may be based on Time of Arrival (TOA). Four main general GPS receiver functions may include: (1) measuring the distance from the satellite to the receiver by determining the pseudorange (code phase); (2) extracting the TOA of the signal from the content of the messages transmitted by the satellite; (3) calculating the satellite's location by evaluating ephemeris data at the indicated TOA; and (4) calculating the location of the receiving antenna and the clock offset of the receiver using the aforementioned data items.

[0093] Some positioning errors at the receiver can be caused by satellite clocks, satellite orbits, ephemeris predictions, ionospheric delays, and / or tropospheric delays. To reduce these errors, distance and rate of change of distance corrections can be applied to the raw pseudorange measurements to create positioning solutions accurate to meters in open environments. One correction technique is Differential GPS (DGPS), which uses a reference receiver at the surveyed location to transmit correction information to the mobile receiver via a communication link.

[0094] AGPS positioning improves upon GPS positioning performance because GPS positioning can be limited by certain drawbacks. For example, the startup time (e.g., from receiver connection to initial positioning) can be relatively long due to the long acquisition time of navigation messages (e.g., 30 seconds to several minutes). GPS devices may fail to detect weak signals generated by indoor and urban environments (or lower antenna capabilities). The power dissipation per station in GPS positioning can be relatively high, likely due to the long signal acquisition time in unassisted applications. Therefore, the concept of AGPS is to establish a GPS reference network (or wide-area DGPS network) whose receivers have a clear view of the sky and can operate continuously. This reference network can also connect to cellular infrastructure, continuously monitor the real-time constellation status, and provide data such as approximate mobile phone positioning (or base station location), satellite visibility, ephemeris and clock correction, Doppler, and even pseudo-random noise code phase of each satellite at a specific epoch. Upon request from the UE or location-based applications, auxiliary data derived from the GPS reference network is sent to the UE GPS receiver (or sensor) to assist in rapid startup and increase sensor sensitivity. Therefore, acquisition time can be reduced because the Doppler and / or code phase uncertainty space is much smaller than in GPS positioning, since this search space has already been predicted by the reference receiver and network. This allows for faster search speeds and much narrower signal search bandwidth, which enhances sensitivity and reduces UE power consumption.

[0095] At 606, in response to a location download request based on AGPS / cell ID, UE 602 can determine whether to download AGPS data or cell ID data. For example, if UE 602 receives an AGPS download request and UE 602 already has up-to-date AGPS data, then UE 602 can determine that no AGPS data will be downloaded (e.g., from the corresponding server). On the other hand, if UE 602 does not have AGPS data or the AGPS data is not up-to-date, then UE 602 can determine that AGPS data will be downloaded. If UE 602 is specified to download AGPS data, then UE 602 can be configured to execute a first criterion associated with the selection of network / subnode (e.g., as described below in conjunction with 608). On the other hand, if UE 602 is specified to download cell ID data, then UE 602 can be configured to execute a second criterion associated with the selection of cell ID (e.g., as described below in conjunction with 608). Figure 7 (as described).

[0096] At 608, if UE 602 is designated to download AGPS data, UE 602 can be configured to select one of the networks / subnodes for (e.g., from a first network / subnode or a second network / subnode) to download AGPS data. In one aspect of this disclosure, to determine which network / subnode to select for downloading AGPS data, UE 602 can be configured to calculate a weight for each network / subnode based on one or more parameters.

[0097] As shown at 610, in one example, the one or more parameters may include the reference received power (RSRP) between UE 602 and each network / subnode (e.g., the current RSRP in dBm as measured by Layer 1 (L1), ranging from -80dBm to -100dBm), the reference received quality (RSRQ) (e.g., the RSRQ value in dB (a signed integer value) as measured by L1), the exact signal strength, and / or the signal-to-noise ratio (SNR) (e.g., as an SNR level scaled to an integer in 0.1dB). In some examples, UE 602 may also be able to query the signal strength from the corresponding network or network access service (NAS) (e.g., using a NAS_GET_SIG_INFO message) and receive the RSRP, RSRQ, and / or SNR values ​​from the network or NAS. In another example, the one or more parameters may include the real-time transmit (Tx) / receive (Rx) speed (e.g., data transmission speed) from the lower layer between UE 602 and each network / subnode. For example, UE 602 can obtain real-time link speed by querying lower layers. In another example, one or more parameters may include the cellular generation associated with the network / subnode (e.g., 4G LTE, 5G NR, 6G, etc.), where UE 602 can compare modem cellular generations. In another example, these one or more parameters may include channel load (cell load) or channel traffic between UE 602 and each network / subnode. For example, UE 602 can query cell load from the corresponding network using / through an application programming interface (API). In another example, these one or more parameters may include client load / bandwidth (e.g., application occupancy on each network / subnode), which can be made available to UE 602 by obtaining / knowing the application occupancy on each network / subnode.

[0098] Based on one or more of these parameters, UE 602 can calculate the weight of each network / sub-node. For example, a network / sub-node with better RSRP, RSRQ, and / or SNR can be assigned a higher weight compared to a network / sub-node with lower RSRP, RSRQ, and / or SNR. Similarly, a network / sub-node with faster link speed, less client / channel load, and / or newer cellular generation can be assigned a higher weight compared to a network / sub-node with slower link speed, heavier client / channel load, and / or older cellular generation (e.g., 5G can be assigned a higher weight compared to 4G).

[0099] At point 612, based on the calculated weight of each network / sub-node, UE 602 may select one of the networks / sub-nodes to download AGPS data from the server. For example, if the first network / sub-node has a higher weight than the second network / sub-node (because the first network / sub-node may have better RSRP / RSRQ / SNR, link speed, lower client / channel load, and / or a newer cellular generation), then UE 602 may select the first network / sub-node to download AGPS data. On the other hand, if the second network / sub-node has a higher weight than the first network / sub-node, then UE 602 may select the second network / sub-node to download AGPS data. If both networks / sub-nodes have the same weight, then UE 602 may use either network / sub-node to download AGPS data.

[0100] At point 614, after determining which network / subnode to use to download AGPS data, UE 602 can use the corresponding network / subnode to download AGPS data. In one example, AGPS data (or data specifically associated with calculating or deriving the positioning of UE 602) may include: Coordinated Universal Time (UTC), ionospheric (IONO) information, health information, and / or satellite information for one or more satellites. Satellite information for one or more satellites may include: ephemeris for each of the one or more satellites; almanac for each of the one or more satellites; radial coefficient for each of the one or more satellites; cross-track coefficient for each of the one or more satellites; along-track coefficient for each of the one or more satellites; and / or clock offset coefficient for each of the one or more satellites, etc.

[0101] Then, at 616, based on AGPS data, UE 602 can derive a positioning fix, and UE 602 can provide the derived positioning fix to a positioning engine (e.g., a location engine or a GNSS engine), which can be configured to determine the positioning of UE 602. The positioning engine can then provide the estimated positioning of UE 602 to an application that transmits an AGPS download request at 604. For the purposes of this disclosure, a positioning engine (PE) can refer to software or an application that receives positioning-related measurements from a GNSS chipset and / or sensors to estimate the positioning, rate, and / or altitude of the UE (e.g., UE 602).

[0102] Figure 7 This is a flowchart 700 illustrating an example of configuring a UE (e.g., a positioning device) to have DSDA capability to select a network / subnode for conveying (e.g., downloading) positioning-related information according to various aspects of this disclosure.

[0103] At position 702, if combined Figure 6 As discussed in section 606, if UE 602 is designated to download cell ID data, UE 602 can be configured to execute a second criterion associated with the selection of a cell or cell ID. As mentioned above, cell ID-based positioning or cell ID-based WWAN positioning can refer to positioning that uses the cell ID to specify downloading fixed data from the server to assist the UE in positioning.

[0104] At 704, when selecting a cell or cell ID, UE 602 may check whether any fixes associated with the cell / cell ID of the first network / subnode and / or the second network subnode exceed a predefined threshold (e.g., an accuracy threshold). In some examples, these fixes may be stored in the UE 602's non-volatile file system (e.g., from a previous location session or download), and they may be referred to as "cache-based fixes".

[0105] For example, UE 602 may have received and stored a first cache-based fix associated with a cell / cell ID of a first network / subnode (e.g., obtained when UE 602 pre-allocated the cell / cell ID), and UE 602 may also have received and stored a second cache-based fix associated with a cell / cell ID of a second network / subnode (e.g., obtained when UE 602 pre-allocated the cell / cell ID), etc. UE 602 can then determine or verify whether either the first cache-based fix or the second cache-based fix exceeds a predefined accuracy threshold. For example, UE 602 can check whether the Level Estimated Positioning Error (HEPE) value and / or Positioning Uncertainty (PUNC) value of the first cache-based fix and the second cache-based fix exceed the HEPE / PUNC threshold.

[0106] At 706, if at least one cache-based fix exceeds a predefined accuracy threshold (e.g., the HEPE / PUNC threshold), UE 602 can select a cache-based fix from the at least one cache-based fix as the fix used for positioning (e.g., as a positioning fix). In one example, if multiple cache-based fixes exceed the predefined accuracy threshold, UE 602 can be configured to select the cache-based fix with the best HEPE / PUNC value (e.g., the lowest HEPE / PUNC value). In other words, UE 602 can check the best HEPE / PUNC value among two cached fixes (Network 1 / Subnode 1 and Network 2 / Subnode 2) stored in UE 602's non-volatile file system, and if both cache-based fixes meet the threshold criterion, the best subcarrier-based cache-based fix will be used based on the PUNC / HEPE value. On the other hand, if only one cache-based fix exceeds the predefined accuracy threshold, UE 602 can use only that cache-based fix as the positioning fix.

[0107] At 708, after UE 602 selects a cache-based fixation that can be used for positioning fixation, UE 602 can provide this positioning fixation to a positioning engine (e.g., a location engine or a GNSS engine), which can be configured to determine the positioning of UE 602. The positioning engine can then provide the estimated positioning of UE 602 to a transmission (e.g., as combined with...). Figure 6 The application of location download requests based on cell ID (discussed in section 604).

[0108] On the other hand, if none of the cache-based fixes exceed a predefined accuracy threshold, then at 710, UE 602 can be configured to download two network / subnode fixes (which may be referred to as cell ID-based fixes and / or WWAN-based fixes) and cell ID (plot) information based on DSDA. For example, based on the current cell ID occupied by UE 602, cell ID (plot) information can be downloaded to UE 602, where the cell ID (plot) information may include the cell ID (e.g., Mobile Country Code (MCC), Mobile Network Code (MNC), Tracking Area Code (TAC), network mode, etc.) and its associated location information (e.g., latitude and longitude coordinates).

[0109] At 712, after obtaining the fixed and cell ID (pattern) information of the two networks / subnodes based on DSDA, UE 602 can select the most suitable or best fixed as the positioning fixed (e.g., for performing positioning) from the fixed, such as by comparing the HEPE / PUNC values ​​of the two fixed fixeds derived from the first network / subnode and the second network / subnode. Similarly, at 708, after UE 602 selects a fixed that can be used as the positioning fixed, UE 602 can provide the positioning fixed to the positioning engine, which can be configured to determine the positioning of UE 602. The positioning engine can then provide the estimated positioning of UE 602 to the transmission (e.g., as in combination with...). Figure 6 The application of location download requests based on cell ID (discussed in section 604).

[0110] Such as combination Figure 7 and Figure 8 As described, for AGPS data download, criterion 1 can be considered, while for cell ID data download (e.g., cell partition download), criterion 2 can be considered. The case where the first network / sub-node is faster than the second network / sub-node is considered. When the UE 602's modem is in DSDA mode, the AGPS / cell ID-based positioning client can be configured to access network resources and specified to select between the first and second networks / sub-nodes. Based on the combination... Figure 7 and Figure 8 In accordance with the described aspects, the modem may first check Criterion 1 and / or Criterion 2 before selecting any network / sub-node. Then, based on the weights according to Criterion 1 and / or Criterion 2, the modem may select the best or most suitable network / sub-node (e.g., the first network / sub-node) to achieve better service delivery and end-user experience. Therefore, the algorithm described herein can be used to improve location positioning performance (faster download of AGPS / cell ID data).

[0111] Figure 8 This is a flowchart 800 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, 404, 502, 602; device 1004). This method enables the UE to improve positioning performance and latency based on DSDA features.

[0112] At point 802, the UE can establish connections with the first and second network entities based on DSDA, such as combining... Figure 5A , Figure 5B , Figure 5C and Figure 5D , Figure 6 and Figure 7 As described. For example, as in combination Figure 6As discussed, UE 602 may include DSDA capability, wherein UE 602 can simultaneously communicate (and / or monitor communications from) at least a first network / sub-node (e.g., via a first SIM) and a second network / sub-node (e.g., via a second SIM). Connection establishment may be achieved by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0113] At 804, the UE may choose (1) a first network entity or a second network entity to download data associated with calculating the UE's location based on at least one criterion, or choose (2) fixation to calculate the UE's location based on an available cache-based set of fixes associated with the first and second network entities, such as combining... Figure 6 and Figure 7 As described. For example, in Figure 6 At 612, UE 602 can select a network / subnode from multiple networks / subnodes for downloading AGPS data based on the weights of multiple networks / subnodes calculated using one or more criteria (e.g., as shown at 610), which can be used to calculate the positioning of UE 602. Figure 7 At positions 706 or 712, UE 602 can also select the best / suitable fixture for positioning by comparing the HEPE / PUNC values ​​of the fixed set. The selection can be made by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0114] In one example, at least one criterion may include at least one of the following: Reference Signal Received Power (RSRP); Reference Signal Received Quality (RSRQ); Signal-to-Noise Ratio (SNR); Data Transmission Rate; Type of Cellular Network; Application Occupancy; Channel or Cell Load; or Available Bandwidth.

[0115] In another example, the data associated with calculating the UE's positioning includes at least one of the following: Coordinated Universal Time (UTC); ionospheric (IONO) information; health information; or satellite information of one or more satellites. In some specific implementations, the satellite information of one or more satellites may include at least one of the following: ephemeris of each of the one or more satellites; almanac of each of the one or more satellites; radial coefficient of each of the one or more satellites; cross-track coefficient of each of the one or more satellites; along-track coefficient of each of the one or more satellites; or clock offset coefficient of each of the one or more satellites.

[0116] At point 806, the UE can calculate its location based on downloaded data or selected fixed locations, such as combining... Figure 6 and Figure 7 As described. For example, in Figure 6 At position 616, based on AGPS data, UE 602 can derive a fixed location, and UE 602 can provide the derived fixed location to a positioning engine (e.g., a location engine or a GNSS engine), which can be configured to determine the location of UE 602. The calculation of the UE's location can be performed by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0117] In one example, if the UE selects a first network entity or a second network entity to download data associated with calculating the UE's location based on at least one criterion, the UE may calculate the weight of each of the first and second network entities based on at least one criterion; and select the first or second network entity to download data associated with calculating the UE's location based on the first or second network entity having the highest calculated weight, such as combining... Figure 6 As described. For example, at 608, if UE 602 is designated to download AGPS data, UE 602 can be configured to select one of the networks / sub-nodes for (e.g., from a first network / sub-node or a second network / sub-node) downloading AGPS data. In one aspect of this disclosure, in order to determine which network / sub-node to select for downloading AGPS data, UE 602 can be configured to calculate a weight for each network / sub-node based on one or more parameters. Calculating the weights and selecting a first network entity or a second network entity for downloading data can be, for example, by Figure 10 The device 1004 utilizes the DSDA component 198, application processor 1006, cellular baseband processor 1024, and / or transceiver 1022 to perform this function. In some embodiments, to calculate the UE's location based on downloaded data, the UE may derive a second fix based on the downloaded data and calculate the UE's location based on the second fix. In some embodiments, the calculation of the UE's location is associated with Assisted Global Positioning System (AGPS) service or Global Navigation Satellite System (GNSS) assisted service.

[0118] In another example, if the UE selects a fix for calculating its location based on a set of available cached fixes associated with a first network entity and a second network entity, the UE can determine that at least one cached fix in the set of available cached fixes has a Level Estimated Positioning Error (HEPE) or Positioning Uncertainty (PUNC) that satisfies an accuracy threshold, wherein the selected fix may correspond to at least one cached fix with the lowest HEPE or lowest PUNC, such as combining... Figure 7 As described. For example, at 706, if at least one cache-based fix exceeds a predefined accuracy threshold (e.g., a HEPE / PUNC threshold), UE 602 can select a cache-based fix from the at least one cache-based fix as the fix used for positioning (e.g., as a positioning fix). In one example, if multiple cache-based fixes exceed a predefined accuracy threshold, UE 602 can be configured to select the cache-based fix with the best HEPE / PUNC value. The HEPE or PUNC of at least one cache-based fix can be determined by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0119] In another example, if the UE selects a fix for calculating its location based on a set of available cached fixes associated with a first network entity and a second network entity, the UE may determine that the HEPE or PUNC of each cached fix in the set of cached fixes does not meet an accuracy threshold; obtain a first cell identifier (ID) from the first network entity and a second cell ID from the second network entity; and derive a first fix associated with the first network entity based on the first cell ID information, and derive a second fix associated with the second network entity based on the second cell ID information, wherein the selected fix corresponds to either the first fix or the second fix with the lowest HEPE or the lowest PUNC, such as combining... Figure 7As described. For example, if none of the cache-based fixes exceed a predefined accuracy threshold, then at 710, UE 602 can be configured to download the fixes and cell ID (pattern) information of two networks / subnodes based on DSDA. At 712, after obtaining the fixes and cell ID (pattern) information of two networks / subnodes based on DSDA, UE 602 can select the most suitable or best fix as the positioning fix (e.g., for performing positioning) among the fixes, such as by comparing the HEPE / PUNC values ​​of the two fixes derived from the first network / subnode and the second network / subnode. Similarly, at 708, after UE 602 selects a fix that can be used as a positioning fix, UE 602 can provide the positioning fix to a positioning engine, which can be configured to determine the positioning of UE 602. Determining the HEPE or PUNC of each cache-based fix, obtaining the first cell ID information and the second cell ID information, and / or deriving the first fix and the second fix can be done by, for example... Figure 10 The calculation of the UE's location is performed by the DSDA component 198, application processor 1006, cellular baseband processor 1024, and / or transceiver 1022 of the device 1004. In some specific implementations, the calculation of the UE's location may be associated with location based on cell ID.

[0120] In another example, the UE can store a fixed set based on cache in the UE's non-volatile file system.

[0121] In another example, in order to calculate the UE's location based on downloaded data or selected fixes, the UE may provide the downloaded data or selected fixes to the location engine associated with the calculation of the UE's location.

[0122] In another example, the first network entity and the second network entity may be associated with different mobile operators.

[0123] Figure 9 This is a flowchart 900 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, 404, 502, 602; device 1004). This method enables the UE to improve positioning performance and latency based on DSDA features.

[0124] At point 902, the UE can establish connections with the first and second network entities based on DSDA, such as combining... Figure 5A , Figure 5B , Figure 5C and Figure 5D , Figure 6 and Figure 7 As described. For example, as in combination Figure 6As discussed, UE 602 may include DSDA capability, wherein UE 602 can simultaneously communicate (and / or monitor communications from) at least a first network / sub-node (e.g., via a first SIM) and a second network / sub-node (e.g., via a second SIM). Connection establishment may be achieved by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0125] At 904, the UE can choose (1) a first network entity or a second network entity to download data associated with calculating the UE's location based on at least one criterion, or choose (2) fixation to calculate the UE's location based on an available cache-based set of fixes associated with the first and second network entities, such as combining... Figure 6 and Figure 7 As described. For example, in Figure 6 At 612, UE 602 can select a network / subnode from multiple networks / subnodes for downloading AGPS data based on the weights of multiple networks / subnodes calculated using one or more criteria (e.g., as shown at 610), which can be used to calculate the positioning of UE 602. Figure 7 At positions 706 or 712, UE 602 can also select the best / suitable fixture for positioning by comparing the HEPE / PUNC values ​​of the fixed set. The selection can be made by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0126] In one example, at least one criterion may include at least one of the following: RSRP; RSRQ; SNR; data transmission rate; type of cellular network; application occupancy; channel or cell load; or available bandwidth.

[0127] In another example, the data associated with calculating the UE's positioning includes at least one of the following: UTC; IONO information; health information; or satellite information of one or more satellites. In some specific implementations, the satellite information of one or more satellites may include at least one of the following: ephemeris of each of the one or more satellites; almanac of each of the one or more satellites; radial coefficient of each of the one or more satellites; cross-track coefficient of each of the one or more satellites; along-track coefficient of each of the one or more satellites; or clock offset coefficient of each of the one or more satellites.

[0128] At point 906, the UE can calculate its location based on downloaded data or selected fixed locations, such as combining... Figure 6 and Figure 7 As described. For example, in Figure 6 At position 616, based on AGPS data, UE 602 can derive a fixed location, and UE 602 can provide the derived fixed location to a positioning engine (e.g., a location engine or a GNSS engine), which can be configured to determine the location of UE 602. The calculation of the UE's location can be performed by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0129] In one example, at 908, if the UE selects a first network entity or a second network entity to download data associated with calculating the UE's location based on at least one criterion, the UE may calculate the weight of each of the first and second network entities based on at least one criterion; and select the first or second network entity to download data associated with calculating the UE's location based on the first or second network entity having the highest calculated weight, such as combining... Figure 6 As described. For example, at 608, if UE 602 is designated to download AGPS data, UE 602 can be configured to select one of the networks / sub-nodes for (e.g., from a first network / sub-node or a second network / sub-node) downloading AGPS data. In one aspect of this disclosure, in order to determine which network / sub-node to select for downloading AGPS data, UE 602 can be configured to calculate a weight for each network / sub-node based on one or more parameters. Calculating the weights and selecting a first network entity or a second network entity for downloading data can be, for example, by Figure 10 The device 1004 utilizes the DSDA component 198, application processor 1006, cellular baseband processor 1024, and / or transceiver 1022 to perform this function. In some embodiments, to calculate the UE's location based on downloaded data, the UE may derive a second fix based on the downloaded data and calculate the UE's location based on the second fix. In some embodiments, the calculation of the UE's location is associated with AGPS services or GNSS-assisted services.

[0130] In another example, at 910, if the UE selects a fix for calculating its location based on a set of available cached fixes associated with the first and second network entities, the UE can determine that at least one cached fix in the set of available cached fixes satisfies an accuracy threshold for HEPE or PUNC, wherein the selected fix may correspond to at least one cached fix with the lowest HEPE or lowest PUNC, such as in combination. Figure 7 As described. For example, at 706, if at least one cache-based fix exceeds a predefined accuracy threshold (e.g., a HEPE / PUNC threshold), UE 602 can select a cache-based fix from the at least one cache-based fix as the fix used for positioning (e.g., as a positioning fix). In one example, if multiple cache-based fixes exceed a predefined accuracy threshold, UE 602 can be configured to select the cache-based fix with the best HEPE / PUNC value. The HEPE or PUNC of at least one cache-based fix can be determined by, for example... Figure 10 The device 1004 is executed by the DSDA component 198, application processor 1006, cellular baseband processor 1024 and / or transceiver 1022.

[0131] In another example, at 912, if the UE selects a fix for calculating the UE's location based on a set of available cached fixes associated with a first network entity and a second network entity, the UE may determine that the HEPE or PUNC of each cached fix in the set of cached fixes does not meet an accuracy threshold; obtain first cell ID information from the first network entity and second cell ID information from the second network entity; and derive a first fix associated with the first network entity based on the first cell ID information and derive a second fix associated with the second network entity based on the second cell ID information, wherein the selected fix corresponds to the first fix or the second fix with the lowest HEPE or lowest PUNC, such as combining... Figure 7As described. For example, if none of the cache-based fixes exceed a predefined accuracy threshold, then at 710, UE 602 can be configured to download the fixes and cell ID (pattern) information of two networks / subnodes based on DSDA. At 712, after obtaining the fixes and cell ID (pattern) information of two networks / subnodes based on DSDA, UE 602 can select the most suitable or best fix as the positioning fix (e.g., for performing positioning) among the fixes, such as by comparing the HEPE / PUNC values ​​of the two fixes derived from the first network / subnode and the second network / subnode. Similarly, at 708, after UE 602 selects a fix that can be used as a positioning fix, UE 602 can provide the positioning fix to a positioning engine, which can be configured to determine the positioning of UE 602. Determining the HEPE or PUNC of each cache-based fix, obtaining the first cell ID information and the second cell ID information, and / or deriving the first fix and the second fix can be done by, for example... Figure 10 The calculation of the UE's location is performed by the DSDA component 198, application processor 1006, cellular baseband processor 1024, and / or transceiver 1022 of the device 1004. In some specific implementations, the calculation of the UE's location may be associated with location based on cell ID.

[0132] In another example, the UE can store a fixed set based on cache in the UE's non-volatile file system.

[0133] In another example, in order to calculate the UE's location based on downloaded data or selected fixes, the UE may provide the downloaded data or selected fixes to the location engine associated with the calculation of the UE's location.

[0134] In another example, the first network entity and the second network entity may be associated with different mobile operators.

[0135] Figure 10 Figure 1000 illustrates an example of a specific hardware implementation for device 1004. Device 1004 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1004 may include a cellular baseband processor 1024 (also referred to as a modem) coupled to one or more transceivers 1022 (e.g., cellular RF transceivers). Cellular baseband processor 1024 may include on-chip memory 1024'. In some aspects, device 1004 may also include one or more Subscriber Identity Module (SIM) cards 1020 and an application processor 1006 coupled to a Secure Digital (SD) card 1008 and a screen 1010. Application processor 1006 may include on-chip memory 1006'. In some aspects, device 1004 may also include Bluetooth. ®Module 1012, WLAN module 1014, SPS module 1016 (e.g., GNSS module), Ultra-Wideband (UWB) module 1036, one or more sensor modules 1018 (e.g., atmospheric pressure sensor / altimeter; motion sensor, such as inertial measurement unit (IMU), gyroscope and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and / or other technologies for positioning), additional memory module 1026, power source 1030 and / or camera 1032. Bluetooth. ® Modules 1012, WLAN module 1014, UWB module 1036, and SPS module 1016 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). Bluetooth ® Module 1012, WLAN module 1014, UWB module 1036, and SPS module 1016 may include their own dedicated antennas and / or communicate using antenna 1080. Cellular baseband processor 1024 communicates with UE 104 and / or RU associated with network entity 1002 via transceiver 1022 through one or more antennas 1080. Cellular baseband processor 1024 and application processor 1006 may each include computer-readable media / memory 1024', 1006'. Additional memory module 1026 may also be considered as computer-readable media / memory. Each computer-readable media / memory 1024', 1006', 1026 may be non-transitory. Cellular baseband processor 1024 and application processor 1006 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1024 / application processor 1006, the software causes the cellular baseband processor 1024 / application processor 1006 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1024 / application processor 1006 during software execution. The cellular baseband processor 1024 / application processor 1006 may be a component of the UE 350 and may include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, the device 1004 may be a processor chip (modem and / or application) and includes only the cellular baseband processor 1024 and / or application processor 1006, while in another configuration, the device 1004 may be the entire UE (e.g., see...). Figure 3 The UE 350 includes an additional module of the device 1004.

[0136] As discussed above, DSDA component 198 can be configured to establish connections with a first network entity and a second network entity based on DSDA. DSDA component 198 can also be configured to select (1) a first network entity or a second network entity for downloading data associated with calculating the UE's location based on at least one criterion, or select (2) a fixation for calculating the UE's location based on a set of available cache-based fixes associated with the first and second network entities. DSDA component 198 can also be configured to calculate the UE's location based on the downloaded data or the selected fixation. DSDA component 198 can be located within cellular baseband processor 1024, application processor 1006, or both cellular baseband processor 1024 and application processor 1006. DSDA component 198 can be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, apparatus 1004 can include various components configured for various functions. In one configuration, device 1004 (and specifically, cellular baseband processor 1024 and / or application processor 1006) may include components for establishing connections with a first network entity and a second network entity based on DSDA. Device 1004 may also include components for selecting (1) a first network entity or a second network entity for downloading data associated with calculating the location of device 1004 based on at least one criterion, or selecting (2) a fixation for calculating the location of device 1004 based on a set of available cache-based fixes associated with the first and second network entities. Device 1004 may also include components for calculating the location of device 1004 based on the downloaded data or the selected fixation.

[0137] In one configuration, at least one criterion may include at least one of the following: RSRP; RSRQ; SNR; data transmission rate; cellular network type; application occupancy; channel or cell load; or available bandwidth.

[0138] In another configuration, the data associated with the positioning of computing device 1004 includes at least one of the following: UTC; IONO information; health information; or satellite information of one or more satellites. In some specific embodiments, the satellite information of one or more satellites may include at least one of the following: ephemeris of each of the one or more satellites; almanac of each of the one or more satellites; radial coefficient of each of the one or more satellites; cross-track coefficient of each of the one or more satellites; along-track coefficient of each of the one or more satellites; or clock skew coefficient of each of the one or more satellites.

[0139] In another configuration, the components for selecting a first network entity or a second network entity for downloading data associated with calculating the location of device 1004 based on at least one criterion may include: configuring device 1004 to calculate the weight of each of the first network entity and the second network entity based on at least one criterion; and selecting the first network entity or the second network entity for downloading data associated with calculating the location of device 1004 based on the first network entity or the second network entity having the highest calculated weight. In some specific implementations, the calculation of the location of device 1004 is associated with AGPS services or GNSS-assisted services.

[0140] In another configuration, the component for selecting a first network entity or a second network entity for downloading data associated with the location of the device 1004 based on at least one criterion may include: configuring the device 1004 to determine that at least one cached fix in a set of available cached fixes has a HEPE or PUNC that satisfies an accuracy threshold, wherein the selected fix may correspond to at least one cached fix with the lowest HEPE or lowest PUNC.

[0141] In another configuration, the components for selecting a first network entity or a second network entity for downloading data associated with calculating the location of device 1004 based on at least one criterion may include: configuring device 1004 to determine that the HEPE or PUNC of each cached fix in a set of cached fixes does not meet an accuracy threshold; obtaining first cell ID information from the first network entity and second cell ID information from the second network entity; and deriving a first fix associated with the first network entity based on the first cell ID information and deriving a second fix associated with the second network entity based on the second cell ID information, wherein the selected fix corresponds to the first fix or the second fix having the lowest HEPE or the lowest PUNC. In some specific implementations, the calculation of the location of device 1004 may be associated with cell ID-based location.

[0142] In another configuration, the device 1004 may also include components for storing a cache-based fixed set in a non-volatile file system of the device 1004.

[0143] In another configuration, the components for calculating the location of device 1004 based on downloaded data or selected fixation may include: configuring device 1004 to provide the downloaded data or selected fixation to a positioning engine associated with the calculation of the location of device 1004.

[0144] In another configuration, the first network entity and the second network entity can be associated with different mobile operators.

[0145] The component may be a DSDA component 198 of device 1004 configured to perform the functions described therein. As described above, device 1004 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions described therein.

[0146] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0147] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when…”, do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to "output" data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to "receive" data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims.Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” cannot replace the term “component.” Therefore, no claim element will be interpreted as a functional component unless the element is explicitly stated using the phrase “component for…”.

[0148] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0149] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0150] Aspect 1 is a method for wireless communication at a user equipment (UE), the method comprising: establishing a connection with a first network entity and a second network entity based on dual subscriber identity module (SIM) dual activity (DSDA); selecting (1) the first network entity or the second network entity for downloading data associated with calculating the location of the UE based on at least one criterion, or selecting (2) fixing for calculating the location of the UE based on a cache-based set of available fixings associated with the first network entity and the second network entity; and calculating the location of the UE based on the downloaded data or the selected fixing.

[0151] Aspect 2 is the method according to aspect 1, wherein selecting the first network entity or the second network entity for downloading the data associated with calculating the location of the UE based on the at least one criterion includes: calculating the weight of each of the first network entity and the second network entity based on the at least one criterion; and selecting the first network entity or the second network entity for downloading the data associated with calculating the location of the UE based on the first network entity or the second network entity having the highest calculated weight.

[0152] Aspect 3 is the method according to aspect 1 or 2, wherein calculating the location of the UE based on the downloaded data includes: deriving a second fixation based on the downloaded data; and calculating the location of the UE based on the second fixation.

[0153] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein the calculation of the positioning of the UE is associated with Assisted Global Positioning System (AGPS) service or Assisted Global Navigation Satellite System (GNSS) service.

[0154] Aspect 5 is a method according to any one of Aspects 1 to 4, wherein the at least one criterion includes at least one of the following: reference signal received power (RSRP); reference signal received quality (RSRQ); signal-to-noise ratio (SNR); data transmission rate; type of cellular network; application occupancy; channel or cell load; or available bandwidth.

[0155] Aspect 6 is the method according to any one of Aspects 1 to 5, wherein the data associated with calculating the location of the UE includes at least one of: Coordinated Universal Time (UTC); ionospheric (IONO) information; health information; or satellite information of one or more satellites.

[0156] Aspect 7 is the method according to any one of Aspects 1 to 6, wherein the satellite information of the one or more satellites includes at least one of the following: ephemeris of each of the one or more satellites; calendar of each of the one or more satellites; radial coefficient of each of the one or more satellites; cross-track coefficient of each of the one or more satellites; along-track coefficient of each of the one or more satellites; or clock offset coefficient of each of the one or more satellites.

[0157] Aspect 8 is a method according to any one of Aspect 1, wherein selecting the fix for calculating the location of the UE based on the set of available cache-based fixes associated with the first network entity and the second network entity comprises: determining that at least one cache-based fix in the set of available cache-based fixes has a level estimated positioning error (HEPE) or positioning uncertainty (PUNC) that satisfies an accuracy threshold, wherein the selected fix corresponds to the cache-based fix with the lowest HEPE or the lowest PUNC among the at least one cache-based fix.

[0158] Aspect 9 is the method according to aspect 1, wherein selecting the fix for calculating the UE's location based on the set of available cache-based fixes associated with the first network entity and the second network entity comprises: determining that the level estimated positioning error (HEPE) or positioning uncertainty (PUNC) of each cache-based fix in the set of cache-based fixes does not meet an accuracy threshold; obtaining a first cell identifier (ID) from the first network entity and obtaining a second cell ID from the second network entity; and deriving a first fix associated with the first network entity based on the first cell ID information and deriving a second fix associated with the second network entity based on the second cell ID information, wherein the selected fix corresponds to the first fix or the second fix having the lowest HEPE or the lowest PUNC.

[0159] Aspect 10 is the method according to any one of Aspects 8 to 9, wherein the calculation of the location of the UE is associated with location based on cell ID.

[0160] Aspect 11 is the method according to any one of aspects 1 to 10, the method further comprising: storing the cache-based fixed set in the non-volatile file system of the UE.

[0161] Aspect 12 is a method according to any one of aspects 1 to 11, wherein calculating the location of the UE based on downloaded data or selected fixation comprises: providing the downloaded data or selected fixation to a location engine associated with the calculation of the location of the UE.

[0162] Aspect 13 is the method according to aspect 12, wherein the first network entity and the second network entity are associated with different mobile operators.

[0163] Aspect 14 is the method according to any one of aspects 1 to 13, the method further comprising: outputting an indication of the calculated positioning of the UE.

[0164] Aspect 15 is the method according to aspect 14, wherein outputting the indication of the calculated location of the UE includes: sending the indication of the calculated location of the UE; or storing the indication of the calculated location of the UE.

[0165] Aspect 16 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a memory; and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor being configured to implement any one of aspects 1 to 15.

[0166] Aspect 17 is the apparatus according to aspect 16, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0167] Aspect 18 is an apparatus for wireless communication, the apparatus comprising: components for implementing any one of aspects 1 to 15.

[0168] Aspect 19 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 15.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: The connection with the first network entity and the second network entity is established based on the Dual Subscriber Identity Module (SIM) Dual Activity (DSDA). Choose (1) the first network entity or the second network entity to download data associated with calculating the location of the UE based on at least one criterion, or choose (2) fixation to calculate the location of the UE based on a cache-based fixed set of available data associated with the first network entity and the second network entity; as well as The UE's location is calculated based on the downloaded data or the selected fixed location.

2. The apparatus of claim 1, wherein, in order to select the first network entity or the second network entity for downloading the data associated with calculating the location of the UE based on the at least one criterion, the at least one processor is configured to: The weight of each of the first network entity and the second network entity is calculated based on at least one of the criteria; and Based on the fact that the first network entity or the second network entity has the highest computational weight, the first network entity or the second network entity is selected for downloading the data associated with calculating the location of the UE.

3. The apparatus of claim 2, wherein, in order to calculate the location of the UE based on the downloaded data, the at least one processor is configured to: Export the second fixed value based on the downloaded data; and The UE's location is calculated based on the second fixed value.

4. The apparatus of claim 2, wherein the calculation of the positioning of the UE is associated with an Assisted Global Positioning System (AGPS) service or a Global Navigation Satellite System (GNSS) assisted service.

5. The apparatus of claim 1, wherein the at least one criterion comprises at least one of the following: Reference signal received power (RSRP). Reference signal reception quality (RSRQ) Signal-to-noise ratio (SNR). Data transmission speed Types of cellular networks Application usage rate The load of the channel or cell, or Available bandwidth.

6. The apparatus of claim 1, wherein the data associated with calculating the location of the UE includes at least one of the following: Coordinated Universal Time (UTC) Ionospheric (IONO) information, Health information, or Satellite information for one or more satellites.

7. The apparatus of claim 6, wherein the satellite information of the one or more satellites includes at least one of the following: Ephemeris of each of the one or more satellites The calendar for each of the one or more satellites, The radial coefficient of each of the one or more satellites, The cross-trajectory coefficients of each of the one or more satellites. The orbital coefficient of each of the one or more satellites, or Clock offset coefficient for each of the one or more satellites.

8. The apparatus of claim 1, wherein, in order to select the fixation for calculating the UE's location based on the set of available cache-based fixes associated with the first network entity and the second network entity, the at least one processor is configured to: Determine at least one cache-based fix in the set of available cache-based fixes whose level estimation positioning error (HEPE) or positioning uncertainty (PUNC) satisfies an accuracy threshold, wherein the selected fix corresponds to the cache-based fix with the lowest HEPE or lowest PUNC among the at least one cache-based fixes.

9. The apparatus of claim 1, wherein, in order to select the fixation for calculating the UE's location based on the set of available cache-based fixes associated with the first network entity and the second network entity, the at least one processor is configured to: Determine that each of the cache-based fixed level estimation positioning error (HEPE) or positioning uncertainty (PUNC) in the set does not meet the accuracy threshold; Obtain the first cell identifier (ID) from the first network entity, and obtain the second cell ID from the second network entity; and A first fix associated with the first network entity is derived based on the first cell ID, and a second fix associated with the second network entity is derived based on the second cell ID, wherein the selected fix corresponds to the first fix or the second fix having the lowest HEPE or the lowest PUNC.

10. The apparatus of claim 9, wherein the calculation of the location of the UE is associated with location based on cell ID.

11. The apparatus of claim 1, wherein the at least one processor is further configured to: The fixed set based on cache is stored in the non-volatile file system of the UE.

12. The apparatus of claim 1, wherein, in order to calculate the location of the UE based on downloaded data or a selected location, the at least one processor is configured to: The downloaded data or the selected fix is ​​provided to the positioning engine associated with the calculation of the positioning of the UE.

13. The apparatus of claim 1, wherein the first network entity and the second network entity are associated with different mobile operators.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: Output an indication of the calculated location of the UE.

15. The apparatus of claim 14, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to output the indication of the calculated location of the UE, the at least one processor is configured to: Transmit the calculated location indication for the UE via at least one of the transceiver or the antenna; or The indication of the calculated location of the UE is stored.

16. A method for conducting wireless communication at a user equipment (UE), the method comprising: The connection with the first network entity and the second network entity is established based on the Dual Subscriber Identity Module (SIM) Dual Activity (DSDA). Choose (1) the first network entity or the second network entity to download data associated with calculating the location of the UE based on at least one criterion, or choose (2) fixation to calculate the location of the UE based on a cache-based fixed set of available data associated with the first network entity and the second network entity; as well as The UE's location is calculated based on the downloaded data or the selected fixed location.

17. The method of claim 16, wherein selecting the first network entity or the second network entity for downloading the data associated with calculating the location of the UE based on the at least one criterion comprises: The weight of each of the first network entity and the second network entity is calculated based on the at least one criterion. as well as Based on the fact that the first network entity or the second network entity has the highest computational weight, the first network entity or the second network entity is selected for downloading the data associated with calculating the location of the UE.

18. The method of claim 17, wherein calculating the location of the UE based on the downloaded data comprises: Export the second fixed data based on the downloaded data; as well as The UE's location is calculated based on the second fixed value.

19. The method of claim 17, wherein the calculation of the positioning of the UE is associated with an Assisted Global Positioning System (AGPS) service or a Global Navigation Satellite System (GNSS) assisted service.

20. The method of claim 16, wherein the at least one criterion comprises at least one of the following: Reference signal received power (RSRP). Reference signal reception quality (RSRQ) Signal-to-noise ratio (SNR). Data transmission speed Types of cellular networks Application usage rate The load of the channel or cell, or Available bandwidth.

21. The method of claim 16, wherein the data associated with calculating the location of the UE comprises at least one of the following: Coordinated Universal Time (UTC) Ionospheric (IONO) information, Health information, or Satellite information for one or more satellites.

22. The method of claim 21, wherein the satellite information of the one or more satellites includes at least one of the following: Ephemeris of each of the one or more satellites The calendar for each of the one or more satellites, The radial coefficient of each of the one or more satellites, The cross-trajectory coefficients of each of the one or more satellites. The orbital coefficient of each of the one or more satellites, or Clock offset coefficient for each of the one or more satellites.

23. The method of claim 16, wherein selecting the fixation for calculating the UE's location based on the set of available cache-based fixes associated with the first network entity and the second network entity comprises: Determine at least one cache-based fix in the set of available cache-based fixes whose level estimation positioning error (HEPE) or positioning uncertainty (PUNC) satisfies an accuracy threshold, wherein the selected fix corresponds to the cache-based fix with the lowest HEPE or lowest PUNC among the at least one cache-based fixes.

24. The method of claim 16, wherein selecting the fixation for calculating the UE's location based on the set of available cache-based fixes associated with the first network entity and the second network entity comprises: Determine that each of the cache-based fixed level estimation positioning error (HEPE) or positioning uncertainty (PUNC) in the set does not meet the accuracy threshold; Obtain the first cell identifier (ID) from the first network entity, and obtain the second cell ID from the second network entity; as well as A first fix associated with the first network entity is derived based on the first cell ID, and a second fix associated with the second network entity is derived based on the second cell ID, wherein the selected fix corresponds to the first fix or the second fix having the lowest HEPE or the lowest PUNC.

25. The method of claim 24, wherein the calculation of the location of the UE is associated with location based on cell ID.

26. The method according to claim 16, further comprising: The fixed set based on cache is stored in the non-volatile file system of the UE.

27. The method of claim 16, wherein calculating the location of the UE based on downloaded data or a selected fixed location comprises: The downloaded data or the selected fix is ​​provided to the positioning engine associated with the calculation of the positioning of the UE.

28. The method of claim 16, wherein the first network entity and the second network entity are associated with different mobile operators.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Components used to establish connections with a first network entity and a second network entity based on Dual Subscriber Identity Module (SIM) Dual Activity (DSDA); A component for selecting (1) the first network entity or the second network entity for downloading data associated with calculating the location of the UE based on at least one criterion, or selecting (2) a fixed component for calculating the location of the UE based on a cache-based fixed set of available components associated with the first network entity and the second network entity; and A component for calculating the location of the UE based on downloaded data or a selected fixed location.

30. A computer-readable medium storing computer-executable code at a user equipment (UE), the code causing the processor, when executed by a processor, to: The connection with the first network entity and the second network entity is established based on the Dual Subscriber Identity Module (SIM) Dual Activity (DSDA). Choose (1) the first network entity or the second network entity to download data associated with calculating the location of the UE based on at least one criterion, or choose (2) fixation to calculate the location of the UE based on a cache-based fixed set of available data associated with the first network entity and the second network entity; as well as The UE's location is calculated based on the downloaded data or the selected fixed location.

Images