Selective high definition map download

Abstract

Technology is provided for selectively downloading high-definition (HD) maps to mobile devices. A method for selectively downloading HD maps includes: receiving a set of HD map tiles from a network entity via at least one transceiver of the mobile device; updating a previously stored HD map using the set of HD map tiles to create an updated HD map with the updated set of HD map tiles; and storing the updated HD map in a storage memory. The previously stored HD map includes a plurality of previously stored HD map tiles stored in the storage memory of the mobile device.

Description

Background Technology

[0001] Currently, electronic navigation maps are used in autonomous, semi-autonomous, and driver-assisted vehicle systems, referred to herein as assisted vehicles (AVs). Typically, electronic navigation maps have multiple levels of detail. Lower levels of detail (e.g., low-resolution (LD) maps) are used for driver assistance, such as in-dashboard navigation systems, while high-resolution (HD) maps include sufficient detail to enable the vehicle system to navigate automatically or partially automatically on highways. These HD maps provide the AV with information about highways, such as geolocation, road edge (e.g., curb) location, and traffic control elements (e.g., signs, speed limits, traffic lights, etc.). This information can be used by the AV's vehicle components (e.g., navigation or control systems) to drive the AV on highways or assist a driver in driving the AV.

[0002] Compared to LD maps, HD maps typically have geographically smaller tiles or larger tile data sizes, which can put pressure on the delivery network. Additionally, HD map tiles consume more resources than LD map tiles. Furthermore, the more high-resolution details in an HD tile, the greater the likelihood that it will change over time. This makes HD map tile maintenance more complex than LD map tile maintenance. Downloading HD map tiles in dense AV environments can be difficult due to network limitations and / or environmental issues (e.g., congestion, wireless fading, high communication latency, or network availability). Summary of the Invention

[0003] Techniques are provided for selectively downloading high-definition (HD) maps to mobile devices. An example of a method for selectively downloading HD maps to a mobile device includes: receiving a set of HD map tiles from a network entity via at least one transceiver of the mobile device; using the set of HD map tiles to update a previously stored HD map to create an updated HD map with the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and storing the updated HD map in the storage memory.

[0004] A method for selectively sending HD maps from a network entity to a mobile device is also provided. Examples of the method include: receiving a request for a set of HD map tiles from the mobile device at the network entity, wherein the request includes map information corresponding to a previously stored HD map having multiple previously stored HD map tiles; determining the set of HD map tiles at the network entity based on the map information; and sending the set of HD map tiles from the network entity to the mobile device.

[0005] Also provided is an apparatus for selectively downloading HD maps to a mobile device, the apparatus comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor being in signal communication with the at least one transceiver and the at least one memory, the at least one processor being configured to: receive a set of HD map tiles from a network entity via the at least one transceiver from the mobile device; update a previously stored HD map using the set of HD map tiles to create an updated HD map with the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and store the updated HD map in the storage memory.

[0006] Also provided is an apparatus for selectively downloading an HD map to a mobile device, the apparatus comprising: components for receiving a set of HD map tiles from a network entity via at least one transceiver of the mobile device; components for updating a previously stored HD map using the set of HD map tiles to create an updated HD map with the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and components for storing the updated HD map in the storage memory.

[0007] Other devices, apparatuses, systems, methods, features, and advantages of this disclosure will be apparent to or will become apparent to those skilled in the art upon studying the following figures and detailed description. All such additional devices, apparatuses, systems, methods, features, and advantages are intended to be included within the scope of this description, the disclosure, and protected by the appended claims. Attached Figure Description

[0008] Figure 1 This is a simplified diagram of an example wireless communication system.

[0009] Figure 2 yes Figure 1 The system block diagram shown is of the components of an example user equipment.

[0010] Figure 3 yes Figure 1 The system block diagram shown is of the components of the example send / receive point.

[0011] Figure 4 yes Figure 1 The system block diagram of the components of the example server is shown.

[0012] Figure 5 This is a system block diagram for selectively downloading high-definition (HD) maps to assisted vehicle (AV) mobile devices.

[0013] Figure 6 It is shown Figure 5 The illustration shows an example route of an auxiliary vehicle along a simplified map.

[0014] Figure 7 It is used for updating Figure 5 The image shows a system diagram of an HD map on a mobile device.

[0015] Figure 8 It is used to selectively download HD maps from network entities to Figure 5 The system diagram shows an example of a network entity for a mobile device.

[0016] Figure 9A This is an example of a system diagram that uses foreign codes to resend HD map tiles to more than one vehicle.

[0017] Figure 9B This is an example of a system diagram that uses another foreign code to resend HD map tiles to more than one vehicle.

[0018] Figure 10 This is a system illustration for downloading HD map tiles to AV using side links with other network entities.

[0019] Figure 11 It is a system-executed process for selectively downloading HD maps to... Figure 5 The flowchart shows the method for using a mobile device.

[0020] Figure 12 It is performed by the network entity to selectively download HD maps from the network entity to... Figure 5 and Figure 8 The flowchart shows the method for using a mobile device. Detailed Implementation

[0021] This article discusses techniques for providing, for example, enhanced (e.g., optimized) high-definition (HD) electronic navigation maps (hereinafter referred to as “HD maps”) and downloading HD maps from network entities (such as, for example, map servers) to mobile devices. The mobile device may be located within or integrated into an assisted vehicle (AV), where the AV may include autonomous driving and / or driver-assisted vehicle systems.

[0022] Typically, electronic navigation maps (both HD and low-resolution (LD) maps) are divided into multiple map tiles (or simply "tiles") that can be used to zoom in on the map to obtain finer details within it. Map tiles are usually a collection of square "sub-maps" arranged in a grid along a composite map (i.e., the larger LD or HD map). Due to their greater detail, HD maps typically utilize geographically smaller tiles or have larger tile data sizes than LD maps. The information provided can then be used by the vehicle components of the AV (e.g., navigation or control systems) to drive the AV on highways or assist a driver in driving the AV. However, the larger tile data size in HD maps can be resource-intensive and potentially strain delivery networks, as each HD map tile can, for example, occupy up to 100 megabytes.

[0023] Segmenting the map reduces the resources required for the vehicle component to store the map by enabling it to acquire only those map tiles relevant to a given road segment (e.g., a few miles). Typically, map tiles are obtained from cloud services (e.g., downloaded or pushed). However, in some cases, map tiles may be obtained from more local sources (e.g., at the cloud edge or in fog) (such as other vehicles or roadside units (RSUs)). Various radio access technologies (RATs) can be used to deliver map tiles.

[0024] The more HD details there are in these HD map tiles, the greater the likelihood that they will change over time. This typically makes HD map tile maintenance more complex than LD map tile maintenance, and usually requires the AV to update the HD maps stored on the AV more frequently to improve accuracy.

[0025] However, communication resources may be constrained by various factors, and such constraints may prevent an AV traveling along the route from downloading an updated HD map before reaching the corresponding road segment along the route that should have updated HD map tiles. Examples of factors constraining communication resources may include radio fading and / or obstruction along the route, system problems (e.g., bandwidth and capacity), and potentially high communication latency in one or more given areas along the route.

[0026] This paper discusses techniques for acquiring HD maps using buffers or storage on mobile devices / AVs. For example, techniques may utilize storage and incremental transmission strategies, and external decoding or network decoding may be used to better utilize buffers to improve download efficiency in dense traffic scenarios. For example, techniques for selectively downloading HD maps from network entities to mobile devices associated with or integrated with AVs are discussed. The example techniques discussed herein can be used for HD map prefetching calculations and / or configuration for transferring information between AVs, servers, and base stations (e.g., gNBs) to prepare and / or configure HD map data for transmission between servers and AVs. At least some of the techniques discussed may include gNB selection, wireless connectivity between servers and AVs, and transmission timing. Other examples discussed herein can also be used for HD map downloading to AV groups and HD map download strategies for initiating routing for AVs. Other examples discussed herein can be used for HD map tile prioritization, where one or more factors may be considered for the gNB to decide which AV to send to and / or which HD map tiles to send first.

[0027] For example, an example system and example method for selectively downloading HD maps to a mobile device are discussed, the method comprising: receiving a set of HD map tiles from a network entity via at least one transceiver of the mobile device; using the set of HD map tiles to update a previously stored HD map to create an updated HD map with the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and storing the updated HD map in the storage memory.

[0028] Example systems and methods for selectively sending HD maps from a network entity (e.g., a map server) to a mobile device are also discussed. The method includes: receiving a request for a set of HD map tiles from the mobile device at the network entity, wherein the request includes map information corresponding to a previously stored HD map having multiple previously stored HD map tiles; determining the set of HD map tiles at the network entity based on the map information; and sending the set of HD map tiles from the network entity to the mobile device.

[0029] Generally speaking, AVs with larger buffers / storage units can utilize the techniques described herein to reduce the slippage of HD map transmission along the journey and improve HD map availability to the AV by fully utilizing the storage capacity to alleviate the pressure of downloading real-time HD maps to the AV. These techniques can also improve the efficiency of downloading real-time HD maps to the AV in dense traffic environments.

[0030] The projects and / or technologies described herein may provide one or more of the following capabilities, as well as others not mentioned. Other capabilities may be provided, and not every specific implementation of this disclosure is required to provide any, let alone all, of the capabilities discussed.

[0031] The description herein can refer to a sequence of actions to be performed, for example, by elements of a computing device. The various actions described herein can be performed by special-purpose circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of both. The sequence of actions described herein can be embodied in a non-transitory computer-readable medium storing a corresponding set of computer instructions that, when executed, will cause the associated processor to perform the functionality described herein. Therefore, the various examples described herein can be embodied in several different forms, all of which fall within the scope of this disclosure, including the claimed subject matter.

[0032] As used herein, the terms “User Equipment” (UE) and “Base Station” are not specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise indicated. Generally, a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, Internet of Things (IoT) device, etc.) used to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Terminal,” “Mobile Station,” “Mobile Equipment,” or variations thereof. Generally, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via wired access networks, WiFi, etc. ® Networks (e.g., based on IEEE (Institute of Electrical and Electronics Engineers) 802.11, etc.). In addition to exchanging information with each other via a network, or instead of exchanging information with each other via a network, two or more UEs can communicate directly.

[0033] Depending on the network in which the base station is deployed, the base station can operate according to one of several RATs when communicating with the UE. Examples of base stations include access points (APs), network nodes, NodeBs, evolved NodeBs (eNBs), or generic NodeBs (gNodeBs, gNBs). Furthermore, in some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions.

[0034] The UE can be represented by any of several types of devices, including but not limited to printed circuit (PC) cards, compact flash memory devices, external or internal modems, wireless or wired telephones, smartphones, tablet devices, consumer asset tracking devices, asset tags, etc. The communication link through which the UE can transmit signals to the RAN is called an uplink channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the RAN can transmit signals to the UE is called a downlink or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" can refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0035] As used herein, depending on the context, the term "cell" or "sector" may correspond to one of a plurality of cells of a base station or to the base station itself. The term "cell" may refer to a logical communication entity used to communicate with a base station (e.g., on a carrier) and may be associated with identifiers to distinguish adjacent cells operating via the same or different carriers (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a carrier may support multiple cells and may be configured with different cell types based on different protocol types that can provide access to different types of devices (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). In some examples, the term "cell" may refer to a portion of the geographic coverage area on which a logical entity operates (e.g., a sector).

[0036] refer to Figure 1Examples of communication system 100 include UE 105, UE 106, radio access network (RAN) (here, fifth-generation (5G) next-generation (NG) RAN (NG-RAN) 135), 5G core network (5GC) 140, and server 150. UE 105 and / or UE 106 can be, for example, an IoT device, a location tracker device, a cellular phone, a vehicle (e.g., a car, truck, bus, ship, etc.), or another device. 5G network can also be referred to as a new radio (NR) network; NG-RAN 135 can be referred to as 5G RAN or NR RAN; and 5GC 140 can be referred to as NG core network (NGC). Standardization of NG-RAN and 5GC is underway within the 3rd Generation Partnership Project (3GPP). Therefore, NG-RAN 135 and 5GC 140 can follow current or future standards from 3GPP for 5G support. NG-RAN 135 can be another type of RAN, such as 3G RAN, 4G Long Term Evolution (LTE) RAN, etc. UE 106 can be configured and coupled similarly to UE 105 to transmit signals to and / or receive signals from similar other entities in system 100, but for simplicity of the figures, in Figure 1 Such signaling is not indicated in this document. Similarly, for simplicity, the discussion focuses on UE 105. Communication system 100 may utilize information from a constellation 185 of satellite spacecraft (SVs) 190, 191, 192, 193 from a satellite positioning system (SPS) such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional SPS (such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Coverage Service (EGNOS), or the Wide Area Augmentation System (WAAS)). Additional components of communication system 100 are described below. Communication system 100 may include additional or optional components.

[0037] like Figure 1As shown, NG-RAN 135 includes NR nodeBs (gNBs) 110a and 110b and a next-generation eNodeB (ng-eNB) 114, and 5GC 140 includes Access and Mobility Management Functions (AMF) 115, Session Management Functions (SMF) 117, Location Management Functions (LMF) 120, and Gateway Mobile Location Center (GMLC) 125. gNBs 110a, 110b, and ng-eNB 114 are communicatively coupled to each other, each configured to conduct bidirectional wireless communication with UE 105, and each communicatively coupled to AMF 115 and configured to conduct bidirectional communication with AMF. gNBs 110a, 110b, and ng-eNB 114 may be referred to as base stations (BS). AMF 115, SMF 117, LMF 120, and GMLC 125 are communicatively coupled to each other, and the GMLC is communicatively coupled to an external client 130. The SMF117 can be used as the initial contact point for the Service Control Function (SCF) (not shown) to create, control, and delete media sessions. Base stations (such as gNB 110a, 110b, and / or ng-eNB 114) can be macrocells (e.g., high-power cellular base stations), small cells (e.g., low-power cellular base stations), or access points (e.g., short-range base stations configured to use short-range technologies such as WiFi). ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® ,Bluetooth ® Low power (BLE), Zigbee ® (e.g., one or more of gNB 110a, 110b and / or ng-eNB 114) can be configured to communicate with UE 105 via multiple carriers. Each of gNB 110a, 110b and / or ng-eNB 114 can provide communication coverage for a corresponding geographic area (e.g., cell). Each cell can be divided into multiple sectors based on the base station antennas.

[0038] Figure 1Generalized examples of various components are provided, wherein any or all of the components may be appropriately utilized, and each component may be repeated or omitted as needed. Specifically, although a UE 105 is illustrated, many UEs (e.g., hundreds, thousands, millions, etc.) may be utilized in communication system 100. Similarly, communication system 100 may include a larger (or smaller) number of SVs (i.e., more or fewer than the four SVs 190-193 shown), gNBs 110a and 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The illustrated connections connecting the various components in communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, the components may be rearranged, combined, separated, replaced, and / or omitted according to desired functionality.

[0039] Although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations can be used for other communication technologies such as 3G, Long Term Evolution (LTE), etc. The specific implementations described herein (for 5G technology and / or for one or more other communication technologies and / or protocols) can be used to transmit (or broadcast) directional synchronization signals, receive and measure directional signals at a UE (e.g., UE 105), and / or provide location assistance to UE 105 (via GMLC 125 or other location servers), and / or calculate the location of UE 105 at a location-capable device (such as UE 105, gNB 110a, 110b, or LMF 120) based on measurement parameters received at UE 105 for such directional transmissions. Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (eNodeB) 114, and gNB (gNodeB) 110a, 110b are examples and may be replaced by, or include, various other location server functions and / or base station functions, respectively.

[0040] System 100 is capable of wireless communication because its components can communicate directly or indirectly (at least sometimes using a wireless connection), for example, via gNB 110a, 110b, ng-eNB 114 and / or 5GC 140 (and / or one or more other devices not shown, such as one or more other transceiver base stations). For indirect communication, the communication can be modified during transmission from one entity to another, for example, by changing the header information of data packets, changing the format, etc. UE 105 may include multiple UEs and may be mobile wireless communication devices, but can communicate wirelessly as well as via wired connections. UE 105 can be any of a variety of devices, such as smartphones, tablets, vehicle-based devices, etc., but these are merely examples, as UE 105 does not need to be any of these configurations, and other configurations of UEs can be used. Other UEs may include wearable devices (e.g., smartwatches, smart jewelry, smart glasses, or head-mounted devices, etc.). Other UEs, whether currently existing or developed in the future, may also be used. In addition, other wireless devices (whether mobile or not) can be implemented within system 100 and can communicate with each other and / or with UE 105, gNB 110a, 110b, ng-eNB 114, 5GC 140, and / or external client 130. For example, such other devices may include Internet of Things (IoT) devices, medical devices, home entertainment and / or automation devices, etc. 5GC 140 can communicate with external client 130 (e.g., a computer system), for example, to allow external client 130 (e.g., via GMLC 125) to request and / or receive location information about UE 105.

[0041] UE 105 or other devices can be configured to communicate in various networks and / or for various purposes and / or using various technologies (e.g., 5G, Wi-Fi). ® Communication, multi-frequency Wi-Fi ® Communication, satellite positioning, and one or more types of communication (e.g., GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), LTE (Long Term Evolution), V2X (vehicle-to-everything communication, e.g., V2P (vehicle-to-pedestrian), V2I (vehicle-to-infrastructure), V2V (vehicle-to-vehicle), etc.), IEEE 802.11p, etc.). V2X communication can be cellular (Cellular-V2X (C-V2X)) and / or WiFi. ®(For example, DSRC (Dedicated Short Range Connection)). System 100 can support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals simultaneously on multiple carriers. Each modulated signal can be a Code Division Multiple Access (CDMA) signal, a Time Division Multiple Access (TDMA) signal, an Orthogonal Frequency Division Multiple Access (OFDMA) signal, a Single Carrier Frequency Division Multiple Access (SC-FDMA) signal, etc. Each modulated signal can be transmitted on different carriers and can carry pilot, overhead information, data, etc. UEs 105 and 106 can communicate with each other via UE-to-UE sidelink (SL) communication by transmitting on one or more sidelink (SL) channels (such as the Physical Sidelink Synchronization Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), or Physical Sidelink Control Channel (PSCCH)). Direct device-to-device communication (without a network) is generally referred to as sidelink communication, without limiting the communication to a specific protocol.

[0042] UE 105 may include and / or may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location Enabled (SUPL) terminal (SET), or some other name. UE 105 may correspond to a cellular phone, smartphone, laptop computer, tablet device, PDA, consumer asset tracking device, navigation device, Internet of Things (IoT) device, health monitor, security system, smart city sensor, smart meter, wearable tracker, or some other portable or mobile device. Typically, although not required, UE 105 may use one or more Radio Access Technologies (RATs) to support wireless communication, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi, etc. ® (Also known as Wi-Fi) ® ),Bluetooth ® (BT), WiMax (Global Microwave Access) ® 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. UE 105 can use a Wireless Local Area Network (WLAN) to support wireless communication, which can connect to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. Using one or more of these RATs allows UE 105 (e.g., via elements of 5GC 140) Figure 1(not shown in the image), or possibly via GMLC 125, to communicate with external client 130 and / or allow external client 130 (e.g., via GMLC 125) to receive location information about UE 105.

[0043] UE 105 may include a single entity or may include multiple entities, such as in a personal area network, where the user may employ audio, video, and / or data I / O (input / output) devices, and / or body sensors, as well as separate wired or wireless modems. An estimate of the location of UE 105 may be referred to as location, location estimate, location fixed, fixed, positioning, location estimation, or location fixed, and may be geographic, providing location coordinates of UE 105 (e.g., latitude and longitude), which may or may not include an elevation component (e.g., height above sea level; height above ground level, floor level, or basement level, or depth below). Alternatively, the location of UE 105 may be represented as a municipal location (e.g., as a postal address or designation of a point or smaller area (such as a specific room or floor) within a building). The location of UE 105 may be represented as an area or volume (geographically or municipally defined) within which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of UE 105 can be represented as a relative location, which includes, for example, distance and direction relative to a known location. This relative location can be represented as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to an origin at a known location, which can be, for example, geographically, municipally, or with reference to a point, area, or volume indicated, for example, on a map, floor plan, or building plan. In the description contained herein, the use of the term "location" can include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and (possibly also) z coordinates are typically solved, and then (if necessary) the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level).

[0044] UE 105 can be configured to communicate with other entities using one or more of a variety of technologies. UE 105 can be configured to indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. D2D P2P links can use any suitable D2D radio access technology (RAT) such as LTE Direct (LTE-D), WiFi, etc. ® Direct connection (WiFi) ® -D), Bluetooth ®Support is provided. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a Transmit / Receive Point (TRP) (such as one or more of gNB 110a, 110b and / or ng-eNB 114). Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. The TRP can facilitate the scheduling of resources for D2D communication. In other cases, D2D communication may be performed between UEs without involving the TRP. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a TRP. Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. TRP can facilitate the scheduling of resources used for D2D communication. In other cases, D2D communication can be performed between UEs without involving TRP.

[0045] Figure 1 The base stations (BS) in NG-RAN 135 shown include NR Node Bs (referred to as gNB 110a and gNB 110b). Each pair of gNBs 110a and 110b in NG-RAN 135 can be interconnected via one or more other gNBs. Access to the 5G network is provided to UE 105 via wireless communication with one or more of the gNBs 110a and 110b. These gNBs can use 5G to provide wireless communication access to the 5GC 140 on behalf of UE 105. Figure 1 In this context, it is assumed that the serving gNB of UE 105 is gNB 110a, but another gNB (e.g., gNB 110b) may act as the serving gNB or as a secondary gNB to provide additional throughput and bandwidth to UE 105 if UE 105 moves to another location.

[0046] Figure 1The base station (BS) in NG-RAN 135 shown may include ng-eNB 114, also known as Next Generation Evolved Node B. ng-eNB 114 may be connected to one or more of gNBs 110a and 110b in NG-RAN 135 via one or more other gNBs and / or one or more other ng-eNBs. ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to UE 105. One or more of gNBs 110a, 110b and / or ng-eNB 114 may be configured to act as a location-only beacon, which may transmit signals to assist in determining the location of UE 105, but may not receive signals from UE 105 or other UEs.

[0047] gNB 110a, 110b, and / or ng-eNB 114 may each include one or more TRPs. For example, each sector within a cell of the BS may include a TRP, but multiple TRPs may share one or more components (e.g., a shared processor but with separate antennas). System 100 may include only macro TRPs, or system 100 may have different types of TRPs, such as macro TRPs, pico TRPs, and / or femto TRPs. Macro TRPs may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by terminals with service subscriptions. Pico TRPs may cover a relatively small geographic area (e.g., a pico cell) and may allow unrestricted access by terminals with service subscriptions. Femto or home TRPs may cover a relatively small geographic area (e.g., a femto cell) and may allow restricted access by terminals associated with that femto cell (e.g., terminals of users in a home).

[0048] Each of the gNBs 110a, 110b, and / or ng-eNB 114 may include a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the gNB 110b includes RU 111, DU 112, and CU 113. RU 111, DU 112, and CU 113 define the functionality of the gNB 110b. Although the gNB 110b is shown as having a single RU, a single DU, and a single CU, a gNB may include one or more RUs, one or more DUs, and / or one or more CUs. The interface between CU 113 and DU 112 is referred to as the F1 interface. RU 111 is configured to perform digital front-end (DFE) functions (e.g., analog-to-digital conversion, filtering, power amplification, transmit / receive) and digital beamforming, and includes part of the physical (PHY) layer. RU 111 may perform DFE using massive MIMO and may be integrated with one or more antennas of the gNB 110b. DU 112 hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer of gNB 110b. A DU can support one or more cells, and each cell is supported by a single DU. The operation of DU 112 is controlled by CU 113. CU 113 is configured to perform functions for delivering user data, mobility control, radio access network sharing, location, session management, etc., although some functions are only assigned to DU 112. CU 113 hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) of gNB 110b. UE 105 can communicate with CU 113 via the RRC, SDAP, and PDCP layers, with DU 112 via the RLC, MAC, and PHY layers, and with RU 111 via the PHY layer.

[0049] As pointed out, although Figure 1 The diagram depicts nodes configured to communicate according to 5G communication protocols, but nodes configured to communicate according to other communication protocols (such as, for example, LTE or IEEE 802.11x) can also be used. For instance, in an evolved packet system (EPS) providing LTE radio access to UE 105, the RAN may include an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), which may include base stations containing evolved Node Bs (eNBs). The core network for the EPS may include an evolved packet core (EPC). The EPS may include the E-UTRAN plus the EPC, where the E-UTRAN corresponds to... Figure 1 NG-RAN 135 in the figure and EPC corresponds to 5GC 140 in the figure.

[0050] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115; for location functionality, AMF communicates with LMF 120. AMF 115 can support UE 105 mobility (including cell changes and handover) and can participate in supporting signaling connections with UE 105 and (possibly) data and voice bearers for UE 105. LMF 120 can communicate directly with UE 105, for example, wirelessly, or directly with gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can support UE 105 positioning when UE 105 accesses NG-RAN 135, and can support various positioning procedures / methods, such as Auxiliary GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA) (e.g., Downlink (DL) OTDOA or Uplink (UL) OTDOA), Round Trip Time (RTT), Multi-Cell RTT, Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AoA), Angle of Departure (AoD), and / or other positioning methods. LMF 120 can process, for example, location service requests for UE 105 received from AMF 115 or GMLC 125. LMF 120 can connect to AMF 115 and / or GMLC 125. LMF 120 can be referred to by other names, such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value-Added LMF (VLMF). The node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobility Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). At least a portion of the location functionality (including the derivation of the location of UE 105) can be performed at UE 105 (e.g., using signal measurements obtained by UE 105 against signals transmitted by radio nodes (such as gNB 110a, 110b and / or ng-eNB 114), and / or auxiliary data provided to UE 105, for example, by LMF 120). AMF 115 can be used as a control node to process signaling between UE 105 and 5GC 140 and can provide QoS (Quality of Service) streaming and session management. AMF 115 can support the mobility of UE 105 (including cell changes and handover) and can participate in supporting signaling connections with UE 105.

[0051] Server 150 (e.g., a cloud server) is configured to obtain the location estimate of UE 105 and provide it to external client 130. Server 150 may be configured, for example, to run a microservice / service for obtaining the location estimate of UE 105. Server 150 may, for example (e.g., by sending a location request to it), pull the location estimate from one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or ng-eNB 114 and / or LMF 120. As another example, one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or LMF 120 may push the location estimate of UE 105 to server 150.

[0052] GMLC 125 can support location requests for UE 105 received from external client 130 via server 150, and can forward such location requests to AMF 115 for forwarding to LMF 120, or can forward the location request directly to LMF 120. A location response from LMF 120 (e.g., containing a location estimate for UE 105) can be returned to GMLC 125 directly or via AMF 115, and GMLC 125 can then return the location response (e.g., containing the location estimate) to external client 130 via server 150. GMLC 125 is shown connected to both AMF 115 and LMF 120, but in some specific implementations it may not be connected to either AMF 115 or LMF 120.

[0053] like Figure 1 As a further example, the LMF 120 can use the new radio positioning protocol A (which may be referred to as NPPa or NRPPa) to communicate with gNB 110a, 110b and / or ng-eNB 114, which can be defined in 3GPP Technical Specification (TS) 38.455. NRPPa can be the same as, similar to or an extension of the LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, where NRPPa messages are transmitted via AMF 115 between gNB 110a (or gNB 110b) and LMF 120, and / or between ng-eNB 114 and LMF 120. Figure 1As a further example, LMF 120 and UE 105 can communicate using the LTE Location Protocol (LPP), which is defined in 3GPP TS 36.355. LMF 120 and UE 105 can also communicate using a new radio positioning protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of LPP. Here, LPP and / or NPP messages can be transmitted between UE 105 and LMF 120 via AMF 115 and UE 105's serving gNB 110a, 110b, or serving ng-eNB 114. For example, LPP and / or NPP messages can be transmitted between LMF 120 and AMF 115 using the 5G Location Services Application Protocol (LCS AP), and between AMF 115 and UE 105 using the 5G Non-Access Stratum (NAS) protocol. The LPP and / or NPP protocols can be used to support the location of UE 105 using UE-assisted and / or UE-based positioning methods (such as A-GNSS, RTK, OTDOA, and / or E-CID). The NRPPa protocol can be used to support the location of UE 105 using network-based positioning methods (such as E-CID) (e.g., when used in conjunction with measurements obtained by gNB 110a, 110b, or ng-eNB 114) and / or can be used by LMF 120 to obtain location-related information from gNB 110a, 110b, and / or ng-eNB 114, such as defining parameters sent by directional SS or PRS from gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can be co-located or integrated with gNB or TRP, or can be configured to be located away from gNB and / or TRP and communicate directly or indirectly with gNB and / or TRP.

[0054] Using a UE-assisted positioning method, UE 105 can obtain location measurements and transmit these measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105. For example, location measurements may include one or more of the following: Received Signal Strength Indication (RSSI), Round-Trip Time (RTT), Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), and / or Reference Signal Received Quality (RSRQ) for gNB 110a, 110b, ng-eNB 114, and / or WLAN AP. Location measurements may additionally or alternatively include measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190-193.

[0055] Using a UE-based positioning method, UE 105 can obtain a location measurement (e.g., which may be the same as or similar to the location measurement of a UE-assisted positioning method) and can calculate the location of UE 105 (e.g., by means of auxiliary data received from a location server (such as LMF 120) or broadcast by gNB 110a, 110b, ng-eNB 114 or other base stations or APs).

[0056] Using a network-based positioning method, one or more base stations (e.g., gNB 110a, 110b and / or ng-eNB 114) or APs can obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or Time of Arrival (ToA) of signals transmitted by UE 105) and / or can receive measurements obtained by UE 105. One or more base stations or APs can transmit the measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105.

[0057] The information provided to the LMF 120 by the gNB 110a, 110b and / or ng-eNB 114 using NRPPa may include timing and configuration information for directing SS or PRS transmissions, as well as location coordinates. The LMF 120 may provide some or all of this information as supplementary data to the UE 105 in LPP and / or NPP messages via NG-RAN 135 and 5GC140.

[0058] The LPP or NPP message transmitted from LMF 120 to UE 105 can command UE 105 to perform any of a variety of tasks depending on the desired functionality. For example, the LPP or NPP message may contain instructions for UE 105 to obtain measurements of GNSS (or A-GNSS), WLAN, E-CID, and / or OTDOA (or some other positioning method). In the case of E-CID, the LPP or NPP message may command UE 105 to obtain measurements supported by one or more of gNB 110a, 110b, and / or ng-eNB 114 (or by some other type of base station such as eNB or WiFi). ® One or more measurement parameters (e.g., beam ID, beamwidth, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a specific cell supported by the AP. UE 105 can transmit these measurement parameters back to LMF 120 via serving gNB110a (or serving ng-eNB 114) and AMF 115 in an LPP or NPP message (e.g., within a 5G NAS message).

[0059] As noted, while a communication system 100 is described in relation to 5G technology, the communication system 100 can be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) for supporting and interacting with mobile devices (such as UE 105) (e.g., to provide voice, data, location, and other functionalities). In some such specific implementations, the 5GC 140 can be configured to control different air interfaces. For example, the 5GC 140 can use non-3GPP interoperability functions (N3IWF) within the 5GC 140. Figure 1 (Not shown) Connected to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi for UE 105. ® Access, and may include one or more WiFi networks. ® AP. Here, the N3IWF can connect to the WLAN and other components in the 5GC 140, such as the AMF 115. In some specific implementations, both the NG-RAN 135 and the 5GC 140 can be replaced by one or more other RANs and one or more other core networks. For example, in EPS, the NG-RAN 135 can be replaced by an E-UTRAN containing eNBs, and the 5GC 140 can be replaced by an EPC containing a Mobility Management Entity (MME) instead of the AMF 115, an E-SMLC instead of the LMF 120, and a GMLC that can be similar to the GMLC 125. In such EPS, the E-SMLC can use LPPa instead of NRPPa to transmit location information to and receive location information from eNBs in the E-UTRAN, and can use LPP to support the location of the UE 105. In these other examples, the location of UE 105 using directional PRS can be supported in a manner similar to that described herein for 5G networks. The difference lies in the fact that the functions and procedures described herein for gNB 110a, 110b, ng-eNB 114, AMF 115, and LMF 120 can, in some cases, be alternatively applied to other network elements, such as eNBs and WiFi. ® AP, MME, and E-SMLC.

[0060] As noted, in some examples, positioning functionality can be achieved at least in part using directional SS or PRS beams transmitted by base stations (such as gNB 110a, 110b and / or ng-eNB 114) at the location of the UE (e.g., whose location is to be determined). Figure 1 Within the range of UE 105. In some instances, the UE can use directional SS or PRS beams from multiple base stations (such as gNB 110a, 110b, ng-eNB 114, etc.) to calculate the UE's location.

[0061] Also refer to Figure 2UE 200 may be an example of one of UEs 105 and 106, and may include a computing platform containing processor 210, a memory 211 containing software (SW) 212, one or more sensors 213, a transceiver interface 214 for transceivers 215 (including wireless transceiver 240 and wired transceiver 250), a user interface 216, a satellite positioning system (SPS) receiver 217, a camera 218, and a positioning device (PD) 219. The processor 210, memory 211, sensors 213, transceiver interface 214, user interface 216, SPS receiver 217, camera 218, and positioning device 219 may be communicatively coupled to each other via a bus 220 (which may be configured for, for example, optical and / or electrical communication). One or more of the devices shown (e.g., camera 218, positioning device 219, and / or one or more sensors in sensor 213, etc.) may be omitted from UE 200. Processor 210 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 210 may include multiple processors, including a general-purpose / application processor 230, a digital signal processor (DSP) 231, a modem processor 232, a video processor 233, and / or a sensor processor 234. One or more of processors 230 to 234 may include multiple devices (e.g., multiple processors). For example, sensor processor 234 may include processors for, for example, RF (radio frequency) sensing (where one or more transmitted (cellular) wireless signals and reflections are used to identify, map, and / or track objects) and / or ultrasound, etc. Modem processor 232 may support dual SIM / dual connectivity (or even more SIMs). For example, a SIM (subscriber identity module or subscriber identification module) may be used by an original equipment manufacturer (OEM), and another SIM may be used by the end user of UE 200 to obtain connectivity. Memory 211 may be a non-transitory storage medium that may include random access memory (RAM), flash memory, disk memory, and / or read-only memory (ROM), etc. Memory 211 may store software 212, which may be processor-readable, processor-executable software code containing instructions that, when executed, cause processor 210 to perform the various functions described herein. Alternatively, software 212 may not be directly executable by processor 210, but may be configured, for example, to cause processor 210 to perform these functions when compiled and executed. The description herein may refer to processor 210 performing a particular function, but this includes other specific implementations, such as processor 210 performing software and / or firmware. The description herein may refer to the functions performed by processor 210 as abbreviated as processor-executed functions of one or more of processors 230 to 234.The description herein may be referred to as the abbreviation for the execution of functions by one or more appropriate components of UE 200. Processor 210 may include memory with stored instructions as a supplement to and / or alternative to memory 211. The functionality of processor 210 is discussed more fully below.

[0062] Figure 2 The configuration of UE 200 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, an example configuration of the UE may include one or more of processors 230 to 234 in processor 210, memory 211, and wireless transceiver 240. Other example configurations may include one or more of processors 230 to 234 in processor 210, memory 211, wireless transceiver, and one or more of the following devices: sensor 213, user interface 216, SPS receiver 217, camera 218, PD 219, and / or wired transceiver.

[0063] UE 200 may include a modem processor 232 capable of performing baseband processing on signals received and downconverted by transceiver 215 and / or SPS receiver 217. Modem processor 232 may also perform baseband processing on signals to be upconverted for transmission by transceiver 215. Alternatively, baseband processing may be performed by general-purpose / application processor 230 and / or DSP 231. However, other configurations may be used to perform baseband processing.

[0064] UE 200 may include sensor 213, which may include, for example, an inertial measurement unit (IMU) 270, one or more magnetometers 271, and / or one or more environmental sensors 272. IMU 270 may include, for example, one or more accelerometers 273 (e.g., collectively responding to acceleration of UE 200 in three dimensions) and / or one or more gyroscopes 274 (e.g., three-dimensional gyroscopes). Sensor 213 may include one or more magnetometers 271 (e.g., three-dimensional magnetometers) to determine (e.g., relative to magnetic north and / or true north) orientation, which can be used for any of a variety of purposes, such as supporting one or more compass applications. Environmental sensors 272 may include, for example, one or more temperature sensors, one or more barometric pressure sensors, one or more ambient light sensors, one or more camera imagers, and / or one or more microphones, etc. Sensor 213 may generate analog and / or digital signals, indications of which may be stored in memory 211 and processed by DSP 231 and / or general-purpose / application processor 230 to support one or more applications, such as applications involving positioning and / or navigation operations. Sensor 213 may include one or more of other types of sensors, such as one or more optical sensors, one or more weight sensors and / or one or more radio frequency (RF) sensors.

[0065] Sensor 213 can be used for relative position measurement, relative position determination, motion determination, etc. Information detected by sensor 213 can be used for motion detection, relative displacement, dead reckoning, sensor-based position determination, and / or sensor-assisted position determination. Sensor 213 can be used to determine whether UE 200 is stationary or moving and / or whether to report certain useful information related to the mobility of UE 200 to LMF 120. For example, based on information obtained / measured by sensor 213, UE 200 can notify / report to LMF 120 that UE 200 has detected movement or that UE 200 has moved, and report relative displacement / distance (e.g., via dead reckoning implemented by sensor 213, or sensor-based position determination, or sensor-assisted position determination). In another example, for relative positioning information, the sensor / IMU can be used to determine the angle and / or orientation of another device relative to UE 200, etc.

[0066] IMU 270 can be configured to provide measurements of the direction and / or velocity of motion of UE 200, which can be used for relative position determination. For example, one or more accelerometers 273 and / or one or more gyroscopes 274 of IMU 270 can detect the linear acceleration and rotational velocity of UE 200, respectively. The linear acceleration and rotational velocity measurements of UE 200 can be integrated over time to determine the instantaneous direction of motion and displacement of UE 200. The instantaneous direction of motion and displacement can be integrated to track the position of UE 200. For example, a reference position of UE 200 at a given moment can be determined, for example, using SPS receiver 217 (and / or by some other means), and measurements acquired from accelerometers 273 and gyroscopes 274 after that moment can be used for dead reckoning to determine the current position of UE 200 based on the movement (direction and distance) of UE 200 relative to that reference position.

[0067] Magnetometer 271 can determine the strength of magnetic fields in different directions, which can be used to determine the orientation of UE 200. For example, this orientation can be used to provide a digital compass for UE 200. The magnetometer may include a two-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in two orthogonal dimensions. Magnetometer 271 may also include a three-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in three orthogonal dimensions. Magnetometer 271 may provide components for sensing magnetic fields and, for example, providing an indication of the magnetic field to processor 210.

[0068] Transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 240 may include a wireless transmitter 242 and a wireless receiver 244 coupled to antenna 246 for transmitting (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals 248 and converting signals from wireless signals 248 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 248. Wireless transmitter 242 includes suitable components (e.g., power amplifiers and digital-to-analog converters). Wireless receiver 244 includes suitable components (e.g., one or more amplifiers, one or more frequency filters, and analog-to-digital converters). Wireless transmitter 242 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 244 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 240 can be configured to support various radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ®The new radio can transmit signals (e.g., with TRP and / or one or more other devices). The new radio can use millimeter wave frequencies and / or frequencies below 6 GHz. Wired transceiver 250 may include a wired transmitter 252 and a wired receiver 254 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communications from NG-RAN 135. Wired transmitter 252 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wired receiver 254 may include multiple receivers that may be discrete components or combined / integrated components. Wired transceiver 250 may be configured, for example, for optical and / or electrical communication. Transceiver 215 may be communicatively coupled to transceiver interface 214, for example, via optical and / or electrical connections. Transceiver interface 214 may be at least partially integrated with transceiver 215. The wireless transmitter 242, the wireless receiver 244, and / or the antenna 246 may each include multiple transmitters, multiple receivers, and / or multiple antennas for transmitting and / or receiving appropriate signals, respectively.

[0069] User interface 216 may include one or more of a number of devices, such as speakers, microphones, display devices, vibration devices, keyboards, touchscreens, etc. User interface 216 may include more than one of these devices. User interface 216 may be configured to enable a user to interact with one or more applications hosted by UE 200. For example, user interface 216 may store indications of analog and / or digital signals in memory 211 in response to actions from the user, for processing by DSP 231 and / or general-purpose / application processor 230. Similarly, applications hosted on UE 200 may store indications of analog and / or digital signals in memory 211 to present output signals to the user. User interface 216 may include audio input / output (I / O) devices, including, for example, speakers, microphones, digital-to-analog circuitry, analog-to-digital circuitry, amplifiers, and / or gain control circuitry (including more than one of these devices). Other configurations of the audio I / O devices may be used. Additionally or alternatively, the user interface 216 may include one or more touch sensors that respond to touch and / or pressure on, for example, the keyboard and / or touchscreen of the user interface 216.

[0070] SPS receiver 217 (e.g., a Global Positioning System (GPS) receiver) may be able to receive and acquire SPS signal 260 via SPS antenna 262. SPS antenna 262 is configured to convert SPS signal 260 from a wireless signal to a wired signal (e.g., an electrical or optical signal) and may be integrated with antenna 246. SPS receiver 217 may be configured to process the acquired SPS signal 260 fully or partially to estimate the location of UE 200. For example, SPS receiver 217 may be configured to determine the location of UE 200 by performing trilateration using SPS signal 260. The acquired SPS signal may be processed fully or partially using general-purpose / application processor 230, memory 211, DSP 231, and / or one or more dedicated processors (not shown), and / or the estimated location of UE 200 may be calculated. Memory 211 may store indications (e.g., measurements) of SPS signal 260 and / or other signals (e.g., signals acquired from wireless transceiver 240) for use in performing positioning operations. General-purpose / application processor 230, DSP 231, and / or one or more dedicated processors, and / or memory 211 may provide or support a location engine for processing measurements to estimate the location of UE 200.

[0071] UE 200 may include a camera 218 for capturing still or moving images. Camera 218 may include, for example, an imaging sensor (e.g., a charge-coupled device or CMOS (complementary metal-oxide-semiconductor) imager), lenses, analog-to-digital circuitry, frame buffers, etc. Additional processing, conditioning, encoding, and / or compression of signals representing the captured images may be performed by a general-purpose / application processor 230 and / or a DSP 231. Additionally or alternatively, a video processor 233 may perform conditioning, encoding, compression, and / or manipulation of signals representing the captured images. The video processor 233 may decode / decompress stored image data for presentation on a display device (not shown), for example, the user interface 216.

[0072] Location device (PD) 219 may be configured to determine the location of UE 200, the movement of UE 200, and / or the relative location of UE 200, and / or time. For example, PD 219 may communicate with SPS receiver 217 and / or include part or all of the SPS receiver. PD 219 may, where appropriate, work in conjunction with processor 210 and memory 211 to perform at least a portion of one or more location methods, although the description herein may refer to PD 219 being configured to perform according to a location method or the PD performing according to a location method. PD 219 may additionally or alternatively be configured to: perform trilateration using terrestrial signals (e.g., at least some radio signals 248), assist in acquisition, and use SPS signal 260, or both, to determine the location of UE 200. PD 219 may be configured to determine the location of UE 200 based on the cell of the serving base station (e.g., cell center) and / or another technology (such as E-CID). PD 219 can be configured to determine the location of UE 200 using one or more images from camera 218 and image recognition combined with the known location of landmarks (e.g., natural landmarks such as mountains and / or man-made landmarks such as buildings, bridges, streets, etc.). PD 219 can be configured to determine the location of UE 200 using one or more other technologies (e.g., relying on the UE's self-reported location (e.g., part of the UE's positioning beacon)), and can use a combination of these technologies (e.g., SPS and terrestrial positioning signals) to determine the location of UE 200. PD 219 may include one or more sensors 213 (e.g., gyroscopes, accelerometers, magnetometers, etc.) that can sense the orientation and / or motion of UE 200 and provide an indication of such orientation and / or motion, and processor 210 (e.g., general-purpose / application processor 230 and / or DSP 231) can be configured to use this indication to determine the motion of UE 200 (e.g., velocity vector and / or acceleration vector). PD219 can be configured to provide an indication of uncertainty and / or error in the determined positioning and / or motion. The functionality of PD219 can be provided in a variety of ways and / or configurations, such as by a general-purpose / application processor 230, transceiver 215, SPS receiver 217 and / or another component of UE 200, and can be provided by hardware, software, firmware or various combinations thereof.

[0073] Also refer to Figure 3Examples of TRP 300 for gNB 110a, 110b and / or ng-eNB 114 may include a computing platform including processor 310, memory 311 including software (SW) 312, and transceiver 315. Processor 310, memory 311 and transceiver 315 may be communicatively coupled to each other via bus 320 (which may be configured for, for example, optical communication and / or electrical communication). One or more devices in the illustrated apparatus (e.g., wireless transceivers) may be omitted from TRP 300. Processor 310 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 310 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors and / or sensor processors, such as... Figure 2 (As shown). Memory 311 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 311 may store software 312, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 310 to perform the various functions described herein when executed. Alternatively, software 312 may not be directly executable by processor 310, but may be configured to cause processor 310 to perform these functions, for example, when compiled and executed.

[0074] The description herein may refer to processor 310 performing a function, but this includes other specific implementations, such as processor 310 performing software and / or firmware. The description herein may refer to processor 310 performing a function as an abbreviation of one or more processors included in processor 310 performing that function. The description herein may refer to TRP 300 performing a function as an abbreviation of one or more suitable components of TRP 300 (and therefore one of gNB 110a, 110b and / or ng-eNB 114) (e.g., processor 310 and memory 311) performing that function. Processor 310 may include memory with stored instructions as a complement to and / or alternative to memory 311. The functionality of processor 310 is discussed more fully below.

[0075] Transceiver 315 may include a wireless transceiver 340 and / or a wired transceiver 350 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 340 may include a wireless transmitter 342 and a wireless receiver 344 coupled to one or more antennas 346 for transmitting (e.g., on one or more uplink channels and / or one or more downlink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more uplink channels) wireless signals 348 and converting signals from wireless signals 348 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 348. Therefore, wireless transmitter 342 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 344 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 340 can be configured to support various radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ® The wired transceiver 350 may include a wired transmitter 352 and a wired receiver 354 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communications to, for example, LMF 120 and / or one or more other network entities. The wired transmitter 352 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 354 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 350 may be configured, for example, for optical communication and / or electrical communication.

[0076] Figure 3The configuration of TRP 300 shown is illustrative and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, the description herein discusses that TRP 300 may be configured to perform several functions or that the TRP performs several functions, but one or more of these functions may be performed by LMF 120 and / or UE 200 (i.e., LMF 120 and / or UE 200 may be configured to perform one or more of these functions).

[0077] Also refer to Figure 4 Server 400 (LMF 120 may be an example thereof) may include: a computing platform including processor 410, a memory 411 including software (SW) 412, and a transceiver 415. Processor 410, memory 411, and transceiver 415 may be communicatively coupled to each other via bus 420 (which may be configured for, for example, optical communication and / or electrical communication). One or more devices in the illustrated apparatus (e.g., a wireless transceiver) may be omitted from server 400. Processor 410 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 410 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors, and / or sensor processors, such as… Figure 2 (As shown). Memory 411 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 411 may store software 412, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 410 to perform the various functions described herein when executed. Alternatively, software 412 may not be directly executable by processor 410, but may be configured to cause processor 410 to perform these functions, for example, when compiled and executed. The description herein may refer to processor 410 performing a function, but this includes other specific implementations, such as processor 410 performing software and / or firmware. The description herein may refer to the function performed by processor 410 as an abbreviation of one or more processors included in processor 410 performing a function. The description herein may refer to the function performed by server 400 as an abbreviation of one or more suitable components of server 400 performing a function. Processor 410 may include memory with stored instructions as a supplement to and / or alternative to memory 411. The functionality of processor 410 will be discussed more comprehensively below.

[0078] Transceiver 415 may include a wireless transceiver 440 and / or a wired transceiver 450 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 440 may include a wireless transmitter 442 and a wireless receiver 444 coupled to one or more antennas 446 for transmitting (e.g., on one or more downlink channels) and / or receiving (e.g., on one or more uplink channels) wireless signals 448 and converting signals from wireless signals 448 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 448. Therefore, wireless transmitter 442 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 444 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 440 can be configured to support various radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ® The wired transceiver 450 may include a wired transmitter 452 and a wired receiver 454 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communications to, for example, TRP 300 and / or one or more other network entities. The wired transmitter 452 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 454 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 450 may be configured, for example, for optical communication and / or electrical communication.

[0079] The description herein may refer to processor 410 performing a function, but this includes other specific implementations, such as processor 410 performing software and / or firmware (stored in memory 411). The description herein may refer to the function performed by server 400 as an abbreviation for the function performed by one or more appropriate components of server 400 (e.g., processor 410 and memory 411).

[0080] Figure 4The configuration of server 400 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, wireless transceiver 440 may be omitted. Furthermore or alternatively, the description herein discusses server 400 being configured to perform certain functions or the server performing certain functions, but one or more of these functions may be performed by TRP 300 and / or UE 200 (i.e., TRP 300 and / or UE 200 may be configured to perform one or more of these functions).

[0081] Positioning technology

[0082] For terrestrial positioning of UEs in cellular networks, techniques such as Advanced Forward Link Trilateral Measurement (AFLT) and Observed Time Difference of Arrival (OTDOA) typically operate in a “UE-assisted” mode, where measurements of reference signals (e.g., PRS, CRS, etc.) transmitted by the base station are acquired by the UE and subsequently provided to a location server. The location server calculates the UE’s location based on this measurement and the known location of the base station. Because these techniques use a location server (rather than the UE itself) to calculate the UE’s location, they are not frequently used in applications such as car or cellular phone navigation, which typically rely on satellite-based positioning instead.

[0083] UEs can use Satellite Positioning System (SPS) (Global Navigation Satellite System (GNSS)) to achieve high-accuracy positioning using Precise Point Positioning (PPP) or Real-Time Kinematics (RTK) techniques. These techniques use auxiliary data, such as measurements from ground-based stations. LTE Release 15 allows data to be encrypted so that only UEs subscribed to the service can read it. This auxiliary data changes over time. Therefore, a UE with a subscribed service may not be able to easily "crack" the encryption for other UEs by passing the data to them without paying for the subscription. This transmission needs to be repeated every time the auxiliary data changes.

[0084] In UE-assisted positioning, the UE transmits measurements (e.g., TDOA, Angle of Arrival (AoA), etc.) to a positioning server (e.g., LMF / eSMLC). The positioning server has a Base Station Almanac (BSA), which contains multiple "entries" or "records," one record per cell, where each record contains the geographic cell location, but may also include other data. Identifiers of the "records" among the multiple "records" in the BSA can be referenced. The BSA and measurements from the UE can be used to calculate the UE's positioning.

[0085] In conventional UE-based positioning, the UE calculates its own location, thus avoiding transmitting measurements to the network (e.g., a location server), which improves latency and scalability. The UE uses relevant BSA record information from the network (e.g., the location of the gNB (more broadly, the base station)). BSA information can be encrypted. However, since BSA information changes much less frequently than, for example, PPP or RTK auxiliary data described above, it may be easier to make BSA information available to UEs that have not subscribed and have not paid for decryption keys (compared to PPP or RTK information). The transmission of reference signals by the gNB makes BSA information potentially accessible to crowdsourcing or driving attacks, thus essentially enabling BSA information to be generated based on in-the-field and / or over-the-top observations.

[0086] Positioning technologies can be characterized and / or evaluated based on one or more criteria, such as positioning accuracy and / or latency. Latency is the time elapsed between the event that triggers the determination of positioning-related data and the availability of that data at the positioning system interface (e.g., the interface of an LMF 120). The latency for the availability of positioning-related data at the time of positioning system initialization is called the First Fix (TTFF), and is greater than the latency after the TTFF. The reciprocal of the time elapsed between two consecutive availability periods of positioning-related data is called the update rate, i.e., the rate at which positioning-related data is generated after the TTFF. Latency can depend on (e.g., the UE's) processing capacity. For example, assuming an allocation of 272 PRBs (Physical Resource Blocks), the UE can report its processing capacity as the duration (in time units, e.g., milliseconds) of DL PRS symbols that it can process per T time units (e.g., Tms). Other examples of capabilities that may affect latency include the number of TRPs from which the UE can process PRS, the number of PRSs the UE can process, and the UE's bandwidth.

[0087] One or more of many different positioning techniques (also known as positioning methods) can be used to determine the location of an entity (such as one of UE105, 106). Known positioning techniques include RTT, multiple RTT, OTDOA (also known as TDOA and including UL-TDOA and DL-TDOA), Enhanced Cell Identification (E-CID), DL-AoD, UL-AoA, etc. RTT uses the time it takes for a signal to travel from one entity to another and back to determine the range between the two entities. The range, plus the known location of the first entity and the angle between the two entities (e.g., azimuth), can be used to determine the location of the second entity. In multiple RTT (also known as multi-cell RTT), multiple ranges from one entity (e.g., UE) to other entities (e.g., TRP) and the known locations of other entities can be used to determine the location of that one entity. In TDOA, the time difference of travel between an entity and other entities can be used to determine the relative range with respect to other entities, and this relative range, combined with the known locations of other entities, can be used to determine the location of that one entity. Angle of arrival and / or angle of departure can be used to help determine the location of an entity. For example, the angle of arrival or departure of a signal, combined with the range between devices (distances determined using signals (e.g., signal travel time, signal received power, etc.)) and the known location of one of these devices, can be used to determine the location of another device. The angle of arrival or departure can be an azimuth angle relative to a reference direction (such as true north). The angle of arrival or departure can also be a zenith angle relative to directly upwards from the entity (i.e., radially outwards from the Earth's center). E-CID uses the identity of the serving cell, timing advance (i.e., the difference between the reception time and transmission time at the UE), estimated timing and power of detected neighboring cell signals, and possible angles of arrival (e.g., the angle of arrival of signals from the base station at the UE, or vice versa) to determine the location of the UE. In TDOA, the time difference of arrival of signals from different sources at the receiving device, along with the known locations of these sources and the known offsets of the transmission times from these sources, are used to determine the location of the receiving device.

[0088] In network-centric RTT estimation, the serving base station instructs the UE to scan / receive RTT measurement signals (e.g., PRS) on the serving cells of two or more neighboring base stations (and typically the serving base station, as at least three base stations are required). These one or more base stations transmit the RTT measurement signals on low-reuse resources (e.g., resources used by the base station to transmit system information) allocated by the network (e.g., a location server, such as LMF 120). The UE records the arrival time (also referred to as the reception time, received time, time of receipt, or time of arrival (ToA)) of each RTT measurement signal relative to the UE's current downlink timing (e.g., as derived by the UE from DL signals received from its serving base station), and (e.g., when instructed by its serving base station) transmits a shared or individual RTT response message (e.g., an SRS (Sound Reference Signal) for positioning, i.e., UL-PRS) to these one or more base stations, and may include the time difference TRx→Tx between the ToA of the RTT measurement signal and the transmission time of the RTT response message (i.e., UE TRx-Tx or UERx-Tx) in the payload of each RTT response message. The RTT response message will include a reference signal from which the base station can infer the Time of Arrival (ToA) of the RTT response. By comparing the difference T_(Tx→Rx) between the transmission time of the RTT measurement signal from the base station and the ToA of the RTT response at the base station with the time difference T_(Rx→Tx) reported by the UE and subtracting UERx-Tx, the base station can infer the propagation time between the base station and the UE. Based on this propagation time, the base station can determine the distance between the UE and the base station by assuming the speed of light during this propagation time.

[0089] UE-centric RTT estimation is similar to network-based methods, except that the UE sends an uplink RTT measurement signal (e.g., when commanded by a serving base station), which is received by multiple base stations near the UE. Each base station involved responds with a downlink RTT response message, which may include in its payload the time difference between the ToA of the RTT measurement signal at the base station and the time of transmission of the RTT response message from the base station.

[0090] For both network-centric and UE-centric procedures, the side performing RTT calculation (network or UE) typically (but not always) sends a first message or signal (e.g., an RTT measurement signal), while the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the first message or signal and the transmission time of the RTT response message or signal.

[0091] Multiple RTT (Multiple Real-Time Toll) technology can be used to determine location. For example, a first entity (e.g., a UE) may transmit one or more signals (e.g., unicast, multicast, or broadcast from a base station), and multiple second entities (e.g., other TSPs, such as a base station and / or the UE) may receive signals from the first entity and respond to those received signals. The first entity receives responses from the multiple second entities. The first entity (or another entity, such as an LMF) may use the responses from the second entities to determine the range to the second entities, and the location of the first entity may be determined by trilateration using the multiple ranges and the known locations of the second entities.

[0092] In some instances, additional information in the form of angle of arrival (AoA) or angle of departure (AoD) can be obtained, which defines a straight-line direction (e.g., this direction can be in a horizontal plane or in three dimensions) or a possible (e.g., the UE's direction as seen from the base station's location) range of directions. The intersection of the two directions can provide another estimate of the UE's location.

[0093] For positioning techniques that use PRS (Location Reference Signal) signals (e.g., TDOA and RTT), the PRS signals transmitted by multiple TRPs are measured, and the arrival time, known transmission time, and known location of the TRPs are used to determine the range from the UE to the TRPs. For example, RSTD (Reference Signal Time Difference) can be determined for PRS signals received from multiple TRPs, and this RSTD is used in TDOA techniques to determine the UE's location. The Location Reference Signal may be referred to as the PRS or PRS signal. PRS signals are typically transmitted using the same power, and PRS signals with the same signal characteristics (e.g., the same frequency shift) may interfere with each other, causing a PRS signal from a more distant TRP to be overwhelmed by a PRS signal from a closer TRP, making the signal from the more distant TRP undetectable. PRS silencing can be used to help reduce interference by silencing some PRS signals (reducing the power of the PRS signal, e.g., reducing it to zero and thus not transmitting the PRS signal). In this way, the UE can more easily detect the weaker PRS signal (at the UE) without the interference of the stronger PRS signal. The term RS and its variations (e.g., PRS, SRS, CSI-RS (Channel State Information - Reference Signal)) can refer to one or more reference signals.

[0094] The Positioning Reference Signal (PRS) comprises a downlink PRS (DL PRS, often simply referred to as PRS) and an uplink PRS (UL PRS) (the uplink PRS may be referred to as the SRS (Sound Reference Signal) used for positioning). The PRS may include PN codes (pseudo-random codes) or be generated using PN codes (e.g., by modulating a carrier signal with PN codes) so that the PRS source can be used as a pseudo-satellite. The PN code can be unique for the PRS source (at least unique within a specified region, such that the same PRS from different PRS sources does not overlap). The PRS may include PRS resources of a frequency layer and / or a set of PRS resources. The DL PRS positioning frequency layer (or simply frequency layer) is a collection of DL PRS resource sets from one or more TRPs, whose PRS resources have common parameters configured by the higher-level parameters DL-PRS-PositioningFrequencyLayer (DL-PRS-PositioningFrequencyLayer), DL-PRS-ResourceSet (DL-PRS-Resource Set), and DL-PRS-Resource (DL-PRS-Resource). Each frequency layer has a DL PRS subcarrier spacing (SCS) for the DL PRS resource set and DL PRS resources within that frequency layer. Each frequency layer also has a DL PRS cyclic prefix (CP) for the DL PRS resource set and DL PRS resources within that frequency layer. In 5G, a resource block occupies 12 consecutive subcarriers and a specified number of symbols. A shared resource block is a set of resource blocks that occupy the channel bandwidth. A bandwidth portion (BWP) is a set of consecutive shared resource blocks and may include all shared resource blocks within the channel bandwidth or a subset of those shared resource blocks. Furthermore, the DL PRS point A parameter defines the frequency of a reference resource block (and its lowest subcarrier), where DL PRS resources belonging to the same DL PRS resource set have the same point A, and all DL PRS resource sets belonging to the same frequency layer have the same point A. The frequency layers also have the same DL PRS bandwidth, the same starting PRB (and center frequency), and the same comb size value (i.e., the frequency of the PRS resource element per symbol, such that for comb-N, every Nth resource element is a PRS resource element). A PRS resource set is identified by a PRS resource set ID and can be associated with a specific TRP (identified by a cell ID) transmitted by the antenna panel of a base station. The PRS resource ID in a PRS resource set can be associated with an omnidirectional signal and / or with a single beam (and / or beam ID) transmitted from a single base station (where a base station can transmit one or more beams). Each PRS resource in a PRS resource set can be transmitted on a different beam, and thus, a PRS resource (or simply a resource) can also be referred to as a beam. There is no indication as to whether the base station and beam transmitting the PRS on it are known to the UE.

[0095] The TRP can be configured, for example, by instructions received from a server and / or by software within the TRP, to transmit DL PRS according to a schedule. Depending on this schedule, the TRP can transmit DL PRS intermittently (e.g., periodically at consistent intervals from the initial transmission). The TRP can be configured to transmit one or more PRS resource sets. A resource set is a collection of PRS resources spanning a TRP, wherein the resources have the same periodicity, a shared silent mode configuration (if any), and the same cross-slot repetition factor. Each PRS resource set comprises multiple PRS resources, wherein each PRS resource comprises multiple OFDM (Orthogonal Frequency Division Multiplexing) resource elements (REs), which may reside in multiple resource blocks (RBs) within N (or more) consecutive symbols in a time slot. PRS resources (or, in general, reference signal (RS) resources) may be referred to as OFDM PRS resources (or OFDMRS resources). An RB is a set of REs spanning a certain number of one or more consecutive symbols in the time domain and a certain number (12 for 5G RBs) of consecutive subcarriers in the frequency domain. Each PRS resource is configured using RE offset, slot offset, and symbol offset within a slot, as well as the number of consecutive symbols that a PRS resource can occupy within a slot. The RE offset defines the initial RE offset of the first symbol within a DL PRS resource in the frequency. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on the initial offset. The slot offset is the starting slot of the DL PRS resource relative to the corresponding resource set slot offset. The symbol offset determines the starting symbol of the DL PRS resource within the starting slot. Transmitted REs can be repeated across slots, with each transmission referred to as a repetition, allowing for multiple repetitions within a PRS resource. DL PRS resources in a DL PRS resource set are associated with the same TRP, and each DL PRS resource has a DL PRS resource ID. The DL PRS resource ID in a DL PRS resource set is associated with a single beam transmitted from a single TRP (although a TRP can transmit one or more beams).

[0096] PRS resources can also be defined by quasi-co-location parameters and starting PRB parameters. The quasi-co-location (QCL) parameter defines any quasi-co-location information of the DLPRS resource with other reference signals. The DL PRS can be configured to be of QCL type D with DL PRS or SS / PBCH (Synchronization Signal / Physical Broadcast Channel) blocks from the serving cell or non-serving cell. The DL PRS can be configured to be of QCL type C with SS / PBCH blocks from the serving cell or non-serving cell. The starting PRB parameter defines the starting PRB index of the DLPRS resource with respect to reference point A. This starting PRB index has a granularity of one PRB and can have a minimum value of 0 PRBs and a maximum value of 2176 PRBs.

[0097] A PRS resource set is a collection of PRS resources with the same periodicity, the same silent mode configuration (if any), and the same cross-slot repetition factor. Each time all repetitions of all PRS resources in a PRS resource set are configured to be transmitted is called an "instance". Therefore, an "instance" of a PRS resource set is a specified number of repetitions for each PRS resource and a specified number of PRS resources within the PRS resource set, such that the instance is complete once the specified number of repetitions has been transmitted for each of the specified number of PRS resources. An instance can also be referred to as an "opportunity". A DLPRS configuration, including DL PRS transmission scheduling, can be provided to the UE to facilitate (or even enable) the UE to measure DL PRS.

[0098] Multiple frequency layers of a PRS can be aggregated to provide an effective bandwidth greater than any bandwidth in the individual layers. Multiple frequency layers belonging to component carriers (which can be consecutive and / or separate) and satisfying criteria such as Quasi-Co-location (QCL) and having the same antenna port can be stitched together to provide a larger effective PRS bandwidth (for DL ​​PRS and UL PRS), thereby improving the accuracy of time of arrival measurements. Stitching involves combining PRS measurements on individual bandwidth segments into a unified fragment, such that the stitched PRS can be considered as taken from a single measurement. In the case of QCL, different frequency layers behave similarly, resulting in a larger effective bandwidth for PRS stitching. The larger effective bandwidth (which may be referred to as the bandwidth of the aggregated PRS or the frequency bandwidth of the aggregated PRS) provides better time-domain resolution (e.g., the resolution of TDOA). The aggregated PRS comprises a collection of PRS resources, and each PRS resource in the aggregated PRS may be referred to as a PRS component, and each PRS component may be transmitted on different component carriers, frequency bands, or frequency layers, or on different portions of the same frequency band.

[0099] RTT positioning is an active positioning technology because RTT uses positioning signals transmitted from the TRP to the UE and from the UE (participating in RTT positioning) to the TRP. The TRP can transmit DL-PRS signals received by the UE, and the UE can transmit SRS (Sound Reference Signal) signals received by multiple TRPs. The Sound Reference Signal may be referred to as SRS or SRS signal. In 5G multi-RTT, coordinated positioning can be used, where the UE transmits a single UL-SRS for positioning received by multiple TRPs, instead of transmitting a separate UL-SRS for positioning for each TRP. A participating TRP will typically search for UEs currently residing on that TRP (the served UE, where the TRP is the serving TRP) and also search for UEs residing on neighboring TRPs (neighbor UEs). A neighboring TRP can be a TRP of a single BTS (Broadband Transceiver Station) (e.g., gNB), or it can be a TRP of one BTS and a TRP of a single BTS. For RTT positioning (including multi-RTT positioning), the DL-PRS and UL-SRS positioning signals in the PRS / SRS positioning signal pair used to determine the RTT (and thus the range between the UE and TRP) may occur close to each other in time, so that the errors caused by UE movement and / or UE clock drift and / or TRP clock drift are within acceptable limits. For example, the signals in the PRS / SRS positioning signal pair may be transmitted from the TRP and the UE within approximately 10 ms of each other. In cases where the SRS for positioning is being transmitted by the UE and the PRS and the SRS for positioning are transmitted close to each other in time, it has been found that this may lead to radio frequency (RF) signal congestion (which may result in excessive noise, etc.) (especially if many UEs are concurrently attempting positioning), and / or may lead to computational congestion at the TRP where many UEs are concurrently attempting to measure.

[0100] RTT positioning can be UE-based or UE-assisted. In UE-based RTT, UE 200 determines the RTT and corresponding range to each TRP in TRP 300, and determines the location of UE 200 based on the range to TRP 300 and the known location of TRP 300. In UE-assisted RTT, UE 200 measures positioning signals and provides measurement information to TRP 300, and TRP 300 determines the RTT and range. TRP 300 provides the range to a location server (e.g., server 400), and the server determines the location of UE 200, for example, based on the range to different TRP 300s. RTT and / or range can be determined by TRP 300 receiving signals from UE 200, by TRP 300 in conjunction with one or more other devices (e.g., one or more other TRP 300s and / or server 400), or by one or more devices other than TRP 300 receiving signals from UE 200.

[0101] 5G NR supports various positioning technologies. NR-native positioning methods supported in 5G NR include DL-only positioning, UL-only positioning, and DL+UL positioning. Downlink-based positioning methods include DL-TDOA and DL-AoD. Uplink-based positioning methods include UL-TDOA and UL-AoA. Combined DL+UL positioning methods include RTT with one base station and RTT with multiple base stations (multi-RTT).

[0102] Location estimates (e.g., for a UE) may be referred to by other names, such as location estimation, location, positioning, fixed positioning, etc. Location estimates may be geodesic and include coordinates (e.g., latitude, longitude, and possible altitude), or they may be municipal and include street addresses, postal addresses, or some other textual description of the location. Location estimates may be further defined relative to another known location or (e.g., using latitude, longitude, and possible altitude) in absolute terms. Location estimates may include expected errors or uncertainties (e.g., by including areas or volumes that the location is expected to be included with a specified or default confidence level). Location information may include (e.g., one or more satellite signals, PRS, and / or one or more other signals) one or more location signal measurements, and / or one or more values ​​based on one or more location signal measurements (e.g., one or more distances (possibly including one or more pseudoranges), and / or one or more location estimates, etc.).

[0103] exist Figure 5The diagram below shows a system block diagram of a system 500 for selectively downloading HD maps to a mobile device 502. In this example, system 500 includes a mobile device 502, which may be located within or integrated into a vehicle-assisted transportation vehicle 504 (such as, for example, autonomous driving and driver-assisted transportation vehicles). In this example, system 500 may include at least one transceiver 506, at least one memory 508, and at least one processor 510 coupled to the at least one transceiver 506 and the at least one memory 508. The at least one memory 508 may include storage memory 512. In this example, at least one processor 510 may be configured to: store a previously stored HD map in storage memory 512, wherein the previously stored HD map includes a plurality of previously stored HD map tiles; receive an HD map tile set 514 from network entity 516 via at least one transceiver 506; update the previously stored HD map using the HD map tile set 514 to create an updated HD map; and store the updated HD map in storage memory 512; and send a response signal 518 to network entity 516 via at least one transceiver 506, wherein the response signal 518 corresponds to the received HD map tile set 514. In this example, network entity 516 may be, for example, an LMF (as previously described as LMF 120), a 5G core (as previously described as a 5G core 140 including LMF 120), and / or a server (as previously described as... Figure 4 The server 400 shown. Network entity 516 may be or include a map server that dynamically generates HD maps of spatial reference data from geographic information. In this example, the previously stored HD map may optionally be an initial HD map, which is stored in storage memory 512 as a first HD map stored in storage memory 512 when storage memory 512 is empty.

[0104] Generally, mobile device 502 may include and / or be referred to as a device, mobile device, wireless device, mobile terminal, terminal, MS, SUPL SET, or some other name. For example, mobile device 502 may be UE 105 or an integrated device within auxiliary vehicle 504 or auxiliary vehicle 502. In this example, mobile device 502 may optionally be preloaded with an initial HD map stored in storage memory 512, or the initial HD map may be downloaded from network entity 516 before receiving HD map tiles 514 to become a previously stored HD map. If the initial HD map is downloaded from network entity 516, at least one processor 510 is also configured to receive the initial HD map 528 from network entity 516 via at least one transceiver 506.

[0105] At least one transceiver 506 can signal-communicate with network entity 516 via RAN 520 and network 521. Network 521 can be any type of communication network, such as, for example, a telecommunications network for a wireless provider or the Internet. RAN 520 is coupled to at least one transceiver 506 and network entity 516 via signal paths 522 and 523, network 521, and signal path 524, respectively. In this example, RAN 520 can be, for example, a cellular base station communicating with a UE (including mobile device 502) within a first cellular coverage area. At least one transceiver 506 signal-communicates with RAN 520 via signal path 522, which serves as the UE-to-network radio interface. In this example, the UE-to-network radio interface can be, for example, a UMTS air interface (Uu), an LTE-Uu interface, a New Radio Uu interface (NR-Uu), or a similar type of radio interface.

[0106] Circuits, components, modules, and / or devices, or associated circuits, components, modules, and / or devices of mobile device 502, at least one transceiver 506, at least one memory 508, at least one processor 510, RAN 520, network entity 516, and another network entity 534 are described as signaling to each other, wherein signaling communication refers to any type of communication and / or connection between these circuits, components, modules, and / or devices that allows the circuits, components, modules, and / or devices to transmit and / or receive signals and / or information from another circuit, component, module, and / or device. This communication and / or connection can be along any signal path between these circuits, components, modules, and / or devices that allows signals and / or information to be transmitted from one circuit, component, module, and / or device to another, and includes wireless or wired signal paths. These signal paths can be physical, such as, for example, wires, electromagnetic waveguides, cables, attached and / or electromagnetically or mechanically coupled terminals, semiconductor or dielectric materials or devices, or other similar physical connections or couplings. Additionally, the signal path can be non-physical, such as free space (in the case of electromagnetic propagation) or an information path via digital components, where communication information can be transferred from one circuit, component, module, and / or device to another in different digital formats without the need for a direct electromagnetic connection.

[0107] Additionally, at least one processor 510 may be configured to store the HD map tile set 514 based on storage information 526 received together with the HD map tile set 514 from the network entity 516. The storage information 526 may include: information about how long the HD map tile set 514 will be stored in the storage memory 512; information about how far along the route the HD map tile set 514 will be stored in the storage memory 512; and a storage priority for storing each HD map tile in the HD map tile set 514.

[0108] At least one processor 510 may be configured to request, 530, an HD map tile set 514 from network entity 516 via at least one transceiver 506, wherein the request 530 includes map information corresponding to the initial HD map tiles. In this example, the map information may include an HD map tile index corresponding to the initial HD map tiles, the time when the HD map tile set 514 was received at mobile device 502, road segment identifiers along the route traveled along AV 504, and partition identifiers along the route. The map information may also include information about the regular route of AV 504, information about frequently accessed destinations of AV 504, and the available storage size of storage memory 512 for storing updated HD maps on storage memory 512.

[0109] The response signal 518 may include an acknowledgment message / signal for each HD map tile in the HD map tile set 514 that is received by the mobile device 502. In this example, at least one processor 510 may also be configured to receive the HD map tile set 514, wherein the HD map tile set 514 is encoded using an external code, and the response signal 518 may also include a negative acknowledgment for each HD map tile (in the HD map tile set 514) that is not received by the mobile device 502.

[0110] For example, system 500 may also optionally request a new set of HD map tiles from another network entity 534 via a sidelink channel through at least one transceiver 506. In this example, request 532 may include map information corresponding to a previously stored HD map stored in storage memory 512, and the other network entity 534 may be a roadside network device, another AV, or other similar network device capable of updating the HD map of mobile device 502.

[0111] Figure 6 It is shown Figure 5The diagram illustrates an example route 600 along a simplified map 602 for AV 504. In this example, route 600 begins at point A and ends at point B. For illustrative purposes, route 600 may begin in an urban area (i.e., area 604) and travel through different areas. For example, areas 606 and 612 may be open areas where signal reception from wireless base stations may be unobstructed. However, areas 604, 608, and 610 may have obstructed areas where wireless reception from base stations in these areas may be difficult / degraded. For example, area 604 may be an urban area with buildings, tunnels, bridges, and / or other structures that may interfere with the reception of HD map tiles. Area 604 may also have issues with available bandwidth capacity or interference with the wireless network, which may affect the ability to properly download HD map tiles. Areas 608 and 610 may also have wireless availability issues, as area 608 may be, for example, a forest, and area 610 may be a mountainous area. System 500 implements an enhanced method for downloading HD maps along route 600 of AV 504.

[0112] exist Figure 7 The image shows a system diagram for updating HD maps in mobile device 502. Similar to... Figure 5 ,exist Figure 7The image illustrates a mobile device 502 comprising at least one transceiver 506, at least one processor 510, and a storage memory 512. In this example, the storage memory 512 may be or include a database 700 (or storage buffer) for storing HD maps and associated HD map tiles. In an example of operation, at least one processor 510 determines whether a previously stored HD map (i.e., a previously stored HD map tile 704) stored in the database 700 should be updated. If the previously stored HD map tile 704 should be updated, at least one processor 510 may transmit a request 530 for HD map tile 514 to network entity 516 to update the previously stored HD map in the database 700. If the previously stored HD map tile 704 does not need to be updated, at least one processor 510 may continue to monitor the previously stored HD map tile 704 based on multiple criteria to determine whether any of the previously stored HD map tiles 704 should be updated at a later time. In this example, at least one processor 510 may determine that a previously stored HD map should be updated based on multiple criteria / factors, which may include, for example, the timeliness of the stored HD map tile 704, information from network entity 516 regarding how long the previously stored HD map tile 704 has been stored, and / or how far along route 600 the previously stored HD map tile 704 is stored. For example, sensors in AV 504 and / or mobile device 502 may determine that the environment and / or road conditions of route 600 do not correspond to the currently stored HD map tile 704; or AV 504 is about to make some kind of significant movement, such as changing from one lane to another.

[0113] If at least one processor 510 determines that the previously stored HD map tile 704 should be updated and a request 530 for HD map tile 514 has been transmitted to network entity 516 by at least one transceiver 506, then at least one processor 510 waits to receive HD map tile 514 via at least one transceiver 506. Once HD map tile 514 is received by at least one processor 510 via at least one transceiver 506, at least one processor 510 can determine 706 whether HD map tile 514 was correctly received by at least one transceiver 506. If HD map tile 514 was not correctly received, at least one processor 510 may optionally transmit a negative acknowledgment message 708 to network entity 516 as part of a response signal 518. Alternatively, if HD map tile 514 was correctly received, then if at least one processor 510 determines 702 that the HD map tile 704 should be updated (e.g., the HD map tile should be updated), then at least one processor 510 may store HD map tile 514 in database 700. In this example, at least one processor 510 may optionally transmit an acknowledgment message 710 to network entity 516 as part of a response signal 518. At least one processor 510 may also transmit map information 712 corresponding to a previously stored HD map tile 704 as part of a request 530. The map information 712 may be information related to a stored or previously updated initial HD map tile and previously stored HD map tiles 704 in database 700. In this example, map information 712 may include, for example, an HD map tile index corresponding to a stored or previously updated initial HD map tile and a previously stored HD map tile 704; the time when the HD map tile set 514 is received at the mobile device 502 via at least one transceiver 506; one or more road segment identifiers along route 600; one or more partition identifiers along route 600; the regular route of mobile device 502 and / or AV 504 along route 506; frequently visited destinations of mobile device 502 and / or AV 504 along route 600; and the available storage size on storage memory 512 for storing previously stored HD map tiles 704 and / or HD map tiles 514.

[0114] In this example, the initial HD map tiles stored in database 700 are HD map tiles that may have been loaded a priori to download any HD map tile 514. These initial HD map tiles may have been loaded into database 700 by, for example, a readable storage device (such as, for example, a Universal Serial Bus (USB) device, DVD media, flash memory media, or other types of portable storage devices). Alternatively, the initial HD map tiles may be loaded into database 700 by initially downloading an optional initial HD map 528 from network entity 516 before mobile device 502 / AV 504 begins on route 600. Thus, the previously stored HD map tile 704 may optionally be an initial HD map tile that was loaded a priori into database 700 via a readable storage device or downloaded as an optional initial HD map 528 via network entity 516; or it may be a stored HD map tile 514 that has been updated by HD map tile 514 and then stored in database 700 after the previously stored HD map tile 704 has been stored.

[0115] exist Figure 8 The diagram illustrates a system diagram of an example network entity 516 for selectively downloading HD maps from network entity 516 to mobile device 502. In this example, network entity 516 may include at least one transceiver 800, at least one memory 802, and at least one processor 804 coupled to the at least one transceiver 800 and the at least one memory 802. The at least one processor 804 may be configured to: receive a request 530 for a set of HD map tiles from mobile device 502 via the at least one transceiver 800, wherein the request 530 includes map information corresponding to an initial HD map having a plurality of initial HD map tiles; determine 806 the set of HD map tiles based on the map information; and send the set of HD map tiles 514 to mobile device 502 via the at least one transceiver 800.

[0116] In this example, network entity 516 can be configured to track the index and corresponding HD map tiles of HD map tiles 514 sent to mobile device 502. Network entity 516 can also be configured to track HD map tiles 514 sent at different times, because even for the same area or partition, HD maps can differ at different times due to the existence of real-time HD map portions. By tracking HD map tiles 514, network entity 516 possesses this recorded information, allowing it to determine which map tiles 504 and / or mobile device 502 already have based on past tile IDs in request message 530. Network entity 516 can then determine the differential portion to be sent, which reduces the transmission bandwidth used to send HD map information to mobile device 502.

[0117] At least one processor 804 may also be configured to receive a response signal 518 from the mobile device 502 via at least one transceiver 800, wherein the response signal 518 corresponds to an HD map tile set received 514 by the mobile device 502. At least one processor 804 may also be configured to send storage information 526 of the HD map tile set 514, wherein the storage information may include information about how long the HD map tile set 514 has been stored on the mobile device 502, and how far the AV 504 has traveled along route 600 before the HD map tile set 514 is stored on the mobile device 502. The storage information may also include a storage priority for storing each HD map tile in the HD map tile set 514.

[0118] As described above, the map information may include information corresponding to the HD map tile index corresponding to the initial HD map tile or HD map tile 514, the time when the HD map tile set 514 was received at the mobile device 502, road segment identification, and / or zone identification. The map information may also include the regular route of the mobile device 502 along route 600, frequently visited destinations of the mobile device 502, and / or the available storage size on the database 700 for storing previously stored HD map tiles 704 and / or HD map tiles 514.

[0119] In this example, the response signal 518 may include an acknowledgment message for each HD map tile in the HD map tile set 514 received by the mobile device 502. Additionally, at least one processor may also be configured to send the HD map tile set 514 encoded using an external code or network code to the mobile device 502. In this example, the response signal 518 may also include a negative acknowledgment message for each HD map tile 514 not received by the mobile device 502.

[0120] As described above, at least one processor 804 may also be configured to send an optional initial HD map 528 to the mobile device 502 via at least one transceiver 800 upon request from the mobile device 502.

[0121] Go to Figure 9A and Figure 9BThis diagram illustrates a system for transmitting HD map tiles 514 to more than one vehicle using external codes. In this example, the HD map tiles 514 are large, so for dense AV scenes (e.g., area A along route 600), an external decoding transmission scheme can be used as a resource-efficient way to transmit HD map tiles 514 for retransmission, utilizing the buffer available in storage memory 512 in AV 504. In this example, two AVs (i.e., first AV 900 and second AV 902) are shown traveling along route 600 in the same direction 903 through a dense AV scene, which may include buildings 904 and houses 906. First AV 900 and second AV 902 can communicate with signal RAN 908, which communicates with network entity 516.

[0122] For example, if network entity 516 transmits HD map tile 514 to RAN 908 for broadcast or unicast transmission to first AV 900 and second AV 902, but due to the problems described above, first AV 900 and second AV 902 only receive a portion of HD map tile 514, it will be necessary to retransmit HD map tile 514. Assume that first AV 900 only receives the first portion of the transmitted HD map tile 514 (denoted as transmission X). a And the second AV 902 only receives the second part of the transmission of HD map tile 514 (shown as transmission X). b If this happens, a retransmission will be required to provide the missing portion of HD map tile 514 to both AV 900 and AV 902. For simplicity, assume that AV 900 is missing the portion of HD map tile 514 that was sent with X. b The corresponding part, and the second AV 902 is missing the HD map tile 514 and the sending X. a The corresponding part.

[0123] exist Figure 9B The diagram illustrates the use of an external code to retransmit HD map tile 514. In this example, RAN 908 can send the missing portion of HD map tile 514 as an external code F(X). a X b The foreign code is retransmitted. In this example, the foreign code is a decoding technique that utilizes a cascaded decoding system. For example, the foreign code could utilize the XOR logic double-condition technique, where the logical operation is true only if its arguments differ (i.e., one is true and the other is false). Other types of foreign codes, such as erasure codes, could also be used.

[0124] As an example of simple signal erasure using erasure codes with external codes, a single parity check code can correct for an erasure in the transmitted data stream. If the input has three variables, such as... And the input is encoded as a vector. Then it is sent, so any single erase can be recorded using this code. In this example, the operation " " indicates an XOR operation. If the received vector is Then it can be achieved by summing the other elements sent (i.e. To recover the erased element, we can use a variable to restore the erased element, thus recovering element b. This can be described as a linear system on a Galois field with three variables and four linearly independent constraints, such that...

[0125] .

[0126] According to this relationship, any three constraints and one erase are sufficient to obtain these three variables.

[0127] In this example, to enable external code transmission, the first AV 900 and the second AV 902 should send an acknowledgment message back to network entity 516 as part of response signal 518. An acknowledgment message is required for each individual HD map tile sent to the first AV 900 and the second AV 902 because, in order to utilize the external code technology, network entity 516 needs to know which individual HD map tiles were successfully received by each AV. An optional negative acknowledgment message for anticipated HD map tiles that were not successfully received by each AV can also help network entity 516 determine which portions of HD map tile 514 should be retransmitted to the first AV 900 and the second AV 902. Additional fields can be used in the header of the acknowledgment message to indicate information about all transport blocks (TBs) in the external decoding packet. These fields may include, for example, transport block size (TBS), type 2 side link control information (SCI-2), packet identifier (ID) for distinguishing between packets, and the destination ID of the TB (where each TB has a destination receiver, and the destination receiver has an ID). This field can also include the total number of TBs, so that the decoder can decode each TB and know how many TBs should be decoded.

[0128] Go to Figure 10This diagram illustrates a system for downloading HD map tiles using sidelinks with other network entities. System 1000 may include network entity 1002, a first RAN 1004, a second RAN 1006, a first AV 1008, and a second AV 1010. In this example, the first AV 1008 and the second AV 1010 may travel along the same route 600. Network entity 1002 communicates signalically with both the first RAN 1004 and the second RAN 1006 via signal paths 1012 and 1014, respectively. For example, the first AV 1008 may be located in an out-of-coverage area at a first location 1016, and the second AV 1010 may be located in an in-coverage area at a second location 1018. When the first AV 1008 enters an out-of-coverage area, it may have lost radio signal 1020 from the first RAN 1004. Therefore, the first AV 1008 may broadcast a request 1022 to other surrounding network entities to download the required HD map tiles. In this example, the second AV 1010 is another network entity because it communicates with network entity 1002 via the second RAN 1006 and signal paths 1024 and 1014. Other examples of other network entities may include fixed roadside networking devices that communicate with network entity 1002. In this example, once the second AV 1010 receives a broadcast request 1022 from the first AV 1008, the second AV 1010 can initiate a security authentication process, and if acceptable, the second AV 1010 can establish a sidelink channel 1026 (unicast or broadcast) with the first AV 1008. Once the sidelink channel 1026 is established, the second AV 1010 can send the requested HD map tile 1028 to the first AV 1008. In this example, the broadcast request may include a message that includes the required HD map tile index, a segment ID along route 600, or a partition ID along route 600.

[0129] Figure 11 This is a flowchart of a method 1100 performed by system 500 for selectively downloading an HD map to mobile device 502. Method 1100 includes: receiving 1102 an HD map tile set 514 from network entity 516 via at least one transceiver 506; updating 1104 a previously stored HD map using the HD map tile set 514 to create an updated HD map; and storing 1106 the updated HD map in storage memory 512. Method 1100 may further include: sending a response signal 518 to network entity 516 via at least one transceiver 506, wherein the response signal 518 corresponds to the received HD map tile set 514.

[0130] In this example, storing the HD map tile set 514 may further include storing the HD map tile set 514 based on storage information 526 received together with the HD map tile set 514 from the network entity 516. As discussed above, the storage information 526 may include information about how long the HD map tile set 514 will be stored and how far along route 600 the HD map tile set 514 will be stored. The storage information 526 may include a storage priority for storing each HD map tile in the HD map tile set 514.

[0131] Method 1100 may further include: requesting, via at least one transceiver 506, a set of HD map tiles 514 from network entity 516, wherein request 530 includes map information 712 corresponding to the initial HD map tiles. As discussed above, map information 712 may include an HD map tile index corresponding to the initial HD map tiles, the time the HD map tile set was received at the mobile device, road segment identifiers, and zone identifiers. The map information may also include the regular route of the mobile device 502 along route 600, frequently visited destinations of the mobile device 502, and the available storage size on storage memory 512 for storing updated HD maps. In this example, response signal 518 may include an acknowledgment message for each HD map tile received by the mobile device 502 in the HD map tile set 514. Furthermore, receiving 1102 the HD map tile set 514 may include receiving the HD map tile set 514 encoded using an external code. (See below for details.) Figure 9A and Figure 9B As discussed, the response signal 518 may also include an optional negative acknowledgment for each HD map tile not received by the mobile device 502. Method 1100 may also optionally include receiving an initial HD map from network entity 516 via at least one transceiver 506. (See also: Regarding...) Figure 10 As discussed, method 1100 may further include: requesting a new set of HD map tiles 1028 from another network entity (e.g., second AV 1010) via a side link channel 1026 via at least one transceiver 506, the request 1022 including map information corresponding to the HD map.

[0132] Figure 12This is a flowchart of a method 1200 performed by network entity 516 for selectively downloading an HD map from network entity 516 to mobile device 502. Method 1200 includes: receiving a request 530 from mobile device 502 via at least one transceiver 800 for an HD map tile set 514, wherein the request 530 includes map information 712 corresponding to a previously stored HD map having a plurality of previously stored HD map tiles. Method 1200 further determines an HD map tile set 514 based on the map information 712, and sends the HD map tile set 514 to mobile device 502 via at least one transceiver 800.

[0133] In this example, method 1200 may further include receiving a response signal 518 from mobile device 502 via at least one transceiver 800, wherein the response signal 518 corresponds to an HD map tile set 514 received by mobile device 502. Sending 1204 the HD map tile set may include sending storage information about the HD map tile set 514, wherein, as discussed above, the storage information may include information about how long the HD map tile set 514 has been stored on mobile device 502 and how far away the HD map tile set 514 is stored on mobile device 502. The storage information may include a storage priority for storing each HD map tile in the HD map tile set 514. As discussed above, map information 712 may include an HD map tile index corresponding to previously stored HD map tiles, the time the HD map tile set was received at the mobile device, road segment identification, and zone identification. The map information may also include the regular route of mobile device 502 along route 600, frequently visited destinations of mobile device 502, and the available storage size on storage memory 512 for storing updated HD maps.

[0134] As discussed above, response signal 518 may include an acknowledgment message for each HD map tile in the HD map tile set 514 received by mobile device 502. Furthermore, sending 1206 the HD map tile set 514 may include sending the HD map tile set 514 encoded using an external code, and method 1200 may optionally include receiving response signal 518 having a negative acknowledgment for each HD map tile not received by mobile device 502. (See also: Regarding...) Figure 9A and Figure 9B As discussed, the response signal 518 may also include an optional negative acknowledgment for each HD map tile not received by the mobile device 502. Method 1200 may also optionally include sending an initial HD map to the mobile device 502 via at least one transceiver 800.

[0135] Specific implementation examples

[0136] Specific implementation examples are provided in the following numbered clauses.

[0137] Clause 1. A method for selectively downloading a high-definition (HD) map to a mobile device, the method comprising: receiving a set of HD map tiles from a network entity via at least one transceiver of the mobile device; updating a previously stored HD map using the set of HD map tiles to create an updated HD map having the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and storing the updated HD map in the storage memory.

[0138] Clause 2. The method according to Clause 1, wherein storing the updated HD map tile set further comprises storing the updated HD map tile set based on storage information received together with the HD map tile set from the network entity, and the storage information is selected from the group consisting of: information about how long the updated HD map tile set is stored, information about how far along the route traveled by the mobile device is the updated HD map tile set to be stored, and a storage priority for storing each updated HD map tile in the updated HD map tile set.

[0139] Clause 3. The method according to Clause 2, the method further comprising: sending from the mobile device via the at least one transceiver a request for the updated set of HD map tiles from the network entity, wherein the request includes map information corresponding to the plurality of previously stored HD map tiles.

[0140] Clause 4. The method according to Clause 3, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles, the time when the updated HD map tile set is sent to the mobile device, road segment identifiers, zone identifiers, the mobile device’s regular routes, frequently visited destinations of the mobile device, and the available storage size on at least one memory of the mobile device for storing the updated HD map.

[0141] Clause 5. The method according to Clause 1, the method further comprising: sending a response signal to the network entity via the at least one transceiver, wherein the response signal corresponds to the updated set of HD map tiles.

[0142] Clause 6. The method according to Clause 5, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

[0143] Clause 7. The method according to Clause 6, wherein receiving the HD map tile set includes receiving the HD map tile set encoded using an external code.

[0144] Clause 8. The method according to Clause 7, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

[0145] Clause 9. The method according to Clause 1, the method further comprising: receiving, via the at least one transceiver, the previously stored HD map from the network entity, wherein the previously stored HD map is an initial HD map.

[0146] Clause 10. The method according to Clause 1, further comprising: sending from the mobile device via the at least one transceiver, using a sidelink channel, a request for a new, updated set of HD map tiles from another network entity, wherein the request includes map information corresponding to the updated HD map.

[0147] Clause 11. A method for selectively transmitting a high-definition (HD) map from a network entity to a mobile device, the method comprising: receiving, at the network entity, a request from the mobile device for a set of HD map tiles, wherein the request includes map information corresponding to a previously stored HD map having a plurality of previously stored HD map tiles; determining, at the network entity, the set of HD map tiles based on the map information; and transmitting, from the network entity, the set of HD map tiles to the mobile device.

[0148] Clause 12. The method according to Clause 11, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles, the time when the HD map tile set is received at the mobile device, road segment identifiers, zone identifiers, the mobile device’s regular routes, frequently accessed destinations of the mobile device, and the available storage size on the mobile device for storing the HD map.

[0149] Clause 13. The method according to Clause 11, the method further comprising: receiving a response signal at the network entity from the mobile device, wherein the response signal corresponds to the set of HD map tiles sent to the mobile device.

[0150] Clause 14. The method according to Clause 13, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

[0151] Clause 15. The method according to Clause 14, wherein sending the HD map tile set includes sending the HD map tile set encoded using an external code to the mobile device.

[0152] Clause 16. The method according to Clause 15, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

[0153] Clause 17. The method according to Clause 11, the method further comprising: sending from the network entity the previously stored HD map from the network entity, wherein the previously stored HD map is an initial HD map.

[0154] Clause 18. The method according to Clause 11, wherein sending the HD map tile set includes sending storage information of the HD map tile set, and the storage information is selected from the group consisting of: information about how long the HD map tile set is stored on the mobile device, information about how far along the route traveled by the mobile device to store the HD map tile set, and the storage priority for storing each HD map tile in the HD map tile set.

[0155] Clause 19. An apparatus for selectively downloading high-definition (HD) maps to a mobile device, the apparatus comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor being in signal communication with the at least one transceiver and the at least one memory, the at least one processor being configured to: receive from the mobile device, via the at least one transceiver, a set of HD map tiles from a network entity; update a previously stored HD map using the set of HD map tiles to create an updated HD map with the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and store the updated HD map in the storage memory.

[0156] Clause 20. The apparatus of Clause 19, wherein the at least one processor is further configured to store the updated HD map tile set based on storage information received together with the HD map tile set from the network entity, and the storage information is selected from the group consisting of: information about how long to store the updated HD map tile set, information about how far along the route traveled by the mobile device to store the updated HD map tile set, and a storage priority for storing each updated HD map tile in the updated HD map tile set.

[0157] Clause 21. The apparatus according to Clause 20, wherein the at least one processor is further configured to request the set of HD map tiles from the network entity via the at least one transceiver from the mobile device, and the request includes map information corresponding to the plurality of previously stored HD map tiles.

[0158] Clause 22. The apparatus according to Clause 21, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles, the time when the updated HD map tile set is sent to the mobile device, road segment identifiers, zone identifiers, the mobile device’s regular routes, frequently visited destinations of the mobile device, and the available storage size on at least one memory of the mobile device for storing the updated HD map.

[0159] Clause 23. The apparatus according to Clause 19, wherein the at least one processor is further configured to send a response signal to the network entity via the at least one transceiver, and the response signal corresponds to the updated set of HD map tiles.

[0160] Clause 24. The apparatus according to Clause 23, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

[0161] Clause 25. The apparatus according to Clause 24, wherein the at least one processor is further configured to receive the set of HD map tiles encoded using an external code.

[0162] Clause 26. The apparatus of Clause 25, wherein the response signal further includes a negative acknowledgment for each HD map tile in the set that was not received by the mobile device.

[0163] Clause 27. The apparatus according to Clause 19, wherein the at least one processor is further configured to receive the previously stored HD map from the network entity via the at least one transceiver, and the previously stored HD map is an initial HD map.

[0164] Clause 28. The apparatus according to Clause 19, wherein the at least one processor is further configured to send a request from the mobile device via the at least one transceiver, using a sidelink channel, for a new set of HD map tiles from another network entity, and the request includes map information corresponding to the updated HD map.

[0165] Clause 29. A network entity for selectively downloading high-definition (HD) maps to a mobile device, the network entity comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor being in signal communication with the at least one transceiver and the at least one memory, the at least one processor being configured to: receive, at the network entity, a request from the mobile device for a set of HD map tiles, wherein the request includes map information corresponding to a previously stored HD map having a plurality of previously stored HD map tiles; determine, at the network entity, the set of HD map tiles based on the map information; and send, from the network entity, the set of HD map tiles to the mobile device.

[0166] Clause 30. The network entity as described in Clause 29, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles, the time when the HD map tile set was received at the mobile device, road segment identifiers, zone identifiers, the mobile device’s regular routes, the mobile device’s frequently accessed destinations, and the available storage size on the mobile device for storing the HD map.

[0167] Clause 31. The network entity as described in Clause 29, wherein the at least one processor is further configured to receive a response signal from the mobile device at the network entity, and the response signal corresponds to the set of HD map tiles sent to the mobile device.

[0168] Clause 32. The network entity as described in Clause 31, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

[0169] Clause 33. The network entity as described in Clause 32, wherein the at least one processor is further configured to send the set of HD map tiles encoded using an external code to the mobile device.

[0170] Clause 34. The network entity as described in Clause 33, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

[0171] Clause 35. The network entity as described in Clause 29, wherein the at least one processor is further configured to send from the network entity the previously stored HD map, wherein the previously stored HD map is an initial HD map.

[0172] Clause 36. The network entity as described in Clause 29, wherein the at least one processor is further configured to send storage information of the HD map tile set, and the storage information is selected from the group consisting of: information about how long the HD map tile set is stored on the mobile device, information about how far along the route traveled by the mobile device to store the HD map tile set, and the storage priority for storing each HD map tile in the HD map tile set.

[0173] Clause 37. An apparatus for selectively downloading a high-definition (HD) map to a mobile device, the apparatus comprising: components for receiving a set of HD map tiles from a network entity via at least one transceiver of the mobile device; components for updating a previously stored HD map using the set of HD map tiles to create an updated HD map having the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and components for storing the updated HD map in the storage memory.

[0174] Clause 38. The apparatus of Clause 37, wherein the component for storing the updated HD map tile set further includes storing the updated HD map tile set based on storage information received together with the HD map tile set from the network entity, and the storage information is selected from the group consisting of: information about how long the updated HD map tile set is stored, information about how far along the route traveled by the mobile device is the updated HD map tile set to be stored, and a storage priority for storing each updated HD map tile in the updated HD map tile set.

[0175] Clause 39. The apparatus according to Clause 38, the apparatus further comprising a component for transmitting from the mobile device via the at least one transceiver a request for the updated set of HD map tiles from the network entity, wherein the request includes map information corresponding to the plurality of previously stored HD map tiles.

[0176] Clause 40. The apparatus according to Clause 39, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles, the time when the updated HD map tile set is sent to the mobile device, road segment identifiers, zone identifiers, the mobile device’s regular routes, frequently visited destinations of the mobile device, and the available storage size on at least one memory of the mobile device for storing the updated HD map.

[0177] Clause 41. The apparatus according to Clause 37, the apparatus further comprising a component for transmitting a response signal to the network entity via the at least one transceiver, wherein the response signal corresponds to the updated set of HD map tiles.

[0178] Clause 42. The apparatus according to Clause 41, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

[0179] Clause 43. The apparatus according to Clause 42, wherein the component for receiving the HD map tile set includes a component for receiving the HD map tile set encoded using an external code.

[0180] Clause 44. The apparatus according to Clause 43, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

[0181] 45. The apparatus according to Clause 37, the apparatus further comprising a component for receiving the previously stored HD map from the network entity via the at least one transceiver, wherein the previously stored HD map is an initial HD map.

[0182] Clause 46. The apparatus according to Clause 37 further includes components for: transmitting, via the at least one transceiver, from the mobile device using a sidelink channel, a request for a new, updated set of HD map tiles from another network entity, wherein the request includes map information corresponding to the updated HD map.

[0183] Clause 47. A network entity for selectively transmitting high-definition (HD) maps from a network entity to a mobile device, the network entity comprising: means for receiving, at the network entity, a request for a set of HD map tiles from the mobile device, wherein the request includes map information corresponding to a previously stored HD map having a plurality of previously stored HD map tiles; means for determining, at the network entity, the set of HD map tiles based on the map information; and means for transmitting the set of HD map tiles from the network entity to the mobile device.

[0184] Clause 48. The network entity as described in Clause 47, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles, the time when the HD map tile set was received at the mobile device, road segment identifiers, zone identifiers, the mobile device’s regular routes, the mobile device’s frequently accessed destinations, and the available storage size on the mobile device for storing the HD map.

[0185] Clause 49. The network entity as described in Clause 47, the network entity further comprising means for receiving a response signal at the network entity from the mobile device, wherein the response signal corresponds to the set of HD map tiles sent to the mobile device.

[0186] Clause 50. The network entity as described in Clause 49, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

[0187] Clause 51. The network entity as described in Clause 50, wherein the component for transmitting the HD map tile set includes a component for transmitting the HD map tile set encoded using an external code to the mobile device.

[0188] Clause 52. The network entity as described in Clause 51, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

[0189] Clause 53. The network entity as described in Clause 47, the network entity further comprising a component for sending from the network entity the previously stored HD map, wherein the previously stored HD map is an initial HD map.

[0190] Clause 54. The network entity as described in Clause 47, wherein the component for transmitting the HD map tile set includes a component for transmitting storage information of the HD map tile set, and the storage information is selected from the group consisting of: information about how long the HD map tile set is stored on the mobile device, information about how far along the route traveled by the mobile device to store the HD map tile set, and the storage priority for storing each HD map tile in the HD map tile set.

[0191] Clause 55. A non-transitory processor-readable storage medium including processor-readable instructions configured to cause one or more processors of a mobile device to receive selectively downloaded high-definition (HD) maps from a network entity at the mobile device, the processor-readable instructions including: code for receiving a set of HD map tiles from the network entity via at least one transceiver of the mobile device; code for updating a previously stored HD map using the set of HD map tiles to create an updated HD map with the updated set of HD map tiles, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in a storage memory of the mobile device; and code for storing the updated HD map in the storage memory.

[0192] Clause 56. A non-transitory processor-readable storage medium including processor-readable instructions configured to cause one or more processors of a network entity to send selectively downloaded high-definition (HD) maps to a mobile device, the processor-readable instructions including: code for receiving, at the network entity, a request from the mobile device for a set of HD map tiles, wherein the request includes map information corresponding to a previously stored HD map having a plurality of previously stored HD map tiles; code for determining, at the network entity, the set of HD map tiles based on the map information; and code for sending the set of HD map tiles from the network entity to the mobile device.

[0193] Other examples and specific implementations fall within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software and computers, the functions described above can be implemented using software, hardware, firmware, hardwiring, or any combination thereof executed by a processor. Features implementing the functions can also be physically located in various locations, including various parts distributed such that the functions are implemented in different physical locations.

[0194] As used herein, the singular forms “a,” “an,” and “the” also include the plural forms, unless the context clearly indicates otherwise. Thus, references to a device in the singular form included in the claims (e.g., “device,” “the / said device”) include at least one of such devices (i.e., one or more) (e.g., “processor” includes at least one processor (e.g., one processor, two processors, etc.), “the / said processor” includes at least one processor, “memory” includes at least one memory, “the / said memory” includes at least one memory, etc.). The phrases “at least one” and “one or more” are used interchangeably, and such that the object referred to by “at least one” and the object referred to by “one or more” include embodiments having one referred object and embodiments having multiple referred objects. For example, “at least one processor” and “one or more processors” each include embodiments having one processor and embodiments having multiple processors.

[0195] As used herein, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0196] Furthermore, as used herein, the "or" (possibly followed by "at least one of" or "one or more of") used in the item enumeration indicates a disjunctive enumeration such that an enumeration of, for example, "at least one of A, B, or C," or an enumeration of "one or more of A, B, or C," or an enumeration of "A or B or C" represents A or B or C or AB (A and B) or AC (A and C) or BC (B and C) or ABC (i.e., A and B and C), or a combination having more than one feature (e.g., AA, AAB, ABBC, etc.). Therefore, a statement that an item (e.g., a processor) is configured to perform a function relating to at least one of A or B, or a statement that an item is configured to perform function A or function B, indicates that the item can be configured to perform a function relating to A, or can be configured to perform a function relating to B, or can be configured to perform a function relating to both A and B. For example, the phrase "a processor configured to measure at least one of A or B" or "a processor configured to measure A or measure B" means that the processor can be configured to measure A (and may or may not be configured to measure B), or can be configured to measure B (and may or may not be configured to measure A), or can be configured to measure both A and B (and can be configured to select which of A and B or measure both). Similarly, a description of a component for measuring at least one of A or B includes: a component for measuring A (which may or may not be able to measure B), or a component for measuring B (which may or may not be configured to measure A), or a component for measuring A and B (which may be able to select which of A and B or measure both). As another example, a description of an item (e.g., a processor) being configured to perform at least one of function X or function Y means that the item can be configured to perform function X, or can be configured to perform function Y, or can be configured to perform both functions X and Y. For example, the phrase "processor configured to measure at least one of X or Y" means that the processor can be configured to measure X (and may or may not be configured to measure Y), or can be configured to measure Y (and may or may not be configured to measure X), or can be configured to measure both X and Y (and can be configured to select which of X and Y or measure both).

[0197] As used herein, unless otherwise stated, a description of a function or operation as “based on” an item or condition means that the function or operation is based on the described item or condition and may be based on one or more items and / or conditions other than the described item or condition.

[0198] Substantial changes can be made depending on specific requirements. For example, custom hardware may be used, and / or specific elements may be implemented in the hardware, in software executed by the processor (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, may be employed. Unless otherwise specified, components shown in the figures and / or discussed herein that are connected or communicate with each other (functionally or otherwise) are communicatively coupled. That is, these components may be connected directly or indirectly to enable communication between them.

[0199] The systems and devices discussed above are examples. Various configurations may appropriately omit, substitute, or add various processes or components. For example, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of a configuration may be combined in a similar manner. Furthermore, technology is constantly evolving, and therefore many elements are examples and do not limit the scope of this disclosure or the claims.

[0200] A wireless communication system is a system in which communication is transmitted wirelessly between wireless communication devices, that is, through the propagation of electromagnetic waves and / or sound waves through the atmosphere rather than through wires or other physical connections. A wireless communication system (also called a wireless communication system or wireless communication network) may not transmit all communication wirelessly, but is configured to transmit at least some communication wirelessly. Furthermore, the term "wireless communication device" or similar terms do not require the device to be functionally exclusive or even primarily used for communication, do not require that communication using the wireless communication device be exclusive or even primarily wireless, and do not require that the device be a mobile device, but rather indicate that the device includes wireless communication capabilities (one-way or two-way), for example, including at least one radio component (each radio component being part of a transmitter, receiver, or transceiver) for wireless communication.

[0201] Specific details are provided in this description to offer a thorough understanding of the example configurations, including specific implementations. However, the configurations can be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring these configurations. The description herein provides example configurations and does not limit the scope, applicability, or configuration of the claims. Rather, the preceding description of the configurations provides a description for implementing the described techniques. Various changes can be made to the function and arrangement of the elements.

[0202] As used herein, the terms “processor-readable medium,” “machine-readable medium,” and “computer-readable medium” refer to any medium that participates in providing data that enables a machine to operate in a particular manner. Using a computing platform, various processor-readable media may involve providing instructions / code to a processor for execution, and / or may be used to store and / or carry such instructions / code (e.g., as signals). In many specific implementations, processor-readable media are physical and / or tangible storage media. Such media can take many forms, including but not limited to non-volatile and volatile media. Non-volatile media include, for example, optical discs and / or magnetic disks. Volatile media include, but are not limited to, dynamic memory.

[0203] Having described several example configurations, various modifications, alternative constructions, and equivalents can be used. For example, the above elements can be components of a larger system, where other rules may take precedence over or otherwise modify the application of this disclosure. Furthermore, several operations may be performed before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of the claims.

[0204] Unless otherwise indicated, the terms "about" and / or "approximately" as used herein when referring to measurable values ​​(such as quantities, durations of time, etc.) cover variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein. Similarly, unless otherwise indicated, the term "substantially" as used herein when referring to measurable values ​​(such as quantities, durations of time, physical properties (such as frequencies), etc.) also covers variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein.

[0205] A statement that a value exceeds (or is greater than or higher than) a first threshold is equivalent to a statement that a value meets or exceeds a second threshold slightly greater than the first threshold. For example, in the resolution of the computing system, the second threshold is one value higher than the first threshold. A statement that a value is less than the first threshold (or within or below the first threshold) is equivalent to a statement that a value is less than or equal to a second threshold slightly lower than the first threshold. For example, in the resolution of the computing system, the second threshold is one value lower than the first threshold.

Claims

1. A method for selectively downloading high-definition (HD) maps to a mobile device, the method comprising: Receive a set of HD map tiles from a network entity via at least one transceiver of the mobile device; The previously stored HD map is updated using the HD map tile set to create an updated HD map with the updated HD map tile set, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in the storage memory of the mobile device. as well as The updated HD map is stored in the storage memory.

2. The method according to claim 1, wherein Storing the updated HD map tile set further includes storing the updated HD map tile set based on storage information received together from the network entity and the HD map tile set, and The stored information is selected from the following group: Information regarding how long the updated HD map tile set is stored. Information regarding the distance along the route traveled by the mobile device to store the updated set of HD map tiles, and Storage priority for storing each updated HD map tile in the updated HD map tile set.

3. The method according to claim 2, further comprising: The mobile device sends a request for the updated HD map tile set from the network entity via the at least one transceiver. The request includes map information corresponding to the plurality of previously stored HD map tiles.

4. The method according to claim 3, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles. The updated HD map tile set is sent to the mobile device at the time specified. Road signs Partition identifier, The mobile device's usual route, The frequently accessed destinations of the mobile device, and Available storage size on at least one memory of the mobile device for storing the updated HD map.

5. The method according to claim 1, further comprising: A response signal is sent to the network entity via the at least one transceiver, wherein the response signal corresponds to the updated set of HD map tiles.

6. The method of claim 5, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

7. The method of claim 6, wherein receiving the HD map tile set includes receiving the HD map tile set encoded using an external code.

8. The method of claim 7, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

9. The method according to claim 1, further comprising: The previously stored HD map is received from the network entity via the at least one transceiver, wherein the previously stored HD map is the initial HD map.

10. The method according to claim 1, further comprising: The mobile device sends a request for a new, updated set of HD map tiles from another network entity via the at least one transceiver using a sidelink channel. The request includes map information corresponding to the updated HD map.

11. A method for selectively transmitting high-definition (HD) maps from network entities to mobile devices, the method comprising: The network entity receives a request from the mobile device for a set of HD map tiles, wherein the request includes map information corresponding to a previously stored HD map having multiple previously stored HD map tiles. The HD map tile set is determined at the network entity based on the map information; as well as The HD map tile set is sent from the network entity to the mobile device.

12. The method of claim 11, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles. The time when the HD map tile set is received on the mobile device. Road signs Partition identifier, The mobile device's usual route, The frequently accessed destinations of the mobile device, and Available storage size on the mobile device for storing the HD map.

13. The method according to claim 11, further comprising: Receive a response signal from the mobile device at the network entity. The response signal corresponds to the set of HD map tiles sent to the mobile device.

14. The method of claim 13, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

15. The method of claim 14, wherein sending the HD map tile set comprises sending the HD map tile set encoded using an external code to the mobile device.

16. The method of claim 15, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

17. The method according to claim 11, further comprising: Send the previously stored HD map from the network entity, wherein the previously stored HD map is the initial HD map.

18. The method of claim 11, wherein Sending the HD map tile set includes sending the storage information of the HD map tile set, and The stored information is selected from the following group: Information regarding how long the HD map tile set is stored on the mobile device. Information regarding the distance along the route traveled by the mobile device to store the HD map tile set, and This is used to store the storage priority of each HD map tile in the HD map tile set.

19. An apparatus for selectively downloading high-definition (HD) maps to a mobile device, the apparatus comprising: At least one transceiver; At least one memory; and At least one processor, which communicates with the at least one transceiver and the at least one memory signal, is configured to: Receive a set of HD map tiles from a network entity from the mobile device via the at least one transceiver; The previously stored HD map is updated using the HD map tile set to create an updated HD map with the updated HD map tile set, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in the storage memory of the mobile device. as well as The updated HD map is stored in the storage memory.

20. The apparatus of claim 19, wherein The at least one processor is further configured to store the updated HD map tile set based on storage information received together from the network entity and the HD map tile set, and The stored information is selected from the following group: Information regarding how long the updated HD map tile set is stored. Information regarding the distance along the route traveled by the mobile device to store the updated set of HD map tiles, and Storage priority for storing each updated HD map tile in the updated HD map tile set.

21. The apparatus of claim 20, wherein The at least one processor is also configured to request the set of HD map tiles from the network entity from the mobile device via the at least one transceiver, and The request includes map information corresponding to the plurality of previously stored HD map tiles.

22. The apparatus of claim 21, wherein the map information is selected from the group consisting of: HD map tile indexes corresponding to the plurality of previously stored HD map tiles. The updated HD map tile set is sent to the mobile device at the time specified. Road signs Partition identifier, The mobile device's usual route, The frequently accessed destinations of the mobile device, and Available storage size on at least one memory of the mobile device for storing the updated HD map.

23. The apparatus of claim 19, wherein The at least one processor is also configured to send a response signal to the network entity via the at least one transceiver, and The response signal corresponds to the updated set of HD map tiles.

24. The apparatus of claim 23, wherein the response signal includes an acknowledgment for each HD map tile in the HD map tile set received by the mobile device.

25. The apparatus of claim 24, wherein the at least one processor is further configured to receive the set of HD map tiles encoded using an external code.

26. The apparatus of claim 25, wherein the response signal further includes a negative acknowledgment for each HD map tile in the HD map tile set that was not received by the mobile device.

27. The apparatus of claim 19, wherein The at least one processor is also configured to receive the previously stored HD map from the network entity via the at least one transceiver, and The previously stored HD map is the initial HD map.

28. The apparatus of claim 19, wherein The at least one processor is also configured to send a request from the mobile device via the at least one transceiver, using a sidelink channel, for a new set of HD map tiles from another network entity. The request includes map information corresponding to the updated HD map.

29. An apparatus for selectively downloading high-definition (HD) maps to a mobile device, the apparatus comprising: Components for receiving a set of HD map tiles from a network entity via at least one transceiver of the mobile device; A component for updating a previously stored HD map using the HD map tile set to create an updated HD map with an updated HD map tile set, wherein the previously stored HD map includes a plurality of previously stored HD map tiles stored in the storage memory of the mobile device. and Components for storing the updated HD map in the storage memory.

30. The apparatus of claim 29, wherein The component for storing the updated HD map tile set further includes storing the updated HD map tile set based on storage information received together with the HD map tile set from the network entity, and The stored information is selected from the following group: Information regarding how long the updated HD map tile set is stored. Information regarding the distance along the route traveled by the mobile device to store the updated set of HD map tiles, and Storage priority for storing each updated HD map tile in the updated HD map tile set.

Images