CN116341560B

CN116341560B - Monitoring strategy adjustment method and system for transportation process safety

Info

Publication number: CN116341560B
Application number: CN202310101719.3A
Authority: CN
Inventors: 庞含; 庞路
Original assignee: Anhui Longding Information Technology Co ltd
Current assignee: Anhui Longding Information Technology Co ltd
Priority date: 2023-02-13
Filing date: 2023-02-13
Publication date: 2024-03-19
Anticipated expiration: 2043-02-13
Also published as: CN116341560A

Abstract

The application discloses a monitoring strategy adjustment method and system, comprising a transportation sending side receiving a monitoring strategy adjustment request, wherein the monitoring strategy adjustment request is used for indicating to create or delete a target monitoring strategy associated with real-time monitoring data of a transportation vehicle; and in response to the monitoring strategy adjustment request, the transportation sending side adjusts the transportation vehicle traveling information of the real-time monitoring data in the monitoring project library and informs the coordination service of yaw of the transportation vehicle traveling information of the real-time monitoring data. The coordination service informs a transport destination side to carry out parallel adjustment on the transport destination side on the traveling information of the transport vehicle of the real-time monitoring data; meanwhile, the transportation sending side also carries out parallel adjustment on the transportation destination side of the transportation vehicle traveling information of the real-time monitoring data, and after all the transportation destination sides finish the parallel adjustment on the transportation destination side, the transportation sending side carries out delay verification, and through the two-step adjustment, the online real-time adjustment monitoring strategy can be realized.

Description

Monitoring strategy adjustment method and system for transportation process safety

Technical Field

The present application relates to the field of computers, and more particularly, to a method and system for adjusting a monitoring policy for transportation safety.

Background

In some scenarios, a monitoring policy table may be used as a storage space for transportation vehicle data (i.e., custom objects of transportation vehicles), and thus the monitoring policy table stores transportation vehicle data for a plurality of transportation vehicles. Of course, it is not the monitoring policy table that the user sees, but rather the real-time monitoring of data or business tables (e.g., orders, acceptance orders, inventory orders, etc.).

The monitoring strategy is used as a key data structure in the monitoring project library system and plays an important role in the adjustment of the monitoring strategy of the monitoring project library system. Quick access to records in a physical monitoring item library table may be achieved through the use of a monitoring policy.

However, the existing monitoring policy adjustment mode has limitations that the monitoring policy can be only created for the whole table data, and the requirement of creating the monitoring policy on the transportation vehicle data of a certain transportation vehicle can not be met, so that the method can not adapt to a multi-transportation vehicle scene.

Therefore, a monitoring strategy pivot table is introduced, and monitoring strategy data in the monitoring strategy pivot table is defined through the travel of the transport vehicle, so that the monitoring strategy is created for semantic analysis results on real-time monitoring data corresponding to the transport vehicle data, and the requirement of creating the monitoring strategy on the transport vehicle data is met.

However, existing monitoring policy adjustments are performed while the system is idle, not in online real-time. Therefore, how to adjust the monitoring strategy online in real time becomes a subject of current research and development.

Disclosure of Invention

In view of the foregoing, an objective of an embodiment of the present application is to provide a monitoring policy adjustment method and related system, so as to implement online real-time adjustment of a monitoring policy.

In order to achieve the above purpose, the embodiment of the present application provides the following technical solutions:

in one aspect, embodiments of the present application provide a monitoring policy adjustment method, including a transportation issue side receiving a monitoring policy adjustment request for instructing to create or delete a target monitoring policy associated with real-time monitoring data of a transportation vehicle; and in response to the monitoring strategy adjustment request, the transportation sending side adjusts the transportation vehicle traveling information of the real-time monitoring data in the monitoring project library and informs the coordination service of the transportation vehicle traveling information of the real-time monitoring data to yaw. The coordination service informs a transport destination side to carry out parallel adjustment on the transport destination side on the transport vehicle traveling information of the real-time monitoring data; meanwhile, the transportation sending side also carries out parallel adjustment on the transportation destination side on the transportation vehicle traveling information of the real-time monitoring data. After all the transportation destination sides finish the parallel adjustment of the transportation destination sides, the transportation sending side performs delay verification. It can be seen that, in this embodiment, after adjusting the travel information of the transport vehicle to the monitoring item library, the monitoring policy adjustment is implemented in two steps: and in the first step, each data access node carries out parallel adjustment on the transport destination side on the transport vehicle traveling information of the real-time monitoring data. After the parallel adjustment of the transport destination side, each data access node can follow up the data access request aiming at the real-time monitoring data, and can be based on the new transport vehicle travelling information; and secondly, after each data access node completes parallel adjustment of the transportation destination side, executing data delay verification, and creating or deleting a target monitoring strategy. Through the two-step adjustment, the online real-time adjustment of the monitoring strategy can be realized.

In one possible design, after receiving the monitoring policy adjustment request and before adjusting the travel information of the transportation vehicle, the transportation sending side will also add access control rights to the real-time monitoring data; the access control authority is used for prohibiting other requests for adjusting the travel information of the transport vehicle of the real-time monitoring data, wherein the other requests refer to the requests related to the adjustment operation of the travel information of the transport vehicle of the real-time monitoring data. And after the data delay verification is completed, the transport issuing side releases the access control authority. In actual operation, there may be other monitoring policy adjustment requests that also indicate to create or delete a monitoring policy for the semantic analysis result on the same real-time monitoring data, and the access control authority may avoid multiple requests to adjust the travel information of the transportation vehicle of the same real-time monitoring data at the same time, so as to avoid confusion of data adjustment.

In one possible design, the above-mentioned parallel adjustment of the transportation destination side may at least include: refreshing the travel information of the transport vehicle of the real-time monitoring data, which is cached at the transport destination side; and after all the transportation tasks in the current transportation task list are finished, notifying the coordination service to finish the parallel adjustment of the transportation destination side. Wherein waiting for the end of the transportation task in the current transportation task list can ensure that the current transportation task (ongoing data operation) is not affected.

In one possible design, the above-described "transport destination side parallel adjustment" may further include the following operations: and setting the monitoring arrangement of the transportation destination side cache and associated with the real-time monitoring data as a failure type. This is because the monitoring schedule at this time is generated before the metadata information is not adjusted, and setting it to be invalid prevents the new monitoring schedule from being used. It should be noted that, although the monitoring arrangement performs the invalidation process, the transportation task in the current transportation task list may still use the invalidation type monitoring arrangement, but the new query request cannot use the invalidation type monitoring arrangement.

In one possible design, the adjusting the transportation vehicle travel information of the real-time monitoring data in the monitoring item library includes at least adjusting a transportation vehicle travel license plate number of the real-time monitoring data in the monitoring item library. Further, for creating the monitoring policy, adjusting the monitoring policy transportation vehicle travel information may specifically include: a: and storing the monitoring strategy transportation vehicle traveling information of the target monitoring strategy into a monitoring project library. B: the type of the target monitoring policy is set as the first monitoring policy. Specifically, the first monitoring policy may be designed to be "in-creation". The monitoring policy, which is in the first monitoring policy, cannot be referenced by the monitoring arrangement. The target monitoring policy type is set as the first monitoring policy because only the monitoring policy transportation vehicle traveling information of the target monitoring policy is saved to the monitoring item library at this time, and the target monitoring policy itself is not actually created successfully. In this case, if the schedule reference is allowed to be monitored, this may result in a query failure. In addition, the first monitoring strategy has other functions in other embodiments, as will be described later herein; whereas for deleting the monitoring policy, adjusting the monitoring policy transport vehicle travel information may specifically include: the type of the target monitoring policy is set as the second monitoring policy. Specifically, the second monitoring policy may be designed as "in delete". More specifically, the type (Category) semantic analysis result value of the monitoring policy transportation vehicle travel table may be set to "delete" means "in deletion". The monitoring policy at the second monitoring policy cannot be referenced by the monitoring arrangement. The target monitoring policy type is set to the second monitoring policy in order to prevent the monitoring arrangement from referencing the monitoring policy to be deleted. Whether deleting or creating the monitoring strategy, the transportation issuing side can adjust the number of the traveling license plate of the transportation vehicle for monitoring the target real-time monitoring data in the project library. The embodiment provides a specific mode for adjusting the travel information of the transport vehicle for monitoring the data in real time in the project library, and the on-line monitoring strategy adjustment is better realized.

In one possible design, the data delay verification at least includes creating a target monitoring policy or deleting a target monitoring policy according to the monitoring policy adjustment request. The data delay verification further includes adjusting a vehicle travel license plate number in the target vehicle data record after creating the target monitoring policy or deleting the target monitoring policy. For creating the target monitoring strategy, the transportation issuing side can query the transportation vehicle data record associated with the target real-time monitoring data in the monitoring strategy table, parallel the data in the target transportation vehicle data record to the target monitoring strategy, and simultaneously adjust the transportation vehicle travelling license plate number in the target transportation vehicle data record. Wherein the target transportation vehicle data record comprises: and a transportation vehicle data record associated with the real-time monitoring data and having an unadjusted transportation vehicle license plate number. And when the target transport vehicle data record is not queried, the transport issuing side sets the type of the target monitoring strategy in the monitoring project library as a normal type, and informs the coordination service. The coordination service may notify the transportation destination side again to refresh the transportation vehicle traveling information of the target real-time monitoring data cached at the transportation destination side, or refresh only the type of the target monitoring policy cached at the transportation destination side; for deleting the target monitoring strategy, after deleting the target monitoring strategy, the data delay verification further comprises deleting the monitoring strategy transportation vehicle traveling information of the target monitoring strategy in the monitoring project library and notifying the coordination service; the coordination service may again inform the destination side to refresh the transport vehicle travel information of the real-time monitoring data cached at the destination side again.

In yet another aspect, an embodiment of the present application provides a data access node, where the data access node has a function of implementing the behavior of the data access node in the actual implementation of the method described above. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.

In still another aspect, an embodiment of the present application provides a monitoring policy adjustment system, including an application node, a monitoring item library node, and the data access node described above, where the data access node has a function of implementing the actual data access node behavior of the method described above. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.

In yet another aspect, the present application provides a computer-readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform the method of the above aspects.

In yet another aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

In yet another aspect, the present application provides a chip system comprising a processor for supporting a data transmission device to perform the functions referred to in the above aspects, e.g. for generating or processing data and/or information referred to in the above methods. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the data transmission device. The chip system may be formed of a chip or may include a chip and other discrete devices.

In the scheme provided by the application, after the travel information of the transport vehicle is adjusted to the monitoring project library, the monitoring strategy adjustment is realized in two steps: and in the first step, each data access node carries out parallel adjustment on the transport destination side on the transport vehicle traveling information of the real-time monitoring data. After the parallel adjustment of the transport destination side, each data access node can follow up the data access request aiming at the real-time monitoring data, and can be based on the new transport vehicle travelling information; and secondly, after each data access node completes parallel adjustment of the transportation destination side, executing data delay verification, and creating or deleting a target monitoring strategy. Through the two-step adjustment, the online real-time adjustment of the monitoring strategy can be realized.

Drawings

Fig. 1 is an exemplary structural diagram of a monitoring policy adjustment system provided in an embodiment of the present application;

FIG. 2 is an exemplary block diagram of a data access node provided in an embodiment of the present application;

FIG. 3 is an exemplary flowchart of a method for adjusting a monitoring policy according to an embodiment of the present application;

FIG. 4 is an exemplary flowchart of another method for adjusting a monitoring policy according to an embodiment of the present application;

fig. 5 is an exemplary flowchart of another monitoring policy adjustment method provided in an embodiment of the present application.

Detailed Description

For purposes of reference and clarity, terms, abbreviations or abbreviations used hereinafter are summarized as follows:

the multi-lease instance architecture can be applied to a variety of scenarios. For example, software as a service (Software As A Service, saaS) mode. In this mode, saaS vendors uniformly deploy application software, and the transport vehicle orders application software services to vendors via the internet and pays fees according to actual needs. The transport vehicle does not need to additionally construct IT foundation setting of enterprises, and operation and maintenance costs are effectively saved. The multi-lease instance architecture uses a monitoring policy table as a storage space of transportation vehicle data (i.e. a custom object of a transportation vehicle), and for facilitating understanding of the technical scheme provided by the application, the monitoring policy table model, the object transportation vehicle travel table and the semantic analysis result transportation vehicle travel table are described herein.

The monitoring policy table model reserves several (e.g., 100, 500, etc.) non-type semantic analysis results as stored semantic analysis results for the transport vehicle data. For example, value 0-value499 in the following table is the above-mentioned no-type semantic analysis result. Meanwhile, the monitoring policy table model also comprises semantic analysis results describing basic information of the transport vehicle data, such as: a transport vehicle ID (transit_id), an object type ID (obj_id), a globally unique identifier (Globally Unique Identifier, GUID), etc.

In addition, the transport vehicle data is defined by a set of transport vehicle travel tables. The main transport vehicle travel table includes an object transport vehicle travel table and a semantic analysis result transport vehicle travel table. Wherein: the object transport vehicle travel table model is shown below. An object transport vehicle travel table for storing basic transport vehicle travel information of transport vehicle data, comprising: a transport vehicle ID, a name (obj_name), an object type ID, and the like;

objects description

obj_id object type ID

TransVehicle_id transport vehicle ID

obj_name object name

The semantic analysis results the transport vehicle travel table model is shown below. The semantic analysis result transport vehicle travel table is used for storing semantic analysis result detailed information of transport vehicle data, and comprises the following components: semantic analysis result ID (syncaxre_id), name (syncaxre_name), type (data_type) and size (data_size), column number of semantic analysis result in the monitoring policy table, and the like.

SyntaxRes description

SyntaxRe_id semantic analysis result ID

TransVehicle_id transport vehicle ID

obj_id object type ID

SyntaxRe_name semantic analysis result name

data_type semantic analysis result type

data_size semantic analysis result size

SyntaxRe_num semantic analysis results column number in monitoring policy table

Assuming that the transport vehicle 101 has custom ACCOUNT objects (ACCOUNT real-time monitoring data), its object transport vehicle travel table is exemplified as follows, its semantic analysis result transport vehicle travel table is exemplified as follows, and the ACCOUNT data objects of the transport vehicle 101 stored in the monitoring policy table are exemplified as follows.

obj_idTransVehicle_idobj_name

201101ACCOUNT

SyntaxRe_idTransVehicle_idobj_idSyntaxRe_namedata_typedata_size

SyntaxRe_num

301101201ACCOUNT_IDint40

302101201ACCOUNT_NAMEvarchar161

303101201ADDRESSvarchar2562

TransVehicle_idobj_idGuidversiondelete_timevalue0value1value2

1012011000001V1nullACCID_1TomNanjing

1012011000002V1nullACCID_2JackShanghai

1012011000003V1nullACCID_3MaryBeijing

101 201 1000004 V1 null ACCID_4 Penny Hongkong

It can be seen that the customization of data objects by the transport vehicle, such as the addition and deletion of semantic analysis results, type changes, etc., can no longer be based on DDL operations on the entity table of the physical monitoring project library, but can be implemented by DML operations on the travel of the transport vehicle. The transport vehicle can modify its object definition at will without affecting other transport vehicles.

It should be noted that, although the transport vehicle data is stored in the monitoring policy table, it is seen to the user that the transport vehicle data is not the monitoring policy table but the real-time monitoring data or the service table (e.g., order table, acceptance table, inventory table, etc.). Such as the ACCOUNT data object of the transport vehicle 101 in the aforementioned monitoring policy table, it is seen to the user that a logical ACCOUNT table is seen.

As in the logical ACCOUNT table to be queried, the IDs, names (names), and addresses (addresses) in all records named "ABC". Its logical SQL statement is exemplified as follows:

SELECT ACCOUNT_ID,ACCOUNT_NAME,ADDRESS

FROM ACCOUNT

WHERE ACCOUNT_NAME＝‘ABC’。

The transport vehicle's logical SQL access based on custom data objects can be ultimately converted to physical SQL access based on data monitoring policy tables by transport vehicle travel description information. The monitoring strategy is used as a key data structure in the monitoring project library system and plays an important role in query optimization of the monitoring project library system. By using a monitoring policy, quick access to records in a physical monitoring item library table can be achieved. The existing monitoring policy adjustment method has the limitation that the monitoring policy can be only established for the whole table data, and the requirement of establishing the monitoring policy on the transportation vehicle data of a certain transportation vehicle can not be met, so that the method can not adapt to the scene of multiple transportation vehicles.

To this end, a monitoring policy pivot table is introduced to meet the need to create a monitoring policy on certain transportation vehicle data. The monitoring policy pivot table structure is shown below, supporting a non-unique monitoring policy and a unique monitoring policy, respectively.

The method comprises the steps of storing string_value, num_value and date_value semantic analysis results of a monitor_strategy pivot table into character strings, numerical values and date type semantic analysis result values respectively, and creating non-unique monitoring strategies on the character strings, numerical values and date type semantic analysis result values; and Unique monitoring strategies are created on the semantic analysis results of the Unique monitor_strategy pivot table.

Monitor_strategy pivot table description

TransVehicle_id transport vehicle ID

obj_id object type ID

SyntaxRe_num semantic analysis results column number in monitoring policy table

The guide records the global guide

string value

num_value digital value

date value

Uniquemonitor_strategy pivot table description

TransVehicle_id transport vehicle ID

obj_id object type ID

SyntaxRe_num semantic analysis results column number in monitoring policy table

The guide records the global guide

string value

num_value digital value

date value

In addition, data in a monitoring policy pivot table is also defined by a set of transport vehicle travel tables including a monitoring policy transport vehicle travel table (monitor_structures) and a monitoring policy semantic analysis result table (monitor_structures_syncres). The model of monitor_strategies is shown below and the model of monitor_strategy_syncres is shown below.

Monitor_strategyes description

Monitor_strategy_id monitoring policy ID

TransVehicle_id transport vehicle ID

obj_id object type ID

Monitor_strategy_name monitoring policy name

Monitor_strategy_type monitoring policy type

Category monitoring policy type

creation time of create_time

update_time adjustment time

monitor_strategy_SyntaxRes description

Monitor_strategy_id monitoring policy ID

TransVehicle_id transport vehicle ID

obj_id object type ID

SyntaxRe_id semantic analysis result ID

Illustratively, assuming that the ACCOUNT data object of the transport vehicle 101 stored in the monitoring policy table is as described above, in the present application, a non-unique monitoring policy is created if the transport vehicle specifies ACCOUNT_NAME semantic analysis results (value 0 semantic analysis results) at the ACCOUNT object. The monitor_strategies travel table (monitor_strategies) is shown below, and the Monitor policy pivot table is as follows:

it should be noted that, the object transportation vehicle travel table, the semantic analysis result transportation vehicle travel table, the monitoring policy transportation vehicle travel table, and the monitoring policy semantic analysis result table all belong to transportation vehicle travel information of real-time monitoring data. For example, the above-mentioned transportation vehicle traveling information all belongs to the ACCOUNT real-time monitoring data, and in addition, the transportation vehicle traveling information of the real-time monitoring data has a transportation vehicle traveling license plate number.

The embodiment of the application provides a monitoring policy adjustment method and a related system (adjustment system, data access node, monitoring policy adjustment system) so as to solve the problem that the creation of a monitoring policy is limited, for example: the monitoring strategy adjustment mode has certain limitation in terms of semantic analysis result types and monitoring strategy types, so that the transportation vehicle can flexibly specify semantic analysis results to create the monitoring strategy, and meanwhile, the on-line creation process of the monitoring strategy is not influenced by the ongoing data operation.

Referring to fig. 1, the monitoring policy adjustment system described above may include an application node 101, a data access node 102, and a monitoring item library node 103 (storing transport vehicle data). In one example, the monitoring policy adjustment system may be specifically a SaaS application system.

The application node 101 is mainly responsible for running the traffic services of the monitoring policy adjustment system. In a high capacity scenario, cluster deployment may be employed. The data access node 102 is mainly responsible for running the monitoring item library access service of the monitoring policy adjustment system, providing a standard SQL interface, accepting the monitoring item library access request of the application node 101, submitting a monitoring item library query (monitoring arrangement) to the monitoring item library node 103, and returning the result to the application node 101. In a high capacity scenario, cluster deployment may be employed. In addition, the data access node 102 may also execute the monitoring policy adjustment method provided in the present application, for example, the monitoring policy adjustment method provided in the embodiments shown in fig. 3-5 below. The monitoring item library node 103 is mainly responsible for data storage access service of the monitoring policy adjustment system, and may use commercial monitoring item library, for example: oracle monitors project library, mySql monitors project library, etc. In a high capacity scenario, cluster deployment may be employed. In a multi-lease scenario, each transport vehicle data is stored at a designated monitoring item library node, which can be designated by deploying configuration information.

In a cluster scenario, the monitoring policy adjustment system may further include a load balancer 104, where the load balancer 104 is mainly responsible for accepting (e.g. logically SQL requests) requests from clients (e.g. transport vehicles) and distributing the requests to application nodes in the application node cluster according to the load situation of each application node 101.

Coordination service: the coordination service is a distributed application program coordination service of distributed and open source codes, and works such as unified naming service, type parallel service, cluster management, distributed application configuration item management and the like are completed. The coordination service is typically deployed on a separate coordination service node.

Fig. 2 illustrates an exemplary structure of the data access node 102 described above, including:

SQL parser 21: is responsible for parsing the SQL query request sent by the application node 101 and generating a syntax tree. The SQL query request herein may include DDLSQL statements and DMLSQL statements. It should be noted that, the execution of the DMLSQL statement is emphasized in the present application, so if no special statement is made, the subsequent SQL query requests all refer to the DMLSQL statement.

Transport vehicle travel and statistics cache 22: is responsible for transportation vehicle travel on the data access node 102 and for statistical information caching, wherein transportation vehicle travel is loaded from the monitoring item library when the monitoring item library access service is started, and statistical information is collected and stored by the data access service in real time. Query analyzer 23: and the system is responsible for carrying out query analysis based on the grammar tree, the travel of the transport vehicle and the statistical information cache to obtain a query analysis result. Monitoring schedule generator 24: it may be responsible for determining the aforementioned target monitoring arrangement. More specifically, the target monitoring arrangement may be generated based on the query analysis results when the optimal monitoring arrangement is not searched. In addition, the monitoring schedule generator 24 may also determine an alternative monitoring schedule for the SQL query request, query the monitoring item library for query costs for each alternative monitoring schedule when there are multiple alternative monitoring schedules, and cache the alternative monitoring schedule with the smallest query cost as the optimal monitoring schedule for the SQL query request. The DML executor 25 is responsible for executing the target monitoring arrangement, receiving the query result returned by the process monitoring item library, and returning the query result to the application node 101. The DDL executer 26 is responsible for executing ddlql statements (DDL requests) sent by the application node 101. The monitoring item library access interface 27 provides an access interface to the various heterogeneous monitoring item libraries. The adjustment system described above may be deployed in the data access node 102 in hardware or software.

The controller/processor 1 may be a general-purpose processor such as a general-purpose Central Processing Unit (CPU), network processor (Network Processor, NP), microprocessor, etc., or may be an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs in the present application. But also digital signal processors (Digital Signal Processor, DSP), field programmable gate arrays (syncxe-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The controller/processor 1 may also be a combination implementing computing functions, e.g. comprising one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

The processor 1 may be used to implement the functionality of the processing unit 202 described previously. The memory 2 stores programs for executing the technical scheme of the present application, and may also store an operating system and other application programs. In particular, the program may include program code including computer-operating instructions. More specifically, the memory 2 may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (randomaccess memory, RAM), other types of dynamic storage devices that can store information and instructions, a disk memory, and so forth. The input device 4 may include a terminal device that receives data and information input by a user, such as a keyboard, mouse, camera, scanner, light pen, voice input terminal device, touch screen, etc. The output device 5 may comprise a terminal device, such as a screen unit, allowing outputting information to a user. The communication interface 3 may comprise a terminal device using any transceiver or the like in order to support controlling the terminal device to communicate with other devices or a communication network. The communication interface 3 may be used to implement the functionality of the communication unit 201 described previously.

It will be appreciated that fig. 2 shows only a simplified design of the control terminal device. In practical applications, the control terminal device may include any number of transmitters, receivers, processors, controllers, memories, communication interfaces, etc., and all control terminal devices that may implement the present application are within the scope of protection of the present application.

The processor 1 executes the program stored in the memory 2 and invokes other devices, which may be used to implement the monitoring policy adjustment method provided in the embodiments shown in fig. 3-5 described below.

FIG. 3 illustrates an exemplary interaction flow of the monitoring policy adjustment method described above, which includes:

s301: the user (transport vehicle) sends a monitoring policy adjustment request to a certain data access node 102 through the monitoring item library access service of the application node 101.

The process may receive a monitoring policy adjustment request by the communication unit 201 as described above. The monitoring policy adjustment request may be used to instruct the creation or deletion of a target monitoring policy associated with semantic analysis results on real-time monitoring data of the transport vehicle. By target monitoring policy is meant a monitoring policy that the monitoring policy adjustment request indicates to create, or a monitoring policy that the monitoring policy adjustment request indicates to delete. The real-time monitoring data indicated in the monitoring policy adjustment request may be referred to as target real-time monitoring data.

More specifically, the user may directly write the monitoring policy adjustment request, or the application node 101 may provide a graphical interface for the user to customize and automatically generate a related monitoring policy adjustment request, and send the monitoring policy adjustment request to the data access service on a certain data access node 102, to trigger a process of adjusting the monitoring policy. In this way, the transport vehicle is able to perform the monitoring policy adjustment operation itself on the graphical interface provided by the application node 101.

For ease of distinction, the data access node that receives the monitoring policy adjustment request may be referred to as the transportation origin side, while the other data access nodes may be referred to as the transportation destination side.

In one example, a standard DDLSQL statement may be used as the monitoring policy adjustment request.

Taking the example of creating a target monitoring policy, the grammar of the DDLSQL statement is defined as follows:

CREATE[UNIQUE]MONITOR_STRATEGYMONITOR_STRATEGY_NAMEON TABLE_NAME(SYNTAXRE_NAME)。

wherein, "monitor_STRATEGY_NAME" characterizes a specific monitoring policy NAME; "TABLE_NAME" characterizes specific real-time monitoring data NAMEs, such as the NAMEs of ACCOUNT real-time monitoring data described previously; SYNTAXRE_NAME characterizes specific semantic analysis results in real-time monitoring data.

The user can specify the real-time monitoring data name and the semantic analysis result in the monitoring policy adjustment request, and adjust the target monitoring policy associated with the specified semantic analysis result. Thus, the real-time monitoring data and the semantic analysis result can be flexibly specified, and the monitoring strategy is created or adjusted on the specified semantic analysis result.

S302: the transportation issuing side adds access control rights to the target real-time monitoring data.

The access control rights may be used to prohibit other requests for adjustments to the transport vehicle travel information for real-time monitoring of data. Other requests herein refer to requests related to adjustment operations for the travel information of the transport vehicle for the above-mentioned real-time monitoring data. For example, in actual operation, there may be other monitoring policy adjustment requests that also indicate to create or delete a monitoring policy for semantic analysis results on the same real-time monitoring data, and the access control authority may avoid multiple requests to adjust the travel information of the transportation vehicle of the same real-time monitoring data at the same time, thereby avoiding confusion of data adjustment. In one example, the access control rights may be specifically a DDL lock, and the transport issuer side may acquire the DDL lock from a coordination service deployed on the coordination service node to prevent different DDLs from concurrently operating transport vehicle travel information for the same real-time monitoring data.

In one example, step 302 may be performed by the processing unit 202 at the point of delivery origin.

S303: and (5) transporting the transportation vehicle traveling information of the target real-time monitoring data in the sending side adjustment monitoring project library.

Step 303 may be performed by the processing unit 202 at the delivery origin side. The processing unit 202 may instruct the communication unit 201 to submit an adjustment request to the monitoring item library to adjust the transportation vehicle travel information of the target real-time monitoring data.

The transportation vehicle traveling information of the real-time monitoring data is stored in the monitoring item library, and the transportation vehicle traveling information of the real-time monitoring data is cached at each data access node at the transportation destination side. In this step, the adjustment of the travel information of the transport vehicle of the real-time monitoring data in the monitoring item library is performed. In the subsequent step, each data access node also adjusts the travel information of the transport vehicle of the target real-time monitoring data cached at the transport destination side.

In practice, this step is mainly used to adjust the monitoring policy transportation vehicle travel information of the target monitoring policy, and the monitoring policy transportation vehicle travel information of the target monitoring policy is part of the transportation vehicle travel information of the target real-time monitoring data. Therefore, the adjustment of the travel information of the transport vehicle in the monitoring strategy also belongs to the category of the travel information of the transport vehicle of the real-time monitoring data of the adjustment target.

More specifically, the foregoing mentions that the monitoring policy adjustment request may indicate the creation or deletion of the target monitoring policy.

For creating a monitoring strategy, adjusting the monitoring strategy transportation vehicle travel information may specifically include:

a: storing the traveling information of the monitoring strategy transportation vehicle of the target monitoring strategy into a monitoring project library; more specifically, the monitoring policy transportation vehicle travel information of the target monitoring policy may be saved to monitor_strategyes and monitor_strategy_synctaxres tables of the monitoring item library.

B: the type of the target monitoring policy is set as the first monitoring policy. Specifically, the first monitoring policy may be designed to be "in-creation". The monitoring policy, which is in the first monitoring policy, cannot be referenced by the monitoring arrangement.

Illustratively, assuming that the ACCOUNT data object of the transport vehicle 101 stored in the monitoring policy table is as described above, the user's monitoring policy adjustment request instructs the creation of a non-unique monitoring policy at the ACCOUNT_NAME semantic analysis result (value 0 semantic analysis result) of the ACCOUNT object. Then in this step the monitoring policy transport vehicle travel table (Monitor _ lists) monitors the target monitoring policies in the project library. Wherein "creating" of the type (Category) semantic analysis result means "in creation".

The target monitoring policy type is set as the first monitoring policy because only the monitoring policy transportation vehicle traveling information of the target monitoring policy is saved to the monitoring item library at this time, and the target monitoring policy itself is not actually created successfully. In this case, if the schedule reference is allowed to be monitored, this may result in a query failure. In addition, the first monitoring strategy has other roles in other embodiments, as will be described later herein.

Whereas for deleting the monitoring policy, adjusting the monitoring policy transport vehicle travel information may specifically include: the type of the target monitoring policy is set as the second monitoring policy. Specifically, the second monitoring policy may be designed as "in delete". More specifically, the type (Category) semantic analysis result value of the monitoring policy transportation vehicle travel table may be set to "delete" means "in deletion". The monitoring policy at the second monitoring policy cannot be referenced by the monitoring arrangement. The target monitoring policy type is set to the second monitoring policy in order to prevent the monitoring arrangement from referencing the monitoring policy to be deleted.

C: whether deleting or creating the monitoring strategy, the transportation issuing side can adjust the number of the traveling license plate of the transportation vehicle for monitoring the target real-time monitoring data in the project library. For example, the carrier vehicle travel license plate number of the target real-time monitoring data may be adjusted from V1 to V2.

S304: the transportation sending side informs the coordination service target to monitor the data transportation vehicle traveling information in real time to generate yaw.

More specifically, the coordination service target may be notified that the vehicle traveling license plate number of the real-time monitoring data is yawed. Step 304 may be performed by the processing unit 202 on the transport origin side instructing the communication unit 201.

S305: the coordination service informs the transportation destination side of carrying out parallel adjustment on the transportation destination side on the transportation vehicle traveling information of the target real-time monitoring data.

More specifically, the data access service deployed on each destination side will monitor the coordination service for a yaw notification of travel of the transport vehicle, and when the yaw notification of travel of the transport vehicle is monitored, the destination side is adjusted in parallel. The listening mechanism is various and is provided by the coordination service and is not discussed in detail in this scenario.

S306: the transport destination side (data access service on) carries out parallel adjustment on the transport destination side on the transport vehicle travel information of the target real-time monitoring data.

In one example, the "destination-side parallel adjustment" may include at least the steps of:

a: and refreshing the travel information of the transport vehicle of the target real-time monitoring data, which is cached at the transport destination side.

The specific implementation mode of refreshing can be as follows: and replacing the transportation vehicle traveling information of the target real-time monitoring data cached at the transportation destination side by using the transportation vehicle traveling information of the target real-time monitoring data in the monitoring project library. Before refreshing, the destination side of each data access node transmits the target real-time monitoring data to the traveling license plate number V1 of the transport vehicle, and after refreshing, the traveling license plate number V2 of the transport vehicle is obtained.

B: a current shipping task list is obtained.

The transportation task in the current transportation task list is the transportation task being performed.

C: wait for all transport tasks in the current transport task list to end (normal end or timeout end).

Waiting for the end of the transportation task in the current transportation task list can ensure that the current transportation task (ongoing data operation) is not affected, and enhance the user experience. In one example, after all of the transportation tasks in the current transportation task list are completed, the transportation destination side may notify the coordination service to complete the transportation destination side parallel adjustment. And the coordination service may set the transport vehicle travel parallel adjustment type on the transport destination side to complete according to the notification on the transport destination side. More specifically, the coordination service may maintain an adjustment type list, set the type value of the transport destination side in the list, for which parallel adjustment of the travel of the transport vehicle has been completed, to 1, and set the type value of the transport destination side, for which the coordination service is not notified, to 0.

It should be noted that the transportation task may use a monitoring arrangement, which is generated based on transportation vehicle travel information of real-time monitoring data. If a monitoring schedule is generated based on the travel information of a transport vehicle for a real-time monitoring data, the monitoring schedule may be considered to be associated with the real-time monitoring data. For example, in response to a query request, a data access node needs to query the real-time monitoring data a, and then generates a monitoring schedule based on the travel information of the transportation vehicle of the real-time monitoring data a (i.e., generates the monitoring schedule associated with the real-time monitoring data a).

After the inquiry is finished, the data access node caches the generated monitoring arrangement at the transportation destination side so that the monitoring arrangement can be directly used when the same inquiry request is received, and the inquiry efficiency is improved.

Thus, in general, each data access node has multiple monitoring schedules for its destination side cache, so to speak, the data access node maintains a pool of monitoring schedules. Assuming that before the traveling information of the transport vehicle of the target real-time monitoring data is not adjusted, the traveling license plate number of the transport vehicle is V1, and after the adjustment, the traveling license plate number of the transport vehicle is V2.

It is apparent that before performing the above-described operation a, the monitoring schedule associated with the target real-time monitoring data, which is cached by each data access node, is generated based on the old transportation vehicle travel information of the target real-time monitoring data (the monitoring schedule generated based on the old transportation vehicle travel information may be referred to as an old monitoring schedule). Alternatively, the old monitoring schedule is generated based on the V1 version of the transportation vehicle travel information. And the monitoring arrangement associated with the target real-time monitoring data used in the current shipping task list to perform the shipping task is also based on version V1.

Because of the online adjustment monitoring policy, each data access node is likely to receive a new query request, to avoid the old monitoring arrangement being used by the new SQL query request, in one example, the "transport destination side parallel adjustment" described above may further include the following operations: the monitoring schedule (typically, an SQL execution plan) associated with the target real-time monitoring data, which is cached at the transportation destination side, is set to be of the failure type.

That is, old monitoring is arranged as a failure process. It should be noted that, although the old monitoring arrangement is invalidated, the transportation tasks in the current transportation task list may still use the old monitoring arrangement, but the new query request cannot use the old monitoring arrangement.

At the same time, the data access node may generate a monitoring schedule based on the new version of the transportation vehicle travel information (the monitoring schedule generated based on the new version of the transportation vehicle travel information may be referred to simply as a new monitoring schedule). The new SQL query request may use the new monitoring arrangement.

It should also be noted that the monitoring arrangement will ultimately translate into operations on the transport vehicle data records in the monitoring policy table.

And each transport vehicle data record stores the corresponding real-time monitoring data of the number of the traveling license plate of the transport vehicle. After operation, the vehicle license plate number in the vehicle data record will be adjusted to the vehicle license plate number upon which the monitoring arrangement is based.

Assuming that the data in the first transport vehicle data record is changed by the old monitoring arrangement, its value at version semantic analysis results is still V1. And the data in the third and fourth transport vehicle data records are modified by the new monitoring arrangement, then their values at the version semantic analysis result are adjusted to V2. The adjusted transport vehicle data record is shown below.

For the case of newly built target monitoring strategies, since the related information of the target monitoring strategies is not available in the old version, the transport vehicle data modified by the old monitoring arrangement cannot be parallel to the monitoring strategy pivot table, and the parallel can be completed in the subsequent data delay. The transport vehicle data modified by the new monitoring arrangement can be parallel to the monitoring policy pivot table.

Step 306 may be performed by the processing unit 202 on the destination side, wherein the notification coordination service may be instructed by the processing unit 202 on the destination side to complete its communication unit 201.

S307: and the transportation sending side carries out parallel adjustment on the transportation destination side on the transportation vehicle traveling information of the target real-time monitoring data.

Similarly to the transport destination side, the transport origin side also requires parallel adjustment of the transport destination side. Therefore, the transportation origin side also performs operations such as refreshing transportation vehicle travel information of the target real-time monitoring data cached at the transportation destination side, waiting for all transportation tasks in the current transportation task list to end, setting the monitoring schedule associated with the target real-time monitoring data cached at the transportation destination side to be of a failure type, and the like. As to whether or not the coordination service is notified after all the transportation tasks in the current transportation task list are ended, flexible design can be performed. The delivery destination side may be designed to notify the coordination service after completion of the parallel adjustment of the delivery destination side, or may be designed not to notify.

Step 307 may be performed by the processing unit 202 on the transport origin side, wherein the notification coordination service may be instructed by the processing unit 202 on the transport origin side to complete its communication unit 201.

S308: after all the transportation destination sides finish the parallel adjustment of the transportation destination sides, the transportation sending side performs delay verification.

In one example, the transport origin side may continue to query the coordination service for transport vehicle travel parallel adjustment types at the transport destination side until all transport vehicle travel parallel adjustment types at the transport destination side are complete, and then perform the data delay verification. Of course, in other embodiments, the delay verification may also be performed by one of the shipping destination sides. The data delay verification includes at least: and creating a target monitoring strategy according to the monitoring strategy adjustment request, or deleting the target monitoring strategy according to the monitoring strategy adjustment request. How to perform the data delay verification will be specifically described later herein for both the creation and deletion cases. The transport issue side may initiate a deferred task for deferred verification.

S309: after the delay verification is completed, the transport issuing side releases the access control rights. Since the creation or deletion of the monitoring policy is completed after the delay verification is completed, the access control authority can be released.

In other examples of the present invention, after completion of the delay verification, the transport issuer may return the adjustment results to the corresponding application node. More specifically, the adjustment results may include information that characterizes the success or failure of the adjustment. Of course, if the adjustment fails, the adjustment result may also include a failure cause.

Steps 308 and 309 may be completed by the processing unit 202 on the delivery origin side instructing the communication unit 201.

Therefore, in the scheme provided by the application, after the travel information of the transport vehicle is adjusted to the monitoring project library, the monitoring strategy adjustment is realized in two steps: in the first step, each data access node carries out parallel adjustment on the transport destination side on the transport vehicle travelling information of the real-time monitoring data, and in the parallel adjustment on the transport destination side, the end of the transport task in the current transport task list is waited, so that the execution of the current transport task is not influenced. After the parallel adjustment of the transport destination side, each data access node can follow up the data access request aiming at the real-time monitoring data, and can be based on the new transport vehicle travelling information; and secondly, after each data access node completes parallel adjustment of the transportation destination side, executing data delay verification, and creating or deleting a target monitoring strategy. Through the two-step adjustment, the online real-time adjustment monitoring strategy can be realized, meanwhile, the ongoing data operation of the current transportation task is not affected, and the use experience of a user is enhanced.

The steps of creating a monitoring policy and deleting a monitoring policy will be described in more detail below.

FIG. 4 illustrates an exemplary interaction flow of the above monitoring policy adjustment method when creating a target monitoring policy, including:

S401-S402 are the same as S301-S302 described above, and are not described in detail herein.

S403: the transportation origin side saves the monitoring policy transportation vehicle travel information of the target monitoring policy to the monitoring item library, wherein the type of the target monitoring policy is set to "in-process" (first monitoring policy). The related description is referred to the description of the aforementioned S303 section, and will not be repeated here.

S404: and (5) adjusting the traveling license plate number of the transport vehicle for monitoring the target real-time monitoring data in the project library at the transport issuing side. For example, the carrier vehicle travel license plate number of the target real-time monitoring data may be adjusted from V1 to V2.

S405 to S408 are the same as S304 to S307 described above, and are not described here.

S409: and inquiring a transport vehicle data record associated with the target real-time monitoring data in the monitoring policy table at the transport issuing side, paralleling the data in the target transport vehicle data record to the target monitoring policy, and simultaneously adjusting the number of the traveling license plate of the transport vehicle in the target transport vehicle data record.

S409 starts with delay data adjustment. The transport issue side may initiate a deferred task execution deferred data adjustment.

The deferred task may determine which monitoring policies require deferred verification based on the type. Since the type of the target monitoring policy is currently "in creation," the deferred task may determine that the target monitoring policy requires deferred verification based on its type. Of course, in other examples, a table may be created that records the monitoring policies to be created and deleted.

The target transport vehicle data record includes: and (3) a transport vehicle data record associated with the real-time monitoring data and having an unadjusted transport vehicle running license plate number. For example, assume that the carrier vehicle travel license plate number of the target real-time monitoring data is adjusted from V1 to V2. Referring to the above, if the number of the traveling license plate of the transportation vehicle data record is V2, which indicates that the record has been adjusted to the monitoring policy pivot table, the delay task does not perform any operation on the record. If the vehicle number of the vehicle travel license plate of the vehicle data record is not V2, it is indicated that the vehicle data record is not adjusted to the monitoring policy staging table. That is, in the above, the traveling license plate number of the transportation vehicle of the two transportation vehicle data records of the hatched portion, that is, the target transportation vehicle data record, is V1.

The delay task of the first data node will adjust the semantic analysis result value related to the target monitoring policy to the monitoring policy pivot table in the two transportation vehicle data records marked with the shadows. Assuming that the semantic analysis result of the target monitoring policy association is "value0", ACCID_1 and ACCID_2 therein are adjusted to the monitoring policy pivot table. The adjusted monitoring policy pivot table is shown below. At the same time, the delay task also modifies the vehicle license plate number of the two vehicle data records, identifying that it has been adjusted using the new vehicle travel, the modified vehicle data records being as follows.

In one example, to prevent a deferral task from operating a transport vehicle data record concurrently with a normal DML, the deferral task may use select running ate to add a row lock to the transport vehicle data record. Select forudate is a standard DML statement to add a line lock to a record.

S410: the transportation sending side sets the type of the target monitoring strategy in the monitoring project library to be a normal type, and notifies the coordination service.

When the delay task can not inquire the related transportation vehicle data records with the license plate number smaller than V2, the fact that all transportation vehicle data records related to the target real-time monitoring data are adjusted by using the new version transportation vehicle traveling information is explained, and the delay task created by the monitoring strategy is completed. Taking the monitoring strategy transportation vehicle traveling table of the target monitoring strategy as an example, after the type is changed, the monitoring strategy transportation vehicle of the target monitoring strategy travels.

When the coordination service is notified, the coordination service target monitoring policy type can be notified to be adjusted, and the coordination service target real-time monitoring data transport vehicle travel information can also be notified to be adjusted. The coordination service may again inform the transportation destination side to refresh the transportation vehicle traveling information of the target real-time monitoring data cached at the transportation destination side again or refresh only the type of the target monitoring policy cached at the transportation destination side. In the present refreshing, the step B and the step C in the parallel adjustment of the transportation destination side may not be executed. In other embodiments of the present application, the number of monitoring policy records per adjustment or deletion may be limited. For example, the number of monitoring policy records per adjustment or deletion may be limited to a maximum of 1000. The delay task can adjust 1000 monitoring policy records each time, for example, up to 1000 upper limits, and the same operation is performed again. This is to take into account that each adjustment is to generate a log, which would be caused to be large if the record of adjustment data is large, affecting performance. Similarly, for the adjustment of the data record of the transport vehicle in the monitoring policy table, the maximum number of each adjustment may be defined, which is not described herein.

S411: after the delay verification is completed, the transport issuing side releases the access control rights.

S411 is the same as S309, and will not be described here again.

S411 and S410 may be executed simultaneously or sequentially.

Steps 409 to 411 may be instructed by the processing unit 202 at the transport origin side to be completed by the communication unit 201.

FIG. 5 illustrates an exemplary interaction flow of the monitoring policy adjustment method described above when deleting a target monitoring policy, including:

S501-S502 are the same as S401-S402 or S301-S302 described above, and are not described here.

S503: the transportation issuer sets the type of the target monitoring policy in the monitoring item library to "in delete" (second monitoring policy). The related description is referred to the description of the aforementioned S303 section, and will not be repeated here.

S504: and (5) adjusting the traveling license plate number of the transport vehicle for monitoring the target real-time monitoring data in the project library at the transport issuing side. For example, the carrier vehicle travel license plate number of the target real-time monitoring data may be adjusted from V1 to V2.

S505-S508 are the same as S405-S408 or S304-307 described above, and are not described here.

S509: and inquiring a transport vehicle data record associated with the target real-time monitoring data in the monitoring policy table at the transport issuing side, and adjusting the number of a transport vehicle travelling license plate in the target transport vehicle data record.

For example, assume that the carrier vehicle travel license plate number of the target real-time monitoring data is adjusted from V1 to V2. Referring to the above, the transportation vehicle running license plate number of all transportation vehicle data records associated with the target real-time monitoring data may be adjusted to V2. Since the target monitoring policy needs to be deleted in this embodiment, it is not necessary to parallel data in the target real-time monitoring data to the target monitoring policy.

S509 starts to adjust for delay data. The transport issue side may initiate a deferred task execution deferred data adjustment.

The deferred task may determine which monitoring policies require deferred verification based on the type. Since the type of the target monitoring policy is currently "in delete", the deferred task may determine that the target monitoring policy requires deferred verification according to its type. In one example, to prevent a deferral task from operating a transport vehicle data record concurrently with a normal DML, the deferral task may use select running ate to add a row lock to the transport vehicle data record. Select forudate is a standard DML statement to add a line lock to a record.

S510: the transportation issue side deletes the transportation vehicle data record in the pivot table related to the target monitoring policy.

Assume that a pivot table is shown below, wherein "num_value" semantic analysis results are associated with a target monitoring policy. When deleting the target monitoring strategy, deleting the transport vehicle data in the "num_value" semantic analysis result, and deleting the perspective table as follows.

And after the transport vehicle data related to the target monitoring strategy is not deleted in the monitoring strategy pivot table, completing the delay task of deleting the monitoring strategy.

S511: and deleting the traveling information of the transport vehicles of the monitoring strategies of the target monitoring strategies in the monitoring project library at the transport sending side, and informing the coordination service that the traveling information of the transport vehicles of the target real-time monitoring data is adjusted.

The coordination service may inform the destination side to refresh the transport vehicle travel information of the target real-time monitoring data cached at the destination side again. In the present refreshing, the step B and the step C in the parallel adjustment of the transportation destination side may not be executed.

S512: after the delay verification is completed, the transport issuing side releases the access control rights.

S511 and S512 may be executed simultaneously or sequentially.

Steps 509 to 512 may be instructed by the processing unit 202 of the data access node to be completed by the communication unit 201.

In other embodiments of the present application, a type query interface for data delay verification may also be provided, and a user may query the monitoring policy adjustment progress. In addition, a query display interface for the semantic analysis result selectivity of the real-time monitoring data can be provided, the transport vehicle can query one semantic analysis result of the real-time monitoring data through the query display interface before creating the monitoring strategy, the number of different values of the semantic analysis result is displayed, if the number of different values of the semantic analysis result is large, the description selectivity is good, and if the number of different values is small, the selectivity is poor. The user can make a reference to more effectively assist the transport vehicle in completing the monitoring policy creation. Those skilled in the art will appreciate that various modifications and improvements can be made to the disclosure. For example, the various devices or components described above may be implemented in hardware, or may be implemented in software, firmware, or a combination of some or all of the three.

A flowchart is used in this disclosure to describe the steps of a method according to an embodiment of the present disclosure. It should be understood that the steps that follow or before do not have to be performed in exact order. Rather, the various steps may be processed in reverse order or simultaneously. Also, other operations may be added to these processes.

Those of ordinary skill in the art will appreciate that all or a portion of the steps of the methods described above may be implemented by a computer program to instruct related hardware, and the program may be stored in a computer readable storage medium, such as a read only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module/unit in the above embodiment may be implemented in the form of hardware, or may be implemented in the form of a software functional module. The present disclosure is not limited to any specific form of combination of hardware and software.

Unless defined otherwise, all terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

The foregoing is illustrative of the present disclosure and is not to be construed as limiting thereof. Although a few exemplary embodiments of this disclosure have been described, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of this disclosure. Accordingly, all such modifications are intended to be included within the scope of this disclosure as defined in the claims. It is to be understood that the foregoing is illustrative of the present disclosure and is not to be construed as limited to the specific embodiments disclosed, and that modifications to the disclosed embodiments, as well as other embodiments, are intended to be included within the scope of the appended claims. The disclosure is defined by the claims and their equivalents.

In the description of the present specification, reference to the terms "one embodiment," "some embodiments," "illustrative embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

While embodiments of the present invention have been shown and described, it will be understood by those of ordinary skill in the art that: many changes, modifications, substitutions and variations may be made to the embodiments without departing from the spirit and principles of the invention, the scope of which is defined by the claims and their equivalents.

Claims

1. A method for adjusting a monitoring policy for safety of a transportation process, which is applied to a transportation source side, comprising:

receiving a monitoring policy adjustment request, wherein the monitoring policy adjustment request is used for indicating to create or delete a target monitoring policy associated with a semantic analysis result on real-time monitoring data of the transport vehicle;

responding to the monitoring strategy adjustment request, and adjusting the traveling information of the transportation vehicle of the real-time monitoring data in the monitoring project library;

notifying a coordination service that the traveling information of the transport vehicle with the real-time monitoring data is yawed; the coordination service is at least used for informing a transportation destination side to carry out transportation destination side parallel adjustment on transportation vehicle traveling information of the real-time monitoring data;

carrying out parallel adjustment on the transport destination side on the transport vehicle travelling information of the real-time monitoring data;

After all the transportation destination sides finish the parallel adjustment of the transportation destination sides, carrying out data delay verification;

after receiving the monitoring policy adjustment request, before adjusting the transportation vehicle travel information, further comprising: adding access control rights to the real-time monitoring data; the access control authority is used for prohibiting other requests from adjusting the travel information of the transport vehicle of the real-time monitoring data;

after the data delay verification is completed, the method further comprises: releasing the access control authority;

the destination-side parallel adjustment includes at least:

refreshing the travel information of the transport vehicle of the real-time monitoring data, which is cached at the transport destination side;

after all the transportation tasks in the current transportation task list are finished, notifying the coordination service to finish the parallel adjustment of the transportation destination side;

the data delay verification at least comprises the steps of creating a target monitoring strategy or deleting the target monitoring strategy according to the monitoring strategy adjustment request.

2. The method of claim 1, wherein the destination-side parallel adjustment further comprises:

the monitoring schedule associated with the real-time monitoring data is set to be disabled.

3. The method of claim 2, wherein said adjusting the transport vehicle travel information of said real-time monitoring data in the monitoring item library comprises at least: and adjusting the traveling license plate number of the transport vehicle with the real-time monitoring data in the monitoring project library.

4. The method of claim 3, wherein,

if the monitoring policy adjustment request is used for indicating to create a target monitoring policy, the adjusting the traveling information of the transportation vehicle of the real-time monitoring data in the monitoring item library further includes:

storing the monitoring strategy transportation vehicle traveling information of the target monitoring strategy into the monitoring project library; the type of the target monitoring strategy in the monitoring strategy transportation vehicle traveling information is a first monitoring strategy;

if the monitoring policy adjustment request is used for indicating to delete the target monitoring policy, the adjusting the traveling information of the transportation vehicle of the real-time monitoring data in the monitoring item library further includes:

setting the type of the target monitoring strategy in the monitoring project library as a second monitoring strategy;

the monitoring policy of the type first monitoring policy or the second monitoring policy cannot be used by the monitoring arrangement.

5. The method of claim 4, wherein creating the target monitoring policy comprises:

Inquiring a transport vehicle data record associated with the real-time monitoring data in a monitoring policy table;

parallel-running data in a target transport vehicle data record to the target monitoring strategy; the target transport vehicle data record includes: a transportation vehicle data record associated with the real-time monitoring data and having an unadjusted transportation vehicle travel license plate number;

after creating the target monitoring strategy or deleting the target monitoring strategy, the data delay verification further comprises adjusting a transport vehicle running license plate number in the target transport vehicle data record;

if the monitoring policy adjustment request is used for indicating to create a target monitoring policy, after the number of the traveling license plate of the transport vehicle in all the target transport vehicle data records is adjusted, the data delay verification further comprises:

setting the type of the target monitoring strategy in the monitoring project library as a normal type, and notifying the coordination service;

if the monitoring policy adjustment request is used for indicating to delete the target monitoring policy, after deleting the target monitoring policy, the data delay verification further includes:

deleting the traveling information of the monitoring strategy transportation vehicle of the target monitoring strategy in the monitoring project library, and notifying the coordination service;

The coordination service is also used for informing the transportation destination side to refresh transportation vehicle traveling information of the real-time monitoring data cached at the transportation destination side.

6. A monitoring policy adjustment system for transportation process safety, comprising:

a receiving unit configured to receive a monitoring policy adjustment request, where the monitoring policy adjustment request is configured to instruct creation or deletion of a target monitoring policy associated with a semantic analysis result on real-time monitoring data of a transport vehicle;

a processing unit for:

in the aspect of carrying out parallel adjustment of the transport destination side on the transport vehicle traveling information of the real-time monitoring data, the processing unit is specifically configured to:

in terms of a transport destination side parallel adjustment of transport vehicle travel information of the real-time monitoring data, the processing unit is further configured to: setting a monitoring schedule associated with the real-time monitoring data to fail; in terms of data delay verification, the processing unit is specifically configured to: and creating a target monitoring strategy or deleting the target monitoring strategy according to the monitoring strategy adjustment request.

7. The system of claim 6, wherein in adjusting the transport vehicle travel information of the real-time monitoring data in the monitoring item library, the processing unit is specifically configured to: and adjusting the traveling license plate number of the transport vehicle with the real-time monitoring data in the monitoring project library.

8. The system of claim 7, wherein if the monitoring policy adjustment request is for indicating creation of a target monitoring policy, the processing unit is further specifically configured to, in adjusting the transportation vehicle travel information of the real-time monitoring data in the monitoring item library:

if the monitoring policy adjustment request is used for indicating to delete the target monitoring policy, in the aspect of adjusting the travel information of the transportation vehicle of the real-time monitoring data in the monitoring item library, the processing unit is specifically further configured to: setting the type of the target monitoring strategy in the monitoring project library as a second monitoring strategy; the monitoring policy of the type of the first monitoring policy or the second monitoring policy cannot be used by the monitoring arrangement;

in the aspect of creating the target monitoring policy, the processing unit is specifically configured to:

parallel-running data in a target transport vehicle data record to the target monitoring strategy; the target transport vehicle data record includes: and a transportation vehicle data record associated with the real-time monitoring data and having an unadjusted transportation vehicle license plate number.

9. The system of claim 8, wherein in terms of the data delay verification, the processing unit is further specifically configured to: and after the target monitoring strategy is created or deleted, adjusting the number of the traveling license plate of the transport vehicle in the target transport vehicle data record.

10. The system of claim 9, wherein the system comprises a plurality of sensors,

in the aspect of the data delay verification, if the monitoring policy adjustment request is used for indicating to create a target monitoring policy, the processing unit is specifically further configured to:

after the number of the traveling license plate of the transport vehicle in all the target transport vehicle data records is adjusted, setting the type of the target monitoring strategy in the monitoring project library as a normal type, and notifying the coordination service;

in the aspect of the data delay verification, if the monitoring policy adjustment request is used for indicating to delete the target monitoring policy, the processing unit is specifically further configured to: after deleting the target monitoring strategy, deleting the monitoring strategy transportation vehicle traveling information of the target monitoring strategy in the monitoring project library, and notifying the coordination service;