CN111756703A

CN111756703A - Debugging interface management method and device and electronic equipment

Info

Publication number: CN111756703A
Application number: CN202010493578.0A
Authority: CN
Inventors: 陈建波; 屠一凡; 孙鸿青
Original assignee: Lazas Network Technology Shanghai Co Ltd
Current assignee: Lazas Network Technology Shanghai Co Ltd
Priority date: 2020-06-03
Filing date: 2020-06-03
Publication date: 2020-10-09

Abstract

The invention relates to the technical field of computers, and discloses a debugging interface management method, a debugging interface management device and electronic equipment. The method comprises the following steps: receiving an instruction input by a user for starting an ADB interface of an android debug bridge of the equipment; acquiring a communication number bound with a debugging interface management function of the equipment according to the instruction; controlling to send a first verification code to the acquired communication number; receiving a second verification code input by the user; and if the second verification code is matched with the first verification code, starting the ADB interface. Through the mode, the embodiment of the invention improves the safety of ADB interface connection.

Description

Debugging interface management method and device and electronic equipment

Technical Field

The invention relates to the technical field of computers, in particular to a debugging interface management method and device and electronic equipment.

Background

Most of electronic devices with Android operating systems have remote or local debugging functions. An Android Debug Bridge (ADB) is a command line tool in an Android system, which can directly operate and Debug an Android device such as an Android mobile phone or a simulator. After entering the debugging mode, operations such as information reading of the android system, user data reading and the like can be performed. If any user can open the ADB interface, system security may be poor.

Currently, in most android systems, an option of "open/close an android ADB interface" is provided on a setting page of the android system, and any user (including an administrator and a general user) can perform operations. In the prior art, a password protection mode is adopted to carry out authority control on an android ADB interface so as to improve the security level, but the protection mode cannot be associated with the user identity, and the password is easy to crack.

Disclosure of Invention

In view of the above, embodiments of the present invention are proposed to provide a debug interface management method, apparatus and electronic device that overcome or at least partially solve the above problems.

According to an aspect of an embodiment of the present invention, there is provided a debug interface management method, including:

receiving an instruction input by a user for starting an ADB interface of an android debug bridge of the equipment;

acquiring a communication number bound with a debugging interface management function of the equipment according to the instruction;

controlling to send a first verification code to the acquired communication number;

receiving a second verification code input by the user;

and if the second verification code is matched with the first verification code, starting the ADB interface.

In some embodiments, the method further comprises:

and responding to the instruction of starting the ADB interface of the equipment, and reporting early warning information, wherein the early warning information comprises an equipment identifier and a communication number bound with the ADB interface management function of the equipment.

In some embodiments, the pre-warning information further includes a timestamp.

In some embodiments, the method further comprises:

and if the time for opening the ADB interface reaches the preset time length, closing the ADB interface.

In some embodiments, the first verification code is a randomly generated verification code.

In some embodiments, the controlling sending the first verification code to the acquired communication number includes:

sending the acquired communication number to a short message verification module so that the short message verification module sends a first verification code to the communication number;

if the second verification code is matched with the first verification code, the ADB interface is opened, including:

receiving a first verification result sent by the short message verification module, wherein the first verification result is a verification result for verifying whether the second verification code is matched with the first verification code;

and if the first verification result is that the second verification code is matched with the first verification code, the ADB interface is opened.

generating the first verification code;

sending the acquired communication number and the generated first verification code to a short message verification module so that the short message verification module sends the first verification code to the communication number;

judging whether the second verification code is matched with the first verification code;

In some embodiments, the method further comprises:

receiving the communication number input by the user from a communication number binding interface, wherein the communication number is used for binding an ADB interface management function of the equipment;

controlling to send a third verification code to the received communication number;

receiving a fourth verification code input by the user;

and if the fourth verification code is matched with the third verification code, binding the communication number with an ADB interface management function of the equipment.

In some embodiments, the controlling sending a third validation code to the received communication number includes:

sending the received communication number to a short message verification module so that the short message verification module sends a third verification code to the communication number;

if the fourth verification code is matched with the third verification code, the step of binding the communication number to an ADB interface management function of the equipment comprises the following steps:

receiving a second verification result sent by the short message verification module, wherein the second verification result is a verification result for verifying whether the fourth verification code and the third verification code are matched;

and if the second verification result is that the fourth verification code is matched with the third verification code, the communication number binds an ADB interface management function of the equipment.

generating the third verification code;

sending the received communication number and the third verification code to a short message verification module so that the short message verification module sends the third verification code to the communication number;

judging whether the fourth verification code is matched with the third verification code;

In some embodiments, the third passcode is a randomly generated passcode.

In some embodiments, after the obtaining the communication number bound to the debug interface management function of the device, the method further comprises:

and if the communication number bound with the debugging interface management function of the equipment is not acquired, displaying a communication number binding interface.

In some embodiments, the communication number is a mobile phone number, and the first verification code and the third verification code are sent by a short message; or,

the communication number is a communication software account, and the first verification code and the third verification code are sent through a communication message.

In some embodiments, the method further comprises:

prompting a user to input biometric information;

receiving second biological characteristic information input by a user;

and if the second verification code is matched with the first verification code and the second biological characteristic information is matched with the first biological characteristic information bound with the ADB interface management function of the equipment, starting the ADB interface.

According to another aspect of the embodiments of the present invention, there is provided a debug interface management apparatus, including:

the device comprises a first receiving module, a second receiving module and a control module, wherein the first receiving module is used for receiving an instruction input by a user for starting an ADB interface of the android debug bridge of the device;

the acquisition module is used for acquiring a communication number bound with a debugging interface management function of the equipment according to the instruction;

the first control module is used for controlling the sending of a first verification code to the acquired communication number;

the second receiving module is used for receiving a second verification code input by the user;

and the starting module is used for starting the ADB interface if the second verification code is matched with the first verification code.

In some embodiments, the apparatus further comprises:

and the reporting module is used for responding to the instruction of starting the ADB interface of the equipment and reporting early warning information, wherein the early warning information comprises an equipment identifier and a communication number bound with the ADB interface management function of the equipment.

In some embodiments, the pre-warning information further includes a timestamp.

In some embodiments, the apparatus further comprises:

and the closing module is used for closing the ADB interface if the time for opening the ADB interface reaches the preset time length.

In some embodiments, the first control module is further to:

the opening module is further configured to:

In some embodiments, the first control module is further to:

generating the first verification code;

the opening module is further configured to:

In some embodiments, the apparatus further comprises:

a third receiving module, configured to receive, from a communication number binding interface, the communication number input by the user, where the communication number is used to bind an ADB interface management function of the device;

the second control module is used for controlling the sending of a third verification code to the received communication number;

the fourth receiving module is used for receiving a fourth verification code input by the user;

and the binding module is used for binding the communication number with an ADB interface management function of the equipment if the fourth verification code is matched with the third verification code.

In some embodiments, the second control module is further configured to:

the binding module is further to:

In some embodiments, the second control module is further configured to:

generating the third verification code;

the binding module is further to:

In some embodiments, the third passcode is a randomly generated passcode.

In some embodiments, the apparatus further comprises:

and the display module is used for displaying a communication number binding interface if the communication number bound with the debugging interface management function of the equipment is not acquired.

In some embodiments, the apparatus further comprises:

the prompting module is used for prompting a user to input biological characteristic information;

the fifth receiving module is used for receiving second biological characteristic information input by the user;

the opening module is further configured to:

According to still another aspect of an embodiment of the present invention, there is provided an electronic apparatus including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the debugging interface management method.

According to another aspect of the embodiments of the present invention, a computer storage medium is provided, where at least one executable instruction is stored in the storage medium, and the executable instruction causes a processor to execute an operation corresponding to the above debugging interface management method.

According to the embodiment of the invention, the authority management is carried out on the ADB interface opened by the user in a mode of sending the verification code to the communication number bound with the debugging interface management function of the equipment, when the verification code input by the user is the same as the verification code of the communication number sent to the user, the ADB interface is opened, and the authority management of the ADB interface is carried out in a mode of the verification code, so that the ADB interface is not easy to crack in modes of exhaustion, bypass and the like, and the safety is improved.

The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and the embodiments of the present invention can be implemented according to the content of the description in order to make the technical means of the embodiments of the present invention more clearly understood, and the detailed description of the embodiments of the present invention is provided below in order to make the foregoing and other objects, features, and advantages of the embodiments of the present invention more clearly understandable.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the embodiments of the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a schematic view of an application scenario of a debug interface management method according to an embodiment of the present invention;

FIG. 2 is a flowchart of a debug interface management method provided by an embodiment of the present invention;

FIG. 3 is an interaction diagram of a debug interface management method according to an embodiment of the present invention;

FIG. 4 is a flowchart of another debug interface management method provided by an embodiment of the present invention;

FIG. 5 is an interaction diagram of another debug interface management method provided by an embodiment of the present invention;

FIG. 6 is a flowchart illustrating time effectiveness management in a debug interface management method according to an embodiment of the present invention;

FIG. 7 is a flowchart of a further method for debugging interface management according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a debug interface management apparatus according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

Referring to fig. 1, fig. 1 is a schematic view of an application scenario of a debug interface management method according to an embodiment of the present invention. The method comprises the steps that a user applies for opening an Android Debug Bridge (ADB) interface on a device to be debugged, the device to be debugged sends a short message verification code to a mobile phone number bound with the device through a short message verification server, the user obtains the short message verification code from a terminal used by the mobile phone number of the user, the short message verification code is input into the device to be debugged, the device to be debugged verifies whether the short message verification code input by the user is correct through the short message verification server, and the ADB interface is opened for debugging of the user if the short message verification code input by the user is correct. And the device to be debugged sends the action of applying for opening the ADB interface by the user to the management platform for early warning.

The device to be debugged may be any device installed with an android operating system, and the device has an ADB interface, such as a Point Of Sale (POS), a cash register and POS integrated machine, a smart phone, a tablet computer, a portable Digital camera, a media player, a portable game device, a Personal Digital Assistant (PDA), a desktop computer, a notebook computer, and the like.

The user may be a person of the manufacturer of the device to be debugged, including a developer, technical support, or other type of administrator. The user may also be a person who uses the device to be debugged after the device to be debugged leaves the factory, for example, a worker of a merchant who purchases the device to be debugged.

The verification code can be a verification code sent by a short message, and at the moment, the terminal of the user can be an electronic device such as a mobile phone and the like which can receive the short message. The communication number of the user is a mobile phone number, and the mobile phone number can be the mobile phone number of research personnel and technical support personnel of a manufacturer of the device to be debugged, or the mobile phone number of an administrator set by the manufacturer, or the mobile phone number of a worker of a merchant who purchases the device to be debugged.

The verification code may also be a verification code transmitted by other communication software, and in this case, the terminal of the user may be any electronic device capable of performing communication, such as a smart phone, a tablet computer, a portable digital camera, a media player, a portable game device, a Personal Digital Assistant (PDA), a desktop computer, a notebook computer, and the like. The communication number of the user may be a communication software number of a person of a manufacturer of the device to be debugged, a communication software number of a manager set by the manufacturer, or a communication software number of a worker of a merchant who purchases the device to be debugged. In the embodiment of the present invention, a terminal is taken as a mobile phone, and a verification code is taken as a short message verification code.

And when the equipment manufacturer to be debugged purchases the short message verification service of the third party, the short message verification server is the short message verification server of the third party. When the manufacturer of the device to be debugged develops the short message verification service, the short message verification server can be a server of the manufacturer of the device to be debugged.

The management server is a server of a manufacturer of the equipment to be debugged, provides a management platform for managing the equipment to be debugged and user binding information thereof, receives early warning information of ADB interface connection reported by the equipment to be debugged, and sends warning prompt and the like to an administrator.

Binding before leaving a factory:

fig. 2 is a flowchart of a debug interface management method according to an embodiment of the present invention, and fig. 3 is an interaction diagram of the debug interface management method according to an embodiment of the present invention. As shown in fig. 2 and 3, the method includes:

step 201: the device to be debugged is connected with the management server.

Before the device to be debugged leaves a factory, a technician (hereinafter referred to as a "first user") of a device manufacturer to be debugged connects the device to be debugged to a management server through a wireless network or a wired network, so that binding information can be sent to the management server for storage after user mobile phone numbers are subsequently bound. It will be appreciated that this step may also be performed when binding information needs to be sent to the management server.

Step 202: the device to be debugged judges whether a mobile phone number is bound; if yes, go to step 203, otherwise, end.

After the ADB interface of the device to be debugged is required to be opened, a verification code is sent to the bound mobile phone number to carry out permission verification of operating the ADB interface. For example, the binding confirmation interface may prompt "whether a mobile phone number is bound for the ADB interface management function of the device", and display two command input buttons of "yes" and "no". If the first user clicks the "yes" button in the binding confirmation interface, the device to be debugged receives an instruction of the first user confirming the binding of the mobile phone number, and in response to the instruction, the step 203 is continuously executed to perform the binding operation. And if the first user clicks a No button in the binding confirmation interface, the equipment to be debugged receives an instruction that the first user confirms that the mobile phone number is not bound, and the binding operation is finished in response to the instruction. The binding confirmation interface may also be any other interface in any presentation form, as long as the interface can receive the confirmation operation of the first user on whether to bind the mobile phone number.

This step is triggered by the execution of step 201, that is, after the device to be debugged is connected to the management server, a binding confirmation interface is displayed on the display screen of the device to be debugged. It can be understood that, in some embodiments, if step 201 is not executed at the beginning, that is, the device to be debugged is not connected to the management server, the operation of this step may also be triggered in a manner that the first user manually selects the "bound mobile phone number" function, or the operation of this step is automatically triggered when the device to be debugged is turned on each time and an unbound mobile phone number is detected.

Step 203: the device to be debugged receives the mobile phone number input by the first user and sends a short message verification request to the short message verification server.

After receiving an instruction of confirming that the mobile phone number is bound by the first user, displaying a mobile phone number input interface in a display screen of the device to be debugged, and receiving the mobile phone number to be bound input by the first user through the mobile phone number input interface. For example, a prompt of "please input a mobile phone number to be bound" may be provided on the mobile phone number input interface, and a mobile phone number input box may be displayed. The first user may input a mobile phone number to be bound in the input box, for example, a mobile phone number of an administrator of a manufacturer of the device to be debugged or a mobile phone number of a technical support person. And after receiving the mobile phone number input by the first user, the device to be debugged sends a short message verification request to a short message verification server. The short message verification request comprises a mobile phone number and an identifier of the device to be communicated. The identifier of the device to be debugged may be a physical address or a serial number of the device to be debugged, the physical address is a hardware identifier of the device to be debugged, and is determined by hardware of the device to be debugged, and the serial number is an identifier allocated by the management server to the device to be debugged.

Before the device to be debugged sends the short message verification request to the short message server, the first user can be prompted whether to send a verification code to the mobile phone number of the first user, if the first user confirms to send the verification code, the short message verification request is sent to the short message verification server, and if not, the operation is finished.

Step 204: the short message verification server sends a first short message verification code to the mobile phone using the mobile phone number.

And after receiving the mobile phone number, the short message verification server generates a first short message verification code. The first short message verification code can be a randomly generated verification code, and the security is high. For example, the short message authentication server may randomly generate an authentication code using a random function, and the number of bits of the authentication code may be preset, for example, 4 bits or 6 bits. The short message verification server stores information such as the mobile phone number, the first short message verification code, the identifier of the equipment to be communicated and the like in the Session controller Session, and the information is used for later verification.

The short message verification server calls the short message interface to send the mobile phone number and the first short message verification code to an operator to which the mobile phone number belongs. And after the operator checks the number, the operator sends the first short message verification code to the mobile phone using the mobile phone number in a short message mode.

Step 205: and the equipment to be debugged receives the second short message verification code input by the first user and sends the second short message verification code to the short message verification server.

And a verification code input box can be simultaneously displayed in the mobile phone number input interface of the equipment to be debugged. After the mobile phone of the first user receives the first short message verification code, the first user inputs the verification code in the verification code input box of the device to be debugged. The verification code input by the first user at this time may be the same as the first short message verification code or different from the first short message verification code, so we define the verification code input by the first user at this time as the second short message verification code. And the equipment to be debugged receives a second short message verification code input by the first user and sends the second short message verification code to the short message verification server. When the device to be communicated sends the second short message verification code to the short message verification server, the mobile phone number or the identifier of the device to be communicated can be carried at the same time, so that the corresponding first short message verification code can be matched in the later verification.

Step 206: and the short message verification server judges whether the verification is passed or not and sends a verification result to the equipment to be debugged.

After receiving the second short message verification code, the short message verification server judges whether the second short message verification code submitted by the first user is consistent with the first short message verification code stored in the Session of the Session controller, and if so, the verification is passed; otherwise, the verification fails. If the verification is passed, the short message verification server sends a verification result of passing the verification to the equipment to be debugged; and if the verification fails, the short message verification server sends a verification result that the verification fails to pass to the equipment to be debugged.

Step 207: and if the verification result that the verification is passed is received, the equipment to be debugged binds the mobile phone number, and stores and sends the first binding information to the management server.

After receiving the verification result that the verification is passed, the device to be debugged binds the ADB interface management function to the mobile phone number, generates first binding information, locally stores the first binding information, and sends the first binding information to the management server. The first binding information is information of successful binding, and the first binding information comprises an identifier, a mobile phone number, a timestamp and the like of the device to be debugged. The identifier of the device to be debugged may be a physical address or a serial number of the device to be debugged.

Step 208: and if a verification result that the verification fails is received, the device to be debugged prompts that the verification fails, and second binding information is sent to the management server.

And if the verification fails, the equipment to be debugged generates second binding information and sends the second binding information to the management server. The second binding information is information that binding is unsuccessful, and the second binding information includes an identifier of the device to be debugged, a mobile phone number, a timestamp, and the like.

If the verification fails, the device to be debugged can prompt the first user to continue sending and verifying the verification code except that the verification fails on the display screen until the binding is successful. Or, the operation is directly ended.

Step 209: and the management server receives and stores the binding information.

Whether the binding is successful or not, the equipment to be debugged sends the binding information generated by each binding operation to the management server, and the management server stores the binding information of each binding operation. The binding information includes first binding information that binding is successful and second binding information that binding is unsuccessful. The binding operation of the device end to be debugged can be sensed by the management server, so that the safety is improved.

In the embodiment of the invention, the equipment to be debugged calls the short message verification server to send and verify the short message verification code. In some embodiments, the device to be debugged may also call the short message verification server to send the short message verification code, but the verification is performed locally on the device to be debugged. For example, the short message verification server sends the first short message verification code to the mobile phone using the mobile phone number, and also sends the first short message verification code back to the device to be debugged. After receiving the second short message verification code input by the first user, the device to be debugged locally performs matching verification of the first short message verification code and the second short message verification code. However, since the device to be communicated receives the first short message check code, the first short message check code may be acquired or intercepted by an unauthorized user in an unauthorized manner, and the security of the manner of checking by the short message verification server is high.

In other embodiments, the generation and verification of the first short message verification code may be performed locally on the device to be debugged, and the device to be debugged only calls the short message verification server to transmit the first short message verification code. For example, the device to be debugged receives a mobile phone number input by a first user, generates a first short message verification code, and sends a short message verification request to a short message verification server. The short message verification request comprises a mobile phone number and a first short message verification code. After receiving the second short message verification code input by the first user, the device to be debugged locally performs matching verification of the first short message verification code and the second short message verification code. However, the first short message check code is locally generated by the device to be communicated, the first short message check code may be acquired by an unauthorized user in an unauthorized manner, and the security of the manner of generating the first short message check code and checking by the short message verification server is higher.

Debugging after delivery:

fig. 4 is a flowchart of another debug interface management method provided in an embodiment of the present invention, and fig. 5 is an interaction diagram of another debug interface management method provided in an embodiment of the present invention, where the method is a step executed after a device to be debugged leaves a factory, and as shown in fig. 4 and fig. 5, the method includes:

step 301: and the device to be debugged receives a second user input instruction for starting the ADB interface of the device.

After the equipment to be debugged leaves a factory, if the equipment to be debugged needs to be debugged remotely or locally, the ADB interface of the equipment to be debugged needs to be opened. After the ADB interface is opened, operations such as information reading of the android system, user data reading and the like can be performed. The user who debugs the device to be debugged after leaving the factory may be a technical support person of a manufacturer of the device to be debugged or a worker of a merchant of the device to be debugged. In the embodiment of the invention, a user who applies for opening the ADB interface after leaving the factory is called as a second user.

The device to be debugged can set an option of opening/closing an android ADB interface on a setting page of an android operating system of the device to be debugged, and the second user inputs an instruction of opening the ADB interface of the device to be debugged by selecting the option. After the option is selected, the ADB interface is not directly opened, and verification of the verification code is required. In some embodiments, the second user-input instruction to turn on the ADB interface of the device may also be received through any other interface of the display screen of the device to be commissioned.

Step 302: the device to be debugged judges whether a mobile phone number bound with the ADB interface management function of the device to be debugged exists or not according to the instruction for starting the ADB interface; if so, go to step 303, otherwise, go to step 309.

In the embodiments shown in fig. 2 and fig. 3, before shipment, a manufacturer of the device to be debugged may already bind a mobile phone number to an ADB interface management function of the device to be debugged, and the device to be debugged stores binding information. And the device to be debugged responds to the instruction for starting the ADB interface input by the second user, and locally searches the binding information so as to judge whether the mobile phone number bound with the ADB interface management function of the device to be debugged exists. And if the binding information is found, confirming that the mobile phone number bound with the ADB interface management function of the equipment to be debugged exists.

Step 303: and the device to be debugged acquires the mobile phone number bound with the ADB interface management function of the device to be debugged and sends a short message verification request to the short message verification server.

And the equipment to be debugged acquires the mobile phone number from the searched binding information and sends a short message verification request to the short message verification server. The short message verification request comprises the acquired mobile phone number and the identification of the device to be communicated. The identifier of the device to be debugged may be a physical address or a serial number of the device to be debugged. Before the device to be debugged sends the short message verification request to the short message server, the second user can be prompted whether to send a verification code to the mobile phone number of the second user, if the second user confirms to send the verification code, the short message verification request is sent to the short message verification server, and if not, the operation is finished.

Step 304: and the short message verification server sends a third short message verification code to the mobile phone using the mobile phone number.

And after receiving the mobile phone number, the short message verification server generates a third short message verification code. The third short message verification code is similar to the first short message verification code in the foregoing embodiment, and may be a randomly generated verification code, which is higher in security. For example, the short message authentication server may randomly generate an authentication code using a random function, and the number of bits of the authentication code may be preset, for example, 4 bits or 6 bits. The short message verification server can save the information such as the mobile phone number, the third short message verification code, the identifier of the equipment to be communicated and the like in the Session controller Session to be used for later verification. Store

And the short message verification server calls the short message interface to send the mobile phone number and the third short message verification code to the operator to which the mobile phone number belongs. And after the operator checks the number, the third short message verification code is sent to the mobile phone using the mobile phone number in a short message mode.

Step 305: and the equipment to be debugged receives a fourth short message verification code input by the second user and sends the fourth short message verification code to the short message verification server.

And the equipment to be debugged displays a verification code input box for receiving the verification code input by the second user. And after the mobile phone of the second user receives the third short message verification code, the second user inputs the verification code in a verification code input box of the device to be debugged. The verification code input by the second user at this time may be the same as the third short message verification code or different from the third short message verification code, so we define the verification code input by the second user at this time as the fourth short message verification code. And the device to be debugged receives a fourth short message verification code input by the second user and sends the fourth short message verification code to the short message verification server. When the device to be communicated sends the fourth short message verification code to the short message verification server, the device to be communicated can simultaneously carry the mobile phone number or the identifier of the device to be communicated, so that the corresponding third short message verification code can be matched during later verification.

Step 306: and the short message verification server judges whether the verification is passed or not and sends a verification result to the equipment to be debugged.

After receiving the fourth short message verification code, the short message verification server judges whether the fourth short message verification code submitted by the second user is consistent with the third short message verification code stored in the Session of the Session controller, and if so, the verification is passed; otherwise, the verification fails. If the verification is passed, the short message verification server sends a verification result of passing the verification to the equipment to be debugged; and if the verification fails, the short message verification server sends a verification result that the verification fails to pass to the equipment to be debugged.

Step 307: and if the verification result that the verification is passed is received, the device to be debugged starts an ADB interface.

And after receiving the verification result that the verification is passed, indicating that the second user is an authorized user, and starting an ADB interface by the device to be debugged.

Step 308: and if a verification result that the verification fails is received, the device to be debugged prompts that the verification fails.

If the verification fails, the second user is an unauthorized user, or the second user is an authorized user but inputs an incorrect verification code. At this time, the device to be debugged can prompt the second user to continue sending and verifying the verification code until the verification is successful, except that the verification is not passed on the display screen. Or, the operation is directly ended.

Step 309: and the device to be debugged prompts the second user to bind the mobile phone number.

In step 302, the device to be debugged determines that there is no mobile phone number bound to the ADB interface management function of the device to be debugged, so that the second user can be prompted whether to bind the mobile phone number. For example, the device to be debugged may display a binding confirmation interface, prompt "whether a mobile phone number is bound for the ADB interface management function of the device", and display two command input buttons of "yes" and "no". If the second user clicks the "yes" button in the binding confirmation interface, the device to be debugged receives an instruction of the second user confirming the binding of the mobile phone number, and in response to the instruction, the step 310 is continuously executed to perform the binding operation. And if the second user clicks a No button in the binding confirmation interface, the equipment to be debugged receives an instruction that the second user confirms that the mobile phone number is not bound, and the binding operation is finished in response to the instruction. The binding confirmation interface may also be any other interface in any presentation form, as long as the interface can receive the confirmation operation of the second user on whether to bind the mobile phone number.

In some embodiments, the device to be debugged may further perform the binding operation by default when it is determined that there is no mobile phone number bound to the ADB interface management function of the device to be debugged. At this time, only the second user is prompted to perform mobile phone number binding on the binding confirmation interface, and the second user does not need to select whether to perform a binding instruction.

Step 310: and the device to be debugged receives the mobile phone number input by the second user and sends a short message verification request to the short message verification server.

Step 311: the short message verification server sends a first short message verification code to the mobile phone using the mobile phone number.

Step 312: and the equipment to be debugged receives a second short message verification code input by a second user and sends the second short message verification code to the short message verification server.

Step 313: and the short message verification server judges whether the verification is passed or not and sends a verification result to the equipment to be debugged.

Step 314: and if the verification result that the verification is passed is received, the equipment to be debugged binds the mobile phone number, and stores and sends the first binding information to the management server.

After the mobile phone number is bound, step 303 may be executed to continue the verification of the ADB connection.

Step 315: and if a verification result that the verification fails is received, the device to be debugged prompts that the verification fails, and second binding information is sent to the management server.

Step 316: and the management server receives and stores the binding information.

The above step 310-.

Step 317: and the equipment to be debugged reports the early warning information to the management server.

And reporting early warning information to the management server by the equipment to be debugged under the condition that the equipment passes or does not pass the verification. That is, the device to be debugged reports the early warning information in response to the instruction for starting the ADB interface of the device. Step 317 is performed at the same time or after the ADB interface is opened at step 307, and also at the same time or after the verification fails at step 308. The early warning information comprises an equipment identifier and a mobile phone number bound with an ADB interface management function of the equipment. The pre-warning information may also include a timestamp.

Whether the verification code is successfully verified or not, the ADB connection and verification operation can report information to the management server. Through the early warning information, the management server can know who and when to connect the ADB interface of the device to be debugged. After receiving the early warning information, the management server can generate warning information to an administrator. The actions of ADB connection debugging of the device end to be debugged can be sensed by the management server, so that the safety is further improved.

After the second user actively disconnects the ADB connection, the ADB interfacing operation is completed.

According to the embodiment of the invention, the authority management is carried out on the ADB interface opened by the user in a mode of sending the verification code to the communication number bound with the debugging interface management function of the equipment, when the verification code input by the user is the same as the verification code of the communication number sent to the user, the ADB interface is opened, and the authority management of the ADB interface is carried out in a mode of the verification code, so that the ADB interface is not easy to crack in modes of exhaustion, bypass and the like, and the safety is improved. In the related art, the password identification, the gesture identification, the fingerprint identification and other modes are easy to leak or be cracked due to the fixed verification information, and the safety is low. The verification code in the embodiment of the invention is dynamic information, is not easy to leak and crack, and improves the safety.

In some embodiments, to improve security, the length of time that the ADB connection is allowed may be set. As shown in fig. 6, after opening the ADB interface, the method further includes:

step 601: the method comprises the steps that a device to be debugged judges whether the time for starting an ADB interface reaches a preset time length or not; if yes, go to step 602, otherwise, go to step 601.

The preset duration can be set by a manufacturer before delivery or by a merchant after delivery. The preset time period can be set according to requirements, for example, 30 minutes. The judgment of the step 601 may be performed by a timing task, for example, when the preset time duration is 30 minutes, timing is performed from the start time point of the ADB interface by setting a timing task of 30 minutes, and when the timing is finished, the ADB connection needs to be disconnected, that is, the ADB interface is closed.

Step 602: and the device to be debugged closes the ADB interface.

And the second user actively disconnects the ADB or finishes the time effect, and the ADB interface connection operation is finished.

If the connection of the ADB interface is not verified for timeliness, once the connection is verified, the ADB interface can be connected all the time, and the safety cannot be guaranteed. According to the embodiment of the invention, the time length of ADB connection is set, the timing task with the preset time length is started when the ADB connection is started, and the time efficiency of the ADB connection is judged, so that the time efficiency of ADB connection operation at each time can be ensured, and the safety is improved.

During local debugging, the operations of the second user are all executed on the local device to be debugged in the above embodiment. During remote debugging, the operation of the second user in the above embodiment may operate the device to be debugged in a remote connection control manner, and before executing the steps of the above embodiment, the second user needs to execute the operation of remotely connecting and controlling the device to be debugged through the terminal device. During remote debugging, the operation of the second user in the above embodiment may also be performed in a manner of sending an instruction or information to the device to be debugged through a wired network or a wireless network.

In some embodiments, in order to further improve security, for a device to be debugged that supports biometric information identification, the verification information may further include biometric information, the biometric information is bound with the device to be debugged before shipment or before a merchant debugs for the first time, and then the ADB interface may be opened after both the verification code and the biometric information pass verification.

In the step of binding before factory shipment, in addition to the

above step

201 and 209, the method further includes the following biometric information binding step:

step a 1: the device to be debugged judges whether biological characteristic information is bound; if yes, go to step a2, otherwise, end.

The method comprises the steps of displaying a biological characteristic information binding confirmation interface on a display screen of the device to be debugged, receiving confirmation information input by a first user on the binding confirmation interface to judge whether biological characteristic information is bound for an ADB interface management function of the device to be debugged, and subsequently receiving the biological characteristic information input by the user to carry out permission verification on operation of the ADB interface when the ADB interface of the device to be debugged needs to be opened.

Step a 2: the device to be debugged receives first biological characteristic information input by a first user.

The biometric information may be any information that can be used for biometric identification, such as a fingerprint, a palm print, a vein, a human face, an iris, a retina, a voiceprint, and the like. The device to be debugged acquires first biological characteristic information input by a user through a corresponding acquisition device arranged on the device to be debugged, such as a fingerprint acquisition device, a camera and the like.

Step a 3: and the equipment to be debugged binds the first biological characteristic information, stores the third binding information and sends the third binding information to the management server.

And the device to be debugged binds the ADB interface management function with the first biological characteristic information to generate third binding information, locally stores the third binding information and sends the third binding information to the management server. The third binding information is information that the binding is successful, and the third binding information includes an identifier of the device to be debugged, biometric information, a timestamp, and the like.

Step a 4: and the management server receives and stores the binding information.

It can be understood that the binding process of the biometric information may also be combined with the short message verification code described above, for example, the binding of the biometric information is performed after the mobile phone number is successfully bound, after the biometric information input by the first user is received, the device to be debugged sends the short message verification code to the bound mobile phone number, and the user inputs the short message verification code and passes the verification, and then the biometric information can be successfully bound.

In the step of binding the biometric information, the specific implementation manner of the steps that are the same as or similar to the steps in the foregoing embodiment of binding the mobile phone number may refer to the foregoing embodiment of binding the mobile phone number.

In the step of debugging after the factory shipment, in addition to the above-mentioned steps 301-317, the method further includes the following biometric information verification steps:

step b 1: prompting a user to input biological characteristic information by the equipment to be debugged;

step b 2: the device to be debugged receives second biological characteristic information input by a user;

step b 3: the device to be debugged compares the second biological characteristic information with the bound first biological characteristic information;

in this embodiment, the step 307 includes: and if the verification result that the verification is passed is received and the second biological characteristic information is matched with the first biological characteristic information of the ADB interface management function of the bound equipment, starting the ADB interface.

That is, if the second verification code of the short message matches the first verification code and the second biometric information matches the bound first biometric information, the ADB interface is turned on.

On the basis of the short message verification code, the verification process of the biological characteristic information is added, and the safety of ADB opening is further improved.

It is understood that the verification method of the biometric information may also be a separate verification method for opening the ADB interface without adding the verification of the short message verification code. Fig. 7 is a flowchart of another debugging interface management method provided in an embodiment of the present invention, where the method is applied to a device to be debugged. As shown in fig. 7, the method includes:

step 701: receiving an instruction input by a user for starting an ADB interface of an android debug bridge of the equipment;

step 702: acquiring a communication number bound with a debugging interface management function of the equipment according to the instruction;

step 703: controlling to send a first verification code to the acquired communication number;

step 704: receiving a second verification code input by the user;

step 705: and if the second verification code is matched with the first verification code, starting the ADB interface.

Corresponding to the embodiment of the debugging interface management method, the embodiment of the invention also provides a debugging interface management device. The apparatus may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, the apparatus is a logical apparatus, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for running through a processor of the device where the apparatus is located.

Fig. 8 is a schematic structural diagram of a debug interface management apparatus according to an embodiment of the present invention. As shown in fig. 8, the apparatus 300 includes: a first receiving module 301, an obtaining module 302, a first control module 303, a second receiving module 304, and an opening module 305.

The first receiving module 301 is configured to receive an instruction, input by a user, for starting an ADB interface of an android debug bridge of a device;

the obtaining module 302 is configured to obtain, according to the instruction, a communication number bound to a debugging interface management function of the device;

the first control module 303 is configured to control sending of a first verification code to the acquired communication number;

the second receiving module 304 is configured to receive a second verification code input by the user;

the starting module 305 is configured to start the ADB interface if the second verification code matches the first verification code.

In some embodiments, the apparatus 300 further comprises:

In some embodiments, the pre-warning information further includes a timestamp.

In some embodiments, the apparatus 300 further comprises:

In some embodiments, the first control module 303 is further configured to:

the enabling module 305 is further configured to:

In some embodiments, the first control module 303 is further configured to:

generating the first verification code;

the enabling module 305 is further configured to:

In some embodiments, the apparatus 300 further comprises:

In some embodiments, the second control module is further configured to:

the binding module is further to:

In some embodiments, the second control module is further configured to:

generating the third verification code;

the binding module is further to:

In some embodiments, the third passcode is a randomly generated passcode.

In some embodiments, the apparatus 300 further comprises:

In some embodiments, the apparatus further comprises:

the opening module is further configured to:

The implementation process of the functions and actions of the modules in the apparatus 300 is described in detail in the implementation process of the corresponding steps in the method embodiments, and is not described herein again.

The embodiment of the invention provides a nonvolatile computer storage medium, wherein at least one executable instruction is stored in the computer storage medium, and the computer executable instruction can execute the debugging interface management method in any method embodiment.

Fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, where the electronic device is a device to be debugged, and the electronic device may be any device installed with an android operating system, and the device has an ADB interface, such as a Point of sale (POS), a cash register and POS integrated machine, a smart phone, a tablet computer, a portable Digital camera, a media player, a portable game device, a Personal Digital Assistant (PDA), a desktop computer, a notebook computer, and the like. The specific embodiment of the present invention does not limit the specific implementation of the electronic device.

As shown in fig. 9, the electronic device may include: a processor (processor)402, a Communications Interface 404, a memory 406, and a Communications bus 408.

Wherein: the processor 402, communication interface 404, and memory 406 communicate with each other via a communication bus 408. A communication interface 404 for communicating with network elements of other devices, such as clients or other servers. The processor 402 is configured to execute the program 410, and may specifically perform the relevant steps in the embodiment of the debug interface management method described above.

In particular, program 410 may include program code comprising computer operating instructions.

The processor 402 may be a central processing unit CPU, or an application specific Integrated circuit asic, or one or more Integrated circuits configured to implement an embodiment of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.

And a memory 406 for storing a program 410. Memory 406 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of embodiments of the present invention as described herein, and any descriptions of specific languages are provided above to disclose preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that is, the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components according to embodiments of the present invention. Embodiments of the invention may also be implemented as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing embodiments of the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. Embodiments of the invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specified otherwise.

Claims

1. A debug interface management method, comprising:

receiving a second verification code input by the user;

2. The method of claim 1, wherein the method further comprises:

3. The method of claim 2, wherein the early warning information further comprises a timestamp.

4. The method according to any one of claims 1-3, wherein the method further comprises:

5. The method of any of claims 1-4, wherein the first passcode is a randomly generated passcode.

6. The method of any one of claims 1-5,

the controlling sending the first verification code to the acquired communication number includes:

7. The method of any one of claims 1-5,

generating the first verification code;

8. A debug interface management apparatus comprising:

9. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the debugging interface management method of any one of claims 1-7.

10. A computer storage medium having stored therein at least one executable instruction for causing a processor to perform operations corresponding to the debug interface management method of any of claims 1-7.