Managing transmission of improper behavior reports
By dynamically managing the sending of improper behavior reports in V2X systems, the redundant reporting problem is solved, resource use is optimized, and critical information is communicated in a timely manner.
Patent Information
- Application Number
- CN202380032120.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-15
- Filing Date
- 2023-02-21
- Publication Date
- 2024-11-15
AI Technical Summary
In a network of vehicles (V2X) systems, when multiple V2X systems detect and transmit inaccurate or intentionally false information reports, it causes the management agency (MA) to receive redundant reports, consume communication network resources and processing capabilities, and may lead to critical information Ignored or not reported.
By executing methods of managing misbehavior reports in the processor of the V2X system, priority or send probability is dynamically generated and assigned, based on detected V2X misbehavior types, expected responses, number of adjacent vehicles, and other external conditions, optimized Send reports to reduce redundancy and low critical reports.
It effectively reduces the transmission of redundant reports, improves the transmission rate of key information, optimizes the use of communication and processing capabilities, and ensures the timely communication of important information about traffic safety.
Smart Images

Figure CN118975284A_ABST
Abstract
Description
[0001] Related Applications
[0002] This application claims the benefit of priority to U.S. non-provisional application No. 17 / 659,359, filed on April 15, 2022; the entire contents of which are incorporated herein by reference. Background Art
[0003] Vehicle-to-everything (V2X) systems may employ protocols and messaging defined under relevant standards, such as Cellular Vehicle-to-everything (C-V2X), Dedicated Short Range Communications (DSRC), and ITS-G5. These standards are the foundation for vehicle-based wireless communications and may be used to support smart highways, autonomous and semi-autonomous vehicles, and improve the overall efficiency and safety of highway transportation systems. An element of a V2X system is the ability for vehicles to broadcast V2X messages that other vehicles can receive and process to improve traffic safety, such as Basic Safety Messages (BSM) or Collaborative Awareness Messages (CAM).
[0004] The V2X system may be configured to detect inaccurate or intentionally false information in a V2X message received from another vehicle or from an Intelligent Transportation System (ITS) infrastructure device, such as a roadside unit (RSU). In addition, the V2X system may be configured to transmit a report of the detected inaccurate or intentionally false information to a misconduct authority (MA) computing device. However, if many V2X systems each detect and transmit reports about such inaccurate or intentionally false information, the MA computing device may receive many redundant reports, thereby potentially overloading the MA computing device. In addition, the transmission of redundant reports may also consume limited communication network resources and processing power of the V2X system and the MA computing device. Summary of the invention
[0005] Various aspects include methods executable by a processor of a vehicle-to-everything (V2X) system for managing the sending of misbehavior reports. Various aspects may include: generating a misbehavior report based on detected V2X misbehavior; assigning a priority or sending probability to the generated misbehavior report based on external conditions related to the detected V2X misbehavior; and sending the misbehavior report based on the assigned priority or sending probability.
[0006] In some aspects, assigning a priority or a probability of sending to a generated misbehavior report based on an external condition related to the detected V2X misbehavior may include: determining an event type of the detected V2X misbehavior for the misbehavior report, and determining a context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior; and assigning a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior. In such aspects, sending the misbehavior report based on the assigned priority may include sending the misbehavior report based on the assigned criticality value.
[0007] In some aspects, determining the context of the detected V2X misbehavior based on the expected response to the detected V2X misbehavior may include determining the context based on the degree to which the expected response of the vehicle to the detected V2X misbehavior will deviate from the current behavior of the vehicle. In some aspects, determining the context of the detected V2X misbehavior based on the expected response to the detected V2X misbehavior may include determining the expected response of one or more neighboring vehicles to the detected V2X misbehavior. In some aspects, determining the context of the detected V2X misbehavior based on the expected response to the detected V2X misbehavior may include determining the degree to which the detected V2X misbehavior deviates from the ground truth determined by the processor of the V2X system.
[0008] In some aspects, sending the misbehavior report based on the assigned criticality value may include using the assigned criticality value as a weighting factor along with other factors used to determine whether to send the misbehavior report. In some aspects, assigning a priority or a probability of sending to the generated misbehavior report based on external conditions related to the detected V2X misbehavior may include: determining a number of V2X-enabled neighboring vehicles; determining a weighting factor based on the number of V2X-enabled neighboring vehicles; and adjusting the probability of sending using the weighting factor. In such aspects, sending the misbehavior report based on the assigned priority or probability of sending may include sending the misbehavior report based on the adjusted probability of sending.
[0009] Some aspects may include: determining whether the number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles; in response to determining that the number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles, determining the distance between the location associated with the detected V2X misbehavior and the location of each of the neighboring vehicles and the distance between the location associated with the detected V2X misbehavior and the vehicle; determining the number of vehicles closest to the location associated with the detected V2X misbehavior; in response to determining that the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior, taking action to increase the probability that the processor will transmit a misbehavior report; and in response to determining that the vehicle is not among the number of vehicles closest to the location associated with the detected V2X misbehavior, taking action to reduce the probability that the processor will transmit a misbehavior report. In some aspects, assigning a priority or sending probability to a generated misbehavior report based on external conditions related to detected V2X misbehavior may include: receiving a misbehavior reporting policy from a network computing device, the misbehavior reporting policy including parameters that can be used by a processor to determine whether to transmit a misbehavior report; and assigning a priority or sending probability to the generated misbehavior report based on the parameters of the misbehavior reporting policy.
[0010] In some aspects, the misconduct reporting policy parameters may include a time window, and assigning a priority or a probability of transmission to the generated misconduct report based on the parameters of the misconduct reporting policy may include: in response to determining that the misconduct report was generated during the time window, taking action to increase the probability that the processor will transmit the misconduct report. In some aspects, the misconduct reporting policy parameters may include an indication to increase the probability that the processor will transmit the misconduct report, and assigning a priority or a probability of transmission to the generated misconduct report based on the parameters of the misconduct reporting policy may include: in response to the indication in the misconduct reporting policy parameters, taking action to adjust the probability that the processor will transmit the misconduct report. In some aspects, the misconduct reporting policy parameters may include a threshold number of misconduct reports associated with the same V2X transmitter, and assigning a priority or a probability of transmission to the generated misconduct report based on the parameters of the misconduct reporting policy may include: in response to determining that the number of V2X reports generated by the processor associated with the same V2X transmitter meets the threshold included in the misconduct reporting policy parameters, transmitting the misconduct report.
[0011] Additional aspects include a vehicle processing system including a memory and a processor configured to perform operations of any of the methods outlined above. Additional aspects may include a vehicle processing system having various components for performing functions corresponding to any of the methods outlined above. Additional aspects may include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause a processor of the vehicle processing system to perform various operations corresponding to any of the methods outlined above. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the claims and, together with the general description and detailed description given, serve to explain the features herein.
[0013] Figure 1A is a system block diagram illustrating an example communication system suitable for implementing various embodiments.
[0014] Figure 1B is a system block diagram illustrating an example decomposed base station architecture suitable for implementing any of the various embodiments.
[0015] Figure 1C is a system block diagram illustrating a communication system suitable for implementing various embodiments.
[0016] Figure 2A is a component diagram of an example vehicle V2X system suitable for implementing various embodiments.
[0017] Figure 2B is a component block diagram illustrating components of an example vehicle V2X system suitable for implementing various embodiments.
[0018] Figure 3A is a block diagram illustrating components of a system-on-chip for use in a vehicle V2X processing system according to various embodiments.
[0019] Figure 3B is a component block diagram illustrating elements of a vehicle V2X system configured in accordance with various embodiments.
[0020] Figure 4A is a process flow diagram of an example method performed by a processor of a vehicle V2X system for managing the transmission of misbehavior reports according to various embodiments.
[0021] FIG. 4B to FIG. 4Eis a process flow diagram of example operations that may be performed by a processor of a vehicle V2X system as part of a method for managing the transmission of misbehavior reports in accordance with various embodiments.
[0022] Figure 5 is a component block diagram of a computing device suitable for use with various embodiments. DETAILED DESCRIPTION
[0023] Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.
[0024] Various embodiments include methods and processors for a vehicle V2X system for managing the transmission of misbehavior reports to reduce the transmission of low-criticality and / or redundant misbehavior reports by several vehicles without actively coordinating such transmissions (e.g., without a transmission coordinator or controller). The transmission of redundant and low-criticality misbehavior reports may overwhelm the system bandwidth available for sending misbehavior reports (particularly in traffic conditions), which may cause some misbehavior reports to never be sent. However, an active control system deployed across all or most vehicles will require additional bandwidth for control signals. In various embodiments, the V2X system may generate misbehavior reports based on detected V2X misbehavior, dynamically assign a priority or criticality to the generated misbehavior report based on external conditions related to the detected V2X misbehavior, and send the misbehavior report based on the assigned priority or criticality in a manner that reduces the incidence of redundant misbehavior report transmissions when deployed in many other vehicles. In some embodiments, the V2X system may assign a priority to the misbehavior report for transmission, such as based on the type or the determined criticality value, and then transmit the misbehavior report from the queue in priority order, wherein misbehavior reports exceeding a threshold age are discarded before transmission. In some embodiments, the V2X system may assign a transmission probability to the misbehavior report, such as based on the type of misbehavior or the determined criticality value, and then use the probability to determine whether the misbehavior report is transmitted during each transmission opportunity for the misbehavior report. In some embodiments, the assigned probability may be used in conjunction with a random or semi-random process (e.g., a random number generator, a random dice, or other semi-random process) to make a transmission decision, such as comparing the probability with a random number or multiplying the assigned probability by a random value and comparing the product with a threshold. When such an embodiment is implemented in most or all vehicles, the resulting transmission rate of reports of a given misbehavior detected by many or all nearby vehicles can be limited without additional overhead communications or a central controller.
[0025] As used herein, the term "vehicle" generally refers to any of a car, motorcycle, truck, bus, train, boat, and any other type of vehicle V2X-enabled system that may be configured to manage the transmission of misbehavior reports.
[0026] The term "system on a chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that contains multiple resources and / or processors integrated on a single substrate. A single SOC may contain circuits for digital, analog, mixed-signal, and radio frequency functions. A single SOC may also include any number of general-purpose and / or special-purpose processors (digital signal processors, modem processors, video processors, etc.), storage blocks (e.g., ROM, RAM, flash memory, etc.), and resources (e.g., timers, voltage regulators, oscillators, etc.). The SOC may also include software for controlling the integrated resources and processors and for controlling peripheral devices.
[0027] The term "system-in-package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computing units, cores and / or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SOCs that are connected together via high-speed communication circuits and packaged in close proximity, such as on a single motherboard or in a single wireless device. The proximity of the SOCs facilitates high-speed communication and the sharing of memory and resources.
[0028] Technologies and technical standards are being developed in many regions around the world to support evolving future highway systems and vehicles, including the development of standards to enable safe autonomous and semi-autonomous vehicle operations. Such technologies include standardizing vehicle-based communication systems and functions, and developing standards for vehicle automated driving systems (ADS), advanced driver assistance systems (ADAS), etc., generally referred to in this article as "V2X systems."
[0029] Technologies and standards supporting autonomous driving and semi-autonomous driving include communication technologies and networks for intelligent highway systems (ITS). Examples include standards developed by the Institute of Electrical and Electronics Engineers (IEEE) and the Society of Automotive Engineers (SAE) for North America, or standards developed by the European Telecommunications Standards Institute (ETSI) and the European Committee for Standardization (CEN) for Europe. For example, the IEEE 802.11p standard is the basis for dedicated short-range communication (DSRC) and ITS-G5 communication standards. IEEE 1609 is a higher-layer standard based on IEEE 802.11p. The cellular vehicle-to-everything (C-V2X) standard is a competitive standard developed under the support of the Third Generation Partnership Project. These standards are based on the basis of wireless communications for vehicles, and can be used to support intelligent highways, autonomous driving and semi-autonomous driving vehicles, and improve the overall efficiency and safety of highway transportation systems. ITS communications can be supported by the next generation 5G NR communication system. These and other V2X wireless technologies can be used to download map data in various implementations.
[0030] The C-V2X protocol defines two transmission modes, which together provide 360° non-line-of-sight awareness and a higher level of predictability for enhanced road safety and autonomous driving. The first transmission mode includes direct C-V2X, which includes vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) and vehicle-to-pedestrian (V2P), and provides enhanced communication range and reliability in the dedicated intelligent transportation system (ITS) 5.9 gigahertz (GHz) spectrum independent of the cellular network. The second transmission mode includes vehicle-to-network communication (V2N) in mobile broadband systems and technologies (such as third-generation wireless mobile communication technology (3G) (e.g., Global System for Mobile Communications (GSM) Evolution (EDGE) system, Code Division Multiple Access (CDMA) 2000 system, etc.), fourth-generation wireless mobile communication technology (4G) (e.g., Long Term Evolution (LTE) system, Advanced LTE system, Mobile Global Microwave Interoperability Access (Mobile WiMAX) system, etc.), fifth-generation new radio wireless mobile communication technology (5G NR system, etc.), etc.).
[0031] The V2X system may be configured to detect inaccurate or intentionally false information in a V2X message received from another vehicle or from an intelligent transportation system (ITS) infrastructure device (such as a roadside unit (RSU)). Such inaccurate or intentionally false information in a V2X message may be referred to as "V2X misbehavior". The V2X system may be configured to generate a report (such as a misbehavior report) of such detected inaccurate or intentionally false information and transmit it to a misbehavior management agency network computing device (such as a server). (For the sake of simplicity, the misbehavior management agency server and other network computing devices are referred to as "MA" herein). However, V2X system operations are constrained by limited communication resources (such as signal bandwidth, transmission opportunities, reception opportunities, etc.) and computing resources (such as computing resources, data storage capacity, etc.). In addition, if many V2X systems each detect and transmit reports on such inaccurate or intentionally false information, the MA may receive many redundant reports, thereby unnecessarily consuming MA resources and communication resources. Some conventional V2X systems are configured to statically assign priorities to misbehavior reports, for example, by assigning a certain priority to all misbehavior reports of a particular type of V2X misbehavior. This results in all misbehavior reports of a certain V2X misbehavior type being prioritized equally. Furthermore, each conventional V2X system will transmit a misbehavior report to the MA regardless of whether other V2X systems are also transmitting the same misbehavior report. In this case, V2X misbehaviors will be reported to the MA in roughly proportion to the number of V2X systems that observed the V2X misbehavior, creating the risk that more observed V2X misbehaviors may be over-reported, while less observed V2X misbehaviors may be ignored or not reported at all, regardless of how dangerous or disruptive these less observed V2X behaviors may be.
[0032] Various embodiments overcome such limitations by dynamically generating priorities for misbehavior reports based on conditions external to a vehicle (i.e., a vehicle equipped with a V2X system that observes V2X misbehavior) to manage the transmission of misbehavior reports. In some embodiments, the V2X system may be configured to generate misbehavior reports based on detected V2X misbehavior, assign priorities to the generated misbehavior reports based on external conditions related to the detected V2X misbehavior, and transmit the misbehavior reports based on the assigned priorities. For example, the V2X system may transmit misbehavior reports (i.e., misbehavior reports that have been generated, prioritized, and stored in a transmit buffer) in the order of the assigned priorities, wherein the highest priority misbehavior report stored in the buffer is transmitted at each transmission opportunity. Since misbehavior reports may be frequently generated, prioritized, and stored in a buffer, and the V2X transmission window may be limited (e.g., in heavy traffic conditions), only those misbehavior reports that are assigned a high priority may be transmitted, and the probability of low priority misbehavior reports being transmitted before they become too old to be transmitted may be low. In this way, the V2X system can use the priority value assigned to the misbehavior report to increase the probability that a critical misbehavior report will be sent to the MA when operating in limited bandwidth or congested V2X traffic conditions, while less critical or low priority misbehavior reports may or may not be sent, depending on the V2X communication conditions. In some embodiments, the V2X system may also assign a timestamp, an age value, a lifetime value, or another suitable value to the misbehavior report, and may reduce its priority as the misbehavior report ages. In some embodiments, the V2X system may discard misbehavior reports that meet a threshold age. Therefore, when the transmission opportunities for misbehavior reports are limited, low priority misbehavior reports may never be sent because such reports may be discarded before there is a transmission opportunity that would normally be allocated to higher priority misbehavior reports.
[0033] In some embodiments, the V2X system may determine an event type of the detected V2X misbehavior for the misbehavior report, and may determine a context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior. The V2X system may assign a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior, and may send the misbehavior report to the MA based on the assigned criticality value. For example, the V2X system may send a misbehavior report stored in a transmission buffer with a highest criticality value, which is sent at each transmission opportunity. As another example, the V2X system may send a misbehavior report stored in a transmission buffer with a criticality value that meets a transmission threshold. As another example, the V2X system may assign a transmission probability to the misbehavior report based on the criticality value, wherein the probability is used in conjunction with a random or semi-random process for determining whether to send a misbehavior report at any given transmission opportunity, as described herein.
[0034] In some embodiments, the context of the detected V2X misbehavior may be based on an expected response to the detected V2X misbehavior, the expected response including a possible or expected level of disturbance to the behavior of the vehicle or to the traffic around the vehicle. In some embodiments, the expected response may include an action that the processor may take or may instruct the vehicle to take in response to the detected V2X misbehavior. In this way, the processor may dynamically determine the severity of the V2X misbehavior based on one or more conditions external to the vehicle. For example, a V2X message with V2X misbehavior may include incorrect positioning information about the transmitting vehicle, such as an indication that the transmitting vehicle is within a minimum safe distance or a threshold distance of the vehicle. As another example, the V2X misbehavior may indicate incorrect kinematic information about the transmitting vehicle (e.g., related to the speed, movement, maneuvering, etc. of the transmitting vehicle), which is indicated as occurring within a minimum safe distance or a threshold distance of the vehicle.
[0035] In some embodiments, the V2X system of the vehicle may determine an expected response of the vehicle in response to information in the V2X message. For example, the expected response of the vehicle may include gently braking the vehicle. As another example, the expected response of the vehicle may include a heavy application of the vehicle's brakes, such as emergency braking or panic braking. As another example, the expected response of the vehicle may include a gradual lane change. As another example, the expected response of the vehicle may include steering away from a condition indicated by the V2X misbehavior (i.e., a rapid maneuver).
[0036] In some embodiments, the V2X system may determine an expected response to the detected V2X misbehavior by one or more neighboring vehicles, such as traffic surrounding the vehicle (e.g., other vehicles within a threshold distance from the vehicle or within a threshold distance from a location associated with the V2X misbehavior).
[0037] In some embodiments, the V2X system may assign a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior. For example, the V2X system may determine that the V2X misbehavior includes incorrect positioning information within the minimum safety distance of the vehicle, and the V2X system may assign a criticality value of "1" to the relevant misbehavior report. As another or example, the V2X system may determine that the V2X misbehavior includes incorrect positioning information outside the minimum safety distance of the vehicle, and the V2X system may assign a criticality value of "2" to the relevant misbehavior report. As another example, the V2X system may determine that the V2X misbehavior includes incorrect kinematic information within the minimum safety distance of the vehicle, and the V2X system may assign a criticality value of "1" to the relevant misbehavior report. As another example, the V2X system may determine that the V2X misbehavior includes incorrect kinematic information outside the minimum safety distance of the vehicle, and the V2X system may assign a criticality value of "2" to the relevant misbehavior report. As another example, the V2X system may determine that the V2X misbehavior includes incorrect dimension information or incorrect intelligent transportation system station (ITS-S) type information about the transmitting vehicle, and the V2X system may assign a criticality value of "3" to the relevant misbehavior report. Other examples are also possible. In such embodiments, the V2X system may send a misbehavior report to the MA based on the assigned criticality value, such as first transmitting a misbehavior report with a criticality value of "1", then transmitting a misbehavior report with a criticality value of "2", and so on. In some embodiments, the V2X system may assign a transmission probability to the misbehavior report based on the assigned criticality value, wherein the probability is used in conjunction with a random or semi-random process for determining whether to send a misbehavior report at any given transmission opportunity, as described herein. For example, the V2X system may determine whether the probability of sending a misbehavior report meets the transmission criteria based on the generated random value, such as whether the probability is greater than or equal to the generated random value. As another example, the V2X system may multiply the probability by the random value and compare the product with a threshold value. In response to determining that the product of the probability of sending the misbehavior report multiplied by the generated random value exceeds a threshold, the V2X system may send the misbehavior report.
[0038] In some embodiments, the V2X system may determine the context based on the extent to which the vehicle's expected response to the detected V2X misbehavior will deviate from the vehicle's current behavior, and assign a criticality value based at least in part on the extent to which the vehicle's expected response to the detected V2X misbehavior will deviate from the vehicle's current behavior. For example, if the content of the received V2X is not determined to be invalid (i.e., there is no misbehavior), the greater the deviation from the vehicle's current speed and path that the vehicle will have to initiate, the greater the criticality value that will be attributed to the misbehavior report. In some embodiments, the V2X system may determine the context based on the expected level of disturbance to the vehicle's behavior and / or to the behavior of nearby traffic that the detected V2X misbehavior may cause. For example, as described above, the expected response of the vehicle or surrounding vehicles may include gently braking the vehicle, or the expected response may include emergency braking or emergency braking. As another example, the expected response of the vehicle or surrounding vehicles may include gradually changing lanes, or the expected response may include steering away from the condition indicated by the V2X misbehavior.
[0039] In some embodiments, the V2X system may determine the context of the detected V2X misbehavior based on the degree to which the detected V2X misbehavior deviates from the ground truth determined by the processor of the V2X system. In some embodiments, the V2X system may receive information about the V2X transmitter from various sensors of the vehicle, and using such information, the V2X system may determine the speed, location, movement, manipulation, etc. of the V2X transmitter. In some embodiments, the V2X system may receive information about the V2X transmitter from another vehicle or multiple vehicles (such as a trusted third-party vehicle) or from an ITS infrastructure device (such as a roadside unit). In some embodiments, the V2X system is able to use its own sensor information and information received from other vehicles or ITS infrastructure devices in any combination. In some embodiments, based on the degree to which the detected V2X misbehavior deviates from the ground truth determined by the processor of the V2X system, the V2X system may assign a larger criticality value (for a wider deviation) or a smaller criticality value (for a smaller deviation) to the misbehavior report.
[0040] In some embodiments, the V2X system may use the assigned criticality value as a weighting factor or transmission probability for determining whether to send a misbehavior report. For example, the V2X system may determine the probability that the V2X system will send or should send a misbehavior report. In some embodiments, when the assigned criticality value indicates that the V2X misbehavior may have a direct or close-range impact on the safety of the vehicle (e.g., the V2X misbehavior includes incorrect positioning information within the minimum safe distance of the vehicle), the V2X system may increase the probability that the V2X system will send a misbehavior report. As another example, when the assigned criticality value indicates that the V2X misbehavior is far away from the vehicle in time or space and does not pose a direct or close-range threat to the safety of the vehicle, the V2X system may reduce or increase the probability that the V2X system will send a misbehavior report by a smaller margin. For example, in a case where the criticality value is based on a V2X message that incorrectly indicates that the second vehicle is braking, but the positioning of the second vehicle is outside the safe distance of the vehicle to respond to such misbehavior, the V2X system may reduce or increase the probability of sending the associated misbehavior report by a smaller margin. In some embodiments, the V2X system may determine a probability of sending a misbehavior report based on the assigned criticality value and one or more other factors, and may send the misbehavior report based on the determined probability of sending.
[0041] In some embodiments, the determined transmission probability (or criticality value or other similar value) assigned to a given misconduct report may be used in conjunction with a random or semi-random process to determine whether to send a misconduct report at a given misconduct report transmission opportunity. When most or all vehicles in a particular location use the same distribution transmission probability process and the same random or semi-random process to decide whether to send a misconduct report, the transmission of redundant misconduct reports by multiple vehicles may be limited without actively coordinating such transmissions (e.g., without the need to send a coordinator or controller). In some embodiments, the V2X system may generate a random value (e.g., via a random number generator, a digital dice, or other random process), and use the generated random value in conjunction with the probability to determine whether to send a misconduct report. For example, the V2X system may determine whether the probability of sending a misconduct report meets the transmission criteria based on the generated random value, such as whether the probability is greater than or equal to the generated random value. As another example, the V2X system may multiply the probability by the random value and compare the product with a threshold. In response to determining that the product of the probability of sending a misbehavior report multiplied by the generated random value exceeds a threshold, the V2X system may send a misbehavior report. In some embodiments, this operation may be performed at each misbehavior transmission opportunity and applied to all misbehavior reports in the queue for transmission to identify one of the queued misbehavior reports to be transmitted.
[0042] In some embodiments, the V2X system may adjust the probability that a vehicle will send a generated misbehavior report based on external conditions, such as whether other nearby vehicles are likely to also send misbehavior reports regarding detected V2X misbehavior. In some embodiments, the V2X system may determine the number of neighboring vehicles (e.g., the number of vehicles within a threshold distance of the vehicle, or the number of vehicles within a threshold distance of detected V2X misbehavior) that are capable of generating and sending V2X misbehavior reports ("V2X-enabled neighboring vehicles"). In such embodiments, the V2X system may determine a weighting factor based on the number of V2X-enabled neighboring vehicles, and may use the weighting factor to adjust the transmission probability assigned to the misbehavior report. For example, the V2X system may detect or identify n V2X-enabled vehicles. The V2X system may determine a weighting factor based on the number n of V2X-enabled vehicles. In some embodiments, the weighting factor may be expressed as Where f(n) represents a weighting factor, n represents the number of neighboring V2X-enabled vehicles, c represents a constant (e.g., 10) that adjusts the weighting factor based on the number of reporting vehicles n, and e represents a constant (e.g., Euler's number). In some embodiments, the V2X system may use the weighting factor to take action (e.g., perform a mathematical operation such as a multiplication) to adjust the probability that the processor will send a misbehavior report. In this way, the V2X system may adjust the probability that the processor will send a misbehavior report based on the number of neighboring V2X-enabled vehicles. When this is implemented in all surrounding vehicles, the embodiment may have the effect of reducing, on average, the total number of misbehavior reports sent to the MAs of the surrounding vehicles regarding the same V2X misbehavior or triggered by the same V2X misbehavior.
[0043] In some embodiments, the V2X system may send a misbehavior report based on an adjusted probability that the V2X system will report the detected V2X misbehavior (i.e., the probability that the V2X system will send a misbehavior report). In some embodiments, if the V2X system determines that other nearby vehicles may send misbehavior reports under the same conditions, the V2X system may assign a low priority to misbehavior reports generated in response to the same conditions, thereby reducing the probability that the V2X system will send redundant misbehavior reports. In some embodiments, the V2X system may assign a low transmission probability to misbehavior reports generated in response to detected conditions or events, and use a random process to decide whether to send the misbehavior report at a given transmission opportunity. For example, the V2X system may determine whether the probability of sending a misbehavior report meets the transmission criteria based on the generated random value, such as whether the probability is greater than or equal to the generated random value, and send the misbehavior report in response to determining that the transmission criteria are met. As another example, the V2X system may multiply the probability by a random value and compare the product to a threshold, and send a misbehavior report in response to determining that the product of the probability of sending the misbehavior report multiplied by the generated random value exceeds the threshold.
[0044] In some embodiments, the V2X system may determine whether to transmit a misbehavior report based on whether the vehicle is in a group of vehicles closest to the V2X transmitter. In some embodiments, the V2X system may determine whether the number of neighboring vehicles within a threshold distance of the vehicle exceeds a threshold number of vehicles. In some embodiments, the threshold number of vehicles may represent the maximum number of repeated or redundant misbehavior reports that should be transmitted to the MA. In this way, the V2X system may determine whether there are a threshold number of other vehicles that can also transmit misbehavior reports about V2X misbehavior. In response to determining that the number of neighboring vehicles adjacent to the vehicle exceeds the threshold number of vehicles, the V2X system may determine the distance between the position associated with the detected V2X misbehavior (e.g., the claimed position of the V2X transmitter) and the position of each of the neighboring vehicles. The V2X system may also determine the distance between the position associated with the detected V2X misbehavior and the vehicle.
[0045] The V2X system may determine the number of vehicles closest to the location associated with the detected V2X misbehavior (such as within a threshold distance). In some embodiments, the number of vehicles may be a predetermined value (e.g., 10 vehicles). In some embodiments, the V2X system may use a threshold number of vehicles (i.e., a determination based on whether the number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles) to assign a priority to the generated misbehavior report. The V2X system may determine whether the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior. In response to determining that the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior, the V2X system may take action to increase the probability that the V2X system will transmit the misbehavior report. For example, if the V2X system can assign a high priority to the associated misbehavior report, the probability that the V2X system will send the misbehavior report is thereby increased. In response to determining that the vehicle is not among the number of vehicles closest to the location associated with the detected V2X misbehavior, the V2X system may take action to reduce the probability that the V2X system will transmit a misbehavior report. For example, if the V2X system may assign a low priority to the associated misbehavior report, thereby reducing the probability that the V2X system will send a redundant misbehavior report. The V2X system may send its own misbehavior report based on the adjusted (increased or decreased) probability.
[0046] In some embodiments, the V2X system may generate a random value and use the generated random value and the probability of the V2X system deciding whether to send a misbehavior report in a given transmission opportunity. For example, in response to determining that the probability of sending a misbehavior report meets a transmission criterion based on the generated random value (e.g., whether the probability is greater than or equal to the generated random value), the V2X system may send the misbehavior report. As another example, in response to determining that the product of the probability of sending a misbehavior report multiplied by the generated random value meets a threshold (e.g., is greater than or equal to the generated random value), the V2X system may send the misbehavior report.
[0047] In some embodiments, the V2X system may receive a misbehavior reporting policy from a network computing device (e.g., a MA), and may apply one or more parameters from the misbehavior reporting policy to determine whether to send a misbehavior report. In some embodiments, the V2X system may assign a priority to the generated misbehavior report based on external conditions of the parameters from the misbehavior reporting policy. In some embodiments, the misbehavior reporting policy parameters may include a time window, and the V2X system may take action to increase the priority of the misbehavior report or increase the probability that the processor will transmit the misbehavior report in response to determining that a misbehavior report was generated during the time window.
[0048] In some embodiments, the misbehavior reporting policy may indicate a request from the MA to receive a report of a specific V2X misbehavior or a specific type of V2X misbehavior, regardless of whether the MA receives multiple redundant misbehavior reports. In some embodiments, the misbehavior reporting policy parameters may include an indication to increase the priority of the misbehavior report or to increase the probability that the processor will transmit the misbehavior report, and the V2X system may take action to increase the priority of the misbehavior report or to increase the probability that the processor will transmit the misbehavior report in response to the indication in the misbehavior reporting policy parameters.
[0049] In some embodiments, the misbehavior reporting policy parameters may include a threshold number of misbehavior reports associated with the same V2X transmitter, and the V2X system may transmit the misbehavior report in response to determining that the number of V2X reports generated by the processor associated with the same V2X transmitter satisfies the threshold included in the misbehavior reporting policy parameters. For example, the misbehavior reporting policy may indicate a request from the MA to receive a report of V2X misbehavior of the same vehicle (the same V2X transmitter), which may indicate multiple occurrences of V2X misbehavior from the same V2X transmitter (which may identify the V2X transmitter as a malicious actor).
[0050] In various embodiments, the misbehavior reporting policy may include various parameters, including the types of V2X misbehavior that the MA is particularly interested in. In some embodiments, the MA may send the misbehavior reporting policy to the V2X system (e.g., the MA may "push" the misbehavior reporting policy). In some embodiments, the MA may send the misbehavior reporting policy to the V2X system in response to a request from the V2X system (e.g., the V2X system may "pull" the misbehavior reporting policy from the MA).
[0051] Various embodiments may improve the operation of a V2X system by enabling the V2X system to dynamically prioritize misbehavior reports based on external conditions associated with detected V2X misbehavior. Various embodiments may increase the efficiency of or improve the operation of a V2X system and V2X network by reducing redundant reports of V2X misbehavior and by dynamically prioritizing reports of more critical V2X misbehavior, thereby more efficiently using limited computing power and computing resources.
[0052] Figure 1A1 is a system block diagram illustrating an example communication system 100 suitable for implementing various embodiments. The communication system 100 includes a 5G New Radio (NR) network, an ITS V2X wireless network, and / or any other suitable network, such as a Long Term Evolution (LTE) network. References to 5G networks and 5G network elements in the following description are for illustrative purposes and are not intended to be limiting.
[0053] The communication system 100 may include a heterogeneous network architecture including a core network 140, a plurality of base stations 110, and various mobile devices including a vehicle 102 equipped with a V2X system 104 including wireless communication capabilities. The base stations 110 may communicate with the core network 140 via a wired communication link 126. The communication system 100 may also include a roadside unit 112 that supports V2X communication with the vehicle 102 via the V2X wireless communication link 124.
[0054] The base station 110 is a network element that communicates with a wireless device (e.g., the V2X system 104 of the vehicle 102) via a wireless communication link 122, and may be referred to as a Node B, an LTE evolved Node B (eNodeB or eNB), an access point (AP), a radio head, a transmit receive point (TRP), a new radio base station (NR BS), a 5G Node B (NB), a next generation Node B (gNodeB or gNB), etc. Each base station 110 may provide communication coverage for a particular geographic area or "cell". In 3GPP, the term "cell" may refer to the coverage area of a base station, or a base station subsystem serving the coverage area, or a combination thereof, depending on the context in which the term is used. The core network 140 may be any type of core network, such as an LTE core network (e.g., an evolved packet core (EPC) network), a 5G core network, a reference Figure 1B The decomposed network, etc.
[0055] The roadside unit 112 may communicate with the core network 140 via a wired or wireless communication link 128. The roadside unit 112 may communicate with a vehicle 102 equipped with a V2X system via a V2X wireless communication link 124 for downloading information useful for the V2X system autonomous and semi-autonomous driving functions, and for receiving information such as misbehavior reports from the V2X system 104.
[0056] A misbehavior authority network computing device (MA) 132 may communicate with the core network 140 via a wired or wireless communication link 127. The MA 132 may receive misbehavior reports from the V2X system 104, as may be transmitted by the V2X system 104 from time to time.
[0057] The wireless communication link 122 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. The wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in the wireless communication links include: 3GPP LTE, 3G, 4G, 5G (e.g., NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile phone communication technology cellular RATs. Other examples of RATs that may be used in one or more of the various wireless communication links within the communication system 100 include medium-range protocols (such as Wi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire) and relatively short-range RATs (such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE)).
[0058] Figure 1B is a system block diagram illustrating an example decomposed base station 160 architecture that may be part of a V2X and / or 5G network suitable for communicating map data to vehicles and communicating updated object / feature location data in accordance with any of various embodiments. Figure 1A and Figure 1B , the decomposed base station 160 architecture may include one or more central units (CU) 162, which may communicate directly with the core network 180 via a backhaul link, or indirectly with the core network 180 through one or more decomposed base station units (such as a near real-time (Near-RT) RAN intelligent controller (RIC) 164 via an E2 link, or a non-real-time (Non-RT) RIC 168 associated with a service management and orchestration (SMO) framework 166, or both). The CU 162 may communicate with one or more distributed units (DU) 170 via corresponding midhaul links (such as an F1 interface). The DU 170 may communicate with one or more radio units (RU) 172 via corresponding fronthaul links. The RU 172 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a user equipment (UE) such as a V2X system 104 may be served by multiple RUs 172 simultaneously.
[0059] Each of the units (i.e., CU 162, DU 170, RU 172), as well as near-RT RIC 164, non-RT RIC 168, and SMO framework 166 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.
[0060] In some aspects, CU 162 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 162. CU 162 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 162 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 162 may be implemented to communicate with DU 170 for network control and signaling.
[0061] DU 170 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 172. In some aspects, DU 170 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional partitioning such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 170 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 170 or with control functions hosted by CU 162.
[0062] The lower layer functionality may be implemented by one or more RUs 172. In some deployments, the RUs 172 controlled by the DUs 170 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splits (such as lower layer functional splits). In such an architecture, the RUs 172 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RUs 172 may be controlled by the corresponding DUs 170. In some scenarios, this configuration may enable the DUs 170 and CUs 162 to be implemented in a cloud-based radio access network (RAN) architecture (such as a vRAN architecture).
[0063] The SMO framework 166 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 166 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 166 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 176) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 162, DU 170, RU 172, and near-RT RIC 164. In some specific implementations, the SMO framework 166 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 174) via the O1 interface. Additionally, in some specific implementations, the SMO framework 166 may communicate directly with one or more RUs 172 via the O1 interface. The SMO framework 166 may also include a non-RT RIC 168 configured to support the functionality of the SMO framework 166 .
[0064] The non-RT RIC 168 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 164. The non-RT RIC 168 may be coupled to or in communication with the near-RT RIC 164 (such as via an A1 interface). The near-RT RIC 164 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 162, one or more DUs 170, or both, and the O-eNB with the near-RT RIC 164.
[0065] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 164, the non-RT RIC 168 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 164 and may be received from a non-network data source or from a network function at the SMO framework 166 or the non-RT RIC 168. In some examples, the non-RT RIC 168 or the near-RT RIC 164 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 168 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 166 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).
[0066] Figure 1C is a system block diagram illustrating a communication system 103 suitable for implementing various embodiments. Figures 1A to 1C, the communication system 103 may include three vehicles 12, 14, 16. Each vehicle 12, 14, 16 may include a V2X system 104, 106, 108, respectively, each V2X system being configured to periodically broadcast V2X messages such as basic safety messages 30, 40, 50 for reception and processing by the V2X systems (e.g., 104, 106, 108) of other vehicles. By sharing vehicle position, speed, direction, braking, and other information, vehicles can maintain safe intervals and identify and avoid potential collisions. For example, a trailing vehicle 12 that receives a basic safety message 40 from a leading vehicle 16 can determine the speed and position of the vehicle 16, which in turn enables the vehicle 12 to match the speed and maintain a safe interval distance 20. By being notified by the basic safety message 40 when the leading vehicle 16 applies brakes, the V2X equipment 102 in the trailing vehicle 12 can also apply brakes simultaneously to maintain a safe interval distance 20 even when the leading vehicle 16 suddenly applies brakes. As another example, the V2X equipment 104 in the truck vehicle 14 can receive basic safety messages 30, 50 from two vehicles 12, 16, and thus be notified that the loaded vehicle 14 should stop at the intersection to avoid a collision. Each of the vehicle V2X airborne equipment 104, 106, 108 can communicate with each other using any of a variety of close proximity communication protocols. In addition, the vehicle may be able to send data and information about the detected basic safety messages and misbehavior reports about the detected V2X misbehavior to the original equipment manufacturer (OEM) (70, 72) and / or MA74 (e.g., 132) via the communication network 18 via communication links 60, 61, 62. The misbehavior report can be sent directly to the MA 74 (e.g., via communication links 64, 66). In other embodiments, the misbehavior report may first be sent to a misbehavior report preprocessing unit (such as an OEM server 70, 72) for preprocessing via communication links 64, 66. The pre-processed misconduct report may then be sent from the misconduct report pre-processing server 70, 72 to the MA 74 via the communication link 64, 66. In other embodiments, the misconduct report may be received at the MA 74 from a vehicle, such as from the vehicle 16. The MA 74 may relay the misconduct report received from the vehicle 16 to the OEM server 70, 72 via the communication link 64, 66. In addition, the OEM server 70, 72 may provide a confirmation report to the MA 74 via the communication link 64, 66.
[0067] Figure 2A is a component diagram of an example vehicle V2X system 200 suitable for implementing various embodiments. Figures 1A to 2A, the system 200 may include a vehicle 102 that includes a V2X system 104. The vehicle processing system 104 may communicate with various systems and devices such as an on-board network 210, an infotainment system 212, various sensors 214, various actuators 216, and a radio module 218 coupled to an antenna 219. The vehicle processing system 104 may also communicate with a roadside unit 112, a cellular communication network base station 110, and other external devices.
[0068] The V2X system 204 may include a processor 205, a memory 206, an input module 207, an output module 208, and a radio module 218. The processor 205 may be coupled to the memory 206 (i.e., a non-transitory storage medium) and may be configured with processor-executable instructions stored in the memory 206 to perform operations according to the methods of the various embodiments described herein. In addition, the processor 205 may be coupled to the output module 208 (which may control an in-vehicle display) and to the input module 207 to receive information from vehicle sensors and driver input.
[0069] The V2X system 204 may include a V2X antenna 219 coupled to a radio module 218, the V2X antenna being configured to communicate with one or more ITS participants (e.g., stations), roadside units 112, and base stations 110 or another suitable network access point. The V2X antenna 219 and radio module 218 may be configured to receive dynamic traffic flow characteristics information via vehicle-to-everything (V2X) communications. In various embodiments, the V2X system may receive information from multiple information sources, such as an onboard network 210, an infotainment system 212, various sensors 214, various actuators 216, and a radio module 218. The V2X system may be configured to use map data and sensor data to perform autonomous or semi-autonomous driving functions, as further described below.
[0070] Examples of vehicle-mounted networks 210 include controller area networks (CAN), local interconnect networks (LIN), networks using the FlexRay protocol, media-oriented systems transport (MOST) networks, and automotive Ethernet networks. Examples of vehicle sensors 214 include location determination systems (such as global navigation satellite systems (GNSS) systems), cameras, radars, lidars, ultrasonic sensors, infrared sensors, and other suitable sensor devices and systems. Examples of vehicle actuators 216 include various physical control systems such as for steering, braking, engine operation, lights, direction signals, etc.
[0071] Figure 2B2 is a component block diagram illustrating components of an example vehicle V2X system 220 (e.g., V2X system 104) suitable for implementing various embodiments. The V2X system 220 may include various subsystems, communication elements, computing elements, computing devices, or units that can be utilized within the vehicle 102. Figures 1A to 2A , various computing elements, computing devices or units within the V2X system 220 can be connected via the vehicle-mounted network 210 (e.g., by Figure 2B In some implementations, the various computing elements, computing devices, or units within the V2X system 220 may be implemented within a single computing device, such as a separate thread, process, algorithm, or computing element. Thus, Figure 2B Each subsystem / computing element illustrated in is also generally referred to herein as a "layer" within the computing "stack" that makes up the vehicle V2X system 220. However, the use of the terms layer and stack when describing various embodiments is not intended to imply or require that the corresponding functionality be implemented within a single vehicle computing device, although this is a potential specific embodiment. Instead, the use of the term "layer" is intended to include subsystems with independent processors, computing elements (e.g., threads, algorithms, subroutines, etc.) running in one or more computing devices, and combinations of subsystems and computing elements.
[0072] The V2X system 220 may include a radar and / or lidar perception layer 222, a camera perception layer 224, a positioning engine layer 226, a map database 228, a map fusion and arbitration layer 230, a route planning layer 232, an operating mode evaluation layer 234, a sensor fusion and road world model (RWM) management layer 236, a motion planning and control layer 238, and a behavior planning and prediction layer 240. The layers 222-240 are merely examples of some of the layers in one example configuration of the V2X system 220. In other configurations, other layers may be included, such as additional layers for other perception sensors (e.g., a lidar perception layer, etc.), additional layers for planning and / or control, additional layers for modeling, etc., and / or some of the layers 222-240 may be excluded from the V2X system 220. Figure 2BAs illustrated by the arrows in , each of the layers 222-240 can exchange data, calculation results, and commands. In addition, the V2X system 220 can receive and process data from sensors (e.g., radar, lidar, camera, inertial measurement unit (IMU), etc.), navigation information sources (e.g., global positioning system (GPS) receiver, IMU, etc.), vehicle networks (e.g., controller area network (CAN) bus), and databases in memory (e.g., digital map data). The V2X system 220 can output vehicle control commands or signals to the ADS vehicle control unit 242, which is a system, subsystem, or computing device that interfaces directly with the vehicle steering, throttle, and brake controls. Figure 2A The configuration of the V2X system 220 and the ADS vehicle control unit 242 illustrated in FIG. 1 is merely an example configuration, and other configurations of the vehicle management system and other vehicle components may be used. As an example, Figure 2B The configuration of the V2X system 220 and the ADS vehicle control unit 242 illustrated in FIG. 2 may be used in a vehicle configured for autonomous operation or semi-autonomous operation, while a different configuration may be used in a non-autonomous vehicle.
[0073] The radar and / or lidar perception layer 222 may receive data from one or more detection and ranging sensors, such as radar (e.g., 132) and / or lidar (e.g., 138), and process the data to identify and determine the location of other vehicles and objects in the vicinity of the vehicle 100. The radar perception layer 222 may include the use of neural network processing and artificial intelligence methods to identify objects and vehicles, and pass such information to the sensor fusion and RWM management layer 236.
[0074] The camera perception layer 224 may receive data from one or more cameras, such as cameras (e.g., 158, 160), and process the data to identify and determine the location of other vehicles and objects in the vicinity of the vehicle 100. The camera perception layer 224 may include the use of neural network processing and artificial intelligence methods to identify objects and vehicles, and pass such information to the sensor fusion and RWM management layer 236.
[0075] The positioning engine layer 226 can receive data from the radar and / or lidar perception layer 222, the camera perception layer 224, and various navigation information sources, and process the data and information to determine the location of the vehicle 100. The various navigation information sources may include, but are not limited to, GPS receivers, IMUs, and / or other sources and sensors connected via a CAN bus. The positioning engine layer 226 can also utilize input from one or more cameras, such as cameras (e.g., 158, 160) and / or any other available sensors capable of identifying and determining the direction and distance to objects near the vehicle, such as radar, lidar, etc.
[0076] The vehicle V2X system 220 may include or be coupled to a vehicle wireless communication subsystem 218. One or more of the layers 222-240 may provide information to or receive information from the wireless communication subsystem 218. The wireless communication subsystem 218 may be configured to communicate with a highway communication system, such as via a V2X communication link (e.g., 124) and / or communicate with a remote information source (e.g., computing device 132) via a cellular wireless communication link (e.g., 122), such as via a 5G cellular network.
[0077] The map fusion and arbitration layer 230 can access the map database 228 to obtain location information about nearby objects and features, and receive positioning / navigation information output from the positioning engine layer 226, and process this data to further determine the positioning of the vehicle 102 in the map, such as the position within the traffic lane, the position within the street map, etc. The sensor data can be stored in a memory (e.g., memory 312).
[0078] Similar to the location information in some map objects and features and sensor accuracy and precision, GPS positioning includes some errors, so the map fusion and arbitration layer 230 can be used to determine the best guess position of the vehicle within the road based on arbitration between GPS coordinates, sensor data, and map data regarding objects and features in and near the road. For example, although the GPS coordinates may place the vehicle near the middle of a two-lane road in the sensor data, the map fusion and arbitration layer 230 may determine that the vehicle is most likely aligned with a lane of travel that is consistent with the direction of travel based on the direction of travel. The map fusion and arbitration layer 230 can pass the arbitrated map position information to the sensor fusion and RWM management layer 236.
[0079] The route planning layer 232 can utilize sensor data and input from an operator or dispatcher to plan a route to be followed by the vehicle 102 to a particular destination. The route planning layer 232 can pass map-based location information to the sensor fusion and RWM management layer 236. However, other layers (such as the sensor fusion and RWM management layer 236, etc.) do not require the use of a priori maps. For example, other stacks can operate and / or control vehicles based solely on sensory data without a provided map, building concepts of lanes, boundaries, and local maps as the sensory data is received.
[0080] In embodiments including an operating mode evaluation layer 234, the processing layer may use safety and / or confidence information about nearby objects and features to select an appropriate ADS driving mode. In some embodiments, the operating mode evaluation layer 234 may determine whether a current autonomous or semi-autonomous driving mode is consistent or appropriate with the driving environment in view of safety and / or confidence information about nearby objects and features in the driving environment.
[0081] The sensor fusion and RWM management layer 236 may receive data and outputs generated by the radar and / or lidar perception layer 222, the camera perception layer 224, the map fusion and arbitration layer 230, the route planning layer 232, and the operating mode evaluation layer 234, and use some or all of such inputs to estimate or refine the position and state of the vehicle 102 relative to the road, other vehicles on the road, and other objects in the vicinity of the vehicle 100. For example, the sensor fusion and RWM management layer 236 may combine image data from the camera perception layer 224 with arbitration map position information from the map fusion and arbitration layer 230 to refine the determined position of the vehicle within the traffic lane. As another example, the sensor fusion and RWM management layer 236 may combine object recognition and image data from the camera perception layer 224 with object detection and ranging data from the radar and / or lidar perception layer 222 to determine and refine the relative position of other vehicles and objects in the vicinity of the vehicle. As another example, the sensor fusion and RWM management layer 236 may receive information about the location and direction of travel of other vehicles from V2X communications (such as via a CAN bus) and combine this information with information from the radar and / or lidar perception layer 222 and the camera perception layer 224 to refine the location and motion of other vehicles. The sensor fusion and RWM management layer 236 may output the refined location and state information of the vehicle 100 and the refined location and state information of other vehicles and objects in the vicinity of the vehicle to the motion planning and control layer 238 and / or the behavior planning and prediction layer 240.
[0082] As a further example, the sensor fusion and RWM management layer 236 can use dynamic traffic control instructions to direct the vehicle 102 to change speed, lane, direction of travel, or other navigation elements, and combine this information with other received information to determine refined position and state information. The sensor fusion and RWM management layer 236 can output the refined position and state information of the vehicle 102 and the refined position and state information of other vehicles and objects in the vicinity of the vehicle 100 to the motion planning and control layer 238, the behavior planning and prediction layer 240, and / or devices remote from the vehicle 102, such as data servers, other vehicles, etc., via wireless communication (such as through a C-V2X connection, other wireless connections, etc.).
[0083] As yet a further example, the sensor fusion and RWM management layer 236 may monitor perception data from various sensors (such as perception data from the radar and / or lidar perception layer 222, the camera perception layer 224, other perception layers, etc.) and / or data from one or more sensors themselves to analyze conditions in the vehicle sensor data. The sensor fusion and RWM management layer 236 may be configured to detect conditions in the sensor data, such as sensor measurements being at, above, or below a threshold, certain types of sensor measurements occurring, etc., and may output the sensor data as part of refined position and state information of the vehicle 102 that is provided to the behavior planning and prediction layer 240 and / or devices remote from the vehicle 100 (such as data servers, other vehicles, etc.) via wireless communications (such as through a C-V2X connection, other wireless connections, etc.).
[0084] The behavior planning and prediction layer 240 of the autonomous vehicle V2X system 220 may use the refined position and state information of the vehicle 102 and the position and state information of other vehicles and objects output from the sensor fusion and RWM management layer 236 to predict the future behavior of other vehicles and / or objects. For example, the behavior planning and prediction layer 240 may use such information to predict the future relative positions of other vehicles based on its own vehicle position and speed and the positions and speeds of other vehicles in the vicinity of the vehicle. Such predictions may take into account information from map data and route planning to anticipate changes in relative vehicle positioning as the host vehicle and other vehicles move along the road. The behavior planning and prediction layer 240 may output other vehicle and object behavior and position predictions to the motion planning and control layer 238. Additionally, the behavior planning and prediction layer 240 may use the object behavior in conjunction with the position predictions to plan and generate control signals for controlling the motion of the vehicle 102. For example, based on the route planning information, the refined position in the road information, and the relative position and movement of other vehicles, the behavior planning and prediction layer 240 may determine that the vehicle 102 needs to change lanes and acceleration, such as to maintain or achieve a minimum spacing with other vehicles, and / or to prepare for a turn or exit. Therefore, the behavior planning and prediction layer 240 may calculate or otherwise determine the steering angle of the wheels and the change to the throttle setting, which will be commanded to the motion planning and control layer 238 and the ADS vehicle control unit 242 along with various such parameters necessary to achieve such lane changes and acceleration. One such parameter may be the calculated steering wheel command angle.
[0085] The motion planning and control layer 238 may receive data and information output from the sensor fusion and RWM management layer 236, map data from the map database 232, and other vehicle and object behavior and position predictions from the behavior planning and prediction layer 240, and use this information to plan and generate control signals for controlling the motion of the vehicle 102, and verify that such control signals meet the safety requirements of the vehicle 100. For example, based on the route planning information, the refined position in the road information, and the relative position and motion of other vehicles, the motion planning and control layer 238 may verify and pass various control commands or instructions to the ADS vehicle control unit 242.
[0086] The ADS vehicle control unit 242 may receive commands or instructions from the motion planning and control layer 238 and convert such information into mechanical control signals for controlling the wheel angles, brakes, and throttle of the vehicle 100. For example, the ADS vehicle control unit 242 may respond to a calculated steering wheel command angle by transmitting a corresponding control signal to a steering wheel controller.
[0087] In various embodiments, the wireless communication subsystem 218 can communicate with other V2X system participants (e.g., other vehicles 12, 14, 16) via wireless communication links to send sensor data, positioning data, vehicle data, and data collected by onboard sensors about the vehicle's surroundings. Other V2X system participants can use such information to update stored sensor data for relay to other V2X system participants.
[0088] In various embodiments, the vehicle V2X system 220 may include functionality to perform safety checks or oversight of various commands, plans, or other decisions of various layers that may affect the safety of the vehicle and occupants. Such safety checks or oversight functionality may be implemented within a dedicated layer or distributed between various layers and included as part of the functionality. In some embodiments, various safety parameters may be stored in memory, and the safety check or oversight functionality may compare the determined values (e.g., relative spacing from nearby vehicles, distance from the centerline of the road, etc.) with the corresponding safety parameters, and issue a warning or command if the safety parameters are violated or will be violated. For example, the safety or oversight function in the behavior planning and prediction layer 240 (or in a separate layer) may determine the current or future separation distance between another vehicle (as defined by the sensor fusion and RWM management layer 236) and the vehicle (e.g., based on a world model refined by the sensor fusion and RWM management layer 236), compare the separation distance with the safe separation distance parameter stored in the memory, and issue instructions to the motion planning and control layer 238 to accelerate, decelerate, or turn if the current or predicted separation distance violates the safe separation distance parameter. As another example, safety or supervisory functionality in the motion planning and control layer 238 (or in a separate layer) may compare a determined or commanded steering wheel command angle to a safe wheel angle limit or parameter and issue an override command and / or alarm in response to the commanded angle exceeding the safe wheel angle limit.
[0089] Some safety parameters stored in memory may be static (i.e., do not change over time), such as maximum vehicle speed. Other safety parameters stored in memory may be dynamic in that they are continuously or periodically determined or updated based on vehicle state information and / or environmental conditions. Non-limiting examples of safety parameters include: maximum safe speed, maximum brake pressure, maximum acceleration, and safe wheel angle limits, all of which may vary depending on road and weather conditions.
[0090] Figure 3Ais a block diagram illustrating example components of a system on a chip (SOC) 300 for use in a vehicle V2X processing system according to various embodiments. Figures 1A to 3A , the processing device SOC 300 may include multiple heterogeneous processors, such as a digital signal processor (DSP) 303, a modem processor 304, an image and object recognition processor 306, a mobile display processor 307, an application processor 308, and a resource and power management (RPM) processor 317. The processing device SOC 300 may also include one or more coprocessors 310 (e.g., a vector coprocessor) connected to one or more of the heterogeneous processors 303, 304, 306, 307, 308, 317. Each of these processors may include one or more cores and an independent / internal clock. Each processor / core may perform operations independently of other processors / cores. For example, the processing device SOC 300 may include a processor that executes a first type of operating system (e.g., FreeBSD, LINUX, OS X, etc.) and a processor that executes a second type of operating system (e.g., Microsoft Windows). In some embodiments, the application processor 308 may be the main processor, central processing unit (CPU), microprocessor unit (MPU), arithmetic logic unit (ALU), etc. of the SOC 300. Graphics processor 306 may be a graphics processing unit (GPU).
[0091] The processing device SOC 300 may include analog circuitry and custom circuitry 314 for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations, such as processing encoded audio and video signals for rendering in a web browser. The processing device SOC 300 may further include system components and resources 316, such as voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components for supporting processors and software clients (e.g., web browsers) running on the computing device.
[0092] The processing device SoC 300 may also include a dedicated circuit system (CAM) 305 for camera actuation and management, which includes, provides, controls and / or manages the operation of one or more cameras (e.g., main camera, web camera, 3D camera, etc.), video display data from camera firmware, image processing, video pre-processing, video front end (VFE), embedded JPEG, high-definition video codec, etc. The CAM 305 can be an independent processing unit and / or include an independent or internal clock.
[0093] In some embodiments, the image and object recognition processor 306 may be configured with processor executable instructions and / or specialized hardware that is configured to perform the image processing and object recognition analysis involved in various embodiments. For example, the image and object recognition processor 306 may be configured to perform operations of processing images received from cameras (e.g., 158, 160) via CAM 305 to recognize and / or identify other vehicles, and otherwise perform the functions of the camera perception layer 224 as described. In some embodiments, the processor 306 may be configured to process radar or lidar data and perform the functions of the radar and / or lidar perception layer 222 as described.
[0094] System components and resources 316, analog and custom circuits 314, and / or CAM 305 may include circuits for interfacing with peripheral devices such as cameras 158, 160, radar 168, lidar 170, electronic displays, wireless communication devices, external memory chips, etc. Processors 303, 304, 306, 307, 308 may be interconnected to one or more memory elements 312, system components and resources 316, analog and custom circuits 314, CAM 305, and RPM processor 317 via interconnect / bus module 324, which may include a reconfigurable logic gate array and / or implement a bus architecture (e.g., CoreConnect, AMBA, etc.). Communications may be provided by advanced interconnects, such as a high-performance network-on-chip (NoC).
[0095] The processing device SOC 300 may further include an input / output module (not illustrated) for communicating with resources external to the SOC, such as a clock 318 and a voltage regulator 320. Resources external to the SOC (e.g., clock 318, voltage regulator 320) may be shared by two or more internal SOC processors / cores (e.g., DSP 303, modem processor 304, graphics processor 306, application processor 308, etc.).
[0096] In some embodiments, the processing device SOC 300 may be included in a control unit (e.g., 140) for use in a vehicle (e.g., 100). The control unit may include a communication link for communicating with a telephone network (e.g., 180), the Internet, and / or a network server (e.g., 184), as described.
[0097] The processing device SOC 300 may also include additional hardware and / or software components suitable for collecting sensor data from sensors, including motion sensors (e.g., accelerometers and gyroscopes of an IMU), user interface elements (e.g., input buttons, touch screen displays, etc.), microphone arrays, sensors for monitoring physical conditions (e.g., position, direction, motion, orientation, vibration, pressure, etc.), cameras, compasses, GPS receivers, communication circuit systems (e.g., WLAN, WiFi, etc.) and other well-known components of modern electronic devices.
[0098] Figure 3B is a component block diagram illustrating elements of a vehicle V2X system 330 configured according to various embodiments. Figures 1A to 3B , the V2X system 330 may include a vehicle processing system 204 of a vehicle (e.g., 102), which may be configured to communicate with a roadside unit 112, a cellular network base station 110, and / or one or more other vehicles 12, 14, 16.
[0099] The vehicle processing system 204 may include one or more processors 205 , memory 206 , a radio module 218 , and other components. The vehicle processing system 204 may include a number of hardware, software, and / or firmware components that operate together to provide the functionality attributed herein to the processor 205 .
[0100] The memory 206 may include a non-transitory storage medium that electronically stores information. The electronic storage medium of the memory 206 may include a system storage device provided integrally (i.e., substantially non-removable) with the vehicle processing system 204 and / or one or both of a removable storage device that is removably connected to the vehicle processing system 204 via, for example, a port (e.g., a universal serial bus (USB) port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). In various embodiments, the memory 206 may include one or more of a charge-based storage medium (e.g., EEPROM, RAM, etc.), a solid-state storage medium (e.g., a flash drive, etc.), an optically readable storage medium (e.g., an optical disk, etc.), a magnetically readable storage medium (e.g., a magnetic tape, a magnetic hard drive, a floppy disk drive, etc.), and / or other electronically readable storage media. The memory 206 may include one or more virtual storage resources (e.g., a cloud storage device, a virtual private network, and / or other virtual storage resources). The memory 206 may store software algorithms, information determined by the processor 205, information received from one or more other vehicles 12, 14, 16, information received from the roadside unit 112, information received from the base station 110, and / or other information that enables the vehicle processing system 204 to function as described herein.
[0101] Processor 205 may include one of a plurality of local processors that may be configured to provide information processing capabilities in vehicle processing system 204. Thus, processor 205 may include one or more of the following: a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and / or other mechanisms for electronically processing information. Although processor 205 may be configured to provide information processing capabilities in vehicle processing system 204, processor 205 may include one or more of the following: a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and / or other mechanisms for electronically processing information. Figure 3B 205 is illustrated as a single entity, but this is for illustration purposes only. In some embodiments, processor 205 may include multiple processing units. These processing units may be physically located within the same device, or processor 205 may represent processing functionality of multiple devices distributed in the vehicle and operating in coordination.
[0102] The vehicle processing system 204 may be configured by machine-readable instructions 332, which may include one or more instruction modules. The instruction module may include a computer program module. In various embodiments, the instruction module may include one or more of the following: a misconduct reporting module 334, a misconduct reporting priority module 336, a situation determination module 338, a criticality value module 340, a transmission probability module 342, a misconduct reporting strategy module 344, a transmit / receive (TX / RX) module 346, and / or other modules.
[0103] The misbehavior reporting module 334 may be configured to generate a misbehavior report based on the detected V2X misbehavior. The misbehavior reporting module 334 may be configured to send the misbehavior report based on the assigned priority (in some embodiments, using the TX / RX module 346). The misbehavior reporting module 334 may be configured to send the misbehavior report based on the assigned criticality value. The misbehavior reporting module 334 may be configured to send the misbehavior report based on the probability that the neighboring vehicle will report the detected V2X misbehavior.
[0104] The misbehavior report priority module 336 may be configured to assign priorities to the generated misbehavior reports based on external conditions related to the detected V2X misbehavior. The misbehavior report priority module 336 may be configured to determine the probability that a neighboring vehicle will report the detected V2X misbehavior. The misbehavior report priority module 336 may be configured to assign priorities to the generated misbehavior reports based on parameters of a misbehavior reporting policy received from, for example, the MA.
[0105] The context determination module 338 may be configured to determine an event type of the detected V2X misbehavior for the misbehavior report, and determine the context of the detected V2X misbehavior based on the expected response to the detected V2X misbehavior. The context determination module 338 may be configured to determine the context based on the degree to which the expected response of the vehicle to the detected V2X misbehavior will deviate from the current behavior of the vehicle. The context determination module 338 may be configured to determine the expected response of one or more neighboring vehicles to the detected V2X misbehavior. The context determination module 338 may be configured to determine the degree to which the detected V2X misbehavior deviates from the ground truth determined by the processor of the V2X system. The context determination module 338 may be configured to determine the number of V2X-enabled neighboring vehicles of the vehicle. The situation determination module 338 may be configured to determine whether the number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles, determine the distance between the location associated with the detected V2X misbehavior and the location of each of the neighboring vehicles and the distance between the location associated with the detected V2X misbehavior and the vehicle in response to determining that the number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles, and determine the number of vehicles closest to the location associated with the detected V2X misbehavior.
[0106] The criticality value module 340 may be configured to assign a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior.
[0107] The transmission probability module 342 may be configured to use the assigned criticality value as a weighting factor along with other factors used to determine whether to send a misbehavior report. The transmission probability module 342 may be configured to determine the weighting factor based on the number of neighboring vehicles that are enabled with V2X. The transmission probability module 342 may be configured to use the weighting factor to take action to adjust the probability that the processor will send a misbehavior report. The transmission probability module 342 may be configured to take action to increase the probability that the processor will transmit the misbehavior report in response to determining that the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior. The transmission probability module 342 may be configured to take action to reduce the probability that the processor will transmit a misbehavior report in response to determining that the vehicle is not among the number of vehicles closest to the location associated with the detected V2X misbehavior.
[0108] The misconduct reporting policy module 344 may be configured to receive a misconduct reporting policy including parameters that can be used by the processor to determine whether to transmit a misconduct report from a network computing device (e.g., MA 74, 132). The misconduct reporting policy module 344 may be configured to apply one or more of these parameters, which may include a time window, an indication to increase the probability of the processor transmitting a misconduct report, a threshold number of misconduct reports related to the same V2X transmitter, and / or other suitable parameters that can be used by the processor to determine whether to transmit a misconduct report.
[0109] The TX / RX module 346 may be configured to control the operation of communication devices of the vehicle processing system, such as the radio module 218 .
[0110] Processor 205 may be configured to execute modules 332 - 346 and / or other modules via software, hardware, firmware, or some combination of software, hardware, and / or firmware and / or other mechanisms for configuring processing capabilities on processor 205 .
[0111] The description of the functionality provided by the different modules 332 to 346 is for illustrative purposes and is not intended to be limiting, as any of the modules 332 to 346 may provide more or less functionality than that described. For example, one or more of the modules 332 to 346 may be eliminated, and some or all of their functionality may be provided by other modules of the modules 332 to 346. As another example, the processor 205 may be configured to execute one or more additional modules that may perform some or all of the functionality attributed below to one of the modules 332 to 346.
[0112] Figure 4A is a process flow diagram of an example method 400a performed by a processor of a vehicle V2X system for managing the transmission of misbehavior reports according to various embodiments. Figures 1A to 4A , method 400a may be performed by a processor of a V2X system (e.g., 205, 300) or other vehicle processors (e.g., 104, 204, 205, 220, 300), which may be implemented in hardware elements, software elements, or a combination of hardware and software elements (collectively referred to as "vehicle processors").
[0113] In block 402, the vehicle processor may generate a misbehavior report based on the detected V2X misbehavior. Means for performing the operations of block 402 may include executing the misbehavior reporting module 334 and the processor (e.g., 205, 303, 304, 306, 307, 308, 310) of the radio module 218.
[0114] In block 404, the vehicle processor may assign a priority or a transmission probability to the generated misbehavior report based on external conditions related to the detected V2X misbehavior. Means for performing the operations of block 404 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the misbehavior report priority module 336.
[0115] In some embodiments, in optional determination block 405, the vehicle processor may determine whether the assigned priority or transmission probability satisfies the transmission threshold. Means for performing the operations of optional determination block 405 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the misconduct report priority module 336.
[0116] In response to determining that the assigned priority or probability does not meet the sending threshold (ie, optional determination block 405 = "No"), in optional block 406 the vehicle processor may not send the misbehavior report.
[0117] In block 404, after the vehicle processor assigns a priority to the generated misbehavior report based on external conditions related to the detected V2X misbehavior, or in response to determining that the assigned priority meets the transmission threshold (i.e., optional determination block 405 = "Yes"), the vehicle processor may store the generated and prioritized misbehavior report in a transmission buffer, and then determine in block 408 whether to transmit a given misbehavior report during a transmission opportunity based on the assigned priority or probability. In some embodiments, the V2X system may transmit the misbehavior reports that have been generated, prioritized, and stored in the transmission buffer in the order of the assigned priorities, wherein the highest priority misbehavior report stored in the buffer is transmitted at each V2X transmission opportunity. In some embodiments, the V2X system may determine whether the assigned probability of transmitting the misbehavior report meets the transmission criteria based on the generated random value, such as whether the probability is greater than or equal to the generated random value, and transmit the misbehavior report in response to determining that the transmission criteria are met. In some embodiments, the V2X system may multiply the assigned transmission probability by a random value, compare the product to a threshold, and transmit the misbehavior report in response to determining that the product of the probability of transmitting the misbehavior report multiplied by the generated random value exceeds the threshold. Means for performing the operations of block 406 may include executing a processor (e.g., 205, 303, 304, 306, 307, 308, 310) of the misbehavior reporting module 334, the TX / RX module 334, and the radio module 218.
[0118] FIG. 4B to FIG. 4Eis a process flow diagram of example operations 400b-400e that may be performed by a processor of a vehicle V2X system as part of a method 400a for managing the transmission of misconduct reports, according to various embodiments. Figures 1A to 4E , operations 400b-400e may be performed by a processor of the V2X system (e.g., 205, 300) or other vehicle processors (e.g., 104, 204, 205, 220, 300), which may be implemented in hardware elements, software elements, or a combination of hardware and software elements (collectively referred to as "vehicle processors").
[0119] refer to Figure 4B , after performing the operations of generating a misbehavior report based on the detected V2X misbehavior in block 402 as described, in block 410, the vehicle processor may determine the event type of the detected V2X misbehavior for the misbehavior report, and determine the context of the detected V2X misbehavior based on the expected response to the detected V2X misbehavior. In some embodiments, the vehicle processor may determine the context based on the degree to which the expected response of the vehicle to the detected V2X misbehavior will deviate from the current behavior of the vehicle. In some embodiments, the vehicle processor may determine the expected response of one or more neighboring vehicles to the detected V2X misbehavior. In some embodiments, the vehicle processor may determine the degree to which the detected V2X misbehavior deviates from the ground truth determined by the processor of the V2X system. The components for performing the operations of block 410 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310), a sensor 214, and a radio module 218 that executes the misbehavior reporting module 334 and the context determination module 338.
[0120] In block 412, the vehicle processor may assign a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior. Means for performing the operations of block 412 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the criticality value module 340.
[0121] In some embodiments, in optional determination block 414, the vehicle processor may determine whether the assigned criticality value meets the transmission threshold. The means for performing the operation of optional determination block 414 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the misbehavior report priority module 336.
[0122] In response to determining that the assigned criticality value does not satisfy the transmission threshold (ie, optional determination block 414 = "No"), in optional block 416 the vehicle processor may not transmit the misbehavior report.
[0123] In block 412, after the vehicle processor assigns a criticality value to the generated misbehavior report based on external conditions related to the detected V2X misbehavior, or in response to determining that the assigned priority meets the transmission threshold (i.e., optional determination block 414 = "Yes"), the vehicle processor may store the generated and prioritized misbehavior reports in a transmission buffer, and then transmit the misbehavior reports based on the assigned criticality values in block 418. In some embodiments, the V2X system may transmit the misbehavior reports stored in the transmission buffer in the order of the assigned criticality values, such that the misbehavior report stored in the buffer with the highest priority is transmitted at each V2X transmission opportunity.
[0124] In some embodiments, the vehicle processor may use the assigned criticality value as a transmission probability value, or assign a transmission probability value for determining whether to send a misbehavior report. In some embodiments, the V2X system may determine whether the transmission probability assigned to the misbehavior report meets the transmission criteria based on the generated random value, such as whether the probability is greater than or equal to the generated random value, and send the misbehavior report in response to determining that the transmission criteria are met. In some embodiments, the V2X system may multiply the assigned transmission probability by the random value, compare the product to a threshold, and send the misbehavior report in response to determining that the product of the probability of sending the misbehavior report multiplied by the generated random value meets or exceeds the threshold.
[0125] In some embodiments, the vehicle processor may use the assigned criticality value as a weighting factor to determine whether to send a misconduct report. For example, the processor may determine the probability that the processor can send a misconduct report. In some embodiments, the processor may determine or assign a baseline or initial probability of sending a misconduct report to the misconduct report, and then adjust (e.g., increase or decrease) the probability of sending a misconduct report based on the criticality value. In some embodiments, the vehicle processor may generate a random value, and use the generated random value and the adjusted transmission probability to determine whether to send a misconduct report. In some embodiments, the V2X system may determine whether the assigned probability of sending a misconduct report meets the transmission criteria based on the generated random value, such as whether the probability is greater than or equal to the generated random value, and send a misconduct report in response to determining that the transmission criteria are met. In some embodiments, the V2X system may multiply the assigned transmission probability by the random value, compare the product with a threshold, and send a misconduct report in response to determining that the product of the transmission probability multiplied by the generated random value exceeds the threshold.
[0126] Means for performing the operations of block 418 may include a processor (eg, 205 , 303 , 304 , 306 , 307 , 308 , 310 ) executing the transmit probability module 342 , the TX / RX module 334 , and the radio module 218 .
[0127] refer to Figure 4C After performing operations to generate a misbehavior report based on detected V2X misbehavior in block 402 as described, the vehicle processor may determine the number of V2X-enabled neighboring vehicles in block 420. The means for performing the operations of block 420 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the context determination module 338.
[0128] In block 422, the vehicle processor may determine a weighting factor based on the number of V2X-enabled neighboring vehicles. For example, the vehicle processor may detect or identify n V2X-enabled vehicles. The vehicle processor may determine a weighting factor based on the number n of V2X-enabled vehicles.
[0129] In some embodiments, the weighting factor can be expressed as Where f(n) represents a weighting factor, n represents the number of V2X-enabled vehicles in proximity, c represents a constant (e.g., 10) that adjusts the weighting factor according to the number of reporting vehicles n, and e represents a constant (e.g., Euler's number). The means for performing the operations of block 422 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) that executes the transmit probability module 342.
[0130] In block 424, the vehicle processor may use the weighting factor to take action to adjust the probability that the processor will send the misbehavior report. In some embodiments, the V2X system may use the weighting factor to perform a mathematical operation to adjust the probability that the processor will send a misbehavior report. In this way, the V2X system may adjust the probability that the processor will send a misbehavior report based on the number of V2X-enabled neighboring vehicles, so that the total number of misbehavior reports sent to the MA for the same V2X misbehavior is reduced. The means for performing the operations of block 424 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing a transmission probability module 342.
[0131] In block 426, the vehicle processor may send a misbehavior report based on the adjusted transmission probability. In some embodiments, the V2X system may determine whether the assigned probability of sending a misbehavior report meets a transmission criterion based on the generated random value, such as whether the probability is greater than or equal to the generated random value, and send the misbehavior report in response to determining that the transmission criterion is met. In some embodiments, the V2X system may multiply the assigned transmission probability by the random value, compare the product to a threshold, and send the misbehavior report in response to determining that the product of the transmission probability multiplied by the generated random value exceeds the threshold. The components for performing the operations of block 426 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) that executes the transmission probability module 342, the misbehavior report module 334, and the TX / RX module 346.
[0132] refer to Figure 4D After determining the probability that a neighboring vehicle will report detected V2X misbehavior in block 420 as described, the vehicle processor may determine whether the number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles in determination block 430. Means for performing the operations of determination block 430 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the context determination module 338.
[0133] In response to determining that the number of neighboring vehicles proximate to the vehicle does not exceed a threshold number of vehicles (i.e., determination box 430 = "No"), the vehicle processor may send a misbehavior report as described in box 422 based on the probability that the neighboring vehicle will report the detected V2X misbehavior.
[0134] In response to determining that the number of neighboring vehicles adjacent to the vehicle exceeds the threshold number of vehicles (i.e., determination block 430 = "Yes"), the vehicle processor may determine, in block 432, a distance between the location associated with the detected V2X misbehavior and the location of each of the neighboring vehicles and a distance between the location associated with the detected V2X misbehavior and the vehicle in response to determining that the number of neighboring vehicles adjacent to the vehicle exceeds the threshold number of vehicles. Means for performing the operations of block 432 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the context determination module 338.
[0135] In block 434, the vehicle processor may determine the number of vehicles closest to the location associated with the detected V2X misbehavior. Means for performing the operations of block 434 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the context determination module 338.
[0136] In determination block 436, the vehicle processor may determine whether the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior. Means for performing the operations of block 436 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing a context determination module 338.
[0137] In response to determining that the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior (i.e., determination block 436 = "Yes"), the vehicle processor may responsively take action in block 438 to increase the probability that the processor will transmit a misbehavior report. Means for performing the operations of block 438 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing a transmit probability module 342.
[0138] In response to determining that the vehicle is not among the number of vehicles closest to the location associated with the detected V2X misbehavior (i.e., determination block 436 = "No"), the vehicle processor may responsively take action in block 440 to reduce the probability that the processor will transmit a misbehavior report. Means for performing the operations of block 440 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing a transmit probability module 342.
[0139] After performing the operations of block 438 or 440 , the vehicle processor may send a misbehavior report as described in block 426 based on the probability that the neighboring vehicle will report the detected V2X misbehavior.
[0140] refer to Figure 4E After performing operations to generate a misbehavior report based on detected V2X misbehavior in block 402 as described, the vehicle processor may receive a misbehavior reporting policy from a network computing device (e.g., MA 74, 132), the misbehavior reporting policy including parameters that can be used by the vehicle processor to determine whether to send a misbehavior report in block 450. Means for performing the operations of block 450 may include executing a misbehavior reporting policy module 344 and a processor (e.g., 205, 303, 304, 306, 307, 308, 310) of the radio module 218.
[0141] In box 452, in some embodiments, the vehicle processor may assign a priority to the generated misconduct report based on the parameters of the misconduct reporting strategy. In some embodiments, the vehicle processor may adjust the priority of the assignment of the misconduct report based on the parameters of the misconduct reporting strategy. In some embodiments, the misconduct reporting strategy parameters may include a time window. In such embodiments, in response to determining that a misconduct report was generated during the time window, the vehicle processor may take action to assign a relatively high priority to the misconduct report or increase the priority of the assignment of the misconduct report. In some embodiments, the misconduct reporting strategy parameters may include an indication of increasing the priority of the misconduct report. For example, the strategy parameters may indicate that a certain or certain types of V2X misconduct should be reported to the MA first. In such embodiments, the vehicle processor may take action to increase the priority of the misconduct report in response to the indication in the misconduct reporting strategy parameters. In some embodiments, the misconduct reporting strategy parameters may include a threshold number of misconduct reports associated with the same V2X transmitter. In such embodiments, the vehicle processor may take action to increase the priority of the misbehavior report in response to determining that the number of V2X reports generated by the processor related to the same V2X transmitter meets a threshold included in the misbehavior reporting policy parameter. The means for performing the operations of block 452 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) executing the misbehavior reporting policy module 344 and the misbehavior reporting priority module 336.
[0142] In block 454, the vehicle processor may send the misbehavior report based on the assigned priority. In some embodiments, the vehicle processor may send the misbehavior report based on the adjusted priority. The components for performing the operations of block 454 may include executing the misbehavior report policy module 344, the misbehavior report priority module 336, the TX / RX module 346, and the processor (e.g., 205, 303, 304, 306, 307, 308, 310) of the radio module 218.
[0143] In block 456, in some embodiments, the vehicle processor may assign a probability of transmission to the generated misbehavior report based on the parameters of the misbehavior strategy. In some embodiments, the vehicle processor may also take action to adjust the probability that the processor will send a misbehavior report. In some embodiments, the misbehavior report policy parameters may include a time window. In such embodiments, the vehicle processor may take action to increase the probability that the processor will transmit the misbehavior report in response to determining that a misbehavior report was generated during the time window. In some embodiments, the misbehavior report policy parameters may include an indication of increasing the probability that the processor transmits the misbehavior report. In such embodiments, the vehicle processor may take action to increase the probability that the processor will transmit the misbehavior report in response to an indication in the misbehavior report policy parameters. In some embodiments, the misbehavior report policy parameters may include a threshold number of misbehavior reports associated with the same V2X transmitter. In such embodiments, the vehicle processor may take action to increase the probability that the processor will transmit the misbehavior report in response to determining that the number of V2X reports associated with the same V2X transmitter generated by the processor meets a threshold included in the misbehavior report policy parameters. The means for performing the operations of block 456 may include a processor (eg, 205 , 303 , 304 , 306 , 307 , 308 , 310 ) executing the misconduct reporting policy module 344 and the transmission probability module 342 .
[0144] In block 458, the vehicle processor may send a misbehavior report based on the adjusted probability (i.e., the vehicle processor will send a misbehavior report). In some embodiments, the V2X system may determine whether the assigned probability of sending a misbehavior report meets a sending criterion based on the generated random value, such as whether the probability is greater than or equal to the generated random value, and send the misbehavior report in response to determining that the sending criterion is met. In some embodiments, the V2X system may multiply the assigned transmission probability by the random value, compare the product to a threshold, and send the misbehavior report in response to determining that the product of the transmission probability multiplied by the generated random value exceeds the threshold. The components for performing the operations of block 458 may include a processor (e.g., 205, 303, 304, 306, 307, 308, 310) that executes the misbehavior report policy module 344, the transmission probability module 342, the TX / RX module 346, and the radio module 218.
[0145] In various embodiments, the V2X system may be configured to perform any or all of the above operations in any combination. For example, the V2X system may be configured to determine the context of the detected V2X misbehavior, and assign a criticality value to the relevant misbehavior report based on the determined event type and the context of the detected V2X misbehavior. The V2X system may also determine a weighting factor based on the number of V2X-enabled vehicles that are neighbors of the vehicle and / or adjacent to the detected V2X misbehavior, and may use the weighting factor to take action to adjust the probability that the processor will send a misbehavior report. The V2X system may also receive a reporting policy from a network computing device (e.g., a MA) that indicates, for example, that the vehicle should prioritize the transmission of a specified type of misbehavior report (i.e., increase the priority of the V2X system transmission or increase the probability of the V2X system transmission). In such embodiments, the V2X system may perform a combination of operations to adjust the priority of the misbehavior report, or adjust the probability that the V2X system can send a misbehavior report.
[0146] Figure 5 is a component block diagram of a network computing device suitable for use with various embodiments. Figures 1A to 5 , various embodiments (including but not limited to the embodiments described with reference to FIG. 6A to FIG. 6E ) can be implemented on a variety of network computing devices, an example of which is shown in FIG. Figure 5 500 is illustrated in the form of a server computing device 500. The computing device 500 may include a processor 501 coupled to a volatile memory 502 and a large capacity non-volatile memory (such as a disk drive 503). The computing device 500 may also include a peripheral memory access device such as a floppy disk drive, a compact disk (CD) or a digital video disk (DVD) drive 506 coupled to the processor 501. The computing device 500 may also include a network access port 504 (or interface) coupled to the processor 501 for establishing a data connection with a network (such as the Internet and / or a local area network coupled to other system computers and servers). The computing device 500 may include one or more transceivers 505 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless communication link. The computing device 500 may include additional access ports such as USB, FireWire, Thunderbolt, etc. for coupling to peripheral devices, external memory or other devices.
[0147] Each specific implementation example is described in the following paragraphs. Although some of the examples in the following specific implementation examples are described in terms of example methods, other example implementations may include: the example method discussed in the following paragraphs implemented by a vehicle processing device that may be an onboard unit, a mobile device unit, a mobile computing unit, or a fixed roadside unit, the vehicle processing device including a processor configured with processor-executable instructions to perform the operations of the method of the following specific implementation example; the example method discussed in the following paragraphs implemented by a vehicle processing device including components for performing the functions of the method of the following specific implementation example; and the example method discussed in the following paragraphs may be implemented on a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause the processor of the vehicle processing device to perform the operations of the method of the following specific implementation example.
[0148] Embodiment 1. A method executed by a processor of a vehicle-to-everything (V2X) system of a vehicle for managing the sending of misbehavior reports, comprising: generating a misbehavior report based on detected V2X misbehavior;
[0149] assigning a priority or a sending probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior; and sending the misbehavior report based on the assigned priority or sending probability.
[0150] Embodiment 2. A method according to embodiment 1, wherein assigning a priority or sending probability to a generated misbehavior report based on an external condition related to the detected V2X misbehavior includes: determining an event type of the detected V2X misbehavior for the misbehavior report, and determining a context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior; and assigning a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior, wherein sending the misbehavior report based on the assigned priority includes sending the misbehavior report based on the assigned criticality value.
[0151] Embodiment 3. A method according to embodiment 2, wherein determining the context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior includes determining the context based on the extent to which the expected response of the vehicle to the detected V2X misbehavior will deviate from the current behavior of the vehicle.
[0152] Embodiment 4. The method of embodiment 2, wherein determining the context of the detected V2X misbehavior based on expected responses to the detected V2X misbehavior includes determining expected responses of one or more neighboring vehicles to the detected V2X misbehavior.
[0153] Embodiment 5. The method of embodiment 2, wherein determining the context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior comprises determining an extent to which the detected V2X misbehavior deviates from ground truth determined by a processor of the V2X system.
[0154] Embodiment 6. The method of embodiment 2, wherein sending the misconduct report based on the assigned criticality value comprises using the assigned criticality value as a weighting factor along with other factors used to determine whether to send the misconduct report.
[0155] Embodiment 7. A method according to any one of embodiments 1 to 6, wherein assigning a priority or sending probability to a generated misbehavior report based on external conditions related to the detected V2X misbehavior includes: determining the number of V2X-enabled neighboring vehicles; determining a weighting factor based on the number of V2X-enabled neighboring vehicles; and using the weighting factor to adjust the sending probability; and sending the misbehavior report based on the assigned priority or sending probability includes sending the misbehavior report based on the adjusted sending probability.
[0156] Embodiment 8. The method according to embodiment 7 further includes: determining whether the number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles; in response to determining that the number of neighboring vehicles adjacent to the vehicle exceeds the threshold number of vehicles, determining the distance between the position associated with the detected V2X misbehavior and the position of each of the neighboring vehicles and the distance between the position associated with the detected V2X misbehavior and the vehicle; determining the number of vehicles closest to the position associated with the detected V2X misbehavior; in response to determining that the vehicle is among the number of vehicles closest to the position associated with the detected V2X misbehavior, taking action to increase the probability that the processor will transmit the misbehavior report; and in response to determining that the vehicle is not among the number of vehicles closest to the position associated with the detected V2X misbehavior, taking action to reduce the probability that the processor will transmit the misbehavior report.
[0157] Embodiment 9. A method according to any one of embodiments 1 to 8, wherein assigning a priority or a probability of sending to a generated misbehavior report based on an external condition related to the detected V2X misbehavior includes: receiving a misbehavior reporting policy from a network computing device, the misbehavior reporting policy including parameters that can be used by the processor to determine whether to transmit a misbehavior report; and assigning the priority or the probability of sending to the generated misbehavior report based on the parameters of the misbehavior reporting policy. Embodiment 10. A method according to embodiment 9, wherein the misbehavior reporting policy parameters include a time window, and wherein assigning a priority or a probability of sending to a generated misbehavior report based on the parameters of the misbehavior reporting policy includes: in response to determining that the misbehavior report was generated during the time window, taking action to increase the probability that the processor will transmit the misbehavior report.
[0158] Example 11. A method according to Example 9, wherein the misconduct reporting policy parameters include an indication of increasing the probability that the processor will transmit the misconduct report, and wherein assigning priority or sending probability to the generated misconduct report based on the parameters of the misconduct reporting policy includes: in response to the indication in the misconduct reporting policy parameters, taking action to adjust the probability that the processor will transmit the misconduct report.
[0159] Embodiment 12. A method according to Embodiment 9, wherein the misbehavior reporting policy parameters include a threshold number of misbehavior reports related to the same V2X transmitter, and wherein assigning a priority or a sending probability to the generated misbehavior reports based on the parameters of the misbehavior reporting policy includes: in response to determining that the number of V2X reports related to the same V2X transmitter generated by the processor meets the threshold included in the misbehavior reporting policy parameters, transmitting the misbehavior report.
[0160] The various embodiments illustrated and described are provided merely as examples of the various features described in the claims. However, the features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment, and may be used or combined with other embodiments shown and described. In addition, the claims are not intended to be limited to any one example embodiment. For example, one or more operations of the method may replace or be combined with one or more operations of the method.
[0161] The foregoing method descriptions and process flow charts are provided only as illustrative examples, and are not intended to require or imply that the operations of the various embodiments must be performed in the order given. As will be appreciated by those skilled in the art, the order of operations in the foregoing embodiments may be performed in any order. Words such as "thereafter," "then," "next," etc. are not intended to limit the order of operations; these words are only used to guide the reader through the description of the method. In addition, any reference to a claim element in singular form (e.g., a reference using the article "one," "an," or "the") should not be interpreted as limiting the element to a singular.
[0162] The various exemplary logic blocks, modules, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits, and operations have been generally described above in 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 entire system. Although the technician may implement the described functionality in different ways for each specific application, such implementation decisions should not be interpreted as causing a departure from the scope of the claims.
[0163] The hardware for implementing the various exemplary logics, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or executed with a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Although a general purpose processor may be a microprocessor, in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuits specific to a given function.
[0164] In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored as one or more instructions or codes on a non-transient computer-readable medium or a non-transient processor-readable medium. The operation of the method or algorithm disclosed herein may be embodied in a processor-executable software module, which may reside on a non-transient computer-readable or processor-readable storage medium. A non-transient computer-readable or processor-readable storage medium may be any storage medium accessible by a computer or processor. By way of example and not limitation, such non-transient computer-readable or processor-readable media may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that may be used to store the desired program code in the form of an instruction or data structure and may be accessed by a computer. Disks and optical disks as used herein include compact discs (CDs), laser discs, optical disks, digital versatile discs (DVDs), floppy disks, and blue discs, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination is also included within the scope of non-transient computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a non-transitory processor-readable medium and / or computer-readable medium, which may be incorporated into a computer program product.
[0165] The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but should be granted the broadest scope consistent with the following claims and the principles and novel features disclosed herein.
Claims
1. A method executed by a processor of a vehicle-to-everything (V2X) system of a vehicle for managing the sending of misbehavior reports, comprising: Generate misconduct reports based on detected V2X misconduct; assigning a priority or a transmission probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior; as well as The misconduct report is sent based on the assigned priority or sending probability.
2. The method of claim 1 , wherein assigning a priority or a transmission probability to the generated misbehavior report based on external conditions related to the detected V2X misbehavior comprises: determining an event type of the detected V2X misbehavior for the misbehavior report, and determining a context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior; as well as assigning a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior, Wherein sending the misconduct report based on the assigned priority includes sending the misconduct report based on the assigned criticality value.
3. The method of claim 2 , wherein determining the context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior comprises determining the context based on the extent to which the expected response of the vehicle to the detected V2X misbehavior will deviate from a current behavior of the vehicle.
4. The method of claim 2, wherein determining the context of the detected V2X misbehavior based on expected responses to the detected V2X misbehavior comprises determining expected responses of one or more neighboring vehicles to the detected V2X misbehavior.
5. The method of claim 2, wherein determining the context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior comprises determining an extent to which the detected V2X misbehavior deviates from ground truth determined by a processor of the V2X system.
6. The method of claim 2, wherein sending the misconduct report based on the assigned criticality value comprises using the assigned criticality value as a weighting factor along with other factors used to determine whether to send the misconduct report.
7. The method according to claim 1, wherein: Assigning a priority or a probability of transmission to the generated misbehavior report based on an external condition related to the detected V2X misbehavior includes: Determine the number of V2X-enabled neighboring vehicles; determining a weighting factor based on the number of neighboring V2X-enabled vehicles; and adjusting the transmission probability using the weighting factor; and Sending the misconduct report based on the assigned priority or transmission probability includes sending the misconduct report based on the adjusted transmission probability.
8. The method according to claim 7, further comprising: determining whether a number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles; In response to determining that the number of neighboring vehicles proximate to the vehicle exceeds a threshold number of vehicles, determining a distance between a location associated with the detected V2X misbehavior and a location of each of the neighboring vehicles and a distance between the location associated with the detected V2X misbehavior and the vehicle; determining a number of vehicles closest to the location associated with the detected V2X misbehavior; responsive to determining that the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior, taking action to increase a probability that the processor will transmit the misbehavior report; as well as In response to determining that the vehicle is not among the number of vehicles closest to the location associated with the detected V2X misbehavior, taking action to reduce the probability that the processor will transmit the misbehavior report.
9. The method of claim 1 , wherein assigning a priority or a transmission probability to the generated misbehavior report based on external conditions related to the detected V2X misbehavior comprises: receiving a misconduct reporting policy from a network computing device, the misconduct reporting policy comprising parameters that can be used by the processor to determine whether to transmit a misconduct report; as well as The priority or the sending probability is assigned to the generated misconduct report based on the parameter of the misconduct reporting policy.
10. The method of claim 9, wherein the misconduct reporting policy parameters include a time window, and Wherein assigning a priority or a sending probability to the generated misconduct report based on the parameters of the misconduct reporting strategy comprises: In response to determining that the misconduct report was generated during the time window, an action is taken to increase the probability that the processor will transmit the misconduct report.
11. The method of claim 9, wherein the misconduct reporting policy parameters include an indication to increase the probability that the processor transmits the misconduct report, and Wherein assigning a priority or a sending probability to the generated misconduct report based on the parameters of the misconduct reporting strategy comprises: In response to the indication in the misconduct reporting policy parameter, an action is taken to adjust the probability that the processor will transmit the misconduct report.
12. The method of claim 9, wherein the misbehavior reporting policy parameters include a threshold number of misbehavior reports associated with the same V2X transmitter, and Wherein assigning a priority or a sending probability to the generated misconduct report based on the parameters of the misconduct reporting strategy comprises: In response to determining that a number of V2X reports generated by the processor related to the same V2X transmitter satisfies the threshold included in the misbehavior reporting policy parameter, transmitting the misbehavior report.
13. A vehicle-to-everything (V2X) system for use in a vehicle, comprising: A processor configured with processor-executable instructions to: Generate misconduct reports based on detected V2X misconduct; assigning a priority or a transmission probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior; as well as The misconduct report is sent based on the assigned priority or sending probability.
14. The V2X system of claim 13, wherein the processor is further configured with processor-executable instructions for assigning a priority or a transmission probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior by: determining an event type of the detected V2X misbehavior for the misbehavior report, and determining a context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior; and assigning a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior, Wherein the processor is further configured with processor-executable instructions for sending the misconduct report based on the assigned priority by sending the misconduct report based on the assigned criticality value.
15. The V2X system of claim 14, wherein the processor is further configured with processor-executable instructions for determining the context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior by determining the context based on the extent to which the expected response of the vehicle to the detected V2X misbehavior will deviate from the current behavior of the vehicle.
16. The V2X system of claim 14, wherein the processor is further configured with processor-executable instructions for determining the context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior by determining an expected response of one or more neighboring vehicles to the detected V2X misbehavior.
17. The V2X system of claim 14, wherein the processor is further configured with processor-executable instructions for determining the context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior by determining the extent to which the detected V2X misbehavior deviates from a ground truth determined by the processor of the V2X system.
18. The V2X system of claim 14, wherein the processor is further configured with processor-executable instructions for sending the misbehavior report based on the assigned criticality value by using the assigned criticality value as a weighting factor together with other factors used to determine whether to send the misbehavior report.
19. The V2X system of claim 13, wherein the processor is further configured with processor-executable instructions for: Assigning a priority or a probability of sending to the generated misbehavior report based on external conditions related to the detected V2X misbehavior by: Determine the number of V2X-enabled neighboring vehicles; determining a weighting factor based on the number of neighboring V2X-enabled vehicles; and adjusting the transmission probability using the weighting factor; and The misconduct report is sent based on the assigned priority or the sending probability by sending the misconduct report based on the adjusted sending probability.
20. The V2X system of claim 19, wherein the processor is further configured with processor executable instructions for the following operations: determining whether a number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles; In response to determining that the number of neighboring vehicles proximate to the vehicle exceeds a threshold number of vehicles, determining a distance between a location associated with the detected V2X misbehavior and a location of each of the neighboring vehicles and a distance between the location associated with the detected V2X misbehavior and the vehicle; determining a number of vehicles closest to the location associated with the detected V2X misbehavior; responsive to determining that the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior, taking action to increase the probability that the processor will transmit the misbehavior report; as well as In response to determining that the vehicle is not among the number of vehicles closest to the location associated with the detected V2X misbehavior, taking action to reduce the probability that the processor will transmit the misbehavior report.
21. The V2X system of claim 13, wherein the processor is further configured with processor-executable instructions for assigning a priority or a transmission probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior by: receiving a misconduct reporting policy from a network computing device, the misconduct reporting policy comprising parameters that can be used by the processor to determine whether to transmit a misconduct report; and The priority or the sending probability is assigned to the generated misconduct report based on the parameter of the misconduct reporting policy.
22. The V2X system of claim 21, wherein the misbehavior reporting policy parameters include a time window, and The processor is also configured with processor-executable instructions for assigning a priority or sending probability to the generated misconduct report based on the parameters of the misconduct reporting policy in the following manner: in response to determining that the misconduct report was generated during the time window, taking action to increase the probability that the processor will transmit the misconduct report.
23. The V2X system of claim 21, wherein the misbehavior reporting policy parameters include an indication to increase the probability that the processor transmits the misbehavior report, and The processor is also configured with processor-executable instructions for assigning priorities or sending probabilities to generated misconduct reports based on the parameters of the misconduct reporting policy in the following manner: in response to the indication in the misconduct reporting policy parameters, taking action to adjust the probability that the processor will transmit the misconduct report.
24. The V2X system of claim 21, wherein the misbehavior reporting policy parameters include a threshold number of misbehavior reports associated with the same V2X transmitter, and The processor is also configured with processor-executable instructions for assigning a priority or a sending probability to the generated misbehavior report based on the parameters of the misbehavior reporting strategy in the following manner: in response to determining that the number of V2X reports related to the same V2X transmitter generated by the processor meets the threshold included in the misbehavior reporting strategy parameters, transmitting the misbehavior report.
25. A vehicle-to-everything (V2X) system for use in a vehicle, comprising: A component for generating a misbehavior report based on detected V2X misbehavior; means for assigning a priority or a transmission probability to the generated misbehavior report based on external conditions related to the detected V2X misbehavior; and Means for sending misconduct reports based on an assigned priority or probability of sending.
26. The V2X system of claim 25, wherein the means for assigning a priority or a transmission probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior comprises: means for determining, for the misbehavior report, an event type of the detected V2X misbehavior and determining a context of the detected V2X misbehavior based on an expected response to the detected V2X misbehavior; and means for assigning a criticality value to the misbehavior report based on the determined event type and the context of the detected V2X misbehavior, Wherein the means for sending the misconduct report based on the assigned priority level includes means for sending the misconduct report based on the assigned criticality value.
27. The V2X system according to claim 25, wherein: The means for assigning a priority or a transmission probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior comprises: Means for determining a number of V2X-enabled neighboring vehicles; means for determining a weighting factor based on said number of neighboring V2X-enabled vehicles; and means for adjusting the transmission probability using the weighting factor; and The means for transmitting the misconduct report based on the assigned priority or transmission probability includes means for transmitting the misconduct report based on the adjusted transmission probability.
28. The V2X system according to claim 27, further comprising: means for determining whether a number of neighboring vehicles adjacent to the vehicle exceeds a threshold number of vehicles; means for determining a distance between a location associated with the detected V2X misbehavior and a location of each of the neighboring vehicles and a distance between the location associated with the detected V2X misbehavior and the vehicle in response to determining that the number of neighboring vehicles proximate to the vehicle exceeds a threshold number of the vehicle; means for determining a number of vehicles closest to the location associated with the detected V2X misbehavior; means for taking action to increase the probability that the V2X system will transmit the misbehavior report in response to determining that the vehicle is among the number of vehicles closest to the location associated with the detected V2X misbehavior; and Means for taking action to reduce the probability that the V2X system will transmit the misbehavior report in response to determining that the vehicle is not among the number of vehicles closest to the location associated with the detected V2X misbehavior.
29. The V2X system of claim 25, wherein the means for assigning a priority or a transmission probability to the generated misbehavior report based on external conditions related to the detected V2X misbehavior comprises: means for receiving a misbehavior reporting policy from a network computing device, the misbehavior reporting policy comprising parameters that can be used by the V2X system to determine whether to transmit a misbehavior report; and means for assigning the priority or the sending probability to the generated misconduct report based on the parameter of the misconduct reporting policy.
30. A non-transitory processor-readable medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause a processor of a vehicle-to-everything (V2X) system to perform operations, the operations comprising: Generate misconduct reports based on detected V2X misconduct; assigning a priority or a transmission probability to the generated misbehavior report based on an external condition related to the detected V2X misbehavior; as well as The misconduct report is sent based on the assigned priority or sending probability.
