CN111727615A

CN111727615A - Data management method, data management device, aircraft, mobile terminal, and storage medium

Info

Publication number: CN111727615A
Application number: CN201980012303.6A
Authority: CN
Inventors: 吴忠谦; 海沃
Original assignee: SZ DJI Technology Co Ltd
Current assignee: SZ DJI Technology Co Ltd; Shenzhen DJ Innovation Industry Co Ltd
Priority date: 2019-06-10
Filing date: 2019-06-10
Publication date: 2020-09-29
Also published as: WO2020248106A1

Abstract

A data management method, a data management apparatus, an aircraft, a mobile terminal, and a storage medium, the method comprising: reading status data of a data pattern from a non-volatile memory, initializing service status information according to the status data, the service status information including a prohibition status for indicating prohibition of service networking and/or a permission status for indicating permission of service networking (S110); if the service networking request corresponding to the forbidden state is obtained, intercepting the service networking request (S120); and if the service networking request corresponding to the permission state is acquired, sending the service networking request to a target server to perform data transmission with the server (S130).

Description

Data management method, data management device, aircraft, mobile terminal, and storage medium

Technical Field

The present application relates to the field of data security technologies, and in particular, to a data management method, a data management apparatus, an aircraft, a mobile terminal, and a storage medium.

Background

The software products have long been concerned with data security, especially the security of private data, and european union privacy act was even introduced in 2018 to try to protect the security of private data of users from a legal point of view. However, existing software products still have the problem of confusion in rights management for data networking.

For example, the unmanned aerial vehicle can be widely applied to the fields of judicial evidence obtaining, public security, traffic police, forestry, mining industry, infrastructure construction and the like, and as data of the fields contain various privacy, safety, compliance and other problems, government units and enterprises in the fields have high sensitivity to data safety. How to reduce or eliminate the worry of the government and enterprise users about data security without influencing the business development becomes a problem which is difficult to solve in the industry at present.

Disclosure of Invention

Based on this, the application provides a data management method, a data management device, an aircraft, a mobile terminal and a storage medium, and aims to solve the technical problems that the authority management of data networking is disordered, data on the terminal is easily uploaded to a server by software or the software may acquire the data from the server by the existing data management method.

In a first aspect, the present application provides a data management method, including:

reading status data of a data pattern from a non-volatile memory, initializing service status information according to the status data, the service status information comprising a disabled status for indicating that service networking is disabled and/or a enabled status for indicating that service networking is enabled;

if a service networking request corresponding to the forbidden state is obtained, intercepting the service networking request;

and if the service networking request corresponding to the permission state is acquired, sending the service networking request to a target server to perform data transmission with the server.

In a second aspect, the present application provides a data management apparatus comprising a memory and a processor;

the memory is used for storing a computer program;

the processor is configured to execute the computer program and, when executing the computer program, implement the following steps:

In a third aspect, the present application provides an aircraft comprising:

the data management device is used for controlling whether to send a service networking request to the target server;

the flying assembly is used for flying.

In a fourth aspect, the present application provides a mobile terminal, comprising:

the data management device is used for controlling whether to send a service networking request to the target server.

In a fifth aspect, the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, causes the processor to implement the above-mentioned data management method.

The embodiment of the application provides a data management method, a data management device, an aircraft, a mobile terminal and a storage medium, service state information is initialized according to state data stored in a nonvolatile memory, so that data transmission between the terminal and a server can be prevented or data transmission between the terminal and the server can be allowed according to the service state information; through the communication and data transmission between the service state information management and control terminal and the server, the security of the local data of the terminal is improved, for example, certain data are prevented from being transmitted to the server or the server writes certain data into the terminal.

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.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic flowchart of a data management method according to an embodiment of the present application;

FIG. 2 is a diagram illustrating a state corresponding to service state information in an interface;

FIG. 3 is a schematic flow chart diagram illustrating an embodiment of a data management method of the present application;

FIG. 4 is a schematic flow chart diagram illustrating another embodiment of a data management method of the present application;

FIG. 5 is a schematic flow chart diagram illustrating a further embodiment of a data management method according to the present application;

FIG. 6 is a schematic flow chart diagram illustrating a further embodiment of a data management method according to the present application;

FIG. 7 is a schematic flow chart diagram illustrating a further embodiment of a data management method according to the present application;

FIG. 8 is a schematic flow chart diagram illustrating a further embodiment of a data management method of the present application;

FIG. 9 is a schematic flow chart of the interaction among the service layer, the interceptor and the server in the terminal for implementing the data management method;

fig. 10 is another flow chart illustrating an interaction relationship among a service layer, an interceptor and a server in a terminal for implementing the data management method;

FIG. 11 is a schematic flow chart diagram of a method of implementing data management for a control device of an aircraft;

FIG. 12 is a flow diagram of one embodiment of generating a service networking request;

fig. 13 is a schematic structural view of a terminal and a server implementing the data management method;

FIG. 14 is a schematic block diagram of a data management apparatus according to an embodiment of the present application;

FIG. 15 is a schematic block diagram of an aircraft provided by an embodiment of the present application;

fig. 16 is a schematic block diagram of a mobile terminal according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The flow diagrams depicted in the figures are merely illustrative and do not necessarily include all of the elements and operations/steps, nor do they necessarily have to be performed in the order depicted. For example, some operations/steps may be decomposed, combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.

Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a data management method according to an embodiment of the present application. The data management method can be applied to terminal equipment and is used for managing the processes of data transmission and the like between the terminal equipment and a server; the terminal device can be a mobile phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, a wearable device, a remote control device or an unmanned aerial vehicle, and the server can be an independent server or a server cluster. Further, unmanned aerial vehicle can be rotor type unmanned aerial vehicle, for example, four rotor unmanned aerial vehicle, six rotor unmanned aerial vehicle, eight rotor unmanned aerial vehicle, also can be fixed wing unmanned aerial vehicle.

As shown in fig. 1, the data management method of the present embodiment includes steps S110 to S130.

S110, reading state data of a data mode from a nonvolatile memory, and initializing service state information according to the state data, wherein the service state information comprises a prohibition state for showing prohibition of service networking and/or a permission state for showing permission of service networking.

The non-volatile memory of the terminal stores state data of the data pattern, and the terminal can initialize service state information according to the state data.

In one embodiment, the relationship between the state data and the service state information is shown in table 1.

Table 1 status data and service status information

Status of state	Status data	Service status information
			A	LDM enabled	Disabled state
II	LDM disabled	Permission status

Illustratively, LDM represents a Local Data Mode (Local Data Mode); for example, when the local data mode is turned on, the data on the terminal is only used locally and cannot be sent to a server, such as a server corresponding to software for managing the data or a third-party server; for example, when the local data mode is turned on, the terminal can only use local data, and cannot acquire data from the server.

Illustratively, LDM enabled indicates that the local data mode is in an on state, and LDM disabled indicates that the local data mode is in an off state.

In the embodiment, if the status data read from the nonvolatile memory is LDM enabled, service status information is initialized to a disabled state for indicating that service networking is disabled according to the status data; if the status data read from the nonvolatile memory is LDM disabled, initializing the service status information to be a license status for representing the networking of the license service according to the status data.

For example, the disabled state for indicating that the service networking is disabled may include an LDM enabled state, that is, a state in which a local data mode is turned on, data on the terminal is used only locally and cannot be transmitted to the server, and the terminal can only use the local data and cannot acquire the data from the server; the license status for indicating the networking of the license service may include LDMdisabled, i.e., a status in which the local data mode is off, and data on the terminal may be transmitted to or acquired from the server.

Illustratively, the terminal includes a non-volatile memory, the contents of which are not lost due to power failure and are generally used to store programs or data that do not need to be changed frequently; for example, when the terminal is a mobile phone, the nonvolatile memory includes a Read-only memory (ROM) in the terminal.

Storing state data of the data pattern in a non-volatile memory such that the state data remains unchanged even if the software process is shut down; and after the software is restarted, the service state information corresponding to the state data can still be recovered.

And S120, if the service networking request corresponding to the forbidden state is obtained, intercepting the service networking request.

Illustratively, if software on the terminal generates a service networking request pointing to a certain network address, service state information corresponding to the service networking request is judged according to the service state information.

In some embodiments, said intercepting said service networking request comprises: refraining from sending the service networking request to a target server.

For example, software on the terminal generates a map load request that points to a map load network address located at a map server; and if the software judges that the map loading request corresponds to the forbidden state according to the service state information, intercepting the map loading request to prevent the map loading request from being sent to the map server.

For another example, if the disabled state corresponds to all service networking requests generated by the software, all service networking requests generated by the software are intercepted, so as to prevent the terminal and any server from being connected for data transmission.

Illustratively, intercepting the service networking request comprises: and returning request failure information corresponding to the service networking request to a service layer of the software.

For example, after intercepting a map loading request, the terminal returns request failure information corresponding to the map loading request to a service layer of the software, so that a display interface of the terminal displays the request failure information to inform a user that the service networking request is intercepted and not sent to a corresponding server because service state information corresponding to the service networking request is in a forbidden state.

For example, the request failure information may further include a request permission prompt corresponding to the intercepted service networking request, for example, prompting the user to modify the state data corresponding to the map loading request into the state data corresponding to the permission state.

S130, if the service networking request corresponding to the permission state is obtained, the service networking request is sent to a target server to perform data transmission with the server.

Illustratively, if the software on the terminal judges that the service state information corresponding to the service networking request is in a permission state according to the service state information, the service networking request is sent to the target server for data transmission with the server, for example, local data of the terminal is sent to the server, or the data is obtained from the server and loaded locally on the terminal.

In some embodiments, said sending said service networking request to a target server comprises at least one of:

if the service networking request comprises a firmware upgrading request, sending the service networking request to a firmware upgrading server;

if the service networking request comprises a flight-limiting prohibition request, sending the service networking request to a flight-limiting management server;

if the service networking request comprises a map loading request, sending the service networking request to a map server;

and if the service networking request comprises a data uploading request, sending the service networking request to a data storage server.

The terminal can establish communication connection with the firmware upgrading server by sending a firmware upgrading request to the firmware upgrading server so as to acquire firmware data from the firmware upgrading server and realize firmware upgrading; the terminal can establish communication connection with the flight-restriction management server by sending a flight-restriction prohibition release request to the flight-restriction management server so as to acquire data for releasing a flight-restriction prohibition state from the flight-restriction management server and realize flight-restriction prohibition release; the terminal can establish communication connection with the map server by sending a map loading request to the map server so as to acquire map data from the map server; the terminal can establish communication connection with the data storage by sending a data uploading request to the data storage server so as to upload local data of the terminal to the server for cloud storage.

According to the data management method provided by the embodiment of the application, the service state information is initialized according to the state data stored in the nonvolatile memory, so that data transmission between the terminal and the server can be prevented or data transmission between the terminal and the server can be allowed according to the service state information; through the communication and data transmission between the service state information management and control terminal and the server, the security of the local data of the terminal is improved, for example, certain data are prevented from being transmitted to the server or the server writes certain data into the terminal.

Illustratively, the step S110 reads the status data of the data pattern from the non-volatile memory, and initializes the service status information according to the status data, including: reading state data of a data mode from a local nonvolatile memory when software is started; service state information in the volatile memory is then initialized based on the state data.

Illustratively, the terminal includes a non-volatile memory and a volatile memory; the content in the volatile memory disappears due to power failure, and is usually used as a temporary storage medium for running programs; for example, when the terminal is a mobile phone, the volatile Memory includes a Random Access Memory (RAM) in the terminal.

When the software on the terminal is started, the software reads the state data of the data mode from the nonvolatile memory, and then initializes the service state information in the volatile memory occupied by the software when the software runs according to the state data.

In some embodiments, the state data stored in the local non-volatile memory is encrypted state data.

Illustratively, the initializing service state information in the volatile memory according to the state data includes:

decrypting the state data to obtain service state information corresponding to the state data; the service state information in the volatile memory is then initialized to the decrypted service state information.

Illustratively, the relationship between the encrypted state data and the service state information is shown in table 2.

Table 2 encrypted status data and service status information

Status of state	Status data	Service status information
			A	34erht34334cw5f	LDM enabled
II	Iwxs90skd21hdad5	LDM disabled

By storing the state data in the nonvolatile memory in an encrypted manner, the state data cannot be easily tampered, the reliability of data mode management is further improved, and the security of data on the terminal is improved.

Illustratively, after initializing the service state information in step S110, the method includes: and outputting the state corresponding to the service state information to a display interface.

As shown in fig. 2, the terminal displays the state corresponding to the service state information in the upper right corner of the display interface. Illustratively, the state corresponding to the service state information shown in fig. 2 is a state of local data mode on, i.e., LDM enabled.

Therefore, when the user uses the terminal, the user can observe the service state information of the corresponding software on the terminal and know whether the service networking request is intercepted according to the service state information.

In some embodiments, as shown in fig. 3, the data management method further includes step S140.

And S140, responding to the state modification operation of the user, and modifying the state data of the data mode in the nonvolatile memory.

The user can autonomously set a data mode through state modification operation; the user can independently manage the use permission of the data without worrying about the safety problem of the data, for example, the data of the terminal is not uploaded to the server without authorization or the server sends the data to the terminal without authorization; the user has control right to own data, and has more sense of security to data security.

For example, the user modifies the state data of the terminal to the state data corresponding to the disabled state; during the operation of the unmanned aerial vehicle, if the unmanned aerial vehicle transmits the aerial photography data to the terminal, the terminal intercepts a service networking request sent to the server according to the prohibition state, so that the server cannot acquire the aerial photography data from the terminal. The worry of the user to data safety is reduced, and the unmanned aerial vehicle and the terminal can be used for operation at ease.

For example, when a user wants to use some network services, the local data mode may be temporarily turned off to allow a corresponding service networking request to be sent to a corresponding server so that the corresponding network service can be acquired from the server. For example, the user may modify the state data of the terminal to the state data corresponding to the permission state in a secure and network environment, and thus the terminal may transmit a service networking request to the server and upload aerial data to the server. Therefore, the data security can be protected, and whether the data can be networked or not can be freely controlled under the condition that a user knows; therefore, the user can enjoy the network service and ensure the data safety of the user, and the worry of the user on the data safety when using the software is greatly reduced.

Illustratively, in response to the operation that the user closes the local data mode, the status data is modified from LDM enabled to LDM disabled, so that the terminal can send a service networking request corresponding to the permission status to the target server for data transmission with the server; or responding to the operation that the user opens the local data mode, and modifying the state data from LDMdisabled to LDM enabled, so that the terminal intercepts the service networking request corresponding to the forbidden state.

In some embodiments, the step S140 modifies the state data of the data pattern in the non-volatile memory in response to a state modification operation by a user, including: and modifying the state data of the data mode in the nonvolatile memory in response to a state modification instruction input by a user. Therefore, the user can autonomously set the data mode by inputting the state modification instruction.

Illustratively, the terminal displays a virtual button for state modification, and the user inputs a state modification instruction to the terminal by clicking the virtual button; or the terminal is provided with an entity key corresponding to the state modification instruction or different state data, and the user inputs the state modification instruction to the terminal by clicking the entity key.

In other embodiments, the step S140 modifies the state data of the data pattern in the non-volatile memory in response to a state modification operation by a user, including: and in response to the state modification permission data input or imported by the user, modifying the state data of the data mode in the nonvolatile memory into the state data corresponding to the state modification permission data. So that the user can autonomously set the data mode by the state modification permission data.

Illustratively, the state modification License data is data issued by a software developer to modify state data of the data schema, such as a License (License) issued by the software developer, the License including data encrypted by a specific format. The software on the terminal is provided with an input interface or an import interface of the state modification permission data, and a user can input or import the acquired state modification permission data into the software installed on the terminal; and after the software acquires and decrypts the state modification permission data, modifying the state data into the state data corresponding to the state modification permission data.

For example, if the user imports the software with a license corresponding to the open local data mode, the software modifies the status data to LDM enabled.

In some embodiments, as shown in fig. 4, before modifying the state data of the data pattern in the nonvolatile memory in response to the state modification operation of the user at step S140, step S1401 is included.

S1401, obtaining the verification information input by the user, and judging whether the verification information is matched with the user.

In the present embodiment, the step S140 modifies the state data of the data pattern in the nonvolatile memory in response to the state modification operation by the user, including the step S141.

And S141, if the verification information is matched with the user, responding to the state modification operation of the user, and modifying the state data of the data mode in the nonvolatile memory.

Illustratively, the terminal needs to verify whether the user has the right to modify the state data before modifying the state data of the data pattern. For example, a user needs to input authentication information such as a password and a fingerprint to a terminal, and the terminal judges whether the authentication information is matched with the user; and if the user is determined to have the authority to modify the state data, modifying the state data of the data mode in the nonvolatile memory in response to the state modification operation of the user. Therefore, the safety and the accuracy of the state data of the data mode can be ensured, and the right of a user for autonomously managing the terminal data is ensured.

For example, any modification of the state data requires a prior verification that the user has the right, and the state data is modified in response to a state modification operation of the user only when it is determined that the user has the right and the user permission is obtained.

In some embodiments, after modifying the state data of the data pattern in the nonvolatile memory in response to the state modification operation of the user, step S140 includes: and reading the modified state data from the nonvolatile memory, and initializing service state information in the volatile memory according to the state data.

In this embodiment, after modifying the state data of the data pattern in the nonvolatile memory, the terminal may actively refresh the service state information or refresh the service state information according to the operation of the user without restarting the terminal or restarting software.

Specifically, the terminal reads the modified state data from the nonvolatile memory again, and then initializes the service state information in the volatile memory according to the state data; then, step S120 and step S130 are executed.

Illustratively, after initializing the service state information, the method includes: and outputting the state corresponding to the service state information to a display interface. The state corresponding to the service state information displayed on the terminal display interface is updated in time, so that a user can know whether the service networking request is intercepted or not.

In some embodiments, as shown in fig. 4, step S1402 is included after step S140 modifies the state data of the data pattern in the non-volatile memory in response to a state modification operation by a user.

And S1402, outputting a software restarting prompt to prompt the user to restart the software.

Illustratively, a user restarts software installed on the terminal according to a restart software prompt; after the software is restarted, by executing step S110, the state data of the data pattern modified by the user before the restart is read from the nonvolatile memory, and the service state information is initialized according to the state data; thereby realizing the refreshing of the service state information modified by the user.

In some embodiments, before modifying the state data of the data pattern in the nonvolatile memory in response to the state modification operation of the user, step S140 includes: and if the preset state modification triggering condition is triggered, outputting a state modification prompt corresponding to the state modification triggering condition.

For example, if the software judges that an operation fault occurs and needs to feed back the fault to the server, a corresponding state modification prompt is output to prompt a user whether to modify a prohibition state for indicating prohibition of service networking into a permission state for indicating permission of service networking.

Illustratively, if the terminal acquires the service networking request corresponding to the prohibition state, the request permission prompt corresponding to the service networking request is output.

For example, after acquiring a service networking request corresponding to a forbidden state, a terminal intercepts the service networking request; and if the service networking request corresponds to a higher networking priority, outputting a request permission prompt corresponding to the service networking request.

Illustratively, a certain service networking request is a map loading request, which corresponds to a higher networking priority, since the accuracy of the map may affect the flight mission of the aircraft; and after the service networking request is intercepted, outputting a request permission prompt to prompt a user to modify the state data corresponding to the map loading request into the state data corresponding to the permission state.

Thus, the terminal may prompt the user to modify the status data of the data schema as necessary for the software, the terminal to complete the user-specified task.

For example, after the state modification prompt is output, verification information input by a user is acquired in step S1401, and it is determined whether the verification information matches the user; and if the verification information is matched with the user, modifying the state data of the data mode in the nonvolatile memory in response to the state modification operation of the user.

In some embodiments, as shown in fig. 5, if the service networking request corresponding to the prohibition state is acquired in step S120, intercepting the service networking request includes step S121.

S121, if the service state information comprises global prohibition states corresponding to all the network services, intercepting the service networking request after acquiring any service networking request.

Illustratively, the network service that the terminal needs to cooperate with the server to complete, i.e. the preset network service includes: firmware upgrading, flight restriction and release, map loading, data uploading and the like; each network service corresponds to: the system comprises a firmware upgrading request, a flight-limiting unblocking request, a map loading request, a data uploading request and other service networking requests.

If the initialized service state information comprises a global prohibition state, namely a prohibition state for showing prohibition of all preset network service networking, all service networking requests generated by the terminal correspond to the prohibition state, so that the terminal intercepts all acquired service networking requests, and the terminal can only use local data.

Specifically, the user may set the state data of the data pattern in the nonvolatile memory to the state data corresponding to the global disable state; only this setting is needed to achieve a thorough local data mode in which the terminal cannot send a service networking request to the corresponding server.

Illustratively, the display interface displays an LDM enabled button for indicating that the local data mode is in an on state, and an LDM disabled button for indicating that the local data mode is in an off state. If the LDM enabled button is selected, the local data mode is started, and the state data of the data mode in the nonvolatile memory is set to be the state data corresponding to the global forbidden state; if the LDM disabled button is selected, the local data mode is turned off, and the state data of the data mode in the nonvolatile memory is set to the state data corresponding to the global permission state.

In some embodiments, step S130 sends the service networking request to the target server if the service networking request corresponding to the permission status is acquired, including step S131.

S131, if the service state information includes global permission states corresponding to all network services, the service networking request is sent to a target server after any service networking request is obtained.

If the initialized service state information includes a global permission state, that is, a permission state for indicating permission of all preset network service networking, all service networking requests generated by the terminal correspond to the permission state, so that the terminal does not intercept the acquired service networking requests, and can send any acquired preset service networking request to the target server to perform data transmission with the corresponding server.

Specifically, the user may set the state data of the data pattern in the nonvolatile memory to the state data corresponding to the global permission state; only by the setting, the terminal can normally transmit data with the server when needed, and network services such as firmware upgrading, flight restriction prohibition release, map loading, data uploading and the like can be obtained.

In some embodiments, the initialized service state information includes a global disabled state or a global enabled state; in other embodiments, the initialized service state information may include at least one of a plurality of prohibited states, a plurality of permitted states, a single prohibited state, and a single permitted state; the various disabled states or enabled states may correspond to one or more service networking requests.

For example, as shown in fig. 6, if the service networking request corresponding to the prohibition state is acquired in step S120, intercepting the service networking request includes step S122.

S122, if the service state information comprises a plurality of forbidden states corresponding to a plurality of network services, intercepting the service networking request after acquiring any service networking request corresponding to the plurality of forbidden states.

Exemplarily, as shown in table 3, the service state information obtained by the terminal corresponds to the service networking request.

Table 3 service status information service networking request correspondence

As shown in table 3, the terminal divides the service networking requests corresponding to the network services into a plurality of groups, such as a first group and a second group; the first group comprises a firmware upgrading request corresponding to firmware upgrading and a flight-limiting and forbidding request corresponding to flight-limiting and forbidding, and the second group comprises a map loading request corresponding to map loading and a data uploading request corresponding to data uploading.

Illustratively, if the initialized service state information includes a plurality of prohibition states corresponding to the first set of service networking requests, the terminal intercepts any one of the first set of service networking requests if the service networking request is acquired.

Specifically, the user can manage the terminal to intercept the service networking requests of multiple network services by setting the service state information corresponding to each group of service networking requests as multiple prohibition states.

In some embodiments, as shown in fig. 6, if the service networking request corresponding to the permission status is acquired in step S130, the step S132 is included to send the service networking request to the target server.

S132, if the service state information comprises a plurality of permission states corresponding to a plurality of network services, sending the service networking request to a target server after any service networking request corresponding to the plurality of permission states is acquired.

As shown in table 3, the terminal divides the service networking requests corresponding to the respective network services into a plurality of groups, such as a first group and a second group.

Illustratively, if the initialized service state information includes a plurality of permission states corresponding to the second group of service networking requests, the terminal sends any service networking request in the second group of service networking requests to the target server for data transmission with the corresponding server if the service networking request is acquired.

Specifically, the user can manage the service networking requests of the terminal for releasing various network services by setting the service state information corresponding to each group of service networking requests as a plurality of permission states, so that the terminal can normally transmit data with the server when needed, and acquire various network services such as map loading, data uploading and the like.

In some embodiments, as shown in fig. 6, if the service networking request corresponding to the prohibition state is acquired in step S120, intercepting the service networking request includes step S123.

S123, if the service state information comprises a single prohibition state corresponding to one network service, intercepting the service networking request after the service networking request corresponding to the single prohibition state is obtained.

For example, the user may set the global state corresponding to the state data to a global prohibition state or a global permission state, may set the service state information corresponding to each group of service networking requests to a multiple prohibition state or a multiple permission state, and may set the service state information corresponding to each service networking request to a single prohibition state or a single permission state.

Illustratively, as shown in table 4, a display interface when the user sets the status data corresponding to the service status information is shown.

TABLE 4 status data set interface

For example, as shown in table 4, if the service state information corresponding to the set of service networking requests, that is, the multiple states are multiple prohibition states, is set by the user, the service state information, that is, the single state, of each service networking request in the set is automatically set to the single prohibition state.

Illustratively, if the user sets the global state as the global prohibition state, the multiple states of each group are automatically set as the multiple prohibition states, and the single state of each service networking request is automatically set as the single prohibition state; if the user sets the global state as the global permission state, the multiple states of each group are automatically set as the multiple permission states, and the single state of each service networking request is automatically set as the single permission state.

For example, as shown in table 4, the user sets the service state information corresponding to the map loading request, that is, the single state is a single prohibition state, and the single state of the data uploading request is a single permission state. The single states of the service networking requests in the same group are inconsistent, so that the multiple states corresponding to the group are invalid states; since the states of the different groups of items are not consistent, the global state is also an invalid state.

Illustratively, the service state information includes a single prohibition state corresponding to the map loading request, and the service networking request, such as the map loading request, corresponding to the single prohibition state is intercepted after the service networking request is acquired, so that the terminal is not communicatively connected with the server providing the map loading service to perform data transmission.

Specifically, the user sets the service state information corresponding to a certain service networking request to be a single prohibition state in a targeted manner, so that data transmission between the terminal and a specific server can be accurately prevented.

For example, as shown in fig. 6, if the service networking request corresponding to the permission status is acquired in step S130, the step S133 is included to send the service networking request to the target server.

S133, if the service state information includes a single permission state corresponding to one network service, the service networking request is sent to a target server after the service networking request corresponding to the single permission state is acquired.

Illustratively, the service state information includes a single permission state corresponding to the data upload request, and after a service networking request corresponding to the single permission state, such as a data upload request, is acquired, the service networking request is sent to the target server to be in communication connection with the corresponding server for data transmission.

Specifically, the user sets the service state information corresponding to a certain service networking request to be a single permission state in a targeted manner, so that the terminal and a specific server can be accurately released to perform data transmission, and a certain data service can be acquired.

In some embodiments, as shown in fig. 7, after initializing service status information according to the status data in step S110, step S101 is included.

S101, adjusting the characteristics of the request to be released in the local virtual private network according to the service state information.

Illustratively, the terminal locally opens a Virtual Private Network (VPN) as an interceptor (interceptor), and can acquire data before all requests reach the physical port in the VPN.

Exemplarily, if the service state information includes a global permission state, taking a request feature of each service networking request corresponding to the global permission state as a to-be-released request feature, for example, taking a domain name of each service networking request as the to-be-released request feature; and if the service state information comprises a single permission state corresponding to a certain service networking request, taking the domain name of the service networking request as a to-be-released request feature, and not taking the request features corresponding to a single prohibition state, a plurality of prohibition states and a global prohibition state as the to-be-released request feature.

For example, as shown in fig. 7, if the service networking request corresponding to the prohibition state is acquired in step S120, intercepting the service networking request includes step S1201 and step S1202.

S1201, if a service networking request is acquired, sending the service networking request to the local virtual private network.

Specifically, before the service networking request is sent to the physical network port, the virtual private network first obtains the service networking request.

S1202, if the service networking request is not matched with the characteristics of the request to be released in the adjusted local virtual private network, the service networking request is intercepted.

For example, if the domain name of the service networking request acquired by the virtual private network at a certain time is different from all the characteristics of the request to be released, the service networking request is judged to correspond to a forbidden state, and the service networking request is intercepted.

For example, as shown in fig. 7, if the service networking request corresponding to the permission status is acquired in step S130, the step S1301 of sending the service networking request to the target server to perform data transmission with the server includes.

S1301, if the service networking request is matched with at least one characteristic of the request to be released in the adjusted local virtual private network, the service networking request is sent to a target server.

For example, if the domain name of the service networking request acquired by the virtual private network at a certain time is the same as the characteristic of a certain request to be released, the service networking request is determined to correspond to the permission state, the service networking request is released, and the service networking request is sent to the target server.

According to the characteristics of the request to be released in the virtual private network, the service networking request corresponding to the forbidden state and the service networking request corresponding to the targeted releasing permission state can be comprehensively and accurately filtered.

In other embodiments, as shown in fig. 8, step S102 is included after step S110 initializes service status information according to the status data.

S102, adjusting the request characteristics in the white list and/or the black list according to the service state information.

Illustratively, the terminal maintains a release white list according to the service state information as a condition for the interceptor to decide to intercept or release the service networking request. For example, if the service state information includes a global permission state, the request feature of each service networking request corresponding to the global permission state is used as the request feature in the release white list, for example, the domain name of each service networking request is used as the request feature in the release white list; and if the service state information comprises a single permission state corresponding to a certain service networking request, taking the domain name of the service networking request as a request feature in a release white list, and not taking the request feature corresponding to the single prohibition state, the multiple prohibition states and the global prohibition state as the request feature in the release white list.

Illustratively, the terminal maintains an interception blacklist based on the service status information. For example, if the service state information includes a global prohibition state, the request feature of each service networking request corresponding to the global prohibition state is used as the request feature in the interception blacklist, for example, the domain name of each service networking request is used as the request feature in the interception blacklist; if the service state information comprises a single prohibition state corresponding to a certain service networking request, the domain name of the service networking request is used as the request feature in the interception blacklist, and the request feature corresponding to a single permission state, a plurality of permission states and a global permission state is not used as the request feature in the interception blacklist.

For example, as shown in fig. 8, if the service networking request corresponding to the prohibition state is acquired in step S120, intercepting the service networking request includes step S1203 and step S1204.

S1203, if a service networking request is obtained, judging whether the service networking request is matched with the request characteristics in the released white list and/or the intercepted black list.

For example, after a service networking request is obtained, it is determined whether the domain name of the service networking request is the same as the request characteristics in the white list and/or the interception black list.

S1204, if the service networking request is matched with at least one request feature in the adjusted interception blacklist and/or the service networking request is not matched with the request feature in the adjusted release white list, intercepting the service networking request.

For example, if the service networking request has the same characteristics as a certain request in the interception blacklist, the service networking request is intercepted if the service networking request is determined to correspond to the prohibition state.

For example, if the service networking request does not match all request features in the white list, it is determined that the service networking request corresponds to a prohibited state, and the service networking request is intercepted.

For example, as shown in fig. 8, if the service networking request corresponding to the permission status is acquired in step S130, the step S1302 of sending the service networking request to the target server for data transmission with the server is included.

S1302, if the service networking request is matched with at least one request feature in the adjusted release white list, and/or the service networking request is not matched with the request feature in the adjusted interception blacklist, sending the service networking request to a target server.

For example, if the service networking request has the same characteristics as one of the requests in the released white list, the service networking request is released and sent to the target server if the service networking request is determined to correspond to the permission state.

For example, if the service networking request is not matched with all request characteristics in the interception blacklist, the service networking request is determined to correspond to the prohibition state, the service networking request is released, and the service networking request is sent to the target server.

According to the released white list and/or the blocked black list maintained by the service state information, the service networking request corresponding to the forbidden state and the service networking request corresponding to the targeted released permission state can be comprehensively and accurately filtered.

In some embodiments, if the software is first installed, then at first boot up, the Local Data Mode (LDM) is turned on by default, during which any network requests are filtered and cannot be sent to the internet. The status data read from the non-volatile memory corresponds to a global inhibit status. For example, when the software is installed and started for the first time, the local data mode is acquiescently in an open state, namely LDM enabled; data on the terminal can only be saved for local use and is prohibited from being sent to the server.

Initializing service state information according to the state data includes: and initializing service state information into a global forbidden state corresponding to all network services according to the state data. And the terminal intercepts the service networking request after acquiring any service networking request.

Fig. 9 is a schematic diagram of an interaction relationship between a software service layer, an interceptor and a server in an implementation scenario, which includes the following steps 21 to S293.

And S21, starting the first installation of the software.

And S22, initializing the service state information to be a global forbidden state, and adjusting the interceptors.

Specifically, the interceptor adjusts the request feature to be released in the local virtual private network or adjusts the request feature in the release white list and/or the interception black list according to the global prohibition state.

S231, the software business layer generates a service networking request.

And S232, the interceptor intercepts the service networking request according to the global forbidden state.

And S233, the interceptor feeds back the request failure information to the service layer.

Specifically, when the software business layer generates a service networking Request, such as a Network Request, the interceptor intercepts the service networking Request according to the global prohibition state, and feeds back Request failure information to the business layer.

And S24, starting the software again.

When the software is started again, the service state information is still initialized to the globally disabled state since the state data in the non-volatile memory has not been modified.

And S251, the software business layer generates a service networking request.

And S252, the interceptor intercepts the service networking request according to the global forbidden state.

And S253, the interceptor feeds back the request failure information to the service layer.

And S26, modifying the service state information corresponding to the map loading request into a permission state.

Specifically, in response to a state modification instruction input by a user, service state information corresponding to at least one service networking request is modified from a prohibition state to a permission state. For example, the service state information corresponding to the Map loading Request is modified from a forbidden state to a single permission state through a state modification instruction Enable Map Request. Specifically, after modifying the state data of the data mode in the nonvolatile memory, the terminal may actively refresh the service state information or refresh the service state information according to the operation of the user; or after the state data of the data mode in the nonvolatile memory is modified, prompting a user to restart the software so as to refresh the service state information corresponding to the map loading request into a single permission state.

S271, the interceptor releases the map loading request generated by the software business layer, and sends the map loading request to the server.

And S272, acquiring the map data from the server.

Specifically, when the software business layer generates a Map loading Request, such as a Map Request, the interceptor sends the Map loading Request to a target server, such as a Map server, according to a single permission state corresponding to the Map loading Request, so that the terminal and the target server perform data transmission, for example, Map data is loaded from the Map server.

And S28, modifying the service state information corresponding to the map loading request into a forbidden state.

Specifically, after the map data loading is completed, the user may perform a status modification operation to modify the service status information corresponding to the map loading Request from a single permission status to a prohibition status, for example, modify the service status information corresponding to the map loading Request from the single permission status to the single prohibition status through a status modification instruction DisableMap Request. Specifically, after modifying the state data of the data mode in the nonvolatile memory, the terminal may actively refresh the service state information or refresh the service state information according to the operation of the user; or after the state data of the data mode in the nonvolatile memory is modified, prompting a user to restart the software so as to refresh the service state information corresponding to the map loading request into a single forbidden state.

And S291, the software business layer generates a map loading request.

And S292, the interceptor intercepts the map loading request according to the prohibition state.

S293, the interceptor feeds back the request failure information to the service layer.

When the software business layer generates a Map loading Request, such as Map Request, the interceptor intercepts the Map loading Request according to the single permission state, the global prohibition state or the multiple prohibition states corresponding to the Map loading Request, and feeds back Request failure information to the business layer.

In other embodiments, the state data read from the non-volatile memory corresponds to a global license status if the software is first booted. For example, when the software is installed and started for the first time, the local data mode defaults to an off state, i.e., LDMdisabled; the data on the terminal can be sent to the server or can be acquired from the server.

Initializing service state information according to the state data includes: initializing service state information to a global license state corresponding to all network services according to the state data, wherein the plurality of network services at least comprise a registration service and a login service.

Illustratively, if the service networking request corresponding to the permission status is acquired, the sending of the service networking request to the target server for data transmission with the server includes: and if the service networking request corresponding to the registration service is acquired, sending the service networking request to a server corresponding to the registration service. And if the service networking request corresponding to the login service is obtained, sending the service networking request to a server corresponding to the login service.

Therefore, when the software is installed and started for the first time, the user can register and/or log in the server.

Fig. 10 is a schematic diagram of an interaction relationship between a software service layer, an interceptor and a server in an implementation scenario, which includes the following steps 31 to S393.

And S31, starting the first installation of the software.

And S32, initializing the service state information into a global permission state, and adjusting the interceptors.

Specifically, the interceptor adjusts the request feature to be released in the local virtual private network or adjusts the request feature in the release white list and/or the interception black list according to the global permission state.

And S331, the interceptor passes the service networking request corresponding to the login service and sends the service networking request to the server.

Since the service state information includes the global permission states corresponding to all the network services including the login service, the login service is transmitted to the target server after the login service is acquired. Before the service status information is not modified, such as the local data mode is not turned on, a service networking request may be solicited to the server for network service.

S332, the server feeds back information of successful login.

After receiving the login service sent by the terminal, the server verifies the login information; and if the verification is passed, feeding back information of successful login to the terminal.

And S341, the interceptor releases the service networking request generated by the software business layer and sends the service networking request to the server.

Since the service status information includes global license statuses corresponding to all network services, the service networking request is sent to the target server after any service networking request is acquired.

And S342, acquiring service data from the server.

And after receiving the service networking request sent by the terminal, the server sends service data, such as map data or firmware data, to the terminal according to the service networking request.

And S35, modifying the service state information into a global prohibition state.

Specifically, the user may perform a state modification operation to modify the service state information to a global disabled state. The service status information is modified to a global disabled status, for example by a status modification instruction Enable LDM. Specifically, after modifying the state data of the data mode in the nonvolatile memory, the terminal may actively refresh the service state information or refresh the service state information according to the operation of the user; or after the state data of the data mode in the nonvolatile memory is modified, prompting a user to restart the software so as to refresh the service state information into a global forbidden state.

For example, after the user modifies the local data mode to the on state, any service networking request is filtered by the interceptor and cannot be sent to the internet.

S361, the software business layer generates a service networking request.

And S362, the interceptor intercepts the service networking request according to the global forbidden state.

And S363, the interceptor feeds back the request failure information to the service layer.

And S37, starting the software again.

And S381, the software business layer generates a service networking request.

And S382, the interceptor intercepts the service networking request according to the global forbidden state.

S383, the interceptor feeds back the request failure information to the service layer.

S391, modifying the service state information corresponding to the map loading request into a permission state.

Illustratively, the user operates in a state data setting interface as shown in Table 4 to modify the service state information.

S392, the interceptor releases the map loading request generated by the software business layer and sends the map loading request to the server.

And S393, obtaining the map data from the server.

Specifically, except that the service networking request with the service status information in the permission status is released by the interceptor and sent to the server, any other service networking request is intercepted by the interceptor.

S411, the software service layer generates a firmware upgrading request.

And S412, the interceptor intercepts the firmware upgrading request according to the prohibition state.

And S413, the interceptor feeds back the request failure information to the service layer.

Since step S391 only modifies the service state information corresponding to the map loading request to a permission state, and the service state information corresponding to the firmware upgrading request is regarded as a prohibition state, the interceptor intercepts the firmware upgrading request according to the prohibition state, and feeds back request failure information to the service layer.

And S42, modifying the service state information into a global license state.

Specifically, the user may perform a state modification operation to modify the service state information into a global license state. The service status information is modified to a global license status, for example by a status modification instruction Disable LDM. Specifically, after modifying the state data of the data mode in the nonvolatile memory, the terminal may actively refresh the service state information or refresh the service state information according to the operation of the user; or after the state data of the data mode in the nonvolatile memory is modified, prompting a user to restart the software so as to refresh the service state information into a global license state.

And S431, the interceptor releases the firmware upgrading request generated by the software service layer and sends the firmware upgrading request to the server.

S432, acquiring firmware upgrading data from the server.

Specifically, when the software service layer generates a firmware upgrade request, the interceptor sends the firmware upgrade request to a target server, such as a firmware upgrade server, according to the global permission state corresponding to the firmware upgrade request, so that the terminal performs data transmission with the target server, for example, loads firmware data from the firmware server, thereby implementing firmware upgrade.

Fig. 11 is a schematic flow chart of a method for implementing data management by a control device of an aircraft. The control device may be, for example, an electronic device, such as a mobile phone, tablet, remote control device, etc., of a user of the aircraft, for remotely controlling the aircraft, configuring parameters of the aircraft, and/or performing data transmission with the aircraft.

As shown in fig. 11, the control apparatus implementing the data management method includes the following steps S510 to S620.

S510, after the software on the control device is started, the software reads the state of the local data mode from the local nonvolatile memory of the remote control device.

And S520, judging whether the state of the read local data mode is an open state (LDM enabled) or a closed state (LDM disabled).

If the state of the local data mode is an off state, the service state information includes global permission states corresponding to all network services at this time; the control device executes steps S531 to S610.

S531, generating an msdk (mobile gateway Software Development kit) request, such as a registration request, a login request, and a geographic location reporting request.

S532, generating a software request, wherein the software request is, for example, a networking request sent to a server of a software service party, namely, a software server; for example, the software request is a networking request for communicating with a Flight Hub (Flight Hub), or a networking request for obtaining software or firmware update services.

S533, generating a third party request, where the third party request is, for example, a networking request sent to a server of a non-software service party, that is, a third party server, such as a server providing map data; for example, the third party request is a request for map loading or an abnormal report request.

S540, the control device interacts with the aircraft, such as remotely controlling the aircraft, configuring aircraft parameters, and/or performing data transmission with the aircraft; the method comprises the steps that the control device sends a networking request to the software server or a third-party server, for example, the control device sends a firmware upgrading request to the firmware upgrading server to establish a communication link between the control device and the firmware upgrading server, and then firmware updating data is obtained from the firmware upgrading server to send the firmware updating data to the aircraft and control the aircraft to update the firmware.

After the interaction task of the control device and the aircraft has ended, the user can choose whether to modify the state of the local data pattern, for example from an off state to an on state.

S551, judging whether the local data mode is started or not.

And if the state modification operation of the user is detected, modifying the local data mode from the closed state to the open state, and verifying the authority of the user. And if the state modification operation of the user is not detected, ending the operation.

S552, judging whether the authority verification is passed; for example, whether the authentication information matches the user is determined according to authentication information such as a password and a fingerprint of the user. And if the authority verification is not passed, ending.

And S553, if the authority verification is passed, saving the opened state of the local data mode to a local nonvolatile memory.

And S610, restarting software to read the state of the local data mode modified by the user from the nonvolatile memory after restarting.

After judging that the read state of the local data mode is an on state (LDM enabled) or an off state (LDM disabled) at S520, if the state of the local data mode is the on state, the service state information at this time includes global disabled states corresponding to all network services; the control device executes steps S561 to S620.

In some embodiments, the state of the local data pattern resembles a tree structure, including the state of the global local data pattern and the state of the local data pattern of each submodule. If the status of the overall local data mode is in the on state, the status of the local data mode of each sub-module is set to on, as shown in steps S561, S563, and S564.

S561, setting a local data mode of the MSDK request to be on; the MSDK request includes a registration request, a login request, a geographical location reporting request, etc., and service state information corresponding to the MSDK request may be initialized to a plurality of prohibited states.

And S562, initializing an MSDK manager. Illustratively, the steps allowed to be performed when the control device is not logged on are performed by initializing the MSDK manager.

S563, setting the local data mode of the software request to be started; service state information corresponding to the software request may be initialized to a plurality of disabled states.

S564, setting the local data mode requested by the third party to be on; the service state information corresponding to the third party request may be initialized to a plurality of disabled states.

And S570, the control device interacts with the aircraft, such as remote control of the aircraft, configuration of aircraft parameters, data transmission with the aircraft and the like. The method comprises the step that the control device sends a networking request to the software server or a third-party server, for example, the control device sends a firmware upgrading request to a firmware upgrading server.

S580, the control device intercepts any data sent to the server. The state of the overall local data mode is an open state, and the state of the local data mode of each sub-module is set to be open; any network request sent to the server will be intercepted by the control terminal.

After the interaction task of the control device and the aircraft has ended, the user can choose whether to modify the state of the local data pattern, for example from an on state to an off state.

And S591, judging whether to close the local data mode.

And if the state modification operation of the user is detected, modifying the local data mode from the open state to the closed state, and verifying the authority of the user. And if the state modification operation of the user is not detected, ending the operation.

S592, judging whether the authority verification is passed; for example, whether the authentication information matches the user is determined according to authentication information such as a password and a fingerprint of the user. And if the authority verification is not passed, ending.

S593, if the authority is verified, the state of closing the local data mode is saved to a local nonvolatile memory.

And S620, restarting software to read the state of the local data mode modified by the user from the nonvolatile memory after restarting.

In some embodiments, the obtaining a service networking request comprises: and if a preset service request triggering condition is triggered, generating a service networking request corresponding to the service request triggering condition.

Illustratively, if a certain operation of a user is acquired, it is determined that a service request triggering condition corresponding to the operation is triggered, and a service networking request corresponding to the operation is generated; for example, when a user clicks a button for uploading local data, a data uploading request is generated; or when the user clicks the button for the flight restriction prohibition, generating a flight restriction prohibition request.

For example, the terminal presets a regular task condition, for example, if a firmware upgrade server is queried every month for whether new firmware needs to be upgraded, the terminal generates a firmware upgrade request when the time of the board task condition is met.

Illustratively, as shown in fig. 12, the generating of the service networking request corresponding to the service request triggering condition includes steps S150 to S160.

S150, obtaining service request data corresponding to the service request triggering condition.

Illustratively, the service request data corresponding to the service request triggering condition includes data such as an account number, a password, a terminal physical address, firmware version information, and device use duration of a user; the service networking request generated by the terminal needs to include the information so that the server can perform processes such as permission judgment and the like.

For example, the step S150 of obtaining the service request data corresponding to the service request triggering condition includes: if the service request triggering condition corresponds to the privacy data of the user, authorization request information is output; and responding to the authorization permission input by the user, and acquiring service request data corresponding to the service request triggering condition.

For example, if the required service request data includes the privacy data of the user when a certain service networking request is generated, outputting authorization request information, such as popping up an authorization window; after obtaining the authorization permission input by the user, the privacy data in the service request data can be obtained, and then the service networking request is generated.

And S160, carrying out anonymization processing and secret key signature processing on the service request data to obtain a service networking request.

For example, the service request data may be anonymized and used to generate the service networking request before being encrypted using the key; to protect the data security and privacy of the user.

Fig. 13 is a schematic structural diagram of a terminal and a server.

The state control module 51 of the terminal is used for setting service state information. For example, the state control module 51 is a controller of the local data mode LDM, and is used for receiving a command of a user to turn on or off the local data mode. Illustratively, the state control module 51 is responsible for managing the life state of the entire service state information, and the service state information can still take effect when the software on the terminal is restarted after being closed; unless the user writes to the reinstalled software or clears all cached data.

The interception module 52 is used for adjusting the networking requests needing to be intercepted or released according to the service state information. If the local data mode is started by a user, any network request can be intercepted and request failure information is sent to a service layer to process errors; and the local data mode is transparent to the service of the upper layer, and the developer does not need to care about the fact that the network request is sent to the server when the local data mode is started after the service layer adds a new network request. If the local data mode is turned off by the user, any network request is passed to the server for data transmission with the server.

The request triggering module 53 is an initiator of the service networking request, and if the parameters require the private data of the user, an authorization window is popped up, and the networking request can be initiated after the permission of the user is obtained.

The request processing module 54 is used for anonymizing the request data output by the request triggering module 53 and adding a signature by using a key before being used for sending to the server.

The network interface 55 of the server is used to obtain data transmitted from the terminal from the internet or transmit data to the terminal.

The right verifying module 56 is used for checking the signature of the data sent by the terminal and confirming whether the requested data of the terminal has the access right.

The service module 57 is configured to provide specific cloud services, for example, obtain map data requested by the terminal from a database, and then send the map data to the terminal through the network interface 55.

The database 58 is used for storing data, and corresponding encryption and decryption processing is carried out when the data of the server relates to reading and writing of the database, but the data is not stored in the clear.

Referring to fig. 14, fig. 14 is a schematic block diagram of a data management apparatus 600 according to an embodiment of the present application. The data management apparatus 600 includes a processor 601 and a memory 602, and the processor 601 and the memory 602 are connected by a bus 603, such as an I2C (Inter-integrated Circuit) bus 603.

Specifically, the Processor 601 may be a Micro-controller Unit (MCU), a Central Processing Unit (CPU), a Digital Signal Processor (DSP), or the like.

Specifically, the Memory 602 may be a Flash chip, a Read-Only Memory (ROM) magnetic disk, an optical disk, a usb disk, or a removable hard disk.

The processor 601 is configured to run a computer program stored in the memory 602, and when executing the computer program, implement the foregoing data management method.

Illustratively, the processor 601 is configured to run a computer program stored in the memory 602 and to implement the following steps when executing the computer program:

Referring to fig. 15, fig. 15 is a schematic block diagram of an aircraft 10 according to an embodiment of the present application.

As shown in fig. 15, the aircraft 10 includes:

the data management device 600 is configured to control whether to send a service networking request to a target server;

and the flying assembly 11 is used for flying.

Referring to fig. 16, fig. 16 is a schematic block diagram of a mobile terminal 20 according to an embodiment of the present application.

As shown in fig. 16, the mobile terminal 20 includes:

the data management device 600 is used to control whether to send a service networking request to a target server.

Illustratively, the mobile terminal 20 may be a mobile phone, tablet, remote control device, or the like.

According to the data management device, the aircraft and the mobile terminal provided by the embodiment of the application, the service state information is initialized according to the state data stored in the nonvolatile memory, so that data transmission between the terminal and the server can be prevented or data transmission between the terminal and the server can be allowed according to the service state information; through the communication and data transmission between the service state information management and control terminal and the server, the security of the local data of the terminal is improved, for example, certain data are prevented from being transmitted to the server or the server writes certain data into the terminal.

In an embodiment of the present application, a computer-readable storage medium is further provided, where a computer program is stored in the computer-readable storage medium, where the computer program includes program instructions, and the processor executes the program instructions to implement the steps of the data management method provided in the foregoing embodiment.

The computer-readable storage medium may be an internal storage unit of the data management device according to any of the foregoing embodiments, for example, a hard disk or a memory of the data management device. The computer readable storage medium may also be an external storage device of the data management apparatus, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the data management apparatus.

While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for managing data, comprising:

2. The data management method of claim 1, wherein the reading of the status data from the non-volatile memory, and the initializing of the service status information according to the status data, comprises:

reading state data of a data mode from a local nonvolatile memory when software is started;

and initializing service state information in the volatile memory according to the state data.

3. The data management method of claim 2, wherein the status data is encrypted status data, and the initializing service status information in the volatile memory according to the status data comprises:

decrypting the state data to obtain service state information corresponding to the state data;

and initializing the service state information in the volatile memory into the service state information obtained by decryption.

4. The data management method of claim 2, further comprising:

modifying the state data of the data pattern in the non-volatile memory in response to a state modification operation by a user.

5. The data management method of claim 4, wherein modifying the state data of the data pattern in the non-volatile memory in response to a state modification operation by a user comprises:

and modifying the state data of the data mode in the nonvolatile memory in response to a state modification instruction input by a user.

6. The data management method of claim 4, wherein modifying the state data of the data pattern in the non-volatile memory in response to a state modification operation by a user comprises:

and in response to the state modification permission data input or imported by the user, modifying the state data of the data mode in the nonvolatile memory into the state data corresponding to the state modification permission data.

7. The data management method of claim 4, wherein before modifying the state data of the data pattern in the non-volatile memory in response to the user's state modification operation, the method comprises:

acquiring verification information input by a user, and judging whether the verification information is matched with the user;

the modifying the state data of the data pattern in the non-volatile memory in response to a state modification operation by a user comprises:

and if the verification information is matched with the user, modifying the state data of the data mode in the nonvolatile memory in response to the state modification operation of the user.

8. The data management method of claim 4, wherein after modifying the state data of the data pattern in the non-volatile memory in response to the user's state modification operation, the method comprises:

and reading the modified state data from the nonvolatile memory, and initializing service state information in the volatile memory according to the state data.

9. The data management method of claim 4, wherein after modifying the state data of the data pattern in the non-volatile memory in response to the user's state modification operation, the method comprises:

and outputting a restart software prompt to prompt the user to restart the software.

10. The data management method of claim 4, wherein before modifying the state data of the data pattern in the non-volatile memory in response to the user's state modification operation, the method comprises:

and if the preset state modification triggering condition is triggered, outputting a state modification prompt corresponding to the state modification triggering condition.

11. The data management method according to claim 10, wherein if a preset state modification trigger condition is triggered, outputting a state modification prompt corresponding to the state modification trigger condition, including:

and if the service networking request corresponding to the forbidden state is acquired, outputting a request permission prompt corresponding to the service networking request.

12. The data management method according to any one of claims 1 to 11, wherein after initializing the service state information, comprising:

and outputting the state corresponding to the service state information to a display interface.

13. The data management method according to claim 1, wherein intercepting the service networking request if the service networking request corresponding to the prohibition state is acquired comprises:

and if the service state information comprises global prohibition states corresponding to all the network services, intercepting the service networking request after acquiring any service networking request.

14. The data management method according to claim 1, wherein the sending the service networking request to a target server if the service networking request corresponding to the permission status is obtained comprises:

and if the service state information comprises global permission states corresponding to all network services, sending the service networking request to a target server after any service networking request is obtained.

15. The data management method according to claim 1, wherein intercepting the service networking request if the service networking request corresponding to the prohibition state is acquired comprises:

if the service state information comprises a plurality of forbidden states corresponding to a plurality of network services, intercepting the service networking request after acquiring any service networking request corresponding to the plurality of forbidden states.

16. The data management method according to claim 1, wherein the sending the service networking request to a target server if the service networking request corresponding to the permission status is obtained comprises:

and if the service state information comprises a plurality of permission states corresponding to a plurality of network services, sending the service networking request to a target server after any service networking request corresponding to the plurality of permission states is acquired.

17. The data management method according to any one of claims 1 to 11, 15, or 16, wherein intercepting the service networking request if the service networking request corresponding to the prohibition state is acquired comprises:

if the service state information comprises a single prohibition state corresponding to one network service, intercepting the service networking request after the service networking request corresponding to the single prohibition state is acquired.

18. The data management method according to any one of claims 1 to 11, 15, or 16, wherein the sending the service networking request to a target server if the service networking request corresponding to the permission status is obtained includes:

and if the service state information comprises a single permission state corresponding to one network service, sending the service networking request to a target server after the service networking request corresponding to the single permission state is obtained.

19. The data management method of any of claims 1-11, 13-16, wherein intercepting the service networking request comprises:

refraining from sending the service networking request to a target server.

20. The data management method of claim 19, wherein intercepting the service networking request comprises:

and returning request failure information corresponding to the service networking request to a service layer of the software.

21. The data management method according to any of claims 1-11, 13-16, wherein after initializing service state information according to the state data, comprising:

and adjusting the characteristics of the request to be released in the local virtual private network according to the service state information.

22. The data management method according to claim 21, wherein intercepting the service networking request if the service networking request corresponding to the prohibition state is acquired comprises:

if a service networking request is acquired, sending the service networking request to the local virtual private network;

and if the service networking request is not matched with the characteristics of the request to be released in the adjusted local virtual private network, the service networking request is intercepted.

23. The data management method according to claim 22, wherein the sending the service networking request to a target server if the service networking request corresponding to the permission status is obtained comprises:

and if the service networking request is matched with at least one characteristic of the request to be released in the adjusted local virtual private network, the service networking request is sent to a target server.

24. The data management method according to any of claims 1-11, 13-16, wherein after initializing service state information according to the state data, comprising:

and adjusting the request characteristics in the released white list and/or the intercepted black list according to the service state information.

25. The data management method according to claim 24, wherein intercepting the service networking request if the service networking request corresponding to the prohibition state is acquired comprises:

if a service networking request is obtained, judging whether the service networking request is matched with the request characteristics in the release white list and/or the interception black list;

and if the service networking request is matched with at least one request feature in the adjusted interception blacklist and/or the service networking request is not matched with the request feature in the adjusted release white list, intercepting the service networking request.

26. The data management method according to claim 25, wherein the sending the service networking request to a target server if the service networking request corresponding to the permission status is obtained comprises:

and if the service networking request is matched with at least one request feature in the adjusted release white list and/or the service networking request is not matched with the request feature in the adjusted interception blacklist, sending the service networking request to a target server.

27. The data management method of claim 13, wherein if the software is first booted, the state data read from the non-volatile memory corresponds to a global disabled state;

initializing service state information according to the state data includes:

and initializing service state information into a global forbidden state corresponding to all network services according to the state data.

28. The data management method of claim 14, wherein if the software is first booted, the state data read from the non-volatile memory corresponds to a global license status;

initializing service state information according to the state data includes:

and initializing service state information into a global permission state corresponding to all network services according to the state data, wherein all network services at least comprise a registration service and a login service.

29. The data management method according to claim 28, wherein the sending the service networking request to a target server if the service networking request corresponding to the permission status is obtained comprises:

if a service networking request corresponding to the registration service is obtained, sending the service networking request to a server corresponding to the registration service;

and if the service networking request corresponding to the login service is obtained, sending the service networking request to a server corresponding to the login service.

30. The data management method of any of claims 1-11, 13-16, wherein obtaining the service networking request comprises:

and if a preset service request triggering condition is triggered, generating a service networking request corresponding to the service request triggering condition.

31. The data management method according to claim 30, wherein the generating of the service networking request corresponding to the service request triggering condition includes:

acquiring service request data corresponding to the service request triggering condition;

and carrying out anonymization processing and secret key signature processing on the service request data to obtain a service networking request.

32. The data management method according to claim 31, wherein the obtaining of the service request data corresponding to the service request trigger condition includes:

if the service request triggering condition corresponds to the privacy data of the user, authorization request information is output;

and responding to the authorization permission input by the user, and acquiring service request data corresponding to the service request triggering condition.

33. The data management method of any of claims 1-11, 13-16, wherein sending the service networking request to a target server comprises at least one of:

34. A data management apparatus comprising a memory and a processor;

the memory is used for storing a computer program;

35. An aircraft, characterized in that it comprises:

the data management apparatus of claim 34, for controlling whether to send a service networking request to a target server;

the flying assembly is used for flying.

36. A mobile terminal, comprising:

the data management apparatus of claim 34, configured to control whether to send a service networking request to the target server.

37. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to implement the data management method of any one of claims 1-33.