WO2023186154A1 - Système et procédé de transmission de données - Google Patents

Système et procédé de transmission de données Download PDF

Info

Publication number
WO2023186154A1
WO2023186154A1 PCT/CN2023/085769 CN2023085769W WO2023186154A1 WO 2023186154 A1 WO2023186154 A1 WO 2023186154A1 CN 2023085769 W CN2023085769 W CN 2023085769W WO 2023186154 A1 WO2023186154 A1 WO 2023186154A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
task
subscription relationship
status
task set
Prior art date
Application number
PCT/CN2023/085769
Other languages
English (en)
Chinese (zh)
Inventor
石宜平
高磊
方崇荣
吕彪
祝顺民
蒋江伟
程鹏
陈积明
Original Assignee
浙江大学
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 浙江大学 filed Critical 浙江大学
Publication of WO2023186154A1 publication Critical patent/WO2023186154A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services

Definitions

  • the embodiments of this specification relate to the field of data processing technology, and in particular, to a data transmission system.
  • the functions of task distribution and error recovery are essential in a system composed of large-scale terminals and servers. In this type of system, it is usually necessary to distribute tasks to different terminals for execution at a high frequency and complete the feedback of the results. Once an error occurs on the terminal, the task needs to be retried in a timely manner.
  • a task belongs to a topic, and the terminal obtains the task issued by the topic in the form of a change set by subscribing to the topic.
  • Task distribution uses the subscription relationship between the device and the topic to deliver the dispatched task to the target terminal in a timely manner, confirm the implementation of the task, and obtain feedback; when the task is issued for execution, it may be due to errors in the terminal device or the terminal device is offline.
  • massive terminals mean massive subscription relationships. For example, if a topic in the cloud network needs to distribute tasks to a terminal, then It will notify all devices that subscribe to it. This massive subscription connection relationship and notification will occupy a lot of unnecessary storage and computing resources. In systems with large-scale terminal scenarios, such as cloud networks, computing and storage resources are limited. If task distribution and error recovery functions occupy too many resources, network performance will be reduced.
  • embodiments of this specification provide two data transmission systems.
  • One or more embodiments of this specification simultaneously relate to a data transmission method, a data device, a computing device, a computer-readable storage medium, and a computer program to solve technical deficiencies existing in the prior art.
  • a data transmission system including:
  • the task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the device agent node according to the first subscription relationship with the device agent node;
  • the device agent node is configured to establish a first subscription relationship to the task distribution node according to the second subscription relationship with the device node, and obtain the task set corresponding to the first subscription relationship from the task distribution node. In this case, deliver the tasks in the task set to the corresponding device node according to the second subscription relationship with the device node;
  • the device node is configured to obtain the task issued by the device agent node according to the second subscription relationship with the device agent node.
  • a data transmission method including:
  • the tasks in the task set are distributed to the corresponding device node according to the second subscription relationship with the device node.
  • a data transmission system including:
  • the software-defined network task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the software-defined network agent node according to the first subscription relationship with the software-defined network agent node;
  • the software-defined network proxy node is configured to establish a first subscription relationship to the software-defined network task distribution node according to the second subscription relationship with the software-defined network node, and obtain the software-defined network task distribution node from the software-defined network task distribution node. In the case of a task set corresponding to the first subscription relationship, deliver the tasks in the task set to the corresponding software-defined network node according to the second subscription relationship with the software-defined network node;
  • the software-defined network node is configured to obtain the task issued by the software-defined network agent node according to the second subscription relationship with the software-defined network agent node.
  • a data transmission device including:
  • a creation module configured to establish a first subscription relationship with the task distribution node based on the second subscription relationship with the device node;
  • a distribution module configured to, when obtaining a task set corresponding to the first subscription relationship from the task distribution node, distribute the tasks in the task set to the device node according to the second subscription relationship with the device node. The corresponding device node.
  • a computing device including:
  • the memory is used to store computer-executable instructions
  • the processor is used to execute the computer-executable instructions.
  • the steps of the above data transmission method are implemented.
  • a computer-readable storage medium which stores computer-executable instructions. When the instructions are executed by a processor, the steps of the above data transmission method are implemented.
  • a computer program is provided, wherein when the computer program is executed in a computer, the computer is caused to perform the steps of the above data transmission method.
  • Embodiments of this specification provide a data transmission system and method, wherein the data transmission system includes: a task distribution node configured to deliver a first A task set corresponding to the subscription relationship; the device agent node is configured to establish a first subscription relationship to the task distribution node based on the second subscription relationship with the device node, and obtain the task set corresponding to the first subscription relationship from the task distribution node.
  • the tasks in the task set are delivered to the corresponding device nodes according to the second subscription relationship with the device node; the device node is configured to obtain the tasks issued by the device agent node according to the second subscription relationship with the device agent node.
  • Task Due to the addition of the device agent node, the device node can subscribe to tasks from the device agent node and then subscribe to the task distribution node through the device agent node, which reduces the communication resource usage of the task distribution node.
  • Figure 1 shows an architectural diagram of a data transmission system provided according to an embodiment of this specification
  • Figure 2 is a flow chart of a data transmission method provided by an embodiment of this specification
  • Figure 3 shows a schematic diagram of a data transmission method provided according to an embodiment of this specification
  • Figure 4 is a processing flow chart of a data transmission method provided by an embodiment of this specification.
  • Figure 5 is a schematic structural diagram of a data transmission device provided by an embodiment of this specification.
  • Figure 6 is a structural block diagram of a computing device provided by an embodiment of this specification.
  • first, second, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • the first may also be called the second, and similarly, the second may also be called the first.
  • the word "if” as used herein may be interpreted as "when” or “when” or “in response to determining.”
  • Token an asynchronous task distribution is called a token.
  • a changes set contains a change set ID, distribution status and a set of tasks.
  • Subscription Subscription, the subscription relationship includes topics and subscribers.
  • Topic a concept defined to implement the ability to push different content to different devices, a task belongs to For a topic, the device can obtain all notifications under the topic by subscribing to the topic.
  • Task Contains subject, object identification, timestamp, task data, etc.
  • SDN Software Defined Network
  • This specification also relates to a data transmission method, a data transmission device, a computing device, and a computer-readable storage medium. In the following embodiments, one by one Explain in detail.
  • Figure 1 shows an architectural diagram of a data transmission system provided according to an embodiment of this specification.
  • the data transmission system includes:
  • the task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the device agent node according to the first subscription relationship with the device agent node;
  • the device agent node is configured to establish a first subscription relationship to the task distribution node according to the second subscription relationship with the device node, in the case of obtaining a task set corresponding to the first subscription relationship from the task distribution node. Next, deliver the tasks in the task set to the corresponding device node according to the second subscription relationship with the device node;
  • the device node is configured to obtain the task issued by the device agent node according to the second subscription relationship with the device agent node.
  • the task distribution node can be understood as a node that delivers tasks, for example, a storage computing node;
  • the device agent can be understood as an intermediate node between the task distribution node and the device node, which can obtain tasks from the task distribution node and download them to the device node.
  • Send tasks; device nodes can be understood as nodes that apply tasks; task sets can be understood as topics.
  • the data transmission system consists of three parts: storage computing node, device agent node, and device node.
  • the device agent node subscribes to the storage computing node as the first-level subscription, and the device node registers and subscribes to the device agent node as the first-level subscription.
  • Secondary subscription the specific implementation is as follows:
  • the device agent node is a storage computing node, and the storage computing node is responsible for task distribution and task status feedback.
  • the storage computing node is responsible for distributing tasks to the device agent nodes.
  • the storage computing node receives the tasks expressed in the form of a change set, stores the original change set in the data storage, and re-creates the tasks based on the topics subscribed by different device agent nodes. Organize the change set and deliver the reorganized change set to the corresponding device agent.
  • the storage computing node is also responsible for receiving the task status obtained from the device agent and summarizing it into the total task status.
  • the device agent node subscribes to the topic and is responsible for distributing tasks to corresponding devices and obtaining task status feedback from the devices.
  • a device agent node obtains the topics that the device it represents needs to subscribe to, and the agent subscribes to these topics. After receiving the change set from the storage computing node, the device agent node creates a delivery task to the terminal device.
  • the device node registers with the device agent node, processes the tasks issued by the device agent node, and feeds back the task status. Give the device agent node.
  • the device node is configured to initiate a registration request to a device agent node, and upon receiving a registration completion message sent by the device agent node, establish the third connection with the device agent.
  • device node 1 sends a registration request to device agent node A, and device agent node A returns a registration completion message to device node 1. Then device agent node A completes the registration and creates a two-way connection with device node 1 for subsequent implementation. notifications received.
  • the device node is configured to determine the regional attributes of each device agent node when there are multiple device agent nodes, and determine the target device agent node according to the regional attributes, as well as
  • the geographical attribute of the device agent node can be understood as the geographical location of the device agent node.
  • the device agent node is located in location A.
  • the distance between the geographical location of the device agent node and the geographical location of the device node has a great impact on the communication delay.
  • the geographical location of the device agent node is different from the geographical location of the device node. The closer the distance between locations, the smaller the communication delay. Then, the device can select a nearby device proxy node to reduce communication delay and increase stability.
  • the device agent node includes device agent node A and device agent node B. If the distance between device agent node A and the current device node is relatively close, then device agent node A is selected as the target device agent node, and the device agent node A is established with the target device agent node. Second subscription relationship.
  • the device node is configured to determine the task set attributes of each device agent node when there are multiple device agent nodes, and determine the target device agent according to the task set attributes. node, and
  • the task set attribute of the device agent node can be understood as the topic subscribed by the device agent node.
  • the topics subscribed by the device agent node include topic A and topic B.
  • device agent nodes can also be allocated according to topic types. Dividing device agent nodes according to different topics can reduce the computing pressure of device agent nodes.
  • the device agent node includes device agent node A and device agent node B.
  • the topics subscribed by device agent node A include topic A and topic B.
  • the topics subscribed by device agent node B include topic C and topic D.
  • the device node needs to subscribe Topic A, select device agent node A as the target device agent node, and communicate with the target The device agent node establishes the second subscription relationship.
  • the task distribution node when the data of the target task set changes, is configured to determine the target device agent node corresponding to the target task set according to the first subscription relationship, and send the The target device agent node delivers the target task set;
  • the device agent node is configured to, upon receiving the target task set issued by the task distribution node, determine the target device node corresponding to the target task set according to the second subscription relationship, and send the target device node to the target device node. Send said target task.
  • the task distribution node when the task distribution node receives the data changes in the task, it needs to send the data changes to the device agent node, and then the device agent node sends it to the relevant device nodes.
  • the device agent node that subscribes to topic A is determined, and the added piece of data in topic A is sent to the corresponding device agent node in the form of a change set.
  • the device agent node After the change set is not received, the relevant device nodes that subscribe to topic A will be determined and the change set will be delivered to the relevant device nodes.
  • the device node is configured to respond to a task set modification instruction and update the second subscription relationship with the device agent node according to the target task set carried in the task set modification instruction.
  • the device node may need to add a subscription to a new topic or delete a subscription to a topic, and then delete the task in the subscription relationship. For example, if the device node needs to add a subscription to topic B, then add the subscription relationship of topic B to the second subscription relationship between the device node and the device agent node.
  • the device agent node is configured as:
  • a task set is determined according to the second subscription relationship, and if the first subscription relationship corresponding to the task set is not established, a first subscription relationship of the task set is established.
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • the device agent node is also configured to:
  • Embodiments of this specification provide a data transmission system including: a task distribution node configured to deliver a task set corresponding to the first subscription relationship to the device agent node according to the first subscription relationship with the device agent node; the device agent node is Configured to establish a first subscription relationship to the task distribution node based on the second subscription relationship with the device node, and in the case of obtaining a task set corresponding to the first subscription relationship from the task distribution node, based on the second subscription relationship with the device node , delivers the tasks in the task set to the corresponding device node; the device node is configured to obtain the tasks issued by the device agent node according to the second subscription relationship with the device agent node. Due to the addition of equipment The device agent node enables the device node to subscribe to tasks from the device agent node, and then subscribes to the task distribution node through the device agent node, thereby reducing the communication resource usage of the task distribution node.
  • Figure 2 shows a flow chart of a data transmission method provided according to an embodiment of this specification, which specifically includes the following steps.
  • Step 202 Establish a first subscription relationship with the task distribution node based on the second subscription relationship with the device node.
  • the device node needs to register with the device agent node to establish a second subscription relationship, and then based on the topic to which the device node subscribes, the device agent node then establishes a first subscription relationship with the task distribution node.
  • establishing a first subscription relationship to the task distribution node based on the second subscription relationship with the device node includes:
  • Figure 3 shows a schematic diagram illustrating a data transmission method provided according to an embodiment of this specification, which includes a storage computing node, a device agent node A and a device agent node B, and a device node 1.
  • Device node 2, device node 3, device node 4, and device node 5 determine topic A based on the second subscription relationship between device node 1 and device agent node A, and determine whether there is a first connection between topic A and the storage computing node. Subscription relationship. If the first subscription relationship including topic A and storage computing node already exists, the subscription processing will not be performed. If it does not exist, a subscription relationship between topic A and device agent node A will be created, and the subscription relationship will be created on device agent node A. Store new subscription relationships in memory.
  • Step 204 When the task set corresponding to the first subscription relationship is obtained from the task distribution node, deliver the tasks in the task set to the corresponding device according to the second subscription relationship with the device node. node.
  • the device agent node obtains the subscribed related task set and sends the tasks in the subscribed related task set to the locally registered device node.
  • issuing the tasks in the task set to the corresponding device nodes includes:
  • the device agent After receiving the change set, the device agent finds all the devices that follow the topic based on the topic and obtains the device list.
  • the second subscription relationship determines that the corresponding devices are device node 1, device node 2, device node 3, and device node 4. To the device node 1. Device node 2, device node 3, and device node 4 deliver the task in topic A.
  • issuing the tasks in the task set to the corresponding device includes:
  • each asynchronous task issuance is called a token, and all token statuses are queried in chronological order.
  • the token has six states, namely "initialization state”, “analysis state”, “running state”, “successful state”, “running error state”, and “failure state”.
  • Tokens store two pieces of information, token content and token status.
  • Token content stores change sets, including multiple topics and task lists contained in each topic; token status stores progress updates, including status, start time, number of affected devices, number of affected tasks, number of completed devices, and number of completed tasks and number of errors.
  • the "Initialization State” state indicates that the token is established for the first time. At this time, the token content and token status are stored in the external memory.
  • the "Analysis State” state indicates It is in the analysis state.
  • the device agent is still calculating the device list associated with the change set and creating a delivery task;
  • “Running state” indicates the execution state, and the device agent processes the tasks delivered to the device;
  • “Successful state” indicates execution Completed;
  • “Running Error Status” means that the task has been issued, but the execution has not yet been completed;
  • “Failure Status” means that the execution has been completed but an error occurred.
  • the device agent feeds back the task status to the storage computing node.
  • the feedback information obtained by the storage computing node is summarized and calculated, and the execution status of the change set is stored in the database for future reference.
  • the feedback information includes the number of affected devices, the number of affected tasks, the number of completed devices, the number of completed tasks and the number of errors.
  • the device list is: device node 1, device node 2, device node 3, and device node 4.
  • the tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively, that is, create Deliver the transaction, set the status of the delivered transaction to "Analysis Status", and deliver the tasks in topic A to device node 1, device node 2, device node 3, and device node 4 respectively according to the delivered transaction.
  • the data transmission method in the embodiment of this specification also includes:
  • the device agent node feeds back the task status to the storage computing node.
  • the storage computing node receives the task status feedback from all connected device agent nodes, it feeds back the task status. Summarized into total task status feedback, marked as "Running Status".
  • tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively based on the delivered transactions.
  • these delivered transactions are marked as “running status” and Feedback the status of the transaction issued to the storage computing node, that is, the status of the transaction issued by device node 1 is “running status”, the status of the transaction issued by device node 2 is “running status”, and the status of the transaction issued by device node 3 is “running status”.
  • the status of the transaction issued is "running status”
  • the status of the transaction issued by device node 4 is “running status"
  • modifying the status of the issued transaction according to the task distribution result includes:
  • the device agent node starts to execute the distribution task.
  • the storage computing node marks the task as "successful status”.
  • the storage settlement node receives return messages from the relevant device agent nodes of all change sets, and the return messages are in the completed state, the change set is marked as "completed state" and stored in the database.
  • device node 1 executes the task in topic A. After the execution is completed, it feeds back a message to device agent node A.
  • the device agent node marks the status of the transaction issued by device node 1 as "successful status", and device node 2 executes the topic. After the execution of the task in A is completed, a message is fed back to the device agent node A.
  • the device agent node marks the status of the transaction issued by device node 2 as "successful status”.
  • Device node 3 executes the task in topic A. During execution After completion, the message is fed back to the device agent node A.
  • the device agent node marks the status of the transaction issued by the device node 3 as "successful status”.
  • Device section 4 executes the task in topic A. After the execution is completed, it reports to the device agent Node A feeds back the message, and the device agent node marks the status of the transaction issued by device node 4 as "success status”. Correspondingly, it feeds back the "success status" of the transaction issued to the storage computing node, so that the storage computing node will always Task status feedback, marked as "success status”.
  • modifying the status of the issued transaction according to the task distribution result includes:
  • the task is marked as failed and added to the device's failed task list.
  • the device agent node will determine whether an error occurs for the first time based on the completion of the task, and whether the time since the last feedback of the task status has exceeded the cooling time.
  • device node 1 executes the task in topic A. After the execution is completed, it feeds back a message to device agent node A.
  • the device agent node marks the status of the transaction issued by device node 1 as "successful status", and device node 2 executes the topic. After the execution of the task in A fails, a message is fed back to the device agent node A.
  • the device agent node marks the status of the transaction issued by device node 2 as "failed status”.
  • Device node 3 executes the task in topic A. During execution After completion, the message is fed back to the device agent node A.
  • the device agent node marks the status of the transaction issued by the device node 3 as "successful status”.
  • Device section 4 executes the task in topic A.
  • the device agent Node A After the execution is completed, it reports to the device agent Node A feeds back the message, and the device agent node marks the status of the transaction issued by device node 4 as "success status”. Correspondingly, it feeds back the "success status" of the transaction issued to the storage computing node, so that the storage computing node will always Task status feedback, marked as "Running Error Status”. Add "Add to failed tasks list" Device node 2 failed to deliver the task in topic A.”
  • it also includes:
  • the retry mechanism is triggered and the task is retried.
  • device node 2 executes the task in topic A. After the execution fails, it feeds back a message to device agent node A.
  • the device agent node marks the status of the transaction issued by device node 2 as "failed status" and executes it on device node 2.
  • the retry mechanism is triggered 3 milliseconds after the task in topic A fails.
  • delivering the tasks in the task set to the corresponding device according to the failed task list includes:
  • the change set is read from the storage, the subscription of each topic is recalculated, and distributed to the corresponding device agent, and the number of retries of the delivery task is increased by one.
  • the device agent node finds all the devices paying attention to the topic based on topic A, and obtains the device list.
  • the device list is: device node 1, device node 2, device node 3, device node 4, traverses the device list, and checks the failed task list. Whether the task exists, if so, create a resend task.
  • the error has been resolved before the retry mechanism, then the corresponding task does not exist in the failed task list. If it does not exist, it means that the device has successfully retransmitted, and the task is ignored. .
  • the retransmission results are summarized and fed back to the task distribution node. If successful, the token status is set to "success status", otherwise the token status is still "failure status”. If the number of retries exceeds the retry threshold, output to the alarm system.
  • the number of retries of the delivered task will be increased by one. If the threshold of the number of retries is three, then when the number of retries reaches three, then Output to the alarm system so that the problem can be solved manually.
  • it also includes:
  • the regional attribute can be understood as the geographical location, for example, place A.
  • the device can choose Close device agent nodes to reduce communication delays and increase stability.
  • the device agent node includes device agent node A and device agent node B.
  • the distance between device agent node A and the current device node is relatively close.
  • device agent node B When the device node sends a registration request to device agent node B, device agent node B will register. The request is forwarded to device agent node A, which serves as the target device agent node and establishes the second subscription relationship with the target device agent node A.
  • it also includes:
  • the task set attribute can be understood as the subscribed topic.
  • the subscribed topics include topic A and topic B.
  • device agent nodes can also be allocated according to topic types, and dividing device agent nodes according to different topics can reduce the computing pressure of the device agent nodes.
  • the device agent node includes device agent node A and device agent node B.
  • the topics subscribed by device agent node A include topic A and topic B.
  • the topics subscribed by device agent node B include topic C and topic D.
  • the device node needs to subscribe Topic A, when the device node sends a registration request to the device agent node B, the device agent node B forwards the registration request to the device agent node A.
  • the device agent node A serves as the target device agent node and establishes with the target device agent node A. The second subscription relationship.
  • Embodiments of this specification provide a data transmission method, which includes: establishing a first subscription relationship to a task distribution node based on a second subscription relationship with a device node, and obtaining a task set corresponding to the first subscription relationship from the task distribution node. Next, according to the second subscription relationship with the device node, the tasks in the task set are delivered to the corresponding device node. Due to the addition of the device agent node, the device node can subscribe to the task from the device agent node, and then submit the task to the task through the device agent node. The distribution node subscribes to the task, which reduces the communication resource usage of the task distribution node.
  • FIG. 4 shows a process flow chart of a data transmission method provided by an embodiment of this specification, which specifically includes the following steps.
  • Step 402 The device agent node determines a task set according to the second subscription relationship.
  • topic A is determined according to the second subscription relationship between device node 1 and device agent node A.
  • Step 404 When the device agent node has not established a first subscription relationship corresponding to the task set, establish a first subscription relationship to the task distribution node according to the task set.
  • Step 406 The device agent node determines the corresponding device according to the second subscription relationship corresponding to the task set.
  • the second subscription relationship determines that the corresponding devices are device node 1, device node 2, device node 3, and device node 4.
  • Step 408 The device agent node creates a issued transaction for the task set, marks the status of the issued transaction as an analysis status, and feeds back the status of the issued transaction to the task distribution node.
  • the device list is: device node 1, device node 2, device node 3, and device node 4.
  • the tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively, that is, , create a issued transaction, and set the status of the issued transaction to "Analysis Status".
  • Step 410 The device agent node delivers the tasks in the task set to the corresponding device according to the delivery transaction.
  • the tasks in topic A are delivered to device node 1, device node 2, device node 3, and device node 4 respectively according to the delivery transaction.
  • Step 412 The device agent node receives the task distribution result returned by each device node.
  • device node 1 executes the task in topic A. After the execution is completed, it feeds back a message to device agent node A.
  • the device agent node marks the status of the transaction issued by device node 1 as "successful status", and device node 2 Execute the task in topic A. After the execution is completed, a message is fed back to the device agent node A.
  • the device agent node marks the status of the transaction issued by device node 2 as "successful status”.
  • Device node 3 executes the task in topic A. After the task is executed, a message is fed back to the device agent node A.
  • the device agent node marks the status of the transaction issued by the device node 3 as "successful status”.
  • Device section 4 executes the task in topic A. After the execution is completed, Finally, the message is fed back to the device agent node A, and the device agent node marks the status of the transaction issued by the device node 4 as "successful status”.
  • Step 414 When each task distribution result is successful, the device agent node marks the status of the issued transaction as a successful status, and feeds back the status of the issued transaction to the task distribution node.
  • the "success status" of the transaction is fed back to the storage computing node, so that the storage computing node feeds back the total task status and marks it as "success status”.
  • the device agent node is added, so that the device node can subscribe to tasks from the device agent node, and then subscribe to the task to the task distribution node through the device agent node, thereby reducing the communication resource usage of the task distribution node.
  • This manual also provides a data transmission system, including:
  • the software-defined network task distribution node is configured to deliver a task set corresponding to the first subscription relationship to the software-defined network agent node according to the first subscription relationship with the software-defined network agent node;
  • the software-defined network proxy node is configured to establish a first subscription relationship to the software-defined network task distribution node according to the second subscription relationship with the software-defined network node, and obtain the software-defined network task distribution node from the software-defined network task distribution node. In the case of a task set corresponding to the first subscription relationship, deliver the tasks in the task set to the corresponding software-defined network node according to the second subscription relationship with the software-defined network node;
  • the software-defined network node is configured to obtain the task issued by the software-defined network agent node according to the second subscription relationship with the software-defined network agent node.
  • the software-defined network agent node can be a gateway, private cloud and other devices.
  • the software-defined network node is configured to initiate a registration request to the software-defined network proxy node, and upon receiving the registration completion message sent by the software-defined network proxy node, communicate with the software-defined network proxy node.
  • the device agent establishes the second subscription relationship.
  • the software-defined network agent node is configured to determine a task set according to the second subscription relationship, and establish all the task sets when the first subscription relationship corresponding to the task set is not established.
  • the first subscription relationship of the above task set is not established.
  • the software-defined network node is configured to determine the regional attributes of each software-defined network agent node when there are multiple software-defined network agent nodes, and determine the regional attributes of each software-defined network agent node according to the regional properties identify the target software-defined network agent node, and
  • the software-defined network node is configured as a software-defined network agent When there are multiple nodes, determine the task set attributes of each software-defined network agent node, and determine the target software-defined network agent node according to the task set attributes, and
  • the software-defined network task distribution node when the data of the target task set changes, is configured to determine the target software definition corresponding to the target task set according to the first subscription relationship. a network agent node, and delivers the target task set to the target software-defined network agent node;
  • the software-defined network proxy node is configured to determine the target software-defined network node corresponding to the target task set according to the second subscription relationship when receiving the target task set issued by the software-defined network task distribution node, and sends the target task to the target software-defined network node.
  • the software-defined network node is configured to respond to a task set modification instruction and update the communication with the software-defined network agent node according to the target task set carried in the task set modification instruction. Second subscription relationship.
  • the software-defined network proxy node is configured as:
  • a task set is determined according to the second subscription relationship, and if the first subscription relationship corresponding to the task set is not established, a first subscription relationship of the task set is established.
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • the status of the issued transaction is marked as successful, and feeding back the status of the issued transaction to the software-defined network task distribution node.
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • the software-defined network proxy node is also configured to:
  • Embodiments of this specification provide a data transmission system including: a software-defined network task distribution node configured to deliver tasks corresponding to the first subscription relationship to the software-defined network agent node according to the first subscription relationship with the software-defined network agent node. set; the software-defined network proxy node is configured to establish a first subscription relationship to the software-defined network task distribution node based on the second subscription relationship with the software-defined network node, and obtain the first subscription relationship from the software-defined network task distribution node In the case of the corresponding task set, the tasks in the task set are delivered to the corresponding software-defined network node according to the second subscription relationship with the software-defined network node; the software-defined network node is configured to be based on the software-defined network proxy node.
  • the second subscription relationship is to obtain the tasks issued by the software-defined network agent node. Due to the addition of the device agent node, the device node can subscribe to tasks from the device agent node and then subscribe to the task distribution node through the device agent node, which reduces the communication resource usage of the task distribution node.
  • Figure 5 shows a schematic structural diagram of a data transmission device provided by an embodiment of this specification. As shown in Figure 5, the device includes:
  • the creation module 502 is configured to establish a first subscription relationship to the task distribution node based on the second subscription relationship with the device node;
  • the distribution module 504 is configured to, after obtaining the task set corresponding to the first subscription relationship from the task distribution node, distribute the tasks in the task set according to the second subscription relationship with the device node. To the corresponding device node.
  • the creation module 502 is also configured to:
  • the distribution module 504 is also configured to:
  • the distribution module 504 is also configured to:
  • the distribution module 504 is also configured to:
  • the distribution module 504 is also configured to:
  • the distribution module 504 is also configured to:
  • the distribution module 504 is also configured to:
  • the distribution module 504 is also configured to:
  • Embodiments of this specification provide a data transmission device, wherein the data transmission device includes: a creation module configured to establish a first subscription relationship to a task distribution node based on a second subscription relationship with a device node; a distribution module configured to When the task set corresponding to the first subscription relationship is obtained from the task distribution node, the tasks in the task set are distributed to the corresponding device node according to the second subscription relationship with the device node. Due to the addition of the device agent node, the device node can subscribe to tasks from the device agent node and then subscribe to the task distribution node through the device agent node, which reduces the communication resource usage of the task distribution node.
  • the above is a schematic solution of a data transmission device in this embodiment. It should be noted that the technical solution of the data transmission device and the technical solution of the above-mentioned data transmission method belong to the same concept. For details that are not described in detail in the technical solution of the data transmission device, please refer to the description of the technical solution of the above-mentioned data transmission method. .
  • Figure 6 shows a structural block diagram of a computing device 600 provided according to an embodiment of this specification.
  • Components of the computing device 600 include, but are not limited to, memory 610 and processor 620 .
  • the processor 620 and the memory 610 are connected through a bus 630, and the database 650 is used to save data.
  • Computing device 600 also includes an access device 640 that enables computing device 600 to communicate via one or more networks 660 .
  • networks include the Public Switched Telephone Network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communications networks such as the Internet.
  • Access device 640 may include one or more of any type of network interface (eg, a network interface card (NIC)), wired or wireless, such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Worldwide Interconnection for Microwave Access (WLAN) Wi-MAX) interface, Ethernet interface, Universal Serial Bus (USB) interface, cellular network interface, Bluetooth interface, Near Field Communication (NFC) interface, etc.
  • NIC network interface card
  • the above-mentioned components of the computing device 600 and other components not shown in FIG. 6 may also be connected to each other, such as through a bus. It should be understood that the structural block diagram of the computing device shown in FIG. 6 is for illustrative purposes only and does not limit the scope of this description. Those skilled in the art can add or replace other components as needed.
  • Computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet computer, personal digital assistant, laptop computer, notebook computer, netbook, etc.), a mobile telephone (e.g., smartphone ), a wearable computing device (e.g., smart watch, smart glasses, etc.) or other type of mobile device, or a stationary computing device such as a desktop computer or PC.
  • a mobile computer or mobile computing device e.g., tablet computer, personal digital assistant, laptop computer, notebook computer, netbook, etc.
  • a mobile telephone e.g., smartphone
  • a wearable computing device e.g., smart watch, smart glasses, etc.
  • stationary computing device such as a desktop computer or PC.
  • Computing device 600 may also be a mobile or stationary server.
  • the processor 620 is configured to execute the following computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above data transmission method are implemented.
  • the above is a schematic solution of a computing device in this embodiment. It should be noted that the technical solution of the computing device and the technical solution of the above-mentioned data transmission method belong to the same concept. For details that are not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above data transmission method.
  • An embodiment of the present specification also provides a computer-readable storage medium that stores computer-executable instructions.
  • the computer-executable instructions are executed by a processor, the steps of the above data transmission method are implemented.
  • the above is a schematic solution of a computer-readable storage medium in this embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the above-mentioned data transmission method belong to the same concept. For details that are not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the above-mentioned data transmission method.
  • An embodiment of the present specification also provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to perform the steps of the above data transmission method.
  • the computer instructions include computer program code, which may be in the form of source code, object code, executable file or some intermediate form.
  • the computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media, etc.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • electrical carrier signals telecommunications signals
  • software distribution media etc.
  • the content contained in the computer-readable medium can be appropriately added or deleted according to the requirements of legislation and patent practice in the jurisdiction.
  • the computer-readable medium Excludes electrical carrier signals and telecommunications signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

Les modes de réalisation de la présente invention concernent un système et un procédé de transmission de données. Le système de transmission de données comprend : un noeud de distribution de tâches configuré pour émettre un ensemble de tâches correspondant à une première relation d'abonnement vers un noeud mandataire de dispositif selon la première relation d'abonnement avec le noeud mandataire de dispositif ; le noeud mandataire de dispositif étant configuré pour établir une première relation d'abonnement pour le noeud de distribution de tâches selon une seconde relation d'abonnement avec un noeud de dispositif, et, lorsque l'ensemble de tâches correspondant à la première relation d'abonnement est obtenu en provenance du noeud de distribution de tâches, pour émettre une tâche de l'ensemble de tâches vers le noeud de dispositif correspondant selon la seconde relation d'abonnement avec le noeud de dispositif ; et le noeud de dispositif étant configuré pour obtenir la tâche émise par le noeud mandataire de dispositif selon la seconde relation d'abonnement avec le noeud mandataire de dispositif. Du fait que le noeud mandataire de dispositif est ajouté, le noeud de dispositif peut s'abonner à une tâche à partir du noeud mandataire de dispositif, la tâche est souscrite auprès du noeud de distribution de tâches au moyen du noeud mandataire de dispositif, et la quantité de ressources de communication utilisées par le noeud de distribution de tâche est réduite.
PCT/CN2023/085769 2022-04-02 2023-03-31 Système et procédé de transmission de données WO2023186154A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210345992.6 2022-04-02
CN202210345992.6A CN114885020B (zh) 2022-04-02 2022-04-02 数据传输系统以及方法

Publications (1)

Publication Number Publication Date
WO2023186154A1 true WO2023186154A1 (fr) 2023-10-05

Family

ID=82669479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/085769 WO2023186154A1 (fr) 2022-04-02 2023-03-31 Système et procédé de transmission de données

Country Status (2)

Country Link
CN (1) CN114885020B (fr)
WO (1) WO2023186154A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114885020B (zh) * 2022-04-02 2024-02-13 浙江大学 数据传输系统以及方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101848236A (zh) * 2010-05-06 2010-09-29 北京邮电大学 具有分布式网络架构的实时数据分发系统及其工作方法
US20130227119A1 (en) * 2012-02-29 2013-08-29 Research In Motion Limited System and method for providing access to presence status for mobile devices
CN113162970A (zh) * 2021-01-27 2021-07-23 中央财经大学 基于发布/订阅模型的消息路由方法、装置、设备及介质
CN114885020A (zh) * 2022-04-02 2022-08-09 浙江大学 数据传输系统以及方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140101607A (ko) * 2013-02-12 2014-08-20 삼성테크윈 주식회사 데이터 배포 서비스의 데이터베이스 관리 시스템 및 방법
CN107908465B (zh) * 2017-10-19 2020-11-03 深圳索信达数据技术有限公司 大数据平台的任务调度方法
CN112769885A (zh) * 2019-11-04 2021-05-07 千寻位置网络有限公司 基于数据点订阅的代理播发方法及其装置
CN112788074B (zh) * 2019-11-07 2024-05-31 中兴通讯股份有限公司 数据发送方法、处理方法、接收方法及其设备、存储介质
CN113726896B (zh) * 2021-09-01 2022-09-27 看屋(上海)信息科技有限公司 基于商业智能房地产行业的任务分发系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101848236A (zh) * 2010-05-06 2010-09-29 北京邮电大学 具有分布式网络架构的实时数据分发系统及其工作方法
US20130227119A1 (en) * 2012-02-29 2013-08-29 Research In Motion Limited System and method for providing access to presence status for mobile devices
CN113162970A (zh) * 2021-01-27 2021-07-23 中央财经大学 基于发布/订阅模型的消息路由方法、装置、设备及介质
CN114885020A (zh) * 2022-04-02 2022-08-09 浙江大学 数据传输系统以及方法

Also Published As

Publication number Publication date
CN114885020B (zh) 2024-02-13
CN114885020A (zh) 2022-08-09

Similar Documents

Publication Publication Date Title
WO2021088641A1 (fr) Procédé de transmission de données, procédé de traitement de données, procédé et dispositif de réception de données, et support de stockage
CN111277639B (zh) 一种保持数据一致性的方法和装置
US8380820B1 (en) Sending synchronous responses to requests from frontend applications
WO2013078689A1 (fr) Procédé et dispositif pour réaliser un transfert de message dans un service de messagerie en nuage
CN114363407B (zh) 消息服务方法及装置、可读存储介质及电子设备
US20220413937A1 (en) Node management method, device and apparatus, storage medium, and system
CN102143194A (zh) 数据同步的方法、系统、中间数据节点及终止数据节点
WO2019109923A1 (fr) Procédé et système de traitement de message, support de stockage, et dispositif électronique
WO2023186154A1 (fr) Système et procédé de transmission de données
TWI716822B (zh) 事務因果序的校正方法及裝置、電子設備
WO2023143503A1 (fr) Système et procédé de planification de ressources
CN108390919B (zh) 一种用于高可靠双机热备的消息同步系统及方法
WO2023185934A1 (fr) Procédé et dispositif de traitement de données
CN111277483A (zh) 一种多端消息的同步方法、服务器及可存储介质
CN114025002A (zh) 一种基于mqtt信息传输的方法、系统及通信设备
US9043274B1 (en) Updating local database and central database
CA3065729A1 (fr) Cadre de traitement de regles administratives
CN114500651A (zh) 一种区块链数据传输方法、装置和设备及可读存储介质
CN105447000A (zh) 一种事务消息的传输方法和设备
WO2020220272A1 (fr) Procédé et système de changement d'état de ressource, terminal et support de stockage
CN117336346A (zh) 一种ippbx与pms对接状态转换方法、终端设备及介质
WO2019201111A1 (fr) Procédé, appareil et dispositif de traitement d'informations, et support de stockage lisible par ordinateur
CN109257435A (zh) 基于消息中间件的多实例多子系统应用的通信系统
CN114090687A (zh) 一种数据同步方法及装置
CN113296968B (zh) 地址列表更新方法、装置、介质及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23778518

Country of ref document: EP

Kind code of ref document: A1