CN114885020A

CN114885020A - Data transmission system and method

Info

Publication number: CN114885020A
Application number: CN202210345992.6A
Authority: CN
Inventors: 石宜平; 高磊; 方崇荣; 吕彪; 祝顺民; 蒋江伟; 程鹏; 陈积明
Original assignee: Zhejiang University ZJU
Current assignee: Zhejiang University ZJU
Priority date: 2022-04-02
Filing date: 2022-04-02
Publication date: 2022-08-09
Anticipated expiration: 2042-04-02
Also published as: WO2023186154A1; CN114885020B

Abstract

An embodiment of the present specification provides a data transmission system and a method, where the data transmission system includes: the task distribution node is configured to issue a task set corresponding to a first subscription relation to the equipment agent node according to the first subscription relation with the equipment agent node; the device agent node is configured to establish a first subscription relation to the task distribution node according to a second subscription relation with the device node, and issue the tasks in the task set to the corresponding device node according to the second subscription relation with the device node under the condition that the task set corresponding to the first subscription relation is obtained from the task distribution node; and the equipment node is configured to acquire the task issued by the equipment proxy node according to the second subscription relation with the equipment proxy node. Due to the fact that the equipment agent nodes are added, the equipment nodes can subscribe the tasks from the equipment agent nodes and then subscribe the tasks to the task distribution nodes through the equipment agent nodes, and therefore the communication resource usage amount of the task distribution nodes is reduced.

Description

Data transmission system and method

Technical Field

The embodiment of the specification relates to the technical field of data processing, in particular to a data transmission system.

Background

The functions of task distribution and error recovery are indispensable in a system composed of large-scale terminals and servers. In such systems, tasks are usually distributed to different terminals to be executed frequently, and feedback of results is completed. In the process, one task belongs to one topic, and the terminal acquires the task issued by the topic in a change set form by subscribing the topic. The task distribution uses the subscription relationship between the equipment and the topic, and timely delivers the dispatched task to the target terminal, confirms the realization of the task and obtains feedback; when the task is issued, the total task execution may fail due to the error of the terminal device or the offline of the terminal device, so that the task failure error occurring on the terminal needs to be found in time, and after the terminal error is found, the error needs to be retried with a certain logic to realize error recovery, so as to maintain the normal operation of the whole configuration distribution system. Therefore, methods of task distribution and error recovery are crucial to the field of configuration distribution.

However, with the increase of system complexity and the continuous expansion of scale, a large-scale terminal scene needs to accommodate a large number of terminals, and the large number of terminals means a large number of subscription relationships, for example, a topic in a cloud network needs to distribute a task to one terminal, and then it will notify all devices subscribing to it, and such a large number of subscription connection relationships and notifications will occupy a large amount of unnecessary storage and computing resources. In a system of a large-scale terminal scene, such as a cloud network, computing and storage resources are limited, and if too many resources are occupied by task distribution and error recovery functions, network performance is reduced.

Disclosure of Invention

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

According to a first aspect of embodiments herein, there is provided a data transmission system, including:

the task distribution node is configured to issue a task set corresponding to a first subscription relation to the equipment agent node according to the first subscription relation with the equipment agent node;

the device agent node is configured to establish a first subscription relationship to the task distribution node according to a second subscription relationship with the device node, and issue the tasks in the task set to the corresponding device node according to the second subscription relationship with the device node under the condition that the task set corresponding to the first subscription relationship is obtained from the task distribution node;

and the equipment node is configured to acquire the task issued by the equipment proxy node according to the second subscription relation with the equipment proxy node.

According to a second aspect of embodiments herein, there is provided a data transmission method including:

establishing a first subscription relation to the task distribution node according to a second subscription relation with the equipment node;

and under the condition that the task set corresponding to the first subscription relationship is obtained from the task distribution node, the tasks in the task set are issued to the corresponding equipment nodes according to the second subscription relationship with the equipment nodes.

According to a third aspect of embodiments herein, there is provided a data transmission system including:

the software defined network task distribution node is configured to issue a task set corresponding to a first subscription relation to a software defined network proxy node according to the first subscription relation with the software defined network proxy node;

the software-defined network agent node is configured to establish a first subscription relationship with the software-defined network task distribution node according to a second subscription relationship with the software-defined network node, and issue tasks in the task set to the corresponding software-defined network node according to the second subscription relationship with the software-defined network node under the condition that the task set corresponding to the first subscription relationship is obtained from the software-defined network task distribution node;

and the software-defined network node is configured to acquire the task issued by the software-defined network agent node according to a second subscription relationship with the software-defined network agent node.

According to a fourth aspect of embodiments herein, there is provided a data transmission apparatus including:

the creation module is configured to establish a first subscription relation to the task distribution node according to a second subscription relation with the equipment node;

and the distribution module is configured to issue the tasks in the task set to the corresponding equipment nodes according to the second subscription relationship with the equipment nodes under the condition that the task set corresponding to the first subscription relationship is obtained from the task distribution node.

According to a fifth aspect of embodiments herein, there is provided a computing device comprising:

a memory and a processor;

the memory is configured to store computer-executable instructions and the processor is configured to execute the computer-executable instructions, which when executed by the processor implement the steps of the data transmission method described above.

According to a sixth aspect of embodiments herein, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the above-described data transmission method.

According to a seventh aspect of embodiments herein, there is provided a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned data transmission method.

Drawings

FIG. 1 illustrates an architecture diagram of a data transmission system provided in accordance with one embodiment of the present description;

FIG. 2 is a flow chart of a data transmission method provided by an embodiment of the present specification;

FIG. 3 illustrates a schematic diagram of a data transmission method provided in accordance with one embodiment of the present description;

FIG. 4 is a flowchart illustrating a data transmission method according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of a data transmission device according to an embodiment of the present disclosure;

fig. 6 is a block diagram of a computing device according to an embodiment of the present disclosure.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.

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

It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

First, the noun terms to which one or more embodiments of the present specification relate are explained.

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

Change set: a changeset contains a changeset identification, a distribution status, and a set of tasks.

Subscribing: subscription, Subscription relationship includes topic, subscriber.

Topic: the Topic is used for realizing a concept defined by pushing different content capabilities to different devices, one task belongs to one Topic, and the devices can acquire all notifications under the Topic by subscribing to the Topic.

Task: including subject, object identification, timestamps, task data, and the like.

Software Defined Network (SDN): the method is a novel network innovation architecture and is an implementation mode of network virtualization.

In the present specification, two data transmission systems are provided, and the present specification relates to a data transmission method, a data transmission apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.

Referring to fig. 1, fig. 1 shows an architecture diagram of a data transmission system provided according to an embodiment of the present specification, the data transmission system including:

The task distribution node can be understood as a node for issuing a task, 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, and can acquire the task from the task distribution node and issue the task to the device node; a device node may be understood as a node of an application task; a set of tasks may be understood as a topic.

In practical application, referring to fig. 1, the data transmission system is composed of a storage computing node, a device agent node, and a device node, where the device agent node subscribes the storage computing node for a first-level subscription, and the device node registers and subscribes the device agent node for a second-level subscription, and the specific implementation manner is as follows:

the equipment agent node is a storage computing node which is responsible for distributing tasks and feeding back task states. Firstly, the storage computing node is responsible for distributing tasks to the equipment agent nodes, the storage computing node receives the tasks expressed in the form of change sets, the original change sets are stored in the data storage, the change sets are reorganized according to topics subscribed by different equipment agent nodes, and the reorganized change sets are issued to the corresponding equipment agents. Secondly, the storage computing node is also responsible for receiving the task state obtained from the device agent and summarizing the task state into the total task state.

The device broker node subscribes to topics and is responsible for distributing tasks to corresponding devices and obtaining task state feedback of the devices. A device proxy node obtains topics to which devices it proxies need to subscribe and proxies subscriptions to those topics. After receiving the change set from the storage computing node, the equipment agent node creates a sending task for the terminal equipment.

And the equipment node is registered to the equipment proxy node, processes the task issued by the equipment proxy node and feeds back the task state to the equipment proxy node.

In an implementation manner, the device node is configured to initiate a registration request to a device agent node, and establish the second subscription relationship with the device agent node when receiving a registration completion message sent by the device agent node.

For example, the device node 1 sends a registration request to the device agent node a, and the device agent node a returns a registration completion message to the device node 1, so that the device agent node a completes registration and establishes a bidirectional connection with the device node 1 to implement subsequent notification reception.

In one implementation manner, the device node is configured to determine a region attribute of each device agent node and determine a target device agent node according to the region attribute if there are multiple device agent nodes, and

and initiating a registration request to the target equipment proxy node, and establishing the second subscription relationship with the target equipment proxy node under the condition of receiving a registration completion message sent by the target equipment proxy node.

The geographical attribute of the device agent node may be understood as the geographical location of the device agent node, for example, the device agent node is located at a-ground.

In practical application, the distance between the geographical position of the device agent node and the geographical position of the device node has a great influence on the communication delay, and under the same other conditions, the closer the distance between the geographical position of the device agent node and the geographical position of the device node is, the smaller the communication delay is, and then the device may select a similar device agent node to reduce the communication delay and increase the stability.

For example, the device agent node includes a device agent node a and a device agent node B, and if the device agent node a is closer to the current device node, the device agent node a is selected as the target device agent node, and the second subscription relationship is established with the target device agent node.

In one implementation manner, the device node is configured to determine a task set attribute of each device agent node and determine a target device agent node according to the task set attribute, if a plurality of device agent nodes are provided, an

The task set attribute of the device broker node may be understood as the topic subscribed by the device broker node, for example, the topic subscribed by the device broker node includes topic a and topic B.

In practical application, the equipment proxy nodes can be distributed according to the types of topics, and the calculation pressure of the equipment proxy nodes can be reduced by dividing the equipment proxy nodes according to different topics.

For example, the device broker node includes a device broker node a and a device broker node B, the topic preparation subscribed by the device broker node a includes a topic a and a topic B, the topic preparation subscribed by the device broker node B includes a topic C and a topic D, and the device node needs to subscribe to the topic a, then the device broker node a is selected as the target device broker node, and the second subscription relationship is established with the target device broker node.

In an implementation manner, in the case of data change of a target task set, the task distribution node is configured to determine a target device agent node corresponding to the target task set according to the first subscription relationship, and issue the target task set to the target device agent node;

and the device agent node is configured to determine a target device node corresponding to a target task set according to the second subscription relationship under the condition of receiving the target task set issued by the task distribution node, and send the target task to the target device node.

In the case of changing the data of the target task set, it can be understood that there is a change in the data corresponding to the task, for example, the task a is added with one item of data.

In practical application, when a task distribution node receives data change in a task, the data change needs to be issued to a device agent node, and then the device agent node sends the data change to a related device node.

For example, if one item of data is added to the task of the topic a, determining the device agent node subscribing to the topic a, and issuing the added item of data in the topic a to the corresponding device agent node in the form of a change set, and after the device agent node does not receive the change set, determining the related device node subscribing to the topic a, and issuing the change set to the related device node.

In an implementation 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 a target task set carried in the task set modification instruction.

In practical applications, if it is possible that a device node needs to add a subscription to a new topic or delete a subscription to a certain topic, the task in the subscription relationship is deleted. For example, if the device node needs to add a subscription to topic B, the subscription relationship for topic B is added in the second subscription relationship between the device node and the device broker node.

In one implementation, the device broker node is configured to:

and determining a task set according to the second subscription relationship, and establishing a first subscription relationship of the task set under the condition that the first subscription relationship corresponding to the task set is not established.

In one implementation, the device broker node is further configured to:

determining a task set according to the second subscription relationship;

and under the condition that a first subscription relation corresponding to the task set is not established, establishing a first subscription relation to the task distribution node according to the task set.

In one implementation, the device broker node is further configured to:

determining corresponding equipment according to a second subscription relation corresponding to the task set;

and issuing the tasks in the task set to the corresponding equipment.

In one implementation, the device broker node is further configured to:

creating a issued transaction aiming at the task set, marking the state of the issued transaction as an analysis state, and feeding back the state of the issued transaction to the task distribution node;

and issuing the tasks in the task set to the corresponding equipment according to the issued transaction.

In one implementation, the device broker node is further configured to:

receiving a task distribution result returned by each equipment node;

and modifying the state of the issued transaction according to the task distribution result.

In one implementation, the device broker node is further configured to:

and under the condition that each task distribution result is successful, marking the state of the issued transaction as a successful state, and feeding back the state of the issued transaction to the task distribution node.

In one implementation, the device broker node is further configured to:

under the condition that any task distribution result is failed, the state of the issued transaction is marked as a failure state, and a task corresponding to the task distribution result is added into a failure task list, and

and feeding back the state of the issued transaction to the task distribution node.

In one implementation, the device broker node is further configured to:

re-acquiring the task set and recording the acquisition times;

and issuing the tasks in the task set to corresponding equipment according to the failure task list.

In one implementation, the device broker node is further configured to:

under the condition that the task is in the failed task list, a retransmission transaction is created for the equipment which fails in the task issuing;

and issuing the task to the corresponding equipment according to the retransmission affair.

In one implementation, the device broker node is further configured to:

receiving a registration request of the equipment node, and matching a target equipment proxy node according to the region attribute carried by the registration request;

forwarding the registration request to a target device proxy node.

In one implementation, the device broker node is further configured to:

receiving a registration request of the equipment node, and matching a target equipment proxy node according to the task set attribute carried by the registration request;

forwarding the registration request to a target device proxy node.

An embodiment of this specification provides a data transmission system including: the task distribution node is configured to issue a task set corresponding to a first subscription relation to the equipment agent node according to the first subscription relation with the equipment agent node; the device agent node is configured to establish a first subscription relation to the task distribution node according to a second subscription relation with the device node, and issue the tasks in the task set to the corresponding device node according to the second subscription relation with the device node under the condition that the task set corresponding to the first subscription relation is obtained from the task distribution node; and the equipment node is configured to acquire the task issued by the equipment proxy node according to the second subscription relation with the equipment proxy node. Due to the fact that the equipment agent nodes are added, the equipment nodes can subscribe the tasks from the equipment agent nodes and then subscribe the tasks to the task distribution nodes through the equipment agent nodes, and therefore the communication resource usage amount of the task distribution nodes is reduced.

Referring to fig. 2, fig. 2 shows a flowchart of a data transmission method provided according to an embodiment of the present specification, which specifically includes the following steps.

Step 202: and establishing a first subscription relation to the task distribution node according to the second subscription relation with the equipment node.

In practical application, the device node needs to register with the device proxy node to establish a second subscription relationship, and then according to the topic subscribed by the device node, the device proxy node establishes a first subscription relationship with the task distribution node.

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

determining a task set according to the second subscription relationship;

For example, referring to fig. 3, fig. 3 shows a schematic diagram illustrating a data transmission method provided according to an embodiment of the present specification, which includes a storage computing node, a device broker node a and a device broker node B, and a device node 1, a device node 2, a device node 3, a device node 4, and a device node 5, determines a topic a according to a second subscription relationship of the device node 1 and the device broker node a, determines whether a first subscription relationship with the storage computing node containing the topic a exists, does not perform subscription processing if the first subscription relationship with the storage computing node containing the topic a already exists, and if not, creates a subscription relationship between the topic a and the device broker node a, and stores a new subscription relationship in a memory of the device broker node a.

Step 204: and under the condition that the task set corresponding to the first subscription relationship is obtained from the task distribution node, the tasks in the task set are issued to the corresponding equipment nodes according to the second subscription relationship with the equipment nodes.

In practical application, under the condition that a task distributing node receives a task, a device agent node acquires a subscribed related task set and issues the task in the subscribed related task set to a device node registered locally. In an implementation manner, the issuing the task in the task set to the corresponding device node includes:

and issuing the tasks in the task set to the corresponding equipment.

In practical application, after receiving the change set, the device agent finds all devices paying attention to the topic according to the topic to obtain a device list.

For example, referring to fig. 3, for the 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, and issues the task in topic a to the device node 1, device node 2, device node 3, and device node 4.

In an implementation manner, according to the task of issuing the task set to the corresponding device, the method includes:

In practical applications, each asynchronous task is issued as a token, and all token states are queried in time sequence. The token has six states, namely an initialization state, an analysis state, an operating state, a success state, an operating error state and a failure state. The token stores two pieces of information, token content and token state. A token content storage changeset comprising a plurality of topics and a task list contained in each topic; the token state stores progress updates including state, start time, number of affected devices, number of affected tasks, number of completed devices, number of completed tasks, and number of errors. The state of the 'initialization state' indicates that the token is established for the first time, the content of the token and the state of the token are stored in an external memory at the moment, and the token can still be recovered from the external memory when the intermediate service goes down; the state of "analysis state" indicates that the device agent is in an analysis state, and at this time, the device agent also calculates a device list associated with the change set and creates a task to be issued; the 'running state' represents an execution state, and the device agent processes a task issued to the device; "success status" indicates that execution is complete; "error in progress" indicates that a delivered task has occurred, but execution has not yet been completed; a "failed state" indicates that execution has completed but an error occurred. Under the condition of issuing the tasks in the task set, firstly, traversing the device list, and creating an issuing task for the devices in each device list, wherein in the process, the task state is marked as an analysis state. And after all the issued tasks are established, the equipment agent feeds the task state back to the storage computing node. And the storage computing node performs summary computation on the obtained feedback information and stores the execution condition of the change set into a database for future reference. The feedback information includes the number of influencing devices, the number of influencing tasks, the number of completing devices, the number of completing tasks, and the number of errors.

For example, the device list is: the device node 1, the device node 2, the device node 3 and the device node 4 respectively issue tasks in the topic A to the device node 1, the device node 2, the device node 3 and the device node 4, namely, the issued transaction is created, the state of the issued transaction is set to be an analysis state, and the tasks in the topic A are respectively issued to the device node 1, the device node 2, the device node 3 and the device node 4 according to the issued transaction.

In an implementation manner, the data transmission method in this embodiment further includes:

receiving a task distribution result returned by each equipment node;

In practical application, after all issued tasks are created, the device agent node feeds the task state back to the storage computing node, and after the storage computing node receives the task state feedback of all connected device agent nodes, the task state feedback is collected into total task state feedback and marked as an "operating state".

For example, the tasks in the topic a are issued to the device node 1, the device node 2, the device node 3, and the device node 4 respectively according to the issued transactions, after the issued transactions are completed, the issued transactions are all marked as "running state", and the state of the issued transactions is fed back to the storage computing node, that is, the state of the issued transactions of the device node 1 is "running state", the state of the issued transactions of the device node 2 is "running state", the state of the issued transactions of the device node 3 is "running state", and the state of the issued transactions of the device node 4 is "running state", so that the storage computing node feeds back the total task state and marks the total task state as "running state".

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

In practical application, the device agent node starts to execute the distribution task, and after the task execution on each device is completed, the storage computing node marks the task as a "success state". And when the storage settlement node receives the return messages of all the related equipment agent nodes of the change set and the return messages are in the finished state, marking the change set as the finished state and storing the finished state in the database.

For example, the device node 1 executes a task in the topic a, after the execution is completed, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 1 as a "successful state", the device node 2 executes the task in the topic a, after the execution is completed, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 2 as a "successful state", the device node 3 executes the task in the topic a, after the execution is completed, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 3 as a "successful state", the device node 4 executes the task in the topic a, after the execution is completed, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 4 as a "successful state", correspondingly, the 'success state' of the issued transaction is fed back to the storage computing node, so that the storage computing node feeds back the overall task state and marks the overall task state as the 'success state'.

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

In practical applications, if execution fails, the task is marked as failed and added to the failed task list of the device. When the task execution state is refreshed, the equipment agent node judges whether an error occurs for the first time according to the task completion condition and whether the distance from the last feedback task condition is more than the cooling time.

For example, the device node 1 executes a task in the topic a, after the execution is completed, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 1 as a "successful state", the device node 2 executes the task in the topic a, after the execution fails, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 2 as a "failed state", the device node 3 executes the task in the topic a, after the execution is completed, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 3 as a "successful state", the device node 4 executes the task in the topic a, after the execution is completed, a message is fed back to the device agent node a, the device agent node marks the state of the issued transaction of the device node 4 as a "successful state", correspondingly, the 'success state' of the issued transaction is fed back to the storage computing node, so that the storage computing node feeds back the total task state and marks the total task state as an 'error state in operation'. And adding 'the task failure in the topic A issued to the equipment node 2' into the failure task list.

In one implementation, the method further comprises:

re-acquiring the task set and recording the acquisition times;

In practical application, when a task distribution result is failure, whether the failure exceeds the configured retry delay time is judged, and if the failure exceeds the configured retry delay time, a retry mechanism is triggered to retry the task delivery.

For example, the device node 2 executes the task on topic a, after the execution fails, a message is fed back to the device agent node a, the device agent node marks the status of the issued transaction of the device node 2 as "failure status", and after the device node 2 fails to execute the task on topic a for 3 milliseconds, a retry mechanism is triggered.

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

In practical application, the change set is read from the storage, and the subscription of each topic is recalculated and distributed to the corresponding home device agent, and the retry number of the issued task is increased by one.

For example, the device broker node finds all devices that concern the topic according to topic a to obtain a device list, where the device list is: device node 1, device node 2, device node 3, device node 4, traverse the device list and check if the task exists in the failed task list, if so, create a re-send task.

In an implementation manner, if there is "failure to issue the task in topic a to the device node 2" in the failed task list, the task in topic a is issued to the device node 2, that is, a retransmission transaction is created, and the status of the issued transaction is set to "analysis status".

In another implementable manner, it is possible that an error has been resolved before the retry mechanism, and the corresponding task is not present in the failed task list, and if not, the task is ignored if it indicates that the device has successfully retransmitted.

For example, if there is no "failure to issue a task on topic a to the device node 2" in the failed task list, retry of "failure to issue a task on topic a to the device node 2" is ignored.

Further, the retransmission results are fed back to the task distribution node in a gathering mode, if the retransmission results are successful, the token state is set to be the 'success state', otherwise, the token state is still the 'failure state', and if the retry times exceed the retry threshold, the retransmission results are output to the alarm system.

For example, if "the task in the topic a is delivered to the device node 2 fails" in the failed task list, the task in the topic a is delivered to the device node 2, that is, a retransmission transaction is created, and the status of the delivery transaction is set to "analysis status", and when the device node 2 feeds back that the status of the delivery transaction is "success status", the retransmission result is summarized and fed back to the task distribution node, that is, the device agent node marks the status of the delivery transaction of the device node 1 as "success status", the device agent node marks the status of the delivery transaction of the device node 2 as "success status", the device agent node marks the status of the delivery transaction of the device node 3 as "success status", the device agent node marks the status of the delivery transaction of the device node 4 as "success status", the device node 1, the device node 2, the states of the issued transactions of the equipment nodes 3 and 4 are fed back to the task distribution node, and the token state is set as a success state.

If the state of the issued transaction fed back by the equipment node 2 is still in a failure state, adding one to the retry number of the issued task, and if the threshold value of the retry number is three, outputting the retry number to an alarm system when the retry number reaches three so as to solve the problem manually.

In one implementation, the method further comprises:

forwarding the registration request to a target device proxy node.

Therein, a geographical attribute may be understood as a geographical location, e.g. a-ground.

In practical applications, as described in the foregoing embodiments, under the same other conditions, the closer the distance between the geographic location of the device agent node and the geographic location of the device node is, the smaller the communication delay is, and then the device may select a close device agent node to reduce the communication delay and increase the stability.

For example, the device agent node includes a device agent node a and a device agent node B, the device agent node a is closer to the current device node, when the device node sends the registration request to the device agent node B, the device agent node B forwards the registration request to the device agent node a, and the device agent node a serves as the target device agent node and establishes the second subscription relationship with the target device agent node a.

In one implementation, the method further comprises:

forwarding the registration request to a target device proxy node.

Wherein the task set attribute can be understood as a subscribed topic, for example, the subscribed topic includes topic a and topic B.

In practical application, as described in the foregoing embodiment, the device proxy nodes may also be allocated according to the types of topics, and dividing the device proxy nodes according to different topics may reduce the computational pressure of the device proxy nodes.

For example, the device agent node includes a device agent node a and a device agent node B, the topic equipment subscribed by the device agent node a includes a topic a and a topic B, the topic equipment subscribed by the device agent node B includes a topic C and a topic D, the device node needs to subscribe to the topic a, in case that 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, and the device agent node a serves as a target device agent node and establishes the second subscription relationship with the target device agent node a.

An embodiment of the present specification provides a data transmission method, including: the method comprises the steps of establishing a first subscription relation to a task distribution node according to a second subscription relation with an equipment node, issuing tasks in the task set to the corresponding equipment node according to the second subscription relation with the equipment node under the condition that a task set corresponding to the first subscription relation is obtained from the task distribution node, and enabling the equipment node to subscribe the tasks from the equipment proxy node due to the fact that the equipment proxy node is added, and then subscribing the tasks to the task distribution node through the equipment proxy node, so that the use amount of communication resources of the task distribution node is reduced.

The following describes the data transmission method further by taking an application of the data transmission method provided in this specification to a device agent node as an example, with reference to fig. 4. Fig. 4 shows a flowchart of a processing procedure of a data transmission method provided in an embodiment of the present specification, which specifically includes the following steps.

Step 402: and the equipment agent node determines a task set according to the second subscription relation.

For example, topic a is determined from the second subscription relationship of device node 1 and device broker node a.

Step 404: and under the condition that the first subscription relation corresponding to the task set is not established, the equipment proxy node establishes the first subscription relation to the task distribution node according to the task set.

Following the above example, it is determined whether there is a first subscription relationship with the storage computing node containing topic a, if there is already a first subscription relationship with the storage computing node containing topic a, no subscription processing is performed, if not, a subscription relationship between topic a and device broker node a is created, and a new subscription relationship is stored in the memory of device broker node a.

Step 406: and the equipment agent node determines corresponding equipment according to the second subscription relation corresponding to the task set.

Following the above example, for the 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: and the equipment agent node creates a issued transaction aiming at the task set, marks the state of the issued transaction as an analysis state and feeds back the state of the issued transaction to the task distribution node.

Following the above example, the device list is: the device node 1, the device node 2, the device node 3 and the device node 4 respectively issue tasks in the topic A to the device node 1, the device node 2, the device node 3 and the device node 4, namely, the issued transaction is created, and the state of the issued transaction is set to be an analysis state.

Step 410: and the equipment agent node issues the tasks in the task set to the corresponding equipment according to the issuing transaction.

And along the use example, the tasks in the topic A are issued to the equipment node 1, the equipment node 2, the equipment node 3 and the equipment node 4 respectively according to the issued transactions.

Step 412: and the equipment proxy node receives the task distribution result returned by each equipment node.

Following the above example, the device node 1 executes 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 state of the issued transaction of the device node 1 as "successful state", the device node 2 executes the task in topic a, after the execution is finished, feeding back a message to the equipment proxy node A, marking the state of the issued transaction of the equipment node 2 as a 'success state' by the equipment proxy node, executing the task in the topic A by the equipment node 3, after the execution is finished, feeding back a message to the equipment agent node A, marking the state of the issued transaction of the equipment node 3 as a successful state by the equipment agent node, executing the task in the topic A by the equipment node 4, after the execution is completed, a message is fed back to the device agent node a, and the device agent node marks the state of the issued transaction of the device node 4 as a "successful state".

Step 414: and the equipment agent node marks the state of the issued transaction as a successful state under the condition that the distribution result of each task is successful, and feeds the state of the issued transaction back to the task distribution node.

And feeding back the success state of the issued transaction to the storage computing node along the use example so that the storage computing node feeds back the total task state and marks the total task state as the success state.

In the embodiment of the specification, because the device agent node is added, the device node can subscribe the task from the device agent node, and then subscribe the task to the task distribution node through the device agent node, so that the use amount of communication resources of the task distribution node is reduced.

This specification also provides a data transmission system including:

and the software defined network node is configured to acquire the task issued by the software defined network agent node according to a second subscription relation with the software defined network agent node.

The software-defined network proxy node may be a gateway, a private cloud, or other devices.

In an implementable manner, the software defined network node is configured to initiate a registration request to a software defined network proxy node, and to establish the second subscription relationship with the device proxy upon receipt of a complete registration message sent by the software defined network proxy node.

In an implementation manner, the software-defined network proxy node is configured to determine a task set according to the second subscription relationship, and establish a first subscription relationship of the task set without establishing a first subscription relationship corresponding to the task set.

In one implementation, the software-defined network node is configured to determine a regional attribute of each software-defined network proxy node and determine a target software-defined network proxy node according to the regional attribute, in case that the plurality of software-defined network proxy nodes are provided, and

and initiating a registration request to the target software-defined network agent node, and establishing the second subscription relationship with the target device agent under the condition of receiving a registration completion message sent by the target software-defined network agent node.

In an implementable manner, the software defined network node is configured to determine a task set attribute for each software defined network proxy node and determine a target software defined network proxy node based on the task set attribute, if there are a plurality of software defined network proxy nodes, an

In an implementation manner, in the case of data change of a target task set, the software-defined network task distribution node is configured to determine a target software-defined network proxy node corresponding to the target task set according to the first subscription relationship, and issue the target task set to the target software-defined network proxy node;

and the software defined network agent node is configured to determine a target software defined network node corresponding to a target task set according to the second subscription relationship under the condition of receiving the target task set issued by the software defined network task distribution node, and send 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 second subscription relationship with the software defined network proxy node according to a target task set carried in the task set modification instruction.

In one implementation, the software-defined network proxy node is configured to:

In one implementation, the software-defined network proxy node is further configured to:

determining a task set according to the second subscription relationship;

and under the condition that a first subscription relation corresponding to the task set is not established, establishing a first subscription relation to the software defined network task distribution node according to the task set.

and issuing the tasks in the task set to the corresponding equipment.

creating a issued transaction aiming at the task set, marking the state of the issued transaction as an analysis state, and feeding back the state of the issued transaction to the software defined network task distribution node;

receiving a task distribution result returned by each software-defined network node;

and under the condition that the distribution result of each task is successful, marking the state of the issued transaction as a successful state, and feeding back the state of the issued transaction to the software defined network task distribution node.

and feeding back the state of the issued transaction to the software defined network task distribution node.

re-acquiring the task set and recording the acquisition times;

receiving a registration request of the software defined network node, and matching a target software defined network proxy node according to a region attribute carried by the registration request;

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

receiving a registration request of the software defined network node, and matching a target software defined network proxy node according to task set attributes carried by the registration request;

An embodiment of this specification provides a data transmission system including: the software defined network task distribution node is configured to issue a task set corresponding to a first subscription relation to the software defined network agent node according to the first subscription relation with the software defined network agent node; the software defined network agent node is configured to establish a first subscription relationship to the software defined network task distribution node according to a second subscription relationship with the software defined network node, and under the condition that a task set corresponding to the first subscription relationship is obtained from the software defined network task distribution node, tasks in the task set are issued to the corresponding software defined network node according to the second subscription relationship with the software defined network node; and the software-defined network node is configured to acquire the task issued by the software-defined network agent node according to the second subscription relation with the software-defined network agent node. Due to the fact that the equipment agent nodes are added, the equipment nodes can subscribe the tasks from the equipment agent nodes and then subscribe the tasks to the task distribution nodes through the equipment agent nodes, and therefore the communication resource usage amount of the task distribution nodes is reduced.

Corresponding to the above method embodiment, the present specification further provides an embodiment of a data transmission device, and fig. 5 shows a schematic structural diagram of a data transmission device provided in an embodiment of the present specification. As shown in fig. 5, the apparatus includes:

a creating module 502 configured to establish a first subscription relationship to the task distribution node according to a second subscription relationship with the device node;

the distributing module 504 is configured to, when the task set corresponding to the first subscription relationship is obtained from the task distributing node, issue the tasks in the task set to the corresponding device nodes according to the second subscription relationship with the device nodes.

In one implementation, the creating module 502 is further configured to:

determining a task set according to the second subscription relationship;

In one implementation, the distribution module 504 is further configured to:

and issuing the tasks in the task set to the corresponding equipment.

In one implementation, the distribution module 504 is further configured to:

receiving a task distribution result returned by each equipment node;

In one implementation, the distribution module 504 is further configured to:

re-acquiring the task set and recording the acquisition times;

In one implementation, the distribution module 504 is further configured to:

creating a retransmission transaction for a device that failed the task delivery if the task is in the failed task list

An embodiment of the present specification provides a data transmission apparatus, where the data transmission apparatus includes: the creation module is configured to establish a first subscription relation to the task distribution node according to a second subscription relation with the equipment node; and the distribution module is configured to issue the tasks in the task set to the corresponding equipment nodes according to the second subscription relationship with the equipment nodes under the condition that the task set corresponding to the first subscription relationship is obtained from the task distribution node. Due to the fact that the equipment agent nodes are added, the equipment nodes can subscribe the tasks from the equipment agent nodes and then subscribe the tasks to the task distribution nodes through the equipment agent nodes, and therefore the communication resource usage amount of the task distribution nodes is reduced.

The above is a schematic scheme of the data transmission apparatus of this embodiment. It should be noted that the technical solution of the data transmission apparatus and the technical solution of the data transmission method belong to the same concept, and details that are not described in detail in the technical solution of the data transmission apparatus can be referred to the description of the technical solution of the data transmission method.

FIG. 6 illustrates a block diagram of a computing device 600 provided in accordance with one embodiment of the present description. The components of the computing device 600 include, but are not limited to, a memory 610 and a processor 620. The processor 620 is coupled to the memory 610 via a bus 630 and a database 650 is used to store data.

Computing device 600 also includes access device 640, access device 640 enabling computing device 600 to communicate via one or more networks 660. Examples of such 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 communication networks such as the internet. Access device 640 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the above-described components of computing device 600, as well as other components not shown in FIG. 6, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 6 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.

Computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, 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.

Wherein the processor 620 is configured to execute computer-executable instructions that, when executed by the processor, implement the steps of the data transmission method described above.

The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the data transmission method belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the data transmission method.

An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which when executed by a processor, implement the steps of the above data transmission method.

The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the data transmission method, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the data transmission method.

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

The above is an illustrative scheme of a computer program of the present embodiment. It should be noted that the technical solution of the computer program and the technical solution of the data transmission method belong to the same concept, and details that are not described in detail in the technical solution of the computer program can be referred to the description of the technical solution of the data transmission method.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U.S. disk, removable hard disk, magnetic diskette, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signal, telecommunications signal, and software distribution medium, etc. It should be noted that the computer-readable medium may contain suitable additions or subtractions depending on the requirements of legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer-readable media may not include electrical carrier signals or telecommunication signals in accordance with legislation and patent practice.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts, but those skilled in the art should understand that the present embodiment is not limited by the described acts, because some steps may be performed in other sequences or simultaneously according to the present embodiment. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for an embodiment of the specification.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the embodiments. The specification is limited only by the claims and their full scope and equivalents.

Claims

1. A data transmission system comprising:

and the equipment node is configured to acquire the task issued by the equipment agent node according to the second subscription relation with the equipment agent node.

2. The system of claim 1, further comprising:

the device node is configured to initiate a registration request to a device agent node, and establish the second subscription relationship with the device agent node when receiving a registration completion message sent by the device agent node.

3. The system of claim 1, further comprising:

and the equipment proxy node is configured to determine a task set according to the second subscription relationship, and establish a first subscription relationship of the task set under the condition that the first subscription relationship corresponding to the task set is not established.

4. The system of claim 1, further comprising:

the device node is configured to determine a region attribute of each device proxy node and determine a target device proxy node according to the region attribute, if a plurality of device proxy nodes are provided, an

5. The system of claim 1, further comprising:

the device node is configured to determine a task set attribute of each device agent node and determine a target device agent node according to the task set attribute, if a plurality of device agent nodes are provided, an

6. The system of claim 1, further comprising:

under the condition of data change of a target task set, the task distribution node is configured to determine a target device agent node corresponding to the target task set according to the first subscription relation and issue the target task set to the target device agent node;

7. The system of claim 1, further comprising:

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

8. A data transmission method is applied to a device agent node and comprises the following steps:

9. The method of claim 8, the establishing a first subscription relationship to the task distribution node according to a second subscription relationship with a device node, comprising:

determining a task set according to the second subscription relationship;

10. The method of claim 8, wherein the issuing the tasks in the task set to the corresponding device nodes comprises:

and issuing the tasks in the task set to the corresponding equipment.

11. The method of claim 10, wherein the issuing of the task in the task set to the corresponding device comprises:

12. The method of claim 11, further comprising:

receiving a task distribution result returned by each equipment node;

13. The method of claim 12, the modifying the state of the issued transaction according to the task distribution result, comprising:

14. The method of claim 12, the modifying the state of the issued transaction according to the task distribution result, comprising:

15. The method of claim 14, further comprising:

re-acquiring the task set and recording the acquisition times;

16. The method of claim 15, wherein the issuing the tasks in the task set to the corresponding devices according to the failed task list comprises:

under the condition that the task is in the failed task list, a retransmission transaction is created for the equipment with failed task issuing;

17. The method of claim 8, further comprising:

forwarding the registration request to a target device proxy node.

18. The method of claim 8, further comprising:

forwarding the registration request to a target device proxy node.

19. A data transmission system comprising:

20. A computing device, comprising:

a memory and a processor;

the memory is for storing computer-executable instructions and the processor is for executing the computer-executable instructions, which when executed by the processor, perform the steps of the data transmission method of any one of claims 8 to 18.

21. A computer-readable storage medium storing computer-executable instructions which, when executed by a processor, perform the steps of the data transmission method of any one of claims 8 to 18.