Efficient Route History and Complete Certificate Inclusion in Safety Messages

Abstract

The present disclosure provides systems, methods, and devices for wireless communication supporting enhanced Basic Safety Message (BSM) reporting. In a first aspect, a method of wireless communication includes receiving, by a wireless communication device, a C-V2X message from another wireless communication device, and transmitting, by the wireless communication device, a safety message including route history information in response to determining, by the wireless communication device, that a route history information trigger condition is met based on the C-V2X message. In a second aspect, a method of wireless communication includes receiving, by the wireless communication device, a C-V2X message from another wireless communication device, and transmitting, by the wireless communication device, a safety message including certificate information in response to determining, by the wireless communication device, that a certificate information trigger condition is met based on the C-V2X message. Other aspects and features are also claimed and described.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS)

[0001] This application claims the benefit of U.S. patent application Ser. No. 17 / 646,976, entitled "EFFICIENT PATH HISTORY AND FULL CERTIFICATE INCLUSION IN SAFETY MESSAGES," filed Jan. 4, 2022, the entire contents of which are expressly incorporated by reference into this specification.

[0002]

[0002] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to device-to-device communication. Several features can enable and provide improved communication, including enhanced safety messages, such as Basic Safety Messages (BSMs), and reporting operations. [Background technology]

[0003]

[0003] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple access networks capable of supporting multiple users by sharing available network resources. Such networks may be multiple access networks that support communication for multiple users by sharing available network resources.

[0004]

[0004] A wireless communication network may include several components. These components may include wireless communication devices, such as base stations (or Node Bs), that can support communication for several user equipments (UEs). The UEs may communicate with the base stations via a downlink and an uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station.

[0005]

[0005] A base station may transmit data and control information to a UE on the downlink or receive data and control information from a UE on the uplink. On the downlink, transmissions from a base station may experience interference due to transmissions from neighboring base stations or from other wireless radio frequency (RF) transmitters. On the uplink, transmissions from a UE may experience interference from uplink transmissions of other UEs communicating with neighboring base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and the uplink.

[0006]

[0006] As the demand for mobile broadband access continues to increase, more UEs access long-range wireless communication networks, and more short-range wireless systems are deployed in regions, increasing the possibility of interference and network congestion. Research and development continues to evolve wireless technologies to not only meet the growing demand for mobile broadband access, but also to evolve and improve the user experience of mobile communications. Summary of the Invention

[0007]

[0007] The following summarizes some aspects of the present disclosure to provide a basic understanding of the discussed technology. This summary is not an extensive overview of all of the contemplated features of the present disclosure, and is not intended to identify key or critical elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in summary form as a prelude to the more detailed description presented later.

[0008]

[0008] In one aspect of the disclosure, a method of wireless communication includes receiving, by a wireless communication device, a C-V2X message from another wireless communication device, and transmitting, by the wireless communication device, a safety message including route history information in response to determining that a route history information trigger condition is met based on the C-V2X message.

[0009]

[0009] In another aspect of the present disclosure, an apparatus for wireless communication includes a processor and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the processor to receive a C-V2X message from a wireless communication device and, in response to determining that a route history information trigger condition is met based on the C-V2X message, send a safety message including route history information.

[0010]

[0010] In one aspect of the present disclosure, a method for wireless communication includes receiving, by a wireless communication device, a C-V2X message from another wireless communication device, and transmitting, by the wireless communication device, a secure message including certificate information in response to determining, based on the C-V2X message, that a certificate information trigger condition is satisfied.

[0011]

[0011] In another aspect of the present disclosure, an apparatus for wireless communication includes a processor and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the processor to receive a C-V2X message from a wireless communication device and, in response to determining that a certificate information trigger condition is met based on the C-V2X message, send a secure message including certificate information.

[0012]

[0012] The foregoing has outlined rather broadly the features and technical advantages of the embodiments of the present disclosure in order that the following "Detailed Description of the Invention" may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures are within the scope of the appended claims. The concepts disclosed herein, both their organization and the method of operation, characteristic of the concepts disclosed herein, together with associated advantages, will be better understood in the following description taken in conjunction with the accompanying figures. Each of the figures is provided for illustration and explanation, and not as a definition of the limits of the claims.

[0013]

[0013] Although aspects and implementations are described in this application by illustrating some examples, those skilled in the art will understand that additional implementations and use cases may arise in many different configurations and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or applications may arise with integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some examples may or may not be specifically targeted to a use case or application, but a wide variety of applicability of the described innovation may arise. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovation. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processor(s), interleavers, summers / analog summers, etc.). It is contemplated that the innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, end-user devices, etc. of various sizes, shapes, and configurations. [Brief description of the drawings]

[0014]

[0014] A further understanding of the nature and advantages of the present disclosure can be realized by referring to the following drawings. In the accompanying drawings, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. When only a first reference label is used in this specification, the description is applicable to any one of the similar components having the same first reference label, regardless of the second reference label. [Figure 1]

[0015] FIG. 1 is a block diagram illustrating details of an example wireless communication system in accordance with one or more aspects. [Diagram 2]

[0016] FIG. 1 is a block diagram illustrating an example of a base station and user equipment (UE) in accordance with one or more aspects. [Figure 3A]

[0017] FIG. 1 is a diagram of a device-to-device communication system. [Figure 3B]

[0018] FIG. 1 is an exemplary diagram illustrating device-to-device communication. [Figure 4]

[0019] FIG. 1 is a block diagram illustrating an example wireless communication system supporting enhanced secure message reporting operations in accordance with one or more aspects. [Diagram 5]

[0020] FIG. 1 illustrates an example wireless communication system that supports enhanced secure message reporting operations in accordance with one or more aspects. [Figure 6]

[0021] FIG. 1 is a flow diagram illustrating an example process for supporting enhanced secure message reporting operations in accordance with one or more aspects. [Figure 7]

[0022] FIG. 1 is a flow diagram illustrating an example process for supporting enhanced secure message reporting operations in accordance with one or more aspects. [Figure 8]

[0023] 1 is a block diagram of an example UE that supports enhanced secure message reporting operations in accordance with one or more aspects.

[0015]

[0024] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016]

[0025] The detailed description of the present invention, set forth below in conjunction with the accompanying drawings, is intended as an illustration of various configurations and is not intended to limit the scope of the present disclosure. Rather, the detailed description of the present invention includes specific details intended to provide a thorough understanding of the subject matter of the present invention. Those skilled in the art will appreciate that these specific details are not required in every instance and that in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0017]

[0026] The present disclosure generally relates to providing or participating in authorized shared access among two or more wireless devices in one or more wireless communication systems, also referred to as wireless communication networks. In various implementations, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th Generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems, or devices), and other communication networks. The terms "network" and "system" described herein may be used interchangeably.

[0018]

[0027] For example, a CDMA network may implement a radio technology such as universal terrestrial radio access (UTRA), cdma2000, etc. UTRA includes wideband-CDMA (W-CDMA) and low chip rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0019]

[0028] The TDMA network may implement a radio technology such as Global System for Mobile Communication (GSM). The 3rd Generation Partnership Project (3GPP) defines standards for the GSM EDGE (Enhanced Data Rates for GSM Evolution) radio access network (RAN), also denoted as GERAN. GERAN is the radio component of GSM / EDGE, together with the network connecting base stations (e.g., Ater and Abis interfaces) and base station controllers (such as A interface). The radio access network represents the component of the GSM network through which telephone calls and packet data are routed to and from the public switched telephone network (PSTN) and the Internet to and from subscriber handsets, also known as user terminals or user equipment (UEs). A mobile operator's network may include one or more GERANs, which may be combined with a UTRAN in the case of a UMTS / GSM network. In addition, the operator network may also include one or more LTE networks or one or more other networks. Various different network types may use different radio access technologies (RATs) and RANs.

[0020]

[0029] OFDMA networks may implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, Flash OFDM, etc. UTRA, E-UTRA, and GSM are parts of the universal mobile telecommunication system (UMTS). Specifically, long term evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration between groups of telecommunications associations whose purpose is to define globally applicable third generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. Although the present disclosure may describe some aspects with reference to LTE, 4G, or 5G NR technology, the description is not intended to be limited to a particular technology or application, and it may be understood that one or more aspects described with reference to one technology may be applicable to another technology. Additionally, one or more aspects of the present disclosure may relate to shared access to a wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0021]

[0030] 5G networks promise diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using an OFDM-based unified air interface. To achieve these goals, further extensions to LTE and LTE-A will be considered in addition to the development of new radio technologies for 5G NR networks. 5G NR is expected to achieve the following: (1) Ultra-high density (e.g., ~1M nodes / km); 2 (2) for large-scale Internet of things (IoTs) with deep coverage with the ability to reach difficult locations, ultra-low complexity (e.g., ~tens of bits / second), ultra-low energy (e.g., ~10+ year battery life), and reach, and (3) for mission-critical control, including users with strong security to protect sensitive personal, financial, and confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1 millisecond (ms)), and wide-area mobility or lack thereof; and (4) for very high capacity (e.g., ~10 Tbps / km). 2 ), very high data rates (e.g., multi-Gbps rates, 100+ Mbps user experience rates), and coverage with enhanced mobile broadband including deep awareness with advanced discovery and optimization.

[0022]

[0031] Devices, networks, and systems may be configured to communicate over one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc., based on frequency or wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "mmWave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" (mmWave) band.

[0023]

[0032] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "mmWave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0024]

[0033] 5G NR devices, networks, and systems may be implemented to use optimized OFDM-based waveform features. These features may include advanced wireless technologies such as scalable numerology and transmission time intervals (TTIs), a common flexible framework for efficient multiplexing of services and features with dynamic low-latency time division duplex (TDD) or frequency division duplex (FDD) designs, massive multiple input, multiple output (MIMO), robust mmWave transmission, advanced channel coding, and device-centric mobility. The scalability of numerology in 5G NR, along with the scaling of subcarrier spacing, may efficiently address the operation of diverse services across diverse spectrums and diverse deployments. For example, in various outdoor and macro coverage deployments of FDD or TDD implementations below 3 GHz, subcarrier spacing may occur at 15 kHz, for example, over bandwidths of 1, 5, 10, 20 MHz, etc. For various other outdoor and small cell coverage deployments of TDD above 3 GHz, the subcarrier spacing may occur at 30 kHz over an 80 / 100 MHz bandwidth. For various other indoor wideband implementations using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting on a mmWave component at 28 GHz TDD, the subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.

[0025]

[0034] 5G NR's scalable numerology facilitates scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to start on symbol boundaries. 5G NR can also expect self-contained, unified subframe designs with uplink or downlink scheduling information, data, and acknowledgements in the same subframe. Self-contained, unified subframes support communication in unlicensed or contention-based shared spectrum, adaptive uplink or downlink that can be flexibly configured per cell to dynamically switch between uplink and downlink to meet current traffic needs.

[0026]

[0035] For clarity, some aspects of the apparatus and techniques may be described below with respect to an example 5G NR implementation or in a 5G-centric manner, and 5G terminology may be used as an illustrative example in parts of the description below, however, the description is not intended to be limited to 5G applications.

[0027]

[0036] It should further be understood that in operation, a wireless communications network adapted in accordance with the concepts herein may operate in any combination of licensed or unlicensed spectrum depending on loading and availability. Accordingly, it will be apparent to those skilled in the art that the systems, apparatus, and methods described herein may be applied to communications systems and applications other than the specific examples shown.

[0028]

[0037] Although aspects and implementations are described in this application by illustrating some examples, those skilled in the art will understand that additional implementations and use cases may occur in many different configurations and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations or applications may occur via integrated chip implementations or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail or purchasing devices, medical devices, AI-enabled devices, etc.). Some examples may or may not be specifically targeted to a use case or application, but a wide variety of applicability of the described innovations may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more described aspects. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features in order to implement and practice the claimed and described aspects. It is contemplated that the innovations described herein may be practiced in a wide variety of implementations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed configurations, end-user devices, and the like, of various sizes, shapes, and configurations.

[0029]

[0038] 1 is a block diagram illustrating details of an exemplary wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may include, for example, a 5G wireless network. As will be appreciated by those skilled in the art, the components appearing in FIG. 1 likely have related counterparts including other network configurations, for example, cellular network configurations and non-cellular network configurations (e.g., device-to-device or peer-to-peer or ad-hoc network configurations, etc.).

[0030]

[0039] The wireless network 100 shown in FIG. 1 includes several base stations 105 and other network entities. A base station may be a station that communicates with UEs and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to this particular geographic coverage area of ​​a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In implementations of the wireless network 100 herein, the base stations 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include a multi-operator wireless network). Additionally, in implementations of the wireless network 100 herein, the base station 105 may provide wireless communication using one or more of the same frequencies as neighboring cells (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof). In some examples, each base station 105 or UE 115 may be operated by more than one network operation entity, while in some other examples, each base station 105 and UE 115 may be operated by a single network operation entity.

[0031]

[0040] A base station may provide communication coverage for a macro cell, or a small cell such as a pico cell or femto cell, or other type of cell. A macro cell generally covers a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription with the network provider. A small cell such as a pico cell generally covers a relatively small geographic area and may allow unrestricted access by UEs with a service subscription with the network provider. A small cell such as a femto cell will also generally cover a relatively small geographic area (e.g., a home) and may provide unrestricted access as well as restricted access by UEs with an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In the example shown in FIG. 1, base stations 105d and 105e are regular macro base stations, while base stations 105a-105c are macro base stations enabled with one of three dimension (3D) MIMO, full dimension (FD) MIMO, or massive MIMO. Base stations 105a-105c take advantage of their higher dimensional MIMO capabilities to leverage 3D beamforming in both advanced and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station that may be a home node or a portable access point. A base station may support one or multiple (e.g., two, three, four, etc.) cells.

[0032]

[0041] The wireless network 100 can support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous or asynchronous operation.

[0033]

[0042] The UEs 115 are dispersed throughout the wireless network 100, and each UE may be fixed or mobile. Although mobile devices are generally referred to as UEs in standards and specifications promulgated by 3GPP, it should be understood that such devices may additionally or otherwise be referred to by those skilled in the art as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices, or vehicle modules, or some other suitable terminology. Within this document, a "mobile" device or UE does not necessarily have to be capable of movement and may be stationary. Some non-limiting examples of mobile devices that may have one or more implementations of UE 115 include mobile, cellular (cell) phones, smartphones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, and personal digital assistants (PDAs).The mobile device may also be an automobile or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multicopter, a quadcopter, a smart energy or security device, an IoT or "Internet of everything" (IoE) device such as a solar panel or solar array, city lighting, water, other infrastructure, industrial automation and enterprise devices, eyewear, wearable cameras, smart watches, health or fitness trackers, mammalian implantable devices, gesture tracking devices, medical devices, consumer and wearable devices such as digital audio players (e.g., MP3 players), cameras, game consoles, and digital home or smart home devices such as home audio, video, multimedia devices, appliances, sensors, vending machines, intelligent lighting, home security systems, smart meters, etc. In one aspect, the UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. The UEs 115a-115d in the implementation shown in FIG. 1 are examples of mobile smartphone type devices accessing the wireless network 100. The UEs may also be machines specifically configured for connected communications, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. The UEs 115e-115k shown in FIG. 1 are examples of various machines configured for communications accessing the wireless network 100.

[0034]

[0043] A mobile device such as the UE 115 may be capable of communicating with any type of base station, such as a macro base station, a pico base station, a femto base station, a relay, etc. In FIG. 1, the communication links (represented as lightning bolts) indicate wireless transmissions between the UE and a serving base station, which is a base station designated to serve the UE on the downlink or uplink, or desired transmissions between base stations, as well as backhaul transmissions between base stations. The UE may act as a base station or other network node in some scenarios. Backhaul communication between base stations of the wireless network 100 may be performed using wired or wireless communication links.

[0035]

[0044] In operation in the wireless network 100, the base stations 105a-105c serve the UEs 115a and 115b using coordinated spatial techniques such as 3D beamforming and coordinated multipoint (CoMP) or multi-connectivity. The macro base station 105d performs backhaul communications with the base stations 105a-105c and the small cell base station 105f. The macro base station 105d also transmits multicast services to which the UEs 115c and 115d subscribe and receive. Such multicast services may include mobile television or stream video, or may include other services for providing community information, such as weather emergencies or alerts such as amber or grey alerts.

[0036]

[0045] The wireless network 100 of the implementation supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as drone UE 115e. Redundant communication links with UE 115e include from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device) can communicate through the wireless network 100 with base stations such as small cell base station 105f and macro base station 105e directly or by communicating with another user device that relays that information to the network in a multi-hop setting, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports that information to the network through small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic low-latency TDD or low-latency FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between the UEs 115i-115k communicating with the macro base station 105e.

[0037]

[0046] FIG. 2 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be any of the base stations and one of the UEs of FIG. 1. In the case of a restricted association scenario (as described above), the base station 105 may be the small cell base station 105f of FIG. 1, and the UE 115 may be the UE 115c or 115d operating in the coverage area of ​​the base station 105f, and the UE 115c or 115d will be included in the list of accessible UEs for the small cell base station 105f to access the small cell base station 105f. The base station 105 may also be some other type of base station. As shown in FIG. 2, the base station 105 may be equipped with antennas 234a-t and the UE 115 may be equipped with antennas 252a-r to facilitate wireless communication.

[0038]

[0047] At the base station 105, the transmit processor 220 may receive data from a data source 212 and control information from a controller 240, such as a processor. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. In addition, the transmit processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, e.g., for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), as well as a cell-specific reference signal. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, or reference symbols, if applicable, and provide output symbol streams to the modulators (MODs) 232a through 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include precoding.Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

[0039]

[0048] At the UE 115, antennas 252a-252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a-254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain the received symbols from the demodulators 254a-254r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols and provide decoded data for the UE 115 to a data sink 260 and provide decoded control information to a controller 280, such as a processor.

[0040]

[0049] On the uplink, at the UE 115, a transmit processor 264 may receive and process data (e.g., for a physical uplink shared channel (PUSCH)) from a data source 262 and control information (e.g., for a physical uplink control channel (PUCCH)) from a controller 280. In addition, the transmit processor 264 may generate reference symbols for a reference signal. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, uplink signals from the UE 115 may be received by antennas 234, processed by demodulator 232, detected by a MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by the UE 115. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to a controller 240 .

[0041]

[0050] The controllers 240 and 280 may direct operation at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105, or the controller 280 or other processors and modules at the UE 115, may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution shown in Figures 6 and 7 or other processes for the techniques described herein. The memory 242 and the memory 282 may store data and program codes for the base station 105 and the UE 115, respectively. The scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0042]

[0051] In some cases, the UE 115 and the base station 105 may operate in a shared radio frequency spectrum band, which may include a licensed frequency spectrum or an unlicensed (e.g., contention-based) frequency spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or the base station 105 may perform a medium sensing procedure to contend for access to the frequency spectrum, as is conventional. For example, the UE 115 or the base station 105 may perform a listen-before-talk (LBT) or listen-before-transmitting (LBT) procedure, such as a clear channel assessment (CCA), before communicating to determine if a shared channel is available. In some implementations, the CCA may include an energy detection procedure to determine if there are any other active transmissions. For example, the device may infer that a change in a received signal strength indicator (RSSI) on a power meter indicates that the channel is occupied. Specifically, signal power concentrated within some bandwidth and exceeding a predefined noise floor may indicate another wireless transmitter. CCA may also include detection of specific sequences indicative of channel usage. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT procedure may include a wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgment / negative acknowledgment (ACK / NACK) feedback for its own transmitted packets as a proxy for collisions.

[0043]

[0052] 3A is a diagram of a device-to-device (D2D) communication system 360. The D2D communication system 360 includes multiple UEs 364, 366, 368, 370. The D2D communication system 360 may overlap with a cellular communication system, such as a WWAN. Some of the UEs 364, 366, 368, 370 may communicate together in D2D communication using DL / UL WWAN spectrum, some may communicate with a base station 362, and some may do both. For example, as shown in FIG. 3A, the UEs 368, 370 are in D2D communication and the UEs 364, 366 are in D2D communication. The UEs 364, 366 are also in communication with the base station 362. D2D communication may be through one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), and the physical sidelink control channel (PSCCH).

[0044]

[0053] The exemplary methods and apparatus discussed below may be applied to any of a variety of wireless D2D communication systems, such as wireless device-to-device communication systems based on NR, LTE, FlashLinQ, WiMedia, Bluetooth, ZigBee, or Wi-Fi based on the IEEE 802.11 standard. To simplify the discussion, the exemplary methods and apparatus are discussed in the context of NR. However, those skilled in the art will appreciate that the exemplary methods and apparatus are more generally applicable to a variety of other wireless device-to-device communication systems.

[0045]

[0054] D2D communication may be used to provide direct communication between devices. D2D communication allows one device to communicate with another device and transmit data to the other device through allocated resources. One application of D2D communication is vehicle-to-vehicle (V2V) communication and vehicle-to-everything (V2X) communication. Thus, according to V2V communication, a device of a first vehicle can perform D2D communication with a device of another vehicle. According to V2X communication, a device of a vehicle can perform D2D communication with another device, regardless of whether the device is in the vehicle or not.

[0046]

[0055] One type of communication that can be used for V2V communication is dedicated short range communication (DSRC). DSRC is a short-range wireless communication capability, typically based on IEEE 802.11p, similar to Wi-Fi. In DSRC, devices may survey the channel before transmitting. For traffic-related communications (e.g., V2X communications), the 5.9 GHz unlicensed spectrum is generally reserved for communicating intelligent transportation services (ITS). Recently, implementing other types of communication, such as NR communication, for V2V communication is under development. For example, NR D2D can be utilized for V2V communication over licensed and / or unlicensed spectrum.

[0047]

[0056] In a vehicle-to-everything (V2X) wireless communication system, UEs may communicate directly using device-to-device communication, also known as sidelink communication, without using a network entity (e.g., a base station) as an intermediary. In some cases, the UE may operate using a specific transmission mode, such as transmission mode 4, in which resource selection and / or scheduling is performed by the UE rather than a network entity (e.g., a base station). In some aspects, the UE may perform resource selection and / or scheduling by measuring one or more sidelink channels, by decoding sidelink control information (SCI) indicative of channel availability, by determining channel busy rates (CBRs) associated with various sidelink channels, etc.

[0048]

[0057] In transmission mode 4, the UE may generate a sidelink grant and may transmit the sidelink grant in the SCI. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for the next V2X transmission (e.g., V2X data transmission), such as one or more resource blocks to be used for the next V2X transmission, one or more subframes to be used for the next V2X transmission, a modulation and coding scheme (MCS) to be used for the next V2X transmission, etc.

[0049]

[0058] In a V2X communication system, conditions of a sidelink channel used to carry V2X communications may vary significantly and change rapidly due to high mobility of vehicles and UEs associated with the vehicles, significant variations in vehicle traffic at different times and different locations, the wide variety of terrains that vehicles may traverse (e.g., densely populated urban environments, hilly environments, flat environments, etc.). Furthermore, V2X communication systems need to be highly reliable due to, for example, mission-critical safety issues associated with autonomous vehicles. Some techniques and apparatus described herein improve the performance of a V2X communication system by dynamically determining parameters for V2X transmissions based at least in part on dynamic factors associated with one or more vehicles, sidelink channels, etc.

[0050]

[0059] In some aspects, the V2X transmission may be a one-to-many broadcast and / or multicast transmission. In some aspects, the V2X transmission may not require any physical layer feedback from the receiving device, such as an acknowledgement (ACK) or a negative acknowledgement (NACK) feedback. In some aspects, the V2X transmission may be configured with no retransmissions. In some aspects, the V2X transmission may be configured with several retransmissions (e.g., 5 retransmissions). In certain aspects, the retransmissions are automatic, such as without ACK / NACK feedback.

[0051]

[0060] The first UE may communicate with the second UE (and one or more other UEs) using device-to-device (D2D) communications over one or more sidelink channels. In some aspects, the UE may correspond to one or more other UEs described elsewhere herein. The UE may transmit V2X communications using the sidelink channels.

[0052]

[0061] The sidelink channels may include a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH). The sidelink channels may optionally include a physical sidelink feedback channel (PSFCH). The PSCCH may be used to communicate control information similar to a physical downlink control channel (PDCCH) and / or a physical uplink control channel (PUCCH) used for communication with a base station. The PSSCH may be used to communicate data similar to a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH) used for communication with a base station. For example, the PSCCH may carry sidelink control information (SCI), which may indicate various control information used for sidelink communication, such as one or more resources (e.g., time and / or frequency resources), where a transport block (TB) containing data is carried on the PSSCH. The TB may include V2X data such as basic safety messages (BSM), traffic information messages (TIM), signal phase and time (SPAT) messages, MAP messages for conveying geographic road information, cooperative awareness messages (CAM), distributed environment notification messages (DENM), and in-vehicle information (IVI) messages.

[0053]

[0062] In some aspects, the sidelink channel may use a resource pool. For example, a scheduling assignment (e.g., included in the SCI) may be transmitted in a subchannel using specific resource blocks (RBs) over time. In some aspects, a data transmission (e.g., on a PSSCH) associated with a scheduling assignment may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and associated data transmission are not transmitted on adjacent RBs.

[0054]

[0063] In some aspects, the UE may operate using transmission mode 4, in which case resource selection and / or scheduling is performed by the UE, rather than the base station. In some aspects, the UE may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, the UE may measure received signal strength indicator (RSSI) parameters (e.g., sidelink-RSSI, S-RSSI parameters) associated with various sidelink channels, may measure reference signal received power (RSRP) parameters (e.g., PSSCH-RSRP parameters) associated with various sidelink channels, may measure reference signal received quality (RSRQ) parameters (e.g., PSSCH-RSRQ parameters) associated with various sidelink channels, etc., and may select a channel for transmission of V2X communications based at least in part on the measurement(s).

[0055]

[0064] Additionally or alternatively, the UE may perform resource selection and / or scheduling using the SCI received in the PSCCH, which may indicate occupied resources, channel parameters, etc. Additionally or alternatively, the UE may perform resource selection and / or scheduling by determining a Channel Busy Rate (CBR) associated with various sidelink channels, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE may use for a particular set of subframes).

[0056]

[0065] In transmission mode 4, the UE may generate a sidelink grant and transmit the grant in the SCI. The sidelink grant may indicate one or more parameters (e.g., transmission parameters) to be used for the next V2X transmission, such as, for example, one or more resource blocks to be used for the next V2X transmission on the PSSCH (e.g., for the TB), one or more subframes to be used for the next V2X transmission, a modulation and coding scheme (MCS) to be used for the next V2X transmission, etc. In some aspects, the UE may generate a sidelink grant indicating one or more parameters for semi-persistent scheduling (SPS), such as a periodicity of the V2X transmission (e.g., periodic V2X messages such as safety messages). Additionally or alternatively, the UE may generate a sidelink grant for event-driven scheduling, such as for on-demand V2X messages.

[0057]

[0066] In a V2X communication system, conditions of a sidelink channel used to carry V2X communications may vary significantly and change rapidly due to high mobility of vehicles and UEs associated with the vehicles, significant variations in vehicle traffic at different times and different locations, the wide variety of terrains that vehicles may traverse (e.g., densely populated urban environments, hilly environments, flat environments, etc.). Furthermore, V2X communication systems need to be highly reliable due to, for example, mission-critical safety issues associated with autonomous vehicles. Some techniques and apparatus described herein improve the performance of a V2X communication system by dynamically determining parameters for V2X transmissions based at least in part on dynamic factors associated with one or more vehicles, sidelink channels, etc.

[0058]

[0067] In some implementations, a UE may be capable of performing autonomous resource selection for V2X transmissions in accordance with various aspects of the present disclosure.

[0059]

[0068] For example, the UE may determine a limitation on the number of resource blocks (RBs) allowed to be used by the UE for V2X transmissions. In some aspects, the UE may determine the limitation based at least in part on a congestion level of one or more sidelink channels, which may be determined at least in part based on measurements of one or more sidelink channels (e.g., for S-RSSI, PSSCH-RSRP, etc.), reception of SCI associated with one or more sidelink channels, etc. For example, the UE may determine a channel busy ratio (CBR) for a sidelink channel associated with a time n at which resource selection is triggered for the UE (e.g., CBR(n-100,n-1), where n-100 indicates a start of a time period and n-1 indicates an end of a time period), and may determine a maximum number of RBs allowed for use by the UE at time n based at least in part on the CBR. Additionally or alternatively, the UE may determine the limit on the number of RBs by determining a maximum number of RBs allowed for use by the UE associated with time n (e.g., CRlimit(n)) and subtracting the number of RBs already used or scheduled by the UE associated with time n (e.g., CR(na,n+b), where na indicates the start of the time period and n+b indicates the end of the time period).

[0060]

[0069] The UE may determine one or more parameters for the V2X transmission based at least in part on the limitation on the number of RBs. In some aspects, the one or more parameters may be referred to as one or more transmission parameters and / or one or more V2X transmission parameters. As shown, the one or more parameters may include a modulation and coding scheme (MCS) for the V2X transmission, a number of transport blocks (TBs) for the V2X transmission, a number of RBs per TB for the V2X transmission, a retransmission configuration for the V2X transmission, etc. In some aspects, the UE may determine the one or more parameters such that the number of RBs for the V2X transmission does not exceed the limitation on the number of RBs.

[0061]

[0070] In one example, if a UE selects an MCS with a lower index value for a V2X transmission (e.g., allowing fewer bits per symbol), the V2X transmission will require more TBs and corresponding RBs than if the same V2X transmission were to use an MCS with a higher index value (e.g., allowing more bits per symbol). However, using an MCS with a lower index value for a V2X transmission may increase the range of the V2X transmission and / or improve the reliability of the V2X transmission compared to using an MCS with a higher index value. Thus, in some aspects, if the limitation on the number of RBs is relatively high (e.g., above a threshold), the UE may select an MCS with a lower index value, and if the limitation on the number of RBs is relatively low (e.g., below a threshold), the UE may select an MCS with a higher index value. In some aspects, the UE may select from multiple different MCS index values, and different MCS index values ​​may be associated with different thresholds for the limitation on the number of RBs.

[0062]

[0071] As another example, if a UE configures a retransmission configuration to enable retransmission for a V2X transmission, that V2X transmission will require more TBs and corresponding RBs than if the UE were to configure a retransmission configuration to disable retransmission for the same V2X transmission. However, enabling retransmission for a V2X transmission may increase the range of the V2X transmission and / or improve the reliability of the V2X transmission compared to disabling retransmission for the V2X transmission. Thus, in some aspects, if the limit on the number of RBs is relatively high (e.g., above a threshold), the UE may enable retransmission, and if the limit on the number of RBs is relatively low (e.g., below a threshold), the UE may disable retransmission. In some aspects, the UE may select from multiple different qualities of retransmission (e.g., one retransmission, two retransmissions, etc.), and different qualities of retransmission may be associated with different thresholds for the limit on the number of RBs.

[0063]

[0072] In some aspects, the UE may select one or more parameters to increase or maximize the range for a V2X transmission (e.g., the distance that may be covered by a V2X transmission and corresponding retransmissions) subject to limitations on the number of RBs, as described in more detail below with respect to Figure 5. In this manner, the UE may improve reliability, increase safety, increase the likelihood of successful reception of the V2X transmission, etc., while operating according to limitations on the number of RBs allowed for the V2X transmission.

[0064]

[0073] In a V2X communication system, sidelink channel conditions may vary significantly at different times, in different geographic locations, on different frequencies, etc. Thus, the UE may dynamically determine one or more parameters for a V2X transmission based at least in part on conditions existing at the time the V2X transmission is scheduled. In some aspects, the UE may determine one or more transmission parameters based at least in part on dynamic factors associated with the UE and / or a vehicle associated with the UE (e.g., network traffic demands, congestion associated with one or more applications of the UE, etc.). Additionally or alternatively, the UE may determine one or more transmission parameters based at least in part on dynamic factors associated with a wireless network over which the V2X transmission will be transmitted (e.g., a congestion level associated with the wireless network, a carrier frequency over which the V2X transmission will be transmitted, a priority of the V2X transmission on the wireless network, etc.). In this manner, the UE may improve or optimize transmission of V2X messages under changing conditions.

[0065]

[0074] Additionally or alternatively, the UE may determine one or more V2X transmission parameters based at least in part on the selected frequency or frequencies. For example, different frequencies may be associated with different CBR values ​​and thus different RB number limitations permitted for use by the UE. Additionally or alternatively, different transmission parameter combinations may result in different performance at different frequencies, which the UE may use as a factor when determining the one or more transmission parameters.

[0066]

[0075] In some aspects, the UE may determine one or more transmission parameters based at least in part on a network traffic requirement associated with one or more applications of the UE. For example, if a first UE has a relatively high network traffic requirement (e.g., the number of requested V2X transmissions is equal to or greater than a threshold), the UE may use fewer RBs per V2X transmission. Conversely, if the UE has a relatively low network traffic requirement (e.g., the number of requested V2X transmissions is equal to or less than a threshold), the UE may use more RBs per V2X transmission. The UE may configure fewer RBs per V2X transmission by using a higher MCS index, by disabling retransmissions or configuring fewer retransmissions, by using fewer TBs, and / or by using fewer RBs per TB. Conversely, the UE may configure more RBs per V2X transmission by using a lower MCS index, by enabling retransmissions or configuring more retransmissions, by using more TBs, and / or by using more RBs per TB.

[0067]

[0076] Additionally or alternatively, the UE may determine the one or more transmission parameters based at least in part on a congestion level associated with the wireless network over which the V2X transmission is to be transmitted (e.g., congestion levels of a sidelink channel and / or one or more frequencies over which the V2X transmission is to be transmitted). For example, if the wireless network has a relatively high congestion level, the UE may use fewer RBs per V2X transmission. Conversely, if the wireless network has a relatively low congestion level, the UE may use more RBs per V2X transmission. In some aspects, the UE may determine the congestion level based at least in part on a CBR, resource limitations (e.g., rate control parameters, power control parameters, congestion control parameters, etc.), measured parameters (e.g., energy levels) of the wireless network, etc.

[0068]

[0077] The UE may transmit a V2X transmission (e.g., to a second UE and / or one or more other UEs) based at least in part on one or more parameters. For example, the UE may modulate and / or code the V2X transmission using a selected MCS, transmit the V2X transmission using a selected number of TBs, transmit the V2X transmission using a selected number of RBs per TB, retransmit or prevent retransmission of the V2X transmission according to a selected retransmission configuration, transmit the V2X transmission on a selected carrier frequency, etc. By taking dynamic factors into account when determining the above transmission parameter(s), the UE may improve the performance (e.g., transmission range) of the V2X transmission subject to constraints on the V2X transmission. For example, in some cases, the UE may transmit the V2X transmission using an MCS with a high index rather than dropping the V2X transmission.

[0069]

[0078] 3B is an example diagram 300 illustrating device-to-device communication. A first device 312 (e.g., a UE 312) may be in a first vehicle 310 and thus move with the first vehicle 310. A second device 332 (e.g., another UE 332) may be in a second vehicle 330. In another aspect, the first device 312 may exist independently of the first vehicle 310 or may be part of the first vehicle 310. The second device 332 may exist independently of the second vehicle 330 or may be part of the second vehicle 330. The first device 312 and the second device 332 may be connected to a network entity, such as in a connected mode with a base station 350. The first device 312 and the second device 332 may also be configured to perform D2D communication with each other through NR. The first device 312 and the second device 332 can also perform short-range communications with each other via IEEE 802.11p.

[0070]

[0079] The vehicles may include autonomous vehicles, semi-autonomous vehicles, non-autonomous vehicles, etc. Although both UEs in FIG. 3B are shown as associated with a vehicle, in some aspects one or more of the UEs may not be associated with a vehicle. For example, the UEs may be associated with infrastructure (e.g., traffic infrastructure), such as traffic signals, lane signals, sensors, traffic controller systems, etc.

[0071]

[0080] NR V2V communications may provide more reliable performance than LTE V2V by providing a more history-based calculation of congestion and / or a more limited reliance on future periodic transmissions. Although the following discussion refers to NR V2V communications by way of example and not by way of limitation, NR D2D communications is similar to LTE V2V communications, and therefore the following discussion may also apply to NR and LTE D2D communications.

[0072]

[0081] Congestion may occur in NR V2V communications, for example, due to increased network traffic. Congestion control may be implemented to control network congestion via some parameters for communications over NR V2V based on the level of congestion. For example, in certain cases, there may be no centralized entity to perform spectrum congestion control. Congestion control may be performed without a centralized entity (e.g., eNB) to manage admission control and / or radio resource utilization (e.g., out-of-network coverage operation and / or decentralized resource selection / reselection procedures). Without a centralized entity to manage network resources and device communications, collisions of different communications may occur. Too many collisions may adversely affect the performance of the communications system. For example, collisions may occur when resources are not properly allocated to different device communications, resulting in some devices not having enough resources for communication. Depending on the communications system and / or the channel access method of the communications system, the devices may not be able to handle network congestion. For example, the number of communications that can be reliably performed successfully in a network may vary depending on the type of communications system. The decentralized congestion control may be based on the physical layer of 802.11p and may be generalized to achieve coexistence of various technologies. Thus, in systems without a centralized entity for managing congestion, a technology-neutral decentralized congestion control may be desirable. In some aspects, technology-specific improvements for the decentralized congestion control may be provided.

[0073]

[0082] In an aspect, congestion control may be based on a channel busy ratio (CBR) and / or channel utilization. The CBR may represent the percentage of resources that are busy. The channel utilization may represent the percentage of the channel that is utilized for communication. The CBR and channel utilization may be technology neutral as described below. Although distributed congestion control for 802.11p technology may be derived based on technology neutral congestion control, a technology neutral approach for distributed congestion control may be used for NR V2V.

[0074]

[0083] Each UE may estimate channel utilization based on the CBR, which may be an estimate of the percentage of a resource that is considered busy / utilized. In an aspect, a resource may be considered busy and / or utilized if a signal is decoded on such resource or if the energy in such resource is higher than an energy threshold.

[0075]

[0084] The original V2X communication uses WLAN technology and operates directly between vehicle-to-vehicle (V2V) and traffic infrastructure (V2I), forming a vehicular ad-hoc network when two V2X senders come within range of each other. Thus, it does not require any communication infrastructure for vehicles to communicate, which helps ensure safety in remote or undeveloped areas. WLAN is particularly suitable for V2X communication because of its low latency. V2X communication includes messages known as Cooperative Awareness Messages (CAM) or Basic Safety Messages (BSM), and Distributed Environment Notification Messages (DENM). Other roadside infrastructure related messages are Signal Phase and Timing Messages (SPAT), Vehicle Information Messages (IVI), and Service Request Messages (SRM). The data volume of these messages is very small. The wireless technology is part of the WLAN IEEE 802.11 family of standards, known in the United States as Wireless Access in Vehicular Environments (WAVE) and in Europe as ITS-G5. https: / / en.wikipedia.org / wiki / Vehicle-to-everything-cite_note-8. To complement the direct communication mode, vehicles can be equipped with traditional cellular communication technologies supporting V2N based services. This expansion with V2N has been achieved in Europe under the C-ITS platform umbrella with cellular and broadcast systems (TMC / DAB+).

[0076]

[0085] Route history (also called route history information) is included in the BSM (e.g., BSM report) to indicate vehicle position information. Route history information indicates the last position information or information about a series of past positions of the vehicle. Route history information is traditionally used for road geometry estimation and target classification. In the current implementation, route history information indicates the last 5 or 15 positions of the vehicle and is included in every BSM.

[0077]

[0086] Additional information is sometimes included in the BSM. For example, a certificate (also known as a full certificate) is typically appended to the BSM at defined intervals, such as 450 ms. Additionally, limited certificate information, called a digest of the certificate, is appended to other BSMs that are sent at shorter intervals, such as 100 ms intervals, and do not assume congestion control. A receiving device may be able to utilize the digest (referred to herein as digest information or partial certificate information) to find the full certificate (referred to herein as certificate information) that corresponds to the digest. The digest may be 8 bytes in some implementations and may include a summary of the material information of the certificate information and / or may indicate or identify the certificate information. In certain implementations, the digest includes or indicates message source authentication information, integrity check information, or both.

[0078]

[0087] Current implementations that include Path History (PH) and full certificates in many BSMs are inefficient and bandwidth intensive. This is especially true since BSMs constitute a large portion of bandwidth usage in such scenarios. For example, BSMs constitute a large portion of the load on ITS bandwidth, which is ever more scarce.

[0079]

[0088] Current implementations that include information about the last 5 or 15 locations in each BSM occupy approximately 43 or 123 bytes. A complete authentication is approximately 100 bytes (e.g., 125 bytes) and is included at a frequency of 2 Hz (every 0.5 seconds). Thus, the overhead caused by the inclusion of route history information and certificate information can account for approximately 47-58% of the BSM message size.

[0080]

[0089] In aspects described herein, the wireless communication device selectively includes certain information in a safety message in response to a corresponding trigger condition. For example, a host vehicle (HV) includes PH information in a BSM or CAM / DENM based on one or more conditions being met. The conditions may include new vehicle detection, collision zone identification, channel parameters, timing, etc. As another example, a host vehicle includes certificate information in a BSM or CAM / DENM based on one or more conditions being met. The conditions may include new vehicle detection, collision zone identification, channel parameters, timing, critical events, etc.

[0081]

[0090] As an illustrative and non-limiting example, the HV selectively includes PH information in its BSM only if it detects an actual new vehicle in its collision zone vicinity. Other vehicles already within the broadcast range of the HV can use previously received BSMs to build a route history trajectory for the HV. The HV can also include PH points during poor channel conditions where there is uncertainty around the reception of the HV's past BSMs by another device (e.g., a Remote Vehicle (RV)). The HV can take a similar approach for the inclusion of complete certificate information and can use the same or different parameters.

[0082]

[0091] Aspects described herein allow for reduced over-the-air (OTA) congestion by including PH information and complete certificate information based on conditions that may actually lead to adverse events or when additional information is needed. These aspects reduce congestion by reducing the inclusion of information in safety messages and may be utilized with C-SAE (e.g., SAE standards J3161 / 1 and J2945 / 1) and / or ETSI CAM.

[0083]

[0092] 4 illustrates an example of a wireless communication system 400 supporting enhanced safety message reporting operations according to aspects of the present disclosure. In some examples, the wireless communication system 400 may implement aspects of the wireless communication system 100. For example, the wireless communication system 400 may include UEs 115, 115A, and 115B. The enhanced safety message (e.g., BSM) reporting operations may reduce signaling overhead and latency and increase throughput. Thus, network and device performance may be improved.

[0084]

[0093] The UEs 115, 115A, and 115B may be configured to communicate over one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although portions of FR1 are higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "mmWave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmWave" band by the International Telecommunications Union (ITU).

[0085]

[0094] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "mmWave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0086]

[0095] It should be noted that the SCS may be equal to 15, 30, 60, or 120 kHz for some data channels. The UEs 115, 115A, and 115B may be configured to communicate over one or more component carriers (CCs), such as an exemplary first CC 481, a second CC 482, a third CC 483, and a fourth CC 484. Although four CCs are shown, this is for illustrative purposes only, and more or less than four CCs may be used. One or more CCs may be used to communicate control channel transmissions, data channel transmissions, and / or sidelink channel transmissions.

[0087]

[0096] Such transmissions may include a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), or a physical sidelink feedback channel (PSFCH). Such transmissions may be scheduled by aperiodic and / or periodic grants.

[0088]

[0097] Each periodic grant may have a corresponding configuration, such as configuration parameters / settings. A periodic grant configuration may include configured grant (CG) configurations and settings. Additionally or alternatively, one or more periodic grants (e.g., their CGs) may have or be assigned a CC ID, such as an intended CC ID.

[0089]

[0098] Each CC may have a corresponding configuration, such as configuration parameters / settings. The configuration may include a bandwidth, a bandwidth part, a HARQ process, a TCI state, an RS, a control channel resource, a data channel resource, or a combination thereof. Additionally or alternatively, one or more CCs may have or be assigned a Cell ID, a Bandwidth Part (BWP) ID, or both. The Cell ID may include a unique cell ID for the CC, a virtual cell ID, or a specific cell ID of a specific CC among the multiple CCs. Additionally or alternatively, one or more CCs may have or be assigned a HARQ ID. Each CC may also have a corresponding management function, such as beam management, BWP switching function, or both. In some implementations, two or more CCs are quasi-colocated such that the CCs have the same beam and / or the same symbols.

[0090]

[0099] In some implementations, control information may be communicated via the UEs 115, 115A, and 115B. For example, the control information may be communicated using a MAC-CE transmission, an RRC transmission, a downlink control information (DCI) transmission, an uplink control information (UCI) transmission, a sidelink control information (SCI) transmission, another transmission, or a combination thereof.

[0091]

[0100] The UE 115 may include various components (e.g., structural components, hardware components) used to perform one or more functions described herein. For example, these components may include a processor 402, a memory 404, a transmitter 410, a receiver 412, an encoder 413, a decoder 414, a device-to-device (D2D) communications manager 415, a BSM manager 416, and antennas 252a-r. The processor 402 may be configured to execute instructions stored in the memory 404 to perform operations described herein. In some implementations, the processor 402 includes or corresponds to the controller / processor 280, and the memory 404 includes or corresponds to the memory 282. The memory 404 may also be configured to store device information data 406, channel condition data 408, trigger condition data 442, configuration data 444, or combinations thereof, as further described herein.

[0092]

[0101] The device information data 406 includes or corresponds to data associated with or corresponding to the UE 115 and other devices involved in device-to-device communication operations. For example, the device information data 406 may include UE-related information such as route history information, certificate information, digest information, temporary ID information, etc. The device information data 406 may further include other UE-related information (e.g., other UEs, such as UEs 115A and 115B), such as route history information of other devices, certificate information of other devices, digest information, temporary ID information of other devices, temporary ID information history, etc. Information for other devices may be associated with each other or otherwise correlated with other information to create a local dynamic map (LDM). The LDM may include information about devices that are persistent (non-temporary identifiers) or that allow for identification of devices on a persistent or non-temporary basis.

[0093]

[0102] The channel condition data 408 includes or corresponds to data related to or corresponding to channel quality or congestion conditions for device-to-device communication operations. For example, the channel condition data 408 may include channel quality measurements or determinations. The channel condition data 408 may include or correspond to received power thresholds or ranges, or received quality thresholds or ranges. For example, the channel condition data 408 may utilize a channel quality indicator (CQI), RSRP, RSRQ, Signal-to-interference-plus-noise ratio (SINR), etc. The channel condition data 408 may further include operations for determining or adjusting quality conditions. For example, the channel condition data 408 includes operations for determining quality conditions based on one or more parameters, such as channel congestion. To illustrate, the UE 115 may utilize a packer error rate (PER) to determine congestion.

[0094]

[0103] The trigger condition data 442 includes or corresponds to data indicating or corresponding to a trigger condition for inclusion of information in the BSM. For example, the trigger condition data 442 may include data indicating a particular trigger condition parameter value or range of values ​​where route history information is included in the BSM, certificate information is included in the BSM, or both are included in the BSM. Additionally or alternatively, the trigger condition data 442 may include data indicating a particular trigger condition parameter value or range of values ​​where route history information is not included in the BSM, certificate information is not included in the BSM, or neither is included in the BSM. As illustrative examples of types of trigger conditions, the trigger conditions may include a timing condition, a new device determination condition, a collision zone detection condition, a channel quality condition (e.g., CQI), a congestion related condition (e.g., PER), or combinations thereof. The conditions may be used in succession or parallel to one another. For example, multiple conditions may have to be met to include route history information in the BSM, and the UE 115 may determine whether either A or B is met before determining whether C or D is met only when at least one of A or B is met. As another example, certification information may be included in a secure message using additional conditions or conditions different from those used for route history information.

[0095]

[0104] The configuration data 444 includes or corresponds to data associated with enhanced BSM feedback and reporting operations for sidelink communications. The configuration data 444 may include one or more types of BSM feedback operating modes and / or thresholds or conditions for switching between BSM feedback modes and / or configurations. For example, the configuration data 444 may have data indicating different thresholds for different BSM feedback modes, such as a reduced PH reporting mode, a reduced certificate reporting mode, or a collision zone only reporting mode.

[0096]

[0105] The transmitter 410 is configured to transmit data to one or more other devices, and the receiver 412 is configured to receive data from one or more other devices. For example, the transmitter 410 may transmit data and the receiver 412 may receive data via a network, such as a wired network, a wireless network, or a combination thereof. For example, the UE 115 may be configured to transmit and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that enables two or more electronic devices to communicate. In some implementations, the transmitter 410 and the receiver 412 may be replaced with a transceiver. Additionally or alternatively, the transmitter 410, the receiver 412, or both may include or correspond to one or more components of the UE 115 described with reference to FIG. 2.

[0097]

[0106] The encoder 413 and the decoder 414 may be configured to encode and decode data for transmission. The D2D communications manager 415 may be configured to determine and perform D2D communication operations, such as for V2X operations over Wi-Fi or cellular. For example, the D2D communications manager 415 is configured to determine D2D communication timing, message generation, etc. As another example, the D2D communications manager 415 is configured to determine whether to perform an enhanced BSM reporting or feedback operation. In some implementations, the D2D communications manager 415 is configured to determine in which particular BSM reporting or feedback mode to operate.

[0098]

[0107] The BSM manager 416 may be configured to determine a BSM mode operation and perform that operation. For example, the BSM manager 416 may be configured to determine which one or more resources to use for BSM feedback, such as when and where to perform a BSM transmission. As another example, the BSM manager 416 may be configured to determine whether to include route history information or certificate information in a particular BSM. In implementations in which it is determined that additional information should be included in the BSM, the BSM manager 416 may be configured to determine what type of information to include and how long.

[0099]

[0108] The UEs 115A and 115B include a processor 430, a memory 432, a transmitter 434, a receiver 436, an encoder 437, a decoder 438, a D2D communications manager 439, a BSM manager 440, and antennas 234a-t. The processor 430 may be configured to execute instructions stored in the memory 432 to perform operations described herein. In some implementations, the processor 430 includes or corresponds to the controller / processor 240, and the memory 432 includes or corresponds to the memory 242. The memory 432, like the UE 115, may be configured to store device information data 406, channel condition data 408, trigger condition data 442, configuration data 444, or a combination thereof, as further described herein.

[0100]

[0109] The transmitter 434 is configured to transmit data to one or more other devices, and the receiver 436 is configured to receive data from one or more other devices. For example, the transmitter 434 may transmit data, and the receiver 436 may receive data over a network, such as a wired network, a wireless network, or a combination thereof. For example, the UEs 115A and 115B may be configured to transmit and / or receive data over a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that enables two or more electronic devices to communicate. In some implementations, the transmitter 434 and the receiver 436 may be replaced with a transceiver. Additionally or alternatively, the transmitter 434, the receiver 436, or both may include or correspond to one or more components of the UE 115 described with reference to FIG. 2.

[0101]

[0110] The encoder 437 and the decoder 438 may include the same functionality as described with reference to the encoder 413 and the decoder 414, respectively. The D2D communications manager 439 may include similar functionality as described with reference to the D2D communications manager 415. The BSM manager 440 may include similar functionality as described with reference to the BSM manager 416.

[0102]

[0111] During operation of the wireless communication system 400, the UE 115A may determine that the UE 115 has enhanced HARQ feedback operation capability. For example, the UE 115 may transmit a message 448 including an extended resource reservation indicator 490 (e.g., a HARQ feedback for sidelink channel indicator). The indicator 490 may indicate an extended HARQ feedback operation capability for unlicensed spectrum and / or sidelink channel operation, or a particular type or mode of HARQ feedback operation. In some implementations, a network entity (e.g., the network entity 405) or the UE 115A / B transmits control information to indicate to the UE 115 that an extended HARQ feedback operation and / or a particular type of extended HARQ feedback operation should be used. For example, in some implementations, the message 448 (or another message, such as a configuration transmission 450) is transmitted by the UE 115A / B or the network entity 405. The configuration transmission 450 may include or indicate using an extended HARQ feedback operation or adjusting or implementing a setting for a particular type of extended HARQ feedback operation. For example, the configuration transmission 450 may include trigger condition data 442, settings data 444, or both, as shown in the example of FIG.

[0103]

[0112] During operation, devices of the wireless communication system 400 perform enhanced safety message (e.g., BSM) reporting operations. For example, the UEs 115, 115A, 115B exchange transmissions via D2D communication, such as via a sidelink channel. In the example of FIG. 4, the UE 115A transmits a message 452. The message 452 may include or correspond to a beacon type message or a broadcast message. In some implementations, the message 452 includes a BSM.

[0104]

[0113] The UE 115 may receive the message 452 and may perform one or more evaluations or decisions on or using the message 452. The UE 115 may determine a location of the UE 115A based on the message 452 and may use the location to determine whether the UE 115A is or will be within a collision detection zone of the UE 115. Additionally or alternatively, the UE 115 may determine an identifier of the first UE 115A. For example, the UE 115 may extract or parse a temporary identifier from the message 452 and use the temporary identifier to determine whether the UE 115A is “new” to the UE 115, such as not being in a map of devices maintained by the UE 115. In certain implementations, the UE 115 may further reference or generate an LDM based on the message and use the LDM to determine whether the first UE 115A is new. To illustrate, the UE 115 may correlate the information in message 452 with previously received information to determine whether the UE 115a, such as its temporary ID, maps to or corresponds to a previous temporary or non-transient identifier in the LDM. Based on this determination and that a trigger condition has been identified, such as a new device or a device in the collision zone of the UE 115, the UE 115 may decide to include the information in the next BSM. Examples of trigger conditions are further described with reference to FIG. 5.

[0105]

[0114] As shown in the example of FIG. 4, UE 115 determines to include route history information, a complete certificate, or both in a next safety message (e.g., BSM). UE 115 generates and transmits a safety message including the route history information and / or the complete certificate. For example, UE 115 broadcasts a safety message 454 (e.g., BSM). One of more other UEs, such as UE 115A and UE 115B, may receive the safety message 454 and extract the route history information and the complete certificate. The route history information and / or the complete certificate may enable the receiving UE to identify new devices and / or avoid and reduce collisions or near collisions. By the UE selectively including the route history information and / or the certificate information, network signaling overhead may be reduced.

[0106]

[0115] Thus, the UEs 115, 115A, and 115B may be able to perform safety message operations (e.g., BSM operations) more efficiently. Thus, FIG. 4 illustrates an enhanced safety message reporting operation. Using an enhanced safety message reporting operation may enable improvements when operating in D2D communications. Performing an enhanced safety message reporting operation enables reduced bandwidth / spectrum wastage when transmitting and receiving safety messages, thus enabling enhanced UE and network performance by increasing throughput and reducing latency. Efficiency is achieved without reducing the safety or effectiveness of safety message transmissions, since safety message transmissions are still transmitted under certain conditions that are more likely to lead to collisions.

[0107]

[0116] FIG. 5 illustrates a diagram of an example wireless communication system supporting enhanced safety message reporting operations according to one or more aspects. The example of FIG. 5 includes devices similar to those described in FIG. 1, FIG. 2, and FIG. 4, such as UEs 115, 115A, and 115B. Devices such as UEs 115a-115c of FIG. 5 may include one or more of the components described in FIG. 2 and FIG. 4. In FIG. 5, these devices may utilize antennas 252a-r, transmitter 410, receiver 412, encoder 413, and / or decoder 414, or may utilize antennas 234a-t, transmitter 434, receiver 436, encoder 437, and / or decoder 438 to communicate transmissions and receptions.

[0108]

[0117]

[0036] Referring to Figure 5, Figure 5 is a diagram 500 of dynamic information inclusion in BSM operations. Although the example shown in Figure 5 shows multiple vehicle UEs or HVs, in other implementations, operations may occur between other wireless communication devices, such as non-vehicle UEs, base stations, etc.

[0109]

[0118] At 510, the first UE 115a transmits a message. For example, the first UE 115a is connected to the second UE 115b and transmits a unicast message to the second UE 115b. As another example, the first UE 115a transmits a broadcast message and at least the second UE 115b receives the broadcast message. The message may be transmitted over a sidelink communication channel or a D2D communication channel. In some implementations, the message may include or correspond to a BSM or beacon transmission.

[0110]

[0119] In certain implementations, the message is a BSM. In some such implementations, the BSM includes a PH or certificate information. In some other implementations, the BSM does not include a PH or certificate information. In some such implementations, the first UE 115a may determine not to include a PH or certificate information in the BSM based on determining that the trigger condition is not met.

[0111]

[0120] The second UE 115b may receive and decode the message. The second UE 115b may update or add device-related information for the first UE 115a to its stored information. For example, the second UE 115b may determine the location of the first UE 115a based on the message or update its records (e.g., LDM) based on the message. After receiving the message, the second UE 115b may decide to transmit a BSM. For example, the second UE 115b may decide to transmit a BSM based on timing, such as in response to a normal operating procedure for transmitting a BSM every X durations. As another example, the second UE 115b may decide to transmit a BSM in response to a particular trigger, such as determining that a new device is present (e.g., a new temporary ID) or determining that a device is in proximity to the second UE 115b.

[0112]

[0121] At 515, the second UE 115b determines whether to include information in the outgoing BSM based on evaluating one or more trigger conditions. For example, the BSM manager 416 or 440 of the second UE 115b determines whether one or more trigger conditions for inclusion of PH information are met in connection with determining to transmit the BSM. In some implementations, the second UE 115b determines how much PH information to include, such as a certain number of past positions. Additionally or alternatively, the second UE 115b determines how long to transmit the PH information. In such implementations, the second UE 115b may determine based on any of how many trigger conditions are met, which trigger conditions are met, or a combination thereof. For example, when a new device condition is met, the second UE 115b may decide to transmit more or 15 past positions for a shorter period of time compared to when a collision zone detection condition is met, and the second UE 115b may transmit 5 past positions for a longer period of time (e.g., until the collision is resolved / avoided).

[0113]

[0122] At 520, the second UE 115b transmits a BSM with the PH information. For example, the BSM manager 416 or 440 of the second UE 115b generates a BSM including the route history information and broadcasts it to other devices, such as the first and third UEs 115a and 115c.

[0114]

[0123] From 520 to 525, the second UE 115b transmits additional BSMs with PH information. For example, the BSM manager 416 or 440 of the second UE 115b generates and broadcasts one or more second BSMs including the route history information to other devices. The PH information of the one or more second BSMs may be the same as or different from the PH information of the BSM. For example, the PH information of the one or more second BSMs may include a smaller number of PHs.

[0115]

[0124] At 530, the second UE 115b uses a BSM transmission. For example, the BSM manager 416 or 440 of the second UE 115b generates and broadcasts to other devices a third BSM that does not include the route history information. The second UE 115b can determine not to include the route history information based on satisfying the duration or number of BSMs with the route history information from the determination at 515. In some such implementations, the second UE 115b can further determine not to include the PH or certificate information in the BSM based on determining that the trigger condition is not satisfied at 530.

[0116]

[0125] At 535, the third UE 115c transmits a message (e.g., a second message). For example, the third UE 115c is connected to the second UE 115b and transmits a unicast message to the second UE 115b. As another example, the third UE 115c transmits a broadcast message and at least the second UE 115b receives the broadcast message. The message may be transmitted over a sidelink communication channel or a D2D communication channel. In some implementations, the message may include or correspond to a BSM or beacon transmission.

[0117]

[0126] In certain implementations, the message is a BSM. In some such implementations, the BSM includes the PH or certificate information. In some other implementations, the BSM does not include the PH or certificate information. In some such implementations, the third UE 115c may determine not to include the PH or certificate information in the BSM based on determining that the trigger condition is not met.

[0118]

[0127] The second UE 115b may receive and decode the message. The second UE 115b may update or add device-related information for the third UE 115c to its stored information. For example, the second UE 115b may determine the location of the third UE 115c based on the message or update its records (e.g., LDM) based on the message. After receiving the message, the second UE 115b may decide to transmit a BSM. For example, the second UE 115b may decide to transmit a BSM based on timing, such as in response to a normal operating procedure for transmitting a BSM every X durations. As another example, the second UE 115b may decide to transmit a BSM in response to a particular trigger, such as determining that a new device is present (e.g., a new temporary ID) or determining that a device is in proximity to the second UE 115b.

[0119]

[0128] At 540, the second UE 115b determines whether to include information in the outgoing BSM based on evaluating one or more trigger conditions. For example, the BSM manager 416 or 440 of the second UE 115b determines whether one or more trigger conditions for inclusion of certificate information are met in connection with determining to send a BSM. In some implementations, the second UE 115b determines how much certificate information to include, such as the complete certificate (full certificate information). Additionally or alternatively, the second UE 115b determines how long the certificate information should be sent. In such implementations, the second UE 115b may determine based on any of how many trigger conditions are met, which trigger conditions are met, or a combination thereof. For example, when a new device condition is met, the second UE 115b may decide to transmit more or 15 past positions for a shorter period of time compared to when a collision zone detection condition is met, and the second UE 115b may transmit 5 past positions for a longer period of time (e.g., until the collision is resolved / avoided).

[0120]

[0129] At 545, the second UE 115b transmits a BSM with the certificate information. For example, the BSM manager 416 or 440 of the second UE 115b generates a fourth BSM including the certificate information and broadcasts it to other devices, such as the first and third UEs 115a and 115c.

[0121]

[0130] From 545 to 550, the second UE 115b transmits an additional BSM with certificate information. For example, the BSM manager 416 or 440 of the second UE 115b generates and broadcasts one or more fifth BSMs including the route history information to other devices. The certificate information of the one or more fifth BSMs may be the same as or different from the certificate information of the fourth BSM. For example, the certificate information of the one or more fifth BSMs may include digest information.

[0122]

[0131] In some implementations, the trigger condition for the inclusion of additional device-related information in the safety message corresponds to the detection of a "new" vehicle in the collision zone of the transmitting device. Since devices use temporary IDs that change periodically, such as every 5 minutes, the receipt of a new temporary ID does not necessarily indicate a new vehicle. Thus, the received temporary ID should be correlated with the dynamics (past or predicted movements) of other devices or vehicles to exclude that the "new" temporary ID does not belong to an existing known nearby device or vehicle that the transmitting device already knows. In some such implementations, the transmitting device utilizes an LDM to determine whether the new temporary ID corresponds to a new device or to a temporary ID change.

[0123]

[0132] In some implementations, the collision zone trigger condition is based on distance, time to collision (TTC), or both. As an illustrative and non-limiting example, the collision zone trigger condition is based on both distance and TTC conditions. Below is an exemplary formula for the distance and TTC conditions between two devices or entities A and B: Δx AB ≦X and 0≦TTC AB < Y. The distance threshold for the collision zone may be static, dynamic, and / or based on speed or operating conditions. In addition, the TTC condition may be static or dynamic and based on the size of the collision zone. The distance and TTC between the devices may be calculated based on the speed and trajectory of the transmitting device and the estimated trajectory of the other device.

[0124]

[0133] In some implementations, once the transmitting device decides to include PH information or certificate information in a BSM, the transmitting device can continue to include the PH information or certificate information in subsequent BSMs to increase the likelihood of reception. The transmitting device can determine the number of BSMs in which to include additional information or can determine the time period in which to include additional information in the BSM. As an illustrative and non-limiting example, the transmitting device can use the following formula to determine how long to include such additional information:

[0125]

number

[0126] In the above formula,

[0127]

number

[0128] is the channel quality index, and N(k) is the number of vehicles within range of a particular vehicle, V A The range can be determined based on the PER, such as by vPERRange. A is the inter-transmission time between subsequent BSM transmissions of the vehicle (V A ), where ITT A ∈{100,...,600}ms. N can be chosen arbitrarily, e.g., N=50, which is the average number of BSM transmissions before resource reselection. The above formula allows the transmitting device to include PH information and / or certificate information until the transmitting vehicle meets the receiving vehicle. A lower ITT allows for transmissions with more such PH information included (which is beneficial as it implies lower vehicle density and therefore lower channel congestion). Also, a higher CQI indicates worse channel conditions and the higher n will be.

[0129]

[0134] In some implementations, the trigger condition corresponds to a channel quality condition. In some such implementations, the trigger condition is a high CQI trigger condition and utilizes a CQI threshold. A high CQI indicates a high average Packer Error Rate (PER) in the BSM received at the transmitting device (e.g., HV) from a neighboring device (e.g., a neighboring RV). Channel reciprocity indicates that the neighboring devices also suffer from dropped BSMs from the transmitting device, which may hinder the receiving device's ability to reconstruct the transmitting device's past location and trajectory (leading to inaccurate future trajectories / predicted trajectories). In such cases, it is beneficial for the transmitting device to include PH information (or certificate information) in its BSM, even if no new vehicles are detected under such circumstances.

[0130]

[0135] As an illustrative and non-limiting example, the CQI may be determined according to the following formula:

[0131]

number

[0132] Here, N X (k) is V where 0≦TTC≦Y A is the number of vehicles within range.

[0133]

[0136] The transmitting device (e.g., vehicle) may include PH information in the BSM based on the following algorithm: The transmitting device may initialize the failed transmission parameter to 0 (TxFailed=0). After each transmission, the transmitting device may select a real value between 0 and 1 (e.g., use a random number generator (RNG) or pseudo-RNG to generate a real value in the space

[0001] ). The random number may be used as an approximation to determine whether the transmission / BSM was received. By using the random number, the transmitting device may estimate whether a particular transmitted transmission was received. If the randomly generated number is less than or equal to the determined CQI value, the failed transmission parameter is adjusted (e.g., incremented). For illustration purposes, the transmitting device may select the following: rand()≦CQI X If the CQI value is greater than the randomly generated number, the estimation indicates that the packet was received and the device can repeat the process to evaluate another BSM. In some implementations, the failed transmission parameter represents consecutive failed transmission parameters. For illustrative purposes, the parameter tracks only consecutive transmission failures. In such implementations, the transmitting device may reset the counter / failed transmission parameter each time a successful transmission is estimated / predicted or when the CQI value is greater than the randomly generated number. The failed transmission parameter may be compared to a threshold to determine whether PH information (or certificate information) should be sent. Furthermore, in some implementations, the threshold may be related to or correspond to the amount of previous positions to transmit. For example, if the threshold is 5, when the transmitting device estimates that 5 BSMs (or 5 consecutive BSMs) have not been received, the BSM includes the PH of the past 5 positions.

[0134]

[0137] Although the CQI is used as an estimate of congestion and / or error rate, other parameters may be used in addition to or instead of the CQI, such other or additional parameters including block error rate (BLER), PER, SINR, RSRP, congestion metrics, utilization metrics, etc.

[0135]

[0138] Additionally or alternatively, the base or standard inclusion rate may be increased to reduce the frequency with which route history and / or certificate information is included in the security message. For example, certificate information is included every 450 ms in some standards (e.g., when certificates may be changed or updated every 450 ms), and this inclusion rate may be relaxed. To illustrate, the UE may decide to increase the base inclusion frequency based on one or more operating conditions (e.g., CQI, PER, range, TTC, collision zone, etc.) or based on receiving a message from the network (e.g., an ITS control or setup message indicating to adjust the base inclusion rate / frequency), and the trigger condition for the inclusion of the additional information may correspond to a timer for this extended or adjusted base inclusion rate / frequency. As an illustrative example, the certificate information trigger condition is a certificate change condition or timer. In response to the condition being met or the timer expiring, the UE decides to include the certificate information in at least the next BSM.

[0136]

[0139] Thus, in the example of Figure 5, the wireless communication devices perform enhanced BSM reporting operations by utilizing dynamic information inclusion operations for BSM transmissions. Although the example of Figure 5 is directed to an example having three devices, in other examples, additional devices and / or device types may be used.

[0137]

[0140] Additionally or alternatively, in other implementations, one or more of the operations of Figures 3-5 may be added, removed, or substituted. For example, in some implementations, one or more of the example steps of Figures 4 and 5 may be used together. For illustration purposes, the trigger condition of Figure 4 may be used with the trigger condition of Figure 5.

[0138]

[0141] FIG. 6 is a flow diagram illustrating example blocks executed by a wireless communication device (e.g., a UE or a base station) configured according to an aspect of the disclosure. The example blocks are also described with respect to a UE 115 as shown in FIG. 8. FIG. 8 is a block diagram illustrating a UE 115 configured according to an aspect of the disclosure. The UE 115 includes the structure, hardware, and components as illustrated for the UE 115 of FIG. 2 and / or FIG. 4. For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in memory 282 and controls the components of the UE 115 that provide the features and functionality of the UE 115. The UE 115 transmits and receives signals via wireless radios 801a-r and antennas 252a-r under the control of the controller / processor 280. 2 for the UE 115, including the modulator / demodulators 254a-r, the MIMO detector 256, the receive processor 258, the transmit processor 264, and the TX MIMO processor 266. As shown in the example of FIG. 8, the memory 282 stores device-to-device (D2D) logic 802 (e.g., C-V2X or ITS logic), safety message (SM) logic 803 (e.g., BSM logic), device information data 804 (e.g., temporary ID information), channel information data 805 (e.g., CQI), trigger condition data 806 (e.g., route history trigger condition, certificate trigger condition, or a combination thereof), mapping data 807 (e.g., LDM data), and configuration data 808. The data (802-808) stored in memory 282 may include or correspond to the data (406, 408, 442, 444) stored in memory 404 of FIG.

[0139]

[0142] In block 600, a wireless communication device, such as a UE (e.g., UE 115, UE 415A, or UE 415B) or a network device (e.g., base station 105), receives a C-V2X message from another wireless communication device. For example, UE 115 receives message 452 of FIG. 4, message 510 of FIG. 5, or message 535 of FIG. 5 from another wireless communication device (e.g., UE 115a, UE 115b, UE 415A, UE 415B, or base station 105), as described with reference to FIGS. 4 and 5. By way of example, a receiver (e.g., receive processor 258 or receiver 412) of UE 115 receives a beacon message, a safety message (e.g., BSM), or other ITS message from UE 415A via wireless radios 801a-r and antennas 252a-r. The message may include device information, such as temporary ID information, as described with reference to FIGS. 3-5. The message may optionally include credential information (e.g., complete or specific credential information) and / or route history information (e.g., second route history information) of the other wireless communication device. Additionally or alternatively, the wireless communication device may determine channel state information based on the message, such as CQI, estimated heading / trajectory / route for the other wireless communication device, collision metrics (e.g., collision zone overlap, TTC, range estimates, etc.), or combinations thereof.

[0140]

[0143] In block 601, the UE 115 transmits a safety message including the route history information in response to determining that the route history information trigger condition is met based on the C-V2X message. For example, the UE 115 transmits the safety message 454 of FIG. 4 or the BSM 520 or BSM 525 of FIG. 5 as described with reference to FIGS. 4 and 5. To illustrate, a transmitter (e.g., the transmit processor 220 or the transmitter 410) of the UE 115 transmits a BSM including the route history information via the wireless radios 801a-r and the antennas 252a-r in response to or based on any of the route history information trigger conditions described with reference to FIGS. 3-5 being met. The BSM may be transmitted (broadcast) to multiple devices (including other wireless communication devices). In addition, the wireless communication device may transmit additional BSMs including the route history information based on determining that the route history trigger condition is met. These additional BSMs have route history information similar to the original BSM and may include updated route history information indicating an updated location.

[0141]

[0144] A wireless communication device (e.g., a UE or a base station) may perform additional blocks (or the wireless communication device may be configured to further perform additional operations) in other implementations. For example, a wireless communication device (e.g., a UE 115) may perform one or more operations described above. As another example, a wireless communication device (e.g., a UE 115) may perform one or more aspects as presented below.

[0142]

[0145] In one or more aspects, techniques for supporting extended BSM reporting operations may include additional aspects, such as any single aspect or any combination of aspects described with respect to one or more other processes or devices described below or elsewhere herein. In a first aspect, supporting extended BSM reporting operations may include an apparatus configured to receive a C-V2X message from a wireless communication device (e.g., another wireless communication device). The apparatus is further configured to transmit a safety message including the path history information in response to determining that a path history information trigger condition is met based on the C-V2X message. In addition, the apparatus may perform one or more aspects or operate according to one or more aspects as described below. In some implementations, the apparatus includes a wireless device, such as a UE. In some implementations, the apparatus may include at least one processor and a memory coupled to the processor. The processor may be configured to perform operations described herein with respect to the apparatus. In some other implementations, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, the program code being executable by a computer to cause the computer to perform operations described herein with respect to the apparatus. In some implementations, the apparatus may include one or more means configured to perform the operations described herein. In some implementations, a method of wireless communication may include one or more operations described herein with respect to the apparatus.

[0143]

[0146] In a second aspect, in combination with the first aspect, the route history information trigger condition includes a collision zone condition, a channel quality condition, a new vehicle condition, or a combination thereof.

[0144]

[0147] In a third aspect, in combination with one or more of the first or second aspect, a safety message transmission that does not satisfy a route history information trigger condition does not include route history information.

[0145]

[0148] In a fourth aspect, in combination with one or more of the first to third aspects, the safety message includes a Basic Safety Message (BSM), a Cooperative Awareness Message (CAM), or a Distributed Environmental Notification Message (DENM).

[0146]

[0149] In a fifth aspect, in combination with one or more of the first through fourth aspects, the route history information includes a plurality of previous positions of the wireless communication device.

[0147]

[0150] In a sixth aspect, in combination with one or more of the first to fifth aspects, the C-V2X message from the other wireless communication device includes a beacon message, a Basic Safety Message (BSM), a Cooperative Awareness Message (CAM), or a Distributed Environment Notification Message (DENM).

[0148]

[0151] In a seventh aspect, in combination with one or more of the first aspect to the sixth aspect, the C-V2X message from the other wireless communication device includes second route history information of the other wireless communication device, and further includes determining, by the wireless communication device, a trajectory of the other wireless communication device (e.g., based on the second route history information, one or more past BSMs, heading information, a route prediction of the other wireless communication device), and determining, by the wireless communication device, a range estimate (e.g., collision zone) or a time to collision (TTC) estimate for the other wireless communication device based on the trajectory of the other wireless communication device.

[0149]

[0152] In an eighth aspect in combination with one or more of the first to seventh aspects, the apparatus is configured to determine, by the wireless communication device, that a route history information trigger condition is satisfied, and determine a number of safety messages to include the route history information based on the wireless communication device determining that the route history information trigger condition is satisfied.

[0150]

[0153] In a ninth aspect, in combination with one or more of the first aspect to the eighth aspect, the C-V2X message includes the temporary ID, and the apparatus is configured to determine, by the wireless communication device, whether the temporary ID corresponds to a new or unknown device based on a local dynamic map (LDM), and to determine, by the wireless communication device, to include route history information in the safety message based on the temporary ID being associated with the new or unknown device.

[0151]

[0154] In a tenth aspect, in combination with the ninth aspect, determining whether the temporary ID corresponds to a new or unknown device based on the LDM includes: comparing, by the wireless communication device, the temporary ID to a stored temporary ID of the LDM; comparing, by the wireless communication device, a predicted trajectory of the other wireless communication device to a stored predicted trajectory of the LDM; and determining, by the wireless communication device, that the other wireless communication device is a new or unknown device due to a mismatch between the temporary ID or predicted trajectory and the stored temporary ID or predicted trajectory of the LDM.

[0152]

[0155] In an eleventh aspect, in combination with one or more of the first aspect to the tenth aspect, the apparatus is configured to: determine, by the wireless communication device, a range estimate (e.g., a collision zone) for the other wireless communication device based on the C-V2X message; determine, by the wireless communication device, a time to collision (TTC) estimate based on the C-V2X message; compare, by the wireless communication device, the range estimate to a range condition; compare, by the wireless communication device, the TTC estimate to the TTC condition; and determine, by the wireless communication device, to include route history information in the safety message based on the range estimate being less than the range condition, the TTC estimate being less than the TTC condition, or both.

[0153]

[0156] In a twelfth aspect, in combination with one or more of the first aspect to the eleventh aspect, the path history information trigger condition is a CQI trigger condition, and the apparatus is configured to: determine, by the wireless communication device, a CQI of the wireless communication device; compare, by the wireless communication device, the CQI to a CQI threshold; and determine, by the wireless communication device, that the CQI is less than or equal to the CQI threshold, such that the CQI trigger condition is satisfied.

[0154]

[0157] In a thirteenth aspect, in combination with one or more of the first to twelfth aspects, the wireless communication device is a user equipment (UE).

[0155]

[0158] In a fourteenth aspect, in combination with one or more of the first to thirteenth aspects, the wireless communication device is a host vehicle (HV) and the other wireless communication device is a remote vehicle (RV).

[0156]

[0159] Thus, a wireless communication device may perform enhanced secure message reporting operations and dynamic inclusion of route history information and / or certificate information into secure messages. Performing enhanced secure message operations or dynamic inclusion of route history information and / or certificate information into secure messages may improve network performance by increasing throughput and reducing overhead and latency through reduced signaling overhead.

[0157]

[0160] Figure 7 is a flow diagram illustrating example blocks performed by a wireless communication device (e.g., a UE or a base station) configured according to one aspect of the disclosure. The example blocks are also described with respect to a UE 115 as shown in Figure 8. Figure 8 is a block diagram illustrating a UE 115 configured according to one aspect of the disclosure. The UE 115 includes the structure, hardware, and components as shown for the UE 115 of Figures 2 and / or 4 and described above with reference to Figure 6.

[0158]

[0161] At block 700, a wireless communication device, such as a UE (e.g., UE 115, UE 415A, or UE 415B) or a network device (e.g., base station 105), receives a C-V2X message from another wireless communication device. For example, UE 115 receives message 452 of FIG. 4, message 510 of FIG. 5, or message 535 of FIG. 5 from another wireless communication device (e.g., UE 115a, UE 115b, UE 415A, UE 415B, or base station 105), as described with reference to FIGS. 4 and 5. By way of example, a receiver (e.g., receive processor 258 or receiver 412) of UE 115 receives a beacon message, a safety message (e.g., BSM), or other ITS message from UE 415A via wireless radios 801a-r and antennas 252a-r. The message may include device information, such as temporary ID information, as described with reference to FIGS. 3-5. The message may optionally include credential information (e.g., complete or specific credential information) and / or route history information (e.g., second route history information) of the other wireless communication device. Additionally or alternatively, the wireless communication device may determine channel state information based on the message, such as CQI, estimated heading / trajectory / route for the other wireless communication device, collision metrics (e.g., collision zone overlap, TTC, range estimates, etc.), or combinations thereof.

[0159]

[0162] In block 701, the wireless communication device transmits a safety message including the certificate information in response to determining that a certificate information trigger condition is met based on the C-V2X message. For example, the wireless communication device transmits the safety message 454 of FIG. 4 including the certificate information, or the BSM 545 or BSM 550 of FIG. 5, as described with reference to FIGS. 4 and 5. To illustrate, the transmitter (e.g., the transmit processor 220 or the transmitter 410) of the UE 115 transmits a BSM including the complete certificate via the wireless radios 801a-r and the antennas 252a-r in response to or based on any of the certificate information trigger conditions described with reference to FIGS. 3-5 being met. The BSM may be transmitted (broadcast) to multiple devices. Additionally, the wireless communication device may transmit an additional BSM including the certificate information based on determining that a certificate information trigger condition is met.

[0160]

[0163] A wireless communication device (e.g., a UE or a base station) may perform additional blocks (or the wireless communication device may be configured to further perform additional operations) in other implementations. For example, the wireless communication device may perform one or more of the operations described above. As another example, the wireless communication device may perform one or more aspects described with reference to FIGS. 3-8.

[0161]

[0164] In one or more aspects, techniques for supporting extended BSM reporting operations may include additional aspects, such as any single aspect or any combination of aspects, described with respect to one or more other processes or devices described below or elsewhere herein. In a first aspect, supporting extended BSM reporting operations may include an apparatus configured to receive a C-V2X message from a wireless communication device (e.g., another wireless communication device). The apparatus is further configured to transmit a safety message including the certificate information in response to determining that a certificate information trigger condition is met based on the C-V2X message. In addition, the apparatus may perform one or more aspects or operate according to one or more aspects as described below. In some implementations, the apparatus includes a wireless device, such as a base station. In some implementations, the apparatus may include at least one processor and a memory coupled to the processor. The processor may be configured to perform operations described herein with respect to the apparatus. In some other implementations, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, the program code being executable by a computer to cause the computer to perform operations described herein with respect to the apparatus. In some implementations, the apparatus may include one or more means configured to perform the operations described herein. In some implementations, a method of wireless communication may include one or more operations described herein with respect to the apparatus.

[0162]

[0165] In a second aspect, in combination with the first aspect, the certificate information trigger condition includes a range condition, a time to collision condition, a new vehicle condition, a timer condition, a critical event condition, or a combination thereof.

[0163]

[0166] In a third aspect, in combination with one or more of the first aspect to the second aspect, the apparatus is configured to determine, by the wireless communication device, that a certificate information trigger condition is not satisfied, and based on the wireless communication device determining that the certificate information trigger condition is not satisfied, refrain from including the certificate information in the second BSM, and send, by the wireless communication device, the second BSM without the certificate information.

[0164]

[0167] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the partial certificate information includes a digest of the certificate information. In a particular implementation, the indicated digest identifies the certificate information (e.g., a previously transmitted full certificate). In another particular implementation, the digest includes or indicates message source authentication information, integrity check information, or both.

[0165]

[0168] In a fifth aspect, in combination with one or more of the first to fourth aspects, the safety message includes a Basic Safety Message (BSM), a Cooperative Awareness Message (CAM), or a Distributed Environmental Notification Message (DENM).

[0166]

[0169] In a sixth aspect, in combination with one or more of the first to fifth aspects, the certificate information includes a complete certificate.

[0167]

[0170] In a seventh aspect, in combination with one or more of the first aspect to the sixth aspect, the C-V2X message from the other wireless communication device includes a beacon message, a Basic Safety Message (BSM), a Cooperative Awareness Message (CAM), or a Distributed Environment Notification Message (DENM).

[0168]

[0171] In an eighth aspect, in combination with one or more of the first aspect to the seventh aspect, the C-V2X message from the other wireless communication device includes second route history information of the other wireless communication device, and the apparatus is configured to determine, by the wireless communication device, a trajectory of the other wireless communication device (e.g., based on the second route history information, one or more past BSMs, heading information, route predictions of the other wireless communication device), and determine, by the wireless communication device, a range estimate (e.g., collision zone) or a time to collision (TTC) estimate for the other wireless communication device based on the trajectory of the other wireless communication device.

[0169]

[0172] In a ninth aspect, in combination with one or more of the first to eighth aspects, the C-V2X message includes the temporary ID, and the apparatus is configured to: determine, by the wireless communication device, based on a local dynamic map (LDM), whether the temporary ID corresponds to a new or unknown device; determine, by the wireless communication device, whether a range or TTC associated with the new or unknown device satisfies a range condition, a TTC condition, or both; and determine, by the wireless communication device, to include certificate information in the safety message based on the temporary ID associated with the new or unknown device and the new or unknown device satisfying the range condition, the TTC condition, or both.

[0170]

[0173] In a tenth aspect, in combination with one or more of the first aspect to the ninth aspect, the certificate information trigger condition is a CQI trigger condition, and the apparatus is configured to: determine, by the wireless communication device, a CQI of the wireless communication device; compare, by the wireless communication device, the CQI to a CQI threshold; determine, by the wireless communication device, whether the CQI trigger condition is satisfied by the CQI being less than or equal to the CQI threshold; and determine, based on the wireless communication device determining that the CQI trigger condition is satisfied by the CQI being less than or equal to the CQI threshold, to include the certificate information in the secure message.

[0171]

[0174] In an eleventh aspect in combination with one or more of the first to tenth aspects, the certificate information trigger condition is a certificate change condition, and the apparatus is configured to: determine, by the wireless communication device, a certificate inclusion frequency for a base frequency (e.g., a standard or base inclusion frequency) greater than 450 ms for inclusion of the certificate information after the certificate change; set, by the wireless communication device, a timer based on the certificate inclusion frequency; and determine, by the wireless communication device, to include the certificate information in the secure message based on expiration of the timer.

[0172]

[0175] In a twelfth aspect, in combination with one or more of the first to eleventh aspects, the certificate inclusion frequency is 2 seconds or greater.

[0173]

[0176] In a thirteenth aspect, in combination with one or more of the first to twelfth aspects, the apparatus is configured to determine, by the wireless communication device, a critical event, the critical event including an acceleration event, a deceleration event, a direction change event, activation of a safety system (e.g., ABS, traction control, driver assistance), or a combination thereof, and determine, by the wireless communication device, based on detecting the critical event, to include the certificate information in the safety message.

[0174]

[0177] In a fourteenth aspect, in combination with one or more of the first to thirteenth aspects, the wireless communication device operates in a Society of Automotive engineers International (SAE) or European Telecommunications Standards Institute (ETSI) Intelligent Transportation System (ITS) mode.

[0175]

[0178] In some aspect implementations, another wireless communication device, such as another UE or a base station, transmits a C-V2X message to the wireless communication device and receives a secure message from the wireless communication device that includes route history information in response to determining that a route history information trigger condition is met based on the C-V2X message, or that includes certificate information in response to determining that a certificate information trigger condition is met based on the C-V2X message.

[0176]

[0179] Thus, a wireless communication device may perform enhanced secure message reporting operations and dynamic inclusion of route history information and / or certificate information into secure messages. Performing enhanced secure message operations or dynamic inclusion of route history information and / or certificate information into secure messages may improve network performance by increasing throughput and reducing overhead and latency through reduced signaling overhead.

[0177]

[0180] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0178]

[0181] The components, functional blocks, and modules described herein with respect to Figures 1-8 comprise, among other examples, processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software code, firmware code, etc., or any combination thereof. Software should be construed broadly to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or the like. Additionally, features discussed herein may be implemented via dedicated processor circuitry, via executable instructions, or a combination thereof.

[0179]

[0182] Those skilled in the art will further appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design constraints imposed on the overall system. Those skilled in the art may realize the described functionality in different ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure. Those skilled in the art will also readily appreciate that the order or combination of components, methods, or interactions described herein are merely examples, and that the components, methods, or interactions of various aspects of the disclosure can be combined or performed in ways other than those shown and described herein.

[0180]

[0183] The various example logic, logic blocks, modules, circuits, and algorithmic processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been described generally in terms of functionality and illustrated in the various example components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the particular application and design constraints imposed on the overall system.

[0181]

[0184] The hardware and data processing devices used to implement the various example logic, logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be realized or performed using general purpose single-chip or multi-chip processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. In some implementations, a processor may be realized as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some implementations, particular processes and methods may be performed by circuitry specific to a given function.

[0182]

[0185] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, or any combination thereof, including the structures disclosed herein and their structural equivalents. Implementations of the subject matter described herein may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by or for controlling the operation of a data processing apparatus.

[0183]

[0186] If implemented in software, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. The processes of the methods or algorithms disclosed herein may be executed in processor-executable software modules that may reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that may enable a computer program to be transferred from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Also, any connection may be properly referred to as a computer-readable medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer readable media.Additionally, operations of a method or algorithm may reside on machine-readable and computer-readable media, which may be embodied as one or any combination or set of codes and instructions into a computer program product.

[0184]

[0187] Various modifications of the implementations described in this disclosure may be readily apparent to those skilled in the art, and the general principles defined herein may be applied to several other implementations without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein, but should be accorded the widest scope consistent with this disclosure, the principles and novel features disclosed herein.

[0185]

[0188] In addition, those skilled in the art will readily appreciate that the terms "upper" and "lower" may be used to facilitate description of the figures, and refer to relative positions that correspond to the orientation of the figure on a properly oriented page, and may not reflect the proper orientation of any implemented device.

[0186]

[0189] Certain features described herein in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable subcombination. Furthermore, although features may be described above as working in certain combinations, and may even be initially claimed as such, one or more features from a claimed combination may, in some cases, be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

[0187]

[0190] Similarly, although operations are shown in the figures in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequential order shown, or that all of the operations shown be performed, to achieve desirable results. Additionally, the figures may generally depict another exemplary process in the form of a flow diagram. However, other operations not shown may be incorporated into the generally depicted exemplary process. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the depicted operations. In some circumstances, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the program components and systems described may generally be integrated together in a single software product or packaged within multiple software products. Additionally, some other implementations fall within the scope of the following claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve desirable results.

[0188]

[0191] As used herein, including in the claims, the term "or", when used in a list of two or more items, means that any one of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as containing components A, B, or C, the composition may contain only A, only B, only C, a combination of A and B, a combination of A and C, a combination of B and C, or a combination of A, B, and C. Also, as used herein, including in the claims, "or" used in a list of items ending with "at least one of" indicates a disjunctive list, such as, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any of these in any combination thereof. As will be understood by one of ordinary skill in the art, the term "substantially" is defined as most of (including) what is specified (e.g., substantially 90 degrees includes 90 degrees, substantially parallel includes parallel), but not necessarily all of it. In any disclosed implementations, the term "substantially" may be replaced with "within a [percentage] of" what is specified, where percentage includes 0.1, 1, 5, or 10 percent.

[0189]

[0192] The above description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. 1. A method of wireless communication, comprising: receiving, by a wireless communication device, a cellular vehicle-to-everything (C-V2X) message from another wireless communication device; determining, by the wireless communication device, whether a route history information trigger condition is met based on the C-V2X message; transmitting, by the wireless communication device, a safety message, wherein the safety message includes route history information in response to determining that the route history information trigger condition is met, and does not include route history information in response to determining that the route history information trigger condition is not met, the route history information trigger condition including a collision zone condition, a channel quality condition, a new vehicle condition, or a combination thereof; A method comprising:

2. The collision zone condition is satisfied when a distance condition and / or a time-to-collision (TTC) condition is satisfied; the channel quality condition is met if a channel quality indicator (CQI) exceeds a threshold; The method of claim 1 , wherein the new vehicle condition is met when a new vehicle enters a collision zone of the wireless communication device.

3. The method of claim 1 , wherein the safety message comprises a Basic Safety Message (BSM), a Cooperative Awareness Message (CAM), or a Distributed Environmental Notification Message (DENM).

4. The method of claim 1 , wherein the route history information includes multiple previous locations of the wireless communication device.

5. 10. The method of claim 1, wherein the C-V2X message from the other wireless communication device comprises a beacon message, a basic safety message (BSM), a cooperative awareness message (CAM), or a distributed environmental notification message (DENM).

6. the C-V2X message from the other wireless communication device includes second route history information of the other wireless communication device, determining, by the wireless communication device, a trajectory of the other wireless communication device; determining, by the wireless communication device, a range estimate or a time-to-collision (TTC) estimate for the other wireless communication device based on the trajectory of the other wireless communication device; 10. The method of claim 1, further comprising: determining, by the wireless communication device, to include the route history information in the safety message based on the range estimate or the TTC estimate.

7. 10. The method of claim 1, further comprising: determining, by the wireless communication device, a number of safety messages to include the route history information based on determining that the route history information trigger condition is met.

8. A non-transitory computer-readable medium having recorded thereon program code that, when executed by a wireless communication device, causes the wireless communication device to perform the operations described in any one of claims 1 to 7.

9. 1. An apparatus comprising: at least one transceiver; Memory and at least one processor coupled to the at least one transceiver and the memory, wherein the at least one processor: receiving a cellular vehicle-to-everything (C-V2X) message from a wireless communication device via the at least one transceiver; determining whether a route history information trigger condition is met based on the C-V2X message; and transmitting a safety message via the at least one transceiver, wherein the safety message includes route history information in response to determining that the route history information trigger condition is met, and does not include route history information in response to determining that the route history information trigger condition is not met, the route history information trigger condition including a collision zone condition, a channel quality condition, a new vehicle condition, or a combination thereof; The apparatus is configured to:

10. the C-V2X message includes a temporary ID, and the at least one processor: determining whether the temporary ID corresponds to a new or unknown device based on a local dynamic map (LDM); The apparatus of claim 9 , further configured to determine to include the route history information in the safety message based on the temporary ID being associated with a new or unknown device.

11. To determine whether the temporary ID corresponds to the new or unknown device based on the LDM, the at least one processor: comparing the temporary ID with a stored temporary ID of the LDM; comparing the predicted trajectory of the wireless communication device with the stored predicted trajectory of the LDM; 11. The apparatus of claim 10, configured to determine that the wireless communication device is a new or unknown device due to a mismatch between the temporary ID or predicted trajectory and the stored temporary ID or the stored predicted trajectory of the LDM.

12. the at least one processor: determining a range estimate for the wireless communication device based on the C-V2X message; determining a time to collision (TTC) estimate based on the C-V2X message; comparing the range estimate with a range condition; comparing the TTC estimate with a TTC condition; 10. The device of claim 9, further configured to determine to include the route history information in the safety message based on the range estimate being less than the range condition, the TTC estimate being less than the TTC condition, or both.

13. the path history information trigger condition is a channel quality indicator (CQI) trigger condition, and the at least one processor: determining a CQI for the device; comparing the CQI to a CQI threshold; The apparatus of claim 9 , further configured to determine that the CQI trigger condition is met by the CQI being less than or equal to the CQI threshold.

14. The apparatus of claim 9 , wherein the apparatus comprises a user equipment (UE).

15. The apparatus of claim 9 , wherein the apparatus comprises a host vehicle (HV) and the wireless communication device comprises a remote vehicle (RV).

Images