CN113656423A

CN113656423A - Method and device for updating data, electronic equipment and storage medium

Info

Publication number: CN113656423A
Application number: CN202110948072.9A
Authority: CN
Inventors: 韩鹏飞
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2021-08-18
Filing date: 2021-08-18
Publication date: 2021-11-16

Abstract

The disclosure provides a method and device for updating data, electronic equipment and a storage medium, and relates to the technical field of computers, in particular to the technical field of cloud computing and the Internet of things. The implementation scheme is as follows: receiving a data updating task, wherein the data updating task comprises an identifier of target data to be updated, and the target data corresponds to at least one target device; determining a target queue corresponding to a data updating task from at least one task queue according to the identification of the target data; adding a data updating task to the tail of the target queue; and in response to the data update task moving to the head of the target queue, sending the data update task to the task execution unit so that the task execution unit executes the data update task to update the target data in the at least one target device.

Description

Method and device for updating data, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to the field of cloud computing and internet of things technologies, and in particular, to a method and an apparatus for updating data, an electronic device, a computer-readable storage medium, and a computer program product.

Background

Cloud computing (cloud computing) refers to a technology architecture that accesses a flexibly extensible shared physical or virtual resource pool through a network, where resources may include servers, operating systems, networks, software, applications, storage devices, and the like, and may be deployed and managed in an on-demand, self-service manner. Through the cloud computing technology, high-efficiency and strong data processing capacity can be provided for technical application and model training of artificial intelligence, block chains and the like.

With the introduction of the Internet of Things (IoE) concept, the Internet of Things (IoT) device is becoming the center of data production. In addition, the internet of things equipment has dispersibility in geographic positions and has higher requirements on response time and data security, so that data calculation in the field of internet of things is gradually closed from cloud calculation to edge calculation.

The approaches described in this section are not necessarily approaches that have been previously conceived or pursued. Unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Similarly, unless otherwise indicated, the problems mentioned in this section should not be considered as having been acknowledged in any prior art.

Disclosure of Invention

The present disclosure provides a method, an apparatus, an electronic device, a computer-readable storage medium, and a computer program product for updating data.

According to an aspect of the present disclosure, there is provided a method of updating data, including: receiving a data updating task, wherein the data updating task comprises an identifier of target data to be updated, and the target data corresponds to at least one target device; determining a target queue corresponding to the data updating task from at least one task queue according to the identification of the target data; adding the data update task to the tail of the target queue; and responding to the data updating task moving to the head of the target queue, and sending the data updating task to a task execution unit, so that the task execution unit executes the data updating task to update target data in the at least one target device.

According to another aspect of the present disclosure, there is provided a method of updating data, including: the method comprises the steps that a data updating task to be executed is obtained from the head of a target queue, the data updating task to be executed comprises an identifier of target data to be updated, the target data correspond to at least one target device, the target queue is one of at least one task queue, and a plurality of data updating tasks used for updating the same data are added into the same task queue according to an execution sequence; and executing the data updating task to be executed so as to update the target data in the at least one target device.

According to another aspect of the present disclosure, there is provided an apparatus for updating data, including: a task receiving module configured to receive a data update task, the data update task including an identification of target data to be updated, the target data corresponding to at least one target device; the queue determining module is configured to determine a target queue corresponding to the data updating task from at least one task queue according to the identification of the target data; a task adding module configured to add the data update task to the tail of the target queue; and the task sending module is configured to respond to the data updating task moving to the head of the target queue, and send the data updating task to the task execution unit, so that the task execution unit executes the data updating task to update the target data in the at least one target device.

According to another aspect of the present disclosure, there is provided an apparatus for updating data, including: the task obtaining module is configured to obtain a data updating task to be executed from the head of a target queue, where the data updating task to be executed includes an identifier of target data to be updated, the target data corresponds to at least one target device, the target queue is one of at least one task queue, and multiple data updating tasks for updating the same data are added to the same task queue according to an execution sequence; and the task execution module is configured to execute the data updating task to be executed so as to update the target data in the at least one target device.

According to another aspect of the present disclosure, there is provided an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any of the above aspects.

According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any of the above aspects.

According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein the computer program realizes the method of any of the above aspects when executed by a processor.

According to one or more embodiments of the present disclosure, a target queue corresponding to a data update task is determined according to an identifier of target data, so that data update tasks for the same target data can be guaranteed to be stored in the same task queue and executed in order according to the queuing sequence, thereby implementing ordered update of the target data in a target device.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the embodiments and, together with the description, serve to explain the exemplary implementations of the embodiments. The illustrated embodiments are for purposes of illustration only and do not limit the scope of the claims. Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements.

FIG. 1 illustrates a schematic diagram of an exemplary system in which various methods described herein may be implemented, according to an embodiment of the present disclosure;

FIG. 2 shows a flow diagram of a method of updating data according to an embodiment of the present disclosure;

FIG. 3 shows a schematic diagram of types of data according to an embodiment of the present disclosure;

FIG. 4 shows a flow diagram of a method of updating data according to another embodiment of the present disclosure;

FIG. 5 shows a schematic diagram of a data update process according to an embodiment of the present disclosure;

FIG. 6 shows a block diagram of an apparatus for updating data according to an embodiment of the present disclosure;

FIG. 7 shows a block diagram of an apparatus for updating data according to another embodiment of the present disclosure; and

FIG. 8 illustrates a block diagram of an exemplary electronic device that can be used to implement embodiments of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In the present disclosure, unless otherwise specified, the use of the terms "first", "second", etc. to describe various elements is not intended to limit the positional relationship, the timing relationship, or the importance relationship of the elements, and such terms are used only to distinguish one element from another. In some examples, a first element and a second element may refer to the same instance of the element, and in some cases, based on the context, they may also refer to different instances.

The terminology used in the description of the various described examples in this disclosure is for the purpose of describing particular examples only and is not intended to be limiting. Unless the context clearly indicates otherwise, if the number of elements is not specifically limited, the elements may be one or more. Furthermore, the term "and/or" as used in this disclosure is intended to encompass any and all possible combinations of the listed items.

Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

Fig. 1 illustrates a schematic diagram of an exemplary system 100 in which various methods and apparatus described herein may be implemented in accordance with embodiments of the present disclosure. Referring to fig. 1, the system 100 includes one or

more client devices

101, 102, 103, 104, 105, and 106, one or more internet of

things devices

141, 142, 143, and 144, a server 120, and one or more communication networks 110. Communication network 110 is used to couple any two of one or more client devices, one or more internet of things devices, and server 120. The

client devices

101, 102, 103, 104, 105, and 106, and the internet of

things devices

141, 142, 143, 144 may be configured to execute one or more applications.

In embodiments of the present disclosure, the server 120 may run one or more services or software applications that enable the method of updating data to be performed such that the server 120 may receive and perform data update tasks submitted by users through the

client devices

101, 102, 103, 104, 105, and 106 to update data stored in the internet of

things devices

141, 142, 143, 144.

In some embodiments, the server 120 may also provide other services or software applications that may include non-virtual environments and virtual environments. In certain embodiments, these services may be provided as web-based services or cloud services, for example, provided to users of

client devices

101, 102, 103, 104, 105, and/or 106 under a software as a service (SaaS) model.

In the configuration shown in fig. 1, server 120 may include one or more components that implement the functions performed by server 120. These components may include software components, hardware components, or a combination thereof, which may be executed by one or more processors. A user operating a

client device

101, 102, 103, 104, 105, and/or 106 may, in turn, utilize one or more client applications to interact with the server 120 to take advantage of the services provided by these components. It should be understood that a variety of different system configurations are possible, which may differ from system 100. Accordingly, fig. 1 is one example of a system for implementing the various methods described herein and is not intended to be limiting.

The user may use the

client device

101, 102, 103, 104, 105, and/or 106 to manage or control the internet of

things device

141, 142, 143, 144, such as to view the operational status of the internet of things device, deploy applications into the internet of things device, and update, delete, etc. data stored in the internet of things device. It is to be appreciated that different client devices may manage or control different internet of things devices. The client device may provide an interface that enables a user of the client device to interact with the client device. The client device may also output information to the user via the interface. Although fig. 1 depicts only six client devices, those skilled in the art will appreciate that the present disclosure may support any variety and number of client devices.

Client devices

101, 102, 103, 104, 105, and/or 106 may include various types of computer devices, such as portable handheld devices, general purpose computers (such as personal computers and laptop computers), workstation computers, wearable devices, gaming systems, thin clients, various messaging devices, sensors or other sensing devices, and so forth. These computer devices may run various types and versions of software applications and operating systems, such as MICROSOFT Windows, APPLE iOS, UNIX-like operating systems, Linux, or Linux-like operating systems (e.g., GOOGLE Chrome OS); or include various Mobile operating systems such as MICROSOFT Windows Mobile OS, iOS, Windows Phone, Android. Portable handheld devices may include cellular telephones, smart phones, tablets, Personal Digital Assistants (PDAs), and the like. Wearable devices may include head mounted displays and other devices. The gaming system may include a variety of handheld gaming devices, internet-enabled gaming devices, and the like. The client device is capable of executing a variety of different applications, such as various Internet-related applications, communication applications (e.g., email applications), Short Message Service (SMS) applications, and may use a variety of communication protocols.

The internet of

things devices

141, 142, 143, 144 may include various types of computer devices. For example, the internet of things device may be a device such as an industrial personal computer, a gateway, a sensing device, a water pump, a fan, etc. in an industrial production scene, a device such as an on-board device, an electric vehicle charging pile, an intelligent street lamp, etc. in a city management scene, a smart traffic scene, a device such as an entrance guard, a camera, a smoke alarm, etc. in a building management scene, and a device such as an intelligent sound box, an intelligent curtain, an intelligent desk lamp, etc. in a household scene. These internet of things devices may run various types and versions of operating systems and software applications and may communicate with external devices through various wired or wireless communication protocols. Although fig. 1 depicts only four client devices, those skilled in the art will appreciate that the present disclosure may support any variety and number of client devices.

It should be noted that, for different application scenarios, the types and functions of the internet of

things devices

141, 142, 143, and 144 are different, and some internet of things devices may have functions of data acquisition, processing, and transmission. In the technical scheme of the disclosure, the processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the personal information of the related users all conform to the regulations of related laws and regulations and do not violate the good customs of the public order.

Network 110 may be any type of network known to those skilled in the art that may support data communications using any of a variety of available protocols, including but not limited to TCP/IP, SNA, IPX, etc. By way of example only, one or more networks 110 may be a Local Area Network (LAN), an ethernet-based network, a token ring, a Wide Area Network (WAN), the internet, a virtual network, a Virtual Private Network (VPN), an intranet, an extranet, a Public Switched Telephone Network (PSTN), an infrared network, a wireless network (e.g., bluetooth, Wi-Fi), and/or any combination of these and/or other networks.

The server 120 may include one or more general purpose computers, special purpose server computers (e.g., PC (personal computer) servers, UNIX servers, mid-end servers), blade servers, mainframe computers, server clusters, or any other suitable arrangement and/or combination. The server 120 may include one or more virtual machines running a virtual operating system, or other computing architecture involving virtualization (e.g., one or more flexible pools of logical storage that may be virtualized to maintain virtual storage for the server). In various embodiments, the server 120 may run one or more services or software applications that provide the functionality described below.

The computing units in server 120 may run one or more operating systems including any of the operating systems described above, as well as any commercially available server operating systems. The server 120 may also run any of a variety of additional server applications and/or middle tier applications, including HTTP servers, FTP servers, CGI servers, JAVA servers, database servers, and the like.

In some implementations, the server 120 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of the

client devices

101, 102, 103, 104, 105, and 106. Server 120 may also include one or more applications to display data feeds and/or real-time events via one or more display devices of

client devices

101, 102, 103, 104, 105, and 106.

In some embodiments, the server 120 may be a server of a distributed system, or a server incorporating a blockchain. The server 120 may also be a cloud server, or a smart cloud computing server or a smart cloud host with artificial intelligence technology. The cloud Server is a host product in a cloud computing service system, and is used for solving the defects of high management difficulty and weak service expansibility in the traditional physical host and Virtual Private Server (VPS) service.

The system 100 may also include one or more databases 130. In some embodiments, these databases may be used to store data and other information. For example, one or more of the databases 130 may be used to store information such as audio files and video files. The data store 130 may reside in various locations. For example, the data store used by the server 120 may be local to the server 120, or may be remote from the server 120 and may communicate with the server 120 via a network-based or dedicated connection. The data store 130 may be of different types. In certain embodiments, the data store used by the server 120 may be a database, such as a relational database. One or more of these databases may store, update, and retrieve data to and from the database in response to the command.

In some embodiments, one or more of the databases 130 may also be used by applications to store application data. The databases used by the application may be different types of databases, such as key-value stores, object stores, or regular stores supported by a file system.

The system 100 of fig. 1 may be configured and operated in various ways to enable application of the various methods and apparatus described in accordance with the present disclosure.

Various data, such as device description data and application data, are stored in the internet of

things devices

141, 142, 143, and 144. The device description data may include, for example, a name, a usage, factory time, a hardware configuration condition, and the like of the internet of things device, and the application data may include, for example, configuration information (e.g., a running environment of the application, a loaded file) and security information (e.g., a key, an HTTPS certificate, a mirror address, a mirror repository key), and the like of the application.

In the internet of things scenario, the server 120 typically manages a large number of internet of things devices, and some of the internet of things devices have the same functions and application deployments. In some cases, there may be a need for ordered updates of data in certain internet of things devices. For example, a certain application deployed in the internet of things device 1-the internet of things device 5 is upgraded from the version V1.0 to the version V2.0, and then the application is upgraded from the version V2.0 to the version V3.0.

In the related art, if a user wants to perform multiple ordered updates on the same kind of data in the internet of things device, he needs to submit multiple data update tasks (each corresponding to one data update) to the server 120 through the client device. In the case that the server 120 is a server cluster (i.e. there are multiple servers 120), multiple data update tasks for the same type of data may be allocated to different servers for execution, however, the execution environments and execution efficiencies of different servers are different, and the execution order of the multiple data update tasks cannot be guaranteed.

Therefore, the data updating method is provided to update the data in the internet of things equipment in order.

FIG. 2 shows a flow diagram of a method 100 of updating data according to an embodiment of the present disclosure. The method 200 may be executed in a server (e.g., the server 120 shown in fig. 1), that is, the execution subject of each step of the method 200 may be the server 120 shown in fig. 1. More specifically, the executing subject of the method 200 may be a message middleware system (Broker) deployed in a server, such as Redis, RabbitMQ, Celery, and the like.

As shown in fig. 2, the method 200 includes:

step 210, receiving a data updating task, where the data updating task includes an identifier of target data to be updated, and the target data corresponds to at least one target device;

step 220, determining a target queue corresponding to the data updating task from at least one task queue according to the identifier of the target device;

step 230, adding a data updating task to the tail of the target queue; and

step 240, in response to the data update task moving to the head of the target queue, sending the data update task to the task execution unit, so that the task execution unit executes the data update task to update the target data in the at least one target device.

According to the embodiment of the disclosure, the target queue corresponding to the data updating task is determined according to the identifier of the target data, so that the data updating tasks aiming at the same target data can be guaranteed to be stored in the same task queue and executed orderly according to the queuing sequence, and the ordered updating of the target data in the target equipment is realized.

The various steps of method 200 are described in detail below.

In step 210, a data update task is received, the data update task including an identification of target data to be updated, the target data corresponding to at least one target device.

In an embodiment of the present disclosure, the target data refers to data to be updated, and the target device refers to an internet of things device deployed with the target data.

Generally, the data update task is submitted by a user through a client device (e.g., the

client devices

101, 102, 103, 104, 105, and 106 shown in fig. 1) according to own needs, for example, the user modifies the code of the application 1(app1), and then the target data is app1, which accordingly needs to update the app1 in the target device (i.e., the internet of things device with app1 deployed).

In other embodiments, the data update task may also be initiated by the server 120. For example, application 1(app1) is deployed in a container manner in a target device, an image (image) of app1 is stored in server a, and when server a fails or hardware maintenance or upgrade is required, the image of app1 can be migrated to another server B, that is, the image address of app1 is updated, so that the server B provides an image service to the target device during the failure, maintenance or upgrade of server a. In this case, the target data is still app1, and accordingly an update of (the mirror address of) app1 in the target device is required.

The data update task includes an identification of target data to be updated. The identification of the target data is used to uniquely identify the target data, and may, for example, include only one field or a combination of fields.

According to some embodiments, the identification of the target data is a combination of an identification of a user submitting the data update task, a type of the target data, and a name of the target data. That is, the data update task submitted by the user through the client device includes the user's identification (namespace), the type of the target data to be updated (dataType), and the name of the target data (dataName), and the target data can be uniquely determined according to the user's identification, the type of the target data, and the name of the target data. Therefore, the target data is jointly identified through the identification of the user, the type of the target data and the name of the target data, and the naming spaces of different types of data of different users are mutually independent, namely, the names of the same type of data of the same user are different, but the same user can set the same data name for the different types of data, different users can set the same data name for the same type of data, and different users can set the same data name for the different types of data, so that the selectivity of the data name is improved, and the user can name the data conveniently. For example, application data (dataType app) deployed in an internet of things device managed by the user 1(namespace 1), and device description data (dataType node) deployed in an internet of things device managed by the user 1(namespace 1) may be named name1(dataName 1).

FIG. 3 shows a schematic diagram of types of data according to an embodiment of the disclosure. As shown in fig. 3, the types of data include device description data 310 and application data 320. The device description data 310 includes, for example, the name, usage, factory time, hardware configuration, etc. of the internet of things device. The application data may include, for example, configuration information 330 and security information 340 of the application, and the like. The configuration information 330 of the application includes the running environment of the application (e.g., CPU core number, memory capacity, etc.), and the security information of the application includes a key 342, a certificate 344 (e.g., HTTPS certificate), image information 346 (e.g., address of application image and image repository key), and so on.

According to further embodiments, the identification of the target data is a combination of an identification of a user submitting the data update task and a name of the target data. That is, the data update task submitted by the user through the client device includes the user's identifier (namespace) and the name (dataName) of the target data, and the target data can be uniquely determined according to the user's identifier and the name of the target data. Therefore, the target data is jointly identified through the identification of the user and the name of the target data, and the namespaces of different users are mutually independent, namely, the names of the data of the same user are different, but different users can set the same data name for different data.

According to further embodiments, the identification of the target data may also comprise only one field of the name of the target data. That is, the name of the target data is included in the data update task submitted by the user through the client device, and from this name, the target data can be uniquely determined. In this case, the data of different users share the same namespace, i.e., the names of the data of the same user are different and also different from the names of the data already existing by other users.

According to some embodiments, the data update task may further include an asynchronous tag to indicate whether the data update task is an asynchronous task.

It should be noted that, in the embodiments of the present disclosure, an asynchronous task refers to a task that is executed asynchronously. After the user submits the asynchronous task on the task submitting interface of the client device, the user can immediately receive a response message returned by the server, and then the user can close the current interface or perform other operations on the current interface without waiting for the execution result of the asynchronous task on line. Synchronous tasks refer to tasks that are executed synchronously. After the user submits the synchronous task, the user needs to wait for the execution result of the synchronous task on line, the current interface can not be operated during the waiting period, and the current interface can be operated only after the server returns the execution result of the synchronous task.

Asynchronous tags are typically specified by a user when submitting a data update task through a client device. After receiving the data update task submitted by the user through step 210, the server immediately returns a message that the data update task is completed to the client device in response to the asynchronous tag indicating that the data update task is an asynchronous task. The user can then perform other operations without waiting for the result of the execution of the data update task, thereby reducing the user's waiting time. It is to be understood that, although in this case, the user does not need to wait for the execution result of the data update task online, after the server obtains the execution result of the data update task, the execution result may be further returned to the client device, so that the user can know the execution condition (whether the execution is successful) of the data update task.

According to other embodiments, after receiving the data update task submitted by the user through step 210, the server does not immediately return a response message to the client device and needs to wait for the execution result of the data update task in response to the asynchronous tag indicating that the data update task is not an asynchronous task (i.e., is a synchronous task). And after receiving the execution result returned by the task execution unit, returning the execution result to the client.

In step 220, a target queue corresponding to the data update task is determined from the at least one task queue according to the identifier of the target data.

In the embodiment of the present disclosure, the task queue is a First-in First-out (FIFO) linear table, a head (front, or front) of which performs a delete operation, and a tail (tail, or rear) of which performs an add operation.

The number of task queues is preset by those skilled in the art. In order to save storage space and improve communication and execution efficiency, the number of task queues is not too large, and for example, the number of task queues may be set to 3.

According to some embodiments, in step 220, the identifier of the target data may be mapped to obtain a mapping value corresponding to the identifier of the target data; and taking the task queue corresponding to the mapping value as a target queue. For example, the number of the task queues is 3, the identifier of the target data may be a combination of the identifier of the user, the type of the target data, and the name of the target data, and accordingly, the identifier of the user, the type of the target data, and the name of the target data may be spliced, and then the splicing result is mapped (Hash) to obtain a corresponding mapping value. If the mapping value is 2, for example, then the second task queue is used as the target queue.

After the target queue is determined by step 220, step 230 is performed to add a data update task to the tail of the target queue.

The task execution unit acquires a task from the head of the target queue and executes the task. Each time the task execution unit executes to complete a task, the task is removed from the target queue and other tasks in the target queue are advanced. When the data update task moves to the head of the target queue, step 240 is executed, in response to the data update task moving to the head of the target queue, the data update task is sent to the task execution unit, so that the task execution unit executes the data update task to update the target data in the at least one target device.

The task execution unit (worker) is a service program for executing a data update task, and may be deployed in a server executing the method 200, or may be deployed in another server.

It should be noted that there may be a plurality of task execution units, but one task queue may be processed by only one task execution unit at the same time, so as to ensure the execution order of each task in the task queue.

In addition, it should be noted that, in step 240, in response to the data update task moving to the head of the target queue, the data update task is sent to the task execution unit, and specifically, the server (in the message middleware) may actively send the data update task at the head of the target queue to the currently idle task execution unit; or passively sending the data update task at the head of the target queue to the task execution unit in response to polling of the task execution unit.

According to some embodiments, the method 200 further comprises: and receiving and storing the execution result of the data updating task returned by the task execution unit in response to the asynchronous label indicating that the data updating task is not an asynchronous task. And further returning the execution result to the client device submitting the data updating task, and deleting the locally stored execution result.

According to another embodiment of the present disclosure, a method of updating data is also provided.

FIG. 4 shows a flow diagram of a method 400 of updating data according to another embodiment of the present disclosure. The method 400 may be performed in a server, which may be the server performing the method 200 or another server different from the server performing the method 200. More specifically, the execution subject of the method 400 may be a service program, i.e., a task execution unit (worker), deployed in a server and used for executing a data update task. There may be one or more task execution units, and each task execution unit may be an execution subject of the method 400 described below.

As shown in fig. 4, the method 400 includes:

step 410, obtaining a data update task to be executed from the head of a target queue, where the data update task to be executed includes an identifier of target data to be updated, the target data corresponds to at least one target device, and the target queue is one of at least one task queue, where multiple data update tasks for updating the same data are added to the same task queue according to an execution sequence; and

and step 420, executing the data updating task to be executed to update the target data in the at least one target device.

According to the embodiment of the disclosure, ordered updating of the target data can be realized.

According to some embodiments, the target queue may be determined by: polling at least one task queue to determine whether an unexecuted data updating task exists at the head of each task queue; and in response to the head of the current task queue having an unexecuted data update task, taking the current task queue as a target queue.

According to some embodiments, the data update task to be performed comprises at least one subtask. Accordingly, performing the data update task to be performed in step 420 includes: and sequentially executing the at least one subtask, and recording the execution result of each subtask when the execution of the subtask is completed, so that rollback and retry when the execution of the task fails are facilitated.

According to some embodiments, the data update task may be divided into a plurality of subtasks in advance, and a correspondence between the data update task and the subtasks is stored, where each subtask may be a function.

FIG. 5 shows a schematic diagram of a data update process according to an embodiment of the present disclosure. In the embodiment shown in fig. 5, the identification of the data is a combination of the identification of the user, the type of the data, and the name of the data.

As shown in fig. 5, three task queues, namely

task queues

530, 540, 550, are provided in message middleware 520. At an initial moment, the task queue 530 includes two data update tasks, which are

tasks

531 and 532 respectively; task queue 540 includes a data update task, namely task 541; the task queue 550 is empty.

Subsequently, the user 1(namespace 1) submits a data update task 511 for the application 1(dataType app, dataName app1) through the client device 501, the content of the data update task is to upgrade the container memory configuration of the application 1 from 200M to 500M, and the task is designated as an asynchronous task. After receiving the task 511, the message middleware 520 returns a message that the execution of the task 511 is completed to the client device 501. The message middleware 520 splices the user1, the app and the app1, and calculates a mapping value of a splicing result, so that the mapping value is 1. Accordingly, the first task queue, i.e., task queue 530, is used as the target queue, and the data update task 511 is added to the tail of the task queue 530.

After submitting the data update task 511, the user 1(namespace 1) submits a data update task 512 for the same application (i.e., dataType app, dataName app1) through the client device 501, the content of which is to upgrade the application 1 from version V1.0 to version V2.0, and designate the task as an asynchronous task. Upon receiving task 512, message middleware 520 returns a message to client device 501 that task 512 execution is complete. The message middleware 520 splices the user1, the app and the app1, and calculates a mapping value of a splicing result, so that the mapping value is 1. Accordingly, the first task queue, namely the task queue 530, is used as a target queue, and the data update task 512 is added to the tail of the task queue 530. It can be seen that the

data update tasks

511 and 512 submitted by the user1 twice for the same data are successively added to the same task queue, so that the two tasks can be executed successively according to the submission order.

The user 1(namespace 1) submits, through the client device 501, a data update task 513 for device description data 1(dataType, dataName, node1), the content of which is the name of the update device, and which is designated as an asynchronous task. After receiving the task 513, the message middleware 520 returns a message that the execution of the task 513 is completed to the client device 501. The message middleware 520 splices the user1, the node and the node1, and calculates the mapping value of the splicing result to obtain a mapping value of 2. Accordingly, the data update task 513 is added to the tail of the task queue 540 with the second task queue, namely the task queue 540, as the target queue.

User 2(namespace 2) submits, via the client device 502, a data update task 514 for application 2(dataType app, dataName app2) whose content is to upgrade application 2 from version V1.0 to version V2.0 and designate the task as a synchronization task. Since the task is a sync task, message middleware 520 does not immediately return a response message to client device 501. The message middleware 520 splices the user2, the app and the app2, and calculates a mapping value of a splicing result, so that the mapping value is 3. Accordingly, a third task queue, namely the task queue 550, is used as a target queue, and the data update task 514 is added to the tail of the task queue 550.

The task execution units 571, 572, 573 execute the data update task at the head of the task queue by polling the

task queues

530, 540, 550. As shown in fig. 5, the task execution units 571, 572, 573 currently execute the data update

tasks

531, 541, 514, respectively.

When executing the data update task, the task execution units 571, 572, and 573 may determine, according to a preset correspondence between data and devices, a target device corresponding to target data of the current data update task, and update the target data in the target device. And the task execution unit may execute the data updating task in units of subtasks according to a preset correspondence between the data updating task and the subtasks, and record an execution result of each subtask when the execution of the subtask is completed, so as to perform rollback and retry in case of a failure in the execution of the task. For example, as shown in fig. 5, the data update task 541 is divided into three sub-tasks 541A, 541B, and 541C, the task execution unit 572 sequentially executes the sub-tasks 541A, 541B, and 541C, and records the execution result of each sub-task when the execution of the sub-task is completed.

Since the data update task 514 is a synchronization task, the task execution unit 573 returns the execution result of the task 514 to the message middleware 520, and the message middleware 520 stores the execution result of the task 514 in the synchronization task state table (the data structure is Map, Key is the ID of the data update task, and Value is the execution result of the data update task). After returning the execution results to client device 502, message middleware 520 deletes the execution results of task 514 from the synchronized task state table.

According to an embodiment of the present disclosure, there is also provided an apparatus for updating data.

Fig. 6 shows a block diagram of an apparatus 600 for updating data according to an embodiment of the present disclosure. As shown in fig. 6, the apparatus 600 includes:

a task receiving module 610 configured to receive a data update task, the data update task including an identification of target data to be updated, the target data corresponding to at least one target device;

a queue determining module 620, configured to determine, according to the identifier of the target data, a target queue corresponding to the data update task from at least one task queue;

a task adding module 630 configured to add the data update task to the tail of the target queue; and

a task sending module 640 configured to send the data update task to a task execution unit in response to the data update task moving to the head of the target queue, so that the task execution unit executes the data update task to update target data in the at least one target device.

According to some embodiments, the identification of the target data is a combination of an identification of a user submitting the data update task, a type of the target data, and a name of the target data.

According to some embodiments, the queue determination module 620 comprises: the mapping unit is configured to map the identifier of the target data to obtain a mapping value corresponding to the identifier of the target data; and a queue determination unit configured to take a task queue corresponding to the mapping value as the target queue.

According to some embodiments, the data update task further comprises an asynchronous tag for indicating whether the data update task is an asynchronous task.

According to some embodiments, the data update task is submitted by a client device; the apparatus 600 further comprises: and the asynchronous response module is configured to respond to the asynchronous label indicating that the data updating task is an asynchronous task after receiving the data updating task, and return a message that the execution of the data updating task is completed to the client device.

According to some embodiments, the apparatus 600 further comprises: an execution result receiving module configured to receive and store the execution result of the data update task returned by the task execution unit in response to the asynchronous tag indicating that the data update task is not an asynchronous task.

According to some embodiments, the data update task is submitted by a client device; the apparatus 600 further comprises: a synchronization response module configured to return the execution result to the client device; and a deletion module configured to delete the stored execution result.

Fig. 7 shows a block diagram of an apparatus 700 for updating data according to an embodiment of the present disclosure. As shown in fig. 7, the apparatus 700 includes:

a task obtaining module 710 configured to obtain a data update task to be executed from a head of a target queue, where the data update task to be executed includes an identifier of target data to be updated, the target data corresponds to at least one target device, and the target queue is one of at least one task queue, where multiple data update tasks for updating the same data are added to the same task queue according to an execution sequence; and

a task execution module 720 configured to execute the data update task to be executed to update the target data in the at least one target device.

It should be understood that the various modules of the apparatus 600 shown in fig. 6 may correspond to the various steps in the method 200 described with reference to fig. 2, and the various modules of the apparatus 700 shown in fig. 7 may correspond to the various steps in the method 400 described with reference to fig. 4. Thus, the operations, features and advantages described above with respect to method 200 are equally applicable to apparatus 600 and the modules included therein, and the operations, features and advantages described above with respect to method 400 are equally applicable to apparatus 700 and the modules included therein. Certain operations, features and advantages may not be described in detail herein for the sake of brevity.

Although specific functionality is discussed above with reference to particular modules, it should be noted that the functionality of the various modules discussed herein may be divided into multiple modules and/or at least some of the functionality of multiple modules may be combined into a single module. For example, the queue determination module 620 and task addition module 630 described above may be combined into a single module in some embodiments.

It should also be appreciated that various techniques may be described herein in the general context of software, hardware elements, or program modules. The various modules described above with respect to fig. 6, 7 may be implemented in hardware or in hardware in combination with software and/or firmware. For example, the modules may be implemented as computer program code/instructions configured to be executed in one or more processors and stored in a computer-readable storage medium. Alternatively, the modules may be implemented as hardware logic/circuitry. For example, in some embodiments, one or more of the task receiving module 610, the queue determining module 620, the task adding module 630, the task sending module 640, the task obtaining module 710, and the task executing module 720 may be implemented together in a System on Chip (SoC). The SoC may include an integrated circuit chip (which includes one or more components of a Processor (e.g., a Central Processing Unit (CPU), microcontroller, microprocessor, Digital Signal Processor (DSP), etc.), memory, one or more communication interfaces, and/or other circuitry), and may optionally execute received program code and/or include embedded firmware to perform functions.

According to an embodiment of the present disclosure, there is also provided an electronic device, a readable storage medium, and a computer program product.

Referring to fig. 8, a block diagram of a structure of an electronic device 800, which may be a server or a client of the present disclosure, which is an example of a hardware device that may be applied to aspects of the present disclosure, will now be described. Electronic device is intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 8, the apparatus 800 includes a computing unit 801 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The calculation unit 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

A number of components in the device 800 are connected to the I/O interface 805, including: an input unit 806, an output unit 807, a storage unit 808, and a communication unit 809. The input unit 806 may be any type of device capable of inputting information to the device 800, and the input unit 806 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device, and may include, but is not limited to, a mouse, a keyboard, a touch screen, a track pad, a track ball, a joystick, a microphone, and/or a remote control. Output unit 807 can be any type of device capable of presenting information and can include, but is not limited to, a display, speakers, a video/audio output terminal, a vibrator, and/or a printer. The storage unit 808 may include, but is not limited to, a magnetic disk, an optical disk. The communication unit 809 allows the device 800 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, such as bluetooth^TMDevices, 1302.11 devices, Wi-Fi devices, Wi-Max devices, cellular communication devices, and/or the like.

Computing unit 801 may be a variety of general and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and the like. The computing unit 801 performs the various methods and processes described above, such as the method 200 and/or the method 400. For example, in some embodiments, method 200 and/or method 400 may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program can be loaded and/or installed onto device 800 via ROM 802 and/or communications unit 809. When loaded into RAM 803 and executed by computing unit 801, may perform one or more steps of method 200 and/or method 400 described above. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the method 200 and/or the method 400 by any other suitable means (e.g., by way of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be performed in parallel, sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

Although embodiments or examples of the present disclosure have been described with reference to the accompanying drawings, it is to be understood that the above-described methods, systems and apparatus are merely exemplary embodiments or examples and that the scope of the present invention is not limited by these embodiments or examples, but only by the claims as issued and their equivalents. Various elements in the embodiments or examples may be omitted or may be replaced with equivalents thereof. Further, the steps may be performed in an order different from that described in the present disclosure. Further, various elements in the embodiments or examples may be combined in various ways. It is important that as technology evolves, many of the elements described herein may be replaced with equivalent elements that appear after the present disclosure.

Claims

1. A method of updating data, comprising:

receiving a data updating task, wherein the data updating task comprises an identifier of target data to be updated, and the target data corresponds to at least one target device;

determining a target queue corresponding to the data updating task from at least one task queue according to the identification of the target data;

adding the data update task to the tail of the target queue; and

responding to the data updating task moving to the head of the target queue, and sending the data updating task to a task execution unit, so that the task execution unit executes the data updating task to update target data in the at least one target device.

2. The method of claim 1, wherein the identification of the target data is a combination of an identification of a user submitting the data update task, a type of the target data, and a name of the target data.

3. The method according to claim 1 or 2, wherein determining a target queue corresponding to the data update task from at least one task queue according to the identification of the target data comprises:

mapping the identifier of the target data to obtain a mapping value corresponding to the identifier of the target data; and

and taking the task queue corresponding to the mapping value as the target queue.

4. The method of any of claims 1-3, wherein the data update task further comprises an asynchronous tag to indicate whether the data update task is an asynchronous task.

5. The method of claim 4, wherein the data update task is submitted by a client device;

the method further comprises the following steps:

and after receiving the data updating task, responding to the asynchronous label indicating that the data updating task is an asynchronous task, and returning a message of completing the execution of the data updating task to the client equipment.

6. The method of claim 4, further comprising:

and receiving and storing the execution result of the data updating task returned by the task execution unit in response to the asynchronous label indicating that the data updating task is not an asynchronous task.

7. The method of claim 6, wherein the data update task is submitted by a client device;

the method further comprises the following steps:

returning the execution result to the client device; and

deleting the stored execution result.

8. A method of updating data, comprising:

the method comprises the steps that a data updating task to be executed is obtained from the head of a target queue, the data updating task to be executed comprises an identifier of target data to be updated, the target data correspond to at least one target device, the target queue is one of at least one task queue, and a plurality of data updating tasks used for updating the same data are added into the same task queue according to an execution sequence; and

and executing the data updating task to be executed so as to update the target data in the at least one target device.

9. The method of claim 8, further comprising:

polling the at least one task queue to determine whether an unexecuted data updating task exists at the head of each task queue; and

and in response to the fact that the head of the current task queue has the data updating task which is not executed, taking the current task queue as the target queue.

10. The method according to claim 8 or 9, wherein the data update task to be performed comprises at least one sub-task, and

wherein executing the data update task to be executed comprises:

and sequentially executing the at least one subtask, and recording the execution result of each subtask when the execution of the subtask is completed.

11. An apparatus for updating data, comprising:

a task receiving module configured to receive a data update task, the data update task including an identification of target data to be updated, the target data corresponding to at least one target device;

the queue determining module is configured to determine a target queue corresponding to the data updating task from at least one task queue according to the identification of the target data;

a task adding module configured to add the data update task to the tail of the target queue; and

the task sending module is configured to respond to the data updating task moving to the head of the target queue, and send the data updating task to the task execution unit, so that the task execution unit executes the data updating task to update the target data in the at least one target device.

12. An apparatus for updating data, comprising:

the task obtaining module is configured to obtain a data updating task to be executed from the head of a target queue, where the data updating task to be executed includes an identifier of target data to be updated, the target data corresponds to at least one target device, the target queue is one of at least one task queue, and multiple data updating tasks for updating the same data are added to the same task queue according to an execution sequence; and

and the task execution module is configured to execute the data updating task to be executed so as to update the target data in the at least one target device.

13. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein

The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-10.

14. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-10.

15. A computer program product comprising a computer program, wherein the computer program realizes the method of any one of claims 1-10 when executed by a processor.