Permission acquisition method, system and device, electronic equipment and readable storage medium

By establishing a communication connection in an electronic device to obtain the root permission file, the problem of inefficient analysis of abnormalities caused by restarting the root permission in the prior art is solved, and the root permissions are quickly obtained and analysis efficiency is improved.

CN119089425APending Publication Date: 2024-12-06RUILIAN XINGCHEN (BEIJING) TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310620652.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-29
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the prior art, when an abnormality occurs in electronic devices, it is necessary to analyze it by restarting to obtain root permissions, resulting in low efficiency of abnormal analysis, and the restarting destroys the scene, making it impossible to accurately locate the abnormality.

Method used

By establishing a communication connection between the target device and the mobile storage device, performing permission verification and obtaining the root permission file issued by the server, using the pre-set root permission application execution file, obtaining the root permission without restarting the device.

Benefits of technology

It realizes rapid acquisition of root permissions without restarting the electronic device, improves the efficiency of exception analysis, and allows exceptions to be checked based on root permissions without restarting during operation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119089425A_ABST
    Figure CN119089425A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a permission acquisition method, system and device, electronic equipment and a readable storage medium, and relates to the technical field of computers. After a user authorizes and starts a permission acquisition function, a target device in the embodiment of the invention can perform permission verification on the mobile storage device through a communication connection with the mobile storage device, so as to acquire a root permission file from the mobile storage device; and directly executing the root permission file through a preset root permission application program to obtain the root permission. Wherein the root permission file acquired by the target equipment does not need to be written into the system of the target equipment, so that the target equipment does not need to be restarted when acquiring the root permission, and the purpose that the electronic equipment quickly acquires the root permission on the premise that the electronic equipment is not restarted is achieved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a permission acquisition method, system, device, electronic device and readable storage medium. Background Art

[0002] At present, the control permissions of electronic devices are usually divided into general permissions and root permissions (root permissions). General permissions are subject to more restrictions. When an electronic device has an abnormality, it is difficult to locate the abnormality through general permissions. At this time, it is necessary to analyze the electronic device through root permissions to accurately locate the abnormality.

[0003] In the related art, the root permission file is generally compiled into the system of the electronic device. If the electronic device obtains the root permission, the electronic device needs to obtain the root permission file in the system and restart to execute the root permission file. However, since the electronic device will destroy the abnormal scene after restarting, it will cause the electronic device to be unable to analyze the abnormality, which makes the abnormality analysis less efficient. Summary of the invention

[0004] In view of this, embodiments of the present application provide a permission acquisition method, system, device, electronic device and readable storage medium to enable an electronic device to quickly acquire root permissions without restarting the electronic device.

[0005] In a first aspect, a method for obtaining a permission is provided. The method is applied to a permission obtaining system. The permission obtaining system includes at least a target device, a mobile storage device, and a server. The method includes:

[0006] In response to the target device and the mobile storage device establishing a communication connection, the target device performs permission verification on the mobile storage device and determines a verification result.

[0007] In response to the permission verification being passed, the target device obtains the root permission file from the mobile storage device, wherein the root permission file stored in the mobile storage device is issued by a server.

[0008] The target device executes the root authority file based on a preset root authority application to obtain root authority.

[0009] In some embodiments, the target device performs permission verification on the mobile storage device, and determining the verification result includes:

[0010] The target device determines the authentication key stored in the mobile storage device.

[0011] The target device performs authority verification on the mobile storage device based on the verification key and determines a verification result.

[0012] In some embodiments, the permission acquisition system also includes an intermediate device.

[0013] The method further comprises:

[0014] The intermediate device sends authentication information to the server, where the authentication information at least includes a user name, a password, and a root authority acquisition request.

[0015] The server performs authority verification on the authentication information and determines a verification result.

[0016] In response to the permission verification being passed, the server sends the root permission file to the intermediate device.

[0017] In response to establishing a connection with the mobile storage device, the intermediate device generates a verification key corresponding to the mobile storage device.

[0018] The intermediate device sends the verification key and the root authority file to the mobile storage device, so that the mobile storage device stores the verification key and the root authority file.

[0019] In some embodiments, the method further comprises:

[0020] The target device sends authentication information to the server, wherein the authentication information at least includes a user name, a password, and a root authority acquisition request.

[0021] The server performs authority verification based on the authentication information and determines a verification result.

[0022] In response to the permission verification being passed, the server sends a root permission file to the target device.

[0023] The target device executes the root authority file based on a preset root authority application to obtain root authority.

[0024] In some embodiments, the target device is a vehicle control terminal.

[0025] In a second aspect, a method for obtaining permissions is provided, the method being applied to a target device in a permission obtaining system, the method comprising:

[0026] In response to establishing a communication connection with the mobile storage device, performing authority verification on the mobile storage device and determining a verification result.

[0027] In response to the authority verification being passed, a root authority file is obtained from the mobile storage device, wherein the root authority file stored in the mobile storage device is issued by a server.

[0028] The root authority file is executed based on a preset root authority application program to obtain root authority.

[0029] In some embodiments, the performing permission verification on the mobile storage device and determining the verification result comprises:

[0030] A verification key stored in the mobile storage device is determined.

[0031] The mobile storage device is authenticated based on the authentication key to determine an authentication result.

[0032] In some embodiments, the method further comprises:

[0033] Sending authentication information to the server so that the server performs authority verification based on the authentication information and determines a verification result, wherein the authentication information at least includes a user name, a password, and a root authority acquisition request.

[0034] In response to the authority verification being passed, a root authority file sent by the server is received, and the root authority file is executed based on a preset root authority application program to obtain root authority.

[0035] In some embodiments, the target device is a vehicle control terminal.

[0036] In a third aspect, a permission acquisition system is provided, the system comprising at least a target device, a mobile storage device and a server.

[0037] The mobile storage device is configured to store a root authority file.

[0038] The server is configured to issue a root authority file to the mobile storage device.

[0039] The target device is configured to execute, in response to establishing a communication connection with the mobile storage device, performing permission verification on the mobile storage device, determining a verification result, and in response to passing the permission verification, obtaining a root permission file from the mobile storage device, and executing the root permission file based on a pre-set root permission application to obtain root permissions.

[0040] In some embodiments, the target device is specifically configured to determine a verification key stored in the mobile storage device, perform authority verification on the mobile storage device based on the verification key, and determine a verification result.

[0041] In some embodiments, the system further includes an intermediate device.

[0042] The intermediate device is configured to send authentication information to the server so that the server performs authority verification on the authentication information, receive the root authority file sent by the server in response to passing the authority verification, generate a verification key corresponding to the mobile storage device in response to establishing a connection with the mobile storage device, and send the verification key and the root authority file to the mobile storage device, wherein the authentication information includes at least a user name, a password, and a root authority acquisition request.

[0043] In some embodiments, the target device can also be configured to send authentication information to the server so that the server performs authority verification on the authentication information, and in response to passing the authority verification, receive a root authority file sent by the server, and execute the root authority file based on a pre-set root authority application to obtain root authority, wherein the authentication information includes at least a user name, a password, and a root authority acquisition request.

[0044] The server may also be configured to perform permission verification based on the authentication information, determine a verification result, and send a root permission file to the target device in response to passing the permission verification.

[0045] In some embodiments, the target device is a vehicle control terminal.

[0046] In a fourth aspect, a permission acquisition device is provided, the device is applied to a target device in a permission acquisition system, and the device includes:

[0047] The verification module is configured to execute, in response to establishing a communication connection with the mobile storage device, to perform permission verification on the mobile storage device and determine a verification result.

[0048] The file acquisition module is configured to execute, in response to passing the authority verification, acquiring the root authority file from the mobile storage device, wherein the root authority file stored in the mobile storage device is issued by a server.

[0049] The permission acquisition module is configured to execute the root permission file based on a preset root permission application to obtain the root permission.

[0050] In some embodiments, the verification module is specifically configured to perform:

[0051] A verification key stored in the mobile storage device is determined.

[0052] The mobile storage device is authenticated based on the authentication key to determine an authentication result.

[0053] In some embodiments, the apparatus further comprises:

[0054] The sending module is configured to execute sending authentication information to the server so that the server performs authority verification based on the authentication information and determines a verification result, wherein the authentication information at least includes a user name, a password and a root authority acquisition request.

[0055] The receiving module is configured to receive the root authority file sent by the server in response to the authority verification being passed, and execute the root authority file based on a preset root authority application program to obtain the root authority.

[0056] In some embodiments, the target device is a vehicle control terminal.

[0057] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method described in the second aspect.

[0058] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the method described in the first aspect or the second aspect is implemented.

[0059] In a seventh aspect, an embodiment of the present application provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the method described in the first aspect or the second aspect.

[0060] The target device of the embodiment of the present application can perform permission verification on the mobile storage device through the communication connection with the mobile storage device. If the permission verification is passed, the target device can obtain the root permission file from the mobile storage device, and directly execute the root permission file through the pre-set root permission application to obtain the root permission. In other words, since the root permission file obtained by the target device does not need to be written into the system of the target device, the target device does not need to be restarted when obtaining the root permission, thereby achieving the purpose of enabling the electronic device to quickly obtain the root permission without restarting the electronic device. In addition, if an exception occurs in the target device during operation, through the embodiment of the present application, the target device can check the exception based on the root permission without restarting, thereby improving the efficiency of exception analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] The above and other purposes, features and advantages of the embodiments of the present application will become more apparent through the following description of the embodiments of the present application with reference to the accompanying drawings, in which:

[0062] Figure 1 A schematic diagram of a permission acquisition system according to an embodiment of the present application;

[0063] Figure 2 A flowchart of a method for obtaining permissions according to an embodiment of the present application;

[0064] Figure 3 A schematic diagram of another permission acquisition system according to an embodiment of the present application;

[0065] Figure 4 A flowchart of another method for obtaining permissions according to an embodiment of the present application;

[0066] Figure 5 A schematic diagram of another permission acquisition system according to an embodiment of the present application;

[0067] Figure 6 A flowchart of another method for obtaining permissions according to an embodiment of the present application;

[0068] Figure 7 A schematic diagram of another permission acquisition system according to an embodiment of the present application;

[0069] Figure 8 A flowchart of another method for obtaining permissions according to an embodiment of the present application;

[0070] Fig. 9 A schematic diagram of another permission acquisition system according to an embodiment of the present application;

[0071] Fig.10 A schematic diagram of the structure of a permission acquisition device according to an embodiment of the present application;

[0072] Fig.11 A schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0073] The present application is described below based on embodiments, but the present application is not limited to these embodiments. In the detailed description of the present application below, some specific details are described in detail. It is possible for those skilled in the art to fully understand the present application without the description of these details. In order to avoid confusing the essence of the present application, known methods, processes, flows, components and circuits are not described in detail.

[0074] In addition, persons of ordinary skill in the art will appreciate that the drawings provided herein are for illustration purposes and are not necessarily drawn to scale.

[0075] Unless the context clearly requires otherwise, the words "include", "comprising" and the like throughout this application should be interpreted as including rather than exclusive or exhaustive; that is, as meaning "including but not limited to".

[0076] In the description of this application, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, the meaning of "plurality" is two or more.

[0077] The solutions described in this specification and in the examples, if they involve the processing of personal information, will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or being necessary for the performance of a contract, etc.), and will only be processed within the scope of regulations or agreements. If a user refuses to process personal information other than the necessary information for basic functions, it will not affect the user's use of basic functions.

[0078] At present, the control permissions of electronic devices are usually divided into general permissions and root permissions (root permissions), among which the root permissions are also the permissions of the super administrator account, which can add, delete, modify, view and other operations on system files. In one scenario, the electronic device can use the root permissions to check for system anomalies that occur in itself.

[0079] That is to say, since general permissions are subject to more restrictions, when an electronic device has an abnormality, it is difficult to locate the abnormality through general permissions. At this time, it is necessary to analyze the electronic device through root permissions to accurately locate the abnormality.

[0080] In the related art, the root permission file is generally compiled into the system of the electronic device. If the electronic device obtains the root permission, the electronic device needs to obtain the root permission file in the system and restart to execute the root permission file. However, since the electronic device will restart the application program accordingly after the restart, this will destroy the scene where the abnormality occurs (i.e., the application program with the problem), which will cause the electronic device to be unable to analyze the abnormality, thereby making the abnormality analysis less efficient.

[0081] Therefore, how to enable an electronic device to quickly obtain root permissions without restarting the electronic device is a problem that urgently needs to be solved.

[0082] In order to solve the above problems, the embodiments of the present application provide a permission acquisition method and a permission acquisition system, wherein the permission acquisition system may be composed of at least a plurality of electronic devices, and the permission acquisition method of the embodiments of the present application may be applied to the permission acquisition system (that is, it may be applied to each electronic device in the permission acquisition system). The electronic device may include a terminal and a server, the terminal may be a smart phone, a tablet computer, a vehicle control terminal, a mobile storage device or a personal computer (PC), etc., and the server may be a single server, a server cluster configured in a distributed manner, or a cloud server.

[0083] like Figure 1 As shown, the permission acquisition system of the embodiment of the present application may include a target device 11, a mobile storage device 12 and a server 13, wherein the mobile storage device 12 may be configured to store a root permission file, and the root permission file stored in the mobile storage device 12 is issued by the server 13, for example, the mobile storage device 12 may be a special USB flash drive storing a root permission file. The server 13 may be configured to issue a root permission file to the mobile storage device. Data may be transmitted between the target device 11 and the mobile storage device 12 via a wired communication connection or a wireless communication connection. For example, data may be transmitted between the target device 11 and the mobile storage device 12 via a wired connection such as a data cable or a Universal Serial Bus (USB) interface, or via a wireless connection such as Bluetooth, a wireless network (Wi-Fi) or the Internet.

[0084] Furthermore, the target device 11 in the permission acquisition system can execute the permission acquisition method of the embodiment of the present application, so that the target device 11 can quickly obtain the root permission file to obtain the root permission without restarting, thereby improving the efficiency of exception analysis.

[0085] Specifically, Figure 2 As shown, the permission acquisition method in the embodiment of the present application may include the following steps:

[0086] In step S110, in response to establishing a communication connection with the mobile storage device, the mobile storage device is authenticated and a authentication result is determined.

[0087] Among them, a wired communication connection can be established between the target device and the mobile storage device through a data cable or a USB interface, or a wireless communication connection can be established through Bluetooth, a wireless network or the Internet. The permission verification method can be a user name and password verification method, a key verification method, or other applicable methods. The verification result can at least include successful authentication and failed authentication. Successful authentication is used to indicate that the target device can obtain root permissions. Failed authentication is used to indicate that the target device cannot obtain root permissions. Optionally, if the target device is currently unable to perform permission verification processing, the verification result may also include similar prompt information such as permission verification exception or permission verification suspension.

[0088] For example, Figure 3As shown, the target device 11 may include a root authority acquisition process 111 and a wired communication module 112, wherein the root authority acquisition process 111 is a process of the target device 11 when acquiring root authority, which can verify the authority of the mobile storage device 12 through a verification key or other applicable methods, receive the root authority file, and execute the root authority file based on a pre-set root authority application, so that the target device 11 obtains the root authority. The wired communication module 112 can be a wired communication module such as a USB module, which can establish a wired communication connection between the target device 11 and the mobile storage device 12, and transfer the root authority file. The mobile storage device 12 can store the root authority file.

[0089] In one scenario, if the target device 11 cannot directly establish a communication connection with the server through a network or other means, the embodiment of the present application can first obtain the root authority file from the server through other devices, and store the root authority file in the mobile storage device 12. In this way, based on the removable property of the mobile storage device 12, the embodiment of the present application can establish a wired communication connection between the mobile storage device 12 and the target device 11, so that the target device 11 can obtain the root authority file from the mobile storage device 12 at any time.

[0090] It should be noted that the embodiments of the present application are not limited to the above-mentioned scenarios, that is, even if the target device 11 can directly establish a communication connection with the server, the embodiments of the present application can also enable the target device 11 to obtain the root permission file through the mobile storage device 12. In addition, if the target device 11 includes a wireless communication module and the mobile storage device 12 has a wireless communication function, the target device 11 can also establish a communication connection with the mobile storage device 12 through the wireless communication module.

[0091] In an optional embodiment, if Figure 4 As shown, the above step S110 may include the following steps:

[0092] In step S111, the verification key stored in the mobile storage device is determined.

[0093] The verification key can be a symmetric key or an asymmetric key.

[0094] In step S112, the mobile storage device is authenticated based on the authentication key and an authentication result is determined.

[0095] The target device of the embodiment of the present application can be connected to the mobile storage device for communication, and authenticate the mobile storage device through the verification key. After that, if the verification result is passed, the target device can directly obtain the root permission file from the mobile storage device, and directly execute the root permission file through the pre-set root permission application to obtain the root permission. Since the root permission file obtained by the target device does not need to be written into the system of the target device, the target device does not need to be restarted when obtaining the root permission, so that the purpose of enabling the electronic device to quickly obtain the root permission without restarting the electronic device is achieved.

[0096] In step S120, in response to the authority verification being passed, a root authority file is obtained from the mobile storage device.

[0097] The root authority file stored in the mobile storage device is issued by the server.

[0098] In an optional implementation, the permission acquisition system in the embodiment of the present application may further include an intermediate device, wherein the intermediate device may be used to establish a wired or wireless communication connection with the server. Taking the above scenario as an example, the intermediate device in the embodiment of the present application may serve as the above other device to obtain the root permission file from the server and store the root permission file in a mobile storage device.

[0099] like Figure 5 As shown, the target device 11 may include a root authority acquisition process 111 and a wired communication module 112, wherein the root authority acquisition process 111 is a process of the target device 11 when acquiring root authority, which can verify the authority of the mobile storage device 12 through the verification key, receive the root authority file and execute the root authority file based on the pre-set root authority application, so that the target device 11 obtains the root authority. The wired communication module 112 can be a wired communication module such as a USB module, which can establish a wired communication connection between the target device 11 and the mobile storage device 12, and transfer the root authority file. The mobile storage device 12 can store the root authority file. The intermediate device 51 can establish a communication connection with the mobile storage device 12 and the server 13 respectively, request the server 13 to obtain the root authority file through the authentication information, and store the root authority file in the mobile storage device 12.

[0100] Specifically, Figure 6 As shown, the process of storing the root authority file to the mobile storage device 12 through the intermediate device 51 in the embodiment of the present application may include the following steps:

[0101] In step S210 , the intermediate device 51 sends authentication information to the server 13 . Accordingly, the server 13 receives the authentication information sent by the intermediate device 51 .

[0102] The authentication information is at least used to request the server 13 to perform authority verification, and the authentication information at least includes a user name, a password, and a root authority acquisition request.

[0103] In step S220, the server 13 performs authority verification on the authentication information to determine a verification result.

[0104] The verification result may include at least authentication success and authentication failure. Optionally, if the server 13 is currently unable to perform the authority verification process, the verification result may also include similar prompt information such as authority verification exception or authority verification suspension.

[0105] In step S230, in response to the authority verification being passed, the server 13 sends the root authority file to the intermediate device 51. Accordingly, the intermediate device 51 receives the root authority file sent by the server 13.

[0106] In step S240 , in response to establishing a connection with the mobile storage device, the intermediate device 51 generates a verification key corresponding to the mobile storage device.

[0107] The intermediate device 51 and the mobile storage device may establish a wired communication connection through a data cable or a USB interface, or may establish a wireless communication connection through Bluetooth or a wireless network, etc. The verification key may be a symmetric key or an asymmetric key.

[0108] In step S250, the intermediate device 51 sends the verification key and the root authority file to the mobile storage device.

[0109] Combination Figure 5 and Figure 6 As shown in the content, the embodiment of the present application can pre-store the verification key and the root authority file in the mobile storage device 12 through the intermediate device 51. When the target device 11 needs to obtain the root authority, the target device 11 can be connected to the mobile storage device 12 by wired communication, and authenticate the mobile storage device 12 through the verification key and obtain the root authority file. Further, the target device 11 can directly execute the root authority file through the pre-set root authority application to obtain the root authority. In other words, since the root authority file obtained by the target device 11 does not need to be written into the system of the target device 11, the target device 11 does not need to be restarted when obtaining the root authority, and the purpose of enabling the electronic device to quickly obtain the root authority without restarting the electronic device is achieved. In addition, if the target device 11 has an exception during operation, through the embodiment of the present application, the target device 11 can check the exception based on the root authority without restarting, thereby improving the efficiency of exception analysis.

[0110] In step S130, the root authority file is executed based on the preset root authority application to obtain the root authority.

[0111] After obtaining the root authority, the target device can check the abnormality of the target device itself based on the root authority. In this process, since the root authority file obtained by the target device does not need to be written into the system of the target device, the target device does not need to be restarted when obtaining the root authority, thereby achieving the purpose of enabling the electronic device to quickly obtain the root authority without restarting the electronic device. In addition, if an abnormality occurs in the target device during operation, through the embodiment of the present application, the target device can check the abnormality based on the root authority without restarting, thereby improving the efficiency of abnormality analysis.

[0112] In an optional implementation, the target device of the embodiment of the present application may include a wireless communication module, and the target device may establish a wireless communication connection with the server based on the wireless communication module, and send authentication information to the server, so that the server performs permission verification on the authentication information and sends a root permission file to the target device. The authentication information includes at least a user name, a password, and a root permission acquisition request.

[0113] like Figure 7 As shown, the target device 11 may include a root authority acquisition process 111 and a wireless communication module 113, wherein the root authority acquisition process 111 is a process of the target device 11 when acquiring root authority, which can generate authentication information, receive root authority files, and execute root authority files based on a pre-set root authority application program, so that the target device 11 acquires root authority. The wireless communication module 113 can be a wireless communication module such as a Bluetooth module, a 4G module, a 5G module, etc., which can establish a wireless communication connection between the target device 11 and the server 13, and transmit authentication information and root authority files. The server 13 can receive authentication information, perform authority verification, and issue root authority files.

[0114] Specifically, Figure 8 As shown, the embodiment of the present application may also include the following steps:

[0115] In step S310, the target device 11 sends authentication information to the server 13. Correspondingly, the server 13 receives the authentication information sent by the target device 11.

[0116] The authentication information includes at least a user name, a password, and a request for obtaining root authority.

[0117] In step S320, the server 13 performs authority verification based on the authentication information and determines a verification result.

[0118] The verification result may include at least authentication success and authentication failure. Authentication success is used to indicate that the permission verification for the target device 11 has passed, that is, the target device 11 can obtain the root permission. Authentication failure is used to indicate that the permission verification for the target device 11 has not passed, that is, the target device 11 cannot obtain the root permission. Optionally, if the server 13 is currently unable to perform the permission verification process, the verification result may also include similar prompt information such as permission verification exception or permission verification suspension.

[0119] In step S330 , in response to the authority verification being passed, the server 13 sends the root authority file to the target device 11 . Accordingly, the target device 11 receives the root authority file sent by the server 13 .

[0120] In step S340, the target device 11 executes the root authority file based on the preset root authority application to obtain the root authority.

[0121] After obtaining the root authority, the target device 11 can check the abnormality of the target device 11 itself based on the root authority. In this process, since the root authority file obtained by the target device 11 does not need to be written into the system of the target device 11, the target device 11 does not need to be restarted when obtaining the root authority, thereby achieving the purpose of enabling the electronic device to quickly obtain the root authority without restarting the electronic device. In addition, if the target device 11 has an abnormality during operation, through the embodiment of the present application, the target device 11 can check the abnormality based on the root authority without restarting, thereby improving the efficiency of abnormality analysis.

[0122] In an optional implementation, the target device of the embodiment of the present application may be a vehicle control terminal, and the authentication information may also include a vehicle identification code corresponding to the vehicle control terminal, wherein the vehicle identification code may be used to identify the corresponding vehicle control terminal to ensure that the server can correctly issue the root authority file.

[0123] In combination with the above-mentioned embodiments, the present application provides an example of a system for obtaining permissions including a vehicle control terminal, such as Fig. 9 As shown, the vehicle control terminal 91 may include a root authority acquisition process 911, a wireless communication module 912, and a wired communication module 913. The vehicle control terminal 91 may be wirelessly connected or wiredly connected to an external device through the wireless communication module 912 and the wired communication module 913. The server 13 may be a cloud server of a vehicle service platform, the mobile storage device 12 may be a special USB flash drive, and the intermediate device 51 may be a terminal device such as a personal computer.

[0124] In one case, the vehicle control terminal 91 can establish a wireless communication connection with the server 13 through the wireless communication module 912, send authentication information to the server 13, and obtain the root permission file through network authentication. Further, the vehicle control terminal 91 can run a pre-set root permission application through the root permission acquisition process 911 to execute the root permission file and obtain the root permission.

[0125] In another case, the permission acquisition system of the embodiment of the present application may also first send authentication information to the server 13 through the intermediate device 51 to obtain the root authority file through network authentication. Further, the intermediate device 51 can generate a verification key corresponding to the mobile storage device 12, and send the verification key and the root authority file to the mobile storage device 12, so that the mobile storage device 12 stores the verification key and the root authority file. Further, the vehicle control terminal 91 can establish a wired communication connection with the mobile storage device 12 through the wired communication module 913, and perform permission verification on the mobile storage device 12 based on the verification key. If the permission verification passes, the vehicle control terminal 91 can obtain the root authority file from the mobile storage device 12. Further, the vehicle control terminal 91 can run a pre-set root authority application through the root authority acquisition process 911 to execute the root authority file and obtain root authority.

[0126] In the above process, the root permission file obtained by the vehicle control terminal 91 does not need to be written into the system of the vehicle control terminal 91. Therefore, the vehicle control terminal 91 does not need to be restarted when obtaining the root permission, thereby achieving the purpose of enabling the electronic device to quickly obtain the root permission without restarting the electronic device. In addition, if an abnormality occurs during the operation of the vehicle control terminal 91, through the embodiment of the present application, the vehicle control terminal 91 can check the abnormality based on the root permission without restarting, thereby improving the efficiency of abnormality analysis.

[0127] Based on the same technical concept, the embodiment of the present application also provides a permission acquisition device, which can be applied to a target device in a permission acquisition system, such as Fig.10 As shown, the device comprises:

[0128] The verification module 1001 is configured to execute, in response to establishing a communication connection with the mobile storage device, to perform permission verification on the mobile storage device and determine a verification result.

[0129] The file acquisition module 1002 is configured to execute, in response to passing the authority verification, acquiring a root authority file from the mobile storage device, wherein the root authority file stored in the mobile storage device is issued by a server.

[0130] The authority acquisition module 1003 is configured to execute the root authority file based on a preset root authority application program to acquire the root authority.

[0131] In some embodiments, the verification module 1001 is specifically configured to perform:

[0132] A verification key stored in the mobile storage device is determined.

[0133] The mobile storage device is authenticated based on the authentication key to determine an authentication result.

[0134] In some embodiments, the apparatus further comprises:

[0135] The sending module is configured to execute sending authentication information to the server so that the server performs authority verification based on the authentication information and determines a verification result, wherein the authentication information at least includes a user name, a password and a root authority acquisition request.

[0136] The receiving module is configured to receive the root authority file sent by the server in response to the authority verification being passed, and execute the root authority file based on a preset root authority application program to obtain the root authority.

[0137] In some embodiments, the target device is a vehicle control terminal.

[0138] The target device of the embodiment of the present application can perform permission verification on the mobile storage device through the communication connection with the mobile storage device. If the permission verification is passed, the target device can obtain the root permission file from the mobile storage device, and directly execute the root permission file through the pre-set root permission application to obtain the root permission. In other words, since the root permission file obtained by the target device does not need to be written into the system of the target device, the target device does not need to be restarted when obtaining the root permission, thereby achieving the purpose of enabling the electronic device to quickly obtain the root permission without restarting the electronic device. In addition, if an exception occurs in the target device during operation, through the embodiment of the present application, the target device can check the exception based on the root permission without restarting, thereby improving the efficiency of exception analysis.

[0139] Fig.11 is a schematic diagram of an electronic device according to an embodiment of the present application, and the electronic device may be an electronic device (target device, server or intermediate device) in a permission acquisition system. Fig.11 As shown, Fig.11The electronic device shown is a general address query device, which includes a general computer hardware structure, which at least includes a processor 1101 and a memory 1102. The processor 1101 and the memory 1102 are connected via a bus 1103. The memory 1102 is suitable for storing instructions or programs executable by the processor 1101. The processor 1101 can be an independent microprocessor or a collection of one or more microprocessors. Thus, the processor 1101 executes the instructions stored in the memory 1102, thereby executing the method flow of the embodiment of the present application as described above to realize the processing of data and the control of other devices. The bus 1103 connects the above-mentioned multiple components together, and at the same time connects the above-mentioned components to the display controller 1104 and the display device and the input / output (I / O) device 1105. The input / output (I / O) device 1105 can be a mouse, a keyboard, a modem, a network interface, a touch input device, a somatosensory input device, a printer, and other devices known in the art. Typically, the input / output device 1105 is connected to the system via an input / output (I / O) controller 1106.

[0140] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices (equipment) or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may adopt a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0141] The present application is described with reference to flowcharts of methods, apparatuses (devices) and computer program products according to embodiments of the present application. It should be understood that each process in the flowchart can be implemented by computer program instructions.

[0142] These computer program instructions may be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device that implements the process Figure 1 A function specified in a process or multiple processes.

[0143] These computer program instructions may also be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce the instructions for implementing the process Figure 1 A device that specifies functions in a process or multiple processes.

[0144] Another embodiment of the present application relates to a non-volatile storage medium for storing a computer-readable program, wherein the computer-readable program is used for a computer to execute part or all of the above method embodiments.

[0145] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by specifying relevant hardware through a program, and the program is stored in a storage medium, including several instructions for a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0146] Another embodiment of the present application relates to a computer program product, including a computer program / instruction, which can implement part or all of the above method embodiments when the computer program / instruction is executed by a processor.

[0147] That is, those skilled in the art can understand that the embodiments of the present application can specify relevant hardware (including the processor itself) through the processor executing a computer program product (computer program / instructions), thereby implementing all or part of the steps in the above-mentioned embodiment method.

[0148] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for obtaining permissions, characterized in that: The method is applied to a permission acquisition system, which at least includes a target device, a mobile storage device and a server. The method includes: In response to the target device and the mobile storage device establishing a communication connection, the target device performs permission verification on the mobile storage device and determines a verification result; In response to the permission verification being passed, the target device obtains a root permission file from the mobile storage device, wherein the root permission file stored in the mobile storage device is issued by a server; and The target device executes the root authority file based on a preset root authority application to obtain root authority.

2. The method according to claim 1, characterized in that The target device performs permission verification on the mobile storage device, and determines the verification result includes: The target device determines the authentication key stored in the mobile storage device; and The target device performs authority verification on the mobile storage device based on the verification key and determines a verification result.

3. The method according to claim 2, characterized in that The authority acquisition system also includes an intermediate device; The method further comprises: The intermediate device sends authentication information to the server, wherein the authentication information includes at least a user name, a password, and a root authority acquisition request; The server performs authority verification on the authentication information and determines a verification result; In response to the permission verification being passed, the server sends a root permission file to the intermediate device; The intermediate device generates a verification key corresponding to the mobile storage device in response to establishing a connection with the mobile storage device; and The intermediate device sends the verification key and the root authority file to the mobile storage device, so that the mobile storage device stores the verification key and the root authority file.

4. The method according to claim 1, characterized in that The method further comprises: The target device sends authentication information to the server, wherein the authentication information at least includes a user name, a password, and a root authority acquisition request; The server performs authority verification based on the authentication information and determines a verification result; In response to the permission verification being passed, the server sending a root permission file to the target device; and The target device executes the root authority file based on a preset root authority application to obtain root authority.

5. The method according to any one of claims 1 to 4, characterized in that The target device is a vehicle control terminal.

6. A method for obtaining permissions, characterized in that: The method is applied to a target device in a permission acquisition system, and the method comprises: In response to establishing a communication connection with the mobile storage device, performing authority verification on the mobile storage device and determining a verification result; In response to the permission verification being passed, obtaining a root permission file from the mobile storage device, wherein the root permission file stored in the mobile storage device is issued by a server; and The root authority file is executed based on a preset root authority application program to obtain root authority.

7. A system for obtaining permissions, characterized in that: The system at least includes a target device, a mobile storage device and a server; The mobile storage device is configured to store a root authority file; The server is configured to issue a root authority file to the mobile storage device; The target device is configured to execute, in response to establishing a communication connection with the mobile storage device, performing permission verification on the mobile storage device, determining a verification result, and in response to passing the permission verification, obtaining a root permission file from the mobile storage device, and executing the root permission file based on a pre-set root permission application to obtain root permissions.

8. The system according to claim 7, characterized in that The target device is specifically configured to determine the verification key stored in the mobile storage device, perform authority verification on the mobile storage device based on the verification key, and determine a verification result.

9. The system according to claim 8, characterized in that The system also includes an intermediate device; The intermediate device is configured to send authentication information to the server so that the server performs authority verification on the authentication information, receive the root authority file sent by the server in response to passing the authority verification, generate a verification key corresponding to the mobile storage device in response to establishing a connection with the mobile storage device, and send the verification key and the root authority file to the mobile storage device, wherein the authentication information includes at least a user name, a password, and a root authority acquisition request.

10. The system according to claim 7, characterized in that The target device may also be configured to send authentication information to the server so that the server performs permission verification on the authentication information, and in response to passing the permission verification, receive a root permission file sent by the server, and execute the root permission file based on a preset root permission application to obtain root permission, wherein the authentication information includes at least a user name, a password, and a root permission acquisition request; The server may also be configured to perform permission verification based on the authentication information, determine a verification result, and send a root permission file to the target device in response to passing the permission verification.

11. The system according to any one of claims 7 to 10, characterized in that: The target device is a vehicle control terminal.

12. A permission acquisition device, characterized in that: The device is applied to a target device in a permission acquisition system, and the device includes: A verification module, configured to execute, in response to establishing a communication connection with the mobile storage device, to perform permission verification on the mobile storage device and determine a verification result; A file acquisition module is configured to acquire a root authority file from the mobile storage device in response to passing the authority verification, wherein the root authority file stored in the mobile storage device is issued by a server; and The permission acquisition module is configured to execute the root permission file based on a preset root permission application to obtain the root permission.

13. An electronic device comprising a memory and a processor, characterized in that: The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method according to claim 6.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

15. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented.