CN111737023A - Vehicle-mounted event processing method, cloud server and computer-readable storage medium - Google Patents
Vehicle-mounted event processing method, cloud server and computer-readable storage medium Download PDFInfo
- Publication number
- CN111737023A CN111737023A CN202010405731.XA CN202010405731A CN111737023A CN 111737023 A CN111737023 A CN 111737023A CN 202010405731 A CN202010405731 A CN 202010405731A CN 111737023 A CN111737023 A CN 111737023A
- Authority
- CN
- China
- Prior art keywords
- event
- message middleware
- module
- middleware cluster
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 15
- 238000012545 processing Methods 0.000 claims abstract description 21
- 230000003993 interaction Effects 0.000 claims abstract description 6
- 238000000034 method Methods 0.000 claims description 21
- 238000001914 filtration Methods 0.000 claims description 18
- 230000010365 information processing Effects 0.000 claims description 10
- 230000008569 process Effects 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 5
- 230000008859 change Effects 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 12
- 238000004458 analytical method Methods 0.000 description 7
- 238000000586 desensitisation Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The scheme relates to a vehicle-mounted event processing method, a cloud server and a computer storage medium.A configuration module manages an event type, a message middleware cluster module, a service module and an event forwarding rule, and realizes unified management of a processing strategy after an event is uploaded to the cloud server. The vehicle-mounted event processing method comprises the following steps: the event distribution module receives the to-be-processed event uploaded by the vehicle-mounted terminal and forwarded by the gateway; the event distribution module identifies an event type corresponding to the event to be processed based on the interaction protocol; the event distribution module reads one or more target forwarding rules corresponding to the event type of the event to be processed from the configuration module to determine one or more target message middleware clusters; the event distribution module sends the data of the event to be processed to a target message middleware cluster unit in the message middleware cluster module for storage based on a target forwarding rule, and one target message middleware cluster unit stores the related information of one target message middleware cluster.
Description
Technical Field
The invention belongs to the technical field of vehicle-mounted event processing, and particularly relates to a vehicle-mounted event processing method, a cloud server and a computer-readable storage medium.
Background
With the development of the internet of things technology, all large automobile factories deeply research and operate the automobile networking technology, vehicles can communicate with the cloud at any time and any place, a large number of vehicle events are reported to the cloud, management aiming at event processing strategies is particularly complex, the state or information of an automobile terminal can be misjudged by the cloud due to carelessness, misoperation is further caused, and even serious accidents are caused. If the automobile terminal directly communicates to different event processing systems in the cloud for different events, the development difficulty of the automobile terminal is increased, and the management of a business system for processing the events is not controlled along with the increase of the type scale of the events. Sometimes, the service system is a third-party system, the event carrying parameters need to be filtered and then transferred to the service system, and the dynamic filtering of the event carrying parameters cannot be realized by a way that the service system directly processes the event.
In recent years, message middleware with different characteristics appears in succession, and message notification modes acceptable by a service system also have various choices. Kafka is selected in a patent application publication No. CN108809994A, "unified message pushing method and system based on event and rule management", which can not select different message middleware or message middleware clusters according to the needs of a service system, and can not dynamically change the configuration of the message middleware or message middleware clusters, and the patent strongly couples event distribution and configuration management in one system (referred to as a unified message center), and the service system can not dynamically update the monitored message clusters.
Disclosure of Invention
The invention provides a vehicle-mounted event processing method, a cloud server and a computer readable storage medium, which manage event types, a message middleware cluster module, a service module and an event forwarding rule through a configuration module, and realize the unified management of a processing strategy after a terminal event is uploaded to a cloud server.
The technical scheme of the invention is as follows:
the invention provides a vehicle event processing method, which is applied to a vehicle event processing system, and the system comprises the following steps: the system comprises an event distribution module, a configuration module, a service module and a message middleware cluster module; the method comprises the following steps:
the event distribution module receives the to-be-processed event uploaded by the vehicle-mounted terminal and forwarded by the gateway;
the event distribution module identifies an event type corresponding to the event to be processed based on an interaction protocol;
the event distribution module reads one or more target forwarding rules corresponding to the event type of the event to be processed from the configuration module to determine one or more target message middleware clusters;
the event distribution module sends the data of the event to be processed to a target message middleware cluster unit in a message middleware cluster module for storage based on the target forwarding rule, wherein one target message middleware cluster unit stores the related information of one target message middleware cluster;
the service module reads a forwarding rule corresponding to the service module from the configuration module so as to identify a message middleware cluster unit where a message middleware cluster corresponding to the forwarding rule is located;
and the service module receives the data of the event to be processed sent by the message middleware cluster unit and processes the event.
Preferably, the type of the target message middleware cluster is one or more of an activemq middleware cluster, a kafka middleware cluster, a rabbitmq middleware cluster and a rocktmq middleware cluster.
Preferably, the method further comprises:
inputting information related to the message middleware cluster into a configuration module in advance to generate a unique identifier M _ ID of the message middleware cluster;
inputting information related to each service module into a configuration module in advance to generate a unique identifier SYSTEM _ ID of each service module;
inputting information related to the EVENT type into a configuration module in advance to generate a unique identifier EVENT _ ID of the EVENT type;
forwarding rule configuration is carried out in a configuration module in advance;
the message middleware cluster related information includes: NAME M _ NAME and configuration information of the message middleware cluster, and the configuration information of the message middleware cluster includes: IP address M _ IP and TOPIC name M _ TOPIC;
the information related to the service module includes: the NAME SYSTEM _ NAME and the CODE SYSTEM _ CODE of the service module;
the event type-related information includes: NAME of EVENT _ NAME, encoding EVENT _ CODE, data type of EVENT generation, and specific data field information.
Preferably, the step of configuring the forwarding rule includes:
creating a forwarding rule and defining: the name of the rule is R, the priority of the rule is L, and the rule state is an enabling state;
and performing a relationship configuration operation: firstly, selecting an EVENT coded as EVENT _ CODE, and carrying out data filtering operation selection on data information corresponding to the EVENT; selecting a message middleware cluster with the NAME of M _ NAME, and performing relation binding on the event and the message middleware cluster; finally, selecting a service module coded as SYSTEM _ CODE, and binding the relation between the message middleware cluster and the service module;
after the relation configuration operation, generating a corresponding forwarding rule; wherein, one forwarding rule records: the corresponding relation of the unique identifier EVENT _ ID of an EVENT, the unique identifier M _ ID of a message middleware cluster, the unique identifiers SYSTEM _ ID of one or more service modules and data filtering information; or, one forwarding rule records: the unique identifier EVENT _ ID of one EVENT, the unique identifiers M _ ID of a plurality of message middleware clusters, the unique identifiers SYSTEM _ ID of one or more service modules and the data filtering information.
Preferably, the step of sending, by the event distribution module, the data of the event to be processed to the target message middleware cluster unit in the message middleware cluster module for storage based on the target forwarding rule includes:
the event distribution module filters the data of the event to be processed based on the data filtering information in the target forwarding rule;
and the event distribution module sends the filtered data to a target message middleware cluster unit in the message middleware cluster module for storage based on the target forwarding rule.
Preferably, before the step of receiving, by the service module, the data of the event to be processed extracted from the message middleware cluster unit and performing event processing on the data, the method further includes:
the service module compares the identified message middleware cluster unit with the message middleware cluster unit identified last time or first time, and judges whether a newly added message middleware cluster unit exists in the identification and/or whether a message middleware cluster with changed configuration information exists;
if the newly added message middleware cluster unit exists, the service module establishes monitoring connection to the newly added message middleware cluster unit and starts to monitor the message of the newly added message middleware cluster unit;
if the message middleware cluster with the changed configuration information exists, the service module monitors the message middleware cluster unit for address change according to the changed cluster configuration information.
The present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a vehicle-mounted information processing module, implements the steps of the vehicle-mounted event processing method described above.
The invention also provides a cloud server which comprises a memory and a vehicle-mounted information processing module, wherein the memory stores computer readable instructions, and the vehicle-mounted information processing module executes the computer readable instructions to execute the vehicle-mounted event processing method.
The invention has the beneficial effects that:
the event handling strategy of the centralized management vehicle-mounted terminal after the event is uploaded to the cloud server can achieve event type transparence, message middleware cluster transparence, service module transparence and forwarding rule transparence, and once the cloud server finds the relevant problems of the event and data forwarding, the problems can be quickly located. The management of the events of the vehicle-mounted terminal is not dispersed and complex, the cloud server end has a clear context for the event state of the vehicle terminal, and the information cluster, the service system and the event relation can be dynamically managed and the event data can be dynamically filtered. Meanwhile, the event processing flow is simplified, the event distribution and configuration management are decoupled, the stability and maintainability of the Internet of vehicles platform are improved, and the use experience of a user is improved.
Drawings
FIG. 1 is a block diagram of interaction between modules of the present invention for implementing the above method;
FIG. 2 is a flow chart of a configuration module performing message middleware cluster docketing;
FIG. 3 is a flow chart of a configuration module for message middleware cluster docketing
FIG. 4 is a flow chart of event type docketing by the configuration module;
FIG. 5 is a flow chart of a configuration module for configuring forwarding rules;
FIG. 6 is a flow chart of event distribution performed by the event distribution module;
fig. 7 is a flowchart of event monitoring and processing performed by a service module.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
As shown in fig. 1, the present invention provides a vehicle event processing method, which is applied to a vehicle event processing system, and the system includes: the system comprises an event distribution module, a configuration module, a service module and a message middleware cluster module, and certainly, the system also comprises a message analysis module for analyzing messages sent by the gateway, wherein interactive analysis is arranged between the message analysis module and the gateway, so that the message analysis can be carried out on various events sent by the gateway in real time, and the analyzed data is transmitted again, and the method specifically comprises the following steps of:
the event distribution module receives the to-be-processed event uploaded by the vehicle-mounted terminal and forwarded by the gateway, namely the event distribution module receives the data analyzed by the message analysis module.
The event distribution module identifies the event type corresponding to the event to be processed based on the interaction protocol, wherein the event type of the event to be processed is identified through the name of the event to be processed, the names of different events are different, the interaction protocol is established in advance by the vehicle-mounted terminal and the cloud server, and the names of the events are named in a consistent manner through the protocol, so that the event distribution module can accurately identify the type corresponding to the event to be processed.
And the event distribution module reads one or more target forwarding rules corresponding to the event type of the event to be processed from the configuration module so as to determine one or more target message middleware clusters.
And the event distribution module sends the data of the event to be processed to a target message middleware cluster unit in the message middleware cluster module for storage based on the target forwarding rule, wherein one target message middleware cluster unit stores the related information of one target message middleware cluster. Before data storage, the event distribution module needs to judge whether data filtering is needed for the type of event based on a data filtering rule in the forwarding rule, and if so, unnecessary or unsafe information is removed according to a set mode, and desensitization processing and other actions are carried out on data and data fields.
And the service module reads the corresponding forwarding rule from the configuration module so as to identify the message middleware cluster unit where the message middleware cluster corresponding to the forwarding rule is located. The service module can use a CODE SYSTEM _ CODE de-configuration module to acquire the latest message middleware cluster configuration information at regular time or based on manual trigger, the configuration module searches whether the relation with the M _ ID exists in a database thereof based on the SYSTEM _ ID corresponding to the SYSTEM _ CODE, and if so, the corresponding message middleware cluster configuration information is sent to the service module; if not, the business module will not do anything.
And the service module receives the data of the event to be processed sent by the message middleware cluster unit and processes the event. The service module selects a corresponding processor according to the event type to perform specific event logic processing. Therefore, the purpose of dynamically updating the monitoring of the message cluster and processing the corresponding event is achieved.
The type of the target message middleware cluster is one or more of an activemq middleware cluster, a kafka middleware cluster, a rabbitmq middleware cluster and a rocktmq middleware cluster.
The method also comprises the step of configuring relevant information in a configuration module in advance, wherein the configuration process comprises the following steps:
inputting information related to the message middleware cluster into a configuration module in advance to generate a unique identifier M _ ID of the message middleware cluster;
inputting information related to each service module into a configuration module in advance to generate a unique identifier SYSTEM _ ID of each service module;
inputting information related to the EVENT type into a configuration module in advance to generate a unique identifier EVENT _ ID of the EVENT type;
forwarding rule configuration is carried out in a configuration module in advance;
the message middleware cluster related information includes: NAME M _ NAME and configuration information of the message middleware cluster, and the configuration information of the message middleware cluster includes: the IP address M _ IP and the topoic name M _ TOPIC, specifically, as shown in fig. 2, the administrator logs in the configuration module, enters a message middleware cluster filing page provided by the configuration center, and fills in related information of the middleware cluster. The message middleware cluster can be an activemq cluster, a kafka cluster, a rabbitmq cluster, a rocktmq cluster and the like, and any message middleware supported by the platform can be recorded. Defining information such as cluster name, cluster configuration and the like, clicking and storing the information of the message middleware cluster in a database of a configuration module after the information of the message middleware cluster is filled, and automatically generating a unique identifier (M _ ID) of the message middleware cluster if the information of the message middleware cluster is successfully stored. For example, the NAME of the message middleware cluster is set to be M _ NAME, the attribute information of the configuration cluster comprises IP addresses M _ IP1\ M _ IP2\ M _ IP3 and a TOPIC NAME M _ TOPIC, and different types of message middleware cluster configurations have different configurations according to the self needs.
The information related to the service module includes: as shown in fig. 3, the administrator logs in the configuration module, enters a service module filing page provided by the configuration module, and fills information related to the service module. The NAME SYSTEM _ NAME and SYSTEM CODE of the service module are well defined, and no CODE and NAME duplication is allowed. And after the name and the code of the service module are filled, clicking to store the information of the service module in a database of the configuration module, and automatically generating a unique identifier (SYSTEM _ ID) of the service module when the storage is successful.
The event type-related information includes: NAME of EVENT _ NAME, encoding EVENT _ CODE, data type of EVENT generation, and specific data field information. Referring to fig. 4, the administrator logs in the configuration module, enters an event type configuration page provided by the configuration module, and fills in information related to the event type. Defining the EVENT NAME, EVENT _ NAME and EVENT _ CODE of the EVENT, not allowing the EVENT CODE and the EVENT NAME to be repeated, and then defining the data type and specific data field information generated by the EVENT. After the EVENT name and the code are filled in, the EVENT type information is stored in a database of a configuration module by clicking and storing, and the unique identifier (EVENT _ ID) of the EVENT type is automatically generated when the EVENT type information is successfully stored
The step of configuring the forwarding rule comprises: creating a forwarding rule and defining: the name of the rule is R, the priority of the rule is L, and the rule state is an enabling state;
and performing a relationship configuration operation: firstly, selecting an EVENT coded as EVENT _ CODE, and carrying out data filtering operation selection on data information corresponding to the EVENT; selecting a message middleware cluster with the NAME of M _ NAME, and performing relation binding on the event and the message middleware cluster; finally, selecting a service module coded as SYSTEM _ CODE, and binding the relation between the message middleware cluster and the service module;
after the relation configuration operation, generating a corresponding forwarding rule; wherein, one forwarding rule records: the corresponding relation of the unique identifier EVENT _ ID of an EVENT, the unique identifier M _ ID of a message middleware cluster, the unique identifiers SYSTEM _ ID of one or more service modules and data filtering information; or, one forwarding rule records: the unique identifier EVENT _ ID of one EVENT, the unique identifiers M _ ID of a plurality of message middleware clusters, the unique identifiers SYSTEM _ ID of one or more service modules and the data filtering information.
Specifically, as shown in fig. 5, the administrator logs in the configuration module, enters a forwarding rule configuration page provided by the configuration module, and configures the forwarding rule. Firstly, a forwarding rule is created, the name of the rule is defined as R, the priority of the rule is defined as L, and the rule state is an enabled state. Event and message middleware cluster relationship binding and message middleware cluster and business system relationship binding may then occur. And the relationship configuration operation is clicked, so that the relationship between the event and message middleware cluster and the relationship between the message middleware cluster and the service system can be bound. Selecting an EVENT with an EVENT CODE being an EVENT _ CODE, then selecting a message middleware cluster named as M _ NAME, seeing the data information corresponding to the EVENT type after selecting the EVENT type, clicking a data filtering operation, checking whether the data to be forwarded and the data field need desensitization treatment, and if not, indicating that the data filtering operation is not performed. Then, a service module coded as SYSTEM _ CODE is selected, where a plurality of service modules may be selected, indicating that the event may be notified to a plurality of service modules for processing. And clicking to determine, the configuration module stores the corresponding relation of the unique identifier (EVENT _ ID) of the EVENT, the unique identifier (M _ ID) of the message middleware cluster, the unique identifier (SYSTEM _ ID) of the service module and the data filtering information into a database.
The step of sending the data of the event to be processed to a target message middleware cluster unit in the message middleware cluster module for storage by the event distribution module based on the target forwarding rule comprises:
the event distribution module filters the data of the event to be processed based on the data filtering information in the target forwarding rule;
and the event distribution module sends the filtered data to a target message middleware cluster unit in the message middleware cluster module for storage based on the target forwarding rule.
Before the step of receiving, by the service module, data of an event to be processed extracted from the message middleware cluster unit and performing event processing on the data, the method further includes:
the service module compares the identified message middleware cluster unit with the message middleware cluster unit identified last time or first time, and judges whether a newly added message middleware cluster unit exists in the identification and/or whether a message middleware cluster with changed configuration information exists;
if the newly added message middleware cluster unit exists, the service module establishes monitoring connection to the newly added message middleware cluster unit and starts to monitor the message of the newly added message middleware cluster unit;
if the message middleware cluster with the changed configuration information exists, the service module monitors the message middleware cluster unit for address change according to the changed cluster configuration information.
In the method, the automobile terminal transmits the generated event message to the message analysis module through the gateway, the message analysis module analyzes the message and then transmits the message to the event distribution module, the event distribution module distributes the event message to each message middleware cluster module, and then each event processing service module processes the corresponding event according to the information of the event message in the corresponding message middleware cluster module. The event type, the message middleware cluster, the service module and the event forwarding rule are managed through the configuration module, and unified management of processing strategies after the terminal events are uploaded to the cloud server is achieved.
The event handling strategy of the centralized management vehicle-mounted terminal after the event is uploaded to the cloud server can achieve event type transparence, message middleware cluster transparence, service module transparence and forwarding rule transparence, and once the cloud server finds the relevant problems of the event and data forwarding, the problems can be quickly located. The management of the events of the vehicle-mounted terminal is not dispersed and complex, the cloud server end has a clear context for the event state of the vehicle terminal, and the information cluster, the service system and the event relation can be dynamically managed and the event data can be dynamically filtered. Meanwhile, the event processing flow is simplified, the event distribution and configuration management are decoupled, the stability and maintainability of the Internet of vehicles platform are improved, and the use experience of a user is improved.
The present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a vehicle-mounted information processing module, implements the steps of the vehicle-mounted event processing method described above.
The invention also provides a cloud server which comprises a memory and a vehicle-mounted information processing module, wherein the memory stores computer readable instructions, and the vehicle-mounted information processing module executes the computer readable instructions to execute the vehicle-mounted event processing method.
The embodiments described above describe only some of the one or more embodiments of the present invention, but those skilled in the art will recognize that the invention can be embodied in many other forms without departing from the spirit or scope thereof. Accordingly, the present examples and embodiments are to be considered as illustrative and not restrictive, and various modifications and substitutions may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims.
Claims (8)
1. A vehicle-mounted event processing method is applied to a vehicle-mounted event processing system, and the system comprises the following steps: the system comprises an event distribution module, a configuration module, a service module and a message middleware cluster module; it is characterized by comprising:
the event distribution module receives the to-be-processed event uploaded by the vehicle-mounted terminal and forwarded by the gateway;
the event distribution module identifies an event type corresponding to the event to be processed based on an interaction protocol;
the event distribution module reads one or more target forwarding rules corresponding to the event type of the event to be processed from the configuration module to determine one or more target message middleware clusters;
the event distribution module sends the data of the event to be processed to a target message middleware cluster unit in a message middleware cluster module for storage based on the target forwarding rule, wherein one target message middleware cluster unit stores the related information of one target message middleware cluster;
the service module reads a forwarding rule corresponding to the service module from the configuration module so as to identify a message middleware cluster unit where a message middleware cluster corresponding to the forwarding rule is located;
and the service module receives the data of the event to be processed sent by the message middleware cluster unit and processes the event.
2. The method of claim 1, wherein the type of the target message middleware cluster is one or more of an activemq middleware cluster, a kafka middleware cluster, a rabbitmq middleware cluster, and a rocktmq middleware cluster.
3. The method of claim 1, further comprising:
inputting information related to the message middleware cluster into a configuration module in advance to generate a unique identifier M _ ID of the message middleware cluster;
inputting information related to each service module into a configuration module in advance to generate a unique identifier SYSTEM _ ID of each service module;
inputting information related to the EVENT type into a configuration module in advance to generate a unique identifier EVENT _ ID of the EVENT type;
forwarding rule configuration is carried out in a configuration module in advance;
the message middleware cluster related information includes: NAME M _ NAME and configuration information of the message middleware cluster, and the configuration information of the message middleware cluster includes: IP address M _ IP and TOPIC name M _ TOPIC;
the information related to the service module includes: the NAME SYSTEM _ NAME and the CODE SYSTEM _ CODE of the service module;
the event type-related information includes: NAME of EVENT _ NAME, encoding EVENT _ CODE, data type of EVENT generation, and specific data field information.
4. The method of claim 3, wherein the step of configuring the forwarding rule comprises:
creating a forwarding rule and defining: the name of the rule is R, the priority of the rule is L, and the rule state is an enabling state;
and performing a relationship configuration operation: firstly, selecting an EVENT coded as EVENT _ CODE, and carrying out data filtering operation selection on data information corresponding to the EVENT; selecting a message middleware cluster with the NAME of M _ NAME, and performing relation binding on the event and the message middleware cluster; finally, selecting a service module coded as SYSTEM _ CODE, and binding the relation between the message middleware cluster and the service module;
after the relation configuration operation, generating a corresponding forwarding rule; wherein, one forwarding rule records: the corresponding relation of the unique identifier EVENT _ ID of an EVENT, the unique identifier M _ ID of a message middleware cluster, the unique identifiers SYSTEM _ ID of one or more service modules and data filtering information; or, one forwarding rule records: the unique identifier EVENT _ ID of one EVENT, the unique identifiers M _ ID of a plurality of message middleware clusters, the unique identifiers SYSTEM _ ID of one or more service modules and the data filtering information.
5. The method of claim 1, wherein the step of sending, by an event distribution module, the data of the event to be processed to a target message middleware cluster unit in the message middleware cluster module for storage based on the target forwarding rule comprises:
the event distribution module filters the data of the event to be processed based on the data filtering information in the target forwarding rule;
and the event distribution module sends the filtered data to a target message middleware cluster unit in the message middleware cluster module for storage based on the target forwarding rule.
6. The method according to claim 1, wherein before the step of the service module receiving the data of the event to be processed extracted from the message middleware cluster unit and performing event processing on the data, the method further comprises:
the service module compares the identified message middleware cluster unit with the message middleware cluster unit identified last time or first time, and judges whether a newly added message middleware cluster unit exists in the identification and/or whether a message middleware cluster with changed configuration information exists;
if the newly added message middleware cluster unit exists, the service module establishes monitoring connection to the newly added message middleware cluster unit and starts to monitor the message of the newly added message middleware cluster unit;
if the message middleware cluster with the changed configuration information exists, the service module monitors the message middleware cluster unit for address change according to the changed cluster configuration information.
7. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when executed by an in-vehicle information processing module, implements the steps of the in-vehicle event processing method according to any one of claims 1 to 6.
8. A cloud server, characterized by comprising a memory and an on-board information processing module, the memory having stored therein computer-readable instructions which, when executed by the on-board information processing module, cause the on-board information processing module to execute the steps of the on-board event processing method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010405731.XA CN111737023B (en) | 2020-05-14 | 2020-05-14 | Vehicle-mounted event processing method, cloud server and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010405731.XA CN111737023B (en) | 2020-05-14 | 2020-05-14 | Vehicle-mounted event processing method, cloud server and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111737023A true CN111737023A (en) | 2020-10-02 |
| CN111737023B CN111737023B (en) | 2024-04-30 |
Family
ID=72647197
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010405731.XA Active CN111737023B (en) | 2020-05-14 | 2020-05-14 | Vehicle-mounted event processing method, cloud server and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111737023B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112214264A (en) * | 2020-10-10 | 2021-01-12 | 交通运输部规划研究院 | AIS interactive operation processing method and device |
| CN113179333A (en) * | 2021-06-30 | 2021-07-27 | 北京航空航天大学 | File transmission and real-time computing system and method for block chain |
| CN113821513A (en) * | 2021-09-18 | 2021-12-21 | 阿里巴巴（中国）有限公司 | Data processing method, device and storage medium |
| CN114629954A (en) * | 2022-03-16 | 2022-06-14 | 上海哔哩哔哩科技有限公司 | Content distribution method and system |
| CN115794444A (en) * | 2023-02-02 | 2023-03-14 | 广州钛动科技股份有限公司 | Event communication method, device, computer equipment and computer readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101477635A (en) * | 2008-12-12 | 2009-07-08 | 华南理工大学 | Embedded RFID middleware based on light-weight ALE |
| CN102761832A (en) * | 2011-04-28 | 2012-10-31 | 中国移动通信集团河南有限公司 | Message distribution method and device |
| KR101303227B1 (en) * | 2013-03-08 | 2013-09-04 | 주식회사 스마트미디어랩 | Announcement system for multiple groups |
| CN103927218A (en) * | 2014-04-30 | 2014-07-16 | 广州唯品会网络技术有限公司 | Event dispatching method and system |
| WO2016054992A1 (en) * | 2014-10-10 | 2016-04-14 | 中兴通讯股份有限公司 | Network data collection system and method |
| US20190266278A1 (en) * | 2018-02-26 | 2019-08-29 | Altibase Corp. | IoT Data Management System and Method |
| CN110445637A (en) * | 2019-07-05 | 2019-11-12 | 深圳壹账通智能科技有限公司 | Event-monitoring method, system, computer equipment and storage medium |
| CN111049753A (en) * | 2019-12-18 | 2020-04-21 | 网易（杭州）网络有限公司 | Message sending method and device, electronic equipment and computer readable medium |
-
2020
- 2020-05-14 CN CN202010405731.XA patent/CN111737023B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101477635A (en) * | 2008-12-12 | 2009-07-08 | 华南理工大学 | Embedded RFID middleware based on light-weight ALE |
| CN102761832A (en) * | 2011-04-28 | 2012-10-31 | 中国移动通信集团河南有限公司 | Message distribution method and device |
| KR101303227B1 (en) * | 2013-03-08 | 2013-09-04 | 주식회사 스마트미디어랩 | Announcement system for multiple groups |
| CN103927218A (en) * | 2014-04-30 | 2014-07-16 | 广州唯品会网络技术有限公司 | Event dispatching method and system |
| WO2016054992A1 (en) * | 2014-10-10 | 2016-04-14 | 中兴通讯股份有限公司 | Network data collection system and method |
| US20190266278A1 (en) * | 2018-02-26 | 2019-08-29 | Altibase Corp. | IoT Data Management System and Method |
| CN110445637A (en) * | 2019-07-05 | 2019-11-12 | 深圳壹账通智能科技有限公司 | Event-monitoring method, system, computer equipment and storage medium |
| CN111049753A (en) * | 2019-12-18 | 2020-04-21 | 网易（杭州）网络有限公司 | Message sending method and device, electronic equipment and computer readable medium |
Non-Patent Citations (1)
| Title |
|---|
| 汪敏;: "基于netlink的linux服务器集群统一外设事件监听机制", 电子设计工程, vol. 24, no. 23, 5 December 2016 (2016-12-05), pages 76 - 78 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112214264A (en) * | 2020-10-10 | 2021-01-12 | 交通运输部规划研究院 | AIS interactive operation processing method and device |
| CN113179333A (en) * | 2021-06-30 | 2021-07-27 | 北京航空航天大学 | File transmission and real-time computing system and method for block chain |
| CN113821513A (en) * | 2021-09-18 | 2021-12-21 | 阿里巴巴（中国）有限公司 | Data processing method, device and storage medium |
| CN114629954A (en) * | 2022-03-16 | 2022-06-14 | 上海哔哩哔哩科技有限公司 | Content distribution method and system |
| CN114629954B (en) * | 2022-03-16 | 2023-11-17 | 上海哔哩哔哩科技有限公司 | Content distribution method, system, device and storage medium |
| CN115794444A (en) * | 2023-02-02 | 2023-03-14 | 广州钛动科技股份有限公司 | Event communication method, device, computer equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111737023B (en) | 2024-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111737023A (en) | Vehicle-mounted event processing method, cloud server and computer-readable storage medium | |
| CN112988485B (en) | Simulation test method and device for electric power Internet of things equipment | |
| CN110659109B (en) | System and method for monitoring openstack virtual machine | |
| CN106210099B (en) | Data processing system and method | |
| CN102594598A (en) | Log management system and implementation method thereof | |
| CN113127199B (en) | Load balancing configuration method, device, equipment and storage medium | |
| CN110008267B (en) | Data processing system and method | |
| CN108833565A (en) | A kind of method, apparatus of monitoring server, server and storage medium | |
| CN105052079A (en) | Accessing multiple converged infrastructure systems | |
| CN112737800A (en) | Service node fault positioning method, call chain generation method and server | |
| CN108877188B (en) | Environment-friendly data concurrent acquisition and multi-network publishing method and device | |
| CN108762846B (en) | Plug-in real-time recommendation method Server and computer-readable storage medium | |
| CN112600719A (en) | Alarm clustering method, device and storage medium | |
| CN107395687B (en) | Equipment monitoring method, device and system and air conditioner | |
| CN113407555B (en) | Operation data updating method and system of equipment handheld terminal | |
| CN110597600A (en) | Method for modifying application configuration parameters of distributed system and distributed system | |
| CN114817671A (en) | Log analysis method and system for air conditioner Internet of things | |
| CN106855888B (en) | Log monitoring system based on Logstash distributed system | |
| CN108960378A (en) | A kind of data download method, system, device and storage medium | |
| CN114418196A (en) | Vehicle dispatching simulation method, device and system | |
| CN112422314A (en) | Method and system for collecting and reporting alarm performance data | |
| CN110837454A (en) | Interface monitoring processing method and server | |
| CN116095180B (en) | Log return routing method, device and storage medium | |
| CN115959004B (en) | Vehicle safety monitoring system and method, vehicle-mounted communication terminal, vehicle and server | |
| CN113726854B (en) | Information processing method and device, storage medium, debugging equipment and vehicle |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |