C-v2x scenario event management method and system based on multi-source sensor

Abstract

A C-V2X scenario event management method and system based on a multi-source sensor, which method and system belong to the technical field of Internet of Vehicles. The system comprises a roadside device end, a user terminal and a cloud service support platform, wherein traffic events are transmitted from the roadside device end to an EMC for fusion calculation, and traffic event information is then reported to an EMQX cluster and kafka cluster of the cloud service support platform by means of an RSU, and is finally stored in a platform database; and the cloud service support platform issues the traffic event information to the user terminal according to the geographic location of the user terminal, such that C-V2X scenario event early warning is implemented according to the information. By means of the management method and system, the comprehensive traffic status in a test area is learned in real time and data analysis in the test area is implemented in real time, microscopic insight for intersections can be provided, traffic C-V2X scenario events are unified, and the specifications for event transmission data are unified.

Description

C-V2X scenario event management method and system based on multi-source sensors Technical Field

[0001] The present invention relates to a C-V2X scenario event management method and system based on multi-source sensors, and belongs to the technical field of vehicle networking. Background Art

[0002] Transportation is the lifeblood of human economic and social development. An efficient travel and freight transportation system will significantly boost a region's economic development. Since the 1950s, researchers have been exploring intelligent transportation, hoping to leverage advanced technologies such as detection, computing, communication, and control to build a comprehensive transportation system that is real-time, accurate, efficient, and highly aligned with transportation needs.

[0003] Urban road operators lack comprehensiveness, accuracy, and timeliness in the acquisition and dissemination of traffic data, traffic incidents, and other information, making it difficult to meet user demands for diverse, accurate, and efficient travel services. By applying the Internet of Transportation (IoT) and mining and processing data, personalized travel services can be realized, gradually shaping the entire transportation system into an efficient, coordinated, and optimized entity.

[0004] In a V2X system, status information on all traffic elements is digitally collected and rapidly exchanged via mobile communication technology. Traffic participants can collaborate based on this information, while the traffic control center analyzes and extracts big data from the massive amounts of collected information to enable global traffic control. V2X technology is also transforming the service model of traditional road operators, shifting them from simple infrastructure providers to road travel service providers. Through scenario-based information collection and analysis, it enables personalized and flexible services.

[0005] Current vehicle-road cooperative warning solutions are primarily based on Internet of Vehicles (IoV) and intelligent transportation system (ITS) technologies. Through communication and interaction between vehicles and infrastructure, they enable real-time monitoring and early warning of traffic incidents, improving driving safety and traffic efficiency. This solution primarily encompasses the following aspects:

[0006] Vehicle-to-vehicle communication (V2V): Through vehicle-to-vehicle communication technology, vehicles can exchange information with each other, such as vehicle location, speed, direction, etc., to achieve real-time understanding of each other's status and traffic conditions.

[0007] Vehicle-to-Infrastructure (V2I) communication: Communication between vehicles and infrastructure enables the sharing and exchange of information about roads and road conditions, so that drivers and vehicle systems can make more informed decisions.

[0008] Data collection and processing: Through sensors and other equipment, vehicle and road data is collected, processed and analyzed to predict possible traffic events, such as traffic congestion and accidents, and to provide early warnings and avoidance measures.

[0009] However, the current vehicle-road cooperative warning solution still has some shortcomings. For example:

[0010] 1. Data quality issues: Since road and vehicle status information is collected through sensors and other equipment, the quality of the data will directly affect the accuracy and timeliness of the early warning.

[0011] 2. Lack of unified standards: Currently, the vehicle-road collaborative warning solution lacks unified standards and protocols. Equipment from different manufacturers and different regions cannot communicate and exchange information with each other well, which reduces the system's collaborative effect.

[0012] 3. Security issues: Communication between vehicles and infrastructure involves user privacy and information security. If the system security is not guaranteed, it may cause malicious attacks and information leakage.

[0013] Summary of the Invention

[0014] In order to supplement the deficiencies in the above-mentioned existing technologies, to further reduce the frequency of traffic accidents and ensure the safety of drivers and passengers, in addition to the traffic management departments strengthening management, education, and even increasing penalties for violations, it is also very necessary to equip buses, connected vehicles, and some special vehicles with Internet of Vehicles equipment with driving safety reminder functions, early warning, violation warning, collision warning and other functions to timely remind driving safety information and intersection information to avoid accidents, violations and other malicious incidents. At the same time, based on driving safety reminders, functions are expanded to be compatible with the push and sharing of information in various aspects such as tourism, shopping, and food enjoyment. The present invention provides a C-V2X scenario event management method and system based on multi-source sensors, and the technical solution is as follows:

[0015] A first object of the present invention is to provide a C-V2X scenario event management system based on multi-source sensors, characterized in that the system includes: a roadside device, a user terminal, and a cloud service support platform; traffic events are fused and calculated from the roadside device to the EMC, and then the traffic event information is reported to the EMQX cluster and Kafka cluster of the cloud service support platform through the RSU, and finally stored in the platform database; the cloud service support platform releases traffic event information to the user terminal based on the user terminal's geographic location, and implements C-V2X scenario event warnings based on this information;

[0016] The cloud service support platform includes:

[0017] Traffic incident management module, used to edit, delete and query reported traffic incident information;

[0018] Traffic incident release module, used to manage key information of traffic incident release, including: incident type, control level, impact scope, and release rules;

[0019] Regional electronic fence management module, used to edit and manage electronic fence information;

[0020] Event publishing rule management module, used to manage the publishing rules of traffic events;

[0021] Traffic incident map module, used to display the real-time location and query of traffic incidents on the map;

[0022] Traffic event overview module is used to perform basic statistics on traffic events in event dimensions, including event data overview, event type distribution, and processing status distribution;

[0023] The traffic incident statistics module is used to count the cumulative number and proportion of various traffic incident types;

[0024] The traffic warning reminder module is used to issue a warning to the user terminal.

[0025] Optionally, the traffic event management module includes: a traffic event list module and a traffic event retrieval module;

[0026] The traffic event list information includes event number, event type, event source, affected road section, event content, remarks, reporting time, end time, processing status, remarks;

[0027] The traffic event retrieval module is used to retrieve relevant traffic events based on the event type, event source and processing status.

[0028] Optionally, the traffic event publishing module includes: a traffic event editing module, a traffic event adding module, a user management module, a traffic event termination module and a query module;

[0029] The traffic event editing module fills in the key information of the traffic event release, including: event type, control level, impact range, and release rules;

[0030] The traffic event adding module is used to add traffic events, allowing the impact range of traffic events to be drawn directly on the map page, and supports at least three annotation types: point, segment, and surface;

[0031] The user management module is used to manage the user's authority to publish traffic events and provide administrator confirmation function;

[0032] The traffic event termination module is used to support the termination of traffic events, including: automatically terminating traffic events according to the end time and terminating traffic events in advance;

[0033] The query module is used to perform queries based on event type, occurrence time, end time or event status.

[0034] Optionally, the regional electronic fence management module is used to add, modify or delete the fence area, including: fence name, fence current status, fence range, fence area type, fence area map, and is also used to send warning information to vehicles.

[0035] Optionally, the event publishing rule management module is used to provide event publishing rules for the traffic event publishing module, and the event publishing rules include: rule name, rule definition, and rule expression.

[0036] Optionally, the traffic event map module locates and visualizes the location of the traffic event based on the positioning information uploaded to the cloud by multiple roadside devices.

[0037] Optionally, the multiple roadside equipment includes: RSU, radar, camera, electronic signage, which collects C-V2X scene events and transmits them to the cloud service support platform through RSU.

[0038] Optionally, the event types include: road congestion, road construction, traffic accidents, bad weather, and traffic control.

[0039] Optionally, the sources of the event include: police officer reporting, user reporting, self-built map, and third-party access.

[0040] The second object of the present invention is to provide a C-V2X scenario event management method based on multi-source sensors, which is implemented using any of the management systems described above.

[0041] The beneficial effects of the present invention are:

[0042] It can grasp the overall traffic status and data analysis in the test area in real time, provide micro-insights for intersections, unify traffic C-V2X scenario events, and unify the specifications for event transmission data. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0044] FIG1 is a traffic event map of the present invention.

[0045] FIG2 is a diagram of a traffic event overview interface according to an embodiment of the present invention.

[0046] FIG3 is an interface diagram of a trend of changes in the total number of traffic incidents according to an embodiment of the present invention.

[0047] FIG4 is a structural diagram of the scene event management system of the present invention. DETAILED DESCRIPTION

[0048] To make the objectives, technical solutions and advantages of the present invention more clear, the embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.

[0049] Example 1:

[0050] This embodiment provides a C-V2X scenario event management system based on multi-source sensors, including: a roadside device, a user terminal, and a cloud service support platform. Traffic events are fused and calculated from the roadside device to the EMC, and then reported to the EMQX cluster and Kafka cluster of the cloud service support platform via the RSU, and finally stored in the platform database. The cloud service support platform releases traffic event information to the user terminal based on the user terminal's geographic location, and uses this information to implement C-V2X scenario event warnings.

[0051] The cloud service support platform includes:

[0052] Traffic incident management module, used to edit, delete and query reported traffic incident information;

[0053] Traffic incident release module, used to manage key information of traffic incident release, including: incident type, control level, impact scope, and release rules;

[0054] Regional electronic fence management module, used to edit and manage electronic fence information;

[0055] Event publishing rule management module, used to manage the publishing rules of traffic events;

[0056] Traffic incident map module, used to display the real-time location and query of traffic incidents on the map;

[0057] Traffic event overview module is used to perform basic statistics on traffic events in event dimensions, including event data overview, event type distribution, and processing status distribution;

[0058] The traffic incident statistics module is used to count the cumulative number and proportion of various traffic incident types;

[0059] The traffic warning reminder module is used to issue a warning to the user terminal.

[0060] Example 2:

[0061] This embodiment provides a C-V2X scenario event management system based on multi-source sensors, including: roadside equipment, user terminals, and a cloud service support platform. Traffic events are integrated and calculated from the roadside equipment to the EMC, and then the traffic event information is reported to the EMQX cluster and Kafka cluster of the cloud service support platform through the RSU, and finally stored in the platform database. The cloud service support platform releases traffic event information to user terminals based on their geographic locations, and uses this information to implement C-V2X scenario event warnings.

[0062] While a user is driving, the cloud service support platform receives, processes, and issues sharing requests. The target user automatically receives C-V2X traffic event information on their terminal, and based on this information, a C-V2X scenario event warning is implemented.

[0063] The overall framework of the system is shown in Figure 4, which mainly includes the following processes:

[0064] 1. Owner vehicle determination: Supports "who I am" determination, that is, combining vehicle location information and structured data information to comprehensively determine the owner vehicle's location.

[0065] 2. Traffic incident detection: Supports real-time understanding of the overall traffic status and data analysis within the test area, and can provide micro-insights for intersections.

[0066] 3. Individual risk assessment: Supports comprehensive assessment of individual traffic risks based on traffic event scenarios, vehicle risk factor analysis, and other capabilities combined with personal vehicle location information.

[0067] The cloud service support platform includes:

[0068] 1. Traffic incident management module, used to edit, delete and query reported traffic incident information, including: traffic incident list module and traffic incident retrieval module.

[0069] The traffic incident management module supports editing, deleting and querying the basic information of all reported traffic incidents, realizing efficient operational management of traffic incident releases; the traffic incident list information includes incident number, incident type (road congestion, road construction, traffic accident, bad weather, traffic control), incident source (reported by police officer, reported by user, self-built map, third-party access), affected road section, incident content, remarks, reporting time, end time, processing status (signed, not signed), remarks, etc.; users can select incident type, incident source and processing status to search for related traffic incidents.

[0070] 2. Traffic event publishing module, including: traffic event editing module, traffic event adding module, user management module, traffic event termination module and query module, which is used to manage key information of traffic event publishing, including: event type, control level, impact scope and publishing rules.

[0071] The traffic event release module supports filling in key information for traffic event releases, such as event type, control level, impact range, release rules, etc.; supports new traffic event functions, allowing the impact range of traffic events to be drawn directly on the map page, and supports at least three annotation types: point, segment, and surface; supports providing administrator confirmation functions; supports not only automatically ending traffic events according to the end time, but also supports early ending of traffic events; all published content of traffic events can be queried according to event type, occurrence time, end time or event status, and the published content can also be edited and changed.

[0072] 3. Regional electronic fence management module, used to edit and manage electronic fence information, supports adding, modifying or deleting fence demonstration areas; supports filling in the fence name and selecting the current status when adding a fence area; supports selecting locations according to multiple conditions, and the fence area can also change the required fence range at will; supports real-time alarm reminders based on the current location of the vehicle and the combination of electronic fence areas; data support includes at least the following elements: name, status, area type, specific fence area map (administrative district, prototype, irregular shape, etc.).

[0073] 4. Event publishing rule management module is used to manage the publishing rules of traffic events. It supports adding rules, entering rule names, rule definitions, rule expressions and other information; supports selecting associated rules in traffic event publishing so that the rules affect the scope of the event; supports adding or modifying the published rule definitions. When publishing a traffic event, the scope of the event publishing can be selected according to this rule; data information supports the following data elements: rule name, rule definition, rule expression, etc.

[0074] 5. The traffic event map module, as shown in Figure 1, is used to display the real-time positioning and query of traffic events on the map. After the data from multiple roadside equipment such as RSU, MEC, radar, camera and traffic light are integrated, it is uploaded to the cloud through the PC5 interface. Based on the high-precision positioning in the information, it is accurately visualized on the map, supporting real-time positioning and query viewing of traffic events.

[0075] 6. The Traffic Event Overview module, shown in Figure 2, provides basic statistics on traffic events, divided into event data overview, event type distribution, and processing status distribution. The event data overview includes statistics on the total number of events, event type, and processing status.

[0076] 7. The traffic event statistics module is used to count the types of traffic events, as shown in Figure 3, including the cumulative number and proportion of road congestion, road construction, traffic accidents, severe weather, and traffic control events. The sum of each type of traffic event is the cumulative number of traffic events released.

[0077] 8. Traffic warning reminder module, used to issue warnings to user terminals.

[0078] 9. Traffic incident source statistics module: The cumulative number and proportion of event sources reported by administrators and external access sources. The sum of traffic incident source statistics is the cumulative number of published traffic incidents.

[0079] 10. Traffic incident total amount change trend display module: presents the change trend of the total amount of traffic incidents; can filter by event type and time.

[0080] Some steps in the embodiments of the present invention may be implemented using software, and the corresponding software program may be stored in a readable storage medium, such as a CD or a hard disk.

[0081] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A C-V2X scenario event management system based on multi-source sensors, characterized in that: The system includes: a roadside device, a user terminal and a cloud service support platform; traffic events are integrated and calculated from the roadside device to the EMC, and then the traffic event information is reported to the EMQX cluster and the Kafka cluster of the cloud service support platform through the RSU, and finally saved to the platform database; the cloud service support platform releases traffic event information to the user terminal according to the geographical location of the user terminal, and implements C-V2X scenario event warning based on this information; The cloud service support platform includes: Traffic incident management module, used to edit, delete and query reported traffic incident information; Traffic incident release module, used to manage key information of traffic incident release, including: incident type, control level, impact scope, and release rules; Regional electronic fence management module, used to edit and manage electronic fence information; An event publishing rule management module is used to manage the publishing rules of traffic events; Traffic incident map module, used to display the real-time location and query of traffic incidents on the map; Traffic event overview module, which is used to perform basic statistics on traffic events in event dimensions, including event data overview, event type distribution, and processing status distribution; The traffic incident statistics module is used to count the cumulative number and proportion of various types of traffic incidents; The traffic warning reminder module is used to issue a warning to the user terminal.

2. The C-V2X scenario event management system based on multi-source sensors according to claim 1, characterized in that: The traffic event management module includes: a traffic event list module and a traffic event retrieval module; The traffic event list information includes event number, event type, event source, affected road section, event content, remarks, reporting time, end time, processing status, remarks; The traffic event retrieval module is used to retrieve relevant traffic events according to the event type, event source and processing status.

3. The C-V2X scenario event management system based on multi-source sensors according to claim 1, characterized in that: The traffic event publishing module includes: a traffic event editing module, a traffic event adding module, a user management module, a traffic event termination module and a query module; The traffic event editing module fills in the key information of traffic event release, including: event type, control level, impact range, and release rules; The traffic event adding module is used to add traffic events, allowing the traffic event impact range to be drawn directly on the map page, and supports at least three annotation types: point, segment, and surface; The user management module is used to manage the user's authority to publish traffic events and provide an administrator confirmation function; The traffic event termination module is used to support the termination of traffic events, including: automatically terminating traffic events according to the termination time and terminating traffic events in advance; The query module is used to query according to event type, occurrence time, end time or event status.

4. The C-V2X scenario event management system based on multi-source sensors according to claim 1, characterized in that: The regional electronic fence management module is used to add, modify or delete the fence area, including: fence name, fence current status, fence range, fence area type, fence area map, and is also used to send warning information to vehicles.

5. The C-V2X scenario event management system based on multi-source sensors according to claim 1, characterized in that: The event publishing rule management module is used to provide event publishing rules for the traffic event publishing module, and the event publishing rules include: rule name, rule definition, and rule expression.

6. The C-V2X scenario event management system based on multi-source sensors according to claim 1, characterized in that: The traffic event map module locates and visualizes the location of traffic events based on the positioning information uploaded to the cloud by multiple roadside devices.

7. The C-V2X scenario event management system based on multi-source sensors according to claim 6, characterized in that: The multiple roadside equipment includes: RSU, radar, camera, electronic signage, and collects C-V2X scene events and transmits them to the cloud service support platform through RSU.

8. The C-V2X scenario event management system based on multi-source sensors according to claim 2, characterized in that: The event types include: road congestion, road construction, traffic accidents, bad weather, and traffic control.

9. The C-V2X scenario event management system based on multi-source sensors according to claim 2, characterized in that: The sources of the events include: reports from police dispatchers, reports from users, self-built maps, and third-party access.

10. A C-V2X scenario event management method based on multi-source sensors, characterized in that: The method is implemented by using the management system described in any one of claims 1 to 9.

Images