Map data using transformations with limited third party knowledge

Abstract

Aspects presented herein may improve performance of a positioning device by enabling the positioning device to utilize transformed map data with limited knowledge of the transformation by a third party. Aspects presented herein may enable a localization device to make the localization device available map data from another coordinate system for localization algorithms without transformation knowledge. In one aspect, a UE sends a request for map data based on a first set of coordinates in a first coordinate system. The UE receives map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system. The UE calculates a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. non-provisional patent application No. 17 / 814,116, filed on July 21, 2022, entitled “USAGE OF TRANSFORMED MAPDATA WITH LIMITED THIRD PARTY KNOWLEDGE,” and the entire contents of that application are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to positioning systems and, more particularly, to positioning systems that include navigation. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may be 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 telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., together 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 may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5GNR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an extensive overview of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate 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 a more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus sends a request for map data based on a first set of coordinates in a first coordinate system. The apparatus receives map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system. The apparatus calculates a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data.

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

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

[0010] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0011] Figure 2B is a schematic diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0012] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0013] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0014] Figure 3 is a schematic diagram showing an example of a base station and a user equipment (UE) in an access network.

[0015] Figure 4 is a schematic diagram showing an example of UE positioning based on reference signal measurement.

[0016] Figure 5is a schematic diagram illustrating an example of map data on a corresponding coordinate system according to various aspects of the present disclosure.

[0017] Figure 6 is a schematic diagram illustrating an example of map data that is not on a corresponding coordinate system according to various aspects of the present disclosure.

[0018] Figure 7 is a schematic diagram illustrating an example of using map data from a map provider to improve the performance of a positioning / navigation application according to various aspects of the present disclosure.

[0019] Figure 8 is a communication flow illustrating an example of a UE using map data of a transformed coordinate system to assist its positioning without knowledge of the actual transformation or with limited knowledge of the actual transformation in accordance with various aspects of the present disclosure.

[0020] Fig. 9 1 is a schematic diagram showing an example of calculating a set of relative distances according to map data and performing map-assisted positioning using the calculated set of relative distances according to various aspects of the present disclosure.

[0021] Fig.10 A flow chart of a wireless communication method.

[0022] Fig.11 A flow chart of a wireless communication method.

[0023] Fig.12 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity. Specific implementation method

[0025] Various aspects presented herein can improve the performance of positioning devices such as mobile devices, wearable devices, IoT devices, etc. by enabling the positioning device to utilize transformed map data with limited third-party knowledge of the transformation. Various aspects presented herein can enable the positioning device to make map data of another coordinate system not supported by the positioning device available to the positioning algorithm without knowledge of the transformation (e.g., without knowing that there is a transformation of the coordinates).

[0026] The detailed description set forth below in conjunction with the accompanying drawings describes various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. In order to provide a comprehensive understanding of the various concepts, the detailed description includes specific details. However, these concepts may be practiced without these specific details. In some cases, in order to avoid obscuring these concepts, known structures and components are shown in block diagram form.

[0027] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] For example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes 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 operations (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions or any combination thereof.

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

[0030] Although various aspects, implementations and / or use cases are described in this application by describing some examples, additional or different aspects, implementations and / or use cases can be implemented in many different arrangements and scenarios. The various aspects, implementations and / or use cases described herein can be implemented across multiple different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, implementations and / or use cases can be implemented by integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, devices supporting artificial intelligence (AI), etc.) or combinations thereof. Although some examples may be specifically targeted at use cases or applications, they may not be specifically targeted at use cases or applications, but various applicability of the described examples may occur. The scope of various aspects, implementations and / or use cases can be from chip-level or modular components to non-modular, non-chip-level implementations, and can also be aggregated, distributed or original equipment manufacturer (OEM) devices or systems containing one or more technologies herein. In some actual settings, the equipment containing the described aspects and features may also necessarily include other components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of different sizes, shapes, and configurations.

[0031] The deployment of a communication system such as a 5G NR system may be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network device (e.g., a base station (BS) or one or more units (or one or more components) performing base station functions) may be implemented in an aggregated or decomposed architecture. For example, a BS (e.g., a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also referred to as a stand-alone BS or a monolithic BS) or a decomposed base station.

[0032] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units (e.g., one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit.

[0033] Base station operations or network design may take into account the aggregated nature of base station functionality. For example, a decomposed network may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (e.g., a network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality between two or more units at different physical locations, as well as distributing functionality for at least one unit virtually, which may enable flexibility in network design. Individual units of a decomposed base station or decomposed RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0034] Figure 1 1 is a schematic diagram 100 showing an example of a wireless communication system and access network. The wireless communication system shown includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more decomposed base station units (e.g., 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). The CU 110 may communicate with one or more DUs 130 via corresponding mid-haul links such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 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 unit (i.e., CU 110, DU 130, RU 140, near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces, and the one or more interfaces are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more other units via a transmission medium. For example, these units may include a wired interface, which is configured to receive signals from or send signals to one or more other units via a wired transmission medium. In addition, these units may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver), which is configured to receive signals from or send signals to, or both, one or more other units via a wireless transmission medium.

[0036] In some aspects, CU 110 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to transmit signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RA configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. CU 110 may be implemented to communicate with DU130 as needed for network control and signaling.

[0037] The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of the following, at least in part according to a functional split, such as those defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.). In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with control functions hosted by the CU 110.

[0038] Lower layer functions may be implemented by one or more RUs 140. In some deployments, based at least in part on a functional split such as a split of lower layer functions, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (e.g., a vRAN architecture).

[0039] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and RAN coverage requirements may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-Cloud) 190) to perform network element lifecycle management (e.g., instantiating virtualized network elements) via a cloud computing platform interface (e.g., an 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, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (e.g., an open eNB (O-eNB) 111) via an O1 interface. In addition, in some implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via an O1 interface. The SMO framework 105 may also include a non-RT RIC 115 that is configured to support the functionality of the SMO framework 105 .

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

[0041] In some implementations, in order to generate the AI / ML model 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. Such information may be used by the near-RT RIC 125 and may be received from a non-network data source or from a network function 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 through the SMO framework 105 (e.g., via reconfiguration of O1) or via the creation of a RAN management policy (e.g., an A1 policy).

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

[0043] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[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 identified with the frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations above 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR2-2 (52.6 GHz–71 GHz), FR4 (71 GHz–114.25 GHz), and FR5 (114.25 MHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0047] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used in this document, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used in this document, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR2-2 and / or FR5, or can be within the EHF band.

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

[0049] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network device, or some other appropriate term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station having a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations including decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0050] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and 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 the generation of authentication and key agreement (AKA) credentials, user identification processing, access authorization, and subscription management. One or more location servers 168 are shown as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. The GMLC 165 and LMF 166 support UE positioning services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculation based on the measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signal may be based on one or more of: a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), an LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS), sensor-based information (e.g., a pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (Multi-RTT), DL angle of departure (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, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, user stations, mobile units, user units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals, mobile terminals, wireless terminals, remote terminals, handheld devices, user agents, mobile clients, clients, or some other appropriate terminology. In some scenarios, the term UE may also be applied to one or more companion devices (e.g., in a device constellation arrangement). One or more of these devices may access the network collectively and / or individually.

[0052] Reference again Figure 1 In some aspects, UE 104 can be configured to: send a request for map data based on a first set of coordinates in a first coordinate system; receive map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system; and calculate a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data.

[0053] Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B 230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D is a diagram 280 showing an example of UL channels within a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to either DL or UL), or can be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to both DL and UL). Figure 2A , 2CIn the example provided, 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 flexibly 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 full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured to have a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the above description also applies to the 5G NR frame structure as TDD.

[0054] Figures 2A-2D The frame structure is shown, and various aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a microslot, 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 a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) and, effectively, the symbol length / duration, which is equal to 1 / SCS.

[0055]

[0056] For normal CP (14 symbols / slot), different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, different digital schemes 2 allow 4 slots per subframe. Therefore, for normal CP and digital scheme μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ*15kHz, where μ is digital scheme 0 to 4. As such, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for a normal CP with 14 symbols per slot and a digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific numbering scheme and CP (normal or extended).

[0057] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)), which extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0059] Figure 2BExamples of various DL channels in a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, wherein 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 within symbol 2 of a specific subframe of a frame. The UE 104 uses the PSS 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 a frame. The UE uses the SSS to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically combined 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 that is not sent through the PBCH (e.g., system information block (SIB)), and paging messages.

[0060] like Figure 2C As shown in , some of the REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can send 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 sent in the first one or two symbols of the PUSCH. In different configurations, the PUCCH DM-RS can be sent depending on whether a short PUCCH or a long PUCCH is sent and according to the specific PUCCH format used. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS in one of the combs in the comb. The SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0061] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0062] Figure 3 375. The Controller / Processor 375 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting of 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 functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and switching support functions; RLC layer functions associated with: transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions 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 through HARQ, priority handling, and logical channel prioritization.

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

[0064] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, the RX processor 356 can merge them into a single OFDM symbol stream. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functions.

[0065] The controller / processor 359 may be associated with a memory 360 that stores program codes 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 channels 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 operations.

[0066] Similar to the functions described for DL ​​transmission performed in conjunction with the base station 310, the controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions 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 through HARQ, priority handling, and logical channel prioritization.

[0067] The TX processor 368 may select the appropriate coding and modulation scheme and facilitate spatial processing using channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310. The spatial streams generated by the TX processor 368 may be provided via separate transmitters 354Tx to different antennas 352. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0068] At the base station 310, the UL transmission is processed in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

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

[0070] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform Figure 1 Various aspects related to the map data reference component 198.

[0071] Figure 4 4 is a diagram illustrating 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 the present disclosure. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX Receive a DL positioning reference signal (PRS) (DL-PRS) 410. TRP 406 may be at time T SRS_RX Receive UL-SRS 412, and at time T PRS_TX 410. UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine the UL-SRS 412 based on ||T SRS_RX –T PRS_TX |–|T SRS_TX –T PRS_RX || determines RTT 414. Thus, multi-RTT positioning can utilize UE Rx-Tx time difference measurements (i.e., |T SRS_TX –T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and TRP Rx-Tx time difference measurements measured at multiple TRPs 402, 406 for uplink signals sent from UE 404 (i.e., |T SRS_RX –T PRS_TX |). UE 404 measures UE Rx-Tx time difference measurements (and / or DL-PRS-RSRP of received signals) using assistance data received from the positioning server, and TRP 402, 406 measures gNB Rx-Tx time difference measurements (and / or UL-SRS-RSRP of received signals) using assistance data received from the positioning server. These measurements may be used at the positioning server or UE 404 to determine RTT, which is used to estimate the position of UE 404. Other methods may also be used (e.g., using DL-TDOA and / or UL-TDOA measurements) to determine RTT.

[0072] DL AoD positioning can utilize DL-PRS-RSRP measured at the UE 404 for downlink signals received from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and uses the obtained measurements together with the departure azimuth angle (A-AoD), the departure zenith angle (Z-AoD) and other configuration information to position the UE 404 relative to the neighboring TRPs 402, 406.

[0073] DL-TDOA positioning can utilize DL reference signal time difference (RSTD) (and / or DL-PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 at UE 404. UE 404 uses assistance data received from a positioning server to measure the DL RSTD (and / or DL-PRS-RSRP) of the received signals, and uses the obtained measurements together with other configuration information to position UE 404 relative to neighboring TRPs 402, 406.

[0074] UL-TDOA positioning can utilize the UL relative time of arrival (RTOA) (and / or UL-SRS-RSRP) of uplink signals sent from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use assistance data received from a positioning server to measure the UL-RTOA (and / or UL-SRS-RSRP) of the received signals, and use the obtained measurements together with other configuration information to estimate the position of UE 404.

[0075] UL-AoA positioning can utilize the azimuth angle of arrival (A-AoA) and the zenith angle of arrival (Z-AoA) measured at multiple TRPs 402, 406 of uplink signals sent from the UE 404. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from a positioning server, and use the obtained measurements together with other configuration information to estimate the position of the UE 404.

[0076] Additional positioning methods (e.g., UE-side UL-AoD and / or DL-AoA) may be used to estimate the position of UE 404. It should be noted that data / measurements from various techniques may be combined in various ways to improve accuracy, determine and / or enhance certainty, supplement / augment measurements, and / or replace / provide missing information.

[0077] A device equipped with a Global Navigation Satellite System (GNSS) receiver can determine its position on the Earth based on GNSS measurements (which is also referred to as "GNSS-based positioning"). GNSS is a network of satellites that broadcast timing and orbit information used for navigation and positioning measurements. GNSS may include groups of satellites, called constellations, that broadcast signals (which may be referred to as GNSS signals) to control stations and users of the GNSS. Based on the broadcast signals, users are able to determine their position (e.g., via trilateration). For ease of description of the present disclosure, a device equipped with a GNSS receiver or capable of receiving GNSS signals (e.g., a UE) may be referred to as a GNSS device, and a device capable of sending GNSS signals (e.g., a satellite) may be referred to as a space vehicle (SV).

[0078] For example, a GNSS device can determine its geographic coordinates of latitude, longitude and altitude in a coordinate system based on GNSS signals received from a satellite. A coordinate system (also referred to as a spatial reference system (SRS) or a coordinate reference system (CRS)) is a framework / system that a GNSS device uses to accurately measure a position on the surface of the earth as a coordinate. A reference system can include a selection of an earth ellipsoid, a horizontal datum, a map projection, an origin and / or a measurement unit, etc. Thousands of coordinate systems have been specified around the world or in a specific region. For example, a GPS receiver uses the World Geodetic System (WGS) (the latest version is also referred to as WGS1984 or WGS-84) as its coordinate system, which is composed of a reference ellipsoid, a standard coordinate system, altitude data and a geoid. WGS uses the mass of the center of the earth as the coordinate origin, which has an uncertainty of less than 2 cm.

[0079] Different coordinate systems can provide different coordinates for the same location, or different locations for the same coordinates. For example, GCJ-02 or BD-09 is another coordinate system based on the WGS-84 coordinate system. The GCJ-02 / BD-09 coordinate system uses a fuzzy algorithm that adds a random offset to both latitude and longitude (e.g., for the purpose of improving national security). Therefore, there may be a distance offset (or drift) between a coordinate on the WGS-84 coordinate system and the same coordinate on the GCJ-02 / BD-09 coordinate system. For example, a GCJ-02 / BD-09 coordinate (e.g., a coordinate obtained based on the GCJ-02 / BD-09 coordinate system) can be displayed at the correct location on a GCJ-02 / BD-09 map. However, if the WGS-84 coordinate is placed on a GCJ-02 / BD-09 map, the distance offset may result in an error of 100 to 700 meters from the actual location, and vice versa. Therefore, if the corresponding coordinate system and / or map data is not used, the GNSS device may not be able to accurately determine its location.

[0080] Figure 5 500 is a schematic diagram showing an example of map data on a corresponding coordinate system according to various aspects of the present disclosure. For the sake of convenience of illustrating the present disclosure, map data may include information of any geographical reference object on a map (e.g., roads, walkways, ferry routes, etc.), which may be provided in a variety of formats (e.g., line segments, pixels, etc.). This may include the relative distances of these objects on a map that can be obtained with reference to a set of coordinates. In one example, map data for a region may be obtained as a set of line segments representing different geographical features of the region, such as roads, walkways, ferry routes, etc. These line segments may also be provided as road coordinates. When a coordinate system is used in association with corresponding (or correct) map data (e.g., using GCJ-02 coordinates on a GCJ-02 map), the line segment groups in the map data may be correctly matched / aligned with actual geographical features in the region. For example, a line segment 502 representing an X road may be correctly aligned with an actual X road in the region, and a line segment representing a Y road may be correctly aligned with an actual Y road in the region, and so on.

[0081] Figure 6 600 is a schematic diagram illustrating an example of map data that is not on a corresponding coordinate system according to various aspects of the present disclosure. On the other hand, when a coordinate system is not used in association with corresponding (or correct) map data (e.g., using WGS-84 coordinates on a GCJ-02 map), the line segment groups in the map data may not correctly match the actual geographic features of the area. For example, the line segment 502 representing the X road may be offset from the actual X road in the area by a certain distance (e.g., X meters in longitude, Y meters in latitude, etc.).

[0082] In order to obtain a correct position or correct map data using the coordinates obtained from the first coordinate system in the second coordinate system, the GNSS device (or the map data client / provider) may be configured / designed to have the ability to convert the coordinates obtained via the first coordinate system into corresponding coordinates in the second coordinate system, which may be referred to as "transformation". For example, the GNSS device may convert the WGS-84 coordinates into GCJ-02 coordinates and use the converted coordinates on the GCJ-02 map data, so that the GNSS device can correctly identify its geographic location based on the GCJ-02 map data, such as Figure 5 However, in some areas, converting coordinates from one coordinate system to another may specify a specific algorithm and may be illegal without a valid license. For example, in some areas, converting WGS-84 coordinates to GCJ-02 coordinates may require a valid license, and converting GCJ-02 coordinates to WGS-84 coordinates may be strictly prohibited and illegal.

[0083] In some scenarios, map data for certain areas may be available only in one coordinate system but not in another. For example, there may be map data for a certain area that is available in the GCJ-02 coordinate system but not in the WGS-84 coordinate system. As such, in order to use the map data for that area, the GNSS device may be specified to use the GCJ-02 coordinate system (e.g., if the GNSS device supports the GCJ-02 coordinate system), or the coordinates of another coordinate system may be converted to GCJ-02 coordinates before using the map data (e.g., if the GNSS does not support the GCJ-02 coordinate system). However, in some areas, the algorithms used to transform coordinates between different coordinate systems, or the existence of the transformation in the mapping application, may not be disclosed to the public (e.g., it may be illegal to do so). As such, map data for certain geographic locations may only be available in a transformed coordinate system with an unknown transformation (e.g., a geographic location specified to use the GCJ-02 coordinate system). In addition, if the transformation is unknown, the manufacturer may not be able to directly integrate the converted map data into the positioning software / application on the mobile device (e.g., UE, wearable device, IoT device, etc.).

[0084] A positioning / navigation application (or software) may refer to an application (e.g., a navigation system, a smartphone, etc.) in a user equipment (UE) that provides positioning or navigation directions to a user in real time. The positioning / navigation application may include various positioning / navigation functions that can be used to improve the positioning / navigation provided by the application. For example, the navigation function may include: guiding the user to the destination based on the fastest or shortest route, fitting the user to the nearest road when the user's exact location cannot be determined (e.g., based on a "quickly reach the road" function), and / or avoiding navigating the user through certain areas (e.g., toll roads, congested roads, roads under construction, etc.). In the past few years, because positioning / navigation applications provide various benefits, users have become increasingly dependent on positioning / navigation applications. For the sake of convenience in explaining the present disclosure, a navigation map may refer to a map corresponding to a specific area of ​​the real world, so that when the user is in the specific area, the positioning / navigation application can use the navigation map to navigate (e.g., guide) the user via a display. The navigation map may include multiple layers, each of which may convey different types of information. For example, a first layer of a navigation map may convey geographic (eg, terrain) information, a second layer of the navigation map may convey road information, and a third layer of the navigation map may convey building information, and so on.

[0085] In some examples, a positioning / navigation application may use map data from a map provider (eg, a third-party map provider) to improve positioning and / or navigation performance. Figure 7700 is a schematic diagram illustrating an example of using map data from a map provider to improve the performance of a positioning / navigation application according to various aspects of the present disclosure. A user with a GNSS device 702 (e.g., a UE with a positioning / navigation application) can move from point A to point B. As shown in 704, when the GNSS device 702 is configured to track the user's position without the help of map data, the tracked path may appear more nonlinear and random due to errors and drifts in positioning measurements. For example, if the GNSS device 702 is capable of performing GNSS-based positioning, when the user is in an urban area and the GNSS device 704 cannot receive GNSS signals from satellites based on line of sight (LOS) conditions, the detected user position may be several meters away from the user's actual position. In another example, if the GNSS device is capable of performing dead reckoning (DR) positioning, the detected user position may also be different from the user's actual position when there is a magnetic field disturbance. As such, the tracked path may overlap with areas that the user is unlikely to visit (e.g., buildings or adjacent roads), which may result in inaccurate user positioning.

[0086] On the other hand, as shown in 706, when the GNSS device 702 is configured to track the user's position with the help of map data, the tracked path may appear more linear because the user's path can be configured to fit the path available in the map data (e.g., fit the nearest line segment provided by the map data). For example, some positioning / navigation applications may include a function called "fast adapt to road" or "adapt to road" function, which enables the positioning / navigation program to adapt the user's position to a nearby (or nearest) road / location on the navigation map when the GNSS signal is weak or sporadic. This function can be similar to a map matching function, where the map matching function ensures that the GNSS data is associated with the road that the user is traveling on and does not jitter the user's trajectory and cause confusion. Therefore, the tracked user path may be less likely to overlap with areas that the user has not visited. Therefore, map data from a map provider can be used to improve the positioning accuracy of mobile / wearable / IoT devices (this can be called map-assisted positioning). In addition, in some scenarios, the map data used for positioning may not specify knowledge of absolute map coordinates, but only relative information (e.g., coordinate offsets relative to a reference position). Additionally, map-assisted positioning may not specify that the user's location be shared outside the device to ensure user privacy, which is consistent with privacy standards mandated by some countries.

[0087] As combined Figure 5 and Figure 6As described, for various reasons, map data with location coordinates (e.g., two-dimensional (2D) and / or three-dimensional (3D) map data) may only be available after undergoing a transformation, and the transformation itself is unknown (e.g., converting WGS-84 coordinates to GCJ-02 coordinates, and using / disclosing the transformation without permission is illegal). Therefore, in some scenarios, because the transformation is unknown, manufacturers may not be able to directly integrate transformed map data (e.g., map data based on coordinates converted from one coordinate system to another coordinate system) into positioning / navigation applications on mobile devices, wearable devices, IoT devices, etc.

[0088] The various aspects presented herein can improve the performance of positioning devices such as mobile devices, wearable devices, IoT devices, etc. by enabling the positioning device to utilize transformed map data with limited third-party knowledge of the transformation. The various aspects proposed herein can enable the positioning device to use map data of another coordinate system that is not supported by the positioning device for positioning algorithms without knowledge of the transformation (e.g., without knowing that there is a transformation of coordinates). The various aspects presented herein can enable map data to be integrated with GNSS and sensor navigation filters, which directly integrate GNSS sensors and map data into a Kalman filter to estimate user position and velocity. Map data can be used to impose specific constraints on user position to improve position accuracy.

[0089] In one aspect of the present disclosure, a positioning device can use knowledge of referencing map data to a reference position in a transformed coordinate system. If a position in a known coordinate system corresponding to the same position in the transformed coordinate system is available, it is assumed that the map data referenced to the reference position in the transformed coordinate system can be converted to the reference position in the known coordinate system, and then the map data can be made available to the positioning application without knowing the actual transformation itself. For example, the positioning device can request map data for an area from an entity (e.g., a third-party supplier) that has access to the transformation. Map data corresponding to a position in a known coordinate system can be requested. An entity with access to the transformation can convert the reference position to an unknown coordinate system (e.g., unknown to the positioning device or the requester of the map data). The entity can then obtain map data corresponding to the transformed reference position and provide the map data with the transformed reference position to a GNSS device or a map data requester. The availability of reference positions in known and unknown coordinate systems and corresponding map data in the unknown coordinate system can allow map data to become available in a positioning algorithm (e.g., for map-assisted positioning).

[0090] Figure 8800 is a communication flow illustrating an example of a UE using map data of a transformed coordinate system to assist its positioning without knowledge of the actual transformation or with limited knowledge of the actual transformation according to various aspects of the present disclosure. The numbers associated with the communication flow 800 do not specify a particular time sequence, but are merely used as a reference for the communication flow 800. Various aspects presented herein can enable a UE (e.g., a mobile device, a wearable device, an IoT device, etc.) to make map data from a transformed coordinate system (e.g., from a different coordinate system) available to a positioning algorithm (e.g., to assist its positioning) without knowledge of the transformation.

[0091] At 820, UE 802 (e.g., a first entity) may request map data 806 for an area from a map data client 804 (e.g., a second entity) using a first set of coordinates 808 (e.g., P(A)) in a first coordinate system 810, where the first coordinate system 810 may be a known coordinate system for UE 802 or a coordinate system supported by UE 802. For example, UE 802 may be a GPS / GNSS receiver capable of determining its coordinates based on a WGS-84 coordinate system (e.g., the first coordinate system 810), but UE 802 may not support / be aware of a second coordinate system 814 (e.g., a GCJ-02 coordinate system and / or a BD-09 coordinate system). The UE 802 may request map data 806 associated with a second coordinate system 814 from a map data client 804 based on a first set of coordinates 808 (e.g., WGS-84 coordinates), where the map data client 804 may be an entity with authorization / permission to transform coordinates from the first coordinate system 810 to the second coordinate system 814 (e.g., with permission to transform WGS-84 coordinates to GCJ-02 / BD-09 coordinates).

[0092] At 822, in response to the UE 802's request for the map data 806, the map data client 804 may convert the first set of coordinates 808 (e.g., WGS-84 coordinates) into a second set of coordinates 812 (e.g., GCJ-02 / BD-09 coordinates) in a second coordinate system 814 (e.g., GCJ-02 / BD-09 coordinate system).

[0093] At 824, the map data client 804 may request map data 806 from a map data server 818 (e.g., a third entity) associated with a second coordinate system 814 (e.g., a GCJ-02 / BD-09 map server / provider) based on the second set of coordinates 812 (e.g., GCJ-02 / BD-09 coordinates).

[0094] At 826, in response to the request of the map data client 804, the map data server 818 may send the map data 806 in the second coordinate system 814 to the map data client 806 for forwarding to the UE 802, or directly to the UE 802 according to the configuration. For example, the map data server 818 may send GCJ-02 / BD-09 map data to the map data client 804, and the map data client 806 may forward the GCJ-02 / BD-09 map data to the UE 802.

[0095] As combined Figure 5 and Figure 6 As discussed, the map data 806 may include a set of line segments representing one or more objects / features in the area (e.g., roads, paths, walkways, building locations, and / or vehicle routes (e.g., car, boat, and / or airplane routes) in the area). Figure 6 As shown, since the UE 802 does not support the second coordinate system 814 (e.g., the GCJ-02 / BD-09 coordinate system), the map data 806 received by the UE 802 may include an offset from the actual area. For example, the street X in the map data 806 of the area may be offset by 100 meters in the longitude direction and 200 meters in the latitude direction from the actual street X of the area.

[0096] At 828, based on the map data 806 and the second set of coordinates 812, the UE 802 may calculate a set of relative distances 816 between the second set of coordinates 812 and one or more objects / features (e.g., roads, paths, and / or routes associated with the area) corresponding to the map data 806. Then, at 830, the UE 802 may assist in positioning or navigation of the UE 802 (e.g., in the first coordinate system 810) based on the set of relative distances 816.

[0097] Fig. 9 900 is a diagram illustrating an example of calculating a set of relative distances according to map data and using the calculated set of relative distances for map-assisted positioning according to various aspects of the present disclosure. As shown in 902, after receiving map data 806, UE 802 may have a map (e.g., a set of line segments) that includes one or more features (e.g., roads, walking paths, ferry routes, etc.) of the area relative to a second set of coordinates 812. Then, UE 802 may calculate or obtain the relative distances between the one or more features of the area and the second set of coordinates 812.

[0098] For example, as shown at 904, the map data 806 may include road X, road Y, and street Z. Then, the UE 802 may calculate relative distances (e.g., a set of relative distances 816) between the second set of coordinates 812 and road X, road Y, and street Z. For example, the UE 802 may calculate and determine that road X is D0 meters away from the second set of coordinates 812 in the latitudinal direction, and road X extends from D2 meters to D3 meters in the longitudinal direction relative to the second set of coordinates 812. The UE 802 may also calculate and determine that road Y is D1 meters away from the second set of coordinates 812 in the latitudinal direction, and road Y extends from D3 meters to D4 meters in the longitudinal direction relative to the second set of coordinates 812. Similarly, the UE 802 may also calculate and determine that street Z is D3 meters away from the second set of coordinates 812 in the longitudinal direction, and road Y extends from D3 meters to D4 meters in the transverse direction relative to the second set of coordinates 812, and so on.

[0099] As shown at 908, when the transformation between the first set of coordinates 808 and the second set of coordinates 812 is locally linear (e.g., the first set of coordinates 808 = the second set of coordinates 812 + the offset), the relative distances (e.g., D0, D1, D2, D3, D4, ..., DN) between the second set of coordinates 812 calculated at 906 and the road X, road Y, and street Z may be the same as the relative distances between the first set of coordinates 808 and the road X, road Y, and street Z, as shown at 910. For example, even though the offset of a coordinate on the first coordinate system 810 (e.g., one of the coordinates in the first set of coordinates 808) and the corresponding coordinate on the second coordinate system 814 (e.g., one of the coordinates in the second set of coordinates 812) may be X meters / degrees (e.g., resulting from a blur algorithm), the relative distance between the coordinate and the road X may be the same as the relative distance between the corresponding coordinate and the road X. As such, the UE 802 may use the calculated relative distance to assist the UE 802 in positioning and / or navigation in the first coordinate system 810 without generating or obtaining a map in the first coordinate system 810 .

[0100] For example, if UE 802 is at a location corresponding to first set of coordinates 808, UE 802 may guide the user from first set of coordinates 806 to point A on the map by navigating the user to move D0 meters in the latitude direction and D2 meters in the longitude direction. In another example, as shown in 912, if UE 802 guides the user from point A to point B in first coordinate system 810, based on the relative distance obtained from map data 806 of second coordinate system 814, UE 802 may inform the user to move M meters north (e.g., D3 minus D2 meters) from point A, turn east (or turn right) and move N meters (e.g., D1 minus D0 meters), then turn north (or turn left) and move P meters (e.g., D4 minus D3 meters), etc. In another example, as shown in combination with Figure 7 As described, the UE 802 may also use the map data 806 to assist in its positioning or location tracking, such as by fitting the user's location (e.g., by snapping to a suitable feature) to a nearby (or nearest) road / location of the map data 806. For example, when the user moves from point A to point B, the UE 802 may track / record the user's path based on road X, street Z, and road Y.

[0101] Therefore, the various aspects presented herein can enable UE 802 to use map data associated with the second coordinate system 814 to assist its positioning on the first coordinate system 810 without knowing the coordinate transformation between the first coordinate system 810 and the second coordinate system 814, which can improve the positioning accuracy of UE 802 in the first coordinate system 810 while enabling UE 802 to comply with regulations of certain geographic locations (e.g., prohibiting the conversion of coordinates without authorization / permission). In other words, the knowledge of the transformation from the first coordinate system 810 to the second coordinate system 814 may only be known to and permitted by the third-party application / supplier. However, UE 802, map data client 804, and third-party application / supplier may not allow / permit the use of the transformation from the second coordinate system 814 to the first coordinate system 810.

[0102] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 404, 802; GNSS device 702; apparatus 1204). The method may enable a UE (which may be a mobile device, a wearable device, an IoT device, or a device running a positioning application, etc.) to use map data from another coordinate system (e.g., a coordinate system not supported by the UE) for a positioning algorithm without having knowledge of the transformation (e.g., not knowing the transformation of coordinates between coordinate systems).

[0103] At 1002, the UE may send a request for map data based on a first set of coordinates in a first coordinate system, for example in conjunction with Figure 8 For example, at 820, UE 802 may request map data 806 for a certain area from map data client 804 using a first set of coordinates 808 in a first coordinate system 810 (eg, a known coordinate system). Fig.12 The map data reference component 198, cellular baseband processor 1224 and / or transceiver 1222 of the device 1204 in the embodiment may perform the transmission of the request.

[0104] At 1004, the UE may receive map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system, such as in combination with Figure 8 For example, at 826, UE 802 may receive map data 806 in the second coordinate system 814 from map data client 804 or from map data server 818. Fig.12 The map data is received by the map data reference component 198, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204.

[0105] In one example, the first set of coordinates differs from the second set of coordinates by an offset. This may be applicable at least near the first set of coordinates, but may not be applicable over long distances. In such an example, the offset is based on a linear transformation between the first set of coordinates in the first coordinate system and the second set of coordinates in the second coordinate system.

[0106] In another example, the first coordinate system is a World Geodetic System 1984 (WGS-84) coordinate system, and the second coordinate system is at least one of a geodetic datum, a GCJ-02 coordinate system, or a BD-09 coordinate system.

[0107] In another example, a request for map data is sent to at least one of a map data client or a map data server, and wherein the map data is received from at least one of the map data client or the map data server. In such an example, a first set of coordinates in a first coordinate system is transformed to a second set of coordinates in a second coordinate system via the map data client or a third party application (e.g., a third party provider that provides transformation information to the map data client). In some examples, the map data client may access the transformation with permission of the third party application / provider.

[0108] In another example, the UE does not have the capability or permission to operate in the second coordinate system.

[0109] In another example, the map data includes a set of line segments representing one or more objects corresponding to the map data. In such an example, the one or more objects include one or more roads, one or more building locations, one or more paths, one or more pedestrian roads, one or more vehicle routes, or a combination thereof, wherein the one or more vehicle routes are associated with at least one of a car, a ship, or an airplane.

[0110] At 1006, the UE may calculate a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data, for example, in combination with Figure 8 and Fig. 9 For example, at 828, UE 802 may calculate a set of relative distances 816 between the second set of coordinates 812 and one or more objects corresponding to map data 806. Fig.12 The map data reference component 198 and / or the cellular baseband processor 1224 of the device 1204 performs the calculation of the set of relative distances.

[0111] In one example, the set of relative distances between the second set of coordinates and the one or more objects includes a longitudinal coordinate offset and a lateral coordinate offset of the one or more objects relative to the second set of coordinates.

[0112] At 1008, the UE may assist the UE in positioning or navigating in the first coordinate system based on the set of relative distances, for example, in combination with Figure 8 and Fig. 9 For example, at 830, UE 802 may assist in positioning or navigating UE 802 (eg, in first coordinate system 810) based on the set of relative distances 816. Fig.12 The map data reference component 198, cellular baseband processor 1224 and / or transceiver 1222 of the device 1204 in the device are used to perform the positioning or navigation assistance.

[0113] At 1010, the UE may associate (or apply) the set of relative distances with a first set of coordinates in a first coordinate system, for example, in combination with Figure 8 and Fig. 9 For example, as shown at 910, UE 802 may associate a set of relative distances obtained from second set of coordinates 812 and map data 806 with first set of coordinates 808 in first coordinate system 810. Fig.12 The map data reference component 198, cellular baseband processor 1224 and / or transceiver 1222 of the device 1204 in the embodiment may be used to perform the application of the set of relative distances.

[0114] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 404, 802; GNSS device 702; apparatus 1204). The method may enable a UE (which may be a mobile device, a wearable device, an IoT device, or a device running a positioning application, etc.) to use map data from another coordinate system (e.g., a coordinate system not supported by the UE) for a positioning algorithm without having knowledge of the transformation (e.g., not knowing the transformation of coordinates between coordinate systems).

[0115] At 1102, the UE may send a request for map data based on a first set of coordinates in a first coordinate system, for example in conjunction with Figure 8 For example, at 820, UE 802 may request map data 806 for a certain area from map data client 804 using a first set of coordinates 808 in a first coordinate system 810 (eg, a known coordinate system). Fig.12 The map data reference component 198, cellular baseband processor 1224 and / or transceiver 1222 of the device 1204 in the embodiment may perform the transmission of the request.

[0116] At 1104, the UE may receive map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system, such as in combination with Figure 8 For example, at 826, UE 802 may receive map data 806 in the second coordinate system 814 from map data client 804 or from map data server 818. Fig.12 The map data is received by the map data reference component 198, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204.

[0117] In one example, the first set of coordinates differs from the second set of coordinates by an offset. In such an example, the offset is based on a linear transformation between the first set of coordinates in the first coordinate system and the second set of coordinates in the second coordinate system.

[0118] In another example, the first coordinate system is a World Geodetic System 1984 (WGS-84) coordinate system, and the second coordinate system is at least one of a geodetic datum, a GCJ-02 coordinate system, or a BD-09 coordinate system.

[0119] In another example, a request for map data is sent to at least one of a map data client or a map data server, and the map data is received from at least one of the map data client or the map data server. In such an example, a first set of coordinates in a first coordinate system is converted to a second set of coordinates in a second coordinate system via the map data client or a third party application.

[0120] In another example, the UE does not have the capability or permission to operate in the second coordinate system.

[0121] In another example, the map data includes a set of line segments representing one or more objects corresponding to the map data. In such an example, the one or more objects include one or more roads, one or more building locations, one or more paths, one or more pedestrian roads, one or more vehicle routes, or a combination thereof, wherein the one or more vehicle routes are associated with at least one of a car, a ship, or an airplane.

[0122] At 1106, the UE may calculate a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data, for example, in combination with Figure 8 and Fig. 9For example, at 828, UE 802 may calculate a set of relative distances 816 between the second set of coordinates 812 and one or more objects corresponding to map data 806. Fig.12 The map data reference component 198 and / or the cellular baseband processor 1224 of the device 1204 performs the calculation of the set of relative distances.

[0123] In one example, the set of relative distances between the second set of coordinates and the one or more objects includes a longitudinal coordinate offset and a lateral coordinate offset of the one or more objects relative to the second set of coordinates.

[0124] In another example, the UE may assist the positioning or navigation of the UE in the first coordinate system based on the set of relative distances, for example, in combination with Figure 8 and Fig. 9 For example, at 830, UE 802 may assist in positioning or navigating UE 802 (eg, in first coordinate system 810) based on the set of relative distances 816. Fig.12 The map data reference component 198, cellular baseband processor 1224 and / or transceiver 1222 of the device 1204 in the device are used to perform the positioning or navigation assistance.

[0125] In another example, the UE may associate the set of relative distances with a first set of coordinates in a first coordinate system, for example, by combining Figure 8 and Fig. 9 For example, as shown at 910, UE 802 may associate or apply a set of relative distances obtained from second set of coordinates 812 and map data 806 to first set of coordinates 808 in first coordinate system 810. Fig.12 The map data reference component 198, cellular baseband processor 1224 and / or transceiver 1222 of the device 1204 in the embodiment may be used to perform the application of the set of relative distances.

[0126] Fig.121200 is a schematic diagram illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include a cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., a cellular RF transceiver). The cellular baseband processor 1224 may include on-chip memory 1224'. In some aspects, the apparatus 1204 may also include one or more subscriber identity module (SIM) cards 1220 coupled to a secure digital (SD) card 1208 and a screen 1210 and an application processor 1206. The application processor 1206 may include on-chip memory 1206'. In some aspects, the device 1204 may also include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio-aided detection and ranging (RADAR), a sounding navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1226, a power source 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas, and / or communicate using an antenna 1280. The cellular baseband processor 1224 communicates with the UE 104 and / or the RU associated with the network entity 1202 via one or more antennas 1280 through the transceiver 1222. The cellular baseband processor 1224 and the application processor 1206 can each include a computer-readable medium / memory 1224', 1226', respectively. The additional memory module 1226 can also be regarded as a computer-readable medium / memory. Each computer-readable medium / memory 1224', 1206', 1226 can be non-temporary. The cellular baseband processor 1224 and the application processor 1206 are each responsible for general processing, which includes executing software stored on a computer-readable medium / memory. When the software is executed by the cellular baseband processor 1224 / application processor 1206, the cellular baseband processor 1224 / application processor 1206 performs the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1224 / application processor 1206 when executing the software.The cellular baseband processor 1224 / application processor 1206 may be a component of the UE 350 and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360. In one configuration, the device 1204 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1224 and / or the application processor 1206, and in another configuration, the device 1204 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1204.

[0127] As described above, the map data reference component 198 can be configured to send a request for map data based on a first set of coordinates in a first coordinate system. The map data reference component 198 can also be configured to receive map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system. The map data reference component 198 can also be configured to calculate a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data. The map data reference component 198 can be in the cellular baseband processor 1224, the application processor 1206, or in both the cellular baseband processor 1224 and the application processor 1206. The map data reference component 198 can be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1204 can include various components configured to implement various functions. In one configuration, the device 1204 (specifically, the cellular baseband processor 1224 and / or the application processor 1206) may include: a unit for sending a request for map data based on a first set of coordinates in a first coordinate system. The device 1204 may also include: a unit for receiving map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system. The device 1204 may also include: a unit for calculating a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data.

[0128] In one configuration, the apparatus 1204 may further include: means for assisting the UE in positioning or navigation in the first coordinate system based on the set of relative distances.

[0129] In another configuration, the apparatus 1204 may further include: means for associating the set of relative distances with a first set of coordinates in a first coordinate system.

[0130] In another configuration, the first set of coordinates differs from the second set of coordinates by an offset. In such a configuration, the offset is based on a linear transformation between the first set of coordinates in the first coordinate system and the second set of coordinates in the second coordinate system.

[0131] In another configuration, the first coordinate system is a WGS-84 coordinate system, and the second coordinate system is at least one of a geodetic datum, a GCJ-02 coordinate system, or a BD-09 coordinate system.

[0132] In another configuration, a request for map data is sent to at least one of a map data client or a map data server, and wherein the map data is received from at least one of the map data client or the map data server. In such a configuration, a first set of coordinates in a first coordinate system is converted to a second set of coordinates in a second coordinate system via the map data client or a third party application.

[0133] In another configuration, the UE does not have the capability or permission to operate in the second coordinate system.

[0134] In another configuration, the map data includes a set of line segments representing the one or more objects corresponding to the map data. In such a configuration, the one or more objects include one or more roads, one or more building locations, one or more paths, one or more pedestrian roads, one or more vehicle routes, or a combination thereof, wherein the one or more vehicle routes are associated with at least one of a car, a ship, or an airplane.

[0135] In another configuration, a set of relative distances between the second set of coordinates and the one or more objects includes a longitudinal coordinate offset and a lateral coordinate offset of the one or more objects relative to the second set of coordinates.

[0136] These means may be the map data reference component 198 of the device 1204 configured to perform the functions recited by these means. As described above, the device 1204 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, these means may be the TX processor 368, the RX processor 356, and / or the controller / controller 359 configured to perform the functions recited by these means.

[0137] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary manner. Based on design preferences, it should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. Further, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order and are not meant to be limited to the specific order or hierarchy provided.

[0138] To enable any person of ordinary skill in the art to implement the various aspects described herein, the above description is made around various aspects. It is obvious to a person of ordinary skill in the art that various modifications to these aspects are possible, and the general principles defined herein may also be applicable to other aspects. Therefore, the present invention is not limited to the aspects described herein, but is consistent with the full scope of the present invention. Modifying a certain component with a singular form does not mean "one and only one", but may be "one or more". Terms such as "if", "when..." and "when..." do not imply a direct time relationship or reaction. That is, these phrases (e.g., "when...") do not mean to take action immediately in response to an action or to take action during the occurrence of an action, but simply mean that if the conditions are met, an action will occur, but there is no need to have a specific or immediate time constraint on the occurrence of the action. The word "exemplary" used herein means "used as an example, illustration or description". Any aspect described as "exemplary" herein should not be interpreted as being more preferred or more advantageous than 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" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members or some members of A, B, or C. A set should be interpreted as a group of elements, where the elements are numbered one or more. Thus, for a group X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a group of devices. All structural and functional equivalents of the components of the various aspects described throughout the present disclosure are expressly incorporated herein by reference and are intended to be covered by the claims, which are known or will be known to those of ordinary skill in the art. In addition, no disclosure herein is intended to be dedicated to the public, regardless of whether such disclosure is clearly recorded in the claims. Words such as "module", "device", "element", "equipment", etc. are not substitutes for the word "unit".Therefore, a constituent element of a claim should not be construed as a functional module unless the constituent element is explicitly described using the wording of “functional module”.

[0139] As used herein, the phrase "based on" shall not be interpreted as a reference 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" may be information, a condition, a factor, etc.) shall be interpreted as "based at least on A" unless specifically stated otherwise.

[0140] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limited thereto.

[0141] Aspect 1 is a method for wireless communication at a UE, the method comprising: sending a request for map data based on a first set of coordinates in a first coordinate system; receiving the map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system; and calculating a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data.

[0142] Aspect 2 is a method according to aspect 1, further comprising: assisting the UE in positioning or navigating in the first coordinate system based on the set of relative distances.

[0143] Aspect 3 is a method according to any one of aspects 1 or 2, further comprising: associating the set of relative distances with the first set of coordinates in the first coordinate system.

[0144] Aspect 4 is a method according to any one of aspects 1 to 3, wherein the first set of coordinates differs from the second set of coordinates by an offset.

[0145] Aspect 5 is a method according to aspect 4, wherein the offset is based on a linear transformation between the first set of coordinates in the first coordinate system and the second set of coordinates in the second coordinate system.

[0146] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein the first coordinate system is the WGS-84 coordinate system, and the second coordinate system is at least one of a geodetic datum, a GCJ-02 coordinate system, or a BD-09 coordinate system.

[0147] Aspect 7 is a method according to any one of aspects 1 to 6, wherein the request for the map data is sent to at least one of a map data client or a map data server, and wherein the map data is received from at least one of the map data client or the map data server.

[0148] Aspect 8 is a method according to aspect 7, wherein the first set of coordinates in the first coordinate system is converted into the second set of coordinates in the second coordinate system via the map data client or a third-party application.

[0149] Aspect 9 is a method according to any one of aspects 1 to 8, wherein the UE does not have the capability or permission to operate in the second coordinate system.

[0150] Aspect 10 is a method according to any one of aspects 1 to 9, wherein the set of relative distances between the second set of coordinates and the one or more objects includes a longitudinal coordinate offset and a lateral coordinate offset of the one or more objects relative to the second set of coordinates.

[0151] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the map data includes a set of line segments representing the one or more objects corresponding to the map data.

[0152] Aspect 12 is a method according to Aspect 11, wherein the one or more objects include one or more roads, one or more building locations, one or more paths, one or more pedestrian roads, one or more vehicle routes, or a combination thereof, wherein the one or more vehicle routes are associated with at least one of a car, a ship, or an airplane.

[0153] Aspect 13 is an apparatus for wireless communication at a UE, 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 is configured to implement a method according to any one of Aspects 1 to 12.

[0154] Aspect 14 is an apparatus according to Aspect 13, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the transceiver or the antenna is configured to send the request for map data, and wherein the transceiver or the antenna is configured to receive the map data.

[0155] Aspect 15 is an apparatus for wireless communication, comprising means for implementing the method according to any one of aspects 1 to 12.

[0156] Aspect 16 is a computer-readable medium (eg, a non-transitory computer-readable medium) storing computer-executable code, wherein when the code is executed by a processor, the processor is caused to implement the method according to any one of aspects 1 to 12.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: Sending a request for map data based on a first set of coordinates in a first coordinate system; receiving the map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system; as well as A set of relative distances between the second set of coordinates and one or more objects corresponding to the map data is calculated.

2. The device according to claim 1, wherein: The at least one processor is further configured to: Based on the set of relative distances, the positioning or navigation of the UE in the first coordinate system is assisted.

3. The device according to claim 1, wherein: The at least one processor is further configured to: The set of relative distances is associated with the first set of coordinates in the first coordinate system.

4. The device according to claim 1, wherein: The first set of coordinates differs from the second set of coordinates by an offset.

5. The device according to claim 4, wherein: The offset is based on a linear transformation between the first set of coordinates in the first coordinate system and the second set of coordinates in the second coordinate system.

6. The device according to claim 1, wherein: The first coordinate system is a World Geodetic System 1984 (WGS-84) coordinate system, and the second coordinate system is at least one of a geodetic datum, a GCJ-02 coordinate system, or a BD-09 coordinate system.

7. The device according to claim 1, wherein: The request for the map data is sent to at least one of a map data client or a map data server, and wherein the map data is received from at least one of the map data client or the map data server.

8. The device according to claim 7, wherein: The first set of coordinates in the first coordinate system is converted into the second set of coordinates in the second coordinate system via the map data client or a third-party application.

9. The device according to claim 1, wherein: The UE does not have the capability or permission to operate in the second coordinate system.

10. The device according to claim 1, wherein: The set of relative distances between the second set of coordinates and the one or more objects includes a longitudinal coordinate offset and a lateral coordinate offset of the one or more objects relative to the second set of coordinates.

11. The device according to claim 1, wherein: The map data includes a set of line segments representing the one or more objects corresponding to the map data.

12. The device according to claim 11, wherein The one or more objects include one or more roads, one or more building locations, one or more paths, one or more pedestrian roads, one or more vehicle routes, or a combination thereof, wherein the one or more vehicle routes are associated with at least one of a car, a ship, or an airplane.

13. The apparatus of claim 1 , further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the transceiver or the antenna is configured to transmit the request for the map data, and wherein, The transceiver or the antenna is configured to receive the map data.

14. A method of wireless communication at a user equipment (UE), comprising: Sending a request for map data based on a first set of coordinates in a first coordinate system; receiving the map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system; as well as A set of relative distances between the second set of coordinates and one or more objects corresponding to the map data is calculated.

15. The method according to claim 14, further comprising: Based on the set of relative distances, the positioning or navigation of the UE in the first coordinate system is assisted.

16. The method according to claim 14, further comprising: The set of relative distances is associated with the first set of coordinates in the first coordinate system.

17. The method according to claim 14, wherein: The first set of coordinates differs from the second set of coordinates by an offset.

18. The method according to claim 17, wherein: The offset is based on a linear transformation between the first set of coordinates in the first coordinate system and the second set of coordinates in the second coordinate system.

19. The method according to claim 14, wherein: The first coordinate system is a World Geodetic System 1984 (WGS-84) coordinate system, and the second coordinate system is at least one of a geodetic datum, a GCJ-02 coordinate system, or a BD-09 coordinate system.

20. The method according to claim 14, wherein: The request for the map data is sent to at least one of a map data client or a map data server, and wherein the map data is received from at least one of the map data client or the map data server.

21. The method according to claim 20, wherein: The first set of coordinates in the first coordinate system is converted into the second set of coordinates in the second coordinate system via the map data client or a third-party application.

22. The method according to claim 14, wherein: The UE does not have the capability or permission to operate in the second coordinate system.

23. The method according to claim 14, wherein: The set of relative distances between the second set of coordinates and the one or more objects includes a longitudinal coordinate offset and a lateral coordinate offset of the one or more objects relative to the second set of coordinates.

24. The method according to claim 14, wherein: The map data includes a set of line segments representing the one or more objects corresponding to the map data.

25. The method according to claim 24, wherein: The one or more objects include one or more roads, one or more building locations, one or more paths, one or more pedestrian roads, one or more vehicle routes, or a combination thereof, wherein the one or more vehicle routes are associated with at least one of a car, a ship, or an airplane.

26. An apparatus for wireless communication at a user equipment (UE), comprising: means for sending a request for map data based on a first set of coordinates in a first coordinate system; means for receiving the map data based on a second set of coordinates in a second coordinate system, wherein the first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system; as well as Means for calculating a set of relative distances between the second set of coordinates and one or more objects corresponding to the map data.

27. The apparatus of claim 26, further comprising a transceiver.

28. A computer readable medium storing computer executable code at a user equipment (UE), the code, when executed by a processor, causes the processor to perform the following operations: Sending a request for map data based on a first set of coordinates in a first coordinate system; receiving the map data based on a second set of coordinates in a second coordinate system, wherein: The first set of coordinates in the first coordinate system is different from the second set of coordinates in the second coordinate system; as well as A set of relative distances between the second set of coordinates and one or more objects corresponding to the map data is calculated.

Images