Edge device management method and device of Android system, equipment and storage medium

Abstract

The invention provides an edge device management method, device and system of an Android system and a storage medium, and relates to the technical field of edge devices. The method comprises the following steps: when the state of the edge device is an offline state, caching a to-be-issued first management command for the edge device into a Mongo database, initializing the state of the first management command in the Mongo database into a cache, and storing a first command identifier of the first management command into a Redis queue in a Redis database; when an online message sent by the edge device is received, device information of the edge device is extracted from the online message; obtaining a first management command from a Mongo database according to the first command identifier; and sending the first management command to the edge device, and modifying the state of the first management command in the Mongo database to be issued. According to the method provided by the invention, the problems of edge device management of the Android system and application deployment in an offline state are solved.

Description

Technical Field

[0001] This application relates to the technical field of edge devices, and in particular to a method, device, system and storage medium for managing edge devices of the Android system. Background Art

[0002] With the increasing richness of Internet of Things and edge computing application scenarios, the demand for edge computing has surged, and end-edge-cloud collaboration has become an important evolution direction. Collaborative computing between the cloud server and edge computing devices is a distributed computing model aimed at optimizing resource utilization, reducing latency and improving efficiency by distributing computing tasks between the cloud and edge devices close to the data source. Among them, the management of edge devices has become a difficult point.

[0003] In terms of edge device management, the KubeEdge platform is usually combined with cloud native technology to realize the connection and operation of edge devices. However, KubeEdge does not support the management of edge devices of the Android system and has limitations. Extending to edge devices through cloud native technology enables these devices to be connected to the cloud via the public network. This method requires edge devices to continue to operate even in the event of a network disconnection or weak network environment. However, the existing technical implementation methods have not fully considered the management of edge devices in the offline state, resulting in the inability to effectively deploy applications and monitor the status in this case. Summary of the Invention

[0004] This application provides a method, device, system and storage medium for managing edge devices of the Android system, which is used to solve the problems of managing edge devices of the Android system and application deployment in the offline state.

[0005] In a first aspect, this application provides a method for managing edge devices of the Android system, which is applied to an edge device management server. The edge device management server is communicatively connected to an edge device, a Mongo database and a Redis database. The method includes:

[0006] When the status of the edge device is in the offline state, cache the first management command to be sent to the edge device in the Mongo database, and initialize the status of the first management command in the Mongo database as cached, and save the first command identifier of the first management command to the Redis queue in the Redis database;

[0007] When receiving an online message sent by the edge device, extract the device information of the edge device from the online message, so as to obtain the first command identifier to be sent to the edge device from the Redis database according to the device information of the edge device;

[0008] Obtain the first management command from the Mongo database according to the first command identifier;

[0009] The first management command is sent to the edge device, and the status of the first management command in the Mongo database is changed to issued.

[0010] In a possible design, the edge device management server is further connected to the open source IoT message server EMQ, and after caching the first management command to be issued for the edge device in the Mongo database, the method further includes:

[0011] Sending a first delay message to the EMQ, where the first delay message includes a first command identifier and a first timeout duration of the first management command;

[0012] When receiving the first delayed response message replied by EMQ, the status of the first management command is obtained from the Mongo database according to the first command identifier in the first delayed response message. The first delayed response message is sent by EMQ when the first timeout period is reached after receiving the first delayed message.

[0013] When the status of the first management command is in cache, the status in the Mongo database is modified to timed out, and the first command identifier is deleted from the Redis queue.

[0014] In one possible design, the method further includes:

[0015] When receiving the sending response message sent by the edge device for the first management command, the first command identifier is deleted from the Redis queue, and the status of the first management command in the Mongo database is updated according to the sending result in the sending response message. The sending result includes successful sending and failed sending.

[0016] In a possible design, after the status of the first management command in the Mongo database is changed to issued, the following further includes:

[0017] Sending a second delay message to the EMQ, where the second delay message includes the first command identifier and a second timeout duration of the first management command;

[0018] The method also includes:

[0019] When receiving the second delayed response message sent by EMQ, if the response message sent by the edge device for the first management command has not been received, the status of the management command is obtained from the Mongo database. The second delayed response message is sent by EMQ when the second timeout period is reached after receiving the second delayed message;

[0020] If the status of the management command is sent, the retry process of the Mongo database is started to repeatedly send the first management command in the Mongo database N times;

[0021] After the first management command is sent N times, if the status of the first management command is "sent", modify the status of the first management command in the Mongo database to "timed out", and delete the first command identifier from the Redis queue. N is an integer greater than or equal to 1.

[0022] In a possible design, the method further includes:

[0023] If a download response message sent by the edge device for the first management command is received during the retry process, control the Mongo database to stop the retry process, update the status of the first management command in the Mongo database according to the download response message, and delete the first command identifier in the Redis queue.

[0024] In a possible design, the method further includes:

[0025] Receive device information sent by the edge device;

[0026] Send a deployment command of the target application to the edge device according to the device information. The deployment command carries: an application identifier and an application address. The deployment command is used to instruct the edge device to download and install the target application from the edge device management server.

[0027] When the status information sent by the edge device is not received within a preset duration, determine that the status of the edge device is the offline state;

[0028] When the status information sent by the edge device is received within a preset duration, determine that the status of the edge device is the online state.

[0029] In a second aspect, the present application provides an edge device management device for an Android system, which is applied to an edge device management server. The edge device management server is communicatively connected to an edge device, a Mongo database, and a Redis database. The device includes:

[0030] A save identifier module, configured to cache the first management command to be sent to the edge device in the Mongo database when the status of the edge device is the offline state, initialize the status of the first management command in the Mongo database as cached, and save the first command identifier of the first management command to the Redis queue in the Redis database;

[0031] An extract information module, configured to extract the device information of the edge device from the online message when an online message sent by the edge device is received, so as to obtain the first command identifier to be sent to the edge device from the Redis database according to the device information of the edge device;

[0032] A get command module, configured to obtain the first management command from the Mongo database according to the first command identifier;

[0033] A modification status module, configured to send a first management command to an edge device and modify the status of the first management command in the Mongo database to "sent".

[0034] In a third aspect, the present application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0035] The memory stores computer-executable instructions;

[0036] The processor executes the computer-executable instructions stored in the memory, and is configured to implement an edge device management method for an Android system according to the invention content of the first aspect.

[0037] In a fourth aspect, the present application further provides an edge device management system for an Android system, including: an edge device management server, a Mongo database, and a Redis database;

[0038] Wherein, the Mongo database is configured to cache a first management command to be sent to the edge device, the Redis database is configured to store a first command identifier of the first management command, and the edge device management server is configured to implement an edge device management method for an Android system according to the invention content of the first aspect.

[0039] In a fifth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are configured to implement an edge device management method for an Android system according to the invention content of the first aspect.

[0040] In a sixth aspect, the present application provides a computer program product, including: a computer program, and when the computer program is executed by a processor, it is configured to implement an edge device management method for an Android system according to the invention content of the first aspect.

[0041] An edge device management method, device, system, and storage medium for an Android system provided by this application. When the edge device is in an offline state, the first management command to be sent to the edge device is cached in the Mongo database, and the status of the first management command in the Mongo database is initialized to cached, and the first command identifier of the first management command is saved to the Redis queue in the Redis database; when receiving an online message sent by the edge device, the device information of the edge device is extracted from the online message, and according to the device information of the edge device, the first command identifier to be sent to the edge device is obtained from the Redis database; the first management command is obtained from the Mongo database according to the first command identifier; the first management command is sent to the edge device, and the status of the first management command in the Mongo database is modified to sent. The following technical effects are achieved: Through the coordinated processing among the edge device management server, the Mongo database, and the Redis database, the application deployment of the edge device of the Android system is realized; when the edge device is in an offline state, through the processing of the management command by the Mongo database and the modification of the status pair, the application status monitoring of the edge device is realized, and the edge devices of the Android system are uniformly accessed and controlled; during the application operation, the edge device management server can send commands for application installation or start / stop to the edge device at any time, regardless of whether the edge device is offline, realizing the function of remote scheduling. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0043] Figure 1 It is a schematic diagram of the system architecture of the edge device management method for the Android system provided by the embodiment of this application;

[0044] Figure 2 It is a flowchart of the edge device management method for the Android system provided by the embodiment of this application Figure 1 ;

[0045] Figure 3 It is a flowchart of the edge device management method for the Android system provided by the embodiment of this application Figure 2 ;

[0046] Figure 4 It is a flowchart of the edge device management method for the Android system provided by the embodiment of this application Figure 3 ;

[0047] Figure 5 It is an interaction diagram between the server and the edge device of the edge device management method for the Android system provided by the embodiment of the present application;

[0048] Figure 6 It is an online interaction diagram of the edge device of the edge device management method for the Android system provided by the embodiment of the present application;

[0049] Figure 7 It is an offline interaction diagram of the edge device of the edge device management method for the Android system provided by the embodiment of the present application;

[0050] Figure 8 It is an offline interaction diagram of the edge device of the edge device management method for the Android system provided by the embodiment of the present application;

[0051] Figure 9 It is a schematic structural diagram of the edge device management device for the Android system provided by the embodiment of the present application;

[0052] Figure 10 It is a schematic structural diagram of the hardware of the electronic device provided by the embodiment of the present application.

[0053] Reference numerals:

[0054] 100 - Edge device management system for Android system; 200 - EMQ; 300 - Edge device;

[0055] 110 - Edge device management server; 120 - Mongo database; 130 - Redis database;

[0056] 910 - Save identification module; 920 - Extract information module; 930 - Obtain command module; 940 - Modify status module;

[0057] 1010 - Processor; 1020 - Memory; 1030 - Communication component; 1040 - Bus. Detailed implementation manners

[0058] Here, the exemplary embodiments will be described in detail, and the examples are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present application. On the contrary, they are merely examples of the devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0059] In the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean different. It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner. In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more.

[0060] It should be noted that "when... " in the embodiments of the present application can be the instant when a certain situation occurs, or it can be a period of time after a certain situation occurs. The embodiments of the present application do not make specific limitations in this regard. In addition, the method for managing edge devices of the Android system provided in the embodiments of the present application is only an example, and the method for managing edge devices of the Android system may include more or less content.

[0061] To facilitate a clear description of the technical solutions of the embodiments of the present application, the following briefly introduces some terms and technologies involved in the embodiments of the present application:

[0062] Message Broker Server (Erlang MQTT Broker, abbreviated as EMQ): EMQ generally refers to a message broker server developed using the Erlang programming language.

[0063] Mongo database: The Mongo database is a database based on distributed file storage.

[0064] Key-Value Store Database (Remote Dictionary Server, abbreviated as Redis): The Redis database is an open-source, network-supported key-value storage system. It supports a variety of data types, including strings, lists, sets, sorted sets, and hash types.

[0065] Kubernetes (abbreviated as K8s): K8s is an open-source container orchestration platform used for automating the deployment, scaling, and management of containerized applications.

[0066] KubeEdge: KubeEdge is an open-source platform designed to extend the capabilities of K8s from the cloud to edge computing environments. It enables users to run containerized applications on edge devices close to the data source and manage these edge nodes and applications using K8s tools.

[0067] With the increasing richness of Internet of Things and edge computing application scenarios, cloud-edge-terminal collaborative computing technology is more widely applied; cloud-edge-terminal collaborative computing is a distributed computing architecture that optimizes performance, reduces latency, and improves efficiency by allocating computing resources and data processing tasks among the cloud, edge nodes, and terminal devices.

[0068] With the continuous expansion of the collaborative computing between the cloud server and edge computing devices, the types of devices involved are increasing, including industrial control devices of multiple systems, etc. The edge devices corresponding to different systems are different, and there are also certain limitations for different systems.

[0069] In the prior art, mainstream cloud-edge-terminal collaborative computing generally uses the K8s and KubeEdge edge computing platforms, relying on the container orchestration and scheduling capabilities of K8s to achieve smooth access to cloud-edge collaboration, massive devices, and computing sinking; at the same time, the modular decoupling and simplification of KubeEdge reduce the running memory of edge devices to dozens of megabytes, and functions such as cloud-edge collaborative communication and edge offline autonomy are realized, and the local containerized application orchestration and management can be extended to edge devices. In addition, through the combination of cloud-native technology and the cloud-edge-terminal mode of K8s and KubeEdge, it is ensured that the application program is decomposed into a series of small and independent services for easy expansion and upgrade.

[0070] However, although this implementation method realizes cloud-edge-terminal collaborative computing, there are still some problems: The KubeEdge platform supports a variety of operating systems, but it does not support the Android system and cannot reuse the cloud-edge-terminal mode of K8s and KubeEdge; the application of cloud-native technology needs to be connected to the cloud through the public network, and the public network is unstable. Edge devices may be in a state of network disconnection, weak network, or offline state, and at this time, the download of application packages cannot be realized.

[0071] Therefore, how to achieve the management of edge devices for the Android system, as well as application deployment and application status monitoring in the offline state, is an urgent problem to be solved in this application.

[0072] Based on this, the embodiments of this application provide a method, device, system, and storage medium for managing edge devices of the Android system, which can be used in the technical field of edge devices and are designed to solve the above technical problems in the prior art.

[0073] Figure 1This is a schematic diagram of the system architecture of the edge device management method for the Android system provided by the embodiments of the present application. It should be noted that Figure 1 The figure shown is only an example of the system architecture to which the embodiments of the present application can be applied, to help those skilled in the art understand the technical content of the present application, but it does not mean that the embodiments of the present application cannot be used in other devices, systems, environments or scenarios.

[0074] As Figure 1 shown, the system architecture of the edge device management method for the Android system includes: the edge device management system 100 of the Android system, the open-source Internet of Things message server EMQ 200, and the edge device 300.

[0075] The edge device management system 100 of the Android system is communicatively connected to both the open-source Internet of Things message server EMQ 200 and the edge device 300. Among them, the edge device 300 is an Android computing device.

[0076] The edge device management system 100 of the Android system includes an edge device management server 110, a Mongo database 120, and a Redis database 130. Among them, the edge device management server 110, the Mongo database 120, and the Redis database 130 are all communicatively connected.

[0077] The edge device management server 110 is used to obtain information of the open-source Internet of Things message server EMQ 200 and the edge device 300, and issue application deployment commands through the information. The Mongo database 120 is used to cache the management commands issued by the edge device management server 110, as well as the modification of the management status of the edge device 300. The Redis database 130 is used to store the management commands of the edge device management server 110, as well as the corresponding management command identifiers.

[0078] When the edge device 300 is indicated as the online state, the open-source Internet of Things message server EMQ 200 is used to forward the issued commands of the edge device management system 100 of the Android system, as well as the device information of the edge device 700. When the edge device 300 is indicated as the offline state, obtain the issued commands of the edge device management system 100 of the Android system, and issue the issued commands, as well as send and judge the delayed messages.

[0079] Figure 2 This is a schematic diagram of the process of the edge device management method for the Android system provided by the embodiments of the present application Figure 1 . The method is applied to the edge device management server, and the edge device management server is communicatively connected to the edge device, the Mongo database, and the Redis database. All commands in the present application have unique corresponding identifiers.

[0080] As Figure 2 shown, the method includes:

[0081] S201. When the status of the edge device is offline, cache the first management command to be sent to the edge device in the Mongo database, and initialize the status of the first management command in the Mongo database as cached, and save the first command identifier of the first management command to the Redis queue in the Redis database.

[0082] Specifically, after the edge device is activated, add the computing device corresponding to the edge device, and obtain the device information sent by the edge device.

[0083] Create a target application according to the device information, and send the deployment command of the target application. The deployment command includes an application identifier and an application address. After the edge device obtains the deployment command of the target application, download and install the target application from the edge device management server.

[0084] After the target application is successfully installed, the edge device management server reports and obtains information about events, and updates the running status to running.

[0085] During the operation of the edge device, when the status information sent by the edge device is received within a preset duration, determine that the status of the edge device is the online state. When the status information sent by the edge device is not received within the preset duration, determine that the status of the edge device is the offline state.

[0086] When the status of the edge device is offline, perform parameter verification, cache the first management command to be sent to the edge device in the Mongo database, and determine the status of the first management command in the Mongo database as cached. Each management command corresponds to a unique command identifier, so save the first command identifier corresponding to the first management command to the Redis queue in the Redis database.

[0087] Send the first delay information to the open-source Internet of Things message server EMQ. The first delay information includes the first command identifier and the first timeout duration of the first management command. When EMQ reaches the duration indicated by the first timeout duration, obtain the first delay response message sent by EMQ. The first delay response message contains the first command identifier.

[0088] According to the first command identifier of the first delay response message, obtain the status of the first management command from the Mongo database, modify the status in the Mongo database to timed out, and delete the first command identifier from the Redis queue.

[0089] S202. When receiving the online message sent by the edge device, extract the device information of the edge device from the online message, so as to obtain the first command identifier to be sent to the edge device from the Redis database according to the device information of the edge device.

[0090] Specifically, when the edge device indicates being online, extract the device information of the edge device from the online message. Obtain the first command identifier corresponding to the first management command to be sent in the Redis database.

[0091] S203. Obtain the first management command from the Mongo database according to the first command identifier.

[0092] Specifically, judge whether there is a first identifier corresponding to the first management command that has not been sent in the Redis database according to the first command identifier.

[0093] When there is an unsent first management command in the Redis database, obtain the first management command from the Mongo database according to the first command identifier.

[0094] S204. Send the first management command to the edge device, and modify the status of the first management command in the Mongo database to sent.

[0095] Specifically, send the first management command to the online edge device, and modify the status of the first management command in the Mongo database to sent. At the same time, send a second delay message to EMQ, where the second delay message includes the first command identifier and the second timeout duration of the first management command. The second delay response message refers to the message returned by EMQ to the edge device management server after reaching the second timeout duration after receiving the second delay message.

[0096] At this time, after the first management command is sent, obtain the second delay response message returned by EMQ.

[0097] If the sent response message sent by the edge device for the first management command is not received, obtain the status of the management command from the Mongo database. When the status indicated by the management command indicates sent, start the retry process of the Mongo database, send the first management command in the Mongo database multiple times, then modify the status of the first management command in the Mongo database to timed out, and delete the first command identifier from the Redis queue.

[0098] If, during the retry process, the sent response message sent by the edge device for the first management command is received, stop the retry process of the Mongo database, and update the status of the first management command in the Mongo database to successful or failed according to the sent response message, and delete the first command identifier from the Redis queue.

[0099] An edge device management method for the Android system provided by this application. When the edge device is in the offline state, the first management command to be sent to the edge device is cached in the Mongo database, and the status of the first management command in the Mongo database is initialized to cached, and the first command identifier of the first management command is saved in the Redis queue in the Redis database; when receiving the online message sent by the edge device, extract the device information of the edge device from the online message, and based on the device information of the edge device, obtain the first command identifier to be sent to the edge device from the Redis database; obtain the first management command from the Mongo database according to the first command identifier; send the first management command to the edge device, and modify the status of the first management command in the Mongo database to sent. The following technical effects are achieved: Through the coordinated processing among the edge device management server, the Mongo database, and the Redis database, the application deployment of the edge devices in the Android system is realized; when the edge device is in the offline state, through the processing of the management command by the Mongo database and the modification of the status pair, the application status monitoring of the edge device is realized, and the edge devices in the Android system are uniformly accessed and controlled; during the application operation, the edge device management server can send commands for application installation or start / stop to the edge device at any time, regardless of whether the edge device is offline, realizing the function of remote scheduling.

[0100] Figure 3 It is a flowchart illustration of the edge device management method for the Android system provided by the embodiments of this application Figure 2 。This embodiment is based on Figure 2 the embodiment, and details the steps of the edge device in the online and offline states of the edge device management method for the Android system. As Figure 3 shown, an edge device management method for the Android system provided by this embodiment includes:

[0101] S301. Receive the device information sent by the edge device.

[0102] Specifically, after the edge device is activated, a new computing device corresponding to the edge device is added, and the device information sent by the edge device is obtained.

[0103] S302. Send a deployment command for the target application to the edge device according to the device information.

[0104] Among them, the deployment command carries: an application identifier and an application address, and the deployment command is used to instruct the edge device to download and install the target application from the edge device management server.

[0105] Specifically, send the deployment command of the target application to the edge device according to the device information. The edge device downloads and installs the target application through the application identifier and application address. Obtain the deployment response returned by the edge device through event reporting, update the deployment record, and obtain the running status of the edge device and the application service status in real time.

[0106] When the status indication of the edge device is the online state, execute step S303; when the status indication of the edge device is the offline state, execute step S304.

[0107] S303. When the status information sent by the edge device is received within the preset duration, determine that the status of the edge device is the online state.

[0108] Specifically, when the status information sent by the edge device is obtained in real time within the preset duration, determine that the status of the edge device is the online state. The EMQ can start and stop the application service. The EMQ issues the service to the edge device. The edge device starts and stops the application according to the service and reports it to the EMQ in a timely manner. The EMQ forwards it to the edge device management server in a timely manner.

[0109] It should be noted that when the status indication of the edge device is online, the open-source Internet of Things message server EMQ only plays a forwarding role, communicating and forwarding the information between the edge device management server and the edge device.

[0110] S304. When the status information sent by the edge device is not received within the preset duration, determine that the status of the edge device is the offline state.

[0111] Specifically, when the status information sent in real time by the edge device is not received within the preset duration, determine that the status of the edge device is the offline state.

[0112] S305. When the status of the edge device is the offline state, cache the first management command to be issued to the edge device in the Mongo database, and initialize the status of the first management command in the Mongo database as cached, and save the first command identifier of the first management command to the Redis queue in the Redis database.

[0113] Specifically, when the status indication of the edge device is the offline state, send the first management command to be issued to the edge device to the Mongo database, and determine the status of the first management command in the Mongo database as cached. Here, the cached state should be understood as sending the first management command to the Mongo database without issuing it to the edge device.

[0114] Save the first command identifier corresponding to the first management command to the Redis queue in the Redis database.

[0115] S306. Send the first delayed message to EMQ.

[0116] Among them, the first delayed message includes a first command identifier and a first timeout duration of the first management command; the edge device management server is also communicatively connected to the open-source Internet of Things message server EMQ.

[0117] Specifically, send the first delayed message including the first command identifier and the first timeout duration corresponding to the first management command to the communicatively connected EMQ.

[0118] When EMQ reaches the time indicated by the first timeout duration, it returns a first delayed response message.

[0119] S307. When receiving the first delayed response message replied by EMQ, obtain the status of the first management command from the Mongo database according to the first command identifier in the first delayed response message.

[0120] Among them, the first delayed response message is sent by EMQ when it reaches the first timeout duration after receiving the first delayed message.

[0121] Specifically, when receiving the first delayed response message replied by EMQ, obtain the status of the first management command from the Mongo database according to the first command identifier corresponding to the first delayed response message.

[0122] S308. When the status of the first management command is in the cache, modify the status in the Mongo database to timed out and delete the first command identifier from the Redis queue.

[0123] Specifically, the status of the first management command being in the cache means that the first management command has been sent but this cached command has not been deleted.

[0124] When the status of the first management command is in the cache, update the status of the first management command in the Mongo database to timed out and delete the first command identifier from the Redis queue.

[0125] The technical effect provided by this embodiment is that the edge computing power devices of the Android system execute steps separately when online and offline, so as to quickly achieve the application status monitoring of edge devices; through the interaction method among EMQ, Mongo database, Redis database, and the edge device management server, the application distribution or application start / stop of edge devices is realized in the offline state, without the need to judge whether the edge device is online.

[0126] Figure 4 It is a schematic flow of the edge device management method for the Android system provided by the embodiment of the present application Figure 3 . This embodiment is atFigure 2 and Figure 3 Based on the embodiment, the edge device management method of the Android system is described in detail for executing the command online after the edge device is offline. Figure 3 As shown, this embodiment provides an edge device management method for an Android system, including:

[0127] The steps of this method need to be established after the edge device has been registered with the edge device management server and the application is deployed. It is worth noting that the role of EMQ in the offline state of the edge device and in going online after the offline state includes not only forwarding, but also delay processing.

[0128] S401. When receiving an online message sent by an edge device, extract device information of the edge device from the online message, and obtain a first command identifier to be sent to the edge device from a Redis database according to the device information of the edge device.

[0129] Specifically, when the edge device indicates that it is online, the device information corresponding to the edge device is extracted and parsed according to the online message of the edge device.

[0130] According to the online information of the edge device, determine whether the Redis database has a first command identifier that has not been sent to the edge device. If there is an unsent first command identifier, obtain the first command identifier to be sent to the edge device from the Redis database; if there is no unsent first command identifier, the edge device can obtain the instructions sent by the edge device management server at any time through EMQ, and the situation is the same as the steps performed when the status indication of the edge device is online.

[0131] S402: Obtain a first management command from a Mongo database according to a first command identifier.

[0132] Specifically, according to the obtained first command identifier, the first management command corresponding to the first command identifier is obtained from the Mongo database.

[0133] S403: Send the first management command to the edge device, and change the status of the first management command in the Mongo database to issued.

[0134] Specifically, the first management command is sent to the edge device, and the status of the first management command in the Mongo database is modified to have been sent.

[0135] After receiving the first management command, the edge device executes the command and returns a response message.

[0136] S404: Send a second delay message to the EMQ, where the second delay message includes the first command identifier and a second timeout duration of the first management command.

[0137] Specifically, send second delay information including a first command identifier and a second timeout duration of a first management command to EMQ.

[0138] After receiving the second delay information, when the duration indicated by the second timeout duration is reached, EMQ returns a second delay response message.

[0139] S405. When receiving a distribution response message sent by an edge device for the first management command, delete the first command identifier from the Redis queue, and update the status of the first management command in the Mongo database according to the distribution result in the distribution response message.

[0140] Among them, the distribution result includes successful distribution and failed distribution.

[0141] Specifically, when receiving a distribution response message returned by an edge device for the first management command, delete the first command identifier from the Redis queue to avoid duplicate distribution of management commands.

[0142] According to the distribution result of the distribution response message, update the status of the first management command in the Mongo database, and the update result is successful distribution or failed distribution.

[0143] Within the duration indicated by the second timeout duration, when receiving a distribution response message sent by an edge device for the first management command and the distribution result indicates successful distribution, perform the distribution of the next management command.

[0144] If a distribution response message sent by an edge device for the first management command is not received within the duration indicated by the second timeout duration and the update result indicates failed distribution, then perform step S406 until successful distribution.

[0145] S406. When receiving the second delay response message sent by EMQ, if a distribution response message sent by an edge device for the first management command is still not received, obtain the status of the management command from the Mongo database.

[0146] Among them, the second delay response message is sent by EMQ when the second timeout duration is reached after receiving the second delay information.

[0147] Specifically, when receiving the second delay response message sent by EMQ and a distribution response message sent by an edge device for the first management command is not received, obtain the status of the management command from the Mongo database.

[0148] The status of the management command can be sent or not sent. If it is not sent, step S403 is executed to resend the command to the edge device; if the status of the management command is sent, step S407 is executed.

[0149] S407. If the status of the management command is sent, start the retry process of the Mongo database to resend the first management command in the Mongo database N times.

[0150] Specifically, the retry process of the Mongo database refers to the limited number of retries within the Mongo database. Each time a retry is made, the corresponding limited number of retries is decreased by 1 until the number of retries is 0. Among them, N is the limited number of retries, and N is an integer greater than or equal to 1.

[0151] When the status of the management command is sent, start the retry process of the Mongo database to resend the first management command in the Mongo database N times.

[0152] In a possible design, if a delivery response message sent by the edge device for the first management command is received during the retry process, control the Mongo database to stop the retry process, update the status of the first management command in the Mongo database according to the delivery response message, and delete the first command identifier in the Redis queue.

[0153] Specifically, during the retry process, if a delivery response message sent by the edge device for the first management command is received, control the Mongo database to stop the retry process, update the status of the first management command in the Mongo database according to the delivery response message, and delete the first command identifier in the Redis queue to avoid resending the first management command repeatedly.

[0154] S408. After N deliveries, if the status of the first management command is sent, modify the status of the first management command in the Mongo database to timed out and delete the first command identifier from the Redis queue.

[0155] Specifically, after N deliveries, when the status of the first management command is sent but the delivery response message sent by the edge device for the first management command has still not been received, modify the status of the first management command in the Mongo database to timed out and delete the first command identifier from the Redis queue.

[0156] The technical effect provided by this embodiment is that through the embodiments of the present application, an application service for the edge device to go offline and then go online is realized; after the edge device goes online, it consumes the cached command sent down to realize application deployment or application start / stop.

[0157] Figure 5Interaction diagram between the server and edge device for the edge device management method of the Android system provided in the embodiments of this application. On the basis of the Figure 3 embodiment, the preparation process before the edge device of the edge device management method of the Android system goes online is described in detail. As Figure 5 shown, it includes:

[0158] S501. The edge device management server creates a device.

[0159] S502. The Android edge device activates the device and reports its attributes to EMQ.

[0160] Among them, the attribute reporting is the computing power registration.

[0161] S503. EMQ sends the computing power registration to the edge device management server.

[0162] S504. The edge device management server adds a computing power device.

[0163] S505. The edge device management server creates a target application.

[0164] S506. The edge device management server sends a target application deployment command to EMQ.

[0165] S507. EMQ forwards the target application deployment command to the Android edge device.

[0166] S508. The Android edge device downloads and installs the target application.

[0167] S509. The Android edge device sends a deployment response to EMQ.

[0168] S510. EMQ forwards the deployment response to the edge device management server.

[0169] S511. The edge device management server updates the deployment record.

[0170] Figure 6 Interaction diagram between the edge device and the server for the edge device management method of the Android system provided in the embodiments of this application. On the basis of the Figure 5 embodiment, when the edge device of the edge device management method of the Android system is online, the application service process is described in detail. As Figure 6 shown, it includes:

[0171] S601. The Android edge device sends the device running status to EMQ.

[0172] S602. EMQ forwards the device running status to the edge device management server.

[0173] S603. The edge device management server updates the application service status.

[0174] S604. The edge device management server sends the start / stop application service to EMQ.

[0175] S605. EMQ forwards the start / stop application service to the Android edge device.

[0176] S606. The Android edge device starts or stops the application.

[0177] S607. The Android edge device sends the start / stop response to EMQ.

[0178] S608. EMQ forwards the start / stop response to the edge device management server.

[0179] S609. The edge device management server updates the application service status.

[0180] Figure 7 This is the offline interaction diagram of the edge device for the edge device management method of the Android system provided by the embodiments of this application. On the basis of the Figure 5 embodiments, the offline process of the edge device for the edge device management method of the Android system is described in detail. As Figure 7 shown, the command issuing service refers to a service of the edge device management server, including:

[0181] S701. The edge device management server calls the command issuing service.

[0182] S702. The command issuing service performs parameter verification.

[0183] S703. The command issuing service caches the first management command in the Mongo database.

[0184] S704. The Mongo database returns the first command identifier of the first management command.

[0185] S705. The command issuing service sends the first command identifier to the Redis database.

[0186] S706. The Redis database saves the first command identifier.

[0187] S707. The command issuing service sends the first delay message to EMQ.

[0188] S708. EMQ returns the first delay response message to the command issuing service.

[0189] S709. The command issuing service determines the status of the first management command in the Mongo database according to the first command identifier.

[0190] If the status is in the cache, modify the status in the Mongo database to timed out, and delete the first command identifier in the Redis database.

[0191] Figure 8 This is the off-line interaction diagram of the edge device for the edge device management method of the Android system provided by the embodiments of the present application. In this embodiment, Figure 5 On the basis of the embodiment, the process of the edge device going online after going offline in the edge device management method of the Android system is described in detail. As Figure 8 shown, it includes:

[0192] S801. The Android edge device goes online and sends the online information to the command issuing service.

[0193] S802. The command issuing service determines whether there is an undelivered first command identifier in the Redis database.

[0194] If there is an undelivered first command identifier, the first command identifier should be a management command issued in the offline state.

[0195] If there is no undelivered first command identifier, the execution process is the same as that of the embodiment of the edge device online process.

[0196] S803. The command issuing service obtains the first management command from the Mongo database according to the first command identifier.

[0197] S804. The Mongo database forwards the first management command to the command issuing service.

[0198] S805. The command issuing service issues the first management command to the Android edge device.

[0199] S806. The Android edge device executes the first management command.

[0200] During this period, the Android edge device can send a delivery response message to the command issuing service at any time.

[0201] For the convenience of display in the figure, this step is drawn with a dotted line, and the sending time of this step is uncertain, as well as whether to send a delivery response message.

[0202] S807. The command issuing service sends a second delay message to the EMQ.

[0203] S808. The EMQ determines whether it times out.

[0204] S809. The command issuing service obtains the second delay response message sent by the EMQ.

[0205] Before the command issuing service obtains the second delayed response message, when receiving that the Android edge device will issue a response message, execute steps S810 to S812.

[0206] Before the command issuing service obtains the second delayed response message, when not receiving that the Android edge device will issue a response message, execute steps S813 to S817.

[0207] S810. The command issuing service issues the command to delete the first command identifier to the Redis database.

[0208] S811. The Redis database deletes the first command identifier.

[0209] S812. The command issuing service modifies the status of the first management command in the Mongo database to success or failure.

[0210] S813. The Mongo database starts the retry process.

[0211] Resend the first management command to the Android edge device.

[0212] If, during the retry process, the issuing response message of the Android edge device is obtained, stop the retry process and execute S814.

[0213] If, after the retry process is completed, the issuing response message of the Android edge device is still not obtained, then execute S815.

[0214] S814. The command issuing service modifies the status of the first management command in the Mongo database to success or failure.

[0215] S815. The command issuing service modifies the status of the first management command in the Mongo database to timed out.

[0216] S816. The command issuing service issues the command to delete the first command identifier to the Redis database.

[0217] S817. The Redis database deletes the first command identifier.

[0218] The technical effect provided by the real-time example of this application is that through the example, the execution process of the edge device going offline and then going online realizes the application service process, and successfully realizes the application remote scheduling.

[0219] Embodiments of the present invention can divide functional modules for an electronic device or a main control device according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present invention is illustrative, only a logical function division, and there may be other division methods in actual implementation.

[0220] Figure 9 It is a schematic structural diagram of an edge device management device for an Android system provided by an embodiment of the present application. As Figure 9 shown, the edge device management device for the Android system includes: a save identification module 910, an extract information module 920, a obtain command module 930, and a modify status module 940.

[0221] The save identification module 910 is configured to, when the status of the edge device is an offline state, cache a first management command to be sent to the edge device in the Mongo database, and initialize the status of the first management command in the Mongo database as cached, and save the first command identifier of the first management command to the Redis queue in the Redis database;

[0222] The extract information module 920 is configured to, when receiving an online message sent by the edge device, extract the device information of the edge device from the online message, so as to obtain the first command identifier to be sent to the edge device from the Redis database according to the device information of the edge device;

[0223] The obtain command module 930 is configured to obtain the first management command from the Mongo database according to the first command identifier;

[0224] The modify status module 940 is configured to send the first management command to the edge device and modify the status of the first management command in the Mongo database to sent.

[0225] In a possible design, the edge device management server is also communicatively connected to the open source Internet of Things message server EMQ, and the save identification module 910 further includes:

[0226] A send message module, configured to send a first delay message to the EMQ, where the first delay message includes the first command identifier and the first timeout duration of the first management command;

[0227] An acquisition status module, configured to, when receiving a first delay response message replied by EMQ, obtain the status of a first management command from a Mongo database according to a first command identifier in the first delay response message, where the first delay response message is sent by EMQ when a first timeout duration is reached after receiving a first delay message;

[0228] A deletion identifier module, configured to, when the status of the first management command is in the cache, modify the status in the Mongo database to timed out and delete the first command identifier from a Redis queue.

[0229] In a possible design, the deletion identifier module includes:

[0230] A status update module, configured to, when receiving a distribution response message sent by an edge device for the first management command, delete the first command identifier from the Redis queue and update the status of the first management command in the Mongo database according to a distribution result in the distribution response message, where the distribution result includes successful distribution and failed distribution.

[0231] In a possible design, the modification status module 940 includes:

[0232] A second delay information module, configured to send a second delay message to EMQ, where the second delay message includes the first command identifier and a second timeout duration of the first management command;

[0233] The modification status module 940 further includes:

[0234] A command status module, configured to, when receiving a second delay response message sent by EMQ, if a distribution response message sent by the edge device for the first management command has not been received yet, obtain the status of the management command from the Mongo database, where the second delay response message is sent by EMQ when a second timeout duration is reached after receiving the second delay message;

[0235] A repeated distribution module, configured to, if the status of the management command is sent, start a retry process of the Mongo database to repeatedly distribute the first management command in the Mongo database N times;

[0236] A first identifier deletion module, configured to, after N distributions, if the status of the first management command is sent, modify the status of the first management command in the Mongo database to timed out and delete the first command identifier from the Redis queue, where N is an integer greater than or equal to 1.

[0237] In a possible design, the modification status module 940 further includes:

[0238] A stop sending module, configured to, if a sending response message sent by an edge device for a first management command is received during the retry process, control the Mongo database to stop the retry process, update the status of the first management command in the Mongo database according to the sending response message, and delete the first command identifier in the Redis queue.

[0239] In a possible design, the edge device management device of the Android system further includes:

[0240] An information receiving module, configured to receive device information sent by an edge device;

[0241] A deployment command module, configured to send a deployment command of a target application to the edge device according to the device information, where the deployment command carries: an application identifier and an application address, and the deployment command is used to instruct the edge device to download and install the target application from the edge device management server;

[0242] An offline status module, configured to determine that the status of the edge device is an offline status when status information sent by the edge device is not received within a preset duration;

[0243] An online status module, configured to determine that the status of the edge device is an online status when status information sent by the edge device is received within a preset duration.

[0244] The edge device management device of the Android system provided in this embodiment can execute the edge device management method of the Android system in the foregoing embodiment, and its implementation principle and technical effects are similar, which will not be elaborated here in this embodiment.

[0245] In the specific implementation of the foregoing edge device management method of the Android system, each module can be implemented as a processor, and the processor can execute computer execution instructions stored in a memory, so that the processor executes the foregoing edge device management method of the Android system.

[0246] This application further provides an edge device management system of the Android system, including: an edge device management server, a Mongo database, and a Redis database;

[0247] Wherein, the Mongo database is used to cache a first management command to be sent to the edge device, the Redis database is used to store a first command identifier of the first management command, and the edge device management server is used to implement the edge device management method of the Android system in the foregoing embodiment.

[0248] Specifically, for a specific illustration, reference can be made to Figure 1 the edge device management system 100 of the Android system in.

[0249] The edge device management system 100 of the Android system includes an edge device management server 110, a Mongo database 120, and a Redis database 130.

[0250] The edge device management server 110 is used to process various acquired information and issue corresponding management commands. The Mongo database 120 is used to manage the corresponding status of edge devices and the cache of management commands. The Redis database 130 is used to store the management commands of the edge device management server 110 and the command identifiers corresponding to the management commands.

[0251] Figure 10 It is a schematic structural diagram of the hardware of the electronic device provided by the embodiment of the present application. As Figure 10 shown, the electronic device includes: at least one processor 1010 and a memory 1020. The electronic device also includes a communication component. Among them, the processor 1010, the memory 1020, and the communication component are connected through a bus 1040.

[0252] In a specific implementation process, at least one processor 1010 executes the computer execution instructions stored in the memory 1020, so that at least one processor 1010 executes an edge device management method of an Android system executed on the electronic device side as described above.

[0253] For the specific implementation process of the processor 1010, reference can be made to the above method embodiment, and its implementation principle and technical effects are similar, which will not be elaborated here in this embodiment.

[0254] In the above embodiment, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, abbreviated as: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processor, abbreviated as: DSP), application-specific integrated circuits (English: Application Specific Integrated Circuit, abbreviated as: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the invention can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0255] The memory may include high-speed RAM memory, and may also include non-volatile storage NVM, such as at least one disk memory.

[0256] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, the buses in the drawings of this application are not limited to only one bus or one type of bus.

[0257] The functions implemented by the above-mentioned electronic device and master device are introduced for the solution provided by the embodiments of the present invention. It can be understood that in order for the electronic device or the master device to implement the above functions, it includes the corresponding hardware structures and / or software modules for executing each function. Combining the units and algorithm steps of each example described in the embodiments disclosed in the embodiments of the present invention, the embodiments of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiments of the present invention.

[0258] This application also provides a computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When the computer-executable instructions are executed by a processor, they are used to implement an edge device management method for an Android system as described above.

[0259] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof.

[0260] Such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic memory, flash memory, a magnetic disk or an optical disc. The readable storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0261] Read-Only Memory, EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic memory, flash memory, a magnetic disk or an optical disc. The readable storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0262] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an Application Specific Integrated Circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in an electronic device or a master device.

[0263] The present application also provides a computer program product, which includes: a computer program stored in a readable storage medium. At least one processor of an electronic device can read the computer program from the readable storage medium. When the computer program is executed by the processor, it is used to implement an edge device management method for an Android system as described above.

[0264] Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps including the above method embodiments; and the foregoing storage medium includes: various media such as ROM, RAM, magnetic disks, or optical discs that can store program codes.

[0265] So far, the technical solutions of the present application have been described in conjunction with the preferred embodiments shown in the drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An edge device management method for an Android system, characterized in that: Applied to an edge device management server, the edge device management server is communicatively connected to the edge device, the Mongo database, and the Redis database, the method comprising: When the state of the edge device is offline, cache the first management command to be issued for the edge device in the Mongo database, initialize the state of the first management command in the Mongo database to the cache, and save the first command identifier of the first management command in the Redis queue in the Redis database; When receiving the online message sent by the edge device, extracting the device information of the edge device from the online message, so as to obtain the first command identifier to be sent to the edge device from the Redis database according to the device information of the edge device; Acquire the first management command from the Mongo database according to the first command identifier; The first management command is sent to the edge device, and the status of the first management command in the Mongo database is modified to have been issued.

2. The method according to claim 1, characterized in that: The edge device management server is also communicatively connected to an open source Internet of Things message server EMQ. After caching the first management command to be issued for the edge device in the Mongo database, the method further includes: Sending a first delay message to the EMQ, where the first delay message includes the first command identifier and a first timeout duration of the first management command; Upon receiving the first delayed response message replied by the EMQ, obtaining the status of the first management command from the Mongo database according to the first command identifier in the first delayed response message, wherein the first delayed response message is sent by the EMQ when the first timeout period is reached after receiving the first delayed message; When the status of the first management command is in cache, the status in the Mongo database is modified to timed out, and the first command identifier is deleted from the Redis queue.

3. The method according to claim 2, characterized in that The method further comprises: When receiving the sending response message sent by the edge device for the first management command, the first command identifier is deleted from the Redis queue, and the status of the first management command in the Mongo database is updated according to the sending result in the sending response message, and the sending result includes sending success and sending failure.

4. The method according to claim 3, characterized in that After the state of the first management command in the Mongo database is changed to issued, the method further includes: Sending a second delayed message to the EMQ, where the second delayed message includes the first command identifier and a second timeout duration of the first management command; The method further comprises: When receiving the second delayed response message sent by the EMQ, if the response message sent by the edge device for the first management command has not been received, the status of the management command is obtained from the Mongo database, and the second delayed response message is sent by the EMQ when the second timeout period is reached after receiving the second delayed message; If the status of the management command is sent, starting a retry process of the Mongo database to repeatedly send the first management command in the Mongo database N times; After being sent N times, if the status of the first management command is sent, the status of the first management command in the Mongo database is modified to timed out, and the first command identifier is deleted from the Redis queue, where N is an integer greater than or equal to 1.

5. The method according to claim 4, characterized in that The method further comprises: If a response message is received from the edge device in response to the first management command during the retry process, the Mongo database is controlled to stop the retry process, and the status of the first management command in the Mongo database is updated according to the response message, and the first command identifier in the Redis queue is deleted.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Receiving device information sent by the edge device; Sending a deployment command of the target application to the edge device according to the device information, wherein the deployment command carries: an application identifier and an application address, and the deployment command is used to instruct the edge device to download and install the target application from the edge device management server; When the status information sent by the edge device is not received within a preset time period, determining that the status of the edge device is an offline state; When the status information sent by the edge device is received within the preset time period, it is determined that the status of the edge device is an online status.

7. An edge device management device for an Android system, characterized in that: Applied to an edge device management server, the edge device management server is communicatively connected to the edge device, the Mongo database and the Redis database, and the device includes: A saving identification module is used to cache the first management command to be issued for the edge device in the Mongo database when the state of the edge device is offline, initialize the state of the first management command in the Mongo database to the cache, and save the first command identifier of the first management command in the Redis queue in the Redis database; an information extraction module, configured to extract device information of the edge device from the online message when receiving the online message sent by the edge device, so as to obtain the first command identifier to be sent to the edge device from the Redis database according to the device information of the edge device; An acquisition command module, configured to acquire the first management command from the Mongo database according to the first command identifier; A status modification module is used to send the first management command to the edge device and modify the status of the first management command in the Mongo database to have been issued.

8. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; When the processor executes the computer-executable instructions stored in the memory, it is used to implement an edge device management method for an Android system as described in any one of claims 1 to 6.

9. An edge device management system for an Android system, characterized in that: include: Edge device management server, Mongo database and Redis database; Among them, the Mongo database is used to cache the first management command to be sent to the edge device, the Redis database is used to store the first command identifier of the first management command, and the edge device management server is used to execute an edge device management method for an Android system as described in any one of claims 1 to 6.

10. A computer storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement an edge device management method for an Android system as described in any one of claims 1 to 6.

Images