Efficient routing history and complete certificate inclusion in security 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 of related applications)

[0001] This application claims the benefit of U.S. Patent Application No. 17 / 646,976, filed on 4 January 2022, entitled “EFFICIENT PATH HISTORY AND FULL CERTIFICATE INCLUSION IN SAFETY MESSAGES,” which is expressly incorporated herein by reference in its entirety.

[0002]

[0002] The aspects of this disclosure generally relate to wireless communication systems, and more specifically 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, and broadcast. 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 a base station (or node B) that can support communication for several user equipments (UEs). The UEs may communicate with the base station via downlinks and uplinks. A downlink (or forward link) refers to a communication link from the base station to the UE, and an uplink (or reverse link) refers to a communication link from the UE to the base station.

[0005]

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

[0006]

[0006] As the demand for mobile broadband access continues to increase, more UEs will access long-range wireless communication networks, and more short-range wireless systems will be deployed in areas, increasing the potential for interference and network congestion. Research and development to advance wireless technology continues not only to meet the growing demand for mobile broadband access, but also to evolve and improve the user experience of mobile communications. [Overview of the project]

[0007]

[0007] The following summarizes several aspects of the Disclosure in order to provide a basic understanding of the technology discussed. This summary is not intended to be a comprehensive overview of all conceivable features of the Disclosure, nor to identify any major or significant elements of all aspects of the Disclosure, nor to specify the scope of any or all aspects of the Disclosure. Its sole purpose is to present in summary form some concepts of one or more aspects of the Disclosure as an introduction to the more detailed descriptions to be presented later.

[0008]

[0008] In one aspect of the present disclosure, a wireless communication method includes: a wireless communication device receiving a C-V2X message from another wireless communication device; and the wireless communication device transmitting a security message containing route history information in response to determining that a route history information trigger condition has been met based on the C-V2X message.

[0009]

[0009] In another aspect of the present disclosure, the device 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 has been met based on the C-V2X message, to send a security message containing route history information.

[0010]

[0010] In one aspect of the present disclosure, a method for wireless communication includes: a wireless communication device receiving a C-V2X message from another wireless communication device; and the wireless communication device sending a security message containing certificate information in response to determining that a certificate information trigger condition has been met based on the C-V2X message.

[0011]

[0011] In another aspect of the present disclosure, the device 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 has been met based on the C-V2X message, to send a security message containing certificate information.

[0012]

[0012] The foregoing has provided a fairly broad overview of the features and technical advantages of the embodiments of this disclosure in order to better understand the following “Modes for Carrying Out the Invention.” Additional features and advantages will be described thereafter. The concepts and specific examples disclosed can be readily used as a basis for modifying or designing other structures to accomplish the same objectives of this disclosure. Such equivalent structures will not deviate from the scope of the appended claims. Both their configuration and method of operation, which are characteristics of the concepts disclosed herein, will be better understood, along with the relevant advantages, by considering the following description in relation to the appended figures. Each of the figures is provided for illustrative and explanatory purposes only, and not as a definition of the limitations of the claims.

[0013]

[0013] While the embodiments and implementations described herein are illustrated by several 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 can be implemented across many different platform types, devices, systems, forms, sizes, and packaging arrangements. For example, embodiments and / or applications may arise from 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 specifically target use cases or applications, but may result in a wide range of applicability of the innovations described. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and may even extend to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more embodiments of the innovations described. In some practical settings, devices incorporating the described embodiments and features may also necessarily include additional components and features for the implementation and practice of the claims and described embodiments. For example, the transmission and reception of wireless signals necessarily include several components (hardware components including, for example, antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors (one or more), interleavers, adders / analog adders, etc.) for analog and digital purposes. The innovations described herein are intended to be implemented in a wide variety of devices, chip-level components, systems, distributed configurations, end-user devices, etc., of various sizes, shapes, and structures. [Brief explanation of the drawing]

[0014]

[0014] Further understanding of the nature and advantages of this disclosure can be achieved 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 adding a dash after the reference label and a second label to distinguish similar components. Where only the first reference label is used herein, the description is applicable to any one of the similar components having the same first reference label, notwithstanding the second reference label. [Figure 1]

[0015] This block diagram shows details of an exemplary wireless communication system in one or more embodiments. [Figure 2]

[0016] This is a block diagram showing examples of base stations and user equipment (UEs) in one or more forms. [Figure 3A]

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

[0018] This is an illustrative diagram showing device-to-device communication. [Figure 4]

[0019] This block diagram shows an exemplary wireless communication system that supports enhanced safety message reporting operations in one or more ways. [Figure 5]

[0020] This figure shows an exemplary wireless communication system that supports enhanced safety message reporting operations in one or more ways. [Figure 6]

[0021] This flowchart illustrates an exemplary process that supports enhanced safety message reporting behavior in one or more ways. [Figure 7]

[0022] This flowchart illustrates an exemplary process that supports enhanced safety message reporting behavior in one or more ways. [Figure 8]

[0023] FIG. 0 is a block diagram of an exemplary UE supporting an extended security message reporting operation according to one or more aspects.

[0015]

[0024] Like reference numerals and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION

[0016]

[0025] In connection with the accompanying drawings, the “Detailed Description” set forth below is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Rather, the “Detailed Description” includes specific details aimed at providing a complete understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case and that, in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0017]

[0026] This disclosure relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems, also commonly 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” as described herein may be used interchangeably.

[0018]

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

[0019]

[0028] TDMA networks may implement radio technologies such as the Global System for Mobile Communication (GSM). The 3rd Generation Partnership Project (3GPP) defines standards for GSM EDGE (GSM Evolutionary High-Speed ​​Data Rate) radio access networks (RAN), also known as GERAN. GERAN is a radio component of GSM / EDGE, along with the network connecting base stations (e.g., Ater interfaces and Abis interfaces) and base station controllers (e.g., A interfaces). The radio access network represents a component of the GSM network through which telephone calls and packet data are routed to and from the public switched telephone network (PSTN), and to the internet, and to subscriber handsets, also known as user terminals or user equipment (UEs). A mobile operator's network may include one or more GERANs, such GERANs may be coupled with UTRAN in the case of UMTS / GSM networks. In addition, the operator's 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 can implement wireless technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and Flash OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunication System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS release that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are documented in documents provided by an organization called the "Third Generation Partnership Project" (3GPP), and cdma2000 is documented in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). These various wireless technologies and standards are known or under development. For example, 3GPP is a collaborative effort among groups of telecommunications associations aimed at defining 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. While this disclosure may describe several aspects with reference to LTE, 4G, or 5G NR technologies, the description is not intended to be limited to any particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to other technologies as well. In addition, one or more aspects of this disclosure may relate to shared access to the wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0021]

[0030] 5G networks are expected to enable diverse deployments, diverse spectrums, and diverse services and devices, which can be implemented using OFDM-based integrated air interfaces. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further extensions to LTE and LTE-A will be considered. 5G NR will (1) be ultra-high density (e.g., ~1M nodes / km) 2 (2) Mission-critical controls with strong security to protect sensitive personal, financial, and confidential information, ultra-high reliability (e.g., approximately 99.9999% reliability), ultra-low latency (e.g., approximately 1 millisecond (ms)), and wide mobility, including users without such mobility, for the Internet of Things (IoTs) on a large scale, with ultra-low complexity (e.g., ~tens of bits / second), ultra-low energy (e.g., battery life of ~10 years or more), and the ability to reach hard-to-reach places, with ultra-high reliability (e.g., approximately 99.9999% reliability), ultra-low latency (e.g., approximately 1 millisecond (ms)), and wide mobility, including users without such mobility, with very high capacity (e.g., approximately 10 Tbps / km) 2 It can scale to provide coverage with enhanced mobile broadband, including very high data rates (e.g., multi-Gbps rates, user experience rates exceeding 100 Mbps), and deep awareness with advanced discovery and optimization.

[0022]

[0031] Devices, networks, and systems may be configured to communicate over one or more parts 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 are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. Although a portion of FR1 is above 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue can 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 to 300 GHz) which is designated as the "mmWave" band by the International Telecommunication Union (ITU).

[0023]

[0032] With the above aspects in mind, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that are below 6GHz, within FR1, or may include intermediate band frequencies when used herein. Furthermore, unless otherwise specified, terms such as "mmWave" may broadly refer to frequencies that are within the intermediate band, within FR2, or within the EHF band when used herein.

[0024]

[0033] 5G NR devices, networks, and systems can be implemented to use optimized OFDM-based waveform features. These features may include scalable numerology and transmission time intervals (TTIs), a common flexible framework for efficiently multiplexing services and features in 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 advanced wireless technologies such as device-centric mobility. Numerology scalability in 5G NR, with subcarrier spacing scaling, can efficiently address the operation of diverse services across diverse spectrums and 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 across bandwidths such as 1, 5, 10, and 20 MHz. For various other outdoor and small cell coverage deployments of TDD above 3 GHz, the subcarrier spacing can be 30 kHz over an 80 / 100 MHz bandwidth. For various other indoor broadband implementations using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing can be 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting with millimeter-wave components in a 28 GHz TDD, the subcarrier spacing can be 120 kHz over a 500 MHz bandwidth.

[0025]

[0034] 5G NR's scalable numerology facilitates scalable Time-to-Impact (TTI) for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs may be used for lower latency and higher reliability, while longer TTIs may be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to initiate on symbol boundaries. 5G NR can also be expected to feature self-contained, integrated subframe designs that have uplink or downlink scheduling information, data, and acknowledgments within the same subframe. Self-contained, integrated subframes support communications in unlicensed or competition-based shared spectrum and adaptive uplinks or downlinks that can be flexibly configured per cell to dynamically switch between uplinks and downlinks to meet current traffic needs.

[0026]

[0035] For clarity, several aspects of the apparatus and techniques may be described below in relation to exemplary 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in the following sections of the description. However, the description is not intended to be limited to 5G applications.

[0027]

[0036] Furthermore, it should be understood that, during operation, a wireless communication network adapted according to the concepts herein may operate in any combination of licensed or unlicensed spectra depending on the load and availability. Therefore, it will be apparent to those skilled in the art that the systems, apparatus, and methods described herein may be applied to communication systems and applications other than the specific examples shown.

[0028]

[0037] While this application illustrates several examples of embodiments and implementations, 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 can be implemented across many different platform types, devices, systems, forms, 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 specifically target use cases or applications, but they may give rise to a wide range of applicability of the innovations described. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the embodiments described herein. In some practical settings, devices incorporating the described embodiments and features may also necessarily include additional components and features for the implementation and practice of the claims and described embodiments. The innovations described herein can be implemented in a wide variety of implementation forms, including both large and small devices of various sizes, shapes, and structures, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed configurations, and end-user devices.

[0029]

[0038] Figure 1 is a block diagram showing details of an exemplary wireless communication system in one or more embodiments. 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 understood by those skilled in the art, the components shown in Figure 1 are likely to have corresponding components in relation to other network configurations, such as cellular and non-cellular network configurations (e.g., device-to-device, peer-to-peer, or ad-hoc network configurations).

[0030]

[0039] The wireless network 100 shown in Figure 1 includes several base stations 105 and other network entities. A base station may also be a station communicating with a UE and may be referred to as an evolved node B (eNB), next-generation eNB (gNB), access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term “cell” may refer to this specific geographic coverage area of ​​a base station or base station subsystem serving a coverage area, depending on the context in which the term is used. In the implementations of the wireless network 100 described herein, base stations 105 may be associated with the same operator or different operators (for example, the wireless network 100 may include multiple operator wireless networks). In addition, in the implementations of the wireless network 100 described herein, base stations 105 may provide wireless communication using one or more of the same frequencies as adjacent cells (e.g., one or more frequency bands in the licensed spectrum, unlicensed spectrum, or a combination thereof). In some examples, individual base stations 105 or UE115 may be operated by two or more network operations entities. In some other examples, each base station 105 and UE115 may be operated by a single network operations entity.

[0031]

[0040] Base stations can provide communication coverage to macrocells, or small cells such as picocells or femtocells, or other types of cells. Macrocells generally cover relatively large geographical areas (e.g., a radius of several kilometers) and may enable unrestricted access by UEs (Users) subscribed to a network provider's service. Small cells such as picocells generally cover relatively small geographical areas and may enable unrestricted access by UEs subscribed to a network provider's service. Small cells such as femtocells also generally cover relatively small geographical areas (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femtocell (e.g., UEs within a closed subscriber group (CSG), UEs for users in a home, etc.). Base stations for macrocells are sometimes called macro base stations. Base stations for small cells are sometimes called small cell base stations, pico base stations, femto base stations, or home base stations. In the example shown in Figure 1, base stations 105d and 105e are standard macro base stations, while base stations 105a–105c are macro base stations enabled with one of the following: 3D MIMO, full-dimension (FD) MIMO, or massive MIMO. Base stations 105a–105c leverage their higher-dimensional MIMO capabilities to utilize 3D beamforming in both high-altitude 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 more (e.g., two, three, or four) cells.

[0032]

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

[0033]

[0042] UE115 is distributed throughout the entire wireless network 100, and each UE may be fixed or mobile. Mobile devices are generally referred to as UEs in the standards and specifications published by 3GPP, but it should be understood that such devices may also be referred to by those skilled in the art in additional or other ways as mobile station (MS), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, game device, augmented reality device, vehicle component, vehicle device, or vehicle module, or any other appropriate term. For the purposes of this document, a “mobile” device or UE does not necessarily have to be mobile and may be fixed. Some non-exclusive examples of mobile devices that may have one or more implementations of UE115 include mobile phones, cellular 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 further include automobiles or other transport vehicles, satellite radios, global positioning system (GPS) devices, global navigation satellite system (GNSS) devices, logistics controllers, drones, multicopters, quadcopters, smart energy or security devices, solar panels or solar arrays, urban lighting, water, and other infrastructure IoT or "Internet of Everything" (IoE) devices, industrial automation and enterprise devices, eyewear, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, and other consumer and wearable devices, as well as digital home or smart home devices such as home audio, video, and multimedia devices, home appliances, sensors, vending machines, intelligent lighting, home security systems, and smart meters. In one embodiment, the UE may be a device including a Universal Integrated Circuit Card (UICC). In another embodiment, the UE may be a device not including a UICC. In some embodiments, a UE that does not include UICC may also be called an IoE device. UE115a to UE115d in the implementation shown in Figure 1 are examples of mobile smartphone-type devices accessing the wireless network 100. UEs can also be machines specifically configured for connected communications, including machine-type communication (MTC), enhanced MTC (eMTC), and narrowband IoT (NB-IoT). UE115e to UE115k shown in Figure 1 are examples of various machines configured for communications accessing the wireless network 100.

[0034]

[0043] Mobile devices such as the UE115 may be able to communicate with all types of base stations, including macro base stations, pico base stations, femto base stations, and relays. In Figure 1, the communication links (represented as lightning bolts) show wireless transmissions between the UE and a serving base station, which is a base station designated to service the UE on the downlink or uplink, or desired transmissions between base stations, as well as backhaul transmissions between base stations. In some scenarios, the UE may act as a base station or other network node. Backhaul communication between base stations in wireless network 100 may be performed using wired or wireless communication links.

[0035]

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

[0036]

[0045] The implemented wireless network 100 supports mission-critical communications using highly reliable and redundant links for mission-critical devices such as the UE115e drone. The redundant communication links with the UE115e include those from macro base stations 105d and 105e, as well as from small cell base station 105f. Other machine-type devices such as the UE115f (thermometer), UE115g (smart meter), and UE115h (wearable device) can communicate through the wireless network 100, either directly with base stations such as the small cell base station 105f and macro base station 105e, or with other user devices that relay their information to the network in a multi-hop configuration. For example, the UE115f can communicate temperature measurement information to the smart meter UE115g, and then that information can be reported to the network via the small cell base station 105f. The wireless network 100 can also provide further network efficiency through dynamic low-latency TDD communication or low-latency FDD communication in a vehicle-to-vehicle (V2V) mesh network between UE115i~115k communicating with macro base stations 105e.

[0037]

[0046] Figure 2 is a block diagram showing examples of base stations 105 and UEs 115 in one or more embodiments. Base stations 105 and UEs 115 may be any of the base stations and UEs in Figure 1. In the case of a limited association scenario (as described above), base station 105 may be the small cell base station 105f in Figure 1, and UE 115 may be a UE 115c or 115d operating in the service area of ​​base station 105f, and UE 115c or 115d will be included in the list of accessible UEs to small cell base station 105f in order to access small cell base station 105f. Base station 105 may also be any other type of base station. As shown in Figure 2, base station 105 may be equipped with antennas 234a-234t, and UE 115 may be equipped with antennas 252a-252r to facilitate wireless communication.

[0038]

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

[0039]

[0048] In UE115, antennas 252a to 252r can receive downlink signals from base station 105 and each can provide the received signals to demodulators 254a to 254r. Each demodulator 254 may adjust its respective received signal (e.g., filter, amplify, downconvert, and digitize) to obtain an input sample. Each demodulator 254 may further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbol from demodulators 254a to 254r, perform MIMO detection on the received symbol where applicable, and supply the detected symbol. The receiving processor 258 can process the detected symbol (e.g., demodulate, deinterleave, and decode) and provide the decoded data for UE115 to the data sink 260 and the decoded control information to a controller 280 such as a processor.

[0040]

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

[0041]

[0050] Controllers 240 and 280 may each instruct the operation of base station 105 and UE 115. Other processors and modules in controller 240 or base station 105, or in controller 280 or UE 115, may perform or instruct various processes for the techniques described herein, such as performing or instructing the execution shown in Figures 6 and 7 or other processes for the techniques described herein. Memories 242 and 282 may each store data and program code for base station 105 and UE 115. Scheduler 244 may schedule UEs for data transmission on downlink or uplink.

[0042]

[0051] In some cases, the UE 115 and base station 105 may operate in a shared radio frequency spectrum band that may include licensed frequency spectrum or unlicensed (e.g., contention-based) frequency spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or base station 105 may conventionally perform medium sensing procedures to compete for access to the frequency spectrum. For example, the UE 115 or base station 105 may perform listen-before-talk (LBT) or listen-before-transmitting (listen-before-transmitting, LBT) procedures, such as a clear channel assessment (CCA), before communication to determine whether a shared channel is available. In some implementations, the CCA may include energy sensing procedures to determine whether there are any other active transmissions. For example, a device may infer that a change in the received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, signal power concentrated within several bandwidths and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include the detection of specific sequences indicating 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 acknowledgment / negative acknowledgment (ACK / NACK) feedback to its own transmitted packets as a proxy for the amount of energy or collision detected on the channel.

[0043]

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

[0044]

[0053] The exemplary methods and apparatus discussed below are applicable to any of the various 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. For the sake of simplicity, the exemplary methods and apparatus will be discussed in the context of NR. However, those skilled in the art will understand 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 can be used to provide direct communication between devices. D2D communication allows one device to communicate with another device and send 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 in one vehicle can perform D2D communication with a device in another vehicle. According to V2X communication, a device in one vehicle can perform D2D communication with another device regardless of whether the device is inside 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, a device can explore the channel before transmission. For transportation-related communications (e.g., V2X communication), the 5.9 GHz unlicensed spectrum is generally reserved for intelligent transportation services (ITS) communications. Recently, other types of communication, such as NR communication, are being developed for V2V communication. For example, NR D2D can be used for V2V communication through licensed and / or unlicensed spectrum.

[0047]

[0056] In vehicle-to-everything (V2X) wireless communication systems, a UE 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 by a network entity (e.g., a base station). In some embodiments, the UE may perform resource selection and / or scheduling by determining the channel busy rate (CBR) associated with various sidelink channels, such as by measuring one or more sidelink channels, decoding sidelink control information (SCI) indicating channel availability, or by measuring the channel busy rate (CBR) associated with various sidelink channels.

[0048]

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

[0049]

[0058] In V2X communication systems, the state of the side link channels used to carry V2X communications can fluctuate and change rapidly due to factors such as the high mobility of vehicles and associated UEs, significant fluctuations in vehicle traffic volume at different times and locations, and the diverse terrains that vehicles may traverse (e.g., densely populated urban environments, hilly environments, flat environments, etc.). Furthermore, V2X communication systems require high reliability, for example, due to mission-critical safety issues associated with autonomous vehicles. Several techniques and devices described herein improve the performance of V2X communication systems by dynamically determining parameters for V2X transmission based at least in part on dynamic factors associated with one or more vehicles, side link channels, etc.

[0050]

[0059] In some embodiments, V2X transmissions may be one-to-many broadcast and / or multicast transmissions. In some embodiments, V2X transmissions may not require any physical layer feedback from the receiving device, such as acknowledgment (ACK) or negation (NACK) feedback. In some embodiments, V2X transmissions may be configured without retransmissions. In some embodiments, V2X transmissions may consist of several retransmissions (e.g., five retransmissions). In certain embodiments, retransmissions may occur automatically, 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) communication via one or more sidelink channels. In some embodiments, the UE may correspond to one or more other UEs as described elsewhere in this specification. The UE may transmit V2X communication using the sidelink channels.

[0052]

[0061] A sidelink channel may include a physical sidelink control channel (PSCCH) and a physical sidelink sharing channel (PSSCH). A sidelink channel may optionally include a physical sidelink feedback channel (PSFCH). A PSCCH may be used to communicate control information, similar to a physical downlink control channel (PDCCH) and / or physical uplink control channel (PUCCH) used for communication with a base station. A PSSCH may be used to communicate data, similar to a physical downlink sharing channel (PDSCH) and / or physical uplink sharing channel (PUSCH) used for communication with a base station. For example, a PSCCH may carry sidelink control information (SCI), which may represent various control information used for sidelink communication, such as one or more resources (e.g., time and / or frequency resources), in which case a transport block (TB) containing data is carried over the PSSCH. 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 geographical road information, cooperative awareness messages (CAM), distributed environment notification messages (DENM), and in-vehicle information (IVI) messages.

[0053]

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

[0054]

[0063] In some embodiments, the UE may operate using transmit mode 4, in which case resource selection and / or scheduling is performed by the UE rather than the base station. In some embodiments, 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 associated with various sidelink channels (e.g., sidelink-RSSI (S-RSSI) parameters), reference signal received power (RSRP) parameters associated with various sidelink channels (e.g., PSSCH-RSRP parameters), reference signal received quality (RSRQ) parameters associated with various sidelink channels (e.g., PSSCH-RSRQ parameters), and so on, and may select a channel for transmitting V2X communication based at least in part on the measured values(s).

[0055]

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

[0056]

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

[0057]

[0066] In V2X communication systems, the state of the side link channels used to carry V2X communications can fluctuate and change rapidly due to factors such as the high mobility of vehicles and associated UEs, significant fluctuations in vehicle traffic volume at different times and locations, and the diverse terrains that vehicles may traverse (e.g., densely populated urban environments, hilly environments, flat environments, etc.). Furthermore, V2X communication systems require high reliability, for example, due to mission-critical safety issues associated with autonomous vehicles. Several techniques and devices described herein improve the performance of V2X communication systems by dynamically determining parameters for V2X transmission based at least in part on dynamic factors associated with one or more vehicles, side link channels, etc.

[0058]

[0067] In some implementations, the UE may be capable of performing autonomous resource selection for V2X transmission according to various aspects of this disclosure.

[0059]

[0068] For example, a UE may determine a limit on the number of resource blocks (RBs) that the UE is permitted to use for V2X transmission. In some embodiments, the UE may determine the limit based at least partly on the congestion level of one or more sidelink channels, which may be determined at least partly on the measurement of one or more sidelink channels (for, e.g., S-RSSI, PSSCH-RSRP, etc.), the reception of SCIs associated with one or more sidelink channels, etc. For example, the UE may determine a channel busy rate (CBR) for a sidelink channel (e.g., CBR(n-100, n-1), where n-100 indicates the start of the time period and n-1 indicates the end of the time period) related to time n when resource selection is triggered for the UE, and may determine at least partly on the CBR the maximum number of RBs made available for use by the UE at time n. Alternatively, the UE may determine a limit on the number of RBs by determining the maximum number of RBs made available for use by the UE for time n (e.g., CRlimit(n)) and subtracting the number of RBs already used or scheduled by the UE for time n (e.g., CR(na, n+b), where na indicates the start of a time period and n+b indicates the end of a time period).

[0060]

[0069] The UE may determine one or more parameters for V2X transmission based at least in part on the limit on the number of RBs. In some embodiments, one or more parameters may be called one or more transmission parameters and / or one or more V2X transmission parameters. As illustrated, one or more parameters may include the modulation and coding scheme (MCS) for V2X transmission, the number of transport blocks (TBs) for V2X transmission, the number of RBs per TB for V2X transmission, the retransmission configuration for V2X transmission, and so on. In some embodiments, the UE may determine one or more parameters so that the number of RBs for V2X transmission does not exceed the limit on the number of RBs.

[0061]

[0070] For example, if a UE selects an MCS with a lower index value for a V2X transmission (e.g., allowing fewer bits per symbol), that V2X transmission will require more TB and corresponding RBs than the same V2X transmission would require if it used 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. Therefore, in some embodiments, if the limit 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 limit 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 embodiments, the UE may select from several different MCS index values, and different MCS index values ​​may be associated with different thresholds for the limit 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 TB 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 a V2X transmission. Therefore, in some embodiments, 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 embodiments, the UE may choose from several different retransmission qualities (e.g., one retransmission, two retransmissions, etc.), and different retransmission qualities may be associated with different thresholds for limiting the number of RBs.

[0063]

[0072] In some embodiments, the UE may select one or more parameters to increase or maximize the range for V2X transmissions subject to the number of RBs (e.g., the distance that can be covered by V2X transmissions and corresponding retransmissions), as will be described in more detail below with respect to Figure 5. In this way, the UE can improve reliability, enhance security, and increase the likelihood of successful reception of V2X transmissions, while operating in accordance with the limit on the number of RBs allowed for V2X transmissions.

[0064]

[0073] In V2X communication systems, sidelink channel conditions can vary significantly at different times, geographical locations, and on different frequencies. Therefore, a UE can dynamically determine one or more parameters for a V2X transmission based at least partially on the conditions present at the time the V2X transmission is scheduled. In some embodiments, the UE can determine one or more transmission parameters based at least partially on dynamic factors associated with the UE and / or vehicles associated with the UE (e.g., network traffic demand, congestion, etc., associated with one or more applications of the UE). Additionally or alternatively, the UE can determine one or more transmission parameters based at least partially on dynamic factors associated with the wireless network to which the V2X transmission will be transmitted (e.g., congestion level associated with the wireless network, carrier frequency to which the V2X transmission will be transmitted, priority of V2X transmission on the wireless network, etc.). In this way, the UE can improve or optimize the transmission of V2X messages under changing conditions.

[0065]

[0074] As an addition or alternative, the UE may determine one or more V2X transmit parameters based at least partially on one or more selected frequencies. For example, different frequencies may be associated with different CBR values ​​and therefore with a limit on the number of different RBs permitted for use by the UE. As an addition or alternative, different combinations of transmit parameters may result in different performance at different frequencies, and the UE may use this as a factor when determining one or more transmit parameters.

[0066]

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

[0067]

[0076] As an addition or alternative, the UE may determine one or more transmission parameters based at least in part on the congestion level associated with the wireless network to which the V2X transmission will be transmitted (e.g., the congestion level of the sidelink channel and / or one or more frequencies to which the V2X transmission will 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 embodiments, the UE may determine the congestion level based at least in part on the CBR, resource limits (e.g., rate control parameters, power control parameters, congestion control parameters, etc.), and measurement parameters of the wireless network (e.g., energy level).

[0068]

[0077] A 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, a UE may modulate and / or encode a V2X transmission using a selected MCS, transmit a V2X transmission using a selected number of TBs, transmit a V2X transmission using a selected number of RBs per TB, retransmit or prevent retransmission of a V2X transmission according to a selected retransmission configuration, transmit a V2X transmission on a selected carrier frequency, and so on. By taking dynamic factors into account when determining the above transmission parameters (one or more), a UE may improve the performance of a V2X transmission that is constrained by the V2X transmission (e.g., transmission range). For example, in some cases, a UE may transmit a V2X transmission using an MCS with a high index rather than dropping the V2X transmission.

[0069]

[0078] Figure 3B is an exemplary Figure 300 illustrating device-to-device communication. The first device 312 (e.g., UE312) is located in the first vehicle 310 and may move with the first vehicle 310. The second device 332 (e.g., another UE332) may be located in the second vehicle 330. In another embodiment, 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 connection 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 via NR. The first device 312 and the second device 332 can also perform short-range communication with each other via IEEE 802.11p.

[0070]

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

[0071]

[0080] NR V2V communication may offer more reliable performance than LTE V2V by providing more history-based congestion calculations and / or a more limited reliance on future periodic transmissions. The following discussion refers to NR V2V communication as an example, not an limitation, but since NR D2D communication is similar to LTE V2V communication, the following discussion may also apply to NR and LTE D2D communication.

[0072]

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

[0073]

[0082] In some embodiments, congestion control may be based on the channel busy ratio (CBR) and / or channel utilization. The CBR may represent the percentage of busy resources. The channel utilization may represent the percentage of channels being used for communication. The CBR and channel utilization may be technology-neutral, as described below. Distributed congestion control for 802.11p technology may be derived based on technology-neutral congestion control, but 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 can be an estimate of the percentage of resources considered busy / utilized. In some embodiments, a resource may be considered busy and / or utilized if a signal is decoded over such a resource, or if the energy in such a resource is above an energy threshold.

[0075]

[0084] Originally, V2X communication uses WLAN technology and operates directly between vehicle-to-vehicle (V2V) and traffic infrastructure (V2I), forming a vehicle ad-hoc network when two V2X transmitters are within each other's range. Therefore, vehicles do not require any communication infrastructure to communicate, which helps ensure safety in remote or undeveloped areas. WLAN is particularly well-suited for V2X communication due to its low latency. V2X communication includes messages known as Coordinated Recognition Messages (CAM) or Basic Safety Messages (BSM), and Distributed Environment Notification Messages (DENM). Other roadside infrastructure-related messages include Signaling Phase and Timing Messages (SPAT), Vehicle Information Messages (IVI), and Service Request Messages (SRM). The data size of these messages is very small. The wireless technology is part of the WLAN IEEE 802.11 standard family and is 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 direct communication modes, vehicles can be equipped with conventional cellular communication technologies that support V2N-based services. This V2N extension 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 location information. Route history information shows the vehicle's last location or information about a series of past locations. Traditionally, route history information has been used for road geometry estimation and target classification. In current implementations, route history information shows the vehicle's last 5 or 15 locations and is included in all BSMs.

[0077]

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

[0078]

[0087] The current implementation of including Path History (PH) and complete certificates in many BSMs is inefficient and bandwidth-intensive. This is especially true because BSMs constitute a large portion of the bandwidth usage in such scenarios. For example, BSMs constitute a large portion of the load on the already insufficient ITS bandwidth.

[0079]

[0088] The current implementation, which includes information indicating the last 5 or 15 locations within each BSM, occupies approximately 43 or 123 bytes. Full authentication is approximately 100 bytes (e.g., 125 bytes) and is included at a frequency of 2 Hz (every 0.5 seconds). Therefore, the overhead caused by including routing history and certificate information can account for approximately 47-58% of the BSM message size.

[0080]

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

[0081]

[0090] As an illustrative and non-limiting example, an HV may selectively include PH information in its BSM only if it detects an actual new vehicle near its collision zone. Other vehicles already within the HV's broadcast range can use previously received BSMs to construct the HV's path history trajectory. The HV may also include PH points in 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 may employ similar techniques for including complete certificate information, using the same or different parameters.

[0082]

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

[0083]

[0092] Figure 4 shows an example of a wireless communication system 400 that supports enhanced security message reporting operation according to an aspect of this disclosure. In some examples, the wireless communication system 400 may implement an aspect of the wireless communication system 100. For example, the wireless communication system 400 may include UE115, 115A, and 115B. Enhanced security message (e.g., BSM) reporting operation can reduce signaling overhead and latency and increase throughput. Thus, network and device performance can be improved.

[0084]

[0093] UE115, 115A, and 115B can be configured to communicate over one or more parts 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 are designated as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. Although a portion of FR1 is above 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue can 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 to 300 GHz) designated as the "mmWave" band by the International Telecommunication Union (ITU).

[0085]

[0094] With the above aspects in mind, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that are below 6GHz, within FR1, or may include intermediate band frequencies when used herein. Furthermore, unless otherwise specified, terms such as "mmWave" may broadly refer to frequencies that are within the intermediate band, within FR2, or within the EHF band when used herein.

[0086]

[0095] Note that the SCS may be equal to 15, 30, 60, or 120 kHz for some data channels. UE115, 115A, and 115B may be configured to communicate via one or more component carriers (CCs), such as the typical first CC481, second CC482, third CC483, and fourth CC484. While four CCs are shown, this is for illustrative purposes only, and more or fewer 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 physical downlink control channels (PDCCH), physical downlink sharing channels (PDSCH), physical uplink control channels (PUCCH), physical uplink sharing channels (PUSCH), physical sidelink control channels (PSCCH), physical sidelink sharing channels (PSSCH), or physical sidelink feedback channels (PSFCH). Such transmissions may be scheduled by aperiodic grants and / or periodic grants.

[0088]

[0097] Each periodic grant may have a corresponding configuration, such as configuration parameters / settings. Periodic grant configurations 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 bandwidth, bandwidth parts, HARQ processes, TCI states, RS, control channel resources, data channel resources, or a combination thereof. Additionally or alternatively, one or more CCs may have, or be assigned to, a cell ID, a bandwidth part (BWP) ID, or both. A cell ID may include a unique cell ID for the CC, a virtual cell ID, or a specific cell ID for a particular CC among multiple CCs. Additionally or alternatively, one or more CCs may have, or be assigned to, a HARQ ID. Each CC may also have a corresponding management function, such as beam management, BWP switching functionality, or both. In some implementations, two or more CCs are quasi-colocated so that the CCs have the same beam and / or the same symbol.

[0090]

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

[0091]

[0100] The UE115 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, memory 404, transmitter 410, receiver 412, encoder 413, decoder 414, device-to-device (D2D) communication manager 415, BSM manager 416, and antennas 252a-r. The processor 402 may be configured to execute instructions stored in memory 404 to perform the operations described herein. In some implementations, the processor 402 includes or corresponds to a controller / processor 280, and the memory 404 includes or corresponds to memory 282. The memory 404 may also be configured to store device information data 406, channel status data 408, trigger condition data 442, configuration data 444, or a combination thereof, as further described herein.

[0092]

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

[0093]

[0102] The channel status data 408 includes or corresponds to data related to or corresponding to channel quality or congestion status for device-to-device communication operation. For example, the channel status data 408 may include channel quality measurements or determined values. The channel status data 408 may include or correspond to received power thresholds or ranges, or received quality thresholds or ranges. For example, the channel status data 408 may utilize channel quality indicators (CQI), RSRP, RSRQ, signal-to-interference-plus-noise ratios (SINR), etc. The channel status data 408 may further include operations for determining or adjusting the quality status. For example, the channel status data 408 may include operations for determining the quality status based on one or more parameters, such as channel congestion. For illustrative purposes, the UE115 may utilize the packer error rate (PER) to determine congestion.

[0094]

[0103] Trigger condition data 442 indicates or includes data corresponding to trigger conditions for the inclusion of information into the BSM. For example, trigger condition data 442 may include data indicating specific trigger condition parameter values ​​or ranges 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, trigger condition data 442 may include data indicating specific trigger condition parameter values ​​or ranges 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. Exemplary examples of trigger condition types include timing conditions, new device determination conditions, collision zone detection conditions, channel quality conditions (e.g., CQI), congestion-related conditions (e.g., PER), or combinations thereof. Conditions may be used sequentially or in parallel with each other. For example, there may be several conditions that must be met for route history information to be included in the BSM, and UE 115 can determine whether either A or B is met before determining whether C or D is met, only if at least one of A or B is met. As another example, certificate information can be included in security messages using conditions different from those used for additional conditions or route history information.

[0095]

[0104] Configuration data 444 includes or corresponds to data associated with enhanced BSM feedback and reporting operations for sidelink communication. Configuration data 444 may include one or more types of BSM feedback operation modes, and / or thresholds or conditions for switching between BSM feedback modes and / or configurations. For example, 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 over 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 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 currently known or to be developed that enables two or more electronic devices to communicate. In some implementations, the transmitter 410 and receiver 412 may be replaced by transceivers. In addition or alternative, the transmitter 410, receiver 412, or both may include or correspond to one or more components of the UE 115 described with reference to Figure 2.

[0097]

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

[0098]

[0107] The BSM manager 416 may be configured to determine and perform BSM mode operations. 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 routing history information or certificate information in a particular BSM. In implementations where 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 for how long.

[0099]

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

[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, UE115A and 115B may be configured to transmit and / or receive data over direct device-to-device connections, local area networks (LANs), wide area networks (WANs), modem-to-modem connections, the Internet, intranets, extranets, cable transmission systems, cellular communication networks, any combination of the above, or any other communication networks currently known or to be developed that enable two or more electronic devices to communicate. In some implementations, the transmitter 434 and receiver 436 may be replaced by transceivers. In addition or alternative, the transmitter 434, receiver 436, or both may include or correspond to one or more components of the UE115 described with reference to Figure 2.

[0101]

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

[0102]

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

[0103]

[0112] During operation, devices in the wireless communication system 400 perform extended safety message (e.g., BSM) reporting operations. For example, UE115, 115A, and 115B exchange transmissions via D2D communication, such as over a sidelink channel. In the example in Figure 4, UE115A transmits message 452. Message 452 may contain or correspond to a beacon-type message or a broadcast message. In some implementations, message 452 contains a BSM.

[0104]

[0113] UE115 may receive message 452 and perform one or more evaluations or decisions on or using message 452. Based on message 452, UE115 may determine the location of UE115A and use that location to determine whether UE115A is in or will be in UE115's collision detection zone. Additionally or alternatively, UE115 may determine an identifier for the first UE115A. For example, UE115 may extract or parse a temporary identifier from message 452 and use that temporary identifier to determine whether UE115A is "new" to UE115, such as not being in a map of devices held by UE115. In certain implementations, UE115 may further refer to or generate an LDM based on the message and use the LDM to determine whether the first UE115A is new. For illustrative purposes, UE115 can correlate the information in message 452 with previously received information to determine whether UE115a, 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 the identification of trigger conditions, such as a new device or a device in UE115's collision zone, UE115 may decide to include the information in the next BSM. Examples of trigger conditions are further illustrated with reference to Figure 5.

[0105]

[0114] As shown in the example in Figure 4, UE115 decides to include routing history information, a complete certificate, or both in the following security message (e.g., BSM). UE115 generates and transmits a security message containing the routing history information and / or the complete certificate. For example, UE115 broadcasts security message 454 (e.g., BSM). One of several other UEs, such as UE115A and UE115B, may receive security message 454 and extract the routing history information and the complete certificate. The routing history information and / or the complete certificate may enable the receiving UE to identify a new device and / or avoid and reduce collisions or near-collisions. By selectively including routing history information and / or certificate information, UEs can reduce network signaling overhead.

[0106]

[0115] Therefore, UE115, 115A, and 115B may be able to perform safe message operation (e.g., BSM operation) more efficiently. Accordingly, Figure 4 illustrates the enhanced safe message reporting operation. Using the enhanced safe message reporting operation may enable improvements when operating in D2D communication. Performing the enhanced safe message reporting operation enables a reduction in bandwidth / spectrum waste when sending and receiving safe messages, and thus enables enhanced UE and network performance by increasing throughput and reducing latency. The efficiency is achieved without reducing the safety or effectiveness of safe message transmission, since safe message transmission is still transmitted under certain conditions where collisions are more likely to occur.

[0107]

[0116] Figure 5 shows a diagram of an exemplary wireless communication system that supports extended safety message reporting operation in one or more embodiments. The example in Figure 5 includes devices similar to those described in Figures 1, 2, and 4, such as UE115, 115A, and 115B. Devices such as UE115a-115c in Figure 5 may include one or more of the components described in Figures 2 and 4. In Figure 5, these devices may utilize antennas 252a-r, transmitter 410, receiver 412, encoder 413, and / or decoder 414 for transmitting and receiving communications, or they may utilize antennas 234a-t, transmitter 434, receiver 436, encoder 437, and / or decoder 438.

[0108]

[0117] Referring to Figure 5, Figure 500 shows dynamic information inclusion in BSM operation. The example shown in Figure 5 shows multiple vehicle UEs or HVs, but in other implementations, the operation may occur between other wireless communication devices such as non-vehicle UEs and base stations.

[0109]

[0118] In 510, the first UE115a transmits a message. For example, the first UE115a is connected to the second UE115b and transmits a unicast message to the second UE115b. In another example, the first UE115a transmits a broadcast message, and at least the second UE115b receives the broadcast message. The message may be transmitted via 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 PH or certificate information. In some other implementations, the BSM does not include PH or certificate information. In some such implementations, the first UE115a may determine that the BSM does not include PH or certificate information based on its determination that the trigger condition is not met.

[0111]

[0120] The second UE115b may receive and decode messages. The second UE115b may update or add device-related information for the first UE115a to its stored information. For example, the second UE115b may determine the location of the first UE115a based on the message, or update its record (e.g., LDM) based on the message. After receiving a message, the second UE115b may decide to send a BSM. For example, the second UE115b may decide to send a BSM based on timing, such as in response to a normal operating procedure for sending a BSM every X duration. As another example, the second UE115b may decide to send a BSM in response to a specific trigger, such as determining that a new device exists (e.g., a new temporary ID) or determining that a device is close to the second UE115b.

[0112]

[0121] In 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 including PH information are met in connection with determining to transmit a BSM. In some implementations, the second UE 115b determines how much PH information to include, such as a certain number of past locations. Additionally or alternatively, the second UE 115b determines how long the PH information should be transmitted. In such implementations, the second UE 115b may determine this based on how many trigger conditions are met, which trigger conditions are met, or a combination thereof. For example, if a new device condition is met, the second UE115b may decide to transmit more or 15 past positions for a shorter time period compared to when the collision zone detection condition is met, and the second UE115b may transmit 5 past positions for a longer time period (e.g., until the collision is resolved / avoided).

[0113]

[0122] In 520, the second UE115b transmits a BSM containing PH information. For example, the BSM manager 416 or 440 of the second UE115b generates a BSM containing route history information and broadcasts it to other devices such as the first and third UE115a and 115c.

[0114]

[0123] From 520 to 525, the second UE115b transmits additional BSMs containing PH information. For example, the BSM manager 416 or 440 of the second UE115b generates one or more second BSMs containing routing history information and broadcasts them to other devices. The PH information of 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 one or more second BSMs may contain fewer PHs.

[0115]

[0124] In 530, the second UE115b uses BSM transmission. For example, the second UE115b's BSM manager 416 or 440 generates a third BSM that does not contain routing history information and broadcasts it to other devices. The second UE115b can determine that a BSM does not contain routing history information based on whether it satisfies the duration or number of BSMs that have routing history information from the decision in 515. In some such implementations, the second UE115b can further determine that a BSM does not contain PH or certificate information based on the determination in 530 that the trigger condition is not met.

[0116]

[0125] In 535, the third UE115c transmits a message (e.g., a second message). For example, the third UE115c is connected to the second UE115b and transmits a unicast message to the second UE115b. In another example, the third UE115c transmits a broadcast message, and at least the second UE115b receives the broadcast message. Messages may be transmitted via a sidelink communication channel or a D2D communication channel. In some implementations, messages may include or correspond to BSM or beacon transmissions.

[0117]

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

[0118]

[0127] The second UE115b may receive and decode a message. The second UE115b may update or add device-related information for the third UE115c to its stored information. For example, the second UE115b may determine the location of the third UE115c based on the message, or update its record (e.g., LDM) based on the message. After receiving the message, the second UE115b may decide to send a BSM. For example, the second UE115b may decide to send a BSM based on timing, such as in response to a normal operating procedure for sending a BSM every X duration. As another example, the second UE115b may decide to send a BSM in response to a specific trigger, such as determining that a new device exists (e.g., a new temporary ID) or determining that a device is close to the second UE115b.

[0119]

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

[0120]

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

[0121]

[0130] From 545 to 550, the second UE115b transmits additional BSMs containing certificate information. For example, the BSM manager 416 or 440 of the second UE115b generates one or more fifth BSMs containing routing history information and broadcasts them to other devices. The certificate information of 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 one or more fifth BSMs may include digest information.

[0122]

[0131] In some implementations, the trigger condition for including additional device-related information in the safety message corresponds to the detection of a "new" vehicle within the transmitting device's collision zone. Since the device uses a temporary ID that changes periodically, such as every five minutes, the reception of a new temporary ID does not necessarily indicate a new vehicle. Therefore, the received temporary ID should be correlated with the movement (past or predicted movement) of other devices or vehicles to rule out the possibility that the "new" temporary ID does not belong to an existing known neighboring device or vehicle that the transmitting device already knows. In some such implementations, the transmitting device uses LDM to determine whether the new temporary ID corresponds to a new device or to a temporary ID change.

[0123]

[0132] In some implementations, collision zone trigger conditions are based on distance, time to collision (TTC), or both. As an illustrative and non-limiting example, collision zone trigger conditions are based on both distance and TTC conditions. Below are exemplary formulas for 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 velocity or operating conditions. In addition, the TTC condition may be static or dynamic and may be based on the size of the collision zone. The distance and TTC between devices may be calculated based on the velocity and trajectory of the transmitting device, as well as the estimated trajectory of the other device.

[0124]

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

[0125]

number

[0126] In the above formula,

[0127]

number

[0128] V is the channel quality index, where N(k) is the number of vehicles within a given range of vehicles. A The range can be determined based on PER, such as by vPERRange. A This is the transmission interval (V) between subsequent BSM transmissions of the vehicle. A ) and here, ITT A The time interval is ∈{100,...,600}ms. N can be arbitrarily chosen, for example, N=50, which is the average number of BSM transmissions before resource re-selection. 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 to include more such PH information (which is beneficial as it implies lower vehicle density and therefore lower channel congestion). Also, a higher CQI indicates worse channel conditions, and n will be higher.

[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 packet error rate (PER) in the BSM received from an adjacent device (e.g., adjacent RV) at the transmitting device (e.g., HV). Channel reciprocity indicates that neighboring devices also suffer from dropped BSMs from the transmitting device, which may prevent the receiving device's ability to reconstruct the past position and trajectory of the transmitting device (leading to an inaccurate future trajectory / predicted trajectory). In such cases, it may be 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] By way of illustrative and non-limiting example, the CQI can be determined by the following formula.

[0131]

Number

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

[0133]

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

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

[0134]

[0137] While CQI is used as an estimate of congestion and / or error rate, other parameters can be used in addition to or instead of CQI. Such other or additional parameters include block error rate (BLER), PER, SINR, RSRP, congestion metric, utilization metric, etc.

[0135]

[0138] As an addition or alternative, the base or standard inclusion rate may be increased to reduce the frequency with which routing history and / or certificate information is included in secure messages. For example, certificate information may be included every 450ms in some standards (e.g., when certificates may be changed or updated every 450ms), and this inclusion rate may be relaxed. For illustrative purposes, a 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 an adjustment to the base inclusion rate / frequency), and the trigger condition for the inclusion of additional information may correspond to a timer for this extended or adjusted base inclusion rate / frequency. As an illustrative example, a certificate information trigger condition may be a certificate change condition or a timer. In response to the condition being met or the timer expiring, the UE decides to include the certificate information in at least the following BSMs.

[0136]

[0139] Therefore, in the example in Figure 5, the wireless communication device performs the extended BSM reporting operation by utilizing the dynamic information inclusion operation for BSM transmission. The example in Figure 5 concerns an example with three devices, but other examples may use additional devices and / or device types.

[0137]

[0140] As an addition or alternative, other implementations may include, delete, or replace one or more of the operations in Figures 3 to 5. For example, in some implementations, one or more exemplary steps in Figures 4 and 5 may be used together. For illustrative purposes, the trigger condition in Figure 4 may be used together with the trigger condition in Figure 5.

[0138]

[0141] Figure 6 is a flowchart showing an exemplary block performed by a wireless communication device (e.g., a UE or base station) configured according to one aspect of the present disclosure. The exemplary block is also described with respect to a UE115 as shown in Figure 8. Figure 8 is a block diagram showing a UE115 configured according to one aspect of the present disclosure. The UE115 includes structures, hardware, and components as illustrated for the UE115 in Figures 2 and / or 4. For example, the UE115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in memory 282 and controls components of the UE115 that provide the features and functions of the UE115. The UE115 transmits and receives signals via wireless radios 801a-r and antennas 252a-r under the control of the controller / processor 280. The wireless radios 801a-r include various components and hardware, including modulators / demodulators 254a-r, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, and a TX MIMO processor 266, as shown in Figure 2 for the UE115. As shown in the example in Figure 8, the memory 282 stores device-to-device (D2D) logic 802 (e.g., C-V2X or ITS logic), security 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 conditions, certificate trigger conditions, or a combination thereof), mapping data 807 (e.g., LDM data), and configuration data 808. The data stored in memory 282 (802-808) may include, or correspond to, the data stored in memory 404 in Figure 4 (406, 408, 442, 444).

[0139]

[0142] In block 600, a wireless communication device such as a UE (e.g., UE115, UE415A, or UE415B) or a network device (e.g., base station 105) receives a C-V2X message from another wireless communication device. For example, UE115 receives message 452 in Figure 4, message 510 in Figure 5, or message 535 in Figure 5 from another wireless communication device (e.g., UE115a, UE115b, UE415A, UE415B, or base station 105), as described with reference to Figures 4 and 5. For example, the receiver of UE115 (e.g., receiving processor 258 or receiver 412) receives a beacon message, a safety message (e.g., BSM), or other ITS message from UE415A 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 Figures 3-5. The message may optionally include certificate information (e.g., complete or specific certificate information) and / or route history information (e.g., second route history information) of other wireless communication devices. Additionally or alternatively, the wireless communication device may determine channel state information based on the message, such as CQI, estimated heading / trajectory / route for other wireless communication devices, collision metrics (e.g., collision zone overlap, TTC, range estimate, etc.), or a combination thereof.

[0140]

[0143] In block 601, UE115 transmits a safety message containing route history information in response to determining that the route history information trigger condition has been met based on the C-V2X message. For example, UE115 transmits safety message 454 in Figure 4, or BSM520 or BSM525 in Figure 5, as described with reference to Figures 4 and 5. For example, the transmitter of UE115 (e.g., the transmit processor 220 or transmitter 410) transmits a BSM containing route history information via the wireless radios 801a-r and antennas 252a-r in response to, or based on, that any of the route history information trigger conditions described with reference to Figures 3-5 have been met. The BSM may be transmitted (broadcast) to multiple devices (including other wireless communication devices). In addition, a wireless communication device may transmit additional BSMs containing route history information based on determining that the route history trigger condition has been met. These additional BSMs have similar route history information to the original BSM and may include updated route history information indicating updated locations.

[0141]

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

[0142]

[0145] In one or more embodiments, the techniques for supporting the extended BSM reporting operation may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below or elsewhere in this specification with respect to one or more other processes or devices. In a first embodiment, supporting the extended BSM reporting operation may include an apparatus configured to receive C-V2X messages from a wireless communication device (e.g., another wireless communication device). The apparatus may be further configured to send a safety message containing route history information in response to determining that a route history information trigger condition has been met based on the C-V2X message. In addition, the apparatus may perform or operate according to one or more embodiments, as described below. In some implementations, the apparatus may include a wireless device such as a UE. In some implementations, the apparatus may include at least one processor and memory coupled to that processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other implementations, the apparatus may include a non-temporary computer-readable medium recording program code, which may be executable by a computer to cause the computer to perform the operations described herein with respect to the apparatus. In some implementations, the device may include one or more means configured to perform the operations described herein. In some implementations, the wireless communication method may include one or more operations described herein with respect to the device.

[0143]

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

[0144]

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

[0145]

[0148] In the 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 recognition message (CAM), or a distributed environment notification message (DENM).

[0146]

[0149] In the fifth embodiment, in combination with one or more of the first to fourth embodiments, the route history information includes multiple previous locations of the wireless communication device.

[0147]

[0150] In the sixth aspect, in combination with one or more of the first to fifth aspects, the C-V2X message from another wireless communication device includes a beacon message, a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment notification message (DENM).

[0148]

[0151] In the seventh aspect, in combination with one or more of the first to sixth aspects, a C-V2X message from another wireless communication device includes second path history information of the other wireless communication device, and the wireless communication device determines the trajectory of the other wireless communication device (e.g., based on the second path history information, one or more past BSMs, heading information, and the path prediction of the other wireless communication device), and the wireless communication device determines 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 embodiment, which is a combination of one or more of the first to seventh embodiments, the device is configured to determine, by a wireless communication device, that a route history information trigger condition is met, and to determine, based on the wireless communication device's determination that the route history information trigger condition is met, the number of safety messages to include route history information.

[0150]

[0153] In the ninth aspect, in combination with one or more of the first to eighth aspects, the C-V2X message includes a temporary ID, and the device is configured such that a wireless communication device determines, based on a local dynamic map (LDM), whether the temporary ID corresponds to a new or unknown device, and the wireless communication device decides, based on the fact that the temporary ID is associated with a new or unknown device, to include routing history information in the secure message.

[0151]

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

[0152]

[0155] In the eleventh embodiment, in combination with one or more of the first to tenth embodiments, the apparatus is configured such that a wireless communication device determines a range estimate (e.g., collision zone) for other wireless communication devices based on a C-V2X message, a wireless communication device determines a time to collision (TTC) estimate based on a C-V2X message, a wireless communication device compares the range estimate to a range condition, a wireless communication device compares the TTC estimate to a TTC condition, and, based on whether the range estimate is less than the range condition, the TTC estimate is less than the TTC condition, or both, the wireless communication device decides to include path history information in the safety message.

[0153]

[0156] In the twelfth embodiment, in combination with one or more of the first to eleventh embodiments, the route history information trigger condition is a CQI trigger condition, and the device is configured such that a wireless communication device determines the CQI of the wireless communication device, the wireless communication device compares the CQI with a CQI threshold, and the wireless communication device determines that the CQI trigger condition is met because the CQI is less than or equal to the CQI threshold.

[0154]

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

[0155]

[0158] In the 14th embodiment, in combination with one or more of the first to 13 embodiments, the wireless communication device is a host vehicle (HV). The other wireless communication device is a remote vehicle (RV).

[0156]

[0159] Therefore, wireless communication devices can perform enhanced secure message reporting behavior and dynamic inclusion of routing history information and / or certificate information into secure messages. By performing enhanced secure message behavior, or by dynamic inclusion of routing history information and / or certificate information within secure messages, network performance can be improved by increasing throughput and reducing overhead and latency through reduced signaling overhead.

[0157]

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

[0158]

[0161] In block 700, a wireless communication device such as a UE (e.g., UE115, UE415A, or UE415B) or a network device (e.g., base station 105) receives a C-V2X message from another wireless communication device. For example, UE115 receives message 452 in Figure 4, message 510 in Figure 5, or message 535 in Figure 5 from another wireless communication device (e.g., UE115a, UE115b, UE415A, UE415B, or base station 105), as described with reference to Figures 4 and 5. For example, the receiver of UE115 (e.g., receiving processor 258 or receiver 412) receives a beacon message, a safety message (e.g., BSM), or other ITS message from UE415A 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 Figures 3-5. The message may optionally include certificate information (e.g., complete or specific certificate information) and / or route history information (e.g., second route history information) of other wireless communication devices. Additionally or alternatively, the wireless communication device may determine channel state information based on the message, such as CQI, estimated heading / trajectory / route for other wireless communication devices, collision metrics (e.g., collision zone overlap, TTC, range estimate, etc.), or a combination thereof.

[0159]

[0162] In block 701, the wireless communication device sends a security message containing certificate information in response to determining that the certificate information trigger condition is met based on the C-V2X message. For example, the wireless communication device sends security message 454 in Figure 4, or BSM 545 or BSM 550 in Figure 5, which contains certificate information, as described with reference to Figures 4 and 5. For example, the transmitter of UE115 (e.g., the transmit processor 220 or transmitter 410) sends a BSM containing the complete certificate via the wireless radios 801a-r and antennas 252a-r in response to, or based on, that any of the certificate information trigger conditions described with reference to Figures 3-5 are met. The BSM may be transmitted (broadcast) to multiple devices. Furthermore, the wireless communication device may send additional BSMs containing certificate information based on determining that the certificate information trigger condition is met.

[0160]

[0163] A wireless communication device (e.g., a UE or base station) may perform additional blocks in other implementations (or the wireless communication device may be configured to perform additional operations). 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 of the embodiments described with reference to Figures 3 to 8.

[0161]

[0164] In one or more embodiments, techniques for supporting extended BSM reporting operations may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below or elsewhere in this specification with respect to one or more other processes or devices. In a first embodiment, supporting extended BSM reporting operations may include an apparatus configured to receive C-V2X messages from a wireless communication device (e.g., another wireless communication device). The apparatus may be further configured to send a security message containing certificate information in response to determining that a certificate information trigger condition has been met based on the C-V2X message. In addition, the apparatus may perform or operate according to one or more embodiments, 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 memory coupled to that processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other implementations, the apparatus may include a non-temporary computer-readable medium recording program code, which may be computer-executable to cause the computer to perform the operations described herein with respect to the apparatus. In some implementations, the device may include one or more means configured to perform the operations described herein. In some implementations, the wireless communication method may include one or more operations described herein with respect to the device.

[0162]

[0165] In the second embodiment, in combination with the first embodiment, 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 embodiment, the device is configured such that, in combination with one or more of the first to second embodiments, the wireless communication device determines that the certificate information trigger condition is not met, and based on this determination, the wireless communication device refrains from including the certificate information in the second BSM, and the wireless communication device transmits the second BSM without the certificate information.

[0164]

[0167] In the fourth embodiment, the partial certificate information, either alone or in combination with one or more of the first to third embodiments, includes a digest of the certificate information. In a particular implementation, the indicated digest identifies the certificate information (e.g., a previously sent complete certificate). In another particular implementation, the digest includes or indicates message source authentication information, integrity check information, or both.

[0165]

[0168] In the 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 recognition message (CAM), or a distributed environment notification message (DENM).

[0166]

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

[0167]

[0170] In the seventh aspect, in combination with one or more of the first to sixth aspects, the C-V2X message from another wireless communication device includes a beacon message, a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment notification message (DENM).

[0168]

[0171] In the eighth aspect, in combination with one or more of the first to seventh aspects, a C-V2X message from another wireless communication device includes second path history information of the other wireless communication device, and the device is configured such that the wireless communication device determines the trajectory of the other wireless communication device (for example, based on the second path history information, one or more past BSMs, heading information, and path predictions of the other wireless communication device), and the wireless communication device determines 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 the ninth aspect, in combination with one or more of the first to eighth aspects, the C-V2X message includes a temporary ID, and the device is configured such that a wireless communication device determines, based on a local dynamic map (LDM), whether the temporary ID corresponds to a new or unknown device; the wireless communication device determines, whether the range or TTC associated with the new or unknown device satisfies range conditions, TTC conditions, or both; and the wireless communication device decides to include certificate information in the security message based on the temporary ID associated with the new or unknown device and the new or unknown device that satisfies range conditions, TTC conditions, or both.

[0170]

[0173] In the tenth embodiment, in combination with one or more of the first to ninth embodiments, the certificate information trigger condition is a CQI trigger condition, and the device is configured such that the wireless communication device determines the CQI of the wireless communication device, the wireless communication device compares the CQI with a CQI threshold, the wireless communication device determines whether the CQI trigger condition is met by the CQI being less than or equal to the CQI threshold, and the wireless communication device decides to include the certificate information in the secure message based on the determination that the CQI trigger condition is met by the CQI being less than or equal to the CQI threshold.

[0171]

[0174] In an eleventh embodiment, combined with one or more of the first to tenth embodiments, the certificate information trigger condition is a certificate change condition, and the device is configured such that a wireless communication device determines a certificate inclusion frequency for a base frequency greater than 450 ms (e.g., standard or base inclusion frequency) for inclusion of certificate information after a certificate change, the wireless communication device sets a timer based on the certificate inclusion frequency, and the wireless communication device decides to include the certificate information in a security message based on the expiration of the timer.

[0172]

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

[0173]

[0176] In the 13th embodiment, in combination with one or more of the first to 12 embodiments, the device is configured to determine critical events by a wireless communication device. Critical events include acceleration events, deceleration events, direction change events, activation of safety systems (e.g., ABS, traction control, driver assistance), or a combination thereof, and the wireless communication device, based on the detection of a critical event, decides to include certificate information in a safety message.

[0174]

[0177] In the 14th embodiment, in combination with one or more of the first to 13 embodiments, the wireless communication device operates in an Intelligent Transportation System (ITS) mode of the Society of Automotive Engineers (SAE) or the European Telecommunications Standards Institute (ETSI).

[0175]

[0178] In some implementations, another wireless communication device, such as another UE or base station, sends a C-V2X message to a wireless communication device, and receives a security message from the wireless communication device that either contains route history information in response to determining that a route history information trigger condition has been met based on the C-V2X message, or contains certificate information in response to determining that a certificate information trigger condition has been met based on the C-V2X message.

[0176]

[0179] Therefore, wireless communication devices can perform enhanced secure message reporting behavior and dynamic inclusion of routing history information and / or certificate information into secure messages. By performing enhanced secure message behavior, or by dynamic inclusion of routing history information and / or certificate information within secure messages, network performance can be improved by increasing throughput and reducing overhead and latency through reduced signaling overhead.

[0177]

[0180] Those skilled in the art will understand that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0178]

[0181] With respect to Figures 1 to 8, the components, functional blocks, and modules described herein include, among other examples, processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, or any combination thereof. Software should be broadly interpreted, in particular among the examples, to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, regardless of the names used, such as software, firmware, middleware, microcode, and hardware description languages. In addition, the features considered herein may be implemented via dedicated processor circuits, via executable instructions, or a combination thereof.

[0179]

[0182] Those skilled in the art will further understand that the various exemplary logic blocks, modules, circuits, and algorithmic steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly demonstrate this hardware-software compatibility, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art will also readily recognize that the described functionality can be implemented in various ways for specific applications, but such implementation decisions should not be construed as causing a departure from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein are merely examples, and that components, methods, or interactions of various aspects of this disclosure can be combined or implemented in ways other than those illustrated and described herein.

[0180]

[0183] The various exemplary logics, logic blocks, modules, circuits, and algorithmic processes described in relation to the implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. Hardware-software compatibility is briefly described functionally and illustrated in the various exemplary components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0181]

[0184] Hardware and data processing devices used to implement the various exemplary logics, logic blocks, modules, and circuits described in relation to the embodiments disclosed herein may be implemented or run 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, the processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. In some implementations, specific processes and methods may be performed by circuit configurations specific to a given function.

[0182]

[0185] In one or more embodiments, the functions described may be implemented in hardware, digital electronic circuit configurations, 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 modules of computer programs, i.e., computer program instructions encoded on a computer storage medium for execution by a data processing device or for controlling the operation of a data processing device.

[0183]

[0186] Where implemented in software, the functionality may be stored on or transmitted via computer-readable media as one or more instructions or codes. The processes of the methods or algorithms disclosed herein may be executed in processor-executable software modules that reside on computer-readable media. Computer-readable media include both computer storage media and communication media, including any media that can enable the transfer of computer programs from one location to another. Storage media may be any available media accessible by a computer. Such computer-readable media may include, but are not limited to, 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 media that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Any connection may also be appropriately referred to as computer-readable media. The terms "Disk" and "Disc" as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where a disk typically reproduces data magnetically, and a disc reproduces data optically using a laser. Combinations of the above should also be included within the scope of computer-readable media.In addition, the operation of a method or algorithm may exist on machine-readable and computer-readable media, which may be incorporated into a computer program product as one or any combination or set of code and instructions.

[0184]

[0187] Various modifications of the implementations described herein 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. Accordingly, the claims should not be limited to the implementations shown herein, but should be given the broadest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0185]

[0188] In addition, it will be readily apparent to those skilled in the art that the terms “upper” and “lower” are sometimes used to facilitate the description of a figure, indicating a relative position corresponding to the orientation of the figure on a properly oriented page, and may not reflect the proper orientation of any implemented device.

[0186]

[0189] Some 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 separately or in any suitable partial combination in multiple implementations. Furthermore, features may be described above as working in several combinations, and may even be initially claimed as such, but one or more features from a claimed combination may, in some cases, be removed from that combination, and the claimed combination may be a partial combination or a variation of a partial combination.

[0187]

[0190] Similarly, while operations are shown in a specific order in the diagrams, this should not be understood as requiring that such operations be performed in a specific or sequential order, or that all shown operations be performed, in order to achieve the desired result. Furthermore, the diagrams may schematically illustrate another exemplary process in the form of a flowchart. However, other operations not shown may be incorporated into the schematically illustrated exemplary process. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some situations, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system components in the implementation forms described above should not be understood as requiring such separation in all implementation forms, and it should be understood that the program components and systems described may generally be integrated together within a single software product or packaged within multiple software products. In addition, several other implementation forms fall within the scope of the following claims. In some cases, the actions embodied in the claims may be performed in a different order and still achieve the desired result.

[0188]

[0191] As used herein, including in the claims, the term “or” means, when used in a list of two or more items, that any one of the listed items may be taken alone, or any combination of two or more of the listed items may be taken. For example, if a composition is described as containing component 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” when used in a list of items ending in “at least one of” means a disjunctive list, for example, that the list “at least one of A, B, or C” means any of these in the case of A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination thereof. As will be understood by those skilled in the art, the term “substantially” is defined as the majority of the specified (including the specified, for example, substantially 90 degrees includes 90 degrees, substantially parallel includes parallel), but not necessarily all of it. In any disclosed implementation, the term “substantially” may be replaced by “within [percentage] of” the specified, where the percentage includes 0.1, 1, 5, or 10 percent.

[0189]

[0192] The above description in this disclosure is provided so that any person skilled in the art can create or use this disclosure. Various modifications to this disclosure will be readily apparent to a person skilled in the art, and the general principles defined herein can be applied to other modifications without departing from the spirit or scope of this disclosure. Accordingly, this disclosure is not intended to be limited to the examples and designs described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein. The invention described in the original claims of this application is listed below. [C1] A method of wireless communication, A wireless communication device receives cellular vehicle-to-everything (C-V2X) messages from another wireless communication device, A method comprising: transmitting a safety message containing route history information in response to the wireless communication device determining that a route history information trigger condition has been met based on the C-V2X message. [C2] The method according to C1, wherein the route history information trigger condition includes a collision zone condition, a channel quality condition, a new vehicle condition, or a combination thereof. [C3] The method according to C1, wherein the transmission of a safety message that does not satisfy the route history information trigger condition does not include the route history information. [C4] The method according to C1, wherein the safety message includes a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment notification message (DENM). [C5] The method according to C1, wherein the route history information includes a plurality of previous locations of the wireless communication device. [C6] The method according to C1, wherein the C-V2X message from the other wireless communication device includes a beacon message, a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment notification message (DENM). [C7] The C-V2X message from the other wireless communication device includes second route history information of the other wireless communication device, and the method The wireless communication device determines the trajectory of the other wireless communication device, The wireless communication device determines 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, The method of C1, further comprising: the wireless communication device deciding to include the route history information in the safety message based on the range estimate or the TTC estimate. [C8] The wireless communication device determines that the route history information trigger condition is met, The method according to C1, further comprising determining the number of safety messages that include the route history information based on the wireless communication device's determination that the route history information trigger condition has been met. [C9] A device, At least one transceiver, Memory and The system comprises at least one transceiver and at least one processor coupled to the memory, wherein the at least one processor is The transceiver receives a cellular vehicle-to-everything (C-V2X) message from a wireless communication device via at least one of the transceivers. A device configured to transmit a safety message containing route history information via at least one transceiver in response to determining that a route history information trigger condition has been met based on the C-V2X message. [C10] The C-V2X message includes a temporary ID, and at least one processor determines, based on a local dynamic map (LDM), whether the temporary ID corresponds to a new or unknown device. The apparatus according to C9, further configured to determine whether to include the route history information in the security message based on whether the temporary ID is associated with a new or unknown device. [C11] In order to determine whether the temporary ID corresponds to the new or unknown device based on the LDM, at least one processor: The temporary ID is compared with the temporary ID stored in the LDM. The predicted trajectory of the wireless communication device is compared with the stored predicted trajectory of the LDM. The apparatus according to C10, configured to determine that the wireless communication device is a new or unknown device if the temporary ID or predicted trajectory does not match the stored temporary ID or the stored predicted trajectory of the LDM. [C12] The at least one processor, Based on the C-V2X message, the range estimate for the wireless communication device is determined. Based on the aforementioned C-V2X message, an estimated time to collision (TTC) is determined. Compare the estimated range with the range conditions, The TTC estimate is compared with the TTC conditions. The apparatus according to C9, further configured to determine whether to include the route history information in the safety message based on whether the range estimate is less than the range condition, whether the TTC estimate is less than the TTC condition, or both. [C13] The route history information trigger condition is a channel quality indicator (CQI) trigger condition, and the at least one processor is Determine the CQI of the aforementioned device, The aforementioned CQI is compared with the CQI threshold, The apparatus according to C9, further configured to determine that the CQI trigger condition is met if the CQI is less than or equal to the CQI threshold. [C14] The apparatus according to C9, wherein the apparatus includes user equipment (UE). [C15] The apparatus according to C9, wherein the apparatus includes a host vehicle (HV) and the wireless communication device includes a remote vehicle (RV). [C16] A method of wireless communication, A wireless communication device can receive Cellular Vehicle-to-Everything (C-V2X) messages from another wireless communication device, A method comprising: transmitting a security message containing certificate information in response to the wireless communication device determining that a certificate information trigger condition is met based on the C-V2X message. [C17] The method according to C16, wherein 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. [C18] The wireless communication device determines that the certificate information trigger condition is not met, Based on the wireless communication device's determination that the certificate information trigger condition is not met, the certificate information is not included in the second security message. The method according to C16, further comprising transmitting the second security message without certificate information by the wireless communication device. [C19] The method according to C18, wherein the second security message includes partial certificate information, and the partial certificate information includes a digest of the certificate information. [C20] The method according to C16, wherein the safety message includes a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment notification message (DENM). [C21] The method of C16 wherein the certificate information includes a complete certificate. [C22] The method according to C16, wherein the C-V2X message from the other wireless communication device includes a beacon message, a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment notification message (DENM). [C23] The C-V2X message from the other wireless communication device includes second route history information of the other wireless communication device, and the method The wireless communication device determines the trajectory of the other wireless communication device, The wireless communication device determines 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, The method according to C16, further comprising: the wireless communication device deciding to include the certificate information in the security message based on the range estimate or the TTC estimate. [C24] A device, At least one transceiver, Memory and The system comprises at least one transceiver and at least one processor coupled to the memory, wherein the at least one processor is The transceiver receives a cellular vehicle-to-everything (C-V2X) message from a wireless communication device via at least one of the transceivers. A device configured to send a security message containing certificate information via at least one transceiver in response to determining that a certificate information trigger condition has been met based on the aforementioned C-V2X message. [C25] The C-V2X message includes a temporary ID, and at least one processor determines, based on a local dynamic map (LDM), whether the temporary ID corresponds to a new or unknown device. Determine whether the range or time to collision (TTC) associated with the new or unknown device satisfies the range condition, the TTC condition, or both. The apparatus according to C24, further configured to determine whether to include the certificate information in the security message based on whether the temporary ID is associated with the new or unknown device and whether the new or unknown device satisfies the range condition, the TTC condition, or both. [C26] The certificate information trigger condition is a channel quality indicator (CQI) trigger condition, and the at least one processor is Determine the CQI of the aforementioned device, The aforementioned CQI is compared with the CQI threshold, It is determined whether the CQI trigger condition is met because the CQI is below the CQI threshold. The apparatus according to C24, further configured to determine that the CQI trigger condition is met because the CQI is below the CQI threshold, and to decide to include the certificate information in the security message. [C27] The certificate information trigger condition is a certificate change condition, and the at least one processor Determine the certificate inclusion frequency for a base frequency greater than 450 milliseconds for including the certificate information after the certificate change. A timer is set based on the certificate inclusion frequency. The apparatus according to C24, further configured to determine whether to include the certificate information in the safety message based on the expiration of the timer. [C28] The device according to C27, wherein the certificate inclusion frequency is 2 seconds or more. [C29] The at least one processor, Determine critical events, including acceleration events, deceleration events, direction change events, and safety system activations. The apparatus according to C24, further configured to decide to include the certificate information in the safety message based on the detection of the critical event. [C30] The apparatus described in C24, wherein the apparatus is operating in an International Association of Automotive Engineers (SAE) or European Telecommunications Standards Institute (ETSI) Intelligent Transport System (ITS) mode.

Claims

1. A method of wireless communication, A wireless communication device receives cellular vehicle-to-everything (C-V2X) messages from other wireless communication devices, The wireless communication device determines whether the route history information trigger condition is met based on the C-V2X message, The wireless communication device transmits a safety message, wherein the safety message includes route history information in response to a determination that the route history information trigger condition is met, and does not include route history information in response to a determination that the route history information trigger condition is not met, and the route history information trigger condition includes a collision zone condition, a channel quality condition, a new vehicle condition, or a combination thereof. Methods that include...

2. When the distance condition and / or time to collision (TTC) condition is met, the collision zone condition is met, When the Channel Quality Indicator (CQI) exceeds the threshold, the channel quality condition is met. The method according to claim 1, wherein the new vehicle condition is met when a new vehicle enters the collision zone of the wireless communication device.

3. The method according to claim 1, wherein the safety message includes a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment notification message (DENM).

4. The method according to claim 1, wherein the route history information includes a plurality of previous locations of the wireless communication device.

5. The method according to claim 1, wherein the C-V2X message from the other wireless communication device includes a beacon message, a basic safety message (BSM), a cooperative recognition message (CAM), or a distributed environment 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, and the method The wireless communication device determines the trajectory of the other wireless communication device, The wireless communication device determines 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, The method according to claim 1, further comprising the wireless communication device determining, based on the range estimate or the TTC estimate, whether to include the route history information in the safety message.

7. The method according to claim 1, further comprising determining the number of safety messages that include the route history information based on the determination by the wireless communication device that the route history information trigger condition has been met.

8. A non-temporary computer-readable medium on which program code is recorded that causes the wireless communication device to perform the operation described in any one of claims 1 to 7 when executed by the wireless communication device.

9. It is a device, At least one transceiver, Memory and The system comprises at least one transceiver and at least one processor coupled to the memory, wherein the at least one processor is The at least one transceiver receives a cellular vehicle-to-everything (C-V2X) message from a wireless communication device, Based on the C-V2X message, it is determined whether the route history information trigger condition is met, A safety message is transmitted via at least one of the transceivers, wherein the safety message includes route history information in response to a determination that the route history information trigger condition is met, and does not include route history information in response to a determination that the route history information trigger condition is not met, and the route history information trigger condition includes a collision zone condition, a channel quality condition, a new vehicle condition, or a combination thereof. A device configured to perform the following actions.

10. The C-V2X message includes a temporary ID, and the at least one processor, Based on the Local Dynamic Map (LDM), it is determined whether the temporary ID corresponds to a new or unknown device. The apparatus according to claim 9, further configured to determine whether to include the route history information in the security message based on whether the temporary ID is associated with a new or unknown device.

11. In order to determine whether the temporary ID corresponds to the new or unknown device based on the LDM, the at least one processor, The temporary ID is compared with the temporary ID stored in the LDM. The predicted trajectory of the wireless communication device is compared with the predicted trajectory stored in the LDM. The apparatus according to claim 10, configured to determine that the wireless communication device is a new or unknown device if the temporary ID or predicted trajectory does not match the stored temporary ID or predicted trajectory of the LDM.

12. The aforementioned at least one processor, Based on the C-V2X message, the estimated range for the wireless communication device is determined. Based on the C-V2X message, an estimated time to collision (TTC) is determined. Compare the estimated range with the range conditions, The TTC estimate is compared with the TTC conditions, The apparatus according to claim 9, further configured to determine whether to include the route history information in the safety message based on whether the range estimate is less than the range condition, whether the TTC estimate is less than the TTC condition, or both.

13. The route history information trigger condition is a channel quality indicator (CQI) trigger condition, and the at least one processor is Determine the CQI of the aforementioned device, The CQI is compared with the CQI threshold, The apparatus according to claim 9, further configured to determine that the CQI trigger condition is met if the CQI is less than or equal to the CQI threshold.

14. The apparatus according to claim 9, wherein the apparatus includes user equipment (UE).

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

Images