CN114666332A - Data transmission method, edge box, edge cloud and data transmission system - Google Patents
Data transmission method, edge box, edge cloud and data transmission system Download PDFInfo
- Publication number
- CN114666332A CN114666332A CN202210318582.2A CN202210318582A CN114666332A CN 114666332 A CN114666332 A CN 114666332A CN 202210318582 A CN202210318582 A CN 202210318582A CN 114666332 A CN114666332 A CN 114666332A
- Authority
- CN
- China
- Prior art keywords
- edge
- task
- box
- heartbeat packet
- cloud
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
Abstract
The application provides a data transmission method, an edge box, an edge cloud and a data transmission system, wherein the data transmission method is applied to the edge box and comprises the following steps: sending a heartbeat packet to the edge cloud, wherein the heartbeat packet carries an identifier of the edge box, so that the edge cloud can determine whether a task to be executed of the edge box exists at present according to the identifier of the edge box; if a feedback heartbeat packet of the edge cloud is received and the content of the feedback heartbeat packet is not empty, a task request is generated and sent to the edge cloud so that the edge cloud can issue a corresponding task to be executed to the edge box according to the task request, and the feedback heartbeat packet is generated by the edge cloud based on the heartbeat packet of the edge box. The method and the device can avoid the situation that the edge box without the task in the edge cloud sends the task request to the edge cloud, reduce the transmission quantity of data between the edge box and the edge cloud, reduce the occupation of transmission resources, and enable the edge cloud to interact with more edge boxes simultaneously.
Description
Technical Field
The present application relates to the field of data transmission technologies, and in particular, to a data transmission method, an edge box, an edge cloud, and a data transmission system.
Background
With the maturation of the fifth Generation Mobile Communication Technology (5th Generation Mobile Communication Technology, 5G), edge computing Technology began to evolve. In edge computing, an edge cloud and an edge box are indispensable. The edge cloud is a small-scale cloud data center which is distributed at the edge side of the network and provides real-time data processing, analysis and decision. The edge box, by its very nature, is a lightweight edge computing device with Artificial Intelligence (AI) capabilities.
Generally, for an edge cloud, there are multiple edge boxes. When tasks in the edge cloud require certain edge boxes to be executed, the current main adopted method is as follows: each edge box sends a task request to the edge cloud, and the edge cloud analyzes and processes the task request sent by each edge box and responds only to the edge boxes specified by the task, so that the task can be executed in the edge boxes.
However, each edge box sends a task request to the edge cloud, and the task request carries detailed information of the task requested by the edge box and various information of the edge box itself, which increases the burden of data transmission between the edge cloud and the edge box and occupies too much transmission resources.
Disclosure of Invention
An object of the embodiment of the present application is to provide a data transmission method, an edge box, an edge cloud, and a data transmission system, so as to reduce resources occupied by data transmission between the edge cloud and the edge box.
In order to solve the above technical problem, an embodiment of the present application provides the following technical solutions:
a first aspect of the present application provides a data transmission method, which is applied to an edge box; the method comprises the following steps: sending a heartbeat packet to an edge cloud, wherein the heartbeat packet carries an identifier of the edge box, so that the edge cloud can determine whether a task to be executed of the edge box exists currently according to the identifier of the edge box; if a feedback heartbeat packet of the edge cloud is received and the content of the feedback heartbeat packet is not empty, a task request is generated and sent to the edge cloud so that the edge cloud can issue a corresponding task to be executed to the edge box according to the task request, and the feedback heartbeat packet is generated by the edge cloud based on the heartbeat packet of the edge box.
A second aspect of the present application provides a data transmission method, which is applied to an edge cloud; the method comprises the following steps: receiving a heartbeat packet sent by an edge box, wherein the heartbeat packet carries an identifier of the edge box; determining whether there is a task to be performed for the edge box based on the identification; if the feedback heartbeat packet exists, sending a feedback heartbeat packet with non-empty content to the edge box, so that the edge box generates a task request according to the feedback heartbeat packet with non-empty content, wherein the task request is used for acquiring a target task to be executed from the edge cloud.
A third aspect of the present application provides an edge box comprising: the sending module is used for sending a heartbeat packet to the edge cloud, wherein the heartbeat packet carries the identifier of the edge box, so that the edge cloud can determine whether the task to be executed of the edge box exists currently according to the identifier of the edge box; the generating module generates a task request and sends the task request to the edge cloud if a feedback heartbeat packet of the edge cloud is received and the content of the feedback heartbeat packet is not empty, so that the edge cloud can issue a corresponding task to be executed to the edge box according to the task request, and the feedback heartbeat packet is generated by the edge cloud based on the heartbeat packet of the edge box.
A fourth aspect of the present application provides an edge cloud, comprising: the receiving module is used for receiving a heartbeat packet sent by an edge box, and the heartbeat packet carries an identifier of the edge box; the judging module is used for determining whether the tasks to be executed of the edge box exist or not based on the identification; and if the feedback heartbeat packet does not exist, sending a feedback heartbeat packet with non-empty content to the edge box, so that the edge box generates a task request according to the feedback heartbeat packet with non-empty content, wherein the task request is used for acquiring a target task to be executed from the edge cloud.
A fifth aspect of the present application provides a data transmission system, the system comprising: the edge box of the third aspect and the edge cloud of the fourth aspect.
Compared with the prior art, according to the data transmission method provided by the first aspect of the application, the heartbeat packet carrying the identifier of the edge box is sent to the edge cloud through the edge box, then the edge cloud determines whether the edge box to-be-executed task exists according to the identifier in the heartbeat packet, if the edge box to-be-executed task exists, the edge cloud returns the feedback heartbeat packet with the content not being empty to the edge box, and if the feedback heartbeat packet does not exist, the edge cloud edge box returns the feedback heartbeat packet with the content being empty, so that the edge box can determine whether a task request for acquiring the to-be-executed task from the edge cloud is generated based on the feedback heartbeat packet, and finally the edge box with the to-be-executed task in the edge cloud sends the task request to the edge cloud so as to acquire the to-be-executed task of the edge box in the edge cloud. Therefore, the task request sent by the edge box without the task in the edge cloud to the edge cloud can be avoided, the data transmission quantity between the edge box and the edge cloud is reduced, the occupation of transmission resources is reduced, and the edge cloud can interact with more edge boxes simultaneously.
The data transmission method provided by the second aspect, the edge box provided by the third aspect, the edge cloud provided by the fourth aspect, and the data transmission system provided by the fifth aspect of the present application have the same or similar beneficial effects as the data transmission method provided by the first aspect.
Drawings
The above and other objects, features and advantages of exemplary embodiments of the present application will become readily apparent from the following detailed description read in conjunction with the accompanying drawings. Several embodiments of the present application are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings and in which like reference numerals refer to similar or corresponding parts and in which:
fig. 1 is a first schematic flow chart of a data transmission method in an embodiment of the present application;
fig. 2 is a second flowchart illustrating a data transmission method according to an embodiment of the present application;
fig. 3 is a third schematic flowchart of a data transmission method in an embodiment of the present application;
fig. 4 is a fourth schematic flowchart of a data transmission method in the embodiment of the present application;
FIG. 5 is a schematic structural diagram of an edge box in an embodiment of the present application;
FIG. 6 is a schematic structural diagram of an edge cloud in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a data transmission system in an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
It is to be noted that, unless otherwise specified, technical or scientific terms used herein shall have the ordinary meaning as understood by those skilled in the art to which this application belongs.
Currently, when there are tasks in the edge cloud to be executed by some edge boxes, a task request is usually sent to the edge cloud for each edge box. The task request typically carries the requested task information and information of the edge box that sent the request. After receiving the task requests sent by each edge box, the edge cloud needs to process the task requests sent by each edge box, and after determining the edge box with the task to be executed, the edge cloud responds to the edge box corresponding to the task to be executed, and sends the task to the edge box corresponding to the task to be executed. The information interaction mode between the edge box and the edge cloud increases invalid transmission between the edge cloud and the edge box, increases the burden of data transmission between the edge cloud and the edge box, and leads to occupation of excessive transmission resources.
In view of this, an embodiment of the present application provides a data transmission method, an edge box, an edge cloud, and a data transmission system. In the heartbeat packet, only the identification of the edge box exists, and detailed information of the task is not contained. Then, the edge cloud analyzes and processes the heartbeat packets sent by each edge box, and only enables the edge box with the task to send a task request to the edge box, so that the task is distributed to the edge box. When data is transmitted between each edge box and the edge cloud first, each edge box does not send detailed information of a requested task to the edge cloud first, and only sends a heartbeat packet carrying a current edge box identifier to the edge cloud first. Only after the edge cloud determines which edge boxes have tasks, the edge boxes send task requests carrying detailed task information to the edge cloud. Therefore, the data transmission quantity between the edge box and the edge cloud can be reduced, the data transmission burden between the edge cloud and the edge box is further reduced, and the occupation of transmission resources is reduced.
First, a data transmission method provided in an embodiment of the present application is described in detail.
Fig. 1 is a schematic flow chart of a data transmission method in an embodiment of the present application, and referring to fig. 1, the method is applied to an edge box. The method can comprise the following steps:
s101: and sending a heartbeat packet to the edge cloud, wherein the heartbeat packet carries the identifier of the edge box, so that the edge cloud can determine whether the task to be executed of the edge box exists at present according to the identifier of the edge box.
S102: if the feedback heartbeat packet of the edge cloud is received and the content of the feedback heartbeat packet is not empty, a task request is generated and sent to the edge cloud, so that the edge cloud can issue the corresponding task to be executed to the edge box according to the task request, and the feedback heartbeat packet is generated by the edge cloud based on the heartbeat packet of the edge box.
Fig. 2 is a schematic flow diagram of a data transmission method in the embodiment of the present application, and referring to fig. 2, the method is applied to an edge cloud. The method can comprise the following steps:
s201: and receiving a heartbeat packet sent by the edge box, wherein the heartbeat packet carries the identifier of the edge box.
S202: determining whether there is a task of the edge box to be performed based on the identification.
S203: if the feedback heartbeat packet exists, sending a feedback heartbeat packet with non-empty content to the edge box, so that the edge box generates a task request according to the feedback heartbeat packet with non-empty content, wherein the task request is used for acquiring a target task to be executed from the edge cloud.
Next, the data transmission method provided in the embodiment of the present application is described in detail with a specific process of interaction between the edge box and the edge cloud.
Fig. 3 is a schematic flow chart of a data transmission method in the embodiment of the present application, and referring to fig. 3, the method may include:
s301: the edge box sends heartbeat packets to the edge cloud.
The heartbeat packet carries an identifier of the edge box, so that the edge cloud can determine whether the task to be executed of the edge box exists currently according to the identifier of the edge box.
In the process of information interaction between a plurality of edge boxes and an edge cloud, firstly, each edge box sends a heartbeat packet to the edge cloud. In the heartbeat packet, the identification of the edge box is carried. That is, each edge box sends its own identifier to the edge cloud at certain time intervals, so that the edge cloud searches whether there is a task that the edge box needs to perform currently.
S302: and the edge cloud receives the heartbeat packet sent by the edge box.
Wherein, the heartbeat package carries the identification of the edge box.
S303: the edge cloud determines whether there is a task to be performed for the edge box based on the identification. If yes, go to S304; if not, S305 is executed.
When tasks need to be executed by certain edge boxes, the edge cloud stores the tasks and generates a list of the tasks to be executed. And then, the edge cloud receives heartbeat packets which are sent by each edge box and carry the self identification of the edge box. The edge cloud can compare the identification of each edge box with the tasks in the list and determine which tasks need which edge boxes to execute. That is, it is determined whether each edge box has a task in the edge cloud that needs to be performed.
S304: the edge cloud sends a feedback heartbeat packet to the edge box that is not empty in content.
The feedback heartbeat packet is used for indicating that an edge box exists in the edge cloud and a task to be executed exists. The feedback heartbeat packet may also be referred to as a heartbeat message, so that the edge box generates a task request according to the feedback heartbeat packet whose content is not empty. The task request is used for acquiring a task to be executed from the edge cloud.
When the edge cloud determines that a task corresponding to an edge box currently exists, the edge cloud responds to the edge box, namely, returns a feedback heartbeat packet. The feedback heartbeat packet carries information indicating that the task to be executed exists in the edge cloud. To inform the edge box that there is a task to be performed in the edge cloud, so that the edge box further requests the task from the edge cloud.
S305: the edge cloud sends a feedback heartbeat packet to the edge box with empty content.
When the edge cloud determines that the task corresponding to a certain edge box does not exist currently, the edge cloud can also respond to the edge box, namely, the feedback heartbeat packet with empty feedback content is fed back, namely, the edge box is told that the task corresponding to the edge box does not exist currently, and then the interaction process of the edge box and the edge cloud is finished. Of course, the edge cloud may not respond to the edge box at all. In the event that the edge box does not receive an edge cloud after a period of time, the edge box can determine that there are no tasks in the edge cloud that it is required to perform.
Then, when the edge box receives the feedback heartbeat packet whose content is not empty, the edge box generates a task request based on the feedback heartbeat packet whose content is not empty, and sends the task request to the edge cloud. After receiving the task request, the edge cloud feeds corresponding task information back to the corresponding edge box based on the task request. The edge box can retrieve the tasks it needs to perform from the received task information.
Generally, the task request may carry detailed information of the requested task, so that the edge cloud knows which task or tasks of the edge box request currently sending the request, and further sends the corresponding tasks to the edge box. As for the specific contents of the above detailed information, it may be a name, a version number, and the like of the task. The specific content of the detailed information of the task is not limited herein.
When the edge box receives a feedback heartbeat packet with empty content, the edge box knows that the tasks which need to be executed by the edge box do not exist in the edge cloud. At this time, the edge box does not send any information to the edge cloud any more, thereby reducing the waste of data transmission resources between the edge cloud and the edge box.
As can be seen from the above, in the data transmission method provided in the embodiment of the present application, the edge box sends the heartbeat packet carrying the identifier of the edge box to the edge cloud, and then the edge cloud determines whether the edge box to-be-executed task exists according to the identifier in the heartbeat packet, if the edge box exists, the edge cloud returns the feedback heartbeat packet whose content is not empty to the edge box, and if the feedback heartbeat packet does not exist, the edge cloud edge box returns the feedback heartbeat packet whose content is empty, so that the edge box can determine whether to generate a task request for acquiring the to-be-executed task from the edge cloud based on the feedback heartbeat packet, and finally the edge box having the to-be-executed task in the edge cloud sends the task request to the edge cloud to acquire the to-be-executed task of the edge box in the edge cloud. Therefore, the task request sent by the edge box without the task in the edge cloud to the edge cloud can be avoided, the data transmission quantity between the edge box and the edge cloud is reduced, the occupation of transmission resources is reduced, and the edge cloud can interact with more edge boxes simultaneously.
Further, as a refinement and extension of the method shown in fig. 3, an embodiment of the present application further provides a data transmission method. Fig. 4 is a fourth schematic flowchart of a data transmission method in the embodiment of the present application, and referring to fig. 4, the method may include:
s401: the edge boxes adjust the heartbeat frequency of the heartbeat packet in real time according to the total number of the edge boxes interacting with the edge cloud; and/or the number of servers corresponding to the edge cloud is increased or decreased in real time according to the total number of the edge boxes interacting with the edge cloud.
When the number of edge boxes performing information interaction with the edge cloud is large, a plurality of edge boxes send information to the edge cloud, which may cause congestion of an information interaction channel. Therefore, before each edge box sends a heartbeat packet to the edge cloud, one or more edge boxes can count the total number of the edge boxes performing information interaction with the edge cloud, and then adjust the heartbeat frequency of the heartbeat packet in real time according to the total number, that is, adjust the interval time of sending the identification of each edge box to the edge cloud in real time, so that each edge box sends the heartbeat packet to the edge cloud according to the adjusted heartbeat frequency.
Particularly, when the total number of the edge boxes performing information interaction with the edge cloud is large, the heartbeat frequency of the heartbeat packet can be set to be longer, so that each edge box sends the identification to the edge cloud after a long time, excessive information in an information interaction channel is avoided, and the data transmission efficiency is improved. When the total number of the edge boxes performing information interaction with the edge cloud is small, the heartbeat frequency of the heartbeat packet can be set to be short, so that each edge box can send the identification to the edge cloud again at short intervals, and further, on the basis of ensuring the data transmission efficiency, corresponding tasks can be acquired more quickly, and the execution efficiency of the tasks is improved.
In addition, when the number of edge boxes performing information interaction with the edge cloud is large, more edge boxes send information to the edge cloud, and the edge cloud needs to process more information, which may reduce the management efficiency of the edge cloud, and may even cause an error in management of the edge cloud. Therefore, before each edge box sends a heartbeat packet to the edge cloud, the edge cloud may count the total number of the edge boxes performing information interaction with the edge cloud, and then increase or decrease the number of servers corresponding to the edge cloud in real time according to the total number.
Particularly, when the total number of edge boxes for information interaction with the edge cloud is large, the number of servers corresponding to the edge cloud can be increased, so that the edge cloud can process a large amount of information at the same time, and the information processing efficiency of the edge cloud is improved. When the total number of edge boxes for information interaction with the edge cloud is small, the number of servers corresponding to the edge cloud is reduced, and the cost of edge computing can be saved on the basis of ensuring the processing efficiency of the edge cloud.
S402: the edge box sends a heartbeat packet to the edge cloud according to the adjusted heartbeat frequency; and/or the edge box sends the heartbeat packet to a designated server in the edge cloud.
After the heartbeat frequency of the heartbeat packet is adjusted, the edge box can send the heartbeat packet to the edge cloud according to the adjusted heartbeat frequency; and/or after the number of the servers of the edge cloud is increased or decreased, the edge box can send the heartbeat packet to the server designated by the edge cloud. The specific manner of sending the heartbeat packet to the edge cloud by the edge box is the same as or similar to that in step S301, and is not described herein again.
Here, only a specific manner in which the edge box transmits the heartbeat packet to the server designated in the edge cloud will be described. After the number of the servers in the edge cloud is changed, the corresponding sending relationship between the edge box and the servers is correspondingly adjusted. Typically, several edge boxes correspond to a given server. Therefore, the data processing amount of each server in the edge cloud can be balanced, and the edge cloud can normally process information sent by all edge boxes. Therefore, after the number of servers of the edge cloud is increased or decreased, each edge box needs to send its heartbeat packet to a server designated by the edge cloud.
S403: and judging whether the heartbeat packet is received within the preset time by the edge cloud. If not, executing S404; if yes, go to S405.
S404: the edge cloud modifies the operational status of the edge box to offline, or the edge cloud sends a query to the edge box.
Where the query is used to query whether the edge box is online.
Besides sending a heartbeat packet to the edge cloud for checking whether a corresponding task exists in the edge cloud, the edge box also has the function of reporting the working state of the edge box at regular time, so that the edge cloud can know whether each edge box is on line currently.
If the edge cloud does not receive the heartbeat packet sent by the edge box within the preset time, it is indicated that the edge box may have a problem, and the heartbeat packet is not sent to the edge cloud according to a certain time, then the edge cloud may consider that the edge box is currently in an offline state, and modify the working state of the edge box to be offline.
If the edge cloud does not receive the heartbeat packet sent by the edge box within the preset time, it may be that the edge box has sent the heartbeat packet, but a problem occurs in the transmission process of the heartbeat packet, and the edge cloud cannot receive the heartbeat packet within a certain time. If the edge cloud receives the feedback of the edge box, which indicates that a problem occurs in the transmission process of the heartbeat packet, the edge cloud can cause the edge box to resend the heartbeat packet once so as to ensure that the edge box can continue to perform task inspection. And if the edge cloud does not receive the feedback of the edge box, the edge cloud is proved to be offline, and the working state of the edge box is modified to be offline by the edge cloud.
S405: and the edge cloud determines whether an edge box to-be-executed task exists according to the identifier in the heartbeat packet. If not, executing S406; if yes, go to S407.
If the edge cloud receives the heartbeat packet sent by the edge box within the preset time, it is indicated that the edge box is online currently, and whether a task which needs to be executed by the edge cloud exists needs to be checked, the edge cloud can determine whether the task which needs to be executed by the edge box exists according to the identifier in the heartbeat packet.
After receiving the heartbeat packet sent by the edge box, the edge cloud can record the heartbeat time of the heartbeat packet to avoid repeatedly receiving the same heartbeat packet.
S406: the edge cloud sends a feedback heartbeat packet with empty content to the edge box.
When the edge cloud does not inquire the task corresponding to the edge box, if the edge cloud does not respond to the edge box, the edge box may think that a problem occurs in the information transmission process, but the edge box may send the identification of the edge box to the edge cloud again instead of the edge cloud not having the corresponding task. In order to avoid misunderstanding of the edge box, messages are frequently sent to the edge cloud, and after the edge cloud does not inquire tasks corresponding to the edge box, a feedback heartbeat packet is sent to the edge box. But the content in the feedback heartbeat packet is empty. Therefore, after the edge box receives the feedback heartbeat packet with empty content, the edge box can clearly determine that tasks which need to be executed do not exist in the edge cloud, and further can not frequently send information to the edge cloud, and normal information interaction between the edge cloud and each edge box is ensured.
S407: the edge cloud sends a feedback heartbeat packet to the edge box that is not empty in content.
When the edge cloud queries that the task corresponding to the edge box exists, the edge cloud returns a feedback heartbeat packet with content not being empty to the edge box. The feedback heartbeat packet includes a task list. The task list also contains the types of the tasks to be executed. The edge cloud informs the edge box of the type of the task to be executed through the feedback heartbeat packet, so that the edge box can generate a task request in a corresponding format based on the task type.
Specifically, S407 may include:
step A1: and the edge cloud determines the type of the task to be executed of the edge box from the information of all the tasks to be executed.
In the edge cloud, detailed information of all tasks to be executed is stored. The edge cloud can look up the type of task to be performed by the edge box from this detailed information.
Step A2: the edge cloud generates a task list based on the type, and adds the task list to the feedback heartbeat package.
After finding out the type of the task to be executed by the edge box, the edge cloud can add the type into the task list, and further add the task list into the feedback heartbeat packet for subsequent sending to the corresponding edge box.
Step A3: and the edge cloud sends a feedback heartbeat packet carrying the task list to the edge box.
In this way, the edge box can be enabled to generate a request in a corresponding format according to the type in the feedback heartbeat packet.
The specific way for the edge cloud to return the feedback heartbeat packet to the edge box is the same as or similar to the step S304, and is not described herein again.
S408: and the edge box generates a task request based on the type of the task to be executed in the task list of the feedback heartbeat packet.
The format of the corresponding requests is different for different types of tasks. Therefore, after receiving the feedback heartbeat packet returned by the edge cloud, the edge box firstly analyzes the feedback heartbeat packet, determines the type of the task to be executed in the edge cloud, and then generates a task request in a corresponding format based on the type.
In the process that the edge box generates the task request based on the task type, the task request corresponding to a part of the task types may be generated to obtain a part of the tasks to be executed, and the task request corresponding to all the task types may also be generated to obtain all the tasks to be executed, which may be selected by the edge box according to the actual situation of the edge box, and is not specifically limited herein.
S409: the edge box sends the task request to the edge cloud.
S410: and the edge cloud sends the corresponding target to-be-executed task to the edge box based on the task request, and modifies the state of the target to-be-executed task into the execution state.
After receiving the task request sent by the edge box, the edge cloud can determine which tasks need to be acquired by the edge box by analyzing the task request, and then sends the tasks need to be acquired by the edge box to the edge box, so that the edge box can execute the tasks.
In the process that the edge cloud sends the task to be executed to the edge box, in order to avoid that the task execution fails or is wrong due to the fact that the edge box executes more tasks at the same time, the task request sent by the edge box can also carry current execution task information of the edge box. Therefore, the edge cloud can determine how many tasks to be executed are sent to the edge box according to the number of the tasks actually executed by the edge box at present, so that the edge box is prevented from executing more tasks at the same time, and the execution efficiency of each task is improved.
Specifically, before performing S410, the method may further include:
step B1: and the edge cloud determines a target task to be executed of the edge box from all tasks of the edge box according to the current task execution information of the edge box and the preset maximum value of the task execution amount of the edge box.
The edge cloud can determine all tasks required to be executed by the edge box by querying the task pool in the edge cloud according to the identifier of the edge box in the heartbeat packet. Generally, all tasks herein can be considered tasks that the edge box has not yet performed.
Because the number of tasks that can be performed by the edge box at the same time is limited, if the number of tasks that can be performed by the edge box at the same time exceeds the number of tasks that the edge box can bear, the edge box may be stuck and even have errors when performing the tasks. Therefore, after the edge cloud queries all tasks of the edge box, the edge cloud needs to determine which tasks are currently executed by the edge box according to the currently executed task information of the edge box, and what the number of the currently executed tasks is, and further determines a target task to be executed by the edge box from all the tasks of the edge box by combining a preset maximum value of the task execution amount of the edge box, that is, determines whether a certain number of tasks can be given to the edge box again from all the tasks of the edge box.
For example, assume that an edge box is only able to perform 5 tasks at the same time. And the edge cloud determines that 8 tasks are to be executed by the edge box from the task pool according to the identifier of the edge box. And, according to the currently executed task information of the edge box, the edge box currently executes other 3 tasks. At this time, the edge cloud determines 2 tasks from the 8 tasks as the target tasks to be executed by the edge box.
Of course, it is also possible that the edge box itself determines the number of tasks it performs at one time. Specifically, after the edge cloud determines all tasks to be performed by the edge box, the edge cloud notifies the edge box of all determined tasks. The edge box may determine at its own discretion whether all tasks are performed together or only which of all tasks are performed. The number of tasks performed by the edge box and the manner of determining the number of tasks performed by the edge box are not limited herein.
After the edge cloud sends the corresponding task to the edge box, the edge cloud may modify the state of the task to be in execution to indicate that the task is being executed by the edge box, so as to facilitate management of each task and each edge box by the edge cloud.
S411: and the edge box executes the target task to be executed and feeds back an execution result of the target task to be executed to the edge cloud.
The feedback information is information which is generated by the edge cloud based on the task request and is used for the edge box to execute the corresponding task.
After receiving the task sent by the edge cloud, the edge box can continue to execute the task. The task sent by the edge cloud may be one or more, which requires to see how many tasks to be executed by the edge box actually exist in the edge cloud. After the edge box receives the tasks, if the tasks are multiple tasks, the edge box can also select to execute all the tasks at the same time or execute the tasks at different time intervals according to the actual situation of the edge box, and the specific way of selecting the tasks to execute by the edge box is not limited here.
After the edge box executes the task, the execution result of the corresponding task needs to be fed back to the edge cloud, so that the edge cloud can know the execution condition of the task by the edge box in time, and the edge cloud can manage each task and each edge box conveniently.
S412: and the edge cloud modifies the state of the target task to be executed into the state of successful execution or failed execution based on the execution result, and displays the modified state of the target task to be executed.
If the task is successfully executed by the edge box, the execution result fed back to the edge cloud by the edge box is the successful execution, and then the state of the task can be modified to be the successful execution by the edge cloud, so that the follow-up edge cloud is prevented from repeatedly sending the task to the edge box to be executed.
And if the execution of the task by the edge box fails, the execution result fed back to the edge cloud by the edge box is the execution failure, and then the edge cloud can modify the state of the task into the execution failure, so that the subsequent edge cloud can send the task to the edge box again for execution, and the task is ensured to be executed and completed in the edge box.
Finally, the edge cloud can also display the current state of each task, so that a user can clearly check the execution condition of each task in the corresponding edge box through the edge cloud, and the management work of the edge cloud is further facilitated.
Finally, it should be noted that, in the process of information transmission between the edge cloud and the edge box, the edge cloud sends corresponding information to an agent (agent) node of the edge box, and the edge box receives the information sent by the edge cloud through the agent node. And the edge box also sends corresponding information to the edge cloud through the agent node of the edge box, and the edge cloud receives the information sent by the edge box through the agent node of the edge box. This is because agent nodes in the edge box can know the address of the edge cloud, and thus interact with the edge cloud.
Finally, it should be noted that the task may be an upgrade task in practical applications. For example: the edge boxes request system or software upgrading from the edge cloud, and the edge boxes and the edge cloud interact through heartbeat packages, feedback heartbeat packages, task requests, task responses and the like, so that the edge cloud can control upgrading of the edge boxes, namely, which edge boxes are upgraded and which edge boxes are not upgraded.
The task may also be an application deployment task. For example: the edge cloud stores information of which edge boxes need to install which applications. And then, the edge box and the edge cloud interact through a heartbeat packet, a feedback heartbeat packet, a task request, a task response and the like, so that the edge cloud can control which edge boxes need to install which applications. Of course, the tasks described above may also be other types of tasks. The specific type of task is not limited herein.
As can be seen from the above, the data transmission method for the edge cloud and the edge box provided in the embodiment of the present application enables communication between the edge cloud and the edge box to use a short link (json over http) manner, that is, functions of online status check and work task issue of the edge box are solved by a daily heartbeat manner, so that the concurrent processing capability of the edge cloud can be improved.
Based on the same inventive concept, as an implementation of the method, the embodiment of the application also provides an edge box. Fig. 5 is a schematic structural diagram of an edge box in an embodiment of the present application, and referring to fig. 5, the edge box may include:
a sending module 501, configured to send a heartbeat packet to an edge cloud, where the heartbeat packet carries an identifier of the edge box, so that the edge cloud determines whether a task to be executed of the edge box currently exists according to the identifier of the edge box.
The generating module 502 is configured to generate a task request and send the task request to the edge cloud if a feedback heartbeat packet of the edge cloud is received and the content of the feedback heartbeat packet is not empty, so that the edge cloud issues a corresponding to-be-executed task to the edge box according to the task request, and the feedback heartbeat packet is generated based on the heartbeat packet of the edge box by the edge cloud.
In other embodiments of the present application, the feedback heartbeat packet includes a task list, and the task list includes a type of a task to be executed; and the generating module is used for generating a task request based on the type of the task to be executed.
In other embodiments of the present application, the edge box further comprises: the adjusting module is used for adjusting the heartbeat frequency of the heartbeat packet in real time according to the total number of the edge boxes interacting with the edge cloud; and the sending module is used for sending the heartbeat packet to the edge cloud according to the adjusted heartbeat frequency.
In other embodiments of the present application, the edge box further comprises: and the execution module is used for executing the task to be executed based on the feedback information of the edge cloud and feeding back the execution result of the task to be executed to the edge cloud, wherein the feedback information is information which is generated by the edge cloud based on the task request and is used for the edge box to execute the corresponding task.
It is noted here that the above description of the edge box embodiment, similar to the description of the method embodiment described above, has similar advantageous effects as the method embodiment. For technical details not disclosed in the embodiments of the edge box of the present application, reference is made to the description of the embodiments of the method of the present application.
Based on the same inventive concept, as an implementation of the method, the embodiment of the application further provides an edge cloud. Fig. 6 is a schematic structural diagram of an edge cloud in an embodiment of the present application, and referring to fig. 6, the edge cloud may include:
the receiving module 601 is configured to receive a heartbeat packet sent by an edge box, where the heartbeat packet carries an identifier of the edge box.
A determining module 602, configured to determine whether there is a task to be executed of the edge box based on the identifier.
A response module 603, configured to send a feedback heartbeat packet whose content is not empty to the edge box if the feedback heartbeat packet exists, so that the edge box generates a task request according to the feedback heartbeat packet whose content is not empty, where the task request is used to obtain a target task to be executed from the edge cloud.
In other embodiments of the present application, the response module is configured to determine the type of the task to be executed of the edge box from information of all the tasks to be executed; generating a task list based on the type, and adding the task list to the feedback heartbeat packet; and sending a feedback heartbeat packet carrying the task list to the edge box.
In other embodiments of the present application, the edge cloud further comprises: and the confirming module is used for modifying the working state of the edge box to be offline if the heartbeat packet is not received within preset time, or sending an inquiry to the edge box, wherein the inquiry is used for inquiring whether the edge box is online or not.
In other embodiments of the present application, the edge cloud further comprises: and the adjusting module is used for increasing or decreasing the number of the servers corresponding to the edge cloud in real time according to the total number of the edge boxes interacting with the edge cloud, so that the edge boxes send the heartbeat packets to the appointed servers in the edge cloud.
In other embodiments of the present application, the edge cloud further comprises: the display module is used for sending a corresponding target task to be executed to the edge box based on the task request sent by the edge box and modifying the state of the target task to be executed into execution; receiving an execution result of the target task to be executed fed back by the edge box; and modifying the state of the target task to be executed into the execution success or the execution failure based on the execution result, and displaying the modified state of the target task to be executed.
In other embodiments of the present application, the task request further carries information of a currently executed task of the edge box; the edge cloud further comprises: and the screening module is used for determining a target task to be executed of the edge box from all tasks of the edge box according to the current task execution information of the edge box and a preset maximum value of the task execution amount of the edge box.
It is noted here that the above description of the edge cloud embodiment, similar to the description of the method embodiment described above, has similar beneficial effects as the method embodiment. For technical details not disclosed in the embodiments of the edge cloud of the present application, please refer to the description of the embodiments of the method of the present application for understanding.
Based on the same inventive concept, as the integral realization of the edge box and the edge cloud, the embodiment of the application also provides a data transmission system. Fig. 7 is a schematic structural diagram of a data transmission system in an embodiment of the present application, and referring to fig. 7, the system may include: an edge cloud 701 and a plurality of edge boxes 702.
It is noted here that the above description of the system embodiments, similar to the edge box and edge cloud embodiments described above, have similar benefits as the edge box and edge cloud embodiments. For technical details not disclosed in the embodiments of the system of the present application, please refer to the description of the embodiments of the edge box and edge cloud of the present application.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (13)
1. A data transmission method, characterized in that said method is applied to an edge box; the method comprises the following steps:
sending a heartbeat packet to an edge cloud, wherein the heartbeat packet carries an identifier of the edge box, so that the edge cloud can determine whether a task to be executed of the edge box exists currently according to the identifier of the edge box;
if a feedback heartbeat packet of the edge cloud is received and the content of the feedback heartbeat packet is not empty, a task request is generated and sent to the edge cloud so that the edge cloud can issue a corresponding task to be executed to the edge box according to the task request, and the feedback heartbeat packet is generated by the edge cloud based on the heartbeat packet of the edge box.
2. The method according to claim 1, wherein the feedback heartbeat packet includes a task list, and the task list includes a type of a task to be executed; the generating of the task request comprises:
and generating a task request based on the type of the task to be executed.
3. The method of claim 1, wherein prior to the sending heartbeat packets to an edge cloud, the method further comprises:
adjusting the heartbeat frequency of the heartbeat packet in real time according to the total number of edge boxes interacting with the edge cloud;
the sending of the heartbeat packet to the edge cloud includes:
and sending a heartbeat packet to the edge cloud according to the adjusted heartbeat frequency.
4. The method of any of claims 1-3, wherein after the sending the task request to the edge cloud, the method further comprises:
and executing the task to be executed based on the feedback information of the edge cloud, and feeding back an execution result of the task to be executed to the edge cloud, wherein the feedback information is information which is generated by the edge cloud based on the task request and is used for the edge box to execute a corresponding task.
5. A data transmission method, characterized in that the method is applied to an edge cloud; the method comprises the following steps:
receiving a heartbeat packet sent by an edge box, wherein the heartbeat packet carries an identifier of the edge box;
determining whether there is a task to be performed for the edge box based on the identification;
if the content of the feedback heartbeat packet is not empty, the feedback heartbeat packet with the content not empty is sent to the edge box, so that the edge box generates a task request according to the feedback heartbeat packet with the content not empty, and the task request is used for acquiring a target task to be executed from the edge cloud.
6. The method of claim 5, wherein said issuing a feedback heartbeat packet to said edge box whose contents are not empty comprises:
determining the type of the tasks to be executed of the edge box from the information of all the tasks to be executed;
generating a task list based on the type, and adding the task list to the feedback heartbeat packet;
and sending a feedback heartbeat packet carrying the task list to the edge box.
7. The method of claim 5, further comprising:
if the heartbeat packet is not received within the preset time, the working state of the edge box is changed to be offline, or an inquiry is sent to the edge box, wherein the inquiry is used for inquiring whether the edge box is online or not.
8. The method of claim 5, wherein prior to the receiving the heartbeat packet sent by the edge box, the method further comprises:
and increasing or decreasing the number of servers corresponding to the edge cloud in real time according to the total number of the edge boxes interacting with the edge cloud, so that the edge boxes send the heartbeat packets to the specified servers in the edge cloud.
9. The method according to any one of claims 5 to 8, wherein after said issuing a feedback heartbeat packet to the edge box whose content is not empty, the method further comprises:
sending a corresponding target task to be executed to the edge box based on the task request sent by the edge box, and modifying the state of the target task to be executed into execution;
receiving an execution result of the target task to be executed fed back by the edge box;
and modifying the state of the target task to be executed into the execution success or the execution failure based on the execution result, and displaying the modified state of the target task to be executed.
10. The method of claim 9, wherein the task request further carries information about a currently executed task of the edge box; before the task request sent based on the edge box sends a corresponding target task to be executed to the edge box, the method further includes:
and determining a target task to be executed of the edge box from all tasks of the edge box according to the current task execution information of the edge box and a preset maximum value of the task execution amount of the edge box.
11. An edge box, comprising:
the sending module is used for sending a heartbeat packet to the edge cloud, wherein the heartbeat packet carries the identifier of the edge box, so that the edge cloud can determine whether the task to be executed of the edge box exists currently according to the identifier of the edge box;
the generating module generates a task request and sends the task request to the edge cloud if a feedback heartbeat packet of the edge cloud is received and the content of the feedback heartbeat packet is not empty, so that the edge cloud can issue a corresponding task to be executed to the edge box according to the task request, and the feedback heartbeat packet is generated by the edge cloud based on the heartbeat packet of the edge box.
12. An edge cloud, wherein the edge cloud comprises:
the receiving module is used for receiving a heartbeat packet sent by an edge box, and the heartbeat packet carries an identifier of the edge box;
the judging module is used for determining whether a task to be executed of the edge box exists or not based on the identification;
and if the feedback heartbeat packet does not exist, sending a feedback heartbeat packet with non-empty content to the edge box, so that the edge box generates a task request according to the feedback heartbeat packet with non-empty content, wherein the task request is used for acquiring a target task to be executed from the edge cloud.
13. A data transmission system, the system comprising: the edge box of claim 11 and the edge cloud of claim 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210318582.2A CN114666332A (en) | 2022-03-29 | 2022-03-29 | Data transmission method, edge box, edge cloud and data transmission system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210318582.2A CN114666332A (en) | 2022-03-29 | 2022-03-29 | Data transmission method, edge box, edge cloud and data transmission system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114666332A true CN114666332A (en) | 2022-06-24 |
Family
ID=82033004
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210318582.2A Pending CN114666332A (en) | 2022-03-29 | 2022-03-29 | Data transmission method, edge box, edge cloud and data transmission system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114666332A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104301423A (en) * | 2014-10-24 | 2015-01-21 | 北京奇虎科技有限公司 | Heartbeat message sending method, device and system |
| CN105871678A (en) * | 2016-06-02 | 2016-08-17 | 郭立峰 | Method for remotely managing terminal devices in private network |
| CN109101325A (en) * | 2017-06-21 | 2018-12-28 | 杭州海康威视数字技术股份有限公司 | A kind of method for scheduling task, device, system and electronic equipment |
| CN110389815A (en) * | 2018-04-18 | 2019-10-29 | 阿里巴巴集团控股有限公司 | Task processing method, apparatus and system |
| CN111708557A (en) * | 2020-05-26 | 2020-09-25 | 北京金山云网络技术有限公司 | Method, device and storage medium for updating configuration file |
| WO2020207264A1 (en) * | 2019-04-08 | 2020-10-15 | 阿里巴巴集团控股有限公司 | Network system, service provision and resource scheduling method, device, and storage medium |
| CN113873017A (en) * | 2021-09-06 | 2021-12-31 | 绿盟科技集团股份有限公司 | Heartbeat period adjusting method and device, client and server |
-
2022
- 2022-03-29 CN CN202210318582.2A patent/CN114666332A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104301423A (en) * | 2014-10-24 | 2015-01-21 | 北京奇虎科技有限公司 | Heartbeat message sending method, device and system |
| CN105871678A (en) * | 2016-06-02 | 2016-08-17 | 郭立峰 | Method for remotely managing terminal devices in private network |
| CN109101325A (en) * | 2017-06-21 | 2018-12-28 | 杭州海康威视数字技术股份有限公司 | A kind of method for scheduling task, device, system and electronic equipment |
| CN110389815A (en) * | 2018-04-18 | 2019-10-29 | 阿里巴巴集团控股有限公司 | Task processing method, apparatus and system |
| WO2020207264A1 (en) * | 2019-04-08 | 2020-10-15 | 阿里巴巴集团控股有限公司 | Network system, service provision and resource scheduling method, device, and storage medium |
| CN111708557A (en) * | 2020-05-26 | 2020-09-25 | 北京金山云网络技术有限公司 | Method, device and storage medium for updating configuration file |
| CN113873017A (en) * | 2021-09-06 | 2021-12-31 | 绿盟科技集团股份有限公司 | Heartbeat period adjusting method and device, client and server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200213244A1 (en) | Internet of Things Resource Subscription Method, Device, and System | |
| CN107729139B (en) | Method and device for concurrently acquiring resources | |
| CN113709048A (en) | Routing information sending and receiving method, network element and node equipment | |
| US20110179151A1 (en) | Tuning and optimizing distributed systems with declarative models | |
| US10944655B2 (en) | Data verification based upgrades in time series system | |
| US8538793B2 (en) | System and method for managing real-time batch workflows | |
| CN110209342B (en) | Capacity expansion method, device, equipment and system for cloud hard disk | |
| CN109542718B (en) | Service call monitoring method and device, storage medium and server | |
| US20210342178A1 (en) | Method and device for instantiating virtualized network function | |
| CN112099935B (en) | Task processing method and device | |
| CN111831191A (en) | Workflow configuration method and device, computer equipment and storage medium | |
| CN111507674B (en) | Task information processing method, device and system | |
| US20230029198A1 (en) | Scheduling complex jobs in a distributed network | |
| CN108900627B (en) | Network request method, terminal device and storage medium | |
| CN112448987A (en) | Fusing degradation triggering method and system and storage medium | |
| CN112202879B (en) | Middleware management method and device, electronic equipment and storage medium | |
| CN112583630A (en) | Device management method, device, system, device and storage medium | |
| JP4516594B2 (en) | Message transmission control method, message transmission control device, and message transmission control program | |
| CN114666332A (en) | Data transmission method, edge box, edge cloud and data transmission system | |
| CN114090268B (en) | Container management method and container management system | |
| CN111913784A (en) | Task scheduling method and device, network element and storage medium | |
| CN113220433B (en) | Agent program operation management method and system | |
| CN113254097A (en) | Configuration information issuing method and device, electronic equipment and storage medium | |
| CN114153583A (en) | Task state management method, task management system and task calling system | |
| CN108259527B (en) | Proxy-based service processing method and device and network element equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 101, floor 1, building 3, yard 18, Kechuang 10th Street, Beijing Economic and Technological Development Zone, Daxing District, Beijing 100176 Applicant after: Beijing yisiwei Computing Technology Co.,Ltd. Address before: Room 101, floor 1, building 3, yard 18, Kechuang 10th Street, Beijing Economic and Technological Development Zone, Daxing District, Beijing 100176 Applicant before: Beijing yisiwei Computing Technology Co.,Ltd. |