WO2020062048A1 - Method for transmitting update data, content delivery network node and data update system - Google Patents

Abstract

The present application relates to a method for transmitting update data, a content delivery network node and a data update system. The method for transmitting update data comprises: receiving a device capability model, the device capability model comprising hardware information and the data version of at least one edge device; according to the hardware information and the data version, receiving update data for updating the at least one edge device; receiving an update request for updating the least one edge device; receiving a device context of the edge device; generating a device-to-device communication model according to the update request and the device context; delivering the device-to-device communication model to a source synchronization device in the edge device to be updated; receiving a data request for transmitting the update data to the source synchronization device; and transmitting the update data to the source synchronization device according to the data request. The present application optimizes the delivery of update data by means of the content delivery network and device-to-device communication.

Description

Method for sending updated data, content distribution network node and data updating system Technical field

This application relates to the field of data updating. Specifically, the present application relates to a method for sending updated data, a content distribution network node, and a data update system.

Background technique

Cloud-based IoT systems inevitably require remote updates and device management. The conventional method is to centrally manage the device on the cloud server side. When the device needs to update the firmware or software, the device downloads the required data from the cloud server, and the cloud server controls the process of device update. During this update process, if there are a large number of devices to be updated, the cloud server or cloud platform will bear excessive pressure to provide services for a large number of devices, which will decrease when the network quality between the edge device and the cloud server is not good. Data transfer speed. Although it is possible for IoT devices made by the same manufacturer to share the same network, firmware, or software, the task of remotely updating these devices is usually separate.

Summary of the Invention

The embodiments of the present application provide a method for sending updated data, a content distribution network node device, and a data update system, so as to at least solve the problem of high data transmission pressure between the cloud server and the edge device when remotely updating the edge device in the prior art.

According to an aspect of the embodiment of the present application, a method for sending updated data is provided, including: receiving a device capability model, where the device capability model includes hardware information and data versions of at least one edge device; receiving and updating at least one edge according to the hardware information and data versions Receiving device update data; receiving an update request to update at least one edge device; receiving a device context of the edge device; generating a device-to-device communication model based on the update request and the device context, the device-to-device communication model including the connection relationship of the edge device to be updated; Distribute the device-to-device communication model to the source synchronization device in the edge device to be updated. The source synchronization device is determined from the edge device to be updated according to the connection relationship; receive a data request to send updated data to the source synchronization device, and a data request The receiver is determined according to the connection relationship; and the update data is sent to the source synchronization device according to the data request.

In this way, receiving update data to update the edge device, determining the source synchronization device according to the device-to-device communication model, and sending the update data to the source synchronization device, alleviating the pressure of transmitting update data from the cloud server to the edge device.

According to an exemplary embodiment of the present application, a device capability model is received periodically from a device.

In this way, the status information of the edge device is continuously updated to ensure that the update data required by the edge device is provided.

According to an exemplary embodiment of the present application, receiving the update data for updating at least one edge device further includes: sending a data request for the update data to the database according to the hardware information and the data version, the database includes the update data, and receiving the update data sent from the database .

In this way, the update data corresponding to the edge device is requested.

According to another aspect of the embodiments of the present application, a method for updating a device is further provided, including: receiving a device-to-device communication model, and the device-to-device communication model is generated according to a device context of an edge device and an update request for updating the edge device, wherein The device-to-device communication model includes the connection relationship of the edge devices; the update order of the edge devices is determined according to the connection relationship, and the sending device that sends the update data that updates the edge devices to the edge devices, the sending device is another edge device or a content distribution network node; Send a data request for update data to the sending device according to the update order; receive the update data from the sending device; and deploy the update data on the edge device.

In this way, according to the device communication model, the sending device that sends the update device is determined, and the sending device is requested to update the data to update the edge device, which relieves the pressure of the cloud server to transmit data.

According to an exemplary embodiment of the present application, the method further includes: generating a device capability model, the device capability model including hardware information and data versions of the edge device; and sending the device capability model to the content distribution network node, wherein the update data is based on the edge The hardware information and data version of the device are determined.

In this way, the state of the edge device is kept finer to provide the correct updates.

According to another aspect of the embodiments of the present application, a content distribution network node device is further provided, including: a model receiving unit configured to receive a device capability model, where the device capability model includes hardware information and data versions of at least one edge device; data receiving A unit configured to receive update data for updating at least one edge device according to hardware information and a data version; an update request receiving unit configured to receive update requests for updating at least one edge device; a context receiving unit configured to receive an edge device's Device context; a model generation unit configured to generate a device-to-device communication model according to an update request and a device context, and the device-to-device communication model includes connection relationships of edge devices to be updated; a model distribution unit to distribute the device-to-device communication model to The source synchronization device in the edge device to be updated. The source synchronization device is determined from the edge device to be updated according to the connection relationship; the synchronization request receiving unit is configured to receive a data request for sending updated data to the source synchronization device. The receiver is determined according to the connection relationship; and updating the distribution unit configured to transmit the update data to a data request to the source synchronous device.

In this way, receiving update data to update the edge device, determining the source synchronization device according to the device-to-device communication model, and sending the update data to the source synchronization device, alleviating the pressure of transmitting update data from the cloud server to the edge device.

According to another aspect of the embodiments of the present application, an edge device is further provided, including: a receiving unit configured to receive a device-to-device communication model, and the device-to-device communication model is based on a device context of the edge device and an update request to update the edge device Generated, where the device-to-device communication model includes the connection relationship of the edge device; the communication model execution unit is configured to determine the update order of the edge device according to the connection relationship and send the update data that updates the edge device to the sending device of the edge device, sending The device is another edge device or a content distribution network node; the update request sending unit is configured to send a data request for the update data to the sending device according to the update order; the update data receiving unit is configured to receive the update data from the sending device; and A data deployment unit configured to deploy updated data on an edge device.

In this way, according to the device communication model, the sending device that sends the update device is determined, and the sending device is requested to update the data to update the edge device, which relieves the pressure of the cloud server to transmit data.

According to an exemplary embodiment of the present application, the edge device further includes: a device capability model generating unit configured to generate a device capability model, the device capability model including hardware information and data versions of the edge device; and a device capability model sending unit configured to To send a device capability model to a content distribution network node, where the update data is determined based on the hardware information and data version of the edge device.

In this way, the state of the edge device is kept finer to provide the correct updates.

According to another aspect of the embodiments of the present application, a data update system is further provided, including: at least one edge device; a remote update center configured to manage updates of the edge device; a database configured to store data for updating the edge device; and The content distribution network node device includes: a model receiving unit configured to receive a device capability model, the device capability model including hardware information and a data version of at least one edge device; and a data receiving unit configured to receive an update according to the hardware information and the data version Update data of at least one edge device; an update request receiving unit configured to receive an update request to update at least one edge device; a context receiving unit configured to receive a device context of the edge device; a model generating unit configured to receive the update request according to the update request Generate a device-to-device communication model with the device context. The device-to-device communication model includes the connection relationship of the edge device to be updated. The model distribution unit distributes the device-to-device communication model to the source synchronization device in the edge device to be updated. The synchronization device is determined from the edge device to be updated according to the connection relationship; the synchronization request receiving unit is configured to receive a data request for sending update data to the source synchronization device, and the receiver of the data request is determined according to the connection relationship; and the update The distribution unit is configured to send the update data to the source synchronization device according to the data request.

In this way, receiving update data to update the edge device, determining the source synchronization device according to the device-to-device communication model, and sending the update data to the source synchronization device, alleviating the pressure of transmitting update data from the cloud server to the edge device.

According to an exemplary embodiment of the present application, the edge device includes: a receiving unit configured to receive a device-to-device communication model, and the device-to-device communication model is generated according to a device context of the edge device and an update request to update the edge device, wherein, The device-to-device communication model includes the connection relationship of the edge devices; the communication model execution unit is configured to determine the update order of the edge devices according to the connection relationship and to send the update data that updates the edge device to the sending device of the edge device, and the sending device is another edge device Or a content distribution network node; an update request sending unit configured to send a data request for update data to a sending device according to an update sequence; an update data receiving unit configured to receive update data from the sending device; and a data deployment unit, Configured to deploy updated data on edge devices.

In this way, according to the device communication model, the sending device that sends the update device is determined, and the sending device is requested to update the data to update the edge device, which relieves the pressure of the cloud server to transmit data.

According to another aspect of the embodiments of the present application, a storage medium is also provided, and the storage medium includes a stored program, wherein, when the program runs, the device where the storage medium is located is controlled to execute any of the foregoing methods.

According to another aspect of the embodiments of the present application, a processor is further provided. The processor is configured to run a program, and the method executes any of the foregoing methods when the program is run.

According to another aspect of the embodiments of the present application, a terminal is further provided, including: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to Executed by one or more processors, and one or more programs include a method for performing any of the above.

According to another aspect of the embodiments of the present application, a computer program product is also provided. The computer program product is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, cause at least one processor The method of performing any of the above.

In this way, the technical solution of the present application is implemented in the form of a program to alleviate the pressure of data transmission when updating edge devices in the Internet of Things.

In the embodiment of the present application, a technical solution is provided for sensing a device context and automatically generating a device-to-device communication model, and adopting a content distribution network for distributed remote updating of a large number of IoT devices in order to solve at least the data between the cloud server and the edge device The technical problem of high transmission pressure realizes the technical effects of distributed transmission and control data communication, reducing the bandwidth usage of cloud servers and improving the update speed of edge devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described here are used to provide a further understanding of the present application and constitute a part of the present application. The schematic embodiments of the present application and the description thereof are used to explain the present application, and do not constitute an improper limitation on the present application. In the drawings:

FIG. 1 is a schematic diagram of a data update system according to an embodiment of the present application.

2 is a block diagram of a content distribution network node device according to an embodiment of the present application;

3 is a block diagram of an edge device according to an embodiment of the present application;

4 is a flowchart of a method for sending update data according to an embodiment of the present application;

5 is a flowchart of a method for updating a device according to an embodiment of the present application;

6 is a schematic diagram of a device-to-device communication model according to an exemplary embodiment of the present application;

7 is a schematic diagram of data interaction in a data update system according to an exemplary embodiment of the present application;

8 is a schematic diagram of an interaction between a content distribution node and a source device according to an exemplary embodiment of the present application;

FIG. 9 is a schematic diagram of an interaction between a source device and a target device according to an exemplary embodiment of the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

1. Data update system;

10. Remote update center;

101. Remote update management module;

103. Event generation and triggering module;

30. Content distribution network node device;

301, a model receiving unit;

303: Data receiving unit;

305. The update request receiving unit.

307. The context receiving unit.

309: Model generation unit;

311, a model distribution unit;

313: The synchronization request receiving unit;

315: Update the distribution unit.

50, 50a, 50b, 50c, 50d, edge devices,

501, a receiving unit;

503. The communication model execution unit.

505. An update request sending unit.

507: Update the data receiving unit.

509, a data deployment unit;

511: Equipment capability model generation unit;

513, a device capability model sending unit;

70, the database;

S101-S115, steps;

S201-S213, steps;

FW, firmware;

SW, software;

30-1, 30-2, content distribution network node equipment;

50-1 ～ 50-6, edge equipment;

91 ~ 96, interactive process.

30-1a, the event receiver of the node;

30-1b, content synchronization and cache module;

30-1c, device content learning module;

30-1d, device-to-device communication model generation and notification module;

50-1a, 50-2a, equipment capability model and context report module;

50-1b, 50-2b, event receivers for edge devices;

50-1c, 50-2c, device-to-device communication model execution module;

50-1d, 50-2d, content synchronization and cache module;

50-1e, 50-2e, firmware / software deployment module.

detailed description

In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only Examples are part of this application, but not all examples. Based on the embodiments in this application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts should fall within the protection scope of this application.

It should be noted that the terms “first” and “second” in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data so used may be interchanged where appropriate so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. Furthermore, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or modules or units need not be limited to clearly listed Those steps or modules or units may include other steps or modules or units not explicitly listed or inherent to these processes, methods, products, or equipment.

According to an embodiment of the present application, a data update system is provided. FIG. 1 is a schematic diagram of a data update system according to an embodiment of the present application. As shown in FIG. 1, a data update system 1 according to an embodiment of the present application includes: at least one edge device 50, a remote update center 10, a database 70, and a content distribution network node device 30. The remote update center 10 is configured to manage updates of the edge device 50. Specifically, the remote update center 10 is used for remote update management and event generation and triggering. Regarding remote update management, the remote update center 10 provides a user interface to the user, and the user can interact with it to manage devices and updates. The user can decide which firmware / software to update which device. Regarding time generation and triggering, the remote update center 10 generates update events and information, and sends a notification to the content distribution network node device 30. The database 70 is configured to store data that updates the edge device 50. Specifically, the database 70 provides a synchronization service of firmware and software for requesting, inserting, uploading, and downloading firmware and software. The content distribution network node device 30 includes a model receiving unit 301 configured to receive a device capability model. The device capability model includes hardware information and data versions of at least one edge device 50. The model receiving unit 301 can receive the device capability model of the edge device 50. And dynamically update, organize, and store the context (environment) of the edge device 50, and also provide analysis for the model generation unit 309; the data receiving unit 303 is configured to receive updates that update at least one edge device 50 according to the hardware information and data version Data for synchronizing content and cache; an update request receiving unit 305 configured to receive an update request to update at least one edge device 50, such as receiving update events and information; a context receiving unit 307 configured to receive a device of the edge device 50 Context; a model generation unit 309 configured to generate a device-to-device communication model according to an update request and a device context, and the device-to-device communication model includes a connection relationship of an edge device 50 to be updated; and a model distribution unit 311 to convert the device-to-device communication model Distribute to The source synchronization device in the updated edge device 50 is determined from the edge device 50 to be updated according to the connection relationship; the synchronization request receiving unit 313 is configured to receive a data request for sending updated data to the source synchronization device, The receiver of the data request is determined according to the connection relationship; and the update distribution unit 315 is configured to send the update data to the source synchronization device according to the data request. In this way, receiving update data to update the edge device, determining the source synchronization device according to the device-to-device communication model, and sending the update data to the source synchronization device, alleviating the pressure of transmitting update data from the cloud server to the edge device.

According to an exemplary embodiment of the present application, the edge device 50 includes: a receiving unit 501 configured to receive a device-to-device communication model, and the device-to-device communication model is generated according to a device context of the edge device 50 and an update request to update the edge device Wherein, the device-to-device communication model includes the connection relationship of the edge device 50; the communication model execution unit 503 is configured to determine the update order of the edge device and send the update data updating the edge device 50 to the sending device of the edge device 50 according to the connection relationship. The sending device is another edge device 50 or a content distribution network node 30; the update request sending unit 505 is configured to send a data request for update data to the sending device according to the update order; the update data receiving unit 509 is configured to send The device receives the update data; and a data deployment unit configured to deploy the update data on the edge device 50. In this way, according to the device communication model, the sending device that sends the update device is determined, and the sending device is requested to update the data to update the edge device, which relieves the pressure of the cloud server to transmit data.

According to another embodiment of the embodiments of the present application, a content distribution network node device 30 is also provided. FIG. 2 is a block diagram of a content distribution network node device according to an embodiment of the present application. As shown in FIG. 2, the content distribution network node device 30 according to the embodiment of the present application includes a model receiving unit 301 configured to receive a device capability model, where the device capability model includes hardware information and data versions of at least one edge device. The data receiving unit 303 is configured to receive update data that updates at least one edge device according to the hardware information and the data version. The update request receiving unit 305 is configured to receive an update request to update at least one edge device. The context receiving unit 307 is configured to receive a device context of an edge device. The model generating unit 309 is configured to generate a device-to-device communication model according to an update request and a device context, and the device-to-device communication model includes a connection relationship of an edge device to be updated. The model distribution unit 311 distributes the device-to-device communication model to the source synchronization device in the edge device to be updated, and the source synchronization device is determined from the edge device to be updated according to the connection relationship. The synchronization request receiving unit 313 is configured to receive a data request for sending update data to a source synchronization device, and a receiver of the data request is determined according to a connection relationship. And the update distribution unit 315 is configured to send the update data to the source synchronization device according to the data request. In this way, receiving update data for updating the edge device, determining the source synchronization device according to the device-to-device communication model, and sending the update data to the source synchronization device, alleviating the pressure of transmitting update data from the cloud server to the edge device.

According to an embodiment of the present application, an edge device is also provided. FIG. 3 is a block diagram of an edge device according to an embodiment of the present application. As shown in FIG. 3, the edge device 50 according to the embodiment of the present application includes: a receiving unit 501 configured to receive a device-to-device communication model. The device-to-device communication model is based on the device context of the edge device and an update request to update the edge device. Generated, wherein the device-to-device communication model includes the connection relationship of the edge devices; the communication model execution unit 503 is configured to determine the update order of the edge devices according to the connection relationship and send the update data to update the edge device to the sending device of the edge device, The sending device is another edge device or a content distribution network node. The communication model execution unit 503 analyzes the device-to-device communication model and makes a decision on the update order of the edge device 50, such as where the edge device 50 itself is in the update sequence, and from Which device receives what update data; the update request sending unit 505 is configured to send a data request for the update data to the sending device according to the update order; the update data receiving unit 507 is configured to receive the update data from the sending device, such as from content distribution Network Festival The point or other edge device 50 receives the update data; and the data deployment unit 509 is configured to deploy the update data on the edge device 50, for example, install updated firmware, software, or an application runtime to run the application on the edge device 50 . In this way, according to the device communication model, the sending device that sends the update device is determined, and the sending device is requested to update the data to update the edge device, which relieves the pressure of the cloud server to transmit data.

According to the exemplary embodiment of the present application, the edge device 50 further includes: a device capability model generating unit 511 configured to generate a device capability model, the device capability model including hardware information and data versions of the edge device; and a device capability model sending unit 513 Is configured to send the device capability model to the content distribution network node, and the device capability model sending unit 513 periodically sends the device capability model to the content distribution network node, where the update data is determined according to the hardware information and data version of the edge device. In this way, the state of the edge device is kept finer to provide the correct updates.

An exemplary embodiment according to the present application shows a manner of data interaction in an update system. FIG. 7 is a schematic diagram of data interaction in a data update system according to an exemplary embodiment of the present application. In FIG. 7, an architecture divided into a cloud layer, a content distribution network layer, and a field device layer is shown from top to bottom. Data interaction. The cloud platform of the cloud layer includes a remote update center 10 and a database 70. The database 70 stores firmware FW and software SW required for the update, and may also include other system data. In the middle layer-the content distribution network layer includes a DNS server, a content distribution network node device 30-1, and a content distribution network node device 30-2. Only two content distribution network node devices are shown here. Depending on the actual system environment, there may be more Multi-content distribution network node device. For example, the content distribution network node device 30-1 represents the content distribution network node device in the first city, and the content distribution network node device 30-2 represents the content distribution network node device in the second city. Each edge device (field device) 50-1 to 50-6 is arranged in the bottom layer-field device layer. These edge devices are only exemplarily shown in this example, and there may be more or fewer edge devices according to the actual system environment. For example, the edge devices 50-1, 50-2, and 50-3 are field devices, such as various production equipment, instruments, terminals, and the like, which are set in factories in the first city. The edge devices 50-4, 50-5, and 50-6 are field devices installed in a factory in a second city.

The interactive process of updating the firmware and software is shown in the interactive processes 91 to 96 in FIG. 7. Taking the edge device in the factory in the first city as an example, the edge device 50-1 sends a device context report to the content distribution network node device 30-1 in the first city, which includes a device capability model (interaction process 91), and the content distribution network The node device 30-1 synchronizes the firmware FW / software SW determined according to the device capability model from the database 70 (interaction process 92). The remote update center 10 sends an update trigger event (interaction process 93) to the content distribution network node device 30-1. The update trigger event may be sent according to a user operation. The content distribution network node device 30-1 will The device communication model is distributed to the various edge devices involved in the update (interaction process 94). In this example, the edge device 50-1 analyzes the device-to-device communication model and determines itself as the source device, that is, the device that receives the firmware FW / software SW from the content distribution network node device 30-1, and the edge device 50-1 distributes the content The network node device 30-1 requests to receive the firmware FW / software SW, and the content distribution network node device 30-1 sends the firmware FW / software SW to the edge device 50-1 (interaction process 95). The edge device 50-1 uses the received firmware FW / software SW to perform the update operation. Firmware FW / software SW can be passed between edge devices for updates. The edge device 50-1 can send the firmware FW / software SW to other edge devices 50-2 (interaction process 96), or the edge device 50-3 can send the firmware FW / software SW to other edge devices 50-2 (edge devices The firmware FW / software SW can also be transmitted between each other to update the firmware and software of other edge devices. Similarly, for the content distribution network node device 30-2 in the second city, it can send the firmware FW / software SW to the edge device 50-4, and the edge device 50-4 can further send the firmware FW / software SW to other edge devices. 50-5 and edge device 50-6 to update firmware and software.

The following further illustrates the interaction between the content distribution node and the source device according to an exemplary embodiment of the present application. FIG. 8 is a schematic diagram of an interaction between a content distribution node and a source device according to an exemplary embodiment of the present application. As shown in FIG. 8, it shows a process in which the edge device 50-1 as a source device obtains firmware / software from the content distribution network node device 30-1 and updates it.

The device capability model and context report module 50-1a of the edge device 50-1 sends the device context report, including the device capability model and device context, to the device content acquisition module 30-1c of the content distribution network node device 30-1 in the first city (Interaction Process 91). The content synchronization and cache module 30-1b of the content distribution network node device 30-1 synchronizes the firmware FW / software SW determined according to the device capability model from the database 70 (interaction process 92). The remote update center 10 sends an update trigger event (interaction process 93 in FIG. 7) to the content distribution network node device 30-1, which is specifically divided into an interaction process 93-1 and an interaction process 93-2. The remote update management module 101 in the remote update center 10 generates an update status and sends it to the event generation and triggering module 103 (interaction process 93-1), and the event generation and triggering module 103 distributes events of the nodes of the network node device 30-1 to the content The receiver 30-1a sends an update trigger event (interaction process 93-2). The content distribution network node device 30-1 distributes the device-to-device communication model generated according to the device context to each edge device involved in the update. In this example, the edge device 50-1 is shown (interaction process 94). Interactive process 94-1, interactive process 94-2, interactive process 94-3, and interactive process 94-4. After the event receiver 30-1a of the node receives the update trigger event of the edge device, the device-to-device communication model generation and notification module 30-1d starts to generate the device-to-device communication model (interaction process 94-1). The device-to-device communication model generation and notification module 30-1d interacts with the device content acquisition module 30-1c to analyze the device context (interaction process 94-2), and generates a device-to-device communication model (interaction process 94-3), and sends the device To the device communication model to the event receiver 50-1b of the edge device (interaction process 94-4). The device-to-device communication model execution module 50-1c executes the device-to-device communication model (interaction process 95-1), the content synchronization and caching module 50-1d from the content synchronization and caching module 30-1b of the content distribution network node device 30-1 Update the data synchronously, for example, firmware / software (interaction process 95-2), and the firmware / software deployment module 50-1e of the edge device 50-1 deploys the updated data (interaction process 95-3).

An exemplary embodiment according to the present application also illustrates interaction between a source device and a target device. FIG. 9 is a schematic diagram of an interaction between a source device and a target device according to an exemplary embodiment of the present application. As shown in FIG. 9, some modules of the content distribution network node device 30-1, an edge device 50-1 as a source device, and an edge device 50-2 as a target device are shown. In the exemplary embodiment according to the present application, the edge device 50-2 as the target device can communicate with the edge device 50-1 as the source device to perform firmware / software update, which will be described in detail below.

In addition to the content distribution network node device 30-1 device-to-device communication model generation and notification module 30-1d shown in FIG. 8, the device-to-device communication model is sent to the event receiver 50-1b of the edge device 50-1 (interaction process 94-4), the device-to-device communication model execution module 50-1c executes the device-to-device communication model (interaction process 95-1), the content synchronization and cache module 50-1d from the content synchronization and content synchronization of the network node device 30-1 The cache module 30-1b updates the data synchronously (interaction process 95-2), and the firmware / software deployment module 50-1e of the edge device 50-1 deploys the updated data outside the edge device 50-1 (interaction process 95-3). The device-to-device communication model generation and notification module 30-1d of the content distribution network node device 30-1 also sends the device-to-device communication model to the event receiver 50-2b of the edge device 50-2 as the target device (interaction process 96- 1), the device-to-device communication model execution module 50-2c of the edge device 50-2 executes the device-to-device communication model (interaction process 96-2), and uses the content synchronization and cache module 50-2d -1 content synchronization and caching module 1d synchronizes the update content, such as firmware / software (interaction process 96-3), and the firmware / software deployment module 50-2e of the edge device 50-2 deploys updated data on the edge device 50-2 (interaction process 97). In this way, the edge device as the target device does not need to obtain update data from the content distribution network node, and can obtain update data from other edge devices for update operations.

According to an embodiment of the present application, a method for sending update data is provided. FIG. 4 is a flowchart of a method for sending update data according to an embodiment of the present application. As shown in FIG. 4, the method for sending updated data according to an embodiment of the present application includes: Step S101: Receive a device capability model, where the device capability model includes hardware information and data versions of at least one edge device. For example, the information included in the device capability model is hardware information such as CPU information, memory information, firmware information, application information, and updated data of the synchronization status of the device such as firmware version, synchronization process, application version and its synchronization status. Other examples of information included in the device capability model are: device name, IP address, CPU usage, memory usage, whether to allow device synchronization, and so on. Next, step S103 is performed to receive update data for updating at least one edge device according to the hardware information and the data version. The update data is data that updates data such as firmware, software, and applications, such as updating its version to a new version. Next, step S105 is performed to receive an update request to update at least one edge device. The update request is made by a user, for example, to trigger an event of updating the device. Next, step S107 is performed to receive the device context of the edge device. The device context (device context) reflects the environment and connection relationship where the device is located. Next, step S109 is performed to generate a device-to-device communication model according to the update request and the device context. The device-to-device communication model includes the connection relationship of the edge device to be updated. Next, step S111 is performed to distribute the device-to-device communication model to the source synchronization device in the edge device to be updated. The source synchronization device is determined from the edge device to be updated according to the connection relationship. For example, the source synchronization device is determined according to the optimized resource utilization mode. Sending update data to the source synchronization device and then sending it to other devices will optimize the utilization of communication resources, improve data transmission speed, and ease the cloud server. The pressure to transfer data to a large number of edge devices. Next, step S113 is performed to receive a data request for sending updated data to the source synchronization device. The receiver of the data request is determined according to the connection relationship. For example, the source synchronization device sends a data request to the content distribution node, which is determined according to the connection relationship to optimize the data transmission rate. Next, step S115 is performed to send the update data to the source synchronization device according to the data request. In this way, receiving update data to update the edge device, determining the source synchronization device according to the device-to-device communication model, and sending the update data to the source synchronization device, alleviating the pressure of transmitting update data from the cloud server to the edge device.

According to an exemplary embodiment of the present application, a device capability model is received periodically from a device. In this way, the status information of the edge device is continuously updated to ensure that the update data required by the edge device is provided.

According to an exemplary embodiment of the present application, receiving update data for updating at least one edge device further includes: sending a data request for update data to a database according to the hardware information and the data version, the database including the update data, and receiving the update data sent from the database . In this way, the update data corresponding to the edge device is requested.

According to another embodiment of the present application, a method for updating a device is also provided. FIG. 5 is a flowchart of a method for updating a device according to an embodiment of the present application. As shown in FIG. 5, a method for updating a device according to an embodiment of the present application includes: Step S201: Receive a device-to-device communication model, and the device-to-device communication model is generated according to a device context of an edge device and an update request to update the edge device. The device-to-device communication model includes the connection relationship of edge devices. Next, step S203 is performed to determine the update order of the edge device and the sending device that sends the update data of the updated edge device to the edge device according to the connection relationship. The sending device is another edge device or a content distribution network node. Next, step S205 is performed to send a data request for update data to the sending device according to the update order. Next, step S207 is performed to receive the update data from the transmitting device. Next, step S209 is performed to deploy the update data on the edge device. In this way, according to the device communication model, the sending device that sends the update device is determined, and the sending device is requested to update the data to update the edge device, which relieves the pressure of the cloud server to transmit data.

According to an exemplary embodiment of the present application, the method further includes: Step S211, generating a device capability model, where the device capability model includes hardware information and data versions of the edge device. And step S213, sending the device capability model to the content distribution network node, where the update data is determined according to the hardware information and data version of the edge device. For a specific edge device, determine the updated firmware, software, and applications that the edge device requires. In this way, the state of the edge device is kept finer to provide the correct updates.

The content distribution network node 30 analyzes the device context received from the edge device 50 and generates a device-to-device communication model. The goal of the device-to-device communication model is to optimize resource utilization. For example, if two edge devices 50 are in the same network, the two edge devices 50 may update firmware or software with each other, and the update process may be parallel. When considering resource allocation, resource consumption in the edge device 50 may also be considered. The device-to-device communication model will be sent to all edge devices 50 to be updated after generation. An example of a device-to-device communication model is also provided according to an exemplary embodiment of the present application. FIG. 6 is a schematic diagram of a device-to-device communication model according to an exemplary embodiment of the present application. As shown in FIG. 6, the content distribution network node 30 distributes the application 1 and the application 2 to the edge device 50 a, and distributes the application 3 and the application 4 to the edge device 50 b. The edge device 50 a and the edge device 50 b may use the slave content. The application program sent by the distribution network node 30 is updated. The edge device 50a can send the application 1 to the edge device 50b, the application 2 to the edge device 50c, and the edge device 50b can send the application 3 to the edge device 50c. The application 4 is sent to the edge device 50d, and the edge device 50c can send the application 2 to the edge device 50d, and each edge device can pass the application in any of these ways to implement the update. After receiving the device-to-device communication model, the edge device will determine the order of updating firmware and software. First, the data of the updated firmware and software is transmitted to the content distribution network node 30. The edge device can receive the update data from the content distribution network node. Or you can receive updated data from other edge devices. For example, if the edge device 50a has the application 1, if the network connection quality between the edge device 50a and the edge device 50b is high, the edge device 50b can obtain the application 1 from the edge device 50a.

According to another aspect of the embodiments of the present application, a storage medium is also provided, where the storage medium includes a stored program, and when the program runs, the device where the storage medium is located is controlled to execute the foregoing method.

According to another aspect of the embodiments of the present application, a processor is further provided. The processor is configured to run a program, and the method is executed when the program is run.

According to another aspect of the embodiments of the present application, a terminal is further provided, including: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to Executed by one or more processors, and one or more programs are included to perform the above method.

According to another aspect of the embodiments of the present application, a computer program product is also provided. The computer program product is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, cause at least one processor Perform the above method.

In this way, the technical solution of the present application is implemented in the form of a program to alleviate the pressure of data transmission when updating edge devices in the Internet of Things.

In the above embodiments of the present application, the description of each embodiment has its own emphasis. For a part that is not described in detail in an embodiment, reference may be made to the related description of other embodiments.

The technical solution of this application adopts distributed transmission and control, which can reduce the traffic and bandwidth occupancy of the cloud server side, and automatically generate the communication model of the content distribution network nodes and devices. The remote update is more efficient and optimized, and achieves scalability Management of a large number of edge devices without increasing the load on the cloud server side.

In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the unit or module is only a logical function division. In actual implementation, there may be another division manner, such as multiple units or modules or components. It can be combined or integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, modules or units, and may be electrical or other forms.

The units or modules described as separate components may or may not be physically separated, and the components displayed as units or modules may or may not be physical units or modules, which may be located in one place, or may be distributed to On multiple network elements or modules. Some or all of the units or modules may be selected according to actual needs to achieve the objective of the solution of this embodiment.

In addition, each functional unit or module in each embodiment of the present application may be integrated into one processing unit or module, or each unit or module may exist separately physically, or two or more units or modules may be integrated into one Unit or module. The above-mentioned integrated unit or module can be implemented in the form of hardware or in the form of software functional unit or module.

When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium. , Including a number of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage media include: U disks, Read-Only Memory (ROM), Random Access Memory (RAM), mobile hard disks, magnetic disks, or optical disks, and other media that can store program codes .

The above is only the preferred implementation of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principles of the present application, several improvements and retouches can be made. These improvements and retouches also It should be regarded as the protection scope of this application.

Claims (14)

The method for sending updated data includes: Receiving a device capability model, where the device capability model includes hardware information and data versions of at least one edge device; Receiving update data that updates at least one of the edge devices according to the hardware information and the data version; Receiving an update request to update at least one of the edge devices; Receiving a device context of the edge device; Generating a device-to-device communication model according to the update request and the device context, where the device-to-device communication model includes a connection relationship of the edge device to be updated; Distributing the device-to-device communication model to a source synchronization device in the edge device to be updated, the source synchronization device being determined from the edge device to be updated according to the connection relationship; Receiving a data request for sending the update data to the source synchronization device, and a receiver of the data request is determined according to the connection relationship; and Sending the update data to the source synchronization device according to the data request. The method of claim 1, wherein the device capability model is received periodically from the device. The method according to claim 1 or 2, wherein receiving update data for updating at least one of the edge devices further comprises: Sending a data request for the update data to a database according to the hardware information and data version, the database including the update data, and Receiving the update data sent from the database. The method for updating equipment is characterized by including: Receiving a device-to-device communication model that is generated according to a device context of an edge device and an update request to update the edge device, wherein the device communication model includes a connection relationship of the edge device; Determining an update sequence of the edge device and sending update data for updating the edge device to a sending device of the edge device according to the connection relationship, where the sending device is another edge device or a content distribution network node; Sending a data request for the update data to the sending device according to the update sequence; Receiving the update data from the transmitting device; and Deploying the update data on the edge device. The method according to claim 4, further comprising: Generating a device capability model that includes hardware information and data versions of the edge devices; and Sending the device capability model to the content distribution network node, wherein the update data is determined according to hardware information and a data version of the edge device. The content distribution network node device (30) is characterized in that it includes: The model receiving unit (301) is configured to receive a device capability model, where the device capability model includes hardware information and data versions of at least one edge device; A data receiving unit (303) configured to receive update data that updates at least one of the edge devices according to the hardware information and the data version; An update request receiving unit (305) configured to receive an update request to update at least one of the edge devices; A context receiving unit (307) configured to receive a device context of the edge device; A model generating unit (309) configured to generate a device-to-device communication model according to the update request and the device context, where the device-to-device communication model includes a connection relationship of the edge device to be updated; A model distribution unit (311), which distributes the device-to-device communication model to a source synchronization device in the edge device to be updated, where the source synchronization device is from the edge device to be updated according to the connection relationship definite; A synchronization request receiving unit (313) configured to receive a data request for sending the update data to the source synchronization device, and a receiver of the data request is determined according to the connection relationship; and An update distribution unit (315) is configured to send the update data to the source synchronization device according to the data request. The edge device (50) is characterized in that it includes: The receiving unit (501) is configured to receive a device-to-device communication model, the device-to-device communication model is generated according to a device context of the edge device and an update request to update the edge device, wherein the device communication The model includes a connection relationship of the edge devices; A communication model execution unit (503) configured to determine an update order of the edge device and send update data to update the edge device to a sending device of the edge device according to the connection relationship, where the sending device is another edge device Device or content distribution network node; An update request sending unit (505) configured to send a data request for the update data to the sending device according to the update sequence; An update data receiving unit (507) configured to receive the update data from the transmitting device; and A data deployment unit (509) is configured to deploy the update data on the edge device. The edge device (50) according to claim 7, further comprising: A device capability model generating unit (511) configured to generate a device capability model, the device capability model including hardware information and data versions of the edge devices; and A device capability model sending unit (513) is configured to send the device capability model to the content distribution network node, wherein the update data is determined according to hardware information and a data version of the edge device. A data updating system (1), characterized in that it includes: At least one edge device (50); A remote update center (10) configured to manage updates of the edge device; A database (70) configured to store data that updates the edge device; and Content distribution network node device (30), including: The model receiving unit (301) is configured to receive a device capability model, where the device capability model includes hardware information and data versions of at least one edge device; A data receiving unit (303) configured to receive update data that updates at least one of the edge devices according to the hardware information and the data version; An update request receiving unit (305) configured to receive an update request to update at least one of the edge devices; A context receiving unit (307) configured to receive a device context of the edge device; A model generating unit (309) configured to generate a device-to-device communication model according to the update request and the device context, where the device-to-device communication model includes a connection relationship of the edge device to be updated; A model distribution unit (311), which distributes the device-to-device communication model to a source synchronization device in the edge device to be updated, where the source synchronization device is from the edge device to be updated according to the connection relationship definite; A synchronization request receiving unit (313) configured to receive a data request for sending the update data to the source synchronization device, and a receiver of the data request is determined according to the connection relationship; and An update distribution unit (315) is configured to send the update data to the source synchronization device according to the data request. The data update system (1) according to claim 9, wherein the edge device (50) comprises: The receiving unit (501) is configured to receive a device-to-device communication model, the device-to-device communication model is generated according to a device context of the edge device and an update request to update the edge device, wherein the device communication The model includes a connection relationship of the edge devices; A communication model execution unit (503) configured to determine an update order of the edge device and send update data to update the edge device to a sending device of the edge device according to the connection relationship, where the sending device is another edge device Device or content distribution network node; An update request sending unit (505) configured to send a data request for the update data to the sending device according to the update sequence; An update data receiving unit (507) configured to receive the update data from the transmitting device; and A data deployment unit (509) is configured to deploy the update data on the edge device. The storage medium is characterized in that the storage medium includes a stored program, wherein, when the program runs, the device where the storage medium is located is controlled to perform the method according to any one of claims 1 to 5. A processor, wherein the processor is configured to run a program, and when the program runs, the method according to any one of claims 1 to 5 is executed. A terminal includes: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors Execution, the one or more programs include a method for performing any one of claims 1 to 5. A computer program product tangibly stored on a computer-readable medium and including computer-executable instructions that, when executed, cause at least one processor to perform any of claims 1 to 5 The method of one item.

Images