WO2023186154A1

WO2023186154A1 - Data transmission system and method

Info

Publication number: WO2023186154A1
Application number: PCT/CN2023/085769
Authority: WO
Inventors: 石宜平; 高磊; 方崇荣; 吕彪; 祝顺民; 蒋江伟; 程鹏; 陈积明
Original assignee: 浙江大学
Priority date: 2022-04-02
Filing date: 2023-03-31
Publication date: 2023-10-05
Also published as: CN114885020B; CN114885020A

Abstract

Embodiments of the present invention provide a data transmission system and method. The data transmission system comprises: a task distribution node configured to issue a task set corresponding to a first subscription relationship to a device proxy node according to the first subscription relationship with the device proxy node; the device proxy node configured to establish a first subscription relationship for the task distribution node according to a second subscription relationship with a device node, and in a case of obtaining the task set corresponding to the first subscription relationship from the task distribution node, issue a task in the task set to the corresponding device node according to the second subscription relationship with the device node; and the device node configured to obtain the task issued by the device proxy node according to the second subscription relationship with the device proxy node. Due to the fact that the device proxy node is added, the device node can subscribe a task from the device proxy node, the task is subscribed to the task distribution node by means of the device proxy node, and the use amount of communication resources of the task distribution node is reduced.

Description

Data transmission system and method

This application claims priority to the Chinese patent application filed with the China Patent Office on April 2, 2022, with the application number 202210345992.6 and the application title "Data transmission system and method", the entire content of which is incorporated into this application by reference.

Technical field

The embodiments of this specification relate to the field of data processing technology, and in particular, to a data transmission system.

Background technique

The functions of task distribution and error recovery are essential in a system composed of large-scale terminals and servers. In this type of system, it is usually necessary to distribute tasks to different terminals for execution at a high frequency and complete the feedback of the results. Once an error occurs on the terminal, the task needs to be retried in a timely manner. In this process, a task belongs to a topic, and the terminal obtains the task issued by the topic in the form of a change set by subscribing to the topic. Task distribution uses the subscription relationship between the device and the topic to deliver the dispatched task to the target terminal in a timely manner, confirm the implementation of the task, and obtain feedback; when the task is issued for execution, it may be due to errors in the terminal device or the terminal device is offline. As a result, the total task execution fails, so task failure errors that occur on the terminal need to be discovered in time. After the terminal error is discovered, it needs to be retried with certain logic to achieve error recovery to maintain the normal operation of the entire configuration distribution system. Therefore, methods of task distribution and error recovery are crucial to configuring the distribution domain.

However, as the complexity of the system increases and the scale continues to expand, large-scale terminal scenarios need to accommodate massive terminals, and massive terminals mean massive subscription relationships. For example, if a topic in the cloud network needs to distribute tasks to a terminal, then It will notify all devices that subscribe to it. This massive subscription connection relationship and notification will occupy a lot of unnecessary storage and computing resources. In systems with large-scale terminal scenarios, such as cloud networks, computing and storage resources are limited. If task distribution and error recovery functions occupy too many resources, network performance will be reduced.

Contents of the invention

In view of this, embodiments of this specification provide two data transmission systems. One or more embodiments of this specification simultaneously relate to a data transmission method, a data device, a computing device, a computer-readable storage medium, and a computer program to solve technical deficiencies existing in the prior art.

According to a first aspect of the embodiment of this specification, a data transmission system is provided, including:

The task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the device agent node according to the first subscription relationship with the device agent node;

The device agent node is configured to establish a first subscription relationship to the task distribution node according to the second subscription relationship with the device node, and obtain the task set corresponding to the first subscription relationship from the task distribution node. In this case, deliver the tasks in the task set to the corresponding device node according to the second subscription relationship with the device node;

The device node is configured to obtain the task issued by the device agent node according to the second subscription relationship with the device agent node.

According to the second aspect of the embodiment of this specification, a data transmission method is provided, including:

Establish a first subscription relationship to the task distribution node according to the second subscription relationship with the device node;

When the task set corresponding to the first subscription relationship is obtained from the task distribution node, the tasks in the task set are distributed to the corresponding device node according to the second subscription relationship with the device node.

According to the third aspect of the embodiment of this specification, a data transmission system is provided, including:

The software-defined network task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the software-defined network agent node according to the first subscription relationship with the software-defined network agent node;

The software-defined network proxy node is configured to establish a first subscription relationship to the software-defined network task distribution node according to the second subscription relationship with the software-defined network node, and obtain the software-defined network task distribution node from the software-defined network task distribution node. In the case of a task set corresponding to the first subscription relationship, deliver the tasks in the task set to the corresponding software-defined network node according to the second subscription relationship with the software-defined network node;

The software-defined network node is configured to obtain the task issued by the software-defined network agent node according to the second subscription relationship with the software-defined network agent node.

According to the fourth aspect of the embodiments of this specification, a data transmission device is provided, including:

A creation module configured to establish a first subscription relationship with the task distribution node based on the second subscription relationship with the device node;

A distribution module configured to, when obtaining a task set corresponding to the first subscription relationship from the task distribution node, distribute the tasks in the task set to the device node according to the second subscription relationship with the device node. The corresponding device node.

According to a fifth aspect of the embodiments of this specification, a computing device is provided, including:

memory and processor;

The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above data transmission method are implemented.

According to a sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions. When the instructions are executed by a processor, the steps of the above data transmission method are implemented.

According to a seventh aspect of the embodiment of this specification, a computer program is provided, wherein when the computer program is executed in a computer, the computer is caused to perform the steps of the above data transmission method.

Embodiments of this specification provide a data transmission system and method, wherein the data transmission system includes: a task distribution node configured to deliver a first A task set corresponding to the subscription relationship; the device agent node is configured to establish a first subscription relationship to the task distribution node based on the second subscription relationship with the device node, and obtain the task set corresponding to the first subscription relationship from the task distribution node. In this case, the tasks in the task set are delivered to the corresponding device nodes according to the second subscription relationship with the device node; the device node is configured to obtain the tasks issued by the device agent node according to the second subscription relationship with the device agent node. Task. Due to the addition of the device agent node, the device node can subscribe to tasks from the device agent node and then subscribe to the task distribution node through the device agent node, which reduces the communication resource usage of the task distribution node.

Description of drawings

Figure 1 shows an architectural diagram of a data transmission system provided according to an embodiment of this specification;

Figure 2 is a flow chart of a data transmission method provided by an embodiment of this specification;

Figure 3 shows a schematic diagram of a data transmission method provided according to an embodiment of this specification;

Figure 4 is a processing flow chart of a data transmission method provided by an embodiment of this specification;

Figure 5 is a schematic structural diagram of a data transmission device provided by an embodiment of this specification;

Figure 6 is a structural block diagram of a computing device provided by an embodiment of this specification.

Detailed ways

In the following description, numerous specific details are set forth to facilitate a thorough understanding of this specification. However, this specification can be implemented in many other ways different from those described here. Those skilled in the art can make similar extensions without violating the connotation of this specification. Therefore, this specification is not limited by the specific implementation disclosed below.

The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to limit the one or more embodiments of this specification. As used in one or more embodiments of this specification and the appended claims, the singular forms "a," "the" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used in one or more embodiments of this specification refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be called the second, and similarly, the second may also be called the first. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining."

First, terminology used in one or more embodiments of this specification will be explained.

Token: Token, an asynchronous task distribution is called a token.

Change Set: A changes set contains a change set ID, distribution status and a set of tasks.

Subscription: Subscription, the subscription relationship includes topics and subscribers.

Topic: Topic, a concept defined to implement the ability to push different content to different devices, a task belongs to For a topic, the device can obtain all notifications under the topic by subscribing to the topic.

Task: Contains subject, object identification, timestamp, task data, etc.

Software Defined Network (SDN): It is a new innovative network architecture and an implementation method of network virtualization.

In this specification, two data transmission systems are provided. This specification also relates to a data transmission method, a data transmission device, a computing device, and a computer-readable storage medium. In the following embodiments, one by one Explain in detail.

Referring to Figure 1, Figure 1 shows an architectural diagram of a data transmission system provided according to an embodiment of this specification. The data transmission system includes:

The device agent node is configured to establish a first subscription relationship to the task distribution node according to the second subscription relationship with the device node, in the case of obtaining a task set corresponding to the first subscription relationship from the task distribution node. Next, deliver the tasks in the task set to the corresponding device node according to the second subscription relationship with the device node;

Among them, the task distribution node can be understood as a node that delivers tasks, for example, a storage computing node; the device agent can be understood as an intermediate node between the task distribution node and the device node, which can obtain tasks from the task distribution node and download them to the device node. Send tasks; device nodes can be understood as nodes that apply tasks; task sets can be understood as topics.

In practical applications, see Figure 1, the data transmission system consists of three parts: storage computing node, device agent node, and device node. The device agent node subscribes to the storage computing node as the first-level subscription, and the device node registers and subscribes to the device agent node as the first-level subscription. Secondary subscription, the specific implementation is as follows:

The device agent node is a storage computing node, and the storage computing node is responsible for task distribution and task status feedback. First, the storage computing node is responsible for distributing tasks to the device agent nodes. The storage computing node receives the tasks expressed in the form of a change set, stores the original change set in the data storage, and re-creates the tasks based on the topics subscribed by different device agent nodes. Organize the change set and deliver the reorganized change set to the corresponding device agent. Secondly, the storage computing node is also responsible for receiving the task status obtained from the device agent and summarizing it into the total task status.

The device agent node subscribes to the topic and is responsible for distributing tasks to corresponding devices and obtaining task status feedback from the devices. A device agent node obtains the topics that the device it represents needs to subscribe to, and the agent subscribes to these topics. After receiving the change set from the storage computing node, the device agent node creates a delivery task to the terminal device.

The device node registers with the device agent node, processes the tasks issued by the device agent node, and feeds back the task status. Give the device agent node.

In an implementable manner, the device node is configured to initiate a registration request to a device agent node, and upon receiving a registration completion message sent by the device agent node, establish the third connection with the device agent. 2. Subscription relationship.

For example, device node 1 sends a registration request to device agent node A, and device agent node A returns a registration completion message to device node 1. Then device agent node A completes the registration and creates a two-way connection with device node 1 for subsequent implementation. notifications received.

In an implementable manner, the device node is configured to determine the regional attributes of each device agent node when there are multiple device agent nodes, and determine the target device agent node according to the regional attributes, as well as

Initiate a registration request to the target device proxy node, and establish the second subscription relationship with the target device proxy when receiving a registration completion message sent by the target device proxy node.

The geographical attribute of the device agent node can be understood as the geographical location of the device agent node. For example, the device agent node is located in location A.

In practical applications, the distance between the geographical location of the device agent node and the geographical location of the device node has a great impact on the communication delay. Under other conditions being the same, the geographical location of the device agent node is different from the geographical location of the device node. The closer the distance between locations, the smaller the communication delay. Then, the device can select a nearby device proxy node to reduce communication delay and increase stability.

For example, the device agent node includes device agent node A and device agent node B. If the distance between device agent node A and the current device node is relatively close, then device agent node A is selected as the target device agent node, and the device agent node A is established with the target device agent node. Second subscription relationship.

In an implementable manner, the device node is configured to determine the task set attributes of each device agent node when there are multiple device agent nodes, and determine the target device agent according to the task set attributes. node, and

The task set attribute of the device agent node can be understood as the topic subscribed by the device agent node. For example, the topics subscribed by the device agent node include topic A and topic B.

In practical applications, device agent nodes can also be allocated according to topic types. Dividing device agent nodes according to different topics can reduce the computing pressure of device agent nodes.

For example, the device agent node includes device agent node A and device agent node B. The topics subscribed by device agent node A include topic A and topic B. The topics subscribed by device agent node B include topic C and topic D. The device node needs to subscribe Topic A, select device agent node A as the target device agent node, and communicate with the target The device agent node establishes the second subscription relationship.

In an implementable manner, when the data of the target task set changes, the task distribution node is configured to determine the target device agent node corresponding to the target task set according to the first subscription relationship, and send the The target device agent node delivers the target task set;

The device agent node is configured to, upon receiving the target task set issued by the task distribution node, determine the target device node corresponding to the target task set according to the second subscription relationship, and send the target device node to the target device node. Send said target task.

Among them, when the data of the target task set changes, it can be understood that the data corresponding to the task has changed. For example, task A adds an item of data.

In practical applications, when the task distribution node receives the data changes in the task, it needs to send the data changes to the device agent node, and then the device agent node sends it to the relevant device nodes.

For example, if a piece of data is added to the task of topic A, the device agent node that subscribes to topic A is determined, and the added piece of data in topic A is sent to the corresponding device agent node in the form of a change set. The device agent node After the change set is not received, the relevant device nodes that subscribe to topic A will be determined and the change set will be delivered to the relevant device nodes.

In an implementable manner, the device node is configured to respond to a task set modification instruction and update the second subscription relationship with the device agent node according to the target task set carried in the task set modification instruction.

In actual applications, the device node may need to add a subscription to a new topic or delete a subscription to a topic, and then delete the task in the subscription relationship. For example, if the device node needs to add a subscription to topic B, then add the subscription relationship of topic B to the second subscription relationship between the device node and the device agent node.

In an implementable manner, the device agent node is configured as:

A task set is determined according to the second subscription relationship, and if the first subscription relationship corresponding to the task set is not established, a first subscription relationship of the task set is established.

In an implementable manner, the device agent node is also configured to:

Determine a task set according to the second subscription relationship;

If the first subscription relationship corresponding to the task set is not established, establish a first subscription relationship to the task distribution node according to the task set.

In an implementable manner, the device agent node is also configured to:

Determine the corresponding device according to the second subscription relationship corresponding to the task set;

Deliver the tasks in the task set to the corresponding device.

In an implementable manner, the device agent node is also configured to:

Create a issued transaction for the task set, mark the status of the issued transaction as an analysis status, and feed back the status of the issued transaction to the task distribution node;

Deliver the tasks in the task set to the corresponding device according to the delivery transaction.

In an implementable manner, the device agent node is also configured to:

Receive the task distribution results returned by each device node;

Modify the status of the issued transaction according to the task distribution result.

In an implementable manner, the device agent node is also configured to:

When each task distribution result is successful, the status of the issued transaction is marked as a successful status, and the status of the issued transaction is fed back to the task distribution node.

In an implementable manner, the device agent node is also configured to:

When any task distribution result is a failure, mark the status of the issued transaction as a failure status, and add the task corresponding to the task distribution result in the failed task list, and

Feed back the status of the issued transaction to the task distribution node.

In an implementable manner, the device agent node is also configured to:

Reacquire the task set and record the number of acquisitions;

Deliver the tasks in the task set to the corresponding device according to the failed task list.

In an implementable manner, the device agent node is also configured to:

If the task is in the failed task list, create a reissue transaction for the device that failed to deliver the task;

Deliver the task to the corresponding device according to the retransmission transaction.

In an implementable manner, the device agent node is also configured to:

Receive the registration request from the device node, and match the target device proxy node according to the regional attribute carried in the registration request;

Forward the registration request to the target device proxy node.

In an implementable manner, the device agent node is also configured to:

Receive the registration request of the device node, and match the target device proxy node according to the task set attribute carried in the registration request;

Forward the registration request to the target device proxy node.

Embodiments of this specification provide a data transmission system including: a task distribution node configured to deliver a task set corresponding to the first subscription relationship to the device agent node according to the first subscription relationship with the device agent node; the device agent node is Configured to establish a first subscription relationship to the task distribution node based on the second subscription relationship with the device node, and in the case of obtaining a task set corresponding to the first subscription relationship from the task distribution node, based on the second subscription relationship with the device node , delivers the tasks in the task set to the corresponding device node; the device node is configured to obtain the tasks issued by the device agent node according to the second subscription relationship with the device agent node. Due to the addition of equipment The device agent node enables the device node to subscribe to tasks from the device agent node, and then subscribes to the task distribution node through the device agent node, thereby reducing the communication resource usage of the task distribution node.

Referring to Figure 2, Figure 2 shows a flow chart of a data transmission method provided according to an embodiment of this specification, which specifically includes the following steps.

Step 202: Establish a first subscription relationship with the task distribution node based on the second subscription relationship with the device node.

In practical applications, the device node needs to register with the device agent node to establish a second subscription relationship, and then based on the topic to which the device node subscribes, the device agent node then establishes a first subscription relationship with the task distribution node.

Specifically, establishing a first subscription relationship to the task distribution node based on the second subscription relationship with the device node includes:

Determine a task set according to the second subscription relationship;

For example, referring to Figure 3, Figure 3 shows a schematic diagram illustrating a data transmission method provided according to an embodiment of this specification, which includes a storage computing node, a device agent node A and a device agent node B, and a device node 1. Device node 2, device node 3, device node 4, and device node 5 determine topic A based on the second subscription relationship between device node 1 and device agent node A, and determine whether there is a first connection between topic A and the storage computing node. Subscription relationship. If the first subscription relationship including topic A and storage computing node already exists, the subscription processing will not be performed. If it does not exist, a subscription relationship between topic A and device agent node A will be created, and the subscription relationship will be created on device agent node A. Store new subscription relationships in memory.

Step 204: When the task set corresponding to the first subscription relationship is obtained from the task distribution node, deliver the tasks in the task set to the corresponding device according to the second subscription relationship with the device node. node.

In practical applications, when the task distribution node receives a task, the device agent node obtains the subscribed related task set and sends the tasks in the subscribed related task set to the locally registered device node. In an implementable manner, issuing the tasks in the task set to the corresponding device nodes includes:

Deliver the tasks in the task set to the corresponding device.

In practical applications, after receiving the change set, the device agent finds all the devices that follow the topic based on the topic and obtains the device list.

For example, see Figure 3. For device agent node A, if the task set is topic A, the second subscription relationship determines that the corresponding devices are device node 1, device node 2, device node 3, and device node 4. To the device node 1. Device node 2, device node 3, and device node 4 deliver the task in topic A.

In an implementable manner, issuing the tasks in the task set to the corresponding device includes:

In actual applications, each asynchronous task issuance is called a token, and all token statuses are queried in chronological order. The token has six states, namely "initialization state", "analysis state", "running state", "successful state", "running error state", and "failure state". Tokens store two pieces of information, token content and token status. Token content stores change sets, including multiple topics and task lists contained in each topic; token status stores progress updates, including status, start time, number of affected devices, number of affected tasks, number of completed devices, and number of completed tasks and number of errors. Among them, the "Initialization State" state indicates that the token is established for the first time. At this time, the token content and token status are stored in the external memory. Even if the intermediate service goes down, it can still be recovered from the external storage; the "Analysis State" state indicates It is in the analysis state. At this time, the device agent is still calculating the device list associated with the change set and creating a delivery task; "Running state" indicates the execution state, and the device agent processes the tasks delivered to the device; "Successful state" indicates execution Completed; "Running Error Status" means that the task has been issued, but the execution has not yet been completed; "Failure Status" means that the execution has been completed but an error occurred. When delivering tasks in the task set, the device list is first traversed, and a delivery task is created for each device in the device list. During this process, the task status is marked as "analysis status". When all delivered tasks are created, the device agent feeds back the task status to the storage computing node. The feedback information obtained by the storage computing node is summarized and calculated, and the execution status of the change set is stored in the database for future reference. Among them, the feedback information includes the number of affected devices, the number of affected tasks, the number of completed devices, the number of completed tasks and the number of errors.

For example, the device list is: device node 1, device node 2, device node 3, and device node 4. The tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively, that is, create Deliver the transaction, set the status of the delivered transaction to "Analysis Status", and deliver the tasks in topic A to device node 1, device node 2, device node 3, and device node 4 respectively according to the delivered transaction.

In an implementable manner, the data transmission method in the embodiment of this specification also includes:

Receive the task distribution results returned by each device node;

In actual applications, after all distributed tasks are created, the device agent node feeds back the task status to the storage computing node. When the storage computing node receives the task status feedback from all connected device agent nodes, it feeds back the task status. Summarized into total task status feedback, marked as "Running Status".

For example, tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively based on the delivered transactions. After the delivery is completed, these delivered transactions are marked as "running status" and Feedback the status of the transaction issued to the storage computing node, that is, the status of the transaction issued by device node 1 is "running status", the status of the transaction issued by device node 2 is "running status", and the status of the transaction issued by device node 3 is "running status". The status of the transaction issued is "running status", and the status of the transaction issued by device node 4 is "running status", so that the storage The computing node feeds back the total task status and marks it as "running status".

Specifically, modifying the status of the issued transaction according to the task distribution result includes:

In actual applications, the device agent node starts to execute the distribution task. When the task execution on each device is completed, the storage computing node marks the task as "successful status". When the storage settlement node receives return messages from the relevant device agent nodes of all change sets, and the return messages are in the completed state, the change set is marked as "completed state" and stored in the database.

For example, device node 1 executes the task in topic A. After the execution is completed, it feeds back a message to device agent node A. The device agent node marks the status of the transaction issued by device node 1 as "successful status", and device node 2 executes the topic. After the execution of the task in A is completed, a message is fed back to the device agent node A. The device agent node marks the status of the transaction issued by device node 2 as "successful status". Device node 3 executes the task in topic A. During execution After completion, the message is fed back to the device agent node A. The device agent node marks the status of the transaction issued by the device node 3 as "successful status". Device section 4 executes the task in topic A. After the execution is completed, it reports to the device agent Node A feeds back the message, and the device agent node marks the status of the transaction issued by device node 4 as "success status". Correspondingly, it feeds back the "success status" of the transaction issued to the storage computing node, so that the storage computing node will always Task status feedback, marked as "success status".

In an implementable manner, modifying the status of the issued transaction according to the task distribution result includes:

Feed back the status of the issued transaction to the task distribution node.

In a practical application, if execution fails, the task is marked as failed and added to the device's failed task list. Whenever the task execution status is refreshed, the device agent node will determine whether an error occurs for the first time based on the completion of the task, and whether the time since the last feedback of the task status has exceeded the cooling time.

For example, device node 1 executes the task in topic A. After the execution is completed, it feeds back a message to device agent node A. The device agent node marks the status of the transaction issued by device node 1 as "successful status", and device node 2 executes the topic. After the execution of the task in A fails, a message is fed back to the device agent node A. The device agent node marks the status of the transaction issued by device node 2 as "failed status". Device node 3 executes the task in topic A. During execution After completion, the message is fed back to the device agent node A. The device agent node marks the status of the transaction issued by the device node 3 as "successful status". Device section 4 executes the task in topic A. After the execution is completed, it reports to the device agent Node A feeds back the message, and the device agent node marks the status of the transaction issued by device node 4 as "success status". Correspondingly, it feeds back the "success status" of the transaction issued to the storage computing node, so that the storage computing node will always Task status feedback, marked as "Running Error Status". Add "Add to failed tasks list" Device node 2 failed to deliver the task in topic A."

In one possible implementation, it also includes:

Reacquire the task set and record the number of acquisitions;

In actual applications, when the task distribution result is a failure, it is determined whether the failure exceeds the configured retry delay time. If the configured retry delay time is exceeded, the retry mechanism is triggered and the task is retried.

For example, device node 2 executes the task in topic A. After the execution fails, it feeds back a message to device agent node A. The device agent node marks the status of the transaction issued by device node 2 as "failed status" and executes it on device node 2. The retry mechanism is triggered 3 milliseconds after the task in topic A fails.

Specifically, delivering the tasks in the task set to the corresponding device according to the failed task list includes:

In actual applications, the change set is read from the storage, the subscription of each topic is recalculated, and distributed to the corresponding device agent, and the number of retries of the delivery task is increased by one.

For example, the device agent node finds all the devices paying attention to the topic based on topic A, and obtains the device list. The device list is: device node 1, device node 2, device node 3, device node 4, traverses the device list, and checks the failed task list. Whether the task exists, if so, create a resend task.

In an implementable way, if there is "failed to deliver the task in topic A to device node 2" in the failed task list, then deliver the task in topic A to device node 2, that is, create a retransmission transaction, and Set the status of the issued transaction to "Analysis Status".

In another possible way, it is possible that the error has been resolved before the retry mechanism, then the corresponding task does not exist in the failed task list. If it does not exist, it means that the device has successfully retransmitted, and the task is ignored. .

For example, if "Failed to deliver task in topic A to device node 2" does not exist in the failed task list, then the retry "Failed to deliver task in topic A to device node 2" will be ignored.

Further, the retransmission results are summarized and fed back to the task distribution node. If successful, the token status is set to "success status", otherwise the token status is still "failure status". If the number of retries exceeds the retry threshold, output to the alarm system.

For example, if there is "Failed to deliver the task in topic A to device node 2" in the failed task list, then deliver the task in topic A to device node 2, that is, create a retransmission transaction and set the status of the delivered transaction. is the "Analysis Status", and when device node 2 feedbacks that the status of the transaction issued is "successful status", the retransmission results will be summarized and fed back to the task distribution node, that is, the device agent node will transmit the transaction issued by device node 1 status is marked as "Success status", the device agent node marks the status of the transaction issued by device node 2 as "success status", the device agent node marks the status of the transaction issued by device node 3 as "success status", the device agent node marks the device The status of the transaction issued by node 4 is marked as "successful status". The status of the transaction issued by device node 1, device node 2, device node 3 and device node 4 is fed back to the task distribution node, and the token status is set to "successful". state".

If device node 2 reports that the status of the delivered transaction is still "failed", the number of retries of the delivered task will be increased by one. If the threshold of the number of retries is three, then when the number of retries reaches three, then Output to the alarm system so that the problem can be solved manually.

In one possible implementation, it also includes:

Forward the registration request to the target device proxy node.

Among them, the regional attribute can be understood as the geographical location, for example, place A.

In practical applications, as described in the previous embodiments, under the same conditions, the closer the geographical location of the device agent node to the geographical location of the device node, the smaller the communication delay. Then, the device can choose Close device agent nodes to reduce communication delays and increase stability.

For example, the device agent node includes device agent node A and device agent node B. The distance between device agent node A and the current device node is relatively close. When the device node sends a registration request to device agent node B, device agent node B will register. The request is forwarded to device agent node A, which serves as the target device agent node and establishes the second subscription relationship with the target device agent node A.

In one possible implementation, it also includes:

Forward the registration request to the target device proxy node.

Among them, the task set attribute can be understood as the subscribed topic. For example, the subscribed topics include topic A and topic B.

In practical applications, as described in the foregoing embodiments, device agent nodes can also be allocated according to topic types, and dividing device agent nodes according to different topics can reduce the computing pressure of the device agent nodes.

For example, the device agent node includes device agent node A and device agent node B. The topics subscribed by device agent node A include topic A and topic B. The topics subscribed by device agent node B include topic C and topic D. The device node needs to subscribe Topic A, when the device node sends a registration request to the device agent node B, the device agent node B forwards the registration request to the device agent node A. The device agent node A serves as the target device agent node and establishes with the target device agent node A. The second subscription relationship.

Embodiments of this specification provide a data transmission method, which includes: establishing a first subscription relationship to a task distribution node based on a second subscription relationship with a device node, and obtaining a task set corresponding to the first subscription relationship from the task distribution node. Next, according to the second subscription relationship with the device node, the tasks in the task set are delivered to the corresponding device node. Due to the addition of the device agent node, the device node can subscribe to the task from the device agent node, and then submit the task to the task through the device agent node. The distribution node subscribes to the task, which reduces the communication resource usage of the task distribution node.

The data transmission method will be further described below with reference to Figure 4, taking the application of the data transmission method provided in this specification at a device agent node as an example. Among them, FIG. 4 shows a process flow chart of a data transmission method provided by an embodiment of this specification, which specifically includes the following steps.

Step 402: The device agent node determines a task set according to the second subscription relationship.

For example, topic A is determined according to the second subscription relationship between device node 1 and device agent node A.

Step 404: When the device agent node has not established a first subscription relationship corresponding to the task set, establish a first subscription relationship to the task distribution node according to the task set.

Following the above example, determine whether there is a first subscription relationship between topic A and the storage computing node. If there is already a first subscription relationship between topic A and the storage computing node, the subscription processing will not be performed. If it does not exist, the topic will be created. The subscription relationship between A and the device agent node A, and the new subscription relationship is stored in the memory of the device agent node A.

Step 406: The device agent node determines the corresponding device according to the second subscription relationship corresponding to the task set.

Following the above example, for device agent node A, if the task set is topic A, the second subscription relationship determines that the corresponding devices are device node 1, device node 2, device node 3, and device node 4.

Step 408: The device agent node creates a issued transaction for the task set, marks the status of the issued transaction as an analysis status, and feeds back the status of the issued transaction to the task distribution node.

Following the above example, the device list is: device node 1, device node 2, device node 3, and device node 4. The tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively, that is, , create a issued transaction, and set the status of the issued transaction to "Analysis Status".

Step 410: The device agent node delivers the tasks in the task set to the corresponding device according to the delivery transaction.

Following the above example, the tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively according to the delivery transaction.

Step 412: The device agent node receives the task distribution result returned by each device node.

Following the above example, device node 1 executes the task in topic A. After the execution is completed, it feeds back a message to device agent node A. The device agent node marks the status of the transaction issued by device node 1 as "successful status", and device node 2 Execute the task in topic A. After the execution is completed, a message is fed back to the device agent node A. The device agent node marks the status of the transaction issued by device node 2 as "successful status". Device node 3 executes the task in topic A. After the task is executed, a message is fed back to the device agent node A. The device agent node marks the status of the transaction issued by the device node 3 as "successful status". Device section 4 executes the task in topic A. After the execution is completed, Finally, the message is fed back to the device agent node A, and the device agent node marks the status of the transaction issued by the device node 4 as "successful status".

Step 414: When each task distribution result is successful, the device agent node marks the status of the issued transaction as a successful status, and feeds back the status of the issued transaction to the task distribution node.

Following the above example, the "success status" of the transaction is fed back to the storage computing node, so that the storage computing node feeds back the total task status and marks it as "success status".

In the embodiment of this specification, the device agent node is added, so that the device node can subscribe to tasks from the device agent node, and then subscribe to the task to the task distribution node through the device agent node, thereby reducing the communication resource usage of the task distribution node.

This manual also provides a data transmission system, including:

Among them, the software-defined network agent node can be a gateway, private cloud and other devices.

In an implementable manner, the software-defined network node is configured to initiate a registration request to the software-defined network proxy node, and upon receiving the registration completion message sent by the software-defined network proxy node, communicate with the software-defined network proxy node. The device agent establishes the second subscription relationship.

In an implementable manner, the software-defined network agent node is configured to determine a task set according to the second subscription relationship, and establish all the task sets when the first subscription relationship corresponding to the task set is not established. The first subscription relationship of the above task set.

In an implementable manner, the software-defined network node is configured to determine the regional attributes of each software-defined network agent node when there are multiple software-defined network agent nodes, and determine the regional attributes of each software-defined network agent node according to the regional properties identify the target software-defined network agent node, and

Initiate a registration request to the target software-defined network proxy node, and establish the second subscription relationship with the target device proxy upon receiving a registration completion message sent by the target software-defined network proxy node.

In an implementable manner, the software-defined network node is configured as a software-defined network agent When there are multiple nodes, determine the task set attributes of each software-defined network agent node, and determine the target software-defined network agent node according to the task set attributes, and

In an implementable manner, when the data of the target task set changes, the software-defined network task distribution node is configured to determine the target software definition corresponding to the target task set according to the first subscription relationship. a network agent node, and delivers the target task set to the target software-defined network agent node;

The software-defined network proxy node is configured to determine the target software-defined network node corresponding to the target task set according to the second subscription relationship when receiving the target task set issued by the software-defined network task distribution node, and sends the target task to the target software-defined network node.

In an implementable manner, the software-defined network node is configured to respond to a task set modification instruction and update the communication with the software-defined network agent node according to the target task set carried in the task set modification instruction. Second subscription relationship.

In an implementable manner, the software-defined network proxy node is configured as:

In an implementable manner, the software-defined network proxy node is also configured to:

Determine a task set according to the second subscription relationship;

If the first subscription relationship corresponding to the task set is not established, establish a first subscription relationship to the software-defined network task distribution node according to the task set.

Deliver the tasks in the task set to the corresponding device.

Create a issued transaction for the task set, mark the status of the issued transaction as an analysis status, and feed back the status of the issued transaction to the software-defined network task distribution node;

Receive the task distribution results returned by each software-defined network node;

When the distribution result of each task is successful, the status of the issued transaction is marked as successful, and feeding back the status of the issued transaction to the software-defined network task distribution node.

Feed back the status of the issued transaction to the software-defined network task distribution node.

Reacquire the task set and record the number of acquisitions;

Receive the registration request of the software-defined network node, and match the target software-defined network proxy node according to the regional attribute carried in the registration request;

Forward the registration request to the target software-defined network proxy node.

Receive the registration request of the software-defined network node, and match the target software-defined network proxy node according to the task set attribute carried in the registration request;

Embodiments of this specification provide a data transmission system including: a software-defined network task distribution node configured to deliver tasks corresponding to the first subscription relationship to the software-defined network agent node according to the first subscription relationship with the software-defined network agent node. set; the software-defined network proxy node is configured to establish a first subscription relationship to the software-defined network task distribution node based on the second subscription relationship with the software-defined network node, and obtain the first subscription relationship from the software-defined network task distribution node In the case of the corresponding task set, the tasks in the task set are delivered to the corresponding software-defined network node according to the second subscription relationship with the software-defined network node; the software-defined network node is configured to be based on the software-defined network proxy node. The second subscription relationship is to obtain the tasks issued by the software-defined network agent node. Due to the addition of the device agent node, the device node can subscribe to tasks from the device agent node and then subscribe to the task distribution node through the device agent node, which reduces the communication resource usage of the task distribution node.

Corresponding to the above method embodiments, this specification also provides an embodiment of a data transmission device. Figure 5 shows a schematic structural diagram of a data transmission device provided by an embodiment of this specification. As shown in Figure 5, the device includes:

The creation module 502 is configured to establish a first subscription relationship to the task distribution node based on the second subscription relationship with the device node;

The distribution module 504 is configured to, after obtaining the task set corresponding to the first subscription relationship from the task distribution node, distribute the tasks in the task set according to the second subscription relationship with the device node. To the corresponding device node.

In an implementable manner, the creation module 502 is also configured to:

Determine a task set according to the second subscription relationship;

In an implementable manner, the distribution module 504 is also configured to:

Deliver the tasks in the task set to the corresponding device.

In an implementable manner, the distribution module 504 is also configured to:

Receive the task distribution results returned by each device node;

In an implementable manner, the distribution module 504 is also configured to:

Feed back the status of the issued transaction to the task distribution node.

In an implementable manner, the distribution module 504 is also configured to:

Reacquire the task set and record the number of acquisitions;

In an implementable manner, the distribution module 504 is also configured to:

If the task is in the failed task list, create a reissue transaction for the device that failed to deliver the task.

Embodiments of this specification provide a data transmission device, wherein the data transmission device includes: a creation module configured to establish a first subscription relationship to a task distribution node based on a second subscription relationship with a device node; a distribution module configured to When the task set corresponding to the first subscription relationship is obtained from the task distribution node, the tasks in the task set are distributed to the corresponding device node according to the second subscription relationship with the device node. Due to the addition of the device agent node, the device node can subscribe to tasks from the device agent node and then subscribe to the task distribution node through the device agent node, which reduces the communication resource usage of the task distribution node.

The above is a schematic solution of a data transmission device in this embodiment. It should be noted that the technical solution of the data transmission device and the technical solution of the above-mentioned data transmission method belong to the same concept. For details that are not described in detail in the technical solution of the data transmission device, please refer to the description of the technical solution of the above-mentioned data transmission method. .

Figure 6 shows a structural block diagram of a computing device 600 provided according to an embodiment of this specification. Components of the computing device 600 include, but are not limited to, memory 610 and processor 620 . The processor 620 and the memory 610 are connected through a bus 630, and the database 650 is used to save data.

Computing device 600 also includes an access device 640 that enables computing device 600 to communicate via one or more networks 660 . Examples of these networks include the Public Switched Telephone Network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communications networks such as the Internet. Access device 640 may include one or more of any type of network interface (eg, a network interface card (NIC)), wired or wireless, such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Worldwide Interconnection for Microwave Access (WLAN) Wi-MAX) interface, Ethernet interface, Universal Serial Bus (USB) interface, cellular network interface, Bluetooth interface, Near Field Communication (NFC) interface, etc.

In one embodiment of the present description, the above-mentioned components of the computing device 600 and other components not shown in FIG. 6 may also be connected to each other, such as through a bus. It should be understood that the structural block diagram of the computing device shown in FIG. 6 is for illustrative purposes only and does not limit the scope of this description. Those skilled in the art can add or replace other components as needed.

Computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet computer, personal digital assistant, laptop computer, notebook computer, netbook, etc.), a mobile telephone (e.g., smartphone ), a wearable computing device (e.g., smart watch, smart glasses, etc.) or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 600 may also be a mobile or stationary server.

The processor 620 is configured to execute the following computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above data transmission method are implemented.

The above is a schematic solution of a computing device in this embodiment. It should be noted that the technical solution of the computing device and the technical solution of the above-mentioned data transmission method belong to the same concept. For details that are not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above data transmission method.

An embodiment of the present specification also provides a computer-readable storage medium that stores computer-executable instructions. When the computer-executable instructions are executed by a processor, the steps of the above data transmission method are implemented.

The above is a schematic solution of a computer-readable storage medium in this embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the above-mentioned data transmission method belong to the same concept. For details that are not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the above-mentioned data transmission method.

An embodiment of the present specification also provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to perform the steps of the above data transmission method.

The above is a schematic solution of a computer program in this embodiment. It should be noted that the technical solution of the computer program and the technical solution of the above-mentioned data transmission method belong to the same concept. For details that are not described in detail in the technical solution of the computer program, please refer to the description of the technical solution of the above-mentioned data transmission method.

The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desired results. Additionally, the processes depicted in the figures do not necessarily require the specific order shown, or sequential order, to achieve desirable results. Multitasking and parallel processing are also possible or may be advantageous in certain implementations.

The computer instructions include computer program code, which may be in the form of source code, object code, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately added or deleted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium Excludes electrical carrier signals and telecommunications signals.

It should be noted that for the convenience of description, each of the foregoing method embodiments is expressed as a series of action combinations. However, those skilled in the art should know that the embodiments of this specification are not limited by the described action sequence. limitation, because according to the embodiments of this specification, certain steps may be performed in other orders or at the same time. Secondly, those skilled in the art should also know that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily necessary for the embodiments of this specification.

In the above embodiments, each embodiment is described with its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

The preferred embodiments of this specification disclosed above are only used to help explain this specification. Alternative embodiments are not described in all details, nor are the inventions limited to the specific embodiments described. Obviously, many modifications and changes can be made based on the contents of the embodiments of this specification. These embodiments are selected and described in detail in this specification to better explain the principles and practical applications of the embodiments in this specification, so that those skilled in the art can better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

A data transmission system including:

The task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the device agent node according to the first subscription relationship with the device agent node;

The device agent node is configured to establish a first subscription relationship to the task distribution node according to the second subscription relationship with the device node, in the case of obtaining a task set corresponding to the first subscription relationship from the task distribution node. Next, deliver the tasks in the task set to the corresponding device node according to the second subscription relationship with the device node;

The device node is configured to obtain the task issued by the device agent node according to the second subscription relationship with the device agent node.
The system of claim 1, further comprising:

The device node is configured to initiate a registration request to a device agent node, and upon receiving a registration completion message sent by the device agent node, establish the second subscription relationship with the device agent.
The system of claim 1, further comprising:

The device agent node is configured to determine a task set according to the second subscription relationship, and establish a first subscription relationship for the task set if the first subscription relationship corresponding to the task set is not established.
The system of claim 1, further comprising:

The device node is configured to determine the regional attributes of each device agent node when there are multiple device agent nodes, and determine the target device agent node according to the regional attributes, and

Initiate a registration request to the target device proxy node, and establish the second subscription relationship with the target device proxy when receiving a registration completion message sent by the target device proxy node.
The system of claim 1, further comprising:

The device node is configured to determine the task set attributes of each device agent node when there are multiple device agent nodes, and determine the target device agent node according to the task set attributes, and

Initiate a registration request to the target device proxy node, and establish the second subscription relationship with the target device proxy when receiving a registration completion message sent by the target device proxy node.
The system of claim 1, further comprising:

When the data of the target task set changes, the task distribution node is configured to determine the target device agent node corresponding to the target task set according to the first subscription relationship, and deliver the data to the target device agent node. The target task set;

The device agent node is configured to, upon receiving the target task set issued by the task distribution node, determine the target device node corresponding to the target task set according to the second subscription relationship, and send the target device node to the target device node. Send said target task.
The system of claim 1, further comprising:

The device node is configured to respond to a task set modification instruction and update the second subscription relationship with the device agent node according to the target task set carried in the task set modification instruction.
A data transmission method, applied to device agent nodes, including:

Establish a first subscription relationship to the task distribution node according to the second subscription relationship with the device node;

When the task set corresponding to the first subscription relationship is obtained from the task distribution node, the tasks in the task set are distributed to the corresponding device node according to the second subscription relationship with the device node.
The method according to claim 8, establishing a first subscription relationship to the task distribution node based on a second subscription relationship with a device node, including:

Determine a task set according to the second subscription relationship;

If the first subscription relationship corresponding to the task set is not established, establish a first subscription relationship to the task distribution node according to the task set.
The method according to claim 8, said delivering tasks in the task set to corresponding device nodes includes:

Determine the corresponding device according to the second subscription relationship corresponding to the task set;

Deliver the tasks in the task set to the corresponding device.
The method according to claim 10, according to delivering the tasks in the task set to the corresponding device, including:

Create a issued transaction for the task set, mark the status of the issued transaction as an analysis status, and feed back the status of the issued transaction to the task distribution node;

Deliver the tasks in the task set to the corresponding device according to the delivery transaction.
The method of claim 11, further comprising:

Receive the task distribution results returned by each device node;

Modify the status of the issued transaction according to the task distribution result.
The method according to claim 12, modifying the status of the issued transaction according to the task distribution result includes:

When each task distribution result is successful, the status of the issued transaction is marked as a successful status, and the status of the issued transaction is fed back to the task distribution node.
The method according to claim 12, modifying the status of the issued transaction according to the task distribution result includes:

When any task distribution result is a failure, mark the status of the issued transaction as a failure status, and add the task corresponding to the task distribution result in the failed task list, and

Feed back the status of the issued transaction to the task distribution node.
The method of claim 14, further comprising:

Reacquire the task set and record the number of acquisitions;

Deliver the tasks in the task set to the corresponding device according to the failed task list.
The method according to claim 15, said delivering the tasks in the task set to the corresponding device according to the failed task list, including:

If the task is in the failed task list, create a reissue transaction for the device that failed to deliver the task;

Deliver the task to the corresponding device according to the retransmission transaction.
The method of claim 8, further comprising:

Receive the registration request from the device node, and match the target device proxy node according to the regional attribute carried in the registration request;

Forward the registration request to the target device proxy node.
The method of claim 8, further comprising:

Receive the registration request of the device node, and match the target device proxy node according to the task set attribute carried in the registration request;

Forward the registration request to the target device proxy node.
A data transmission system including:

The software-defined network task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the software-defined network agent node according to the first subscription relationship with the software-defined network agent node;

The software-defined network proxy node is configured to establish a first subscription relationship to the software-defined network task distribution node according to the second subscription relationship with the software-defined network node, and obtain the software-defined network task distribution node from the software-defined network task distribution node. In the case of a task set corresponding to the first subscription relationship, deliver the tasks in the task set to the corresponding software-defined network node according to the second subscription relationship with the software-defined network node;

The software-defined network node is configured to obtain the task issued by the software-defined network agent node according to the second subscription relationship with the software-defined network agent node.
A computing device including:

memory and processor;

The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the data transmission method described in any one of claims 8 to 18 are implemented. .
A computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are executed by a processor, the steps of the data transmission method described in any one of claims 8 to 18 are implemented.