Abnormal behavior indication aggregator for identifying abnormal behavior conditions in internet of vehicles (V2X) communication system
By aggregating the instructions of the abnormal behavior detection agency in the V2X communication system, determining whether there are reportsable abnormal behavior conditions, the problems of redundant reporting and resource consumption are solved, and reliable identification and response to key abnormal behaviors are achieved.
Patent Information
- Application Number
- CN202380034807.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-25
- Filing Date
- 2023-02-21
- Publication Date
- 2024-12-03
AI Technical Summary
When the V2X system detects and transmits inaccurate or intentionally incorrect information, it may cause the abnormal behavior management agency's computing equipment to overload and consume communication network resources, and it is difficult to identify key abnormal behavior reports.
By implementing an aggregation method of abnormal behavior detection agencies in the V2X communication system of the vehicle, we can determine whether there are abnormal behavior conditions that can be reported or acted on, reduce the generation and response of redundant reports, and optimize the sending of abnormal behavior reports.
It effectively reduces the sending of redundant abnormal behavior reports, optimizes the use of limited communication bandwidth, and ensures reliable transmission and timely response of key abnormal behavior reports.
Smart Images

Figure CN119072933A_ABST
Abstract
Description
[0001] Related Applications
[0002] This application claims the benefit of priority to U.S. non-provisional application No. 17 / 660,513, filed on April 25, 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 can 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 of a vehicle to broadcast V2X messages, such as Basic Safety Messages (BSM) or Collaborative Awareness Messages (CAM), which other vehicles can receive and process to improve traffic safety.
[0004] The V2X system may be configured to detect inaccurate or intentionally erroneous 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 erroneous information to an abnormal behavior management agency (abnormal behavior management agency) computing device. However, in situations where many V2X systems detect and transmit reports about such inaccurate or intentionally erroneous information, the abnormal behavior management agency computing device may receive many redundant reports, thereby potentially overloading the abnormal behavior management agency computing device. In addition, the transmission of redundant reports consumes limited communication network resources and processing power of the V2X system and the abnormal behavior management agency computing device. Summary of the invention
[0005] Various aspects include a method performed by a processor of a vehicle-to-everything (V2X) communication system of a vehicle for aggregating indications of abnormal behavior before determining that an abnormal behavior condition exists. Various aspects may include: detecting multiple indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms; aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms; determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications; and sending an abnormal behavior report or taking a responsive action in response to determining that an abnormal behavior condition exists.
[0006] In some aspects, aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms may include determining whether any of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication, and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications may include determining the existence of a reportable or actionable abnormal behavior condition in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication.
[0007] In some aspects, aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms may include determining whether any one of a selected subset of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication, and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications may include determining the existence of a reportable or actionable abnormal behavior condition in response to determining that at least one of the selected subset of the abnormal behavior detection mechanisms outputs an abnormal behavior indication.
[0008] In some aspects, aggregating abnormal behavior indications output from one or more abnormal behavior detection agencies may include aggregating abnormal behavior indications output from multiple abnormal behavior detection agencies, and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications may include determining the existence of a reportable or actionable abnormal behavior condition in response to a threshold number of abnormal behavior detection agencies outputting abnormal behavior indications.
[0009] The method of claim 4, wherein determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of abnormal behavior detection mechanisms outputting abnormal behavior indications may include determining that a reportable or actionable abnormal behavior condition exists in response to a majority of abnormal behavior detection mechanisms outputting abnormal behavior indications.
[0010] In some aspects, aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms may include: applying corresponding weights to the output of each of the one or more abnormal behavior detection mechanisms; and aggregating the weighted outputs of the one or more abnormal behavior detection mechanisms, and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications may include determining that a reportable or actionable abnormal behavior condition exists in response to the weighted output of the abnormal behavior detection mechanism exceeding a threshold.
[0011] In some aspects, detecting multiple indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms may include processing received V2X information through multiple rationality and consistency detectors, the multiple rationality and consistency detectors being configured to detect abnormal behavior conditions and output abnormal behavior indications to a detector selector; aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms may include passing the output of abnormal behavior indications from a selected subset of the multiple rationality and consistency detectors from the detector selector to the abnormal behavior detector; determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications may include determining by the abnormal behavior detector that there is a reportable or actionable abnormal behavior condition in response to the abnormal behavior indications output by the selected subset of the multiple rationality and consistency detectors, and the method may also include: determining a rate of abnormal behavior determinations; determining whether the rate of abnormal behavior determinations exceeds a maximum threshold or is less than a minimum threshold; deactivating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations exceeds a maximum threshold; and activating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations is less than a minimum threshold.
[0012] In some aspects, aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms may include determining a number of events classified as attacks or abnormal behavior indications output by each of the multiple abnormal behavior detection mechanisms within a time window or a set number of events, and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications may include determining that a reportable or actionable abnormal behavior condition exists in response to determining that the number of events classified as attacks or abnormal behavior indications output by any of the multiple abnormal behavior detection mechanisms within the time window or the set number of events exceeds a threshold.
[0013] Additional aspects include a V2X communication processing and management system including a memory and a processor configured to perform operations of any of the methods outlined above. Additional aspects may include a V2X communication processing and management 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 configured to cause a processor of the V2X communication processing and management system to perform various operations corresponding to any of the methods outlined above. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] 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.
[0015] Figure 1A is a system block diagram illustrating an example V2X communication system suitable for implementing various embodiments.
[0016] Figure 1B is a system block diagram illustrating an example decomposed base station architecture for a wireless communication system suitable for implementing any of the various embodiments.
[0017] Figure 2A is a component diagram of an example V2X communication processing and management system suitable for implementing various embodiments.
[0018] Figure 2B is a component block diagram illustrating the computing layer of an example vehicle V2X communication processing and management system in accordance with various embodiments.
[0019] Figure 3 is a block diagram illustrating components of a system-on-chip for use in a vehicle V2X communication processing and management system according to various embodiments.
[0020] Figure 4A is a conceptual block diagram illustrating functional elements of a V2X abnormal behavior detection system including multiple aggregators for untrustworthy and inconsistent detection for abnormal behavior determination according to various embodiments.
[0021] Figure 4B is a conceptual block diagram illustrating the functional elements of an aggregator method or module according to a first embodiment.
[0022] Figure 4C is an example of a method suitable for use in a Figure 4A A conceptual block diagram of the functional elements of an aggregator method or module used in a V2X abnormal behavior detection system as shown in FIG.
[0023] Figure 4D is an example of a method suitable for use in a Figure 4A A conceptual block diagram of the functional elements of an aggregator method or module used in a V2X abnormal behavior detection system as shown in FIG.
[0024] Figure 4E is an example of a method suitable for use in a Figure 4A A conceptual block diagram of the functional elements of an aggregator method or module used in a V2X abnormal behavior detection system as shown in FIG.
[0025] Figure 4Fis an example of a method suitable for use in a Figure 4A A conceptual block diagram of the functional elements of an aggregator method or module used in a V2X abnormal behavior detection system as shown in FIG.
[0026] Figure 4G is an example of a method suitable for use in a Figure 4A A conceptual block diagram of the functional elements of an aggregator method or module used in a V2X abnormal behavior detection system as shown in FIG.
[0027] Figure 5A is a process flow diagram of an example method 500a for detecting and taking action on V2X abnormal behavior conditions, according to various embodiments.
[0028] Figures 5B to 5G is a process flow diagram of example operations 500b - 500g that may be performed as part of a method 500a for aggregating untrustworthy and inconsistent detections for abnormal behavior determination, according to some embodiments. DETAILED DESCRIPTION
[0029] 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.
[0030] Various embodiments include methods and processors for a vehicle V2X communication processing and management system that implements one or more aggregators of abnormal behavior indications identified by any of a plurality of untrusted and inconsistent detection mechanisms, algorithms, modules, and / or detectors configured to identify evidence of events involving inconsistent or untrusted information received within or from V2X messages, vehicle sensors, network information, and the like. Various embodiments include an OR gate aggregator, a quorum-based aggregator, a majority-based aggregator, a majority of abnormal behavior V2X information aggregators, an adaptive aggregator, and combinations of two or more of such aggregators. Aggregating abnormal behavior indications generated by a plurality of untrusted and inconsistent detection mechanisms can improve identification of actual abnormal behavior conditions, avoid or reduce false alarms, and / or reduce generation of redundant abnormal behavior reports and / or responses to abnormal behavior reports. Various embodiments include different methods for aggregating abnormal behavior conditions and determining when a reportable or actionable abnormal behavior condition exists.
[0031] As used herein, the term "vehicle" generally refers to any of a car, truck, bus, train, boat, and any other type of mobile ADS-capable system that can access map data to perform autonomous or semi-autonomous functions.
[0032] The term "system on 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 and / or special 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.
[0033] 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.
[0034] Standards for vehicle-based communication systems and functionality are being developed in many parts of the world. Examples include standards developed by the Institute of Electrical and Electronics Engineers (IEEE) and the Society of Automotive Engineers (SAE) for use in North America, or standards developed in the European Telecommunications Standards Institute (ETSI) and the European Committee for Standardization (CEN) for use in Europe. For example, the IEEE 802.11p standard is the basis for dedicated short-range communications (DSRC) and ITS-G5 communication standards. IEEE 1609 is a higher-layer standard based on IEEE 802.11p. Cellular vehicle-to-everything (C-V2X) standards are competing standards developed under the support of the Third Generation Partnership Project. These standards are the basis for vehicle-based wireless communications and can be used to support smart 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 in various implementations.
[0035] 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.).
[0036] The processing of such messages in the sending and receiving vehicles may be performed by a processor or processing system of onboard equipment providing vehicle-to-everything (V2X) functionality (generally referred to herein as a "V2X communication processing and management system" or simply a "V2X processing system").
[0037] V2X systems and technologies hold great promise for improving traffic flow and vehicle safety by enabling vehicles to share information about their location, speed, direction of travel, braking, and other factors that may be useful for collision avoidance and other safety functions of other vehicles. One element of a V2X system is the ability of vehicles to broadcast V2X information in V2X messages such as Basic Safety Messages (BSM) or European Cooperative Awareness Messages (CAM), which other vehicles can receive and process to improve traffic safety. Vehicles can send V2X messages frequently, up to 20 times per second in some implementations. With most or all vehicles sending V2X information, receiving vehicles can receive information from other vehicles to control their own speed, direction, steering, path planning, etc. to avoid collisions and effectively and safely position vehicles relative to each other. In addition, vehicles equipped with V2X can improve traffic flow by safely reducing separation distances, lining up several vehicles together, and avoiding vehicle breakdowns.
[0038] In V2X communications, it is very important to detect and reduce inaccurate, corrupted, or intentionally falsified data. However, as more and more ITS participants are equipped to participate in such networks, the amount of potentially inaccurate, corrupted, or intentionally tampered information (sometimes referred to herein as "abnormal behavior") is large and exponentially growing. For example, an abnormal behavior ITS participant that is a car may send a V2X message that inaccurately states that the car has the size of a bus in order to deceive other nearby ITS participants to stay away from the car. As another example, an abnormal behavior ITS participant may inaccurately indicate that the width of the ITS participant occupies most of the width of the road so that other vehicles will not try to overtake the ITS participant. As another example, an abnormal behavior ITS participant (e.g., a scooter) may indicate that it is a pedestrian-type ITS participant in order to travel on the sidewalk without triggering a system alarm or warning (e.g., an alarm transmitted to the police). In addition, faulty vehicle sensors or processing errors may provide inaccurate V2X information. Such anomalous behaviour by ITS actors, whether due to equipment failure or deliberate attack, could reduce the effectiveness of the ITS and, in some cases, endanger human health and safety.
[0039] A variety of methods are known for detecting V2X messages that include (or may include) inaccurate or false information, as well as detecting sensor data and other vehicle data indicating abnormal behavior conditions that may result in the generation of an abnormal behavior report and / or require a safety response by the vehicle. Such methods may be implemented in a V2X processing system as an abnormal behavior detection mechanism, which may be implemented in software as an algorithm, in a software module of the V2X processing system, and / or in a circuit or dedicated processor (generally referred to herein as a "device"). Some abnormal behavior detection mechanisms may be configured to detect inconsistencies in information included in a V2X message. Some abnormal behavior detection mechanisms may be configured to detect when information in a V2X message conflicts with information known to the receiving V2X processor and / or the V2X communication system, such as location information that is significantly different from location information determined by a vehicle sensor and / or reliable data (e.g., map information contained in an onboard database). Some abnormal behavior detection mechanisms may be configured to detect reported vehicle size data that changes over time or differs from known values (e.g., in an onboard database). Some abnormal behavior detection mechanisms may be configured to detect substantial or erroneous drift of location information over time. Some anomalous behavior detection mechanisms may be configured to detect when the reported position (and possibly size) of a reporting vehicle indicates that two vehicles are spatially overlapping or that another vehicle is overlapping the own vehicle. Some methods may be configured to monitor velocity and acceleration information received in V2X messages from other vehicles to identify velocities that are inconsistent with current conditions, velocities that are inconsistent with reported accelerations from time to time, etc. using equations of motion. Some methods involve confirming whether sensor data (whether received from sensors inside the vehicle or from other vehicle sensor data included in the anomalous behavior report) is untrustworthy or inconsistent with normal or expected sensor data (e.g., outside the sensor's operating range or inconsistent with limitations imposed by the surrounding environment).
[0040] Each of the various methods for detecting abnormal behavior conditions in information generated by a vehicle or in abnormal behavior reports received can be implemented in a separate algorithm, software module, processing layer and / or processor or dedicated circuit that can independently identify or detect abnormal behavior conditions of a specific type or source. Some non-limiting examples of abnormal behavior detection mechanisms include: a mechanism for identifying erroneous, inconsistent or unreliable information related to the location of the vehicle, the location of other vehicles, road objects and features, and other location information that may be important for navigating the vehicle; a mechanism for identifying erroneous, inconsistent or unreliable information related to the speed of the vehicle or other vehicles; a mechanism for identifying when the location information of other vehicles overlaps with each other or with a self-aware vehicle; a mechanism for identifying when there is unacceptable drift in the location information of the vehicle or other vehicles; and a mechanism for identifying errors or inconsistencies in vehicle sensor data (e.g., conflicts with information received from other vehicles via V2X messages). For ease of reference, various different methods, software modules and / or processors / circuits are referred to herein as "rationality and consistency detectors", "abnormal behavior detection mechanisms" or simply "detectors". In various embodiments, the vehicle V2X system may include any number of such detectors or a plurality of such detectors, and thus such detectors may be referred to as detectors 1 to n, with any one detector being referred to as "detector i". Reference to methods, software, and / or components for identifying abnormal behavior conditions as "detectors" and referring to detectors by numbers or letters is not intended to limit the claims to a particular type or configuration for identifying abnormal behavior conditions or to a particular number of such detectors.
[0041] Identifying abnormal behavior conditions within a vehicle and / or ITS and reporting the condition in an abnormal behavior report that can be processed by other vehicles and abnormal behavior management agencies is important for minimizing the damage and safety challenges that such conditions may cause to all vehicles. However, sending too many abnormal behavior reports (especially redundant reports) by V2X-equipped vehicles may overwhelm the available bandwidth for sending and receiving abnormal behavior reports in the V2X communication channel. Similarly, the sending of a large number of abnormal behavior reports to solve minor problems that do not require action by other vehicles or abnormal behavior management agencies will not make good use of the limited bandwidth used for V2X communications, while making it more difficult for other vehicles to identify critical abnormal behavior reports among many minor abnormal behavior reports. For these reasons, it is necessary for V2X-equipped vehicles to aggregate abnormal behavior condition detections before confirming that reportable and / or actionable abnormal behavior conditions have been detected and generating one or several abnormal behavior reports rather than sending reports based on each detected abnormal behavior condition.
[0042] Various embodiments include methods for aggregating abnormal behavior indications from one or more abnormal behavior detection methods, modules, and / or devices of a vehicle and identifying or determining the presence of a reportable or actionable abnormal behavior condition based on the aggregation, and V2X communication processing and management systems that implement the method. Various embodiments of the method may enable a vehicle V2X system to identify abnormal behavior conditions in a reliable manner and take action on them while minimizing unnecessary and / or redundant abnormal behavior reports. In various embodiments, a vehicle V2X processing system may perform operations including receiving and / or detecting multiple indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms (i.e., methods, modules, and / or detector devices or circuits), and aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms to provide an aggregated output. The vehicle V2X processing system may use or process the aggregated output to determine whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indication. When a reportable or actionable abnormal behavior condition is identified, the V2X processing system may send an abnormal behavior report and / or take a response action in response to determining that an abnormal behavior condition exists.
[0043] Various types of aggregation methods can be implemented in various embodiments. In some embodiments, the V2X processing system can aggregate abnormal behavior indications output from abnormal behavior detection mechanisms by determining whether any of one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication. For example, conclusions or outputs from multiple abnormal behavior detection mechanisms (i.e., algorithms, modules, and / or devices) can be coupled to an "OR" gate used as an aggregator, so that in the event that any of the multiple abnormal behavior detection mechanisms generates or outputs an abnormal behavior indication, the aggregator module outputs the abnormal behavior indication or detection to an abnormal behavior condition determination module or function in the V2X processing system. In such embodiments, the V2X processing system can determine that there is an abnormal behavior condition that can be reported or acted upon in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication. Therefore, any abnormal behavior indication made by one or more of the multiple abnormal behavior detection mechanisms can cause the V2X processing system to determine that there is an abnormal behavior condition for which a report (i.e., an abnormal behavior report) should be sent and / or a response action should be taken.
[0044] In some embodiments, the V2X processing system may aggregate abnormal behavior indications generated or output from one or more abnormal behavior detection mechanisms by determining whether any of a selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication. For example, a conclusion or output from a selected subset of abnormal behavior detection mechanisms (i.e., algorithms, modules, and / or devices) may be coupled to an OR gate used as an aggregator, so that in the event that any of the selected abnormal behavior detection mechanisms generates or outputs an abnormal behavior indication, the aggregator module outputs the abnormal behavior indication or detection to an abnormal behavior condition determination module or function in the V2X processing system. Other abnormal behavior detection mechanisms may be aggregated according to some of the other embodiments disclosed herein, such as counting and comparing a threshold value (e.g., a majority number), or assigning weights according to the type of detection mechanism, wherein a weighted indication is provided to an abnormal behavior condition determination module or function. In such embodiments, the V2X processing system may determine that there is a reportable or actionable abnormal behavior condition in response to determining that at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication.
[0045] In some embodiments, the V2X processing system may aggregate abnormal behavior indications output from one or more abnormal behavior detection mechanisms and output (e.g., to an abnormal behavior condition determination module or function) the number of indications received from abnormal behavior detection mechanisms corresponding to a particular abnormal behavior condition. In such embodiments, the V2X processing system may determine that a reportable or actionable abnormal behavior condition exists in response to the number of abnormal behavior indications satisfying a threshold number. In some embodiments, comparing the number of abnormal behavior conditions to the threshold number may involve determining whether a majority of abnormal behavior detection mechanisms have output abnormal behavior indications.
[0046] In some embodiments, aggregating abnormal behavior indications by the V2X processing system may include applying corresponding weights to the output of each of one or more abnormal behavior detection mechanisms, and aggregating the weighted outputs of one or more abnormal behavior detection mechanisms. For example, the V2X processing system may assign weights to abnormal behavior indications from a particular detection mechanism based on the source or sensor used when detecting abnormal behavior. In such embodiments, the V2X processing system may determine that there is a reportable and / or actionable abnormal behavior condition in response to the weighted output of the abnormal behavior detection mechanism exceeding a threshold, which may be predefined or dependent on the operating environment or context. In some embodiments, the weight assigned to any given abnormal behavior detection mechanism or abnormal behavior indication may be preset or predetermined. In some embodiments, the weight assigned to any given abnormal behavior detection mechanism or abnormal behavior indication may be changed or updated by the V2X processing system according to various conditions, and may be changed or updated by an administrative agency (e.g., an abnormal behavior management agency) via an over-the-air update.
[0047] In some embodiments, the V2X processing system may be configured to adjust the sensitivity or detection threshold or various abnormal behavior detection mechanisms so as to achieve a certain level of sensitivity without generating an excessive number of abnormal behavior reports. In such embodiments, the V2X processing system may process abnormal behavior indications received from multiple rationality and consistency detectors, which are configured to detect abnormal behavior conditions using a detector selector, which is configured to select a specific detector whose output will be evaluated as part of identifying abnormal behavior conditions. In such embodiments, aggregating abnormal behavior indications may include the detector selector passing the output of abnormal behavior indications from a selected subset of multiple abnormal behavior detection mechanisms to an abnormal behavior detector, which is configured to determine whether there is a reportable or actionable abnormal behavior condition based on the indications from the selected subset of multiple rationality and consistency detectors. In such embodiments, the V2X processing system may also determine whether the rate of abnormal behavior determinations made by the system (e.g., the number of abnormal behavior determinations made per unit time) exceeds a maximum threshold rate or is less than a minimum threshold rate. The V2X processing system may then deactivate one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations exceeds a maximum threshold, or activate one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations is less than a minimum threshold. In this way, the V2X processing system may dynamically adjust the sensitivity of abnormal behavior detection so that the rate at which the system reports or acts upon abnormal behavior determinations remains within a predefined range between the maximum rate and the minimum rate.
[0048] In some embodiments, as part of aggregating outputs from multiple abnormal behavior detection mechanisms, the V2X processing system may determine the number of events that are classified as an attack or abnormal behavior indication in the output of each of the abnormal behavior detection mechanisms within a time window or a set number of events. For example, the abnormal behavior detection mechanism may be configured to indicate whether abnormal behavior has been detected periodically (e.g., once per second), such as indicating whether abnormal behavior has been detected or not detected in an intervention period or output cycle. In such a configuration, the V2X processing system may monitor the output from each of the multiple abnormal behavior detection mechanisms within a predetermined time window (e.g., 10 seconds, 30 seconds, one minute, etc.) or a set number of output cycles, thereby counting or otherwise tracking the number of outputs indicating abnormal behavior detection. In such embodiments, the V2X processing system may determine when there is a reportable or actionable abnormal behavior condition based on the count of positive abnormal behavior indications (i.e., indications of attacks or abnormal behavior) by any abnormal behavior detection mechanism within a time window. For example, when the number of events identified as indicative of an attack or abnormal behavior output by any of a plurality of abnormal behavior detection mechanisms within a time window or a set number of output cycles exceeds a threshold (such as a majority of the outputs during the time window or a set number of output cycles), the V2X processing system may determine that a reportable or actionable abnormal behavior condition exists.
[0049] In some embodiments, the specific type of one or more aggregators implemented in the V2X processing system may be changed or implemented based on various conditions, such as traffic volume, driving location, time of day, day of week, and other factors.
[0050] Various embodiments improve V2X communication processing and management systems and the functionality of V2X communications by aggregating abnormal behavior indications and determining whether to report abnormal behavior conditions or take action based on the aggregation, thereby reducing the sending of redundant, false, or low-criticality abnormal behavior reports, which can improve the use of limited V2X communication bandwidth while ensuring that important or critical abnormal behavior reports are sent and / or acted upon.
[0051] Figure 1A 1 is a system block diagram illustrating an example communication system 100 suitable for implementing various embodiments. The illustrated example 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.
[0052] 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 an ADS 104 including wireless communication capabilities. The base stations 110 may communicate with the core network 140 via a wired network 126. The communication system 100 may also include a roadside unit 112 that supports V2X communication with the vehicle 102 via a V2X wireless communication link 124.
[0053] Base station 110 is a network element that communicates with a wireless device (e.g., vehicle 102) 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, a base station subsystem serving the coverage area, or a combination thereof, depending on the context in which the term is used. 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, as referenced in the accompanying drawings. Figure 1B Decomposed networks, etc.
[0054] The roadside unit may be coupled to a remote computing device 132 hosting an abnormal behavior authority (abnormal behavior authority) via a wired network 128. The roadside unit 112 may communicate with an ITS- and V2X-equipped vehicle 102 via a V2X wireless communication link 124 to download information useful for safe operation, including receiving information about V2X abnormal behavior conditions that have been reported by other vehicles and recorded and reported by the abnormal behavior authority.
[0055] In some implementations and scenarios, a cellular wireless communication network (such as a 5G wireless communication network) supported by the base station 110 may also be used for V2X communication. For example, in some locations and implementations, the V2X communication processing and management system may use the 5G wireless communication network to send abnormal behavior reports to an abnormal behavior management agency and receive information about abnormal behavior conditions from the abnormal behavior management agency. To support such communications, the abnormal behavior management agency may be coupled to the core network via a communication link 127 (such as the Internet), and map data and confidence information may be communicated to the base station 110 via a wired communication link 126 (e.g., Ethernet, optical fiber, etc.) for downloading to the vehicle 102 via a cellular wireless communication link 122 (such as a 5G wireless communication link).
[0056] The cellular wireless communication link 122 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. The wireless communication link 122 and the wireless communication link 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)).
[0057] 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 V2X messages and abnormal behavior condition information. 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 vehicle ADS system 104) may be served by multiple RUs 172 simultaneously.
[0058] 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 these 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, these units 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.
[0059] 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.
[0060] 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 split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 170 may further 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.
[0061] 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).
[0062] The SMO framework 166 may be configured to support RAN deployment and provisioning 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 .
[0063] 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.
[0064] 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 of 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).
[0065] Figure 2A is a component diagram of an example vehicle V2X communication system 200 suitable for implementing various embodiments. Figures 1A to 2A , the system 200 may include a vehicle 102 including a vehicle V2X communication processing and management system 104. The V2X communication processing and management system 104 may communicate with various systems and devices such as an onboard network 210, an infotainment system 212, various sensors 214, various actuators 216, and a radio module 218 coupled to an antenna 219. The V2X communication processing and management system 104 may also communicate with a roadside unit 112, a cellular communication network base station 110, and other external devices.
[0066] The vehicle V2X communication processing and management 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 the vehicle-mounted display) and to the input module 207 to receive information from vehicle sensors and driver input.
[0067] The vehicle V2X communication processing and management 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, such as another V2X equipped vehicle 106, a roadside unit 112, and a base station 110, or another suitable network access point. The V2X antenna 219 and the radio module 218 may be configured to support a V2X communication network. In various embodiments, the vehicle V2X communication processing and management system 204 may receive information from a plurality of information sources, such as an onboard network 210, an infotainment system 212, various sensors 214, various actuators 216, and a radio module 218. The vehicle V2X communication processing and management system processor 205 may be configured to perform operations including receiving and detecting indications of abnormal behavior, and applying an aggregator to such detections before reporting or taking action on the determined abnormal behavior condition.
[0068] 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.
[0069] Figure 2B is a component block diagram illustrating elements of a vehicle ADS 230 configured according to various embodiments. Figures 1A to 2B The vehicle ADS 230 may include a vehicle V2X communication processing and management system 204 of a vehicle (eg, 102 ), which may be configured to communicate with a roadside unit 112 and / or a cellular network base station 110 .
[0070] The vehicle V2X communication processing and management system 204 may include one or more processors 205, memory 206, radio modules 218, and other components. The vehicle V2X communication processing and management system 204 may include multiple hardware, software, and / or firmware components that operate together to provide the functionality attributed herein to the processor 205.
[0071] 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 that is provided integrally (i.e., substantially non-removable) with the vehicle V2X communication processing and management system 204 and / or a removable storage device that is removably connected to the vehicle V2X communication processing and management 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.) One or both. 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 220, information received from a roadside unit 112, information received from a base station 110, and / or other information that enables the vehicle V2X communication processing and management system 204 to function as described herein.
[0072] The processor 205 may include one or more local processors that may be configured to provide information processing capabilities in the vehicle V2X communication processing and management system 204. As such, the processor 205 may include one or more of 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 the processor 205 is Figure 2A 205 is shown 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 within the vehicle and operating in coordination.
[0073] The vehicle V2X communication processing and management system 204 may be configured by machine-readable instructions 232, 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 an abnormal behavior detection mechanism module 234, an abnormal behavior detection indication aggregator module 236, an abnormal behavior condition determination module 238, and an abnormal behavior reporting module 240. In some embodiments, the instruction module may also include a V2X rationality and consistency detector module 242, a detector selector module 244, an abnormal behavior detection module 246, an abnormal behavior rate determination module 248, a V2X rationality and consistency detector deactivation module 250, a V2X rationality and consistency detector activation module 252, and an attack or abnormal behavior indication counting module 254.
[0074] In various embodiments, the processor 205 executing the abnormal behavior detection mechanism module 234 may detect multiple indications of abnormal V2X behavior via one or more abnormal behavior detection mechanisms. For example,
[0075] In various embodiments, the processor 205 executing the abnormal behavior detection indication aggregator 236 may aggregate abnormal behavior indications output from one or more abnormal behavior detection mechanisms. In some embodiments, the processor 205 executing the abnormal behavior detection indication aggregator 236 may determine whether any of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication. In some embodiments, the processor 205 executing the abnormal behavior detection indication aggregator 236 may determine whether any of the selected subsets of one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication. In some embodiments, the processor 205 executing the abnormal behavior detection indication aggregator 236 may aggregate abnormal behavior indications output from multiple abnormal behavior detection mechanisms. In some embodiments, the processor 205 executing the abnormal behavior detection indication aggregator 236 may apply corresponding weights to the output of each of the one or more abnormal behavior detection mechanisms, and aggregate the weighted outputs of the one or more abnormal behavior detection mechanisms. In some embodiments, the weight assigned to any given abnormal behavior detection mechanism or abnormal behavior indication may be preset or predetermined. In some embodiments, the weight assigned to any given abnormal behavior detection mechanism or abnormal behavior indication may be changed or updated by the V2X processing system based on various conditions, by an authority (e.g., an abnormal behavior authority) via over-the-air updates.
[0076] In some embodiments, the processor 205 executing the abnormal behavior detection indication aggregator 236 may pass the output of the abnormal behavior indications from the selected subset of the plurality of detectors from the detector selector 244 to the abnormal behavior detector module 246. In some embodiments, the processor 205 executing the abnormal behavior detection indication aggregator 236 may determine the number of events that are classified as attacks or abnormal behavior indications output by each of the plurality of abnormal behavior detection mechanisms within a time window or a set number of events.
[0077] In various embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indication. In some embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine the presence of a reportable or actionable abnormal behavior condition in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication. In some embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine the presence of a reportable or actionable abnormal behavior condition in response to determining that at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication. In some embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine the presence of a reportable or actionable abnormal behavior condition in response to a threshold number of abnormal behavior detection mechanisms outputting abnormal behavior indications. In some embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine the presence of a reportable or actionable abnormal behavior condition in response to a majority of abnormal behavior detection mechanisms outputting abnormal behavior indications. In some embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine that a reportable or actionable abnormal behavior condition exists in response to a weighted output of an abnormal behavior detection mechanism exceeding a threshold. In some embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine that a reportable or actionable abnormal behavior condition exists in response to abnormal behavior indications output by a selected subset of the plurality of rationality and consistency detectors 242. In some embodiments, the processor 205 executing the abnormal behavior condition determination module 238 may determine that a reportable or actionable abnormal behavior condition exists in response to determining that the number of events classified as attacks or abnormal behavior indications output by any of the plurality of abnormal behavior detection mechanisms within a time window or a set number of events exceeds a threshold.
[0078] In various embodiments, the processor 205 executing the abnormal behavior reporting module 240 may send an abnormal behavior report or take responsive action in response to determining that an abnormal behavior condition exists. For example,
[0079] In some embodiments, the processor 205 executing the V2X rationality and consistency detector module 242 may detect an abnormal behavior condition and output an abnormal behavior indication to the detector selector. For example,
[0080] In some embodiments, the processor 205 executing the detector selector module 244 may select the V2X rationality and consistency detectors or all subsets of the detector modules 242 for passing the abnormal behavior detection output to the abnormal behavior detector 246 .
[0081] In some embodiments, the processor 205 executing the abnormal behavior detector 246 may determine that a reportable or actionable abnormal behavior condition exists in response to abnormal behavior indications output by a selected subset of the plurality of rationality and consistency detectors.
[0082] In some embodiments, the processor 205 executing the abnormal behavior rate determination module 238 may determine the rate of abnormal behavior determination output by the abnormal behavior condition determination module 248 .
[0083] In some embodiments, the processor 205 executing the V2X rationality and consistency detector disabling module 250 may disable one or more of the sensitive rationality and consistency detectors 242 in response to determining that the rate of abnormal behavior determinations made by the abnormal behavior condition determination module 238 exceeds a maximum threshold (X). For example,
[0084] In some embodiments, the processor 205 executing the V2X rationality and consistency detector activation module 252 may activate one or more sensitive rationality and consistency detectors 242 in response to determining that the rate of abnormal behavior determinations made by the abnormal behavior condition determination module 238 is less than a minimum threshold (Y).
[0085] In some embodiments, the processor 205 executing the attack or abnormal behavior indicator counting module 254 can determine the number of events classified as attacks or abnormal behavior indicators output by each of the plurality of abnormal behavior detection mechanisms within a time window or a set number of events.
[0086] Processor 205 may execute modules 232 - 254 and / or other modules via software, hardware, firmware, some combination of software, hardware, and / or firmware, and / or other mechanisms for configuring processing capabilities on processor 205 .
[0087] The description of the functionality provided by the different modules 232-244 is for illustrative purposes and is not intended to be limiting, as any of the modules 232-244 may provide more or less functionality than that described. For example, one or more of the modules 232-244 may be eliminated, and some or all of their functionality may be provided by other modules in the modules 232-244. As another example, the processor 205 may execute one or more additional modules that may perform some or all of the functionality attributed below to one of the modules 232-244.
[0088] Figure 3 An example SOC architecture of a processing device system on a chip (SOC) 300 suitable for implementing various embodiments in a vehicle is illustrated. Figures 1A to 3 , the processing device SOC 300 may be included in a vehicle V2X processing system for use in the vehicle 102 .
[0089] The processing device SOC 300 may include a plurality of 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., vector coprocessors) connected to one or more of the heterogeneous processors 303, 304, 306, 307, 308, 317.
[0090] 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. The graphics processor 306 may be a graphics processing unit (GPU).
[0091] The processing device SOC 300 may include analog and custom circuits 314 for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations for performing V2X communications. For example, such specialized operations may include identifying untrustworthy and / or inconsistent information in a V2X message that may indicate abnormal behavior by another vehicle or in another vehicle sensor or internal system (e.g., sensor data that conflicts with information in a received V2X message), and untrustworthy and / or inconsistent vehicle sensor data that may indicate abnormal behavior in a vehicle sensor or internal system.
[0092] The processing device SOC 300 may also 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 vehicle V2X processing system (e.g., 104, 204).
[0093] The processing device SOC 300 also includes a dedicated circuit for camera actuation and management (CAM) 305, which includes, provides, controls and / or manages the operation of one or more cameras (e.g., main camera, network 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 clock or an internal clock.
[0094] In some embodiments, the image and object recognition processor 306 may be configured with processor executable instructions and / or dedicated hardware that is configured to perform 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.
[0095] System components and resources 316, analog and custom circuits 314, and / or CAM 305 may include circuits that interface with peripheral devices such as cameras, radars, lidars, 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 interconnects / bus modules 324, which may include reconfigurable logic gate arrays and / or implement bus architectures (e.g., CoreConnect, AMBA, etc.). Communications may be provided by advanced interconnects, such as high-performance networks on chip (NoCs).
[0096] 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.).
[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, global positioning system (GPS) receivers, communication circuits (e.g., WLAN, WiFi, etc.) and other well-known components of modern electronic devices.
[0098] FIG. 4A to FIG. 4G The present invention is a processing module and process flow diagram illustrating different systems and processes for aggregating abnormal behavior indications and using the aggregated abnormal behavior indications to determine whether there is a reportable or actionable abnormal behavior condition before sending an abnormal behavior report and / or determining that action should be taken on one or more abnormal behavior indications.
[0099] Figure 4A is a functional block diagram of a V2X aggregator system 400 for detecting V2X abnormal behavior events, aggregating V2X abnormal behavior indications, and transmitting / taking action on the determined abnormal behavior conditions, according to various embodiments. Figures 1A to 4AIn various embodiments, the V2X processing system may receive V2X information 402 via the BSM and other V2X messages from other vehicles and roadside units, such as road conditions (e.g., traffic conditions, accident notifications, etc.), the location, speed, and direction of other vehicles. While such information is useful to and used by V2X safety applications 426, the information may also be processed by a plurality of rationality and consistency detectors 404, which may be comprised of a plurality of detector mechanisms, which are illustrated as "detector 1" 406, "detector 2" 408, "detector i" 410, and "detector n" 412. Each of the plurality of detector mechanisms 406-412 may be configured to evaluate a particular type of information from a particular source, and to identify or detect abnormal behavior, errors, or inconsistencies, such as by comparing the received information with data obtained from a particular vehicle information source (including sensor data and data stored in memory).
[0100] The abnormal behavior condition determination module 414 can use multiple aggregators 416, 418, 420, 422 that implement different aggregation methods (including the aggregation methods of various embodiments described herein) to determine whether one or more abnormal behavior conditions exist. Additionally, the abnormal behavior condition determination module 414 can use the outputs from the multiple aggregators 416, 418, 420, 422 to make different types of abnormal behavior determinations 424 that are consistent with a specific abnormal behavior detection mechanism (e.g., one or more of the detector mechanisms 406-412) and the specific aggregator outputs used in making the abnormal behavior determination 424.
[0101] In some embodiments, a plurality of aggregators 416-422 may receive abnormal behavior indications from respective ones of detector mechanisms 406-412 and aggregate these abnormal behavior indications to make abnormal behavior determinations 424. In such embodiments, there may be a one-to-one correlation between a given aggregator and a corresponding detector mechanism. Thus, the aggregation method used by a given aggregator may be appropriate for the type of abnormal behavior detected, the information source used, or the accuracy or reliability of the corresponding detection mechanism.
[0102] In some embodiments, the outputs from the various detector mechanisms 406-412 may be processed by one or more aggregators 416, 418, 420, 422, and the abnormal behavior condition determination module 414414 may use the outputs from the plurality of aggregators 416, 418, 420, 422 coupled to the detector mechanisms 406-412 to make an abnormal behavior determination 424. For example, Figure 4AAs shown, "Aggregator 1" 416 may receive and process abnormal behavior indications output by all detector mechanisms 406-412, while "Aggregator 2" 418 may receive and process abnormal behavior indications output by "Detector 1" 406 and "Detector n" 412. Different aggregators 416-422 may process inputs from multiple detector mechanisms 406-412 using different aggregation methods appropriate to the type of abnormal behavior indications received and processed.
[0103] The abnormal behavior condition determination module 414 can output different types of abnormal behavior determinations 424 based on the outputs processed from the various detectors 406-412 and the various aggregators 416-422 and the corresponding decision criteria for identifying or confirming abnormal behavior conditions. As an example, consider the case of processing information output from an emergency electronic brake light (EEBL) application, which is one of the V2X safety applications. The EEBL application enables a vehicle to broadcast self-generated emergency braking events to surrounding vehicles via V2X messages. The detector (e.g., one of 406-412) can compare the information received in the EEBL V2X message with other vehicle sensor information such as from radar, lidar, and cameras to check whether the remote vehicle transmitting such a V2X message exhibits a high deceleration consistent with emergency braking. Additionally, the detector can determine whether the braking condition of the remote vehicle is related to its vehicle (i.e., a "self-aware vehicle"), such as by determining whether the remote vehicle is in the same lane as the self-aware vehicle and within a specific safety distance (such as 100 meters). Thus, in this example, the abnormal behavior condition determination module 414 that makes an abnormal behavior determination based on information related to an EEBL event may rely on acceleration and position information to determine whether to issue an alert by initiating an abnormal behavior determination 424. Thus, in the case of an EEBL event, the abnormal behavior condition determination module 414 may use outputs from an acceleration-related aggregator and a position-related aggregator, such as Figure 4C shown.
[0104] The abnormal behavior determination 424 may be provided to a V2X safety application 426 for action. In some cases, the V2X safety application 426 may initiate a safety alert 428, such as by sending an abnormal behavior report, generating an internal alert for the driver. In some cases, the V2X safety application 426 may take action to ensure safe operation of the vehicle, such as ignoring V2X information determined to be erroneous, or taking action to avoid a dangerous situation in response to determining that the determined abnormal behavior requires a safety action.
[0105] Figure 4BAn example implementation of a V2X aggregator system 430a for aggregating V2X abnormal behavior indications and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications is illustrated. Figures 1A to 4B In some embodiments, one or more of the abnormal behavior detection mechanisms 406-412 may function as or be similar to an OR gate 432. In such embodiments, one or more of the abnormal behavior detection mechanisms 406-412 may be configured to provide an abnormal behavior indication (e.g., an indication that abnormal behavior has been detected) to the OR gate 432, which may be configured to determine that an abnormal behavior condition exists and initiate an abnormal behavior determination 424 in response to any of the connected abnormal behavior detection mechanisms 406-412 providing an abnormal behavior indication.
[0106] like Figure 4B As shown, using the “OR” function as an integrator can be applied to some but not all of the various abnormal behavior detection mechanisms 406-412. Figures 1A to 4C , Figure 4C An embodiment of a V2X aggregator system 430b for aggregating V2X abnormal behavior indications is illustrated, where some abnormal behavior detection mechanisms (e.g., detectors 406, 408) are aggregated in an OR gate 432, while other abnormal behavior detection mechanisms (e.g., detectors 410, 412) are aggregated using other types of aggregation 436 (including aggregators described herein). For example, the OR gate 432 aggregator can aggregate abnormal behavior indications from location-related detectors 434 (e.g., detectors 406, 408) that identify location-related errors or abnormal behaviors (e.g., untrustworthy and / or inconsistent V2X information), and output an abnormal behavior determination 424 if any of such detectors identifies an abnormal behavior condition.
[0107] Figure 4D Another embodiment of a V2X aggregator system 440 is illustrated for aggregating V2X abnormal behavior indications and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregation of abnormal behavior indications across multiple abnormal behavior detection mechanisms (shown as detectors 406-412). Figures 1A to 4DIn some embodiments, the aggregation of V2X abnormal behavior indications may be accomplished by an aggregator 442 (shown as a "quorum aggregator") that receives abnormal behavior indication outputs from a plurality of abnormal behavior detection mechanisms 406-412 and determines in a determination block 444 whether a predefined threshold number or quorum threshold of detectors are providing or being provided with the same or corroborated abnormal behavior indications, thereby generating an output 446 to the V2X processing equipment that determines that the detected event constitutes abnormal behavior. In some embodiments, the quorum aggregator 442 may receive abnormal behavior indications from the various abnormal behavior detection mechanisms or detectors 406-412, track the received abnormal behavior indications to identify the events reported by the indications, and effectively count the number of indications associated with the same event within a predefined time interval (e.g., one second, 10 seconds, etc.), and then compare the count to the quorum threshold in the determination block 444.
[0108] The quorum threshold against which the number of abnormal behavior indications is compared may be any preset value greater than one and may be dynamically adjusted based on operating conditions, such as the rate at which the behavior events are detected. In addition, the quorum aggregator 442 may be coupled to some but not all abnormal behavior detection mechanisms or detectors 406-412 within the vehicle V2X system, in which case the aggregated number of abnormal behavior indications compared to the quorum threshold may be a subset of the mechanisms or detectors. For example, the quorum aggregator 442 may be coupled to a subset of the mechanisms or detectors that are not coupled to the vehicle V2X system, such as Figure 4C Those abnormal behavior detection mechanisms or detectors 406-412 of the "OR" aggregator 432 are shown.
[0109] Figure 4E Another embodiment of a V2X aggregator system 450 for aggregating V2X abnormal behavior indications and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications is illustrated. Figures 1A to 4EIn some embodiments, weighted aggregation of abnormal behavior indications from multiple abnormal behavior detection mechanisms or detectors 406-412 may be performed by a majority aggregator 456. In such embodiments, the abnormal behavior indications output by each of the abnormal behavior detection mechanisms or detectors 406-412 may be assigned respective weights 451, 452, 453, 454, and the weighted indications may be aggregated by a majority aggregator 458. In determination block 458, the majority aggregator 458 may compare the result of aggregating the weighted indications to a threshold. In response to determining that the weighted indications meet or exceed the threshold, the majority aggregator 458 may output an abnormal behavior determination 446 to the V2X processing equipment, and may output nothing or output a determination 448 that the event is not abnormal behavior. In some embodiments, the weights 451-454 applied to the abnormal behavior indications output by the multiple abnormal behavior detection mechanisms or detectors 406-412 may be predetermined, such as by an abnormal behavior management authority during an over-the-air update or provisioning. In some embodiments, the weights 451-454 applied to the abnormal behavior indications output by multiple abnormal behavior detection mechanisms or detectors 406-412 may be dynamically determined or adjusted, such as by an abnormal behavior management mechanism during over-the-air updates or deployments, by vehicle V2X processing equipment based on the rate of determined abnormal behavior conditions, and other considerations.
[0110] Figure 4F Another embodiment 470 for aggregating V2X abnormal behavior indications and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications is illustrated. Figures 1A to 4F In some embodiments, multiple rationality and consistency detectors 404 may provide multiple outputs to an aggregator system 471, which may include a detector selector 472, an abnormal behavior detector 473, an abnormal behavior rate counter 474, comparators 475, 476, 477 for comparing the abnormal behavior rate with a maximum threshold and a minimum threshold, a circuit or algorithm 478 configured to deactivate a sensitive detector in the detector selector 472 when the abnormal behavior rate exceeds the maximum threshold, and a circuit or algorithm 479 configured to activate a sensitive detector in the detector selector 472 when the abnormal behavior rate is less than the maximum threshold. Such elements of the aggregator system 471 may be implemented in software as an algorithm, a software module, a dedicated circuit, and / or a combination of circuits (e.g., a dedicated processor) and software. Such an aggregator 471 enables the vehicle V2X processing equipment to change the rationality and consistency detector 404 used to detect abnormal behavior conditions so as to maintain the rate of abnormal behavior event detection between the maximum threshold rate and the minimum threshold rate.
[0111] In such embodiments, the vehicle V2X processing equipment may include multiple rationality and consistency detectors 404 (e.g., detection mechanisms, software modules and / or devices) that process information received from V2X communications from other vehicles, roadside units, etc., vehicle sensors, information obtained from on-board memory (e.g., in a database containing map information, information about other types of vehicles, etc.), and other sources to identify inconsistent reports, unreliable results (e.g., information that conflicts with known information or physics), and other indications of possible abnormal behavior within the vehicle, other vehicles, or the smart highway system.
[0112] Outputs from multiple rationality and consistency detectors 404 may be selected or filtered by a detector selector 472, which may be configured to pass abnormal behavior indications from selected rationality and consistency detectors from multiple rationality and consistency detectors 404 to abnormal behavior detector 473. The rationality and consistency detectors 404 passed to abnormal behavior detector 473 may be adjusted by inputs from modules or devices for deactivating sensitive detectors 478 and activating sensitive detectors 479.
[0113] Thus, some, but not necessarily all, abnormal behavior indications output from the rationality and consistency detector 404 may be received by the abnormal behavior detector 473. In turn, the abnormal behavior detector 473 may use the received abnormal behavior indications to make an abnormal behavior determination 424 (e.g., whether an abnormal behavior condition exists in the event that triggers the abnormal behavior indication). The abnormal behavior determination 424 may be passed to and processed by the V2X processing equipment. Additionally, the abnormal behavior rate counter 474 may record or count the abnormal behavior determinations 424 and, based thereon, determine a rate of abnormal behavior determinations made by the aggregator system 471 per unit of time (e.g., per minute, per hour, etc.).
[0114] As part of determining the rate of abnormal behavior determination, the abnormal behavior rate counter 474 or a separate comparison module 475, 476, 477 can determine whether the rate of abnormal behavior determination exceeds a maximum threshold (determination box 475) or is less than a minimum threshold (determination box 476). Based on this comparison, the aggregator system 471 can deactivate one or more sensitive detectors (478) in the event that the rate of abnormal behavior determination exceeds the maximum threshold, or activate one or more sensitive detectors (479) in the event that the rate of abnormal behavior determination is less than the minimum threshold. In some embodiments, the rationality and consistency detectors 404 that are activated or deactivated can be predetermined, such as in an order or ranking based on the accuracy and / or precision of the associated sensors or information sources, and / or the importance or criticality of the type of information addressed by the detector to vehicle safety. In this way, the aggregator system 471 can dynamically adjust the rationality and consistency detectors 404 that are monitored for detecting abnormal behavior conditions in response to environmental and vehicle sensors.
[0115] Figure 4G Another embodiment 460 for aggregating V2X abnormal behavior indications and determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications is illustrated. Figures 1A to 4G In some embodiments, abnormal behavior indications output by multiple abnormal behavior condition detectors 406-412 are received and monitored by a majority abnormal behavior V2X information aggregator 462, which is configured to count or otherwise determine the number of event outputs per unit time (e.g., every five event outputs as illustrated) by each detector (or a selected subset) that are classified as or indicative of an attack (or other abnormal behavior).
[0116] In some embodiments, the majority abnormal behavior V2X information aggregator 462 can determine (e.g., in determination box 468) to a determination module or device 468 whether the majority of events output by a given detector per unit time are classified as attacks (or other abnormal behavior) against any one of the detectors 406-412, which determines whether, and accordingly outputs to the V2X processing system a determination 446 that the event is an abnormal behavior condition or a determination 448 that the event is not an abnormal behavior condition.
[0117] In some embodiments, the majority of unusual behavior V2X information aggregator 462 may determine (e.g., in determination block 468) whether the majority of events output by the unusual behavior condition detectors 406-412 are classified as attacks (or other unusual behavior) per unit time, and accordingly output to the V2X processing system a determination 446 that the event is an unusual behavior condition or a determination 448 that the event is not an unusual behavior condition. In some embodiments, the determination module or device 468 that determines whether the majority of events from a given detector are classified as attacks may be separate from the output from the majority of unusual behavior V2X information aggregator 462 and make the determination based on that output.
[0118] Figure 5A is a process flow diagram of an example method 500a that may be executed by a processor of a vehicle's V2X communication processing and management system (e.g., 104) according to various embodiments, the example method being used to aggregate abnormal behavior indications received from multiple abnormal behavior detection mechanisms (i.e., abnormal behavior detection methods, modules, and / or devices) and determine reportable and / or actionable abnormal behavior conditions based on the aggregated abnormal behavior indications. Figure 5B 5H is a process flow diagram of example operations 500b-500h that may be performed as part of aggregating abnormal behavior indications received from multiple abnormal behavior detection mechanisms as described, according to some embodiments. Figure 1A to Figure 5G , method 500a and operations 500b-500h may be performed by a processor of a vehicle V2X communication processing and management 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 elements and software elements (collectively referred to as "V2X processors").
[0119] In block 502, a V2X processor may perform operations including detecting multiple indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms. The V2X processing system may be coupled to multiple vehicle sensors (e.g., cameras, radars, LIDARs, GPS receivers, etc.) and configured to process information received in V2X messages (e.g., BSMs), and include software-implemented algorithms or modules and / or devices configured to analyze information obtained from sensors and V2X messages to identify inconsistent and / or untrustworthy information indicating an abnormal behavior condition. Such software-implemented algorithms or modules and / or devices may be configured as an abnormal behavior detection mechanism that outputs an abnormal behavior indication when an inconsistent or untrustworthy condition is detected that may be due to a V2X abnormal behavior condition (e.g., a deliberate attack or a sensor failure). The means for performing the operations of block 502 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior detection mechanism module 234.
[0120] In box 504, the V2X processor may perform operations including aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms. Aggregating abnormal behavior indications from multiple detectors (e.g., 406-412) may involve selecting or identifying abnormal behavior indications from one or selected abnormal behavior detection mechanisms for use in determining whether an abnormal behavior condition exists or is detected. In some embodiments, as part of the operations in box 504, multiple aggregators may receive abnormal behavior inputs from one or more of the detector mechanisms and apply an aggregation method of abnormal behavior indications suitable for the type of detector mechanism coupled to each aggregator or processed by each aggregator. In some embodiments, each of the multiple aggregators may be coupled to a corresponding one of the multiple detector mechanisms and configured to aggregate outputs from a corresponding one of the multiple detector mechanisms.
[0121] Aggregating abnormal behavior indications and using the results of such aggregation to determine whether an abnormal behavior condition exists can avoid false detections and / or the generation of redundant reports of abnormal behavior conditions. Based on the different types of aggregation used in the various embodiments described herein, the output of the abnormal behavior detection mechanism can be selected, weighted, analyzed, or otherwise considered over time to support the determination of whether there is a reportable and / or actionable abnormal behavior condition. The means for performing the operations of box 504 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior detection indication aggregator module 236.
[0122] In box 506, the V2X processor may perform operations including determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indication. In some embodiments, the V2X processor may determine that an abnormal behavior condition exists in response to any one of all or a selected number of abnormal behavior detection mechanisms outputting an aggregation of abnormal behavior indications. In some embodiments, the V2X processor may determine that an abnormal behavior condition exists in response to one or more aggregators determining that the number of abnormal behavior detection mechanisms outputting abnormal behavior indications meets or exceeds a threshold (such as a majority or a quorum of multiple abnormal behavior detection mechanisms). In some embodiments, the V2X processor may determine that an abnormal behavior condition exists in response to one or more aggregators indicating that one or more of the abnormal behavior indicators determine that an event is classified as an attack (or other abnormal behavior) within a unit time. The component for performing the operation of box 506 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior condition determination module 238.
[0123] In box 508, the V2X processor may perform operations including sending an abnormal behavior report or taking a response action in response to determining that an abnormal behavior condition exists. For example, the V2X processor may generate an abnormal behavior report including information about the detected abnormal behavior and initiate the sending of the generated abnormal behavior report. As another example, the V2X processor may take action in response to the detected abnormal behavior condition, such as ignoring erroneous or malicious information, taking actions to prevent erroneous or malicious information, or initiating a driving response to ensure safe operation of the vehicle in view of the erroneous or malicious information from the abnormal behavior condition. The component for performing the operation of box 508 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior reporting module 240.
[0124] Figures 5B to 5G 5 is a process flow diagram of example operations 500b-500h according to some embodiments, which operations may be performed as part of aggregating abnormal behavior indications received from multiple abnormal behavior detection agencies and determining reportable and / or actionable abnormal behavior conditions based on the aggregated abnormal behavior indications. Operations 500b-500h may be performed by a processor (e.g., 205) of a vehicle V2X communication processing and management system 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 elements and software elements (collectively, "V2X processors").
[0125] Figure 5BOperations 500b that may be performed by a V2X processor for aggregating abnormal behavior indications are illustrated in accordance with some embodiments. Figures 1A to 5B , after the operations in box 502, the V2X processor may perform operations including determining in box 510 whether any of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication as part of aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms. For example, as part of aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms, the V2X processor may receive inputs from all abnormal behavior detection mechanisms and determine, in response to any abnormal behavior indication, that the abnormal behavior indication should be processed by the abnormal behavior detector. In this regard, the aggregator may act as an "OR" gate, thereby providing an output to the abnormal behavior detector in response to any positive indication of abnormal behavior detection. The component for performing the operations of box 510 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior detection indication aggregator module 236.
[0126] In block 512, the V2X processor may perform operations including determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication as part of determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indication. For example, the abnormal behavior detector may output a determination that a reportable or actionable abnormal behavior condition exists to the rest of the V2X processing system based on the output from the aggregator in block 510. The means for performing the operations of block 512 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) executing an abnormal behavior condition determination module 238.
[0127] Following the operations in block 512 , the V2X processor may perform the operations in block 508 as described.
[0128] Figure 5C Operations 500c that may be performed by a V2X processor for aggregating abnormal behavior indications are illustrated in accordance with some embodiments. Figures 1A to 5C, after the operation in box 502, the V2X processor may perform operations including determining in box 514 whether any of the selected subset of one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication as part of aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms. For example, as part of aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms, the V2X processor may receive input from a selected subset of abnormal behavior detection mechanisms, and determine that the abnormal behavior indication should be processed by the abnormal behavior detector in response to any abnormal behavior indication from the selected subset of abnormal behavior detection mechanisms, while aggregating other abnormal behavior indications from other abnormal behavior detection mechanisms using other aggregation methods. In this regard, one or more aggregators may be used as an "OR" gate for processing outputs from the selected subset of abnormal behavior detection mechanisms, thereby providing an output to the abnormal behavior detector in response to any positive indication of abnormal behavior detection from the selected subset of abnormal behavior detection mechanisms. Such an embodiment may be used to aggregate several abnormal behavior detection mechanisms that will detect abnormal behavior with significant safety hazards, such as abnormal behavior related to determining or tracking the location and navigation of a vehicle. The means for performing the operations of block 514 may include a processor (eg, 205 , 300 ) of a vehicle V2X communication processing and management system (eg, 104 , 204 ) executing an abnormal behavior detection indication aggregator module 236 .
[0129] In block 516, the V2X processor may perform operations including determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication as part of determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indication. In such embodiments, the abnormal behavior detector may output a determination that a reportable or actionable abnormal behavior condition exists to the rest of the V2X processing system based on outputs from the OR aggregator in block 514 or from other aggregators. The means for performing the operations of block 512 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) executing an abnormal behavior condition determination module 238.
[0130] Following the operations in block 516 , the V2X processor may perform the operations in block 508 as described.
[0131] Figure 5D Operations 500d that may be performed by a V2X processor for aggregating abnormal behavior indications are illustrated in accordance with some embodiments. FIG. 1A to FIG. 5D, after the operations in box 502, the V2X processor may perform operations including aggregating abnormal behavior indications output from multiple abnormal behavior detection mechanisms in box 518 as part of aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms. As part of this aggregation, the V2X processor may total the number of abnormal behavior detection mechanisms that output positive abnormal behavior indications. This total may be calculated over a period of time (such as one second, 10 seconds, or several minutes), such as when a single event is detected by multiple abnormal behavior detection mechanisms. The component for performing the operations of box 5xx may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior detection indication aggregator module 236.
[0132] In block 520, the V2X processor may perform operations including determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of abnormal behavior detection mechanisms outputting abnormal behavior indications. In some embodiments, the threshold number may be any predefined number greater than one, so that some confirmation or verification is required in multiple abnormal behavior detection mechanisms before the V2X processor determines that a reportable or actionable abnormal behavior condition exists. In some embodiments, the threshold number may be set to more than half of the number of abnormal behavior detection mechanisms active in the V2X processing system, so that a majority of abnormal behavior detection conditions are required to have detected an output behavior indication before the system determines that a reportable or actionable abnormal behavior condition exists. In some embodiments, the threshold number may be set to a number predefined as a quorum, such as more than half of the number of abnormal behavior detection mechanisms active in the V2X processing system, so that a quorum of abnormal behavior detection conditions are required to have detected an output behavior indication before the system determines that a reportable or actionable abnormal behavior condition exists. In some embodiments, the threshold number may be set to a number substantially greater than half the number of abnormal behavior detection mechanisms active in the V2X processing system, thereby requiring that a majority of abnormal behavior detection conditions have detected an output behavior indication before the system determines that a reportable or actionable abnormal behavior condition exists. Such embodiments may prevent false determinations of reportable or actionable abnormal behavior conditions based on one or more abnormal behavior detection mechanisms that may be subject to errors or abnormal behavior of their own. The means for performing the operations of block 520 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) executing an abnormal behavior condition determination module 238.
[0133] Following the operations in block 520 , the V2X processor may perform the operations in block 508 as described.
[0134] Figure 5E Operations 500e that may be performed by a V2X processor to determine that an abnormal behavior condition exists based on a weighted aggregation of abnormal behavior indications are illustrated in accordance with some embodiments. Figures 1A to 5E , after the operations in box 502, the V2X processor may perform operations including applying corresponding weights to the outputs of each of the one or more abnormal behavior detection mechanisms in box 522. The weights applied to each of the outputs of the abnormal behavior detection mechanisms may depend on a number of factors, including the criticality of the abnormal behavior detected by the particular mechanism, the accuracy or sensitivity of the particular detector mechanism, and / or the reliability of the information used by the particular detection mechanism. For example, an abnormal behavior indication output from an abnormal behavior detection mechanism configured to identify errors, inconsistencies, or other abnormal behaviors related to safety-critical information (e.g., vehicle position or autonomous driving control) may be given a greater weight than an abnormal behavior indication output from an abnormal behavior detection mechanism configured to identify errors or inconsistencies in less critical information. Such waiting for abnormal behavior indications may enable the V2X processing system to more reliably identify reportable or actionable abnormal behavior conditions from many concurrent abnormal behavior indications that may be of less importance or criticality to vehicle safety. The means for performing the operations of box 522 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) executing the abnormal behavior detection indication aggregator module 236.
[0135] In box 524, the V2X processor may perform operations including aggregating weighted outputs of one or more abnormal behavior detection mechanisms as part of aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms. For example, the V2X processor may add weighted abnormal behavior indications to obtain a total weighted indication value. As another example, the V2X processor may determine an average weighted abnormal behavior indication by taking the average of all weighted abnormal behavior indications per unit time. Other processing of weighted abnormal behavior indications may be used in box 524. A component for performing the operations of box 524 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior detection indication aggregator module 236.
[0136] In box 526, the V2X processor may perform operations including determining that a reportable or actionable abnormal behavior condition exists in response to the weighted output of the abnormal behavior detection mechanism exceeding a threshold. In some embodiments, the threshold may be any preset value that may be set by a V2X system provider, a vehicle manufacturer, a smart highway system management, an abnormal behavior management agency, or other management agency. In some embodiments, the threshold may be dynamically set by the V2X system processor in response to an abnormal behavior determination and / or a rate of abnormal behavior determination, or by an external management agency (e.g., an abnormal behavior management agency) such as via an over-the-air system update. The component for performing the operations of box 526 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior condition determination module 238.
[0137] Following the operations in block 526 , the V2X processor may perform the operations in block 508 as described.
[0138] Fig. 5F Operations 500f that may be performed by a V2X processor to dynamically adjust the sensitivity of a V2X abnormal behavior detection capability according to some embodiments are illustrated. Figures 1A to 5F In block 528, the V2X processor may perform operations including processing the received V2X information (including sensor data) through a plurality of rationality and consistency detectors configured to detect abnormal behavior conditions and output abnormal behavior indications to a detector selector (e.g., 472). In some embodiments, such operations may be performed as part of detecting a plurality of indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms as described in block 502. The means for performing the operations of block 528 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) executing a V2X rationality and consistency detector module 242.
[0139] In block 530, the V2X processor may perform operations including passing the output of abnormal behavior indications from a selected subset of a plurality of abnormal behavior detection mechanisms from a detector selector (e.g., 472) to an abnormal behavior detector (e.g., 473) as part of aggregating abnormal behavior indications output from one or more abnormal behavior detection mechanisms. In such operations, the detector selector may act as a filter, thereby accepting for processing abnormal behavior indications output from a particular rationality and consistency detector among a plurality of rationality and consistency detectors (e.g., 404) without passing abnormal behavior indications from non-selected detectors. In such embodiments, the particular rationality and consistency detector accepted for processing may be adjusted in response to various conditions, including in response to the rate at which abnormal behavior determinations are made as described. For example, upon initial activation, abnormal behavior indication outputs from all or a predetermined subset of rationality and consistency detectors may be passed to an abnormal behavior detector (e.g., 473), but over time, the filter settings of the detector selector may be adjusted so that outputs from one or more selected rationality and consistency detectors among the rationality and consistency detectors will not be passed to the abnormal behavior detector. The means for performing the operations of block 530 may include a processor (eg, 205 , 300 ) of a vehicle V2X communication processing and management system (eg, 104 , 204 ) executing the detector selector module 244 .
[0140] In box 532, the V2X processor may perform operations including determining by an abnormal behavior detector that there is a reportable or actionable abnormal behavior condition in response to abnormal behavior indications output by a selected subset of multiple rationality and consistency detectors. In some embodiments, such operations may be performed as part of determining whether there is a reportable or actionable abnormal behavior condition based on aggregated abnormal behavior indications. The abnormal behavior detector 473 may use various methods to identify reportable or actionable abnormal behavior conditions, including the methods described herein, such as reporting detectors based on a threshold number (e.g., a majority of a quorum), or a weighted aggregation of the behavior indications output by a detector selector (e.g., 472). The component for performing the operations of box 526 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior detector module 246.
[0141] In block 508, the V2X processor may perform operations as described including reporting abnormal behavior by sending an abnormal behavior report and / or taking one or more safety actions in response to determining that a reportable or actionable abnormal behavior condition exists. The means for performing the operations of block 508 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) executing an abnormal behavior reporting module 240.
[0142] In block 536, the V2X processor may perform operations including determining the rate (η) of abnormal behavior determinations made in block 532. For example, in some embodiments, the V2X processor determines the number of abnormal behavior determinations made within a given time period (such as one minute, one hour, or one day), and divides the number by the length of the time period to obtain a rate. As another example, in some embodiments, the V2X processor may count the number of abnormal behavior determinations within a given time period, and use the number as the current rate of abnormal behavior determinations. As another example, in some embodiments, the V2X processor may average the time intervals between abnormal behavior determinations, and use the average interval to determine the rate of abnormal behavior determinations within the time period for averaging. In block 536, the V2X processor may also use other means of determining the rate of abnormal behavior determinations. The component for performing the operations of block 536 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior rate determination module 248.
[0143] In determination block 538, the V2X processor may perform operations including comparing the rate (η) of abnormal behavior determinations with a maximum threshold (X) and / or a minimum threshold (Y). In some embodiments, the V2X processor may determine whether the rate of abnormal behavior determinations exceeds the maximum threshold or is less than the minimum threshold. By performing this comparison, the V2X processor determines whether the average rate of abnormal behavior determinations made in the current situation is within a target range for determining the rate. The maximum threshold and / or the minimum threshold may be any preset value and may be set by a V2X system provider, a vehicle manufacturer, an intelligent highway system management, an abnormal behavior management agency, or other management agency. As a non-limiting example, the maximum threshold X may be 100 abnormal behavior determinations per second. Therefore, when the V2X system reports or takes action on more abnormal behavior conditions per unit time than set by an appropriate management agency, the V2X processor may take action in block 540 to reduce the sensitivity of the abnormal behavior detection system, thereby maintaining the abnormal behavior determination rate within the set range of the detection rate and the reporting / action rate. As a non-limiting example, the minimum threshold Y may be one abnormal behavior determination in 10 seconds. Thus, when the V2X system reports or takes action on fewer abnormal behavior conditions per unit time than set by the appropriate regulatory agency, the V2X processor may take action in block 542 to increase the sensitivity of the abnormal behavior detection system to maintain the abnormal behavior determination rate within the set range of the detection rate and the reporting / action rate. The means for performing the operations of block 538 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) executing an abnormal behavior rate determination module 248.
[0144] In block 540, in response to determining that the rate (η) of abnormal behavior determinations exceeds a maximum threshold (X), the V2X processor may perform operations including deactivating one or more sensitive rationality and consistency detectors. For example, in block 540, the V2X processor may reconfigure the detector selector (e.g., 472) to begin filtering one or more rationality and consistency detectors from which detection indications were previously passed to the abnormal behavior detector (e.g., 473). In some embodiments, the V2X processor may identify rationality and consistency detectors that should be deactivated (i.e., whose abnormal behavior indications should be filtered) based on a priority ranking or ranking that may depend on the importance or criticality of the nature of the abnormal behavior that each detector is configured to identify. In this way, the V2X processor may selectively increase filtering of abnormal behavior detections and thereby reduce the rate at which abnormal behavior conditions can be reported and / or acted upon. The means for performing the operations of block 540 may include a processor (eg, 205 , 300 ) of a vehicle V2X communication processing and management system (eg, 104 , 204 ) executing the V2X rationality and consistency detector disabling module 250 .
[0145] In block 542, in response to determining that the rate (η) of abnormal behavior determinations is less than a minimum threshold value Y, the V2X processor may perform operations including activating one or more sensitive rationality and consistency detectors. For example, in block 540, the V2X processor may reconfigure the detector selector (e.g., 472) to stop filtering one or more rationality and consistency detectors that were previously filtered so that subsequent abnormal behavior indications may be passed to the abnormal behavior detector (e.g., 473). In some embodiments, the V2X processor may identify rationality and consistency detectors for activation (i.e., should no longer be filtered) based on a priority ranking or ranking, which may depend on the importance or criticality of the nature of the abnormal behavior that each detector is configured to identify. In this way, the V2X processor may selectively reduce filtering of abnormal behavior detections and, thereby, increase the rate at which abnormal behavior conditions can be reported and / or actioned. The means for performing the operations of block 540 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes a V2X rationality and consistency detector activation module 252.
[0146] In response to determining that the rate (η) of abnormal behavior determinations is between the maximum threshold X and the minimum threshold Y, no changes may be made to the active rationality and consistency detectors, and the V2X processor may continue to perform operation 500f by processing the received V2X information through multiple rationality and consistency detectors in block 528 as described.
[0147] Figure 5G Operations 500g that may be performed by a V2X processor to aggregate abnormal behavior indications and determine whether an abnormal behavior condition exists are illustrated in accordance with some embodiments. Figure 1A to Figure 5G , after the operation in box 502, the V2X processor may perform operations including determining the number of events classified as attacks or abnormal behavior indications output by each of the multiple abnormal behavior detection mechanisms within a time window or a set number of events in box 544. For example, the aggregator may count the events classified as other abnormal behaviors of the attacker within the output string from each abnormal behavior detection mechanism, and determine the score of outputs indicating other abnormal behaviors of the attacker based on the count. This calculation may be completed for some or all abnormal behavior detection mechanisms within the V2X system. In some embodiments, the calculation may be performed continuously, such as maintaining a count of the number or score of a given number of outputs from the abnormal behavior detection mechanism that are classified as attacks or other abnormal behaviors within a given number of outputs or a given time window, and providing the running count or score as an output. The component for performing the operation of box 544 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an attack or abnormal behavior indication counting module 254.
[0148] In determination block 546, the V2X processor may perform operations including determining whether the number of attacks or malicious events indicated in any of the abnormal behavior detection mechanisms exceeds a threshold within a time window or a set number of detector outputs or events. The threshold may be any number greater than one. In some embodiments, the threshold may be set to determine whether the majority of abnormal behavior indications from one or more of the abnormal behavior detection mechanisms indicate other abnormal behavior of the attacker within a time window or a set number of detector outputs or events. The component for performing the operations of block 524 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an attack or abnormal behavior indication counting module 254.
[0149] In response to determining that the number of attacks or malicious events indicated in any of the abnormal behavior detection mechanisms exceeds a threshold within a time window or a set number of events (i.e., determination box 546 = "Yes"), the V2X processor may continue to detect multiple indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms in box 502 as described.
[0150] In response to determining that the number of attacks or malicious events indicated in any of the abnormal behavior detection mechanisms exceeds a threshold within a time window or a set number of events (i.e., determination block 546 = "Yes"), the V2X processor may determine that an abnormal behavior condition exists (block 548). As part of the operations in block 548, the V2X processor may output the abnormal behavior determination to other parts of the V2X system, such as to a reporting and / or response function for performing the operations in block 508 and / or determining a rate of abnormal behavior determinations in block 536 as described. The means for performing the operations of block 548 may include a processor (e.g., 205, 300) of a vehicle V2X communication processing and management system (e.g., 104, 204) that executes an abnormal behavior condition determination module 238.
[0151] Following the operations in block 548 , the V2X processor may perform the operations in block 508 and / or block 548 as described.
[0152] Each specific implementation example is described in the following paragraphs. Although some of the specific implementation 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 V2X communication processing and management system, the V2X communication processing and management system 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 V2X communication processing and management system, the V2X communication processing and management system 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 as 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 V2X communication processing and management system to perform the operations of the method of the following specific implementation example.
[0153] Embodiment 1. A method executed by a processor of a V2X communication system of a vehicle, comprising: detecting multiple indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms; aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms; determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications; and sending an abnormal behavior report or taking a response action in response to determining that an abnormal behavior condition exists.
[0154] Embodiment 2. A method according to embodiment 1, wherein: aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining whether any one of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications includes: determining the existence of a reportable or actionable abnormal behavior condition in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication.
[0155] Embodiment 3. A method according to any one of Embodiments 1 or 2, wherein: aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining whether any one of a selected subset of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications includes: determining the existence of a reportable or actionable abnormal behavior condition in response to determining that at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication.
[0156] Embodiment 4. An embodiment according to any one of embodiments 1 to 3, wherein: aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: aggregating abnormal behavior indications output from multiple abnormal behavior detection mechanisms; and determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications includes: determining the existence of a reportable or actionable abnormal behavior condition in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
[0157] Example 5. A method according to Example 4, wherein determining the existence of a reportable or actionable abnormal behavior condition in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications includes: determining the existence of a reportable or actionable abnormal behavior condition in response to a majority of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
[0158] Embodiment 6. A method according to any one of Embodiments 1 to 5, wherein: aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: applying corresponding weights to the output of each of the one or more abnormal behavior detection mechanisms; and aggregating the weighted outputs of the one or more abnormal behavior detection mechanisms; and determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications includes: determining the presence of a reportable or actionable abnormal behavior condition in response to the weighted output of the abnormal behavior detection mechanism exceeding a threshold.
[0159] Embodiment 7. A method according to any one of embodiments 1 to 6, wherein: detecting multiple indications of V2X abnormal behavior via one or more abnormal behavior detection mechanisms includes: processing received V2X information through multiple rationality and consistency detectors, the multiple rationality and consistency detectors being configured to detect abnormal behavior conditions and output abnormal behavior indications to a detector selector; aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: transmitting the outputs of abnormal behavior indications from a selected subset of the multiple rationality and consistency detectors from the detector selector to the abnormal behavior detector; determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications includes: determining by the abnormal behavior detector that there is a reportable or actionable abnormal behavior condition in response to the abnormal behavior indications output by the selected subset of the multiple rationality and consistency detectors; and the embodiment also includes: determining a rate of abnormal behavior determination; determining whether the rate of abnormal behavior determination exceeds a maximum threshold or is less than a minimum threshold; deactivating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determination exceeds the maximum threshold; and activating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determination is less than the minimum threshold.
[0160] Embodiment 8. A method according to any one of Embodiments 1 to 7, wherein: aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining the number of events classified as attacks or abnormal behavior indications output by each of the multiple abnormal behavior detection mechanisms within a time window or a set number of events; and determining whether there is a reportable or actionable abnormal behavior condition based on the aggregated abnormal behavior indications includes: determining the existence of a reportable or actionable abnormal behavior condition in response to determining that the number of events classified as attacks or abnormal behavior indications output by any one of the multiple abnormal behavior detection mechanisms within the time window or the set number of events exceeds a threshold.
[0161] 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.
[0162] 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.
[0163] 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 technical staff may implement the described functionality in different ways for each specific application, such implementation decisions should not be interpreted as departing from the scope of the claims.
[0164] The hardware for implementing the various exemplary logics, logic boxes, modules, and circuits described in conjunction with the embodiments disclosed herein can be implemented or executed with a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (TCUASIC), 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 can be a microprocessor, in an alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can 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 can be performed by circuits specific to a given function.
[0165] 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 specifically 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.
[0166] 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) communication system of a vehicle, comprising: detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of abnormal V2X behavior; aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms; determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indicators; as well as An abnormal behavior report is sent or a responsive action is taken in response to determining that an abnormal behavior condition exists.
2. The method according to claim 1, wherein: Aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining whether any of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication.
3. The method according to claim 1, wherein: Aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining whether any one of a selected subset of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication.
4. The method according to claim 1, wherein: Aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: aggregating the abnormal behavior indications output from a plurality of abnormal behavior detection mechanisms; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
5. The method of claim 4, wherein determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications comprises: A reportable or actionable abnormal behavior condition is determined to exist in response to a majority of the abnormal behavior detection mechanisms outputting an abnormal behavior indication.
6. The method according to claim 1, wherein: Aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: applying a respective weight to an output of each of the one or more abnormal behavior detection mechanisms; and aggregating weighted outputs of the one or more abnormal behavior detection mechanisms; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes determining that a reportable or actionable abnormal behavior condition exists in response to the weighted output of the abnormal behavior detection mechanism exceeding a threshold.
7. The method according to claim 1, wherein: Detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of V2X abnormal behavior includes: processing received V2X information via a plurality of rationality and consistency detectors configured to detect abnormal behavior conditions and output abnormal behavior indications to a detector selector; Aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: passing the output of the abnormal behavior indications from a selected subset of the plurality of rationality and consistency detectors from the detector selector to an abnormal behavior detector; Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes: determining, by the abnormal behavior detector in response to the abnormal behavior indications output by the selected subset of the plurality of rationality and consistency detectors, that a reportable or actionable abnormal behavior condition exists; and The method further comprises: Determine the rate at which abnormal behavior is determined; determining whether the rate determined by the abnormal behavior exceeds a maximum threshold or is less than a minimum threshold; deactivating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations exceeds the maximum threshold; and One or more sensitive rationality and consistency detectors are activated in response to determining that the rate of abnormal behavior determinations is less than the minimum threshold.
8. The method of claim 1, wherein: Aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining a number of events classified as attacks or abnormal behavior indications output by each of the plurality of abnormal behavior detection mechanisms within a time window or a set number of events; and Determining whether there is a reportable or actionable abnormal behavior condition based on aggregated abnormal behavior indications includes: determining that there is a reportable or actionable abnormal behavior condition in response to determining that the number of events classified as attacks or abnormal behavior indications output by any of the multiple abnormal behavior detection mechanisms within the time window or the set number of events exceeds a threshold.
9. A vehicle-to-everything (V2X) communication system, comprising: A processor configured with processor-executable instructions to: detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of abnormal V2X behavior; aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms; determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indicators; as well as An abnormal behavior report is sent or a responsive action is taken in response to determining that an abnormal behavior condition exists.
10. The V2X communication system of claim 9, wherein the processor is further configured with processor executable instructions to: aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms by determining whether any of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and A determination is made as to whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications by determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication.
11. The V2X communication system of claim 9, wherein the processor is further configured with processor executable instructions to: aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms by determining whether any one of a selected subset of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and A determination is made based on the aggregated abnormal behavior indications whether a reportable or actionable abnormal behavior condition exists by determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication.
12. The V2X communication system of claim 9, wherein the processor is further configured with processor executable instructions to: Aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms by aggregating abnormal behavior indications output from a plurality of abnormal behavior detection mechanisms; and The determination of whether a reportable or actionable abnormal behavior condition exists is made based on the aggregated abnormal behavior indications by determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
13. The V2X communication system of claim 12, wherein the processor is further configured with processor-executable instructions to determine that a reportable or actionable abnormal behavior condition exists in response to a majority of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
14. The V2X communication system of claim 9, wherein the processor is further configured with processor executable instructions to: Aggregating the abnormal behavior indications outputted from the one or more abnormal behavior detection mechanisms by: applying a respective weight to an output of each of the one or more abnormal behavior detection mechanisms; as well as aggregating weighted outputs of the one or more abnormal behavior detection mechanisms; as well as A determination is made based on the aggregated abnormal behavior indications whether a reportable or actionable abnormal behavior condition exists by determining that a reportable or actionable abnormal behavior condition exists in response to the weighted output of the abnormal behavior detection mechanism exceeding a threshold.
15. The V2X communication system of claim 9, wherein the processor is further configured with processor executable instructions to: detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of V2X abnormal behavior by processing the received V2X information with a plurality of rationality and consistency detectors configured to detect abnormal behavior conditions and output abnormal behavior indications to a detector selector; aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms by passing the outputs of the abnormal behavior indications from a selected subset of the plurality of rationality and consistency detectors from the detector selector to an abnormal behavior detector; determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications by determining, by the abnormal behavior detector, in response to the abnormal behavior indications output by the selected subset of the plurality of rationality and consistency detectors, that a reportable or actionable abnormal behavior condition exists; Determine the rate at which abnormal behavior is determined; determining whether the rate determined by the abnormal behavior exceeds a maximum threshold or is less than a minimum threshold; deactivating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations exceeds the maximum threshold; and One or more sensitive rationality and consistency detectors are activated in response to determining that the rate of abnormal behavior determinations is less than the minimum threshold.
16. The V2X communication system of claim 9, wherein the processor is further configured with processor executable instructions to: aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms by determining the number of events classified as an attack or abnormal behavior indication output by each of the plurality of abnormal behavior detection mechanisms within a time window or a set number of events; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications by determining that a reportable or actionable abnormal behavior condition exists in response to determining that the number of events classified as attacks or abnormal behavior indications output by any of the multiple abnormal behavior detection mechanisms within the time window or the set number of events exceeds a threshold.
17. A vehicle-to-everything (V2X) communication system for a vehicle, comprising: means for detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of abnormal V2X behavior; means for aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms; A component for determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications; and Means for sending an abnormal behavior report or taking responsive action in response to determining that an abnormal behavior condition exists.
18. The V2X communication system according to claim 17, wherein: The means for aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes means for determining whether any of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and Means for determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes means for determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the abnormal behavior detection mechanisms outputs an abnormal behavior indication.
19. The V2X communication system according to claim 17, wherein: The means for aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes means for determining whether any of a selected subset of the one or more abnormal behavior detection mechanisms output an abnormal behavior indication; and Means for determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes means for determining that a reportable or actionable abnormal behavior condition exists in response to determining that at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication.
20. The V2X communication system according to claim 17, wherein: The means for aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes means for aggregating abnormal behavior indications output from a plurality of abnormal behavior detection mechanisms; and Means for determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes means for determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
21. The V2X communication system of claim 20, wherein the means for determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications comprises means for determining that a reportable or actionable abnormal behavior condition exists in response to a majority of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
22. The V2X communication system according to claim 17, wherein: The means for aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms comprises: means for applying a respective weight to an output of each of the one or more abnormal behavior detection mechanisms; and means for aggregating weighted outputs of the one or more abnormal behavior detection mechanisms; and Means for determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes means for determining that a reportable or actionable abnormal behavior condition exists responsive to the weighted output of the abnormal behavior detection mechanism exceeding a threshold.
23. The V2X communication system according to claim 17, wherein: means for detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of V2X abnormal behavior including means for processing received V2X information through a plurality of rationality and consistency detectors configured to detect abnormal behavior conditions and output abnormal behavior indications to a detector selector; The means for aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes means for communicating the output of the abnormal behavior indications from a selected subset of the plurality of rationality and consistency detectors from the detector selector to the abnormal behavior detector; means for determining, based on the aggregated abnormal behavior indications, whether a reportable or actionable abnormal behavior condition exists includes means for determining, by the abnormal behavior detector in response to the abnormal behavior indications output by the selected subset of the plurality of rationality and consistency detectors, that a reportable or actionable abnormal behavior condition exists; and The V2X communication system further includes: A component for determining a rate at which abnormal behavior is determined; means for determining whether the rate determined by the abnormal behavior exceeds a maximum threshold or is less than a minimum threshold; means for deactivating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations exceeds the maximum threshold; and Means for activating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations is less than the minimum threshold.
24. The V2X communication system according to claim 17, wherein: The means for aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes means for determining a number of events classified as an attack or abnormal behavior indication output by each of the plurality of abnormal behavior detection mechanisms within a time window or a set number of events; and The means for determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes means for determining that a reportable or actionable abnormal behavior condition exists in response to determining that a number of said events classified as attacks or abnormal behavior indications output by any of said plurality of abnormal behavior detection mechanisms within said time window or said set number of events exceeds a threshold.
25. 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) communication system to perform operations, the operations comprising: detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of abnormal V2X behavior; aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms; determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indicators; as well as An abnormal behavior report is sent or a responsive action is taken in response to determining that an abnormal behavior condition exists.
26. The non-transitory processor-readable medium of claim 25, wherein the stored processor-executable instructions are further configured to cause the processor of the V2X communication system to perform operations such that: Aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining whether any or any one of the selected subset of the one or more abnormal behavior detection mechanisms outputs an abnormal behavior indication; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes determining the presence of a reportable or actionable abnormal behavior condition in response to determining that at least one of the abnormal behavior detection mechanisms or at least one of the selected subset of abnormal behavior detection mechanisms outputs an abnormal behavior indication.
27. The non-transitory processor-readable medium of claim 25, wherein the stored processor-executable instructions are further configured to cause the processor of the V2X communication system to perform operations such that: Aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: Aggregating abnormal behavior indications output from multiple abnormal behavior detection mechanisms; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes determining that a reportable or actionable abnormal behavior condition exists in response to a threshold number of the abnormal behavior detection mechanisms outputting abnormal behavior indications.
28. The non-transitory processor-readable medium of claim 25, wherein the stored processor-executable instructions are further configured to cause the processor of the V2X communication system to perform operations such that: Aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: applying a respective weight to an output of each of the one or more abnormal behavior detection mechanisms; as well as aggregating weighted outputs of the one or more abnormal behavior detection mechanisms; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes determining that a reportable or actionable abnormal behavior condition exists in response to the weighted output of the abnormal behavior detection mechanism exceeding a threshold.
29. The non-transitory processor-readable medium of claim 25, wherein the stored processor-executable instructions are further configured to cause the processor of the V2X communication system to perform operations such that: Detecting, via one or more abnormal behavior detection mechanisms, a plurality of indications of abnormal V2X behavior includes: processing the received V2X information via a plurality of rationality and consistency detectors configured to detect abnormal behavior conditions and output abnormal behavior indications to a detector selector; Aggregating the abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: passing the output of the abnormal behavior indications from a selected subset of the plurality of rationality and consistency detectors from the detector selector to an abnormal behavior detector; and Determining whether a reportable or actionable abnormal behavior condition exists based on the aggregated abnormal behavior indications includes: determining, by the abnormal behavior detector in response to the abnormal behavior indications output by the selected subset of the plurality of rationality and consistency detectors, that a reportable or actionable abnormal behavior condition exists, and The stored processor executable instructions are further configured to cause the processor of the V2X communication system to perform operations, the operations further comprising: Determine the rate at which abnormal behavior is determined; determining whether the rate determined by the abnormal behavior exceeds a maximum threshold or is less than a minimum threshold; deactivating one or more sensitive rationality and consistency detectors in response to determining that the rate of abnormal behavior determinations exceeds the maximum threshold; and One or more sensitive rationality and consistency detectors are activated in response to determining that the rate of abnormal behavior determinations is less than the minimum threshold.
30. The non-transitory processor-readable medium of claim 25, wherein the stored processor-executable instructions are further configured to cause the processor of the V2X communication system to perform operations such that: Aggregating abnormal behavior indications output from the one or more abnormal behavior detection mechanisms includes: determining a number of events classified as indicative of an attack or abnormal behavior output by each of a plurality of abnormal behavior detection mechanisms within a time window or a set number of events; and Determining whether there is a reportable or actionable abnormal behavior condition based on aggregated abnormal behavior indications includes: determining that there is a reportable or actionable abnormal behavior condition in response to determining that the number of events classified as attacks or abnormal behavior indications output by any of the multiple abnormal behavior detection mechanisms within the time window or the set number of events exceeds a threshold.
