WO2021081921A1

WO2021081921A1 - Service authentication method and device and storage medium

Info

Publication number: WO2021081921A1
Application number: PCT/CN2019/114811
Authority: WO
Inventors: 王远; 孙伟杰; 陈庭欣; 黄振昊
Original assignee: 深圳市大疆创新科技有限公司
Priority date: 2019-10-31
Filing date: 2019-10-31
Publication date: 2021-05-06
Also published as: CN112166587A

Abstract

A service authentication method and device and a storage medium. The method comprises: acquiring a device identification associated with data to be processed so as to respond to a service authentication triggering event (100); according to service activation records and the device identification, verifying whether service activation is performed on an autonomous mobile device corresponding to the device identification before the occurrence of the service authentication triggering event (101); and on the basis of the verification result, determining whether the data to be processed passes the service authentication (102). The method can achieve a fine management of service resources and use the service resources for processing task data produced by an autonomous mobile device on which service activation is performed, thus effectively avoiding the loss of service resources.

Description

Service authentication method, equipment and storage medium

Technical field

This application relates to the field of data security technology, and in particular to a service authentication method, device and storage medium.

Background technique

In the application of drones, more and more precision positioning technology is applied in the processing stages of map construction, mission planning, and data analysis to improve the accuracy and reliability of the positioning results during the flight of the drone.

Among them, Post Processed Knematic (PPK) measurement technology can provide higher accuracy and reliability than Real Time Kinematic (RTK) measurement technology, so PPK measurement technology is more favored by users.

At present, the PPK solution service usually adopts the user account mode for authentication, that is, the user account is authenticated to determine whether the user account has the authority to use the PPK solution service. However, in this authentication method, the user account may be stolen or authorized by a legitimate user to other users, causing the loss of service resources and may lead to data security risks.

Summary of the invention

Various aspects of the present application provide a service authentication method, device, and storage medium to avoid the loss of service resources.

The embodiment of the present application provides a service authentication method, including:

Obtain the device identification associated with the data to be processed to respond to the service authentication trigger event;

Verifying, according to the service activation record and the device identifier, whether the autonomous mobile device corresponding to the device identifier has performed service activation before the service authentication trigger event occurs;

Based on the verification result, it is determined whether the to-be-processed data passes service authentication.

The embodiment of the present application also provides a service authentication method, including:

Obtain device identification;

Encrypting the device identification to generate password information;

The device identification and the password information are provided to a data processing server for the data processing server to perform service authentication.

Acquiring task data provided by an autonomous mobile device and a device identifier associated with the task data;

The device identification, or the task data and the device identification are provided to a data processing server, so that the data processing server performs service authentication on the task data based on the device identification.

The embodiment of the present application also provides a data processing server, including a memory, a processor, and a communication component;

The memory is used to store one or more computer instructions;

The processor is coupled with the memory and the communication component, and is configured to execute the one or more computer instructions for:

Obtain the device identification associated with the to-be-processed data through the communication component to respond to the service authentication trigger event;

The embodiments of the present application also provide an autonomous mobile device, including a memory, a processor, and a communication component;

The memory is used to store one or more computer instructions;

Obtain device identification;

Encrypting the device identification to generate password information;

The device identifier and the password information are provided to the data processing server through the communication component, so that the data processing server can perform service authentication.

An embodiment of the present application also provides a data relay device, including a memory, a processor, and a communication component;

The memory is used to store one or more computer instructions;

The device identification, or the task data and the device identification are provided to a data processing server through the communication component, so that the data processing server performs service authentication on the task data based on the device identification.

The embodiments of the present application also provide a computer-readable storage medium storing computer instructions, which when the computer instructions are executed by one or more processors, cause the one or more processors to perform the following operations:

Obtain device identification;

Encrypting the device identification to generate password information;

The embodiments of the present application also provide a computer-readable storage medium storing computer instructions, which, when the computer instructions are executed by one or more processors, cause the one or more processors to perform the following operations:

In the embodiment of this application, each time the data to be processed is the authentication object, and based on the device identification associated with the data to be processed, the producer of the data to be processed can be authenticated, and if the producer has already activated the service , Provide service resources for the data to be processed. Accordingly, in the embodiments of the present application, refined management of service resources can be realized, and the service resources can be used to process task data produced by autonomous mobile devices that have already activated the service, thereby effectively avoiding the loss of service resources.

Description of the drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The exemplary embodiments and descriptions of the application are used to explain the application, and do not constitute an improper limitation of the application. In the attached picture:

FIG. 1 is a schematic flowchart of a service authentication method provided by an embodiment of this application;

2 is a schematic flowchart of a service authentication method provided by another embodiment of this application;

FIG. 3 is a schematic flowchart of a service authentication method provided by another embodiment of this application;

4 is a schematic diagram of an application scenario of PPK solution service authentication provided by another embodiment of this application;

FIG. 5 is a schematic structural diagram of a data processing server provided by another embodiment of this application;

FIG. 6 is a schematic structural diagram of an autonomous mobile device provided by another embodiment of this application;

FIG. 7 is a schematic structural diagram of a data relay device provided by another embodiment of this application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely in conjunction with specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

At present, in the field of autonomous mobile devices, the user account mode is usually used for service authentication, that is, the user account is authenticated to determine whether the user account has the authority to use the service. However, in this authentication method, the user account may be stolen or authorized by a legitimate user to other users, causing the loss of service resources and may lead to data security risks. In order to solve the problems existing in the prior art, in some embodiments of this application: each time the data to be processed is the authentication object, and based on the device identification associated with the data to be processed, the producer of the data to be processed can be authenticated, and In the case where the producer has already activated the service, it provides service resources for the data to be processed. According to this, it is possible to realize refined management of service resources, use service resources to process task data produced by autonomous mobile devices that have already activated services, and avoid unauthorized use of autonomous mobile devices that require authorized service resources. Circumstances, which can effectively avoid the loss of service resources.

Further, according to an embodiment of the present invention, since verification is performed based on the device identification of the autonomous mobile device (for example, the SN number of the drone), it is possible to realize the uploading of each autonomous mobile device (for example, a drone). Data is verified to prevent the common use of multiple autonomous mobile devices for one account. In other words, an autonomous mobile device is managed with an activation code.

The technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

FIG. 1 is a schematic flowchart of a service authentication method provided by an embodiment of this application. The service authentication method provided in this embodiment can be executed by a service authentication device, the service authentication device can be implemented as software or a combination of software and hardware, and the service authentication device can be integrated in the data processing server. As shown in Figure 1, the method includes:

Step 100: Obtain a device identifier associated with the data to be processed in response to a service authentication trigger event;

Step 101: According to the service activation record and the device ID, verify whether the autonomous mobile device corresponding to the device ID has already activated the service before the service authentication trigger event occurs;

Step 102: Based on the verification result, determine whether the to-be-processed data passes service authentication.

The service authentication method provided by the embodiments of the present application can be applied to various scenarios where service resources need to be managed, for example, PPK solution service scenarios and so on. This embodiment does not limit the application scenario.

Among them, the autonomous mobile device can be a drone or an unmanned car, etc., and the autonomous mobile device will generate task data during the execution of the task. We describe these task data that need to be further processed by service resources as data to be processed. For example, the data to be processed may be a large amount of photographing data and satellite observation data collected by the drone in the process of performing surveying and mapping tasks. Of course, the data to be processed is not limited to this in this embodiment.

In step 100, the service authentication trigger event may be a to-be-processed data transmission event or a service authentication request event, etc., which is not limited in this embodiment. For example, the service authentication process can be automatically started when the data to be processed is received. For another example, when a service authentication request for the data to be processed is received, the service authentication process can be started.

For autonomous mobile devices, the device identification can be associated with the data to be processed that it produces. In practical applications, an autonomous mobile device can construct a signature file while producing data to be processed, and configure its device identification in the file to be signed. The data to be processed and the signature file will be associated and provided to the data processing server in this embodiment. The specific scheme for the autonomous mobile device to associate its device identification with the to-be-processed data produced by it will be described in detail in the following embodiments.

Based on this, in step 100, the device identification associated with the data to be processed can be obtained. It can be seen that the device identifier associated with the data to be processed is the device identifier of the producer of the data to be processed. The device identification associated with the data to be processed may characterize the identity of the producer of the data to be processed. Among them, the device identification may be the device serial number (for example, the SN number of the drone) and other information that can characterize the identity of the autonomous mobile device.

In step 101, the service activation record refers to activation data generated during the service activation process. Before using service resources, service activation needs to be performed for autonomous mobile devices to configure service resource usage rights for autonomous mobile devices. The service activation record can contain the activation data of different autonomous mobile devices. Therefore, the service activation record can be used to verify whether the autonomous mobile device has activated the service.

Based on this, in step 101, according to the service activation record and the device identifier (for example, the SN number of the drone), it can be verified whether the autonomous mobile device corresponding to the device identifier has already activated the service before the service authentication trigger event occurs.

In actual applications, it can be determined whether there is activation data for the device identifier in the service activation record. In addition, the service activation time of the autonomous mobile device corresponding to the device identifier (for example, the activation time of the drone) needs to be completed before the service authentication trigger event occurs.

In step 102, it can be determined whether the data to be processed has passed the service authentication based on the verification result of whether the autonomous mobile device corresponding to the device identification has performed service activation before the service authentication trigger event occurs.

The service authentication method provided in this embodiment can be applied in combination with a traditional service authentication scheme, or can be applied separately. For example, in the case of combined application with a traditional service authentication scheme, first verify whether the user account is a registered account. If it is verified as a registered account, the user account can be used based on the service authentication method provided in this embodiment. Provide data to be processed for service certification.

Accordingly, in this embodiment, the data to be processed can be the object of authentication each time, and based on the device identification associated with the data to be processed, the producer of the data to be processed can be authenticated, and if the producer has already activated the service Next, provide service resources for the data to be processed. In this way, refined management of service resources can be realized, and service resources can be used to process task data produced by autonomous mobile devices that have been activated for services, so as to prevent unauthorized autonomous mobile devices from using authorized service resources. , Which can effectively avoid the loss of service resources.

In the above or the following embodiments, according to the device identification associated with the data to be processed, multiple implementations can be used to verify whether the autonomous mobile device corresponding to the device identification has performed service activation before the service authentication trigger event occurs.

In an implementation manner, the device identification of the autonomous device that has performed the service activation may be recorded in the service activation record. Based on this, it is possible to look up whether there is a device identification associated with the data to be processed in the service activation record to verify whether the autonomous mobile device corresponding to the device identification has already activated the service before the service authentication trigger event occurs.

If there is a device ID associated with the data to be processed in the service activation record, and the service activation time is before the occurrence time of the service authentication trigger event, it can be determined that the autonomous mobile device corresponding to the device ID has already performed the service before the service authentication trigger event occurs. activation.

In this implementation manner, the device identification can be recorded in the service activation record during the service activation process of the autonomous mobile device corresponding to the device identification. In practical applications, an encryption algorithm can be used to encrypt the device identification and save it in the service activation record to avoid tampering with the device identification in the service activation record. Correspondingly, when performing the aforementioned operation of finding whether there is a device identifier associated with the data to be processed in the service activation record, the same encryption algorithm can be used to encrypt the device identifier associated with the data to be processed, and then search in the service activation record Whether there is an encryption result of the device ID managed by the data to be processed.

In another implementation manner, the activated activation code and the device identification can be encrypted together to obtain the first authentication information; determine whether there is target activation data matching the first authentication information in the service activation record; if there is target activation Data to determine that the autonomous mobile device corresponding to the device ID has already activated the service before issuing the service authentication request; where the target activation data is based on the activation code and activation code obtained during the service activation process for the autonomous mobile device corresponding to the device ID Encrypted information obtained by encrypting the device identifier.

In this implementation, an activation code is introduced, and the activation code is used for service activation. The activation code can only be used once. After the activation code has been used to complete the service activation, the activation code will become activated to avoid repeated use of the activation code. Among them, in the service activation process, the device identification corresponding to the activated activation code can be recorded. In addition, the activated activation code can be stored in the clear, and the device identification corresponding to each activated activation code may not be clearly indicated, so as to prevent the attacker from discovering the device identification that has been activated for service and embezzling it. Of course, the activated activation code can also be saved in a secret code. In this case, when the activated activation code needs to be used, the activated activation code can be called by decrypting and then using it. The secret code saving method can be better To ensure the security of the activated activation code.

Based on this, the device identification associated with the data to be processed and the activated activation code corresponding to the device identification can be encrypted together to obtain the first authentication information, and determine whether there is target activation data matching the first authentication information in the service activation record . In the case where the autonomous mobile device corresponding to the device identification associated with the data to be processed has already performed service activation, the target activation data that matches the first authentication information can be found in the service activation record.

Accordingly, if there is target activation data in the service activation record, and the service activation time corresponding to the target activation data is before the occurrence time of the service authentication triggering event, it can be determined that the autonomous mobile device corresponding to the device identifier has already occurred before the service authentication triggering event occurs. Service activation has been performed.

In this implementation, the service activation process of the autonomous mobile device corresponding to the device identification associated with the data to be processed may be: receiving a service activation request, the service activation request includes the activation code and the device identification of the autonomous mobile device; if the activation code is determined to be If the activation code is available, the activation code and device identification are encrypted to obtain the target activation data; the target activation data is saved in the service activation record.

In this way, in this implementation manner, the activation data in the service activation record is stored in an encrypted form, which can prevent the activation data in the service activation record from being tampered with, thereby ensuring the accuracy of the verification result.

In the above two exemplary implementation manners, the service activation record can be kept in the data processing server in this embodiment, of course, can also be kept in other storage locations, which is not limited in this embodiment. In addition, the service activation process can be executed in the data processing server in this embodiment. Of course, it can also be executed in other processing devices to share the service activation record with the data processing server in this embodiment. This embodiment does not do anything about this. limited.

It is worth noting that the above two implementation manners are only exemplary. In this embodiment, the verification of whether the autonomous mobile device corresponding to the device identifier has already activated the service before the service authentication trigger event occurs is not limited to this.

In the foregoing or following embodiments, the signature file associated with the data to be processed can be obtained, and the device identification can be unchecked from the signature file as the device identification associated with the data to be processed.

As mentioned above, the autonomous mobile device can construct a signature file while producing task data, and configure its device identification in the signature file, and the task data produced by the autonomous mobile device will be transmitted synchronously with the signature file constructed by the autonomous mobile device.

In practical applications, the signature file may contain clear code information and password information, where the clear code information contains at least the device identification, and the password information contains at least the encryption result of the device identification.

In this embodiment, it is possible to verify whether the autonomous mobile device corresponding to the device ID has activated the service before the service authentication trigger event occurs, according to the device ID contained in the clear code information and the encryption result of the device ID contained in the password information. , To determine whether the device ID unchecked out from the signature file has not been tampered with; if the result of the judgment is yes, perform the operation of verifying whether the autonomous mobile device corresponding to the device ID has performed service activation before the service authentication trigger event occurs.

Specifically, the device identification can be decrypted from the secret code information, and it is determined whether the device identification contained in the clear code information is consistent with the device identification decrypted from the secret code information, and if they are the same, the device identification that is unsigned in the signature file is determined Has not been tampered with.

Through the above non-tampering verification of the device identification associated with the data to be processed, it is possible to prevent the occurrence of service resource occupation by tampering with the device identification associated with the data to be processed. For example, if the device ID that is actually associated with the data to be processed is the device ID of an autonomous mobile device that has not activated the service, even if the device ID associated with the data to be processed is tampered with the device ID of an autonomous mobile device that has already activated the service, this In the embodiment, through the non-tampering verification processing, it can be determined that the verification result corresponding to the to-be-processed data is: the autonomous mobile device corresponding to the device identification has not performed service activation before the service authentication trigger event occurs.

In the above or following embodiments, if it is verified whether the autonomous mobile device corresponding to the device ID has already activated the service before the service authentication event occurs according to the service activation record and the device ID, the corresponding verification result is: the autonomous mobile device corresponding to the device ID The mobile device has already activated the service before the service authentication event occurs. Then, the start time of the task associated with the data to be processed can be obtained.

As mentioned above, the data to be processed may be task data generated by autonomous mobile devices to perform tasks. Therefore, the task start time can be associated in the production process of task data.

In practical applications, the task start time can be configured in the signature file mentioned in the foregoing embodiment. The clear code information of the signature file may include the mission start time, and the secret code information may include the secret encryption result of the mission start time. Based on this, before using the task start time, it can be judged whether the task start time contained in the clear code information and the task start time decrypted from the password information are consistent; if the result of the judgment is yes, then the unchecked out task start time is used as The start time of the task associated with the pending data.

In this embodiment, the service activation time of the autonomous mobile device corresponding to the device identifier can also be obtained. In practical applications, the service activation time can be stored in the service activation record during the service activation process mentioned in the foregoing embodiment. In addition, the service activation time can also be stored in an encrypted manner to prevent the service activation time from being tampered with.

On this basis, it can be determined whether the task start time of the data to be processed is later than the service activation time of the autonomous mobile device corresponding to its associated device ID. If the judgment result is yes, it can be determined that the data to be processed has passed the service authentication.

Among them, the service activation time in this embodiment is the initial activation time, and is recorded according to the actual service activation process. In addition, it is stored in an encrypted form. These measures can ensure the accuracy of the service activation time, thereby improving the accuracy of the service activation time. Accurately judge the sequence of the task start time and the service activation time.

Through the above non-tampering verification of the task start time associated with the data to be processed and the anti-tampering measures on the service activation time, it is possible to prevent the occurrence of service resource occupation by tampering with the task start time and/or service activation time associated with the data to be processed Happening. For example, if the task start time associated with the data to be processed is earlier than the service activation time of the autonomous mobile device corresponding to its associated device ID, even if the task start time associated with the data to be processed is tampered with to be later than the corresponding device ID. For the service activation time of the autonomous mobile device, in this embodiment, through the non-tampering verification process, it can be determined that the data to be processed has not passed the service authentication.

In this embodiment. By comparing the task start time and the service activation time, it can be ensured that the data to be processed is generated by the autonomous mobile device after the service is activated, thereby avoiding the use of service resources for processing task data generated by the autonomous mobile device before the service activation.

In the above or the following embodiments, the data to be processed can also be verified without tampering. In the case where it is determined that the data to be processed has not been tampered with, if it is determined that the data to be processed has passed the service authentication, data processing services are provided for the data to be processed.

Among them, this embodiment does not limit the processing sequence of performing non-tampering verification on the data to be processed and performing service authentication on the data to be processed. The two processing procedures can be executed sequentially or simultaneously.

There are many ways to implement non-tampering verification on the data to be processed, and one of them will be described in detail below.

In this implementation, the check code associated with the data to be processed can be obtained; the check algorithm consistent with the check code is used to perform the check calculation on the data to be processed to obtain the actual check code; if the actual check code is the same as that obtained If the check codes associated with the data to be processed are consistent, it can be determined that the data to be processed has not been tampered with. The check code may be an MD5 code, etc., which is not limited in this embodiment.

Among them, in practical applications, the verification code associated with the data to be processed may be configured in the signature file mentioned in the foregoing embodiment, and may be configured in the password information in the signature file to ensure the security of the verification code.

By performing non-tampering verification on the data to be processed, the security of the data to be processed can be guaranteed, thereby ensuring the accuracy of the data processing result.

In addition, the non-tampering verification of the task start time, the non-tampering verification of the device ID, and the non-tampering verification of the data to be processed can be used to verify whether the autonomous mobile device corresponding to the device ID has performed the service activation operation before the service authentication event occurs. The prerequisite for this, that is, under the condition that all the tamper-free verifications in these aspects are passed, the autonomous mobile device corresponding to the device identification is then executed to verify whether the service activation operation has been performed before the service authentication event occurs. This can ensure that accurate basic authentication information is provided for service authentication, thereby preventing the occupation of service resources by tampering with the basic authentication information.

In practical applications, the clear code information in the signature file associated with the data to be processed may include the device identification and task start time, and the password information may include the encryption result of the device identification, the check value of the data to be processed, and the task start time. Based on this, the above-mentioned non-tampering verification can be performed based on the synchronization of the signature file.

FIG. 2 is a schematic flowchart of a service authentication method provided by another embodiment of this application. As shown in Figure 2, the method includes:

Step 200: Obtain a device identification;

Step 201: Perform encryption processing on the device identification to generate password information;

Step 202: Provide the device identification and password information to the data processing server for the data processing server to perform service authentication.

However, it is not limited to this. According to another embodiment of the present invention, the device identification and task data are obtained; the device identification is encrypted to generate password information; the task data, device identification, and password information are provided to the data processing server to For the data processing server to perform service authentication.

In this embodiment, the service authentication method is mainly explained from the side of the autonomous mobile device. Among them, the camera, encryption component and flight controller (for example, the flight controller of a drone) in the autonomous mobile device will participate in the implementation process of the solution in this embodiment

In this embodiment, the camera can send an encryption request to the encryption component, and the encryption component can request the flight controller for the device identification of the autonomous mobile device to obtain the device identification of the autonomous mobile device. In addition, for the encryption component, the requested device identification can also be encrypted to generate secret code information and return the secret code information to the camera.

Based on this, the camera can establish an association relationship between the task data and the device identification after the task is completed.

In practical applications, the camera can produce task data in the storage device of the autonomous mobile device during the execution of the task, and build a signature file in association with it. Based on the signature file, the camera can configure the device identification and password information returned by the encryption component in the signature file.

Accordingly, the camera can also associate the task data with the signature file to ensure synchronous transmission of the two. It is worth noting that the association here may represent the association relationship in the form of an identification, index, etc., or may be a mechanism of synchronous transmission to represent the association relationship, which is not limited in this embodiment.

In this way, it can be realized that the task data will be associated with the device identification, thereby marking the identity of the producer of the task data.

In step 202, the task data will be provided to the data processing server in synchronization with the device identification and password information, and the data processing server can perform service authentication on the task data when a service authentication trigger event occurs. For the service authentication process in the data processing server, reference may be made to the relevant description in the foregoing embodiment, which will not be repeated here.

In one implementation, the autonomous mobile device can autonomously provide task data, device identification, and password information to the data processing server. Alternatively, the autonomous mobile device can autonomously provide the device identification and password information to the data processing server. In this implementation, a communication link between the autonomous mobile device and the data processing server needs to be established.

In another implementation manner, the autonomous mobile device can send task data, device identification, and password information to the data relay device, so as to use the data relay device to provide the task data, device identification, and password information to the data processing server. Alternatively, the autonomous mobile device can send the device identification and password information to the data relay device, so as to provide the device identification and password information to the data processing server using the data relay device.

In practical applications, there is no need to establish a communication link between the autonomous mobile device and the data processing server. The storage device of the autonomous mobile device can be plugged into the data relay device for the data relay device to read tasks from the storage device. Data and its associated signature file. Thus, the data relay device can obtain the task data device identification and password information, and provide them to the data processing server.

The data relay device may be a remote control of an autonomous mobile device, or any computing device or mobile device, etc., which is not limited in this embodiment.

In this embodiment, after the task is completed, the association relationship between the task data and the device identification can be established to mark the identity of the producer of the task data. Moreover, the device identification can be prevented by transmitting the device identification in the form of password information. It is tampered with to provide accurate basic information for the service authentication of the data processing server to ensure the successful use of service resources.

In the foregoing or following embodiments, the camera may also perform verification calculations based on the task data to generate a verification code of the task data, and send the verification code to the encryption component. The encryption component can encrypt the check code and configure it in the secret code information.

The camera can also record the task start time of the task data and send the task start time to the encryption component. The encryption component can encrypt the task start time and configure the password information.

In this way, the password information may include the encryption result of the device identification, the task start time, and the check value corresponding to the task data. The encryption component can provide such secret code information to the camera.

On this basis, the camera can construct a signature file based on the device identification and password information it obtains from the encryption component, as well as the recorded task start time. In this way, the generated signature file can contain clear code information and password information, the clear code information can contain the device identification and task start time, and the password information can contain the device identification, task start time, and the encryption result of the check value corresponding to the task data.

In this embodiment, by configuring information such as the task start time and check code of the task data into the signature file, the association relationship between the task data and the task start time and check code can be established, thereby implementing on the autonomous mobile device side Mark the attributes of the task data for the data processing server to perform service authentication on the task data.

FIG. 3 is a schematic flowchart of a service authentication method provided by another embodiment of this application. As shown in Figure 3, the method includes:

Step 300: Obtain the task data provided by the autonomous mobile device and the device identification associated with the task data;

Step 301: Provide the device identification, or the task data and the device identification, to the data processing server, so that the data processing server can perform service authentication on the task data based on the device identification.

In this embodiment, the service authentication method is mainly explained from the side of the data relay device.

As mentioned in the previous embodiment, the data relay device can participate in the service authentication process of the task data produced by the autonomous mobile device by the data processing server. For details of related processing in the autonomous mobile device and the data processing server, reference may be made to the description in the foregoing embodiment, which will not be repeated here.

In step 300, when it is detected that the storage device of the autonomous mobile device is inserted into the data relay device, the task data of the autonomous mobile device and the device identification associated with the task data can be obtained from the storage device.

In this embodiment, the task data and device identification can be provided to the data processing server through the data relay device, which eliminates the need for the autonomous mobile device to establish a communication link with the data processing server, simplifies the operation link, and can improve the data Processing efficiency.

In addition, in this embodiment, the data relay device can also carry the service activation function.

In this embodiment, the activation code can be obtained in response to the service activation operation for the autonomous mobile device; the device ID of the autonomous mobile device can be obtained; the service activation request can be generated according to the activation code and the device ID; the service activation request can be sent to the data processing server , For the data processing server to activate the service on the autonomous mobile device.

For the technical details related to service activation in the data processing server, reference may be made to the description in the foregoing embodiment, which will not be repeated here.

In addition, it is worth noting that the above processing link of providing device identification, or task data and device identification to the data processing server and the link of service activation for autonomous mobile devices can be performed in the same data relay device. Of course, It can also be performed in different data relay devices, which is not limited in this embodiment.

FIG. 4 is a schematic diagram of an application scenario of PPK solution service authentication provided by another embodiment of this application. In the following, a detailed description of the service authentication process will be carried out with reference to Figure 4, taking the PPK solution service as an example.

As shown in Figure 4, the system architecture of the PPK solution service includes an autonomous mobile device 1, a data relay device 2, and a data processing server 3. Among them, the data relay device 2 is used to send the task data generated by the autonomous mobile device 1 and the device identification of the autonomous mobile device 1 to the data processing server 3, which can avoid multiple communication between the autonomous mobile device 1 and the data processing server 3 The trouble of establishing a communication link. In some cases, the data relay device 2 may not be involved in the system architecture, and the autonomous mobile device 1 directly provides the task data and device identification to the data processing server 3. This situation is not discussed in FIG. 4 for the time being.

In the process of service activation for the autonomous mobile device 1, the data relay device 2 can establish wireless communication with the autonomous mobile device 1, and obtain the SN number (as a device identification) of the autonomous mobile device (for example, a drone) 1. In addition, the data relay device 2 can also obtain the activation code input for the autonomous mobile device 1 in response to the activation code input operation. The data relay device 2 can provide the activation code and the acquired device identification to the data processing server 3, and the data processing server 3 can encrypt the activation code, SN number, and service activation time when the activation code is available, as The activation data of the autonomous mobile device 1 is stored in the service activation record.

When the autonomous mobile device 1 performs a task, the processor (specifically a camera) on it will create a task folder in the SD card for storing camera photo data (for example, photos taken during a drone flight) Files, and photo recording files) and the original GNSS observation data obtained from the RTK board (used in the subsequent PPK calculation processing), which are used as task data in this embodiment. Among them, the photographing record file includes photographing time and other photographing attributes.

When starting to execute a task job, the processor also records the task start time.

After completing the task, the processor sends a command to 1860AP (that is, a processor that can be used as an encryption component) to request encrypted data, and at the same time calculates the MD5 check code based on the task data, and adds the task start time to the checksum The code is sent to 1860AP.

After receiving the request from the processor, the 1860AP requests the device SN number (for example, the AN number of the drone) from the flight controller, and the flight controller transmits the SN number to the 1860AP of the autonomous mobile device 1. The 1860AP combines the SN number and verification The code and task start time are encrypted by an encryption algorithm to generate secret code information.

The 1860AP transmits the secret code information to the processor, and the processor uses the SN number and the task start time as the clear code information, and combines the aforementioned secret code information to generate a .sig signature file in the task folder.

On this basis, when it is necessary to perform PPK calculation on the task data of the autonomous mobile device 1, the SD card of the autonomous mobile device 1 can be removed and inserted into the data relay device 2.

The data relay device 2 can obtain task data and signature files from the SD card and upload them to the data processing server 3.

The upload event is used as a service authentication trigger event, and the data processing server 3 will start the service authentication of the task data upon receiving the task data and the signature file.

First, the data processing server 3 can unsign the signature file and obtain the following information:

1. Write the SN number in the clear code information of the .sig signature file

2. The start time of the task written in the clear information of the .sig signature file

3. The SN number decrypted from the secret code information

4. The task start time decrypted from the secret code information

5. MD5 decrypted from the secret code information

Based on this information, compare:

1. The SN number in the clear code information and the SN number decrypted from the secret code information

2. The start time of the task in the clear code information and the start time of the task decrypted from the secret code information

3. The MD5 decrypted from the password information and the MD5 calculated based on the task data

If several sets of comparisons are consistent, it means that the task data and the SN number and the task start time in the signature file have not been tampered with.

On this basis, the SN number unsigned from the signature file and the activated activation code can be encrypted to generate authentication information, and the service activation record can be used to find out whether there is target activation data that matches the authentication information. , The encryption algorithm here should be consistent with the encryption algorithm in the aforementioned service activation process. If the activation data of the autonomous mobile device 1 exists in the service activation record, the target activation data can be matched here, and it also indicates that the autonomous mobile device 1 that produced the task data has already activated the service before this service authentication trigger event .

At this time, it can continue to determine whether the start time of the task unchecked out from the signature file is later than the service activation time of the autonomous mobile device 1 corresponding to the device ID unchecked out from the signature file. If it is, it is determined that the mission data passed the service certification, and the PPK solution service can be provided for the mission data.

FIG. 5 is a schematic structural diagram of a data processing server provided by another embodiment of this application. As shown in FIG. 5, the data processing server includes: a memory 50, a processor 51, and a communication component 52.

The processor 51 is coupled with the memory 50 and the communication component 52, and is configured to execute computer programs in the memory for:

Obtain the device identification associated with the to-be-processed data through the communication component 52 to respond to the service authentication trigger event;

According to the service activation record and device ID, verify whether the autonomous mobile device corresponding to the device ID has already activated the service before the service authentication trigger event occurs;

Based on the verification result, it is determined whether the data to be processed passes the service authentication.

In an optional embodiment, the processor 51 is configured to: when verifying whether the autonomous mobile device corresponding to the device ID has already activated the service before the service authentication trigger event occurs, according to the service activation record and the device ID, the processor 51 is used to:

Encrypt the activated activation code and device identification together to obtain the first authentication information;

Determine whether there is target activation data matching the first authentication information in the service activation record. The target activation data is obtained by encrypting the activation code and the device ID obtained during service activation of the autonomous mobile device corresponding to the device ID Encrypted information;

If there is target activation data, it is determined that the autonomous mobile device corresponding to the device identifier has performed service activation before issuing the service authentication request.

In an optional embodiment, the processor 51 is configured to: when performing a service activation process on the autonomous mobile device corresponding to the device identifier:

Receive a service activation request, the service activation request contains the activation code and the device identification of the autonomous mobile device;

If it is determined that the activation code is a usable activation code, encrypt the activation code and device identification to obtain the target activation data;

Save the target activation data to the service activation record.

In an optional embodiment, the processor 51 is configured to: when acquiring the device identification associated with the to-be-processed data:

Obtain the signature file associated with the data to be processed;

Uncheck out the device identification from the signature file.

In an optional embodiment, the signature file includes clear code information and secret code information, the clear code information includes at least the device identification, and the secret code information includes at least the encryption result of the device identification. The processor 51 verifies the autonomous mobile device corresponding to the device identification. Whether the service has been activated before the service authentication trigger event occurs, and it is also used to:

Determine whether the device identification contained in the clear code information is consistent with the device identification decrypted from the secret code information;

If the result of the judgment is yes, the operation of verifying whether the autonomous mobile device corresponding to the device identification has already performed service activation before the occurrence of the service authentication trigger event is performed.

In an optional embodiment, when the processor 51 determines whether the data to be processed passes the service authentication based on the verification result, the processor 51 is configured to:

If the verification result is that the autonomous mobile device corresponding to the device identifier has already activated the service before the service authentication trigger event occurs, obtain the start time of the task associated with the to-be-processed data;

Obtain the service activation time corresponding to the autonomous mobile device;

Determine whether the task start time is later than the service activation time;

If yes, confirm that the data to be processed passes the service authentication.

In an optional embodiment, before determining whether the task start time is later than the service activation time, the processor 51 is further configured to:

Verify that the start time of most tasks has not been tampered with; and

When it is determined that the task start time has not been tampered with, an operation of determining whether the task start time is later than the service activation time is performed.

In an optional embodiment, the processor 51 is further configured to:

Acquire a signature file associated with the data to be processed, the signature file includes clear code information and password information, and the clear code information includes at least one of a device identification or a task start time;

Decrypt the secret code information to obtain the decrypted secret code information;

Compare the decrypted code information with the clear code information to determine whether the decrypted code information is consistent with the clear code information;

If the decrypted code information is consistent with the clear code information, it is verified whether the autonomous mobile device corresponding to the device identifier has already activated the service before the service authentication trigger event occurs.

In an optional embodiment, the password information further includes a check code corresponding to the data to be processed, and the processor 51 is further configured to:

Perform verification calculation on the data to be processed to obtain the actual verification code;

If the actual check code is consistent with the check code in the secret code information, it is verified whether the autonomous mobile device corresponding to the device identifier has already activated the service before the service authentication trigger event occurs.

In an optional embodiment, the autonomous mobile device is a drone or an unmanned vehicle.

Further, as shown in FIG. 5, the data processing server further includes: a power supply component 53 and other components. Only some components are schematically shown in FIG. 5, which does not mean that the data processing server only includes the components shown in FIG. 5.

It is worth noting that, for the technical details in the above embodiments of the data processing server, please refer to the descriptions in the related embodiments of the aforementioned service authentication method. To save space, we will not repeat them here, but this should not cause damage to this application. Loss of protection range.

Correspondingly, an embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed, the steps that can be executed by the data processing server in the foregoing method embodiments can be implemented.

FIG. 6 is a schematic structural diagram of an autonomous mobile device provided by another embodiment of this application. As shown in FIG. 6, the autonomous mobile device may include: a memory 60, a processor 61, and a communication component 62.

The processor 61 is coupled with the memory 60 and the communication component 62, and is configured to execute computer programs in the memory for:

Obtain device identification;

Encrypt the device identification to generate secret code information;

The device identification and password information are provided to the data processing server through the communication component 62 for the data processing server to perform service authentication.

or,

Obtain device identification and task data;

Encrypt the device identification to generate secret code information;

The task data, device identification, and password information are provided to the data processing server through the communication component 62 for the data processing server to perform service authentication.

In an optional embodiment, when the processor 61 provides the device identification to the data processing server, it is used to:

Send the device identification and password information to the data processing server through the communication component 62; or

The device identification and password information are sent to the data relay device through the communication component 62, so that the data relay device is used to provide the device identification and password information to the data processing server.

or,

Send the task data, device identification and password information to the data processing server through the communication component 62; or

The task data, the device identification and the password information are sent to the data relay device through the communication component 62, so that the data relay device provides the task data, the device identification and the password information to the data processing server.

In an optional embodiment, the processor 61 is configured to:

Send an encryption request to the encryption component 63 to use the encryption component 63 to encrypt the clear code information including the device identification to obtain the secret code information;

Generate a signature file based on the clear code information and the secret code information;

Send the signature file to the data processing server.

In an optional embodiment, the processor 61 is further configured to:

Task start time for obtaining task data;

The task start time is configured into the clear code information, so that the encryption component 63 is used to encrypt the clear code information including the device identification and the task start time to obtain the password information.

In an optional embodiment, the processor 61 is further configured to:

Calculate the check code corresponding to the task data;

Configure the check code into the password information.

Further, as shown in FIG. 6, the autonomous mobile device further includes: a power supply component 64, a flight controller 65, a camera 66 and other components. For example, when the autonomous mobile device is a drone, the autonomous mobile device includes the power supply of the drone, the flight controller of the drone, and the camera installed on the drone. Only some of the components are schematically shown in FIG. 6, which does not mean that the autonomous mobile device only includes the components shown in FIG. 6.

It is worth noting that the technical details in the above embodiments for autonomous mobile devices can be referred to the descriptions in the related embodiments of the aforementioned service authentication method. To save space, we will not repeat them here, but this should not cause any damage to this application. Loss of protection range.

Correspondingly, an embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed, each step that can be executed by an autonomous mobile device in the foregoing method embodiment can be implemented.

FIG. 7 is a schematic structural diagram of a data relay device provided by another embodiment of this application. As shown in FIG. 7, the data relay device includes: a memory 70, a processor 71, and a communication component 72.

The processor 71 is coupled with the memory 70 and the communication component 72, and is configured to execute a computer program in the memory for:

Obtain the task data provided by the autonomous mobile device and the device identification associated with the task data through the communication component 72;

The device identification, or the task data and the device identification, are provided to the data processing server through the communication component 72, so that the data processing server can perform service authentication on the task data based on the device identification.

In an optional embodiment, the processor 72 is further configured to:

Acquire the activation code in response to the service activation operation for the autonomous mobile device;

Obtain the device identification of the autonomous mobile device;

Generate a service activation request based on the activation code and device identification;

The service activation request is sent to the data processing server through the communication component 72 for the data processing server to perform service activation on the autonomous mobile device.

Furthermore, as shown in FIG. 7, the data relay device further includes: a power supply component 73 and other components. Only some components are schematically shown in FIG. 7, which does not mean that the data relay device only includes the components shown in FIG. 7.

It is worth noting that, for the technical details in the foregoing embodiments of the data relay device, reference may be made to the description of the related embodiments of the foregoing service authentication method. In order to save space, the details are not repeated here, but this should not cause any damage to the application. Loss of protection range.

Correspondingly, an embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed, the steps that can be executed by the data relay device in the foregoing method embodiment can be implemented.

Among them, the memories in FIGS. 5, 6 and 7 are used to store computer programs, and can be configured to store various other data to support operations on the device to which they belong. Examples of such data include instructions for any application or method operated on the device to which it belongs, contact data, phone book data, messages, pictures, videos, etc. The memory can be implemented by any type of volatile or non-volatile storage devices or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable and programmable Read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

Wherein, the communication components in Figures 5, 6 and 7 are configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination of them. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may be based on near field communication (NFC) technology, radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, or Other technologies are implemented to facilitate short-range communication.

Among them, the power supply components in Figures 5, 6 and 7 provide power for various components of the equipment where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device where the power supply component is located.

Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

The present invention is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing server to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing server are generated for use. It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing server to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing server, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

In a typical configuration, the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include non-permanent memory in a computer readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.

Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or equipment including a series of elements not only includes those elements, but also includes Other elements that are not explicitly listed, or they also include elements inherent to such processes, methods, commodities, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity, or equipment that includes the element.

The foregoing descriptions are only examples of the present application, and are not used to limit the present application. For those skilled in the art, this application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the scope of the claims of this application.

Claims

A service authentication method, characterized in that it includes:

Obtain the device identification associated with the data to be processed to respond to the service authentication trigger event;

Verifying, according to the service activation record and the device identifier, whether the autonomous mobile device corresponding to the device identifier has performed service activation before the service authentication trigger event occurs;

Based on the verification result, it is determined whether the to-be-processed data passes service authentication.
The method according to claim 1, characterized in that, according to the service activation record and the device ID, verify whether the autonomous mobile device corresponding to the device ID has already activated the service before the service authentication trigger event occurs ,include:

Encrypting the activated activation code and the device identifier together to obtain the first authentication information;

Determine whether there is target activation data matching the first authentication information in the service activation record, and the target activation data is based on the activation obtained during service activation of the autonomous mobile device corresponding to the device identifier Encrypted information obtained by encrypting code and device ID;

If the target activation data exists, it is determined that the autonomous mobile device corresponding to the device identifier has already activated the service before issuing the service authentication request.
The method according to claim 2, wherein the process of performing service activation on the autonomous mobile device corresponding to the device identifier comprises:

Receiving a service activation request, where the service activation request includes an activation code and the device identification of the autonomous mobile device;

If it is determined that the activation code is a usable activation code, encrypt the activation code and the device identification to obtain the target activation data;

The target activation data is saved in the service activation record.
The method according to claim 1, wherein said obtaining the device identification associated with the to-be-processed data comprises:

Obtain the signature file associated with the data to be processed;

Uncheck out the device identification from the signature file.
The method according to claim 4, wherein the signature file includes the clear code information and the secret code information, the clear code information includes at least a device identifier, and the secret code information includes at least an encryption result of the device identifier, Before verifying whether the autonomous mobile device corresponding to the device identifier has performed service activation before the service authentication trigger event occurs, the method further includes:

Judging whether the device identification included in the clear code information is consistent with the device identification decrypted from the secret code information;

If the result of the judgment is yes, the operation of verifying whether the autonomous mobile device corresponding to the device identification has already performed service activation before the occurrence of the service authentication trigger event is performed.
The method according to claim 1, wherein the determining whether the to-be-processed data passes service authentication based on the verification result comprises:

If the verification result is that the autonomous mobile device corresponding to the device identifier has already activated the service before the service authentication trigger event occurs, acquiring the task start time associated with the to-be-processed data;

Acquiring the service activation time corresponding to the autonomous mobile device;

Determine whether the task start time is later than the service activation time;

If yes, it is determined that the to-be-processed data passes service authentication.
The method according to claim 6, wherein the judging whether the task start time is later than the service activation time, further comprises:

Verify that the task start time has not been tampered with; and

In the case where it is determined that the task start time has not been tampered with, the operation of determining whether the task start time is later than the service activation time is performed.
The method according to claim 1, further comprising:

Acquiring a signature file associated with the to-be-processed data, where the signature file includes clear code information and password information, and the clear code information includes at least one of a device identification or a task start time;

Decrypt the secret code information to obtain decrypted secret code information;

Comparing the decrypted code information with the clear code information to determine whether the decrypted code information is consistent with the clear code information;

If the decrypted code information is consistent with the clear code information, it is verified whether the autonomous mobile device corresponding to the device identifier has performed service activation before the service authentication trigger event occurs.
The method according to claim 8, wherein the password information further includes a check code corresponding to the data to be processed; the method further comprises:

Perform verification calculations on the to-be-processed data to obtain an actual verification code;

If the actual check code is consistent with the check code in the secret code information, it is verified whether the autonomous mobile device corresponding to the device identifier has already activated the service before the service authentication trigger event occurs.
The method according to claim 1, wherein the autonomous mobile device is a drone or an unmanned vehicle.
A service authentication method, characterized in that it includes:

Obtain device identification;

Encrypting the device identification to generate password information;

The device identification and the password information are provided to a data processing server for the data processing server to perform service authentication.
The method according to claim 11, wherein said providing said device identification and said secret code information to a data processing server comprises:

Sending the device identification and the secret code information to the data processing server; or

The device identification and the password information are sent to a data relay device, so as to use the data relay device to provide the device identification and the password information to the data processing server.
The method according to claim 11, characterized by comprising:

Sending an encryption request to the encryption component, so as to use the encryption component to encrypt the clear code information including the device identification to obtain encrypted code information;

Generating the signature file according to the clear code information and the secret code information;

Sending the signature file to the data processing server.
The method according to claim 13, further comprising:

Task start time for obtaining task data;

The task start time is configured into the clear code information, so as to use the encryption component to encrypt the clear code information including the device identification and the task start time to obtain the secret code information.
The method according to claim 13 or 14, further comprising:

Calculating the check code corresponding to the task data;

The check code is configured into the secret code information.
A service authentication method, characterized in that it includes:

Acquiring task data provided by an autonomous mobile device and a device identifier associated with the task data;

The device identification, or the task data and the device identification are provided to a data processing server, so that the data processing server performs service authentication on the task data based on the device identification.
The method according to claim 16, further comprising:

In response to the service activation operation for the autonomous mobile device, obtaining an activation code;

Acquiring the device identification of the autonomous mobile device;

Generate a service activation request according to the activation code and the device identifier;

The service activation request is sent to the data processing server for the data processing server to perform service activation on the autonomous mobile device.
A data processing server, which is characterized by comprising a memory, a processor, and a communication component;

The memory is used to store one or more computer instructions;

The processor is coupled with the memory and the communication component, and is configured to execute the one or more computer instructions for:

Obtain the device identification associated with the to-be-processed data through the communication component to respond to the service authentication trigger event;

Verifying, according to the service activation record and the device identifier, whether the autonomous mobile device corresponding to the device identifier has performed service activation before the service authentication trigger event occurs;

Based on the verification result, it is determined whether the to-be-processed data passes service authentication.
An autonomous mobile device, which is characterized by comprising a memory, a processor and a communication component;

The memory is used to store one or more computer instructions;

The processor is coupled with the memory and the communication component, and is configured to execute the one or more computer instructions for:

Obtain device identification;

Encrypting the device identification to generate password information;

The device identifier and the password information are provided to the data processing server through the communication component, so that the data processing server can perform service authentication.
A data relay device, which is characterized by comprising a memory, a processor, and a communication component;

The memory is used to store one or more computer instructions;

The processor is coupled with the memory and the communication component, and is configured to execute the one or more computer instructions for:

Acquiring task data provided by an autonomous mobile device and a device identifier associated with the task data;

The device identification, or the task data and the device identification are provided to a data processing server through the communication component, so that the data processing server performs service authentication on the task data based on the device identification.
The data relay device according to claim 20, wherein the data relay device is a remote control of the autonomous mobile device.
A computer-readable storage medium storing computer instructions, wherein when the computer instructions are executed by one or more processors, the one or more processors are caused to perform the following operations:

Obtain the device identification associated with the data to be processed to respond to the service authentication trigger event;

Verifying, according to the service activation record and the device identifier, whether the autonomous mobile device corresponding to the device identifier has performed service activation before the service authentication trigger event occurs;

Based on the verification result, it is determined whether the to-be-processed data passes service authentication.
A computer-readable storage medium storing computer instructions, wherein when the computer instructions are executed by one or more processors, the one or more processors are caused to perform the following operations:

Obtain device identification;

Encrypting the device identification to generate password information;

The device identification and the password information are provided to a data processing server for the data processing server to perform service authentication.
A computer-readable storage medium storing computer instructions, wherein when the computer instructions are executed by one or more processors, the one or more processors are caused to perform the following operations:

Acquiring task data provided by an autonomous mobile device and a device identifier associated with the task data;

The device identification, or the task data and the device identification are provided to a data processing server, so that the data processing server performs service authentication on the task data based on the device identification.