CN115348303A - Mobile device management and control method, cloud platform and system - Google Patents

Abstract

This application relates to the technical field of device management systems, and specifically relates to a mobile device management and control method, cloud platform, and system. Including: disabling and enabling, which can realize remote management and control of mobile devices. When encountering emergencies such as loss of mobile devices, the disabling command can be enabled on mobile devices through the cloud platform to avoid unnecessary losses.

Description

A mobile device management and control method, cloud platform, and system

technical field

The application belongs to the technical field of equipment management systems, and in particular relates to a mobile equipment management and control method, cloud platform, and system.

Background technique

With the rapid development of the online shopping industry, express mail has become a part of people's lives. There are more and more couriers and various collection points. Mobile devices, such as guns, as an indispensable part of the express delivery industry More and more, if you encounter situations such as the loss of the Pakistani gun, it is easy to cause unnecessary losses. Therefore, it is very necessary to realize communication and remote control with the Pakistani gun. However, in the prior art, remote control of the Pakistani gun cannot be realized.

Contents of the invention

In order to overcome the problems existing in the related technologies at least to a certain extent, the present application provides a mobile device management and control method, device, and terminal to solve the technical problem that remote control of mobile devices cannot be realized in the prior art.

In order to achieve the above object, the application adopts the following technical solutions:

first,

This application provides a mobile device management and control method, which is applied to a cloud platform, including:

Obtain the user's control instructions;

Control the function items of the mobile device according to the control instruction;

The function items at least include: disabling and enabling.

Further, the acquisition of the user's management and control instructions is specifically:

Receive the user's control instructions sent by the background server;

The background server is deployed in the cloud platform, or,

The background server is wirelessly connected to the cloud platform.

Further, the receiving the user's management and control instruction sent by the background server is specifically:

Receive the Dubbo request sent by the background server, and the Dubbo request carries the user's management and control instructions.

Further, the function item of controlling the mobile device includes:

Sending the management and control instruction to the mobile device through the MQTT protocol, so that the operating system of the mobile device executes the management and control instruction, and then controls the function items of the mobile device;

An MQTT server is deployed in the cloud platform.

Further, the method also includes:

receiving data information reported by the mobile device, the data information at least including: location information, and/or, operation information;

Forwarding the data information to the background server, so that the user of the background server decides whether to manage and control the mobile device according to the data information.

Further, before obtaining the user's management and control instructions, it also includes:

Obtain the device serial code of the newly added mobile device;

According to the device serial code, a key is allocated to the newly added mobile device, so that the mobile device can establish a communication connection with the cloud platform according to the key.

Further, according to the device serial code, assigning a key to the newly added mobile device includes:

Generate an original key according to the device serial code;

Feedback the original key to the user, so that the user sends the device serial code and the original key to the manufacturer of the mobile device, so that the manufacturer burns the original key into the mobile device to be shipped;

When receiving the connection debugging request of the mobile device, based on the original key, establish a communication connection with the mobile device;

After the debugging is successful, a new key is issued to the mobile device to cover the original key burned into the mobile device before.

Second aspect,

This application provides a cloud platform, including:

An acquisition module, configured to acquire the user's management and control instructions;

A control module, configured to control the function items of the mobile device according to the control instruction;

The function items at least include: disabling and enabling.

third aspect,

This application provides a mobile device management and control system, including:

Mobile devices and the aforementioned cloud platform.

Further, the system further includes: a background server deployed in the cloud platform, or wirelessly connected with the cloud platform.

The application adopts the above technical solutions, and at least has the following beneficial effects:

In practical applications, this application obtains the user's management and control instructions, and controls the function items of the mobile device according to the management and control instructions. The function items at least include: disable and enable, so that remote control of the mobile device can be realized. In emergencies, the mobile device can be disabled through the cloud platform to avoid unnecessary losses.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a flow chart showing a mobile device management and control method according to an exemplary embodiment;

Fig. 2 is a schematic diagram of deploying a background server, a cloud platform, and a mobile device according to an exemplary embodiment;

Fig. 3 is a schematic diagram of deploying a background server, a cloud platform, and a mobile device according to another exemplary embodiment;

Fig. 4 is a sequence diagram of a mobile device management and control method according to an exemplary embodiment;

Fig. 5 is a schematic block diagram of a cloud platform shown according to an exemplary embodiment;

Fig. 6 is a schematic block diagram of a mobile device management and control system according to an exemplary embodiment.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be described in detail below. Apparently, the described embodiments are only some of the embodiments of this application, not all of them. Based on the embodiments in the present application, all other implementation manners obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present application.

Please refer to FIG. 1. FIG. 1 is a flowchart of a mobile device management and control method according to an exemplary embodiment. As shown in FIG. 1, the mobile device management and control method includes the following steps:

Step S01 , acquiring user management and control instructions.

Specifically, the management and control instructions include disabling, enabling, locking the screen, application management, WIFI setting, boot animation, system upgrade, etc. of the mobile device.

Step S02. Control the function items of the mobile device according to the management and control instruction; the function items at least include: disabling and enabling.

When a mobile device is lost or stolen, in order to avoid unnecessary loss, it is necessary to control the mobile device on the server side. Take the most commonly used gun in the express industry as an example for a specific description. In some special cases, such as a stolen gun, in order to avoid the disclosure of customer information, it is necessary to control the gun on the server side. The gun is lost and found, and the disable function has been enabled. At this time, the gun cannot be enabled. It needs to issue a control command to enable it on the server. The gun can only be used normally after receiving the command to enable control and execute the operation.

In the practical application of this application, mobile devices include but are not limited to palmtop computers, guns, mobile phones and so on. According to the management and control instructions, controlling the function items of the mobile device can protect the information on the mobile device from being leaked to the greatest extent.

In one embodiment, the acquisition of the user's management and control instructions is specifically:

Receive the user's control instructions sent by the background server;

The background server is deployed in the cloud platform, or,

The background server is wirelessly connected to the cloud platform.

Please refer to FIG. 2-3. FIG. 2-3 is a schematic structural diagram of a mobile device management and control method according to an exemplary embodiment. As shown in FIG. 2, specifically, the cloud platform 5 corresponds to multiple mobile devices 301, When the user wants to control the mobile device 301, the user first needs to send a control request to the background server, the background server sends the request to the cloud platform 5 through Dubbo, and the cloud platform 5 sends the control request to the mobile device 301 through the MQTT protocol. The background server here can be deployed in the cloud platform 5, please refer to Figure 2. It can also be juxtaposed with the cloud platform 5, and the two communicate through a wireless connection, please refer to FIG. 3 . Here, a specific introduction is only made in the manner of FIG. 3 , which does not limit the present application.

In one embodiment, the receiving the user's management and control instruction sent by the background server is specifically:

Receive the Dubbo request sent by the background server, and the Dubbo request carries the user's management and control instructions.

Specifically, under this solution, if the user wants to control the mobile device 301, the user first needs to send a control request to the background server. After receiving the user's control request, the background server converts the control request into a Dubbo request, and the Dubbo request It carries the management and control instructions that the user wants to implement. Dubbo is a distributed framework for remote service calls. It has distinct roles. It can determine whether the service is running normally according to the status of each node role, and can monitor whether the control is in place.

In one embodiment, the controlling the function items of the mobile device 301 includes:

Send the management and control instruction to the mobile device 301 through the MQTT protocol, so that the operating system of the mobile device 301 executes the management and control instruction, and then control the function items of the mobile device 301;

An MQTT server is deployed in the cloud platform 5 .

Specifically, in this solution, the cloud platform 5 and the mobile device 301 communicate with each other through the MQTT protocol. In this way, when the cloud platform 5 receives the management and control instruction, the instruction can be sent to the mobile device 301 through the MQTT protocol. After the mobile device 301 responds to the corresponding instruction, the response information is sent to the cloud platform 5. The queue feeds information back to the user, realizing a closed-loop operation, allowing the user to know the status information of the mobile device 301, and to perform timely management and control operations on the mobile device 301.

The mobile device 301 will connect to the MQTT server in the cloud platform 5 after being connected to the Internet successfully, and perform authentication. After the authentication is passed, the cloud platform 5 will record the online status of the device and send the information to the background server.

In one embodiment, the method also includes:

receiving data information reported by the mobile device, the data information at least including: location information, and/or, operation information;

Forwarding the data information to the background server, so that the user of the background server decides whether to manage and control the mobile device according to the data information.

Specifically, under this solution, the mobile device 301 will proactively report information to the cloud platform 5, such as: the location of the mobile device 301, operation information, and whether the mobile device 301 is working, stopped or in standby. After the cloud platform 5 receives the reported information, it will forward the information to the background server, and the background personnel can decide whether to control the mobile device 301 according to the reported data situation. For example: if the mobile device 301 exceeds the specified geographic location, you can choose the mobile device 301 to issue a warning or execute commands such as locking the screen or disabling the mobile device 301, so as to ensure the security of the information stored in the mobile device 301 and avoid unnecessary losses. .

In one embodiment, before obtaining the user's management and control instructions, it also includes:

Obtain the device serial code of the newly added mobile device;

According to the device serial code, assign a key to the newly added mobile device, so that the mobile device can establish a communication connection with the cloud platform 5 according to the key.

Specifically, before obtaining the user management and control instruction, the device needs to be initialized. When the mobile device 301 is turned on, it is first connected to the WiFi router through the network, and then the mobile device 301 can send a connection request to the MQTT server. The MQTT server is in the cloud platform 5. After the connection is successful, the cloud platform 5 can record the online status of the mobile device 301.

Specifically, obtaining the device serial code of the newly added mobile device 301 is obtained by the user inputting the device serial code into the background server; if the background server is connected to the cloud platform 5, the initialization key and the message secret key are sent to Obtained by the cloud platform 5; if the background server is deployed on the cloud platform 5, it can be obtained by directly reading the initialization key and message key data saved by the background server.

In one embodiment, assigning a key to the newly added mobile device 301 according to the device serial code includes:

Generate an original key according to the device serial code;

Feedback the original key to the user, so that the user sends the device serial code and the original key to the manufacturer of the mobile device, so that the manufacturer burns the original key into the mobile device to be shipped;

When receiving the connection debugging request of the mobile device, based on the original key, establish a communication connection with the mobile device 301;

After the debugging is successful, a new key is issued to the mobile device 301 to cover the original key burned into the mobile device 301 before.

Specifically, the original secret key includes: an initialization key and a message key. After receiving the serial code added by the user, cloud platform 5 automatically generates the initialization key and message key, and sends the key to the user. The user feeds back the initialization key and message key to the manufacturer, and the manufacturer will initialize the key. The key and the message key are burnt into the mobile device 301 to be delivered from the factory. After the burning is completed, the mobile device 301 is connected and debugged with the cloud platform 5 based on the original key to realize mutual communication between the two. After the debugging is successful, the system will issue a new secret key to overwrite the secret key before burning, and the previous secret key will become invalid. This step is equivalent to encrypting the device to prevent the operator from arbitrarily changing the mobile device 301 or changing the serial number. Codes and secret keys are sent to others for use.

Please refer to Fig. 4. Fig. 4 is a sequence diagram of a method for managing and controlling a mobile device 301 according to an exemplary embodiment. As shown in Fig. 4, firstly, the device is initialized, and the user needs to add the device serial number SN Send it to the background server, and request the cloud platform 5 to obtain the original secret key through Dubbo, and return the result to the background server, and feed back the original secret key to the user. The user sends the original secret key and device serial code to the manufacturer of the mobile device 301, and the manufacturer burns the received original secret key and device serial code into the mobile device 301, and the mobile device 301 is connected to the cloud platform 5 for debugging, and the debugging is successful After that, Cloud Platform 5 will issue a new key to overwrite the original key. So far, the initialization of the mobile device 301 is completed.

When the user needs to issue a control command to the mobile device 301, such as the lock screen in Figure 4, the control command of the lock screen will be sent to the background server first, and the background server will send the lock screen control command to the cloud platform 5 through Dubbo request. The platform 5 issues the MQTT protocol carrying the screen lock command to the mobile device 301, and the mobile device 301 executes the action of locking the screen after receiving the MQTT protocol. After the mobile device 301 executes the action of locking the screen, it feeds back the result to the cloud platform 5, and the cloud platform 5 feeds back the execution result of the lock screen to the background server. In addition, you can also execute control commands such as disable, enable, lock screen, application management, WIFI settings, boot animation, system upgrade, etc.

Here, only the background server and the cloud platform 5 are specifically introduced in the case of a wireless connection, and this application is not limited. When the background server is deployed on the cloud platform 5, the same sequence is also used.

Referring to Fig. 5, Fig. 5 is a schematic block diagram of a cloud platform 5 shown in an exemplary embodiment; as shown in Fig. 5, the cloud platform 5 includes:

Obtaining module 501, configured to obtain user management and control instructions;

A control module 502, configured to control the function items of the mobile device according to the management and control instruction;

The function items at least include: disabling and enabling.

Further, the obtaining module 501 is specifically used for:

Receive the user's control instructions sent by the background server;

The background server is deployed in the cloud platform 5, or,

The background server is wirelessly connected with the cloud platform 5 .

Further, the receiving the user's management and control instruction sent by the background server is specifically:

Receive the Dubbo request sent by the background server, and the Dubbo request carries the user's management and control instructions.

Further, the control module 502 controls the function items of the mobile device, including:

Sending the management and control instruction to the mobile device through the MQTT protocol, so that the operating system of the mobile device executes the management and control instruction, and then controls the function items of the mobile device;

An MQTT server is deployed in the cloud platform 5 .

Further, the control module 502 also includes:

receiving data information reported by the mobile device, the data information at least including: location information, and/or, operation information;

Forwarding the data information to the background server, so that the user of the background server decides whether to manage and control the mobile device according to the data information.

With regard to the cloud platform 5 in the above-mentioned related embodiments, the specific manner in which each module executes operations has been described in detail in the above-mentioned related method embodiments, and will not be described in detail here.

In the actual application of this application, the obtaining module 501 is used to obtain the user's management and control instructions, and the control module 502 is used to control the function items of the mobile device 301 according to the management and control instructions, and the function items at least include: disable, enable, In this way, the remote management and control of the mobile device 301 can be realized. When unexpected situations such as loss of the mobile device are encountered, the disabling command can be enabled on the mobile device 301 through the cloud platform 5, thereby avoiding unnecessary losses.

Please refer to FIG. 6. FIG. 6 is a schematic block diagram of a mobile device management and control system according to an exemplary embodiment. As shown in FIG. 6, the mobile device management and control system 6 includes:

The mobile device 301 and the above-mentioned cloud platform 5 .

Regarding the management and control system 6 of the mobile device 301 in the above embodiment, its specific manner has been described in detail in the above embodiments related to the method, and will not be described in detail here.

Further, the mobile device 301 management and control system also includes:

The background server is deployed in the cloud platform 5, or is wirelessly connected with the cloud platform 5.

Regarding the relationship between the background server and the cloud platform 5 in the above embodiment, the specific manner has been described in detail in the above embodiment of the method, and will not be described in detail here.

In the actual application of this application, the mobile device 301 and the above-mentioned cloud platform 5 can realize the remote management and control of the mobile device 301. When encountering unexpected situations such as the loss of the mobile device, the mobile device 301 can be enabled and disabled through the cloud platform 5 order to avoid unnecessary losses.

It can be understood that, the same or similar parts in the above embodiments can be referred to each other, and the content that is not described in detail in some embodiments can be referred to the same or similar content in other embodiments.

It should be noted that in the description of the present application, terms such as "first" and "second" are used for description purposes only, and should not be understood as indicating or implying relative importance. In addition, in the description of the present application, unless otherwise specified, the meanings of "plurality" and "many" refer to at least two.

It should be understood that when an element is referred to as being "fixed" or "disposed to" another element, it can be directly on the other element or there may be intervening elements at the same time; It may be directly connected to another element or there may be intervening elements at the same time. In addition, "connected" as used herein may include a wireless connection; the use of the word "and/or" includes any of one or more of the associated listed items. One unit and all combined.

Any process or method descriptions in flowcharts or otherwise described herein may be understood as representing a module, segment or portion of code comprising one or more executable instructions for implementing specific logical functions or steps of the process , and the scope of preferred embodiments of the present application includes additional implementations in which functions may be performed out of the order shown or discussed, including in substantially simultaneous fashion or in reverse order depending on the functions involved, which shall It should be understood by those skilled in the art to which the embodiments of the present application belong.

It should be understood that each part of the present application may be realized by hardware, software, firmware or a combination thereof. In the embodiments described above, various steps or methods may be implemented by software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or combination of the following techniques known in the art: Discrete logic circuits, ASICs with suitable combinational logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

Those of ordinary skill in the art can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. During execution, one or a combination of the steps of the method embodiments is included.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing module, each unit may exist separately physically, or two or more units may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. If the integrated modules are realized in the form of software function modules and sold or used as independent products, they can also be stored in a computer-readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, and the like.

In the description of this specification, descriptions referring to the terms "one embodiment", "some embodiments", "example", "specific examples", or "some examples" mean that specific features described in connection with the embodiment or example , structure, material or characteristic is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limitations on the present application, and those skilled in the art can make the above-mentioned The embodiments are subject to changes, modifications, substitutions and variations.

Claims (10)

1. A mobile device management and control method is applied to a cloud platform and is characterized by comprising the following steps:

acquiring a control instruction of a user;

controlling a function item of the mobile equipment according to the control instruction;

the functional items include at least: and (4) disabling and enabling.

2. The method according to claim 1, wherein the obtaining of the user management and control instruction specifically comprises:

receiving a control instruction of a user sent by a background server;

the background server is deployed in the cloud platform, or,

the background server is in wireless connection with the cloud platform.

3. The method according to claim 2, wherein the receiving of the user management and control instruction sent by the background server specifically includes:

receiving a Dubbo request sent by a background server, wherein the Dubbo request carries a control instruction of a user.

4. The method of claim 3, wherein controlling the function item of the mobile device comprises:

sending the management and control instruction to the mobile equipment through an MQTT protocol so that an operating system of the mobile equipment executes the management and control instruction and further controls the function items of the mobile equipment;

an MQTT server is deployed in the cloud platform.

5. The method of claim 2, further comprising:

receiving data information reported by a mobile device, wherein the data information at least comprises: location information, and/or, operational information;

and forwarding the data information to the background server so that a user of the background server determines whether to manage and control the mobile device according to the data information.

6. The method according to any one of claims 1 to 5, wherein before acquiring the user's management and control instruction, the method further comprises:

acquiring a device sequence code of the newly added mobile device;

and distributing a secret key for the newly added mobile equipment according to the equipment sequence code so that the mobile equipment establishes communication connection with the cloud platform according to the secret key.

7. The method of claim 6, wherein the assigning the key to the newly added mobile device according to the device serial number comprises:

generating an original key according to the equipment sequence code;

feeding back the original key to a user so that the user sends the device serial code and the original key to a manufacturer of the mobile device, and the manufacturer burns the original key into the mobile device to be shipped from a factory;

when a connection debugging request of the mobile equipment is received, establishing communication connection with the mobile equipment based on the original secret key;

and when the debugging is successful, issuing a new key to the mobile equipment so as to cover the original key burnt to the mobile equipment before.

8. A cloud platform, comprising:

the acquisition module is used for acquiring a control instruction of a user;

the control module is used for controlling the function items of the mobile equipment according to the control instruction;

the functional items include at least: and (4) disabling and enabling.

9. A mobile device management and control system, comprising:

a mobile device and the cloud platform of claim 8.

10. The system of claim 9, further comprising:

and the background server is deployed in the cloud platform or is in wireless connection with the cloud platform.

Images