Enhancements to reliability of maps with c-v2x system

Abstract

Aspects presented herein may enable a first UE that specifies map data or a map data update to receive the map data or the map data update from at least one second UE when the first UE is unable to obtain the map data or the map data update directly from a server. In one aspect, a first UE detects a connection outage between the first UE and a map server. The first UE broadcasts a map data request that includes map version information of first map data used by the first UE and at least one ROI based on the detection of the connection outage. The first UE receives, from at least one second UE based on the map data request, second map data that includes the at least one ROI.

Description

ENHANCEMENTS TO RELIABILITY OF MAPS WITH C-V2X SYSTEMCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of India Provisional Application Serial No. 202341077295, entitled “ENHANCEMENTS TO RELIABILITY OF MAPS WITH C-V2X SYSTEM’ and filed on November 13, 2023, which is expressly incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to communication systems, and more particularly, to wireless communication involving cellular vehicle-to-everything (C- V2X) communication.INTRODUCTION

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latencycommunications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.BRIEF SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus detects a connection outage between a first user equipment (UE) and a map server. The apparatus broadcasts a map data request that includes map version information of first map data used by the first UE and at least one region of interest (ROI) based on the detection of the connection outage. The apparatus receives, from at least one second UE based on the map data request, second map data that includes the at least one ROI.

[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one ROI. The apparatus verifies, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI. The apparatus transmits, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI.

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0010] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

[0011] FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.

[0012] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0013] FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.

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

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

[0016] FIG. 5 is a diagram illustrating an example of sidelink communication between devices.

[0017] FIG. 6 is a diagram illustrating an example of a vehicle performing map over the air in accordance with various aspects of the present disclosure.

[0018] FIG. 7 is a flowchart illustrating an example of a first UE obtaining map data or a map data update from a second UE when the network communication is not available in accordance with various aspects of the present disclosure.

[0019] FIG. 8 is a communication flow illustrating an example of a UE requesting map data or a map data update from multiple UEs when the network communication is not available in accordance with various aspects of the present disclosure.

[0020] FIG. 9 is a flowchart of a method of wireless communication.

[0021] FIG. 10 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity.

[0022] FIG. 11 is a flowchart of a method of wireless communication.

[0023] FIG. 12 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity.DETAILED DESCRIPTION

[0024] Aspects presented herein may improve the reliability and latency of map data update, thereby improving the performance of applications and devices that use map data (e.g., autonomous driving vehicles, navigation applications, etc.). Aspects presented herein may enable a vehicle (e.g., a UE, a vehicle user equipment (UE), an on-board unit (OBU) of the vehicle, etc.) to dynamically update maps (or map data) in a connected UE / vehicle environment. For example, in one aspect of the present disclosure, a vehicle may be implemented with an algorithm that utilizes cellular vehicle-to-everything (C-V2X) communication technology to obtain real-time map updates from other nearby C-V2X-enabled vehicles, such as during network communication blackout or system specific / network issues. Aspects presented herein may ensure that the map data of a vehicle is able to remain up-to-date and free from stale or outdated information, even in situations where the primary source of communication for map over-the-air (MOTA) updates is unavailable (e.g., receiving the updates directly from a network / map server).

[0025] Aspects presented herein are directed to techniques / protocols for high-definition (HD) maps update in the event of network outage or other network issues that prevent the vehicles from obtaining HD maps updates timely. Aspects presented herein include proposals that utilize C-V2X communication to obtain map updates from nearby C- V2X-enabled vehicles. The target vehicle detects network issues and broadcasts map update request to nearby vehicles including its current map version information. The other vehicles will check to see whether there are updates that can be provided to the target vehicle.

[0026] The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

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

[0028] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

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

[0030] While aspects, implementations, and / or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and / or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and / or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip- level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders / summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

[0031] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmission reception point(TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

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

[0033] Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O- RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0034] FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework 105, or both). A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an Fl interface. The DUs 130 may communicate with one ormore RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.

[0035] Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near- RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0036] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an El interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.

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

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

[0039] The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non- virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 andNear-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O- eNB) 111, via an 01 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an 01interface. The SMO Framework 105 also may include aNon-RT RIC 115 configured to support functionality of the SMO Framework 105.

[0040] The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (Al) / machine learning (ML) (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near- RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.

[0041] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0042] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and / or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between theRUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple- input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. The base station 102 / UEs 104 may use spectrum up to X MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Ex MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respectto DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

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

[0044] The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0045] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) andFR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referredto (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0046] The frequencies between FR1 and FR2 are often referredto as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into midband frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0047] With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

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

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

[0050] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determinethe position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and / or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position / location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle- of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0051] Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as loT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and / or individually access the network.

[0052] Referring again to FIG. 1, in certain aspects, the UE 104 may have a map update component 198 that may be configured to detect a connection outage between the first UE and a map server; broadcast a map data request that includes map version information of first map data used by the first UE and at least one ROI based on thedetection of the connection outage; and receive, from at least one second UE based on the map data request, second map data that includes the at least one ROI. In certain aspects, the map update component 198 may also be configured to receive, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one ROI; verify, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI; and transmit, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI. In certain aspects, the base station 102 or the one or more location servers 168 may have a sidelink communication configuration component 199 that may be configured to provide configurations and / or parameters related to sidelink / C- V2X communication or map data update for the UE 104.

[0053] FIG. 2 A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi- statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD.

[0054] FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP -OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may scale with 1 / SCS.Table 1: Numerology, SCS, and CP

[0055] For normal CP (14 symbols / slot), different numerologies p 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology p, there are 14 symbols / slot and 2^ slots / subframe. The subcarrier spacing may be equal to 2^ * 15 kHz , where g is the numerology 0 to 4. As such, the numerology p=0 has a subcarrier spacing of 15 kHz and the numerology p=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGs.2A-2D provide an example of normal CP with 14 symbols per slot and numerology p=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended).

[0056] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0058] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determinethe locations of the DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.

[0059] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequencydependent scheduling on the UL.

[0060] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and / or negative ACK (NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0061] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control(MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

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

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

[0064] The controller / processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0065] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrityprotection, integrity verification); RLC layer functionality associated with the transfer ofupper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate anRF carrier with a respective spatial stream for transmission.

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

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

[0069] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in connection with the map update component 198 of FIG. 1.

[0070] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects in connection with the side link communication configuration component 199 of FIG. 1.

[0071] FIG. 4 is a diagram 400 illustrating an example of aUE positioning based on reference signal measurements (which may also be referred to as “network-based positioning”)in accordance with various aspects of the present disclosure. The UE 404 may transmit UL SRS 412 at time TSRS_TX and receive DL positioning reference signals (PRS) (DL PRS) 410 at time TPRS RX- The TRP 406 may receive the UL SRS 412 at time TSRS RX and transmit the DL PRS 410 at time TpRSTX- The UE 404 may receive the DL PRS 410 before transmitting the UL SRS 412, or may transmit the UL SRS 412 before receiving the DL PRS 410. In both cases, a positioning server (e.g., location server(s) 168) or the UE 404 may determine the RTT 414 based on ||TSRS _RX - TPRSTX| - ITSRS _TX — TPRS _RX||. Accordingly, multi-RTT positioning may make use of the UE Rx-Tx time difference measurements (i.e., |TSRS_TX - TPRS RXI) and DL PRS reference signal received power (RSRP) (DL PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 and measured by the UE 404, and the measured TRP Rx-Tx time difference measurements (i.e., |TSRS_RX - TPRSTX|) and UL SRS-RSRP at multiple TRPs 402, 406 of uplink signals transmitted from UE 404. The UE 404 measures the UE Rx-Tx time difference measurements (and / or DL PRS-RSRP of the received signals) using assistance data received from the positioning server, and the TRPs 402, 406 measure the gNB Rx-Tx time difference measurements (and / or UL SRS-RSRP of the received signals) using assistance data received from the positioning server. The measurements may be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the location of the UE 404. Other methods are possible for determining the RTT, such as for example using DL-TDOA and / or UL-TDOA measurements.

[0072] PRSs may be defined for network-based positioning (e.g., NR positioning) to enable UEs to detect and measure more neighbor transmission and reception points (TRPs), where multiple configurations are supported to enable a variety of deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). To support PRS beam operation, beam sweeping may also be configured for PRS. The UL positioning reference signal may be based on sounding reference signals (SRSs) with enhancements / adjustments for positioning purposes. In some examples, UL-PRS may be referred to as “SRS for positioning,” and a new Information Element (IE) may be configured for SRS for positioning in RRC signaling.

[0073] DL PRS-RSRP may be defined as the linear average over the power contributions (in [W]) of the resource elements of the antenna port(s) that carry DL PRS reference signals configured for RSRP measurements within the considered measurementfrequency bandwidth. In some examples, for FR1, the reference point for the DL PRS- RSRP may be the antenna connector of the UE. For FR2, DL PRS-RSRP may be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For FR1 and FR2, if receiver diversity is in use by the UE, the reported DL PRS-RSRP value may not be lower than the corresponding DL PRS- RSRP of any of the individual receiver branches. Similarly, UL SRS-RSRP may be defined as linear average of the power contributions (in [W]) of the resource elements carrying sounding reference signals (SRS). UL SRS-RSRP may be measured over the configured resource elements within the considered measurement frequency bandwidth in the configured measurement time occasions. In some examples, for FR1, the reference point for the UL SRS-RSRP may be the antenna connector of the base station (e.g., gNB). For FR2, UL SRS-RSRP may be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For FR1 and FR2, if receiver diversity is in use by the base station, the reported UL SRS- RSRP value may not be lower than the corresponding UL SRS-RSRP of any of the individual receiver branches.

[0074] PRS-path RSRP (PRS-RSRPP) may be defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry DL PRS signal configured for the measurement, where DL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time. In some examples, PRS path Phase measurement may refer to the phase associated with an i- th path of the channel derived using a PRS resource.

[0075] DL-AoD positioning may make use of the measured DL PRS-RSRP of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL PRS-RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with the azimuth angle of departure (A-AoD), the zenith angle of departure (Z-AoD), and other configuration information to locate the UE 404 in relation to the neighboring TRPs 402, 406.

[0076] DL-TDOA positioning may make use of the DL reference signal time difference (RSTD) (and / or DL PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL RSTD (and / or DL PRS-RSRP) of the received signals using assistance data received from the positioning server, andthe resulting measurements are used along with other configuration information to locate the UE 404 in relation to the neighboring TRPs 402, 406.

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

[0078] UL-AoA positioning may make use of the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) at multiple TRPs 402, 406 of uplink signals transmitted from the UE 404. The TRPs 402, 406 measure the A-AoA and the Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE 404. For purposes of the present disclosure, a positioning operation in which measurements are provided by a UE to a base station / positioning entity / server to be used in the computation of the UE’s position may be described as “UE-assisted,” “UE-assisted positioning,” and / or “UE-assisted position calculation,” while a positioning operation in which a UE measures and computes its own position may be described as“UE-based,” “UE-based positioning,” and / or “UE-based position calculation.”

[0079] Additional positioning methods may be used for estimating the location of the UE 404, such as for example, UE-side UL-AoD and / or DL-AoA. Note that data / measurements from various technologies may be combined in various ways to increase accuracy, to determine and / or to enhance certainty, to supplement / complement measurements, and / or to substitute / provide for missing information.

[0080] Note that the terms “positioning reference signal” and “PRS” generally refer to specific reference signals that are used for positioning in NR and LTE systems. However, as used herein, the terms “positioning reference signal” and “PRS” may also refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS as defined in LTE and NR, TRS, PTRS, CRS, CSLRS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. In addition, the terms “positioning reference signal” and “PRS” may refer to downlink or uplink positioning reference signals,unless otherwise indicated by the context. To further distinguish the type of PRS, a downlink positioning reference signal may be referred to as a “DL PRS,” and an uplink positioning reference signal (e.g., an SRS-for-positioning, PTRS) may be referred to as an “UL-PRS.” In addition, for signals that may be transmitted in both the uplink and downlink (e.g., DMRS, PTRS), the signals may be prepended with “UL” or “DL” to distinguish the direction. For example, “UL-DMRS” may be differentiated from “DL-DMRS.” In addition, the term “location” and “position” may be used interchangeably throughout the specification, which may refer to a particular geographical or a relative place.

[0081] FIG. 5 illustrates an example 500 of sidelink communication between devices. The communication may be based on a slot structure similar to aspects described in connection with FIGs. 2A to 2D. For example, a UE 502 may transmit a sidelink (SL) transmission 514, e.g., including a control channel (e.g., a physical sidelink control channel (PSCCH)) and / or a corresponding data channel (e.g., a physical sidelink shared channel (PSSCH)), that may be received by UEs 504, 506, and 508. A control channel may include information (e.g., sidelink control information (SCI)) for decoding a data channel including reservation information, such as information about time and / or frequency resources that are reserved for the data channel transmission. For example, the SCI may indicate a number of transmission time intervals (TTIs), as well as the resource blocks (RBs) that may be occupied by the data transmission. The SCI may be used by receiving devices to avoid interference by refraining from transmitting on the reserved resources. The UEs 502, 504, 506, and 508 may each be capable of sidelink transmission in addition to sidelink reception. Thus, UEs 504, 506, and 508 are illustrated as transmitting sidelink transmissions 513, 515, 516, and 520. The sidelink transmissions 513, 514, 515, 516, and 520 may be unicast, broadcast, or multicast to nearby devices. For example, UE504 may transmit sidelink transmissions 513 and 515 intended for receipt by other UEs within a range 501 of UE 504, and UE 506 may transmit sidelink transmission 516 to a specified UE. Additionally, or alternatively, a roadside unit (RSU) 507 may be configured to receive communication from and / or transmit communication 518 to UEs 502, 504, 506, and 508.

[0082] Sidelink communication may be based on one or more transmission modes. In one transmission mode for a first radio access technologies (RAT) (which may be referred to herein as "Mode 4" of a first RAT), a wireless device may autonomously selectresources for transmission. A network entity may allocate one or more sub-channels for wireless devices to transmit one or more transport blocks (TB) using the one or more channels. A wireless device may randomly reserve an allocated resource for one-shot transmissions. A wireless device may use a sensing-based semi-persistent transmission scheme, or semi-persistent scheduling (SPS) mode, to select a reserved resource for transmission. For example, before selecting a resource for data transmission, a wireless device may first determine whether resources have been reserved by another wireless device. Semi-persistent transmission allows a wireless device to take advantage of semi-periodic traffic arrival by using historical interference patterns to predict future interference patterns. The wireless device may sense at least one of priority information, energy sensing information, or PSCCH decoding information to optimize resource selection. In one aspect, a wireless device may avoid selecting resources for a transmission that are scheduled to be used for a higher priority packet transmission. In another aspect, a wireless device may rank resources according to how much energy is received, and may pick the lowest energy resources. In another aspect, a wireless device may avoid resources for whom control is decoded or for which the received energy may be above a threshold.

[0083] A network entity may configure the periodicity of the reserved sub-channels using DCI transmitted over a PDCCH. The period of a semi-persistent transmission resource may be, for example, 20, 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, or 1000 milliseconds (ms). Such a periodicity may be referred to as a resource reservation period (RSVP). In alternative embodiments, the periodicity may be referred to as a resource reservation interval (RRI). A network entity may limit the possible values for the periodicity of the transmission resource. A wireless device, such as a UE, may select a transmission resource based on the periodicity of an arrival packet. A counter may be used to trigger periodic reselections. For example, a wireless device may randomly select a counter between 5 and 15, and may reserve a resource based on the counter (e.g., 10 * counter resource reservation periods, a number of medium access control (MAC) protocol data unit (PDU) transmissions equal to the counter). After every transmission, or after a reservation period passes, the counter may be decremented until it hits zero. For example, where a reservation period is 100 ms and a counter is 10, every 100 ms the counter may decrement until one second (s) passes, upon which the wireless device may then reselect a sidelink resource. In oneaspect, the wireless device may reselect the sidelink resource based on a re-selection probability value. For example, in response to the counter decrementing to zero, the wireless device may reselect the sidelink resource an x% of the time, and may not reselect the sidelink resource (l-x)% of the time, where x < 1. The wireless device may then resetthe counter and repeat the process when the counter decrements to zero again. A wireless device may measure a received signal strength indicator (RSSI) measurement for each slot of 100 ms, and may then calculate the RSSI of the frequency band resource as an average of each of the 10 RSSI measurements taken over the period of one second. A wireless device may select a suitable frequency band resource as a resource that is in one of the bottom 20% of ranked RSSI calculated resources for a wireless device. In some aspects, the counter may be decremented after every MAC PDU transmission. A wireless device may be configured to reselect a sidelink resource after a counter expires (i.e., reaches zero), and a MAC PDU is received.

[0084] Sidelink communication for other RATs may be based on different types or modes of resource allocation mechanisms. In another resource allocation mode for a second RAT (which may be referred to herein as 'Mode 1" of a second RAT), centralized resource allocation may be provided by a network entity. For example, a network entity may determine resources for sidelink communication and may allocate resources to different wireless devices to use for sidelink transmissions. In this first mode, a wireless device may receive an allocation of sidelink resources from a base station or a network entity. In a second resource allocation mode (which may be referred to herein as "Mode 2"), distributed resource allocation may be provided. In Mode 2, each wireless device may autonomously determine resources to use for sidelink transmission. In order to coordinate the selection of sidelink resources by individual wireless devices, each wireless device may use a sensing technique to monitor for resource reservations by other sidelink wireless devices and may select resources for sidelink transmissions from unreserved resources. Devices communicating based on sidelink, may determine one or more radio resources in the time and frequency domain that are used by other devices in order to select transmission resources that avoid collisions with other devices.

[0085] The sidelink transmission and / or the resource reservation may be periodic or aperiodic, where a wireless device may reserve resources for transmission in a current slot and up to two future slots (discussed below).

[0086] Thus, in the second mode (e.g., Mode 2), individual wireless devices may autonomously select resources for sidelink transmission, e.g., without a central entity such as a base station indicating the resources for the device. A first wireless device may reserve the selected resources in order to inform other wireless devices about the resources that the first wireless device intends to use for sidelink transmission(s).

[0087] In some examples, the resource selection for sidelink communication may be based on a sensing-based mechanism. For instance, before selecting a resource for a data transmission, a wireless device may previously determine whether resources have been reserved by other wireless devices.

[0088] For example, as part of a sensing mechanism for a resource allocation mode 2 of a second RAT, a wireless device may determine (e.g., sense) whether a selected sidelink resource has been reserved by other wireless device(s) before selecting a sidelink resource for a data transmission. If the wireless device determines that the sidelink resource has not been reserved by other wireless devices, the wireless device may use the selected sidelink resource for transmitting the data, e.g., in a PSSCH transmission. The wireless device may estimate or determine which radio resources (e.g., sidelink resources) may be in-use and / or reserved by others by detecting and decoding SCI transmitted by other wireless devices. The wireless device may use a sensing-based resource selection algorithm to estimate or determine which radio resources are in- use and / or reserved by others. The wireless device may receive SCI from another wireless device that may include reservation information based on a resource reservation field in the SCI. The wireless device may continuously monitor for (e.g., sense) and decode SCI from peer wireless devices. The SCI may include reservation information, e.g., indicating slots and RBs that a particular wireless device has selected for a future transmission. The wireless device may exclude resources that are used and / or reserved by other wireless devices from a set of candidate resources for sidelink transmission by the wireless device, and the wireless device may select / reserve resources for a sidelink transmission from the resources that are unused and therefore form the set of candidate resources. A wireless device may continuously perform sensing for SCI with resource reservations in order to maintain a set ofcandidate resources from which the wireless device may select one or more resources for a sidelink transmission. Once the wireless device selects a candidate resource, the wireless device may transmit SCI indicating its own reservation of the resource for a sidelink transmission. The number of resources (e.g., sub-channels per subframe) reserved by the wireless device may depend on the size of data to be transmitted by the wireless device. Although the example is described for a wireless device receiving reservations from another wireless device, the reservations may be received from an RSU or other device communicating based on sidelink.

[0089] In some examples, communications from a vehicle to one or more entities within a range of the vehicle (typically via sidelink (SL) or a mobile network) may be referred to as a vehicle-to-everything (V2X) or cellular vehicle-to-everything (C-V2X) communication or technology. For example, V2X / C-V2X communication or technology may include sensors, cameras, and / or wireless connectivity that enable vehicles (e.g., UEs 502, 504, 506, 508, etc.) to share real-time information with their drivers, other vehicles, cyclists, pedestrians, vulnerable road users (VRUs), mobile networks, and / or roadway infrastructure like roadside units (RSUs) and traffic lights, etc. In addition, C-V2X may utilize available networks (e.g., PC5 channels)) to establish direct and / or indirect communication links, allowing vehicles to exchange information in real-time. In some implementations, C-V2X may operate in two modes: a vehicle-to-vehicle (V2V) mode and a vehicle-to-infrastructure (V2I). In the V2V mode, vehicles may communicate with each other, sharing data such as position, speed, acceleration, and other relevant information. This may enable cooperative driving, collision avoidance, and traffic efficiency improvements.

[0090] In recent years, vehicle manufacturers have been developing vehicles with assisted driving and / or autonomous driving capabilities. Assisted driving, which may also be called advanced driver assistance systems (ADAS), may refer to a set of technologies designed to enhance vehicle safety and improve the driving experience by providing assistance and automation to the driver. These technologies may use various sensor(s), camera(s), and other components to monitor a vehicle’s surroundings and assist the driver of the vehicle with certain driving tasks. For example, some features of assisted driving systems may include: (1) adaptive cruise control (ACC) (e.g., a system that automatically adjusts a vehicle’s speed to maintain a safe following distance from the vehicle ahead), (2) lane-keeping assist (LKA) (e.g., a system that uses cameras todetect lane markings and helps keep the vehicle centered within the lane, and provides steering inputs to prevent unintentional lane departure), (3), autonomous emergency braking (AEB) (e.g., a system that detects potential collisions with obstacles or pedestrians and automatically apply the brakes to avoid or mitigate the impact), (4) blind spot monitoring (BSM) (e.g., a system that uses sensors to detect vehicles in a driver’s blind spots and provides visual or audible alerts to avoid potential collisions during lane changes), (5) parking assistance (e.g., a system that assists drivers in parking their vehicles by using camera(s) and sensor(s) to help with parallel parking or maneuvering into tight spaces), and / or traffic sign recognition (e.g., camera(s) and image processing are used to recognize and display traffic signs such as speed limits, stop signs, and other road regulations on the vehicle’s dashboard).

[0091] Autonomous driving, which may also be called as self-driving or driverless technology, may refer to the ability of a vehicle to navigate and operate itself without specifying human intervention (e.g., without a human controlling the vehicle). The goal of the autonomous driving is to create vehicles that are capable of perceiving their surroundings, making decisions, and controlling their movements, all without the direct involvement of a human driver. To achieve or improve the autonomous driving, a vehicle may be specified to use a map (or map data) with detailed information, such as a high-definition (HD) map. An HD map may refer to a highly detailed and accurate digital map designed for use in autonomous driving and ADAS. In one example, HD maps may typically include one or more of: (1) geometric information (e.g., precise road geometry, including lane boundaries, curvature, slopes, and detailed 3D models of the surrounding environment), (2) lane-level information (e.g., information about individual lanes on the road, such as lane width, lane type (e.g., driving, turning, or parking lanes), and lane connectivity), (3) road attributes (e.g., data on road features like traffic signs, signals, traffic lights, speed limits, and road markings), (4) topology (e.g., information about the relationships between different roads, intersections, and connectivity patterns), (5) static objects (e.g., locations and details of fixed objects along the road, such as buildings, traffic barriers, and poles), (6) dynamic objects (e.g., real-time or frequently updated data about moving objects, like other vehicles, pedestrians, and cyclists), and / or (7) localization and positioning: precise reference points and landmarks that help in accurate vehicle localization on the map, etc.

[0092] As HD maps are capable of providing detailed and up-to-date information about the road network, including lane-level data, traffic signs, road markings, and other important features, etc., HD maps may be an important aspect for enabling autonomous vehicles to navigate complex environments and make informed decisions in real-time. However, to keep the HD map data up-to-date, applications or devices using HD maps may be configured to download and update map data from a server from time to time or based on certain pre-defined conditions (e.g., when travelling to an area that is without map data). In some implementations, downloading map data from a server may be referred to as “map over the air” (MOTA).

[0093] FIG. 6 is a diagram 600 illustrating an example of a vehicle performing map over the air in accordance with various aspects of the present disclosure. In one example, map over the air may refer to a process of a server 604 sending real-time map data 606 to a UE 602 (e.g., a vehicle, an on-board unit (OBU) of the vehicle, an ADAS of the vehicle, a device running a navigation application, etc.) over a wireless network (e.g., an LTE network, a 5G network, etc.), enabling the UE 602 to make decisions based on the latest information about the road and traffic conditions. In a typical implementation, the map data 606 is transmitted from the server 604 (e.g., a cloudbased system), where the server 604 may utilize sensors and other data sources to collect and analyze information about the road network and traffic patterns. This data is then processed and combined with other data, such as GPS / GNSS and camera data from multiple users (e.g., from other UEs / vehicles and / or the UE 602) to create a detailed map of the environment in real-time. Then, an application (e.g., for autonomous driving, navigation, positioning, etc.) of the UE 602 may access the map data 606 over a wireless network (e.g., a cellular or satellite network), and use the map data 606 to make decisions about speed, route, and other factors, etc. For example, the UE 602 may use the map data 606 to avoid road construction, traffic congestion, or accidents, and to optimize its route for efficiency and safety, etc.

[0094] As the integrity of the HD map used in autonomous vehicles may be of paramount importance, any corruption in the map data of a vehicle may have severe implications for the vehicle’s navigation and decision-making capabilities. For example, during a vehicle’s operation (e.g., when the vehicle is under transit), there exists a possibility that the vehicle may lose all the current communication with a network entity (e.g., 5GNR, 4G LTE, or other sources), where the vehicle may not be able to communicatewith a server (e.g., due to a connection outage or a network communication blackout, etc.). Hence, the vehicle may not be able to perform MOTA update as the primary modes for receiving the MOTA update may be from the server.

[0095] When the map data becomes unavailable or is not kept up-to-date, an autonomous vehicle may become stale and / or make erroneous navigation decisions. These could include incorrect lane changes, inaccurate turn instructions, and / or inappropriate route planning, etc. Consequently, the safety and efficiency of the vehicle’s operations may be compromised. In other words, if an HD map used in autonomous vehicles is stale, it may lead to inaccurate perception of the environment and result in incorrect navigation decisions. Therefore, maintaining the integrity of the HD map and ensuring the availability of up-to-date (e.g., at least on the routes of importance) and accurate data may be specified for the effective and safe operation of autonomous vehicles.

[0096] Aspects presented herein may improve the reliability and latency of map data update, thereby improving the performance of applications and devices that use map data (e.g., autonomous driving vehicles, navigation applications, etc.). Aspects presented herein may enable a vehicle (e.g., a UE, a vehicle UE, an OBU of the vehicle, etc.) to dynamically update maps (or map data) in a connected UE / vehicle environment. For example, in one aspect of the present disclosure, a vehicle may be implemented with an algorithm that utilizes C-V2X communication technology to obtain real-time map updates from other nearby C-V2X-enabled vehicles, such as during network communication blackout or system specific / network issues. Aspects presented herein may ensure that the map data of a vehicle is able to remain up-to-date and free from stale or outdated information, even in situations where the primary source of communication for map over-the-air (MOTA) updates is unavailable (e.g., receiving the updates directly from a network / map server).

[0097] FIG. 7 is a flowchart 700 illustrating an example of a first UE obtaining map data or a map data update from a second UE when the network communication is not available in accordance with various aspects of the present disclosure. For purposes of the present disclosure, a network communication may refer to a wireless communication that is performed directly with a network entity / node (e.g., via the Internet), such as a server (e.g., a map server, a positioning server, an autonomous driving system server, etc.), a base station, a transmission reception point (TRP), etc. A network communication blackout or a connection outage may refer to anunavailability of the network communication, where a wireless device may not be able to communicate with (e.g., transmit data to and / or receive data from) the network entity / node (or the communication speed, latency, quality, and / or reliability is below a threshold). Aspects presented herein may enable a vehicle that specifies map data (e.g., the vehicle is traveling to an area without map data) or a map data update (e.g., the map data at the vehicle is outdated) to receive the map data or the map data update from at least one other vehicle when the vehicle is unable to obtain the map data or the map data update directly from a server (e.g., via the Internet).

[0098] At 710, a first UE 702 (e.g., a first vehicle, a first vehicle UE, a first OBU, a first autonomous driving system, etc.) that is specified to download map data (e.g., HD map data) or a map data update (e.g., a HD map data update) may be configured to check the network communication availability. For example, the first UE 702 may be configured to check the network communication availability periodically or when the first UE 702 is specified to access the network (e.g., to download the map data or the map data update).

[0099] At 712, if the network communication is available, the first UE 702 may download the map data or the map data update directly from a server (e.g., a map server). In other words, the first UE 702 may download the map data or the map data update based on the available network communication. However, if the network communication is not available (e.g., a network communication blackout or a connection outage is detected), at 714, the first UE 702 may inform its C-V2X stack, meaning the first UE 702 may initiate or prepare to start a sidelink communication based on a C-V2X mechanism / protocol.

[0100] At 716, the first UE 702 may be configured to periodically check for C-V2X communication opportunity with other vehicle(s). For example, the first UE 702 may broadcast sidelink message(s) periodically to indicate its presence or to send request(s) (e.g., sidelink communication establishment request(s)) to other UEs / sidelink devices, and / or the first UE 702 may monitor for sidelink message(s) transmitted / broadcasted by other UEs (e.g., for indicating their presences).

[0101] At 718, the first UE 702 may continue to monitor whether a C-V2X communication opportunity arises. If a C-V2X communication opportunity does not arise, the first UE 702 may continue to perform the periodic check for such opportunity as discussed in connection with 716. On the other hand, if the first UE 702 detects that a C-V2Xcommunication opportunity arises (e.g., at least one other vehicle responds to the first UE 702’ s sidelink message(s) or the first UE 702 receives sidelink message(s) broadcasted by another vehicle, etc.), then at 720, the first UE 702 may be configured to transmit / broadcast a help request message (e.g., a map data request message). Depending on the implementation, the help request message may include a current map version of the map data used by / available at the first UE 702, a region of interest (ROI) for the map data (e.g., a set of geographic areas / routes in which the first UE 702 is headed to or using), and / or a timestamp (e.g., the time that the help request message is generated / transmitted), etc. In some examples, the first UE 702 may determine / select the map version and / or the interested ROI based on a destination of the first UE 702 and / or based on the current location of the first UE 702.

[0102] At 722, if a second UE 704 (e.g., a second vehicle, a second vehicle UE, a second OBU, a second autonomous driving system, etc.) receives the help request message from the first UE 702, the second UE 704 may check the map version of the map data used by / available at the first UE 702 (e.g., based on information in the help request message). Depending on the implementation, the second UE 704 may also check for other map related information (if they are available or specified), such as the map provider / vendor used by the first UE 702, the software / application used by the first UE 702, whether the map data from both UEs are compatible, etc. In addition, the second UE 704 may also check whether the ROI specified by the first UE 702 is available at the second UE 704 (e.g., the second UE 704 may not have it).

[0103] At 724, the second UE 704 may compare the map version of the first UE 702 with the map version of the map data used by / available at the second UE 704. If the map version of the first UE 702 is newer than the map version of the second UE 704 (e.g., the first UE 702 has a map version 1.2 and the second UE 704 has a map version 1.1, etc.) and / or if the second UE 704 does not have the ROI specified by the first UE 702, at 726, the second UE 704 may ignore the help request from the first UE 702. For example, the second UE 704 may ignore the help request message received from the first UE 702 and take no action(s).

[0104] On other hand, if the map version of the first UE 702 is older than the map version of the second UE 704 (e.g., the first UE 702 has a map version 1.0 and the second UE 704 has a map version 1.3, etc.), and the second UE 704 also has the ROI specified by the first UE 702, at 728, the second UE 704 may check for delta (e.g., thedifference) on ROI specified by the first UE 702. For example, as shown at 730, the second UE 704 may check whether there are new routes, new objects / road blockages, new markers / traffic information, and / or new destination, etc. associated with the ROI.

[0105] At 732, the second UE 704 may send, to the first UE 702, information related to the map data available at the second UE 704 (e.g., the map version details) and also if delta is present (e.g., an indication of yes or no), and the second UE 704 may wait / monitor for a response from the first UE 702.

[0106] At 734, the first UE 702 may receive, from the second UE 704, the information related to the map data available at the second UE 704, and also from other UEs if available. For example, there may be a third UE that also sends information related to its map data (e.g., the map version and / or delta on ROIs) to the first UE 702.

[0107] At 736, the first UE 702 may determine / choose a map version (among the received map versions), and send an acknowledgement (ACK) message to the UE with the map version determined / chosen by the first UE 702. For example, the first UE 702 may decide on a most optimal map data with delta on ROI from map information received via other UEs, and send an ACK message to the UE with that optimal map data (to indicate that the first UE 702 will be receiving map data from that UE). The first UE 702 may also send a negative acknowledgement (NACK) message to other UEs that do not have map version specified / chosen by the first UE 702. In some implementations, the first UE 702 may also be configured to just ignore these UEs without sending a NACK message.

[0108] At 738, the first UE 702 may establish a communication (e.g., a sidelink communication, a communication based on C-V2X protocol, etc.) with a UE that has the map version (e.g., the optimal map with ROI delta) specified / chosen by the first UE 702. For example, assuming that the map version of the map data available at the second UE 704 is selected / specified by the first UE 702, the first UE 702 may establish a sidelink / C-V2X communication with the second UE 704.

[0109] At 740, after a communication is established between the first UE 702 and the second UE 704, the second UE 704 may send its map data, a portion of the map data, or just the ROI delta changes (e.g., to reduce transmission overhead) to the first UE 702.

[0110] At 742, after receiving the map data from the second UE 704, the first UE 702 may validate the received map data (e.g., to ensure the correctness, completeness, and / or the integrity of the map data), and integrate the received map data (or the ROI deltachanges) to the current map data available at the first UE 702. In other words, the first UE 702 may update its map data based on the map data received from the second UE 704. As such, aspects presented herein may enable the first UE 702 to continue to perform map data updates during a network communication blackout.

[0111] At 744, in some implementations, the first UE 702 may also be configured to broadcast the updated map data (the updated map data at the first UE 702 or the map data received from the second UE 704) if specified or upon request (e.g., by other UEs). This may enable a vehicle / UE with a most recent / newest version of map data to provide its map data (directly and indirectly) to multiple vehicles / UEs. In addition, if the first UE 702 detects a change in the route travelled by the first UE 702, the first UE 702 may repeat the processes described above, such as transmit / broadcast another help request that includes the map version information of the map data used by the first UE 702 and the ROI.

[0112] FIG. 8 is a communication flow 800 illustrating an example of a UE requesting map data or a map data update from multiple UEs when the network communication is not available in accordance with various aspects of the present disclosure. The numberings associated with the communication flow 800 do not specify a particular temporal order and are merely used as references for the communication flow 800.

[0113] At 810, a first UE 802 (e.g., a first vehicle, a first vehicle UE, a first OBU, a first autonomous driving system, etc.) that is specified to download map data (e.g., HD map data) or a map data update (e.g., a HD map data update) may be configured to check the network communication availability, such as detecting whether there is a network communication blockage as described in connection with 710 of FIG. 7.

[0114] At 812, if the first UE 802 detects that the network communication is not available, the first UE 802 may inform its C-V2X stack, meaning the first UE 802 may initiate or prepare to start a sidelink communication based on a C-V2X mechanism / protocol as described in connection with 714, 716, and 718 of FIG. 7.

[0115] At 814, the first UE 802 may transmit / broadcast a help request message, where the help request message may include a current map version of the map data used by / available at the first UE 802, an ROI for the map data, and / or a timestamp, etc., as described in connection with 720 of FIG. 7.

[0116] At 816, a second UE 804 (e.g., a second vehicle, a second vehicle UE, a second OBU, a second autonomous driving system, etc.) and a third UE 806 (e.g., a third vehicle, athird vehicle UE, a third OBU, a third autonomous driving system, etc.) may both receive the help request message from the first UE 802. The second UE 804 and the third UE 806 may each check the map version of the map data used by / available at the first UE 802 and compare it with the map version of the map data used by / available at the second UE 804 / the third UE 806, such as described in connection with 722 of FIG. 7.

[0117] At 818, if the map version of the first UE 802 is newer than the map version of the second UE 804 / third UE 806, the second UE 804 / third UE 806 may ignore the help request from the first UE 802, such as described in connection with 724 and 726 of FIG. 7. For purposes of illustration, assuming the map version of the first UE 802 is V.1.0, the map version of the second UE 804 is V.1.1, and the map version of the third UE 806 is V.1.2 (e.g., V.1.2 > V.1.1 > V.1.0).

[0118] At 820, as the map versions of the second UE 804 and the third UE 806 are newer than the map version of the first UE 802, the second UE 804 and the third UE 806 may each indicate to the first UE 802 its map version and / or delta present on the ROI specified (if there are delta / changes present on the ROI), such as described in connection with 732 of FIG. 7. As an alternative, as shown at 822, the second UE 804 and the third UE 806 may also each indicate to the first UE 802 just its map version (if there are no delta / changes present on the ROI).

[0119] At 824, the first UE 802 may receive the map versions of the second UE 804 and the third UE 806 (and also the indication of whether there is delta / changes on the ROI). In some examples, if there are no changes / delta detected on the ROI, the first UE 802 may continue to look / check for map data update(s) from other UEs (e.g., after a certain interval of time) until the first UE 802 reaches its destination and / or until the network communication is available. On the other hand, if the map versions of the second UE 804 and the third UE 806 are both newer than the first UE 802, and both map versions include ROI (and changes / delta in ROI) specified by the first UE 802, the first UE 802 may choose a latest map version (and in which ROI has delta / changes) as described in connection with 736 of FIG. 7. For example, as the map version of the third UE 806 is newer than the map version of the second UE 804 (e.g., V.1.2 > V. 1.1), the first UE 802 may choose the map version of the third UE 806.

[0120] At 824, the first UE 802 may transmit a NACK message to the second UE 804 (e.g., to indicate that the first UE 802 does not specify the map version of the second UE804). At 826, the first UE 802 may transmit an ACK message to the third UE 806 (e.g., to indicate that the first UE 802 is going to accept / receive the map version of the second UE 804).

[0121] At 828, in response to the ACK message, the third UE 806 may transmit its map data, a portion of the map data, or the delta changes on ROI, etc. to the first UE 802, such as described in connection with 740 of FIG. 7.

[0122] At 830, after receiving the map data from the third UE 806, the first UE 802 may validate the received map data (e.g., to ensure the correctness, completeness, and / or the integrity of the map data), and integrate the received map data (or the ROI delta changes) to the current map data available at the first UE 802. In other words, the first UE 802 may update its map data based on the map data received from the third UE 806.

[0123] Aspects presented herein are directed to techniques / protocols for HD maps update in the event of network outage or other network issues that prevent the vehicles from obtaining HD maps updates timely. Aspects presented herein include proposals that utilize C-V2X communication to obtain map updates from nearby C-V2X-enabled vehicles. The target vehicle detects network issues and broadcasts map update request to nearby vehicles including its current map version information. The other vehicles will check to see whether there are updates that can be provided to the target vehicle .

[0124] By leveraging C-V2X communication, aspects presented herein allow vehicles to obtain real-time map updates from nearby C-V2X-enabled vehicles. This ensures that the map data remains accurate and up-to-date, reducing the presence of stale or outdated information. For example, in situations where the primary source of communication for MOTA updates, such as LTE / NR, is blacked out or unavailable, aspects presented herein provide an alternative means of obtaining map updates. It utilizes the C-V2X communication mechanism, enabling vehicles to exchange map data directly, thereby reducing dependence on a single communication channel.

[0125] Aspects presented herein may also improve a user’s safety because real-time map updates are crucial for enabling ADAS and autonomous driving functionalities. By dynamically acquiring and integrating map changes, the algorithm described herein helps vehicles stay informed about the latest road conditions, hazards, and other relevant information, contributing to enhanced safety on the road. The algorithm described herein may also optimize the exchange of map data by calculating andtransmitting just the delta (changes) for region of interest (ROI) between the current map and the most recent map received from a C-V2X-enabled vehicle. This reduces the amount of data transmission specified, minimizing bandwidth usage and facilitating efficient communication between vehicles.

[0126] FIG. 9 is a flowchart 900 of a method of wireless communication at a user equipment (UE). The method may be performed by a UE (e.g., the UE 104, 404, 502, 504, 506, 508, 602; the first UE 702, 802; the apparatus 1004). The method may enable the UE to update its map data (e.g., for autonomous driving and / or navigation purposes) based on sidelink / C-V2X communication(s) with other UE(s) / vehicle(s) when the network communication is not available.

[0127] At 902, a first UE may detect a connection outage between the first UE and a map server, such as described in connection with FIGs. 7 and 8. For example, as discussed in connection with 710 of FIG. 7, a first UE 702 that is specified to download map data or a map data update may be configured to check the network communication availability. The detection of the connection outage may be performed by, e.g., the map update component 198, the transceiver(s) 1022, the cellular baseband processor(s) 1024, and / or the application processor(s) 1006 of the apparatus 1004 in FIG. 10.

[0128] At 904, the first UE may broadcast a map data request that includes map version information of first map data used by the first UE and at least one region of interest (ROI) based on the detection of the connection outage, such as described in connection with FIGs. 7 and 8. For example, as discussed in connection with 720 of FIG. 7, the first UE 702 may be configured to transmit / broadcast a help request message. Depending on the implementation, the help request message may include a current map version of the map data used by / available at the first UE 702, a region of interest (ROI) for the map data (e.g., a set of geographic areas / routes in which the first UE 702 is headed to or using), and / or a timestamp (e.g., the time that the help request message is generated / transmitted), etc. The broadcast of the map data request may be performed by, e.g., the map update component 198, the transceiver(s) 1022, the cellular baseband processor(s) 1024, and / or the application processor(s) 1006 of the apparatus 1004 in FIG. 10.

[0129] At 906, the first UE may receive, from at least one second UE based on the map data request, second map data that includes the at least one ROI, such as described inconnection with FIGs. 7 and 8. For example, as discussed in connection with 740 of FIG. 7, after a communication is established between the first UE 702 and the second UE 704, the first UE 702 may receive map data, a portion of the map data, or just the ROI delta changes from the second UE 704. The reception of the second map data that includes the at least one ROI may be performed by, e.g., the map update component 198, the transceiver(s) 1022, the cellular baseband processor(s) 1024, and / or the application processor(s) 1006 of the apparatus 1004 in FIG. 10.

[0130] In one example, the first UE may validate the received second map data, and apply the received second map data or integrate the received second map data with the first map data. In some implementations, the first UE may detect a change in a route travelled by the first UE, and broadcast a second map data request that includes second map version information of the second map data used by the first UE and at least one second ROI based on the detection of the change in the route.

[0131] In another example, the first UE may receive, from the at least one second UE based on the map data request, an indication of the second map data available at the at least one second UE, and transmit, to the at least one second UE based on the indication, an acknowledgment (ACK) to receive the second map data from the at least one second UE.

[0132] In another example, the first UE may transmit or broadcast the second map data to at least one third UE.

[0133] In another example, the first UE may receive, from a third UE based on the map data request, an indication that the third UE does not have map data that is newer than the first map data or the third UE does not have map data that includes the at least one ROI.

[0134] In another example, the connection outage may correspond to at least one of: a connection speed between the first UE and the map server is below a speed threshold, the first UE is disconnected from the map server, the first UE is unable to retrieve updated map data from the map server, or the map server is irresponsive.

[0135] In another example, the at least one ROI may include: a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the first UE, or a third area associated with a range of the first UE.

[0136] In another example, the first UE may be a first navigation system or a first autonomous driving vehicle, and the at least one second UE may be at least one second navigation system or at least one second autonomous driving vehicle.

[0137] In another example, to broadcast the map data request, the first UE may broadcast the map data request based on cellular vehicle-to-everything (C-V2X) communication.

[0138] FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1004. The apparatus 1004 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1004 may include at least one cellular baseband processor 1024 (also referred to as a modem) coupled to one or more transceivers 1022 (e.g., cellular RF transceiver). The cellular baseband processor(s) 1024 may include at least one on-chip memory 1024'. In some aspects, the apparatus 1004 may further include one or more subscriber identity modules (SIM) cards 1020 and at least one application processor 1006 coupled to a secure digital (SD) card 1008 and a screen 1010. The application processor(s) 1006 may include on-chip memory 1006'. In some aspects, the apparatus 1004 may further include a Bluetooth module 1012, a WLAN module 1014, an ultrawide band (UWB) module 1038, an SPS module 1016 (e.g., GNSS module), one or more sensors 1018 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU), gyroscope, and / or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and / or other technologies used for positioning), additional memory modules 1026, a power supply 1030, and / or a camera 1032. The Bluetooth module 1012, the UWB module 1038, the WLAN module 1014, and the SPS module 1016 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include their own dedicated antennas and / or utilize the antennas 1080 for communication. The cellular baseband processor(s) 1024 communicates through the transceiver(s) 1022 via one or more antennas 1080 with the UE 104 and / or with an RU associated with a network entity 1002. The cellular baseband processor(s) 1024 and the application processor(s) 1006 may each include a computer-readable medium / memory 1024', 1006', respectively. The additional memory modules 1026 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1024', 1006', 1026 may be non-transitory. The cellular baseband processor(s) 1024 and the application processor(s) 1006 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor(s) 1024 / application processor(s) 1006, causes the cellular baseband processor(s) 1024 / application processor(s) 1006 to perform the various functions described supra. The cellular baseband processor(s) 1024 and the application processor(s) 1006 are configured to perform the various functions described supra based at least in part of the information stored in the memory. That is, the cellular baseband processor(s) 1024 and the application processor(s) 1006 may be configured to perform a first subset of the various functions described supra without information stored in the memory and may be configured to perform a second subset of the various functions described supra based on the information stored in the memory. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor(s) 1024 / application processor(s) 1006 when executing software. The cellular baseband processor(s) 1024 / application processor(s) 1006 may be a component of the UE 350 and may include the at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1004 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor(s) 1024 and / or the application processor(s) 1006, and in another configuration, the apparatus 1004 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1004.

[0139] As discussed supra, the map update component 198 may be configured to detect a connection outage between the first UE and a map server. The map update component 198 may also be configured to broadcast a map data request that includes map version information of first map data used by the first UE and at least one ROI based on the detection of the connection outage. The map update component 198 may also be configured to receive, from at least one second UE based on the map data request, second map data that includes the at least one ROI. The map update component 198 may be within the cellular baseband processor(s) 1024, the application processor(s) 1006, or both the cellular baseband processor(s) 1024 and the application processor(s) 1006. The map update component 198 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented byone or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. As shown, the apparatus 1004 may include a variety of components configured for various functions. In one configuration, the apparatus 1004, and in particular the cellular baseband processor(s) 1024 and / or the application processor(s) 1006, may include means for detecting a connection outage between the first UE and a map server. The apparatus 1004 may further include means for broadcasting a map data request that includes map version information of first map data used by the first UE and at least one ROI based on the detection of the connection outage. The apparatus 1004 may further include means for receiving, from at least one second UE based on the map data request, second map data that includes the at least one ROI.

[0140] In one configuration, the apparatus 1004 may further include means for validating the received second map data, and means for applying the received second map data or means for integrating the received second map data with the first map data. In some implementations, the apparatus 1004 may further include means for detecting a change in a route travelled by the first UE, and means for broadcasting a second map data request that includes second map version information of the second map data used by the first UE and at least one second ROI based on the detection of the change in the route.

[0141] In another configuration, the apparatus 1004 may further include means for receiving, from the at least one second UE based on the map data request, an indication of the second map data available at the at least one second UE, and means for transmitting, to the at least one second UE based on the indication, an ACK to receive the second map data from the at least one second UE.

[0142] In another configuration, the apparatus 1004 may further include means for transmitting or broadcasting the second map data to at least one third UE.

[0143] In another configuration, the apparatus 1004 may further include means for receiving, from a third UE based on the map data request, an indication that the third UE does not have map data that is newer than the first map data or the third UE does not have map data that includes the at least one ROI.

[0144] In another configuration, the connection outage may correspond to at least one of: a connection speed between the apparatus 1004 and the map server is below a speed threshold, the apparatus 1004 is disconnected from the map server, the apparatus 1004 is unable to retrieve updated map data from the map server, or the map server is irresponsive.

[0145] In another configuration, the at least one ROI may include: a first area associated with a destination of the apparatus 1004, a second area associated with at least one route towards the destination of the apparatus 1004, or a third area associated with a range of the apparatus 1004.

[0146] In another configuration, the apparatus 1004 may be a first navigation system or a first autonomous driving vehicle, and the at least one second UE may be at least one second navigation system or at least one second autonomous driving vehicle.

[0147] In another configuration, the means for broadcasting the map data request may include configuring the apparatus 1004 to broadcast the map data request based on C-V2X communication.

[0148] The means may be the map update component 198 of the apparatus 1004 configured to perform the functions recited by the means. As described .sz / ra,the apparatus 1004 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0149] FIG. 11 is a flowchart 1100 of a method of wireless communication at a user equipment (UE). The method may be performed by a UE (e.g., the UE 104, 404, 502, 504, 506, 508, 602; the second UE 704, 804; the third UE 806; the apparatus 1204). The method may enable the UE to provide its map data or map data update to another UE based on sidelink / C-V2X communication(s).

[0150] At 1102, a second UE may receive, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one ROI, such as described in connection with FIGs. 7 and 8. For example, as discussed in connection with 722 of FIG. 7, the second UE 704 mat receive the help request message from the first UE 702. Depending on the implementation, the help request message may include a current map version of the map data used by / available at the first UE 702, an ROI for the map data, and / or a timestamp, etc. The reception of themap data request may be performed by, e.g., the map update component 198, the transceiver(s) 1222, the cellular baseband processor(s) 1224, and / or the application processor(s) 1206 of the apparatus 1204 in FIG. 12.

[0151] At 1104, the second UE may verify, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI, such as described in connection with FIGs. 7 and 8. For example, as discussed in connection with 722 of FIG. 7, the second UE 704 may check the map version of the map data used by / available at the first UE 702 (e.g., based on information in the request message). The verification of the map data request may be performed by, e.g., the map update component 198, the transceiver(s) 1222, the cellular baseband processor(s) 1224, and / or the application processor(s) 1206 of the apparatus 1204 in FIG. 12.

[0152] At 1106, the second UE may transmit, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI, such as described in connection with FIGs. 7 and 8. For example, as discussed in connection with 740 of FIG. 7, after a communication is established between the first UE 702 and the second UE 704, the second UE 704 may send its map data, a portion of the map data, or just the ROI delta changes to the first UE 702. The transmission of the second map data may be performed by, e.g., the map update component 198, the transceiver(s) 1222, the cellular baseband processor(s) 1224, and / or the application processor(s) 1206 of the apparatus 1204 in FIG. 12.

[0153] In one example, to transmit the second map data, the second UE may determine a set of delta changes between the first map data and the second map data, and transmit the set of delta changes between the first map data and the second map data. In some implementations, the second UE may receive a second map data request that includes at least one second ROI, and transmit, to the first UE, third map data that includes the at least one second ROI.

[0154] In another example, the second UE may transmit, to the first UE based on the map data request, an indication of the second map data available at the second UE, and receive, from the first UE based on the indication, an ACK to receive the second map data from the second UE.

[0155] In another example, the at least one ROI may include: a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the first UE, or a third area associated with a range of the first UE.

[0156] In another example, the first UE may be a first navigation system or a first autonomous driving vehicle, and the second UE may be a second navigation system or a second autonomous driving vehicle.

[0157] In another example, to receive the map data request, the second UE may receive the map data request based on C-V2X communication.

[0158] FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include at least one cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., cellular RF transceiver). The cellular baseband processor(s) 1224 may include at least one on-chip memory 1224'. In some aspects, the apparatus 1204 may further include one or more subscriber identity modules (SIM) cards 1220 and at least one application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor(s) 1206 may include on-chip memory 1206'. In some aspects, the apparatus 1204 may further include a Bluetooth module 1212, a WLAN module 1214, an ultrawide band (UWB) module 1238, an SPS module 1216 (e.g., GNSS module), one or more sensors 1218 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU), gyroscope, and / or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and / or other technologies used for positioning), additional memory modules 1226, a power supply 1230, and / or a camera 1232. The Bluetooth module 1212, the UWB module 1238, the WLAN module 1214, and the SPS module 1216 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas and / or utilize the antennas 1280 for communication. The cellular baseband processor(s) 1224 communicates through the transceiver(s) 1222 via one or more antennas 1280 with the UE 104 and / or with an RU associated with a network entity 1202. The cellular baseband processor(s) 1224 and the application processor(s) 1206 may each includea computer-readable medium / memory 1224', 1206', respectively. The additional memory modules 1226 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1224', 1206', 1226 may be non- transitory. The cellular baseband processor(s) 1224 and the application processor(s) 1206 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor(s) 1224 / application processor(s) 1206, causes the cellular baseband processor(s) 1224 / application processor(s) 1206 to perform the various functions described supra. The cellular baseband processor(s) 1224 and the application processor(s) 1206 are configured to perform the various functions described supra based at least in part of the information stored in the memory. That is, the cellular baseband processor(s) 1224 and the application processor(s) 1206 may be configured to perform a first subset of the various functions described supra without information stored in the memory and may be configured to perform a second subset of the various functions described supra based on the information stored in the memory. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor(s) 1224 / application processor(s) 1206 when executing software. The cellular baseband processor(s) 1224 / application processor(s) 1206 may be a component of the UE 350 and may include the at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1204 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor(s) 1224 and / or the application processor(s) 1206, and in another configuration, the apparatus 1204 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1204.

[0159] As discussed supra, the map update component 198 may be configured to receive, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one ROI. The map update component 198 may also be configured to verify, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI. The map update component 198 may also be configured to transmit, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI. The map update component 198 maybe within the cellular baseband processor(s) 1224, the application processor(s) 1206, or both the cellular baseband processor(s) 1224 and the application processor(s) 1206. The map update component 198 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. As shown, the apparatus 1204 may include a variety of components configured for various functions. In one configuration, the apparatus 1204, and in particular the cellular baseband processor(s) 1224 and / or the application processor(s) 1206, may include means for receiving, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one ROI. The apparatus 1204 may further include means for verifying, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI. The apparatus 1204 may further include means for transmitting, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI.

[0160] In one configuration, the means for transmitting the second map data may include configuring the apparatus 1204 to determine a set of delta changes between the first map data and the second map data, and transmit the set of delta changes between the first map data and the second map data. In some implementations, the apparatus 1204 may further include means for receiving a second map data request that includes at least one second ROI, and transmit, to the first UE, third map data that includes the at least one second ROI.

[0161] In another configuration, the apparatus 1204 may further include means for transmitting, to the first UE based on the map data request, an indication of the second map data available at the apparatus 1204, and means for receiving, from the first UE based on the indication, an ACK to receive the second map data from the apparatus 1204.

[0162] In another configuration, the at least one ROI may include: a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the first UE, or a third area associated with a range of the first UE.

[0163] In another configuration, the first UE may be a first navigation system or a first autonomous driving vehicle, and the apparatus 1204 may be a second navigation system or a second autonomous driving vehicle.

[0164] In another configuration, the means for receiving the map data request may include configuring the apparatus 1204 to receive the map data request based on C-V2X communication.

[0165] The means may be the map update component 198 of the apparatus 1204 configured to perform the functions recited by the means. As described w / ?ra,the apparatus 1204 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0166] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

[0167] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. A processor may be referred to as processor circuitry. A memory / memory module may be referred to as memory circuitry. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received / transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data or “provide” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,”“element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

[0168] As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

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

[0170] Aspect 1 is a method of wireless communication at a first user equipment (UE), comprising: detecting a connection outage between the first UE and a map server; broadcasting a map data request that includes map version information of first map data used by the first UE and at least one region of interest (ROI) based on the detection of the connection outage; and receiving, from at least one second UE based on the map data request, second map data that includes the at least one ROI.

[0171] Aspect 2 is the method of aspect 1, further comprising: validating the received second map data; and applying the received second map data or integrating the received second map data with the first map data.

[0172] Aspect s is the method of aspect 1 or aspect 2, further comprising: detecting a change in a route travelled by the first UE; and broadcasting a second map data request that includes second map version information of the second map data used by the first UE and at least one second ROI based on the detection of the change in the route.

[0173] Aspect 4 is the method of any of aspects 1 to 3, further comprising: receiving, from the at least one second UE based on the map data request, an indication of the second map data available at the at least one second UE; and transmitting, to the at least one second UE based on the indication, an acknowledgment (ACK) to receive the second map data from the at least one second UE.

[0174] Aspect 5 is the method of any of aspects 1 to 4, further comprising: transmitting or broadcasting the second map data to at least one third UE.

[0175] Aspect 6 is the method of any of aspects 1 to 5, further comprising: receiving, from a third UE based on the map data request, an indication that the third UE does not havemap data that is newer than the first map data or the third UE does not have map data that includes the at least one ROI.

[0176] Aspect 7 is the method of any of aspects 1 to 6, wherein the connection outage corresponds to at least one of a connection speed between the first UE and the map server is below a speed threshold, the first UE is disconnected from the map server, the first UE is unable to retrieve updated map data from the map server, or the map server is irresponsive.

[0177] Aspect 8 is the method of any of aspects 1 to 7, wherein the at least one ROI includes : a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the first UE, or a third area associated with a range of the first UE.

[0178] Aspect 9 is the method of any of aspects 1 to 8, wherein the first UE is a first navigation system or a first autonomous driving vehicle, and wherein the at least one second UE is at least one second navigation system or at least one second autonomous driving vehicle.

[0179] Aspect 10 is the method of any of aspects 1 to 9, wherein broadcasting the map data request comprises: broadcasting the map data request based on cellular vehicle-to- everything (C-V2X) communication.

[0180] Aspect 11 is an apparatus for wireless communication at a first user equipment (UE), including: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to implement any of aspects 1 to 10.

[0181] Aspect 12 is the apparatus of aspect 11, further including at least one transceiver coupled to the at least one processor.

[0182] Aspect 13 is an apparatus for wireless communication at a first user equipment (UE), including means for implementing any of aspects 1 to 10.

[0183] Aspect 14 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 10.

[0184] Aspect 15 is a method of wireless communication at a second user equipment (UE), comprising: receiving, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one region of interest(ROI); verifying, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI; and transmitting, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI.

[0185] Aspect 16 is the method of aspect 15, wherein transmitting the second map data comprises: determining a set of delta changes between the first map data and the second map data; and transmitting the set of delta changes between the first map data and the second map data.

[0186] Aspect 17 is the method of aspect 15 or aspect 16, further comprising: receiving a second map data request that includes at least one second ROI; and transmitting, to the first UE, third map data that includes the at least one second ROI.

[0187] Aspect 18 is the method of any of aspects 15 to 17, further comprising: transmitting, to the first UE based on the map data request, an indication of the second map data available at the second UE; and receiving, from the first UE based on the indication, an acknowledgment (ACK) to receive the second map data from the second UE.

[0188] Aspect 19 is the method of any of aspects 15 to 18, wherein the at least one ROI includes: a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the first UE, or a third area associated with a range of the first UE.

[0189] Aspect 20 is the method of any of aspects 15 to 19, wherein the first UE is a first navigation system or a first autonomous driving vehicle, and wherein the second UE is a second navigation system or a second autonomous driving vehicle.

[0190] Aspect 21 is the method of any of aspects 15 to 20, wherein receiving the map data request comprises: receiving the map data request based on cellular vehicle-to- everything (C-V2X) communication.

[0191] Aspect 22 is an apparatus for wireless communication at a second user equipment (UE), including: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to implement any of aspects 15 to 21.

[0192] Aspect 23 is the apparatus of aspect 22, further including at least one transceiver coupled to the at least one processor.

[0193] Aspect 24 is an apparatus for wireless communication at a second user equipment (UE), including means for implementing any of aspects 15 to 21.

[0194] Aspect 25 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 15 to 21.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a first user equipment (UE), comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to: detect a connection outage between the first UE and a map server; broadcast a map data request that includes map version information of first map data used by the first UE and at least one region of interest (RO I) based on the detection of the connection outage; and receive, from at least one second UE based on the map data request, second map data that includes the at least one ROI.

2. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: validate the received second map data; and apply the received second map data or integrating the received second map data with the first map data.

3. The apparatus of claim 2, wherein the at least one processor, individually or in any combination, is further configured to: detect a change in a route travelled by the first UE; and broadcast a second map data request that includes second map version information of the second map data used by the first UE and at least one second ROI based on the detection of the change in the route.

4. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: receive, from the at least one second UE based on the map data request, an indication of the second map data available at the at least one second UE; and transmit, to the at least one second UE based on the indication, an acknowledgment (ACK) to receive the second map data from the at least one second UE.

5. The apparatus of claim 1, further comprising at least one transceiver coupled to the at least one processor, wherein the at least one processor, individually or in any combination, is further configured to: transmit or broadcast, via the at least one transceiver, the second map data to at least one third UE.

6. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: receive, from a third UE based on the map data request, an indication that the third UE does not have map data that is newer than the first map data or the third UE does not have map data that includes the at least one ROI.

7. The apparatus of claim 1, wherein the connection outage corresponds to at least one of: a connection speed between the first UE and the map server is below a speed threshold, the first UE is disconnected from the map server, the first UE is unable to retrieve updated map data from the map server, or the map server is irresponsive.

8. The apparatus of claim 1, wherein the at least one ROI includes: a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the first UE, or a third area associated with a range of the first UE.

9. The apparatus of claim 1, wherein the first UE is a first navigation system or a first autonomous driving vehicle, and wherein the at least one second UE is at least one second navigation system or at least one second autonomous driving vehicle.

10. The apparatus of claim 1, wherein to broadcast the map data request, the at least one processor, individually or in any combination, is configured to:broadcast the map data request based on cellular vehicle-to-everything (C-V2X) communication.

11. A method of wireless communication at a first user equipment (UE), comprising : detecting a connection outage between the first UE and a map server; broadcasting a map data request that includes map version information of first map data used by the first UE and at least one region of interest (ROI) based on the detection of the connection outage; and receiving, from at least one second UE based on the map data request, second map data that includes the at least one ROI.

12. The method of claim 11, further comprising: validating the received second map data; and applying the received second map data or integrating the received second map data with the first map data.

13. The method of claim 12, further comprising: detecting a change in a route travelled by the first UE; and broadcasting a second map data request that includes second map version information of the second map data used by the first UE and at least one second ROI based on the detection of the change in the route.

14. The method of claim 11, further comprising: receiving, from the at least one second UE based on the map data request, an indication of the second map data available at the at least one second UE; and transmitting, to the at least one second UE based on the indication, an acknowledgment (ACK) to receive the second map data from the at least one second UE.

15. The method of claim 11, further comprising: transmitting or broadcasting the second map data to at least one third UE.

16. The method of claim 11, further comprising:receiving, from a third UE based on the map data request, an indication that the third UE does not have map data that is newer than the first map data or the third UE does not have map data that includes the at least one ROI.

17. The method of claim 11, wherein the connection outage corresponds to at least one of: a connection speed between the first UE and the map server is below a speed threshold, the first UE is disconnected from the map server, the first UE is unable to retrieve updated map data from the map server, or the map server is irresponsive.

18. The method of claim 11, wherein the at least one ROI includes: a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the first UE, or a third area associated with a range of the first UE.

19. The method of claim 11, wherein the first UE is a first navigation system or a first autonomous driving vehicle, and wherein the at least one second UE is at least one second navigation system or at least one second autonomous driving vehicle.

20. The method of claim 11, wherein broadcasting the map data request comprises: broadcasting the map data request based on cellular vehicle-to-everything (C-V2X) communication.

21. An apparatus for wireless communication at a second user equipment (UE), comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to:receive, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one region of interest (ROI); verify, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI; and transmit, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI.

22. The apparatus of claim 21, wherein to transmit the second map data, the at least one processor, individually or in any combination, is configured to: determine a set of delta changes between the first map data and the second map data; and transmit the set of delta changes between the first map data and the second map data.

23. The apparatus of claim 22, further comprising at least one transceiver coupled to the at least one processor, wherein the at least one processor, individually or in any combination, is further configured to: receive a second map data request that includes at least one second ROI; and transmit, to the first UE via the at least one transceiver, third map data that includes the at least one second ROI.

24. The apparatus of claim 21, wherein the at least one processor, individually or in any combination, is further configured to: transmit, to the first UE based on the map data request, an indication of the second map data available at the second UE; and receive, from the first UE based on the indication, an acknowledgment (ACK) to receive the second map data from the second UE.

25. The apparatus of claim 21, wherein the at least one ROI includes: a first area associated with a destination of the first UE,a second area associated with at least one route towards the destination of the firstUE, or a third area associated with a range of the first UE.

26. A method of wireless communication at a second user equipment (UE), comprising: receiving, from a first UE, a map data request that includes map version information of first map data used by the first UE and at least one region of interest (ROI); verifying, based on the map data request, whether the second UE has second map data that is at least newer than the first map data or includes the at least one ROI; and transmitting, to the first UE, the second map data if the second map data is at least newer than the first map data or includes the at least one ROI.

27. The method of claim 26, wherein transmitting the second map data comprises: determining a set of delta changes between the first map data and the second map data; and transmitting the set of delta changes between the first map data and the second map data.

28. The method of claim 27, further comprising: receiving a second map data request that includes at least one second ROI; and transmitting, to the first UE, third map data that includes the at least one secondROI.

29. The method of claim 26, further comprising: transmitting, to the first UE based on the map data request, an indication of the second map data available at the second UE; and receiving, from the first UE based on the indication, an acknowledgment (ACK) to receive the second map data from the second UE.

30. The method of claim 26, wherein the at least one ROI includes: a first area associated with a destination of the first UE, a second area associated with at least one route towards the destination of the firstUE, or a third area associated with a range of the first UE.

Images