CN114885020B

CN114885020B - Data transmission system and method

Info

Publication number: CN114885020B
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: 2024-02-13
Anticipated expiration: 2042-04-02
Also published as: CN114885020A; WO2023186154A1

Abstract

The embodiment of the specification provides a data transmission system and a method, wherein the data transmission system comprises: the task distribution node is configured to issue a task set corresponding to the first subscription relation to the equipment proxy node according to the first subscription relation with the equipment proxy node; the device proxy 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 tasks in the task set to the corresponding device node according to the second subscription relation with the device node under the condition that a 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. Because the equipment proxy node is added, the equipment node can subscribe the task from the equipment proxy node, and then subscribe the task from the task distribution node through the equipment proxy node, so that the communication resource usage amount of the task distribution node 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 one large-scale terminal and server. In such systems, it is often necessary to distribute tasks to different terminals for execution at high frequency and to complete feedback of the results, and once a terminal has an error, it is necessary to retry the task in time. In the process, a task belongs to a topic, and a terminal obtains the task of issuing the topic in a change set form by subscribing the topic. The subscription relation between the task distribution using equipment and topics is used, the dispatched tasks are timely handed to the target terminal, the realization of the tasks is confirmed, and feedback is obtained; when the task is issued and executed, the total task execution failure may be caused by the error of the terminal equipment or the offline of the terminal equipment, so that the task failure error occurring on the terminal needs to be found in time, and a certain logic retry is needed after the error of the terminal is found, so that the error recovery is realized, and the normal operation of the whole configuration distribution system is maintained. Therefore, the methods of task distribution and error recovery are critical to the field of configuration distribution.

However, with the increase of system complexity and the continuous expansion of scale, a massive terminal scenario needs to accommodate a massive number of terminals, and the massive number of terminals means that a massive subscription relationship, for example, one topic in a cloud network needs to distribute tasks to one terminal, then it notifies all devices subscribed to it, and such massive subscription connection relationship and notification will occupy a large amount of unnecessary storage and computing resources. While in large-scale terminal-scene systems, such as cloud networks, the computational and storage resources are limited, if the task distribution and error recovery functions take up too much resources, this will lead to a decrease in network performance.

Disclosure of Invention

In view of this, the present description embodiments provide two data transmission systems. One or more embodiments of the present specification relate to a data transmission method, a data apparatus, a computing device, a computer-readable storage medium, and a computer program to solve the technical drawbacks of the related art.

According to a first aspect of embodiments of the present specification, there is provided a data transmission system comprising:

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

the device proxy 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 tasks in the task set to the corresponding device node according to the second subscription relation with the device node under the condition that a 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 agent node according to the second subscription relation with the equipment agent node.

According to a second aspect of embodiments of the present specification, 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 relation is obtained from the task distribution node, issuing the tasks in the task set to the corresponding equipment nodes according to the second subscription relation of the equipment nodes.

According to a third aspect of embodiments of the present specification, there is provided a data transmission system comprising:

the system comprises a software defined network task distribution node, a software defined network proxy node and a software defined network task processing node, wherein 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 proxy node according to the first subscription relation with the software defined network proxy node;

a software defined network proxy node configured to establish a first subscription relation to the software defined network task distribution node according to a second subscription relation with the software defined network node, and to issue tasks in the task set to corresponding software defined network nodes according to the second subscription relation with the software defined network node when a task set corresponding to the first subscription relation is obtained from the software defined network task distribution node;

And the software defined network node is configured to acquire tasks issued by the software defined network proxy node according to the second subscription relation with the software defined network proxy node.

According to a fourth aspect of embodiments of the present specification, there is provided a data transmission apparatus comprising:

the creation module is configured to create 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 distribute the tasks in the task set to the corresponding equipment nodes according to the second subscription relation with the equipment nodes under the condition that the task set corresponding to the first subscription relation is obtained from the task distribution nodes.

According to a fifth aspect of embodiments of the present specification, there is provided a computing device comprising:

a memory and a processor;

the memory is configured to store computer-executable instructions that, when executed by the processor, perform the steps of the data transmission method described above.

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

According to a seventh aspect of the embodiments of the present specification, there is provided a computer program, wherein the computer program, when executed in a computer, causes the computer to perform the steps of the data transmission method described above.

Drawings

Fig. 1 shows an architecture diagram of a data transmission system provided according to one embodiment of the present specification;

fig. 2 is a flowchart of a data transmission method according to an embodiment of the present disclosure;

fig. 3 is a schematic diagram of a data transmission method according to an embodiment of the present disclosure;

FIG. 4 is a flowchart of a data transmission method according to one 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 provided in one embodiment of the present description.

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 other forms than described herein and similarly generalized by those skilled in the art to whom this disclosure pertains without departing from the spirit of the disclosure and, therefore, this disclosure is not limited by the specific implementations disclosed below.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments 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 or 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 in one or more embodiments of this specification 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 may also be referred to as a second, and similarly, a second may 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 "at … …" or "responsive to a determination", depending on the context.

First, terms related to one or more embodiments of the present specification will be explained.

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

Change set: a change set contains a change set identification, a distribution state, and a set of tasks.

Subscription: subscription relationships include topics, subscribers.

Topic: topic, which is used to implement concepts defined by pushing different content capabilities to different devices, a task belongs to a Topic, and devices can acquire all notifications under the Topic by subscribing to the Topic.

Tasks: including subject matter, object identification, time stamp, task data, etc.

Software defined network (Software Defined Network, SDN): 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 according to an embodiment of the present specification, the data transmission system includes:

Wherein a task distribution node may be understood as a node that issues tasks, e.g., 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 task set may be understood as a topic.

In practical application, referring to fig. 1, the data transmission system is composed of three parts, namely a storage computing node, an equipment proxy node and an equipment node, wherein the equipment proxy node subscribes the storage computing node as a first-level subscription, and the equipment node registers and subscribes the equipment proxy node as a second-level subscription, and the specific implementation modes are as follows:

the device proxy node is a storage computing node, and the storage computing node is responsible for the distribution of tasks and the feedback of task states. Firstly, a storage computing node is responsible for distributing tasks to equipment proxy nodes, the storage computing node receives tasks expressed in the form of change sets, the original change sets are stored in a data storage, the change sets are reorganized according to topics subscribed by different equipment proxy nodes, and the reorganized change sets are issued to corresponding equipment proxy nodes. Second, the storage compute node is also responsible for receiving the task state obtained from the device agents and aggregating it into a total task state.

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

The equipment node registers 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 one implementation, the device node is configured to initiate a registration request to a device proxy node, and establish the second subscription relationship with the device proxy when receiving a registration completion message sent by the device proxy node.

For example, the device node 1 sends a registration request to the device proxy node a, and the device proxy node a returns a registration completion message to the device node 1, so that the device proxy node a completes registration and creates a bidirectional connection with the device node 1 for implementing subsequent notification reception.

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

And initiating a registration request to the target equipment proxy node, and establishing the second subscription relation with the target equipment proxy under the condition that a registration completion message sent by the target equipment proxy node is received.

The regional attribute of the device proxy node may be understood as a geographic location of the device proxy node, for example, the device proxy node is located in a place.

In practical application, the distance between the geographic position of the device proxy node and the geographic position of the device node has great influence on communication delay, and under the condition that other conditions are the same, the closer the distance between the geographic position of the device proxy node and the geographic position of the device node is, the smaller the communication delay is, so that the device can select similar device proxy nodes to reduce the communication delay and increase the stability.

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

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

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

In practical application, the device proxy nodes can be distributed according to the types of topics, and the device proxy nodes can be divided according to different topics, so that the calculation pressure of the device proxy nodes can be reduced.

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

In one implementation manner, under the condition that data of a target task set is changed, the task distribution node is configured to determine a target device proxy node corresponding to the target task set according to the first subscription relationship, and send the target task set to the target device proxy node;

And the device proxy node is configured to determine a target device node corresponding to the target task set according to the second subscription relation under the condition that the target task set issued by the task distribution node is received, and send the target task to the target device node.

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

In practical application, when the task distribution node receives the data change in the task, the data change is sent to the equipment proxy node, and then the equipment proxy node sends the relevant equipment node.

For example, if one item of data is added in the task of the topic a, determining the device proxy node subscribed to the topic a, and transmitting the added item of data in the topic a to the corresponding device proxy node in the form of a change set, and after the device proxy node does not receive the change set, determining the relevant device node subscribed to the topic a and transmitting the change set to the relevant device node.

In one implementation, the device node is configured to respond to a task set modification instruction, and update the second subscription relation with the device proxy node according to a target task set carried in the task set modification instruction.

In practical applications, the device node may need to add a subscription of a new topic or delete a subscription of a topic, and then delete the task in the subscription relationship. For example, if the device node needs to increase the subscription of topic B, the subscription relationship of topic B is added in the second subscription relationship of the device node and the device proxy node.

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

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

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

determining a task set according to the second subscription relation;

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

In one implementation, the device proxy 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 proxy node is further configured to:

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

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

In one implementation, the device proxy 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 proxy node is further configured to:

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

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

if any task distribution result is failure, marking the state of the issued transaction as failure state, adding the task corresponding to the task distribution result in a failure task list, and

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

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

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

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

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

creating a resending transaction for the equipment with failed task issuing under the condition that the task is in the failed task list;

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

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

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

and forwarding the registration request to a target device proxy node.

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

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

and forwarding the registration request to a target device proxy node.

The embodiment of the present specification provides a data transmission system including: the task distribution node is configured to issue a task set corresponding to the first subscription relation to the equipment proxy node according to the first subscription relation with the equipment proxy node; the device proxy 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 tasks in the task set to the corresponding device node according to the second subscription relation with the device node under the condition that a 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. Because the equipment proxy node is added, the equipment node can subscribe the task from the equipment proxy node, and then subscribe the task from the task distribution node through the equipment proxy node, so that the communication resource usage amount of the task distribution node is reduced.

Referring to fig. 2, fig. 2 shows a flowchart of a data transmission method according to an embodiment of the present disclosure, 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 the device proxy node establishes a first subscription relationship with the task distribution node according to topics subscribed by the device node.

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

determining a task set according to the second subscription relation;

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 disclosure, where the method includes a storage computing node, a device proxy node a and a device proxy node B, and device nodes 1, 2, 3, 4, and 5, determining a topic a according to a second subscription relationship between the device nodes 1 and the device proxy node a, determining whether a first subscription relationship between the topic a and the storage computing node exists, if the first subscription relationship between the topic a and the storage computing node already exists, not performing subscription processing, if the first subscription relationship between the topic a and the storage computing node does not exist, creating a subscription relationship between the topic a and the device proxy node a, and storing a new subscription relationship in a memory of the device proxy node a.

Step 204: and under the condition that the task set corresponding to the first subscription relation is obtained from the task distribution node, issuing the tasks in the task set to the corresponding equipment nodes according to the second subscription relation of the equipment nodes.

In practical application, under the condition that the task distribution node receives the task, the device proxy node acquires the subscribed related task set and issues the subscribed related task set to the locally registered device node. In one 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 the device agent receives the change set, all devices focusing on the topic are found according to the topic, and a device list is obtained.

For example, referring to fig. 3, for the device proxy node a, if the task set is topic a, the second subscription relationship determines that the corresponding device is device node 1, device node 2, device node 3, device node 4, and issues tasks in topic a to device node 1, device node 2, device node 3, and device node 4.

In one implementation, according to issuing the task in the task set to the corresponding device, the method includes:

In practical applications, each asynchronous task issue is called a token, and all token states are queried in time sequence. The token has six states, namely an initialization state, an analysis state, an operation state, a success state, an operation error state and a failure state. The token stores two pieces of information, token content and token state. The token content storage change set comprises a plurality of topics and a task list contained in each topic; the token state stores progress updates including state, start time, number of influencing devices, number of influencing tasks, number of completing devices, number of completing tasks, and number of errors. The initialization state indicates that the token is established for the first time, at the moment, the content of the token and the token state are stored in an external memory, and intermediate service is down in time and can still be recovered from the external memory; the analysis state indicates that the device agent is in an analysis state, and the device agent is also calculating a device list associated with the change set and creating an issuing task; "running state" means the execution state, and the device agent processes the task issued to the device; "successful status" indicates execution completion; "error status in run" indicates that an issuing task has occurred, but execution has not yet been completed; the "failure state" indicates that execution has completed but an error has occurred. Under the condition of issuing the tasks in the task set, the device list is traversed first, the issued tasks are created for the devices in each device list, and in the process, the task state is marked as an analysis state. After all the issuing tasks are created, the device agent feeds back the task state to the storage computing node. And the storage computing node gathers and computes the obtained feedback information, and stores the execution condition of the change set into a database for standby. The feedback information comprises the number of influencing devices, the number of influencing tasks, the number of finishing devices, the number of finishing tasks and the number of errors.

For example, the list of devices is: the device node 1, the device node 2, the device node 3 and the device node 4 issue tasks in the topic a to the device node 1, the device node 2, the device node 3 and the device node 4 respectively, namely create an issue transaction, set the state of the issue transaction to be an 'analysis state', and issue the tasks in the topic a to the device node 1, the device node 2, the device node 3 and the device node 4 respectively according to the issue transaction.

In one implementation manner, the data transmission method in the embodiment of the present disclosure further includes:

receiving a task distribution result returned by each equipment node;

In practical application, after all the issued tasks are created, the device proxy node feeds back task states to the storage computing node, and after the storage computing node receives the task state feedback of all the connected device proxy nodes, the task state feedback is summarized into total task state feedback and marked as an 'in-operation state'.

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

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

In actual application, the device agent node begins executing the distributed tasks, and after the task execution on each device is completed, the storage computing node marks the task as "successful state". When the storage settlement node receives the return messages of the related device agent nodes of all the change sets and the return messages are in the completed state, the change sets are marked as the completed state and stored in the database.

For example, the device node 1 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device agent node marks the status of the issue transaction of the device node 1 as "successful status", the device node 2 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device node 3 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device agent node marks the status of the issue transaction of the device node 3 as "successful status", the device node 4 executes the task in the topic a, after execution is completed, the device agent node marks the status of the issue transaction of the device node 4 as "successful status", and accordingly, the storage computing node feeds back the "successful status" of the issue transaction so that the storage computing node feeds back the total task status and marks the status as "successful status".

In one implementation, the modifying the status of the issuing transaction according to the task distribution result includes:

In practical application, if the execution fails, the task is marked as failed, and the task is added in a failed task list of the device. And when the task execution state is refreshed, the equipment proxy node judges whether an error occurs for the first time according to the completion condition of the task, and whether the condition of feeding back the task last time is longer than the cooling time.

For example, the device node 1 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device agent node marks the status of the issue transaction of the device node 1 as "successful status", the device node 2 executes the task in the topic a, after execution is failed, the device agent node feeds back the message to the device agent node a, the device node 3 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device agent node marks the status of the issue transaction of the device node 3 as "successful status", the device agent node 4 executes the task in the topic a, after execution is completed, the device agent node marks the status of the issue transaction of the device node 4 as "successful status", and accordingly, feeds back the "successful status" of the issue transaction to the storage computing node, so that the storage computing node feeds back the status of the total task as "error status in operation". The "task failure in issue topic a to device node 2" is added to the failed task list.

In one implementation, the method further includes:

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

In practical application, if the task distribution result is failure, judging whether the failure exceeds the configured retry delay time, if so, triggering a retry mechanism, and retrying the task distribution.

For example, the device node 2 executes the task in the topic a, and after the execution fails, feeds back a message to the device proxy node a, the device proxy 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 in the topic a for 3 ms, 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, the subscription of each topic is recalculated, and the subscription is distributed to the corresponding attributive equipment agent, and the retry number of the issuing task is increased by one.

For example, the device proxy node finds all devices focusing on the topic a according to the 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 and if so, create a resend task.

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

In another implementation, it is possible that the error has been resolved before the retry mechanism, then there is no corresponding task in the failed task list, and if there is no, the task is ignored if the device has retransmitted successfully.

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

Further, the retransmitted result is summarized and fed back to the task distributing node, if the result is successful, the token state is set to be a successful state, otherwise, the token state is still a failed state, and if the retry times exceed the retry threshold, the result is output to the alarm system.

For example, if the failed task list includes "the task in the issue topic a is failed to the device node 2", the task in the issue topic a is issued to the device node 2, that is, a retransmission transaction is created, the status of the issue transaction is set to be "analysis status", and when the status of the issue transaction fed back by the device node 2 is "success status", the result of retransmission is fed back to the task distribution node in summary, that is, the device proxy node marks the status of the issue transaction of the device node 1 as "success status", the device proxy node marks the status of the issue transaction of the device node 2 as "success status", the device proxy node marks the status of the issue transaction of the device node 3 as "success status", the device proxy node marks the status of the issue transaction of the device node 4 as "success status", the device node 1, the device node 2, the device node 3, and the status of the issue transaction of the device node 4 are fed back to the task distribution node, and the token status is set to be "success status".

If the state of the issuing transaction fed back by the equipment node 2 is still in a 'failure state', the retry number of the issuing task is increased by one, and if the threshold value of the retry number is three, the retry number is output to the alarm system when the retry number reaches three, so that the problem is manually solved.

In one implementation, the method further includes:

and forwarding the registration request to a target device proxy node.

Where a geographic attribute may be understood as a geographic location, e.g., a land.

In practical application, as described in the foregoing embodiment, under the condition that other conditions are the same, the closer the distance between the geographic location of the device proxy node and the geographic location of the device node is, the smaller the communication delay is, the device may select a similar device proxy node to reduce the communication delay and increase the stability.

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

In one implementation, the method further includes:

And forwarding the registration request to a target device proxy node.

Among other things, the task set attribute may be understood as a subscribed topic, e.g., the subscribed topic includes topic A and topic B.

In practical applications, as described in the foregoing embodiments, the device proxy nodes may be further allocated according to the types of topics, and dividing the device proxy nodes according to different topics may reduce the computation pressure of the device proxy nodes.

For example, the device proxy node includes a device proxy node a and a device proxy node B, the topic preparation subscribed by the device proxy node a includes a topic a and a topic B, the topic preparation subscribed by the device proxy node B includes a topic C and a topic D, the device node needs to subscribe to the topic a, and in the case that the device node sends a registration request to the device proxy node B, the device proxy node B forwards the registration request to the device proxy node a, and the device proxy node a serves as a target device proxy node and establishes the second subscription relationship with the target device proxy node a.

The embodiment of the specification provides a data transmission method, which comprises the following steps: according to the second subscription relation with the equipment node, a first subscription relation to the task distribution node is established, under the condition that a task set corresponding to the first subscription relation is obtained from the task distribution node, the tasks in the task set are issued to the corresponding equipment node according to the second subscription relation with the equipment node, and due to the fact that the equipment agent node is added, the equipment node can subscribe the tasks from the equipment agent node, and then the equipment agent node subscribes the tasks to the task distribution node, so that the communication resource usage amount of the task distribution node is reduced.

The application of the data transmission method provided in the present specification to the device proxy node is taken as an example, and the data transmission method is further described below with reference to fig. 4. Fig. 4 is a flowchart of a processing procedure of a data transmission method according to an embodiment of the present disclosure, which specifically includes the following steps.

Step 402: and the equipment proxy 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 agent 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.

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

Step 406: and the device proxy node determines corresponding devices according to the second subscription relation corresponding to the task set.

Along the above example, for the device proxy node a, if the task set is topic a, the second subscription relationship determines that the corresponding device is device node 1, device node 2, device node 3, and device node 4.

Step 408: the device agent node creates an issued transaction for 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.

Along the above example, the list of devices is: device node 1, device node 2, device node 3, device node 4, respectively, issues tasks in topic a to device node 1, device node 2, device node 3, device node 4, i.e., creates an issue transaction, and sets the status of the issue transaction to "analysis status".

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

Along the above example, the tasks in the topic a are respectively issued to the device nodes 1, 2, 3 and 4 according to the issue transaction.

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

Along the above example, the device node 1 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device agent node marks the status of the issue transaction of the device node 1 as "successful status", the device node 2 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device node 3 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, the device agent node marks the status of the issue transaction of the device node 3 as "successful status", the device node 4 executes the task in the topic a, after execution is completed, the device agent node feeds back the message to the device agent node a, and the device agent node marks the status of the issue transaction of the device node 4 as "successful status".

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

Along with the above example, the "successful state" of the issuing transaction is fed back to the storage computing node, so that the storage computing node marks the total task state feedback as "successful state".

According to the embodiment of the specification, the equipment proxy node is added, so that the equipment node can subscribe the task from the equipment proxy node, and then subscribe the task from the task distribution node through the equipment proxy node, so that the communication resource usage amount of the task distribution node is reduced.

The present specification also provides a data transmission system including:

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

In one implementation, the software defined network node is configured to initiate a registration request to a software defined network proxy node, and establish the second subscription relationship with the device proxy upon receiving a complete registration message sent by the software defined network proxy node.

In one implementation, 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 the 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 in a case where there are a plurality of software defined network proxy nodes, and determine a target software defined network proxy node according to the regional attribute, and

And initiating a registration request to the target software defined network proxy node, and establishing the second subscription relationship with the target equipment proxy under the condition that a registration completion message sent by the target software defined network proxy node is received.

In one implementation, the software defined network node is configured to determine a task set attribute of each software defined network proxy node in a case that the software defined network proxy nodes are plural, and determine a target software defined network proxy node according to the task set attribute, and

In one implementation manner, under the condition that data of a target task set is changed, 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 send the target task set to the target software defined network proxy node;

The software defined network proxy node is configured to determine a target software defined network node corresponding to the target task set according to the second subscription relationship under the condition that the target task set issued by the software defined network task distribution node is received, and send the target task to the target software defined network node.

In one implementation, the software-defined network node is configured to 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 response to 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 relation;

and under the condition that the first subscription relation corresponding to the task set is not established, establishing the first subscription relation for 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 an issuing transaction aiming at the task set, marking the state of the issuing transaction as an analysis state, and feeding back the state of the issuing 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 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 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 the regional 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 a task set attribute carried by the registration request;

The embodiment of the present specification provides a data transmission system including: the software defined network task distribution node is configured to issue a task set corresponding to the first subscription relation to the software defined network proxy node according to the first subscription relation with the software defined network proxy node; the software defined network proxy node is configured to establish a first subscription relation to the software defined network task distribution node according to a second subscription relation 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 relation with the software defined network node under the condition that a task set corresponding to the first subscription relation is obtained from the software defined network task distribution node; and the software defined network node is configured to acquire tasks issued by the software defined network proxy node according to the second subscription relation with the software defined network proxy node. Because the equipment proxy node is added, the equipment node can subscribe the task from the equipment proxy node, and then subscribe the task from the task distribution node through the equipment proxy node, so that the communication resource usage amount of the task distribution node is reduced.

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

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

and the distribution module 504 is configured to, when obtaining the task set corresponding to the first subscription relationship from the task distribution node, issue the task in the task set to the corresponding device node according to the second subscription relationship with the device node.

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

determining a task set according to the second subscription relation;

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 resending transaction for the device whose task was issued failed, if the task is in the failed task list

The embodiment of the present specification provides a data transmission apparatus, wherein the data transmission apparatus includes: the creation module is configured to create 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 distribute the tasks in the task set to the corresponding equipment nodes according to the second subscription relation with the equipment nodes under the condition that the task set corresponding to the first subscription relation is obtained from the task distribution nodes. Because the equipment proxy node is added, the equipment node can subscribe the task from the equipment proxy node, and then subscribe the task from the task distribution node through the equipment proxy node, so that the communication resource usage amount of the task distribution node is reduced.

The above is a schematic scheme of a data transmission device of the present embodiment. It should be noted that, the technical solution of the data transmission device and the technical solution of the data transmission method belong to the same conception, and details of the technical solution of the data transmission device, which are not described in detail, 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 computing device 600 include, but are not limited to, memory 610 and processor 620. The processor 620 is coupled to the memory 610 via a bus 630 and a database 650 is used to hold 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. The 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 shown in FIG. 6 is for exemplary purposes only and is not intended to limit 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., smart phone), 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.

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

The foregoing is a schematic illustration of a computing device of this 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 of the technical solution of the computing device, which are not described in detail, can be referred to the description of the technical solution of the data transmission method.

An embodiment of the present disclosure also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the data transmission method described above.

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

An embodiment of the present disclosure also provides a computer program, where the computer program, when executed in a computer, causes the computer to perform the steps of the data transmission method described above.

The above is an exemplary version 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 conception, and details of the technical solution of the computer program, which are not described in detail, can be referred to the description of the technical solution of the data transmission method.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following 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 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 are also possible or may be advantageous.

The computer instructions include computer program code that may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the embodiments are not limited by the order of actions described, as some steps may be performed in other order or simultaneously according to the embodiments of the present disclosure. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all required for the embodiments described in the specification.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are merely used to help clarify the present specification. Alternative embodiments are not intended to be exhaustive or to limit the invention to the precise form disclosed. Obviously, many modifications and variations are possible in light of the teaching of the embodiments. 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 invention. This specification is to be limited only by the claims and the full scope and equivalents thereof.

Claims

1. A data transmission system, comprising:

the task distribution node is configured to issue a task set corresponding to a first subscription relation to the equipment proxy node according to the first subscription relation with the equipment proxy node, wherein the task set is obtained by reorganizing a received original change set;

the device proxy 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 tasks in the task set to the corresponding device node according to the second subscription relation with the device node under the condition that a task set corresponding to the first subscription relation is obtained from the task distribution node, wherein the second subscription relation is a bidirectional connection relation between the device proxy node and the device node;

2. The system of claim 1, further comprising:

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

3. The system of claim 1, further comprising:

the device 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 the first subscription relationship corresponding to the task set.

4. The system of claim 1, further comprising:

the device node is configured to determine a regional attribute of each device agent node in the case that a plurality of device agent nodes are provided, and determine a target device agent node according to the regional attribute, and

5. The system of claim 1, further comprising:

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

6. The system of claim 1, further comprising:

under the condition that the data of the target task set is changed, the task distribution node is configured to determine a target equipment proxy node corresponding to the target task set according to the first subscription relation, and send the target task set to the target equipment proxy node;

7. The system of claim 1, further comprising:

The device node is configured to respond to the task set modification instruction and update the second subscription relation with the device proxy node according to the target task set carried in the task set modification instruction.

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

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

determining a task set according to the second subscription relation;

10. The method of claim 8, the issuing the task in the task set to the corresponding device node, comprising:

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

11. The method of claim 10, according to issuing the tasks in the set of tasks to the corresponding device, comprising:

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 status of the issued transaction according to the task distribution result, comprising:

14. The method of claim 12, the modifying the status 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, the issuing the task in the task set to the corresponding device according to the failed task list, comprising:

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

17. The method of claim 8, further comprising:

and forwarding the registration request to a target device proxy node.

18. The method of claim 8, further comprising:

and forwarding the registration request to a target device proxy node.

19. A data transmission system, comprising:

the system comprises a software defined network task distribution node, a software defined network proxy node and a software defined network proxy node, wherein the software defined network task distribution node is configured to distribute a task set corresponding to a first subscription relation to the software defined network proxy node according to the first subscription relation, and the task set is obtained by reorganizing a received original change set;

a software defined network proxy node configured to establish a first subscription relation to the software defined network task distribution node according to a second subscription relation with the software defined network node, and issue a task in the task set to a corresponding software defined network node according to the second subscription relation with the software defined network node when a task set corresponding to the first subscription relation is obtained from the software defined network task distribution node, wherein the second subscription relation is a bidirectional connection relation between the software defined network proxy node and the software defined network node;

20. A computing device, comprising:

a memory and a processor;

the memory is configured to store computer executable instructions, the processor being configured to execute the computer executable instructions, which when executed by the processor, implement 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.