A login method, system, device and medium of a debugging tool

Abstract

The application provides a login method, system and device of a debugging tool and a medium, relates to the technical field of device debugging, and is used for solving the problem of high leakage risk of the existing debugging tool. The method comprises the following steps: a server determines whether a target username exists in an authorized personnel table; if the server determines that the target username exists in the authorized personnel table, it is determined whether a password associated with the target username is the same as a target password; if it is determined that the password associated with the target username is the same as the target password, the city where a target device is located is determined according to the IP address of the target device, and it is determined whether the city where the target device is located is the same as the city of employment associated with the target username; and if it is determined that the city where the target device is located is the same as the city of employment associated with the target username, a verification success message is sent to the debugging tool. The information of the pre-existing employment personnel is used to avoid the login of the debugging tool by the personnel who have left the employment, and the security is improved.

Description

Technical Field

[0001] The present application relates to the technical field of device debugging, and provides a method, system, device, and medium for logging into a debugging tool. Background Art

[0002] During the installation, maintenance, and troubleshooting of fiber-to-the-room (FTTR) networks, passive optical networks (PONs), optical modems, converged gateways, government and enterprise gateways, and 4 / 5 customer premises equipment (CPE), a company's after-sales personnel can use debugging tools to test and optimize their equipment (such as optical modems). Internal debugging tools are typically standalone versions, making them easily copied and disseminated, especially after a salesperson leaves the company, posing a high risk. Summary of the Invention

[0003] The present application provides a debugging tool login method, system, device and medium, which are used to solve the problem of high leakage risk of debugging tools in the prior art.

[0004] In a first aspect, a method for logging into a debugging tool is provided, comprising:

[0005] The debugging tool responds to the user's login operation in the login box and sends a login request to the server; the login request includes the target user name and target password entered by the user and the IP address of the target device where the debugging tool is located;

[0006] The server determines whether the target user name exists in the authorized personnel table pre-stored in the database; the authorized personnel table includes the user names of all the company's after-sales personnel, the password associated with each user name, and the employment city associated with each user name;

[0007] If the server determines that the target user name exists in the authorized personnel table, determining whether the password associated with the target user name is the same as the target password;

[0008] If the server determines that the password associated with the target user name is the same as the target password, the server determines the city where the target device is located based on the IP address of the target device, and determines whether the city where the target device is located is the same as the employment city associated with the target user name;

[0009] If the server determines that the city where the target device is located is the same as the employment city associated with the target user name, a verification success message is sent to the debugging tool.

[0010] Optionally, if the server determines that the city where the target device is located is the same as the employment city associated with the target user name, after sending a verification success message to the debugging tool, the method further includes:

[0011] The debugging tool receives the verification success message, loads the main interface including the core function module, starts timing, and pops up the login box again after a preset time.

[0012] Optionally, the database further pre-stores an authorized device table, the authorized device table including identification information of all terminal devices authorized by the company; before the debugging tool responds to the user's login operation in the login box and sends a login request to the server, the method includes:

[0013] The debugging tool sends the identification information of the target device to the server;

[0014] If the server determines that the identification information of the target device exists in the authorized device table, sending a device authentication success message to the debugging tool;

[0015] The debugging tool receives the device authentication success message and pops up a login box.

[0016] Optionally, before the debugging tool sends the identification information of the target device to the server, the method includes:

[0017] After being started, the debugging tool connects to the server via a uniform resource identifier and receives the latest version information returned by the server;

[0018] The debugging tool determines whether an upgrade is required based on the version switch identifier in the latest version information; the version switch identifier is used to indicate whether the debugging tool must be upgraded before use;

[0019] If the debugging tool determines that an upgrade is required, the version upgrade is performed according to the download path in the latest version information.

[0020] Optionally, after the debugging tool determines whether an upgrade is required based on the version switch identifier in the latest version information, the method includes:

[0021] If the debugging tool determines that no upgrade is required, the download path is displayed;

[0022] The debugging tool saves the download path in the target device in response to a user's copy operation on the download path;

[0023] In response to a manual upgrade operation by a user, the debugging tool reads the download path from the target device for upgrade.

[0024] Optionally, after sending the verification success message to the debugging tool, if the server determines that the city where the target device is located is the same as the city where the target user is employed, the method comprises:

[0025] The server counts the login times of the target user identified by the target user name within a preset period, and notifies a manager if the login times are greater than a preset number.

[0026] Optionally, the debugging tool sends a login request to the server in response to a login operation of a user in a login box, and the login request comprises:

[0027] The debugging tool acquires the target user name and the target password input by the user in response to a login operation of the user in the login box, and verifies whether the target user name and the target password conform to a preset format.

[0028] If the debugging tool determines that the target user name and the target password conform to the preset format, the debugging tool sends a login request to the server.

[0029] In a second aspect, a login system of a debugging tool is provided, comprising a server and a plurality of terminal devices, and each terminal device is installed with a debugging tool; wherein:

[0030] The debugging tool is configured to send a login request to the server in response to a login operation of a user in a login box, and the login request comprises a target user name and a target password input by the user and an IP address of a target device where the debugging tool is located.

[0031] The server is configured to determine whether the target user name exists in an authorization personnel table pre-stored in a database, and the authorization personnel table comprises user names of all in-service personnel of a company, passwords associated with each user name, and a city where each user name is employed.

[0032] The server is further configured to determine whether the password associated with the target user name is the same as the target password if it is determined that the target user name exists in the authorization personnel table.

[0033] The server is further configured to determine whether the city where the target device is located is the same as the city where the target user name is employed if it is determined that the password associated with the target user name is the same as the target password.

[0034] The server is further configured to send a verification success message to the debugging tool if it is determined that the city where the target device is located is the same as the city where the target user name is employed.

[0035] In a third aspect, the present application provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the login method of the debugging tool.

[0036] In a fourth aspect, the present application provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and a processor executes the computer program to implement the login method of the debugging tool.

[0037] Compared with the prior art, the present application has the following beneficial effects:

[0038] The present application provides a login method of a debugging tool, which comprises: the debugging tool sends a login request to a server in response to a login operation of a user in a login box; the login request comprises a target username and a target password input by the user, and an IP address of a target device where the debugging tool is located; the server determines whether the target username exists in an authorized personnel table pre-stored in a database; the authorized personnel table comprises usernames of all in-service after-sales personnel of a company, passwords associated with each username, and a city of entry associated with each username; if the server determines that the target username exists in the authorized personnel table, it is determined whether the password associated with the target username is the same as the target password; if the server determines that the password associated with the target username is the same as the target password, it is determined whether the city where the target device is located is the same as the city of entry associated with the target username according to the IP address of the target device; and if the server determines that the city where the target device is located is the same as the city of entry associated with the target username, a verification success message is sent to the debugging tool.

[0039] In the present application, a database is established by introducing a server, and information of all in-service after-sales personnel is centrally managed and monitored, so as to ensure transparency and traceability of use of the debugging tool, and the server in the background and the debugging tool in the front end realize interaction, the server verifies the username and the password every time the user logs in, so as to ensure that only authorized in-service after-sales personnel can log in and use the debugging tool, to avoid off-duty personnel from continuing to use the tool, and to improve the security of the tool. The server also verifies the city information of the target device where the tool is located, so as to ensure that the city where the target device is located is the same as the city of entry associated with the username, to avoid someone from logging in the debugging tool in a different place, to effectively reduce the risk of stolen account use, and to further improve the security of the tool. BRIEF DESCRIPTION OF DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the following will briefly introduce the drawings needed to be used in the embodiments or the related art description. Obviously, the drawings described in the following are only part of the present application, and the drawings provided by the present application can be obtained by the drawings provided by the present application without creative labor.

[0041] Figure 1 The application scenario provided by the present application is shown in the figure.

[0042] Figure 2 The flow chart of the login method of the debugging tool provided by the present application is shown in the figure.

[0043] Figure 3 The schematic diagram of the login box provided by the present application is shown in the figure.

[0044] Figure 4 The schematic diagram of the main interface provided by the present application is shown in the figure.

[0045] Figure 5 The interface schematic diagram of the pop-up upgrade version download address provided by the present application is shown in the figure.

[0046] Figure 6 The interface schematic diagram of the login box provided by the present application is shown in the figure.

[0047] Figure 7 The schematic diagram of the web page management interface of the server provided by the present application is shown in the figure. Figure 1

[0048] Figure 8 The schematic diagram of the web page management interface of the server provided by the present application is shown in the figure. Figure 2

[0049] Figure 9 The processing flow schematic diagram of the debugging tool provided by the present application is shown in the figure. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solutions and advantages of the present application more clear, the technical solutions in the embodiments of the present application will be described clearly and completely in the following with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by the ordinary skilled in the art without creative labor are within the scope of the present application. In the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. And, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in different order from here. ​​

[0051] The existing debugging tool has the following problems:

[0052] 1. Security problem of single machine version of tool software: The debugging tool in the company is originally a single machine version, which is easy to copy and spread, especially after the personnel leave, there is a high security risk.

[0053] 2. Lack of centralized management and monitoring: The single machine version tool cannot be centrally managed, cannot monitor the use of the tool, and cannot timely discover and handle abnormal login behavior.

[0054] 3. Difficulty in version control: The single machine version tool is difficult to update and manage uniformly, resulting in different versions of the tool used by different after-sales personnel, affecting work efficiency and security.

[0055] 4. Permission management of personnel leaving: The tool use permission of personnel leaving cannot be revoked in time, which exists potential security risks.

[0056] In view of this, the embodiment of the present application provides a login method of a debugging tool, which is applied to a login system of the debugging tool. Please refer to Figure 1 , which is an application scenario provided by the embodiment of the present application, or can be understood as a structural schematic diagram of the login system of the debugging tool. The login system of the debugging tool includes a server and a plurality of terminal devices.

[0057] Among them, the terminal device is, for example, a mobile terminal, a fixed terminal or a portable terminal, such as a mobile phone, a station, a unit, a device, a multimedia computer, a multimedia tablet, an Internet node, a communicator, a desktop computer, a notebook computer, a tablet computer, a personal communication system (PCS) device, a positioning device, or any combination thereof, including accessories and peripherals of these devices or any combination thereof.

[0058] The server can be a standalone physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and basic cloud computing services such as big data and artificial intelligence platforms, but is not limited thereto.

[0059] It should be noted that Figure 1 The plurality of terminal devices include two terminal devices as an example, and the number of terminal devices is not limited in practice, and each terminal device is installed with a debugging tool. The debugging tool is a TELNET login and instruction set tool, also known as a verification code calculation tool software (referred to as TWW software), which has the functions of decrypting the telnet login password of the company and sending test instructions. For example, optical modem debugging tool, PON debugging tool, etc.

[0060] Based on Figure 1 The application scenarios shown below will be introduced. Figure 2 The login method of a debugging tool is introduced.

[0061] S201, the debugging tool sends a login request to the server in response to the user's login operation in the login box.

[0062] Specifically, when the user wants to use the debugging tool installed on the target device, the user can first input the target username and target password in the login box after starting the debugging tool, and then click the login button. The debugging tool can automatically obtain the IP address of the target device, and then pack the target username and target password input by the user, the IP address of the target device into a login request, and send it to the server.

[0063] Please refer to Figure 3 The schematic diagram of the login box provided by the embodiment of the present application is shown, wherein the user name is the username, and the user password is the password.

[0064] In one possible embodiment, S201 specifically includes the following steps:

[0065] The debugging tool obtains the target username and target password input by the user in response to the user's login operation in the login box, and verifies whether the target username and target password conform to the preset format; if the debugging tool determines that the target username and target password conform to the preset format, the debugging tool sends a login request to the server.

[0066] In the specific implementation process, the debugging tool can verify whether the target username and target password conform to the preset format, for example, cannot be empty, greater than a preset length, contain special characters, if the verification is passed, the login request is sent to the server again. If the verification fails, a prompt information is popped up. For example, "the username cannot be empty", "the password length cannot be less than 8 bits", "the password must contain at least one special character".

[0067] In the embodiment of the present application, the format verification is performed in the front end by the debugging tool, which can quickly improve the user experience, ensure that the data submitted to the server conforms to the basic format requirements, prevent the user from submitting format error data to the server, reduce invalid login requests, thereby reducing the burden of the server and improving the performance.

[0068] S202, the server judges whether the target username exists in the authorized personnel table pre-stored in the database.

[0069] Specifically, the server's database pre-stores an authorized personnel table, which includes the user names of all the company's after-sales personnel, the password associated with each user name, and the city of employment associated with each user name. If the server receives a notification of employment from any person, it reads the person's position and city of employment from the notification. If the person's position is after-sales, it generates the person's user name and password, and saves the person's information in the authorized personnel table. The information includes user name, password, position, and city of employment. If the server receives a notice of resignation from any person, it checks whether the person's user name exists in the authorized personnel table. If so, it deletes the person's information from the authorized personnel table.

[0070] After receiving the login request, the server first parses it to obtain the target username, password, and IP address of the target device. It then searches the authorized personnel table to determine whether the target username exists and whether the target user identified by the target username is an in-service after-sales representative of the company.

[0071] S203. If the server determines that the target user name exists in the authorized personnel table, it determines whether the password associated with the target user name is the same as the target password;

[0072] In a possible embodiment, if the server determines that the target user name exists in the authorized personnel table, it performs a hash operation on the target password to obtain a hash value; the server determines whether the password associated with the target user name is the same as the hash value.

[0073] In the specific implementation process, after the server determines that the target username exists in the authorized personnel table, it reads the password associated with the target username from the authorized personnel table, performs a hash operation on the target password, obtains a hash value, and compares this hash value with the password associated with the target username. If they are the same, it means that the password associated with the target username is the same as the target password entered by the user, and password verification succeeds. If they are different, it means that the password associated with the target username is different from the target password entered by the user, and password verification fails.

[0074] In the embodiment of the present application, the server does not directly store the user's password, but stores the password hash value processed by the hash algorithm. Since the hash algorithm is irreversible, that is, the password cannot be directly inferred from the hash value, even if the database is leaked, the attacker only obtains the hash value and cannot restore it to the original password. The password itself will not be leaked, thereby increasing the security of the system.

[0075] S204. If the server determines that the password associated with the target user name is the same as the target password, the server determines the city where the target device is located based on the IP address of the target device, and determines whether the city where the target device is located is the same as the employment city associated with the target user name.

[0076] Specifically, after the server determines that the password associated with the target username is the same as the target password, the server can first read the entry city associated with the target username from the authorized personnel table, and then use an IP geolocation query service, such as an IPgeolocation API, to obtain city information of the IP address. Finally, it is determined whether the city where the target device is located is the same as the entry city associated with the target username.

[0077] S205, if the server determines that the city where the target device is located is the same as the entry city associated with the target username, the server sends a verification success message to the debugging tool.

[0078] Specifically, after the server determines that the city where the target device is located is the same as the entry city associated with the target username, the server sends a verification success message to the debugging tool. The verification success message is used to indicate that the login request has passed the verification. If the debugging tool receives the verification success message, the debugging tool can load a main interface including a core function module, and the user can operate in the main interface, so as to use the debugging tool to perform debugging operations.

[0079] Please refer to Figure 4 The schematic diagram of the main interface provided by the embodiment of the present application is shown in FIG. 2. As shown in FIG. 2, the address of the server is 192.168.1.1. The user can input a test command in the blank box of “Send Command” and click the “Send Button” on the right side, so as to send the test command to the server.

[0080] In a possible embodiment, before S201 is performed, the method can further include the following steps:

[0081] The debugging tool sends identification information of the target device to the server. If the server determines that the identification information of the target device exists in the authorized device table, the server sends a device authentication success message to the debugging tool. The debugging tool receives the device authentication success message and pops up a login box.

[0082] In the implementation process, the database of the server further pre-stores an authorized device table. The authorized device table includes identification information of all terminal devices authorized by the company. The identification information is used to uniquely identify each terminal device, such as a media access control address (MAC address) and a central processing unit identifier (CPU ID). The MAC address is used to uniquely identify a network interface card (NIC), which is usually embedded in the network card of the device by the hardware manufacturer during the production of the device. The CPU ID is a characteristic value used to uniquely identify the CPU.

[0083] After launching the debugging tool for the target device, it first obtains the target device's identification information. Upon receiving the device identification information from the debugging tool, the server compares it with the authorized device table pre-stored on the server. If the target device's identification information is in the authorized device table, the server sends a device authentication success message to the debugging tool, indicating that the target device has been authorized. If the target device's identification information is not in the authorized device table, the server sends a device authentication failure message, indicating that the target device is unauthorized.

[0084] In the embodiments of the present application, device identification information is unique and difficult to forge. Verifying the device identification before a user logs in effectively prevents unauthorized devices from performing any operations. Only verified devices can further authenticate the user, reducing potential security threats. Even if an attacker knows the user's username and password, if the device is unauthorized, they still cannot access the system. This strengthens the system's security and prevents untrusted devices from logging in.

[0085] In a possible embodiment, before the debugging tool sends the identification information of the target device to the server, the method may further include the following steps:

[0086] After startup, the debugging tool connects to the server via a uniform resource locator and receives the latest version information returned by the server; the debugging tool determines whether an upgrade is required based on the version switch identifier in the latest version information; the version switch identifier is used to indicate whether an upgrade is required before the debugging tool can be used; if the debugging tool determines that an upgrade is required, the version upgrade is performed based on the download path in the latest version information.

[0087] In the specific implementation process, the Uniform Resource Locator (URL) is the address used to locate and access resources on the Internet. After the debugging tool is started, it connects to the server through the URL, and the server will return the latest version information of the debugging tool. The latest version information includes the version number, version switch identifier, version description and download path of the latest version. The version switch identifier is 1, which means that the debugging tool can be used regardless of whether it is upgraded or not. Isopen is 0, which means that the debugging tool must be upgraded before it can be used. After the debugging tool receives the latest version information, if the version switch identifier is 0, it is determined that an upgrade is required, and the version upgrade and forced restart are performed according to the download path in the latest version information.

[0088] For example, the latest version information returned by the server is as follows:

[0089] {'vv':{'twwversion':'v-1.0','isopen':1},'new':{'twwversion':'v-1.0','isopen':1,'expl ain':'Version Description','add':' / static / wwteam-v1.0.zip'}"}

[0090] Among them, twwversion is the version number, isopen is the version switch identifier, explain is the version description, and add is the download path.

[0091] In the embodiments of the present application, the server side can use unified version control and download path management to facilitate management personnel to monitor and control the versions used by all after-sales personnel. Through server management, new versions can be released quickly to fix bugs or release new features, without users having to manually update one by one. By only upgrading when necessary (when an upgrade is required to use debugging tools) rather than frequently forcing upgrades, unnecessary downloads and updates are reduced, saving network bandwidth and storage space.

[0092] In a possible embodiment, after the debugging tool determines whether an upgrade is required based on the version switch identifier in the latest version information, the method may further include the following steps:

[0093] If the debugging tool determines that no upgrade is required, the download path is displayed; in response to the user's copy operation on the download path, the debugging tool saves the download path in the target device; in response to the user's manual upgrade operation, the debugging tool reads the download path from the target device for upgrade.

[0094] In the specific implementation process, if the version switch flag is 1, it is determined that no upgrade is required, and the download path pops up, such as Figure 5 As shown in the figure, the download address for the upgraded version (i.e., the download path for the latest version) is "http: / / 113.125.60.254.8010 / static / wwteam-v1.3." Clicking the "Copy" button will save the download path on the target device. Users can then read the download path from the target device at their leisure to manually upgrade the debugging tool.

[0095] In the embodiments of the present application, if it is confirmed that an upgrade is not required and the debugging tool can be used, the download path is displayed instead of the immediate upgrade and restart, which helps to avoid unnecessary network traffic and resource waste. The user can decide whether to download the update based on the specific situation, reducing the system burden. Some users may work in an environment with low network bandwidth or do not want to download directly online in certain situations. By providing a download path and supporting manual copying, users can choose to download and upgrade in a more suitable network environment, avoiding upgrade failures caused by network problems.

[0096] In one possible embodiment, if the server determines that the target user name does not exist in the authorized personnel table, or if the server determines that the password associated with the target user name is different from the target password, or if the server determines that the city where the target device is located is different from the employment city associated with the target user name, a verification failure message is sent to the debugging tool. If the debugging tool receives the verification failure message, a prompt message indicating the login failure will pop up, such as "Username does not exist," "Incorrect password," "Unusual login location," etc.

[0097] In a possible embodiment, after executing S205, the method may further include:

[0098] The debugging tool receives the verification success message, loads the main interface including the core function module, starts timing, and pops up the login box again after the preset time.

[0099] In the specific implementation process, each time a user successfully logs into the debugging tool, the debugging tool will start timing, and after the preset time (for example, 1 hour), the login box will pop up again for verification. Figure 6 , which is a schematic diagram of a login dialog box that pops up again in an embodiment of the present application. After the user re-enters the target username in the blank box corresponding to the username and the target password in the blank box corresponding to the password, the system will re-execute S201-S205. If the user does not enter the username and password within a preset time period (e.g., 5 minutes), the debugging tool will automatically exit.

[0100] In the embodiment of the present application, the debugging tool will re-authenticate one hour after each login. If the authentication fails, the tool software will be automatically logged out. Even if the user's initial login is verified, re-authentication after one hour ensures that the account is not controlled by an unauthorized third party during long-term use. It also avoids the risk of users leaving the device after opening the tool software and forgetting to close it. Repeated authentication helps ensure that the user is still the same person during operation, especially during long-term work or interaction.

[0101] In a possible embodiment, after executing S205, the method may further include:

[0102] The server counts the number of logins of the target user identified by the target user name within a preset period, and notifies the administrator if the number of logins is greater than the preset number.

[0103] During the specific implementation process, after the server sends a verification success message to the debugging tool, it can record the login information of this time in the log. The login information includes the target user name, login time, login location (i.e., the city where the target device is located), and login device information (i.e., the identification information of the target device). If the target user name is recorded more than a preset number of times (e.g., 10 times) within a preset period (e.g., one day), it indicates that the user login is abnormal, and the administrator is notified by email. The administrator can also log in to the backend server to view the log information for review and judgment.

[0104] In the embodiment of the present application, when a user's login times increase dramatically, it may indicate that the account has been illegally accessed or abused. Counting the user's login times and notifying the administrator when the number exceeds a preset number can help the administrator to conduct timely intervention inspections and improve the security of the system.

[0105] It should be noted that the server in the embodiments of this application is deployed with a backend server program. For example, using the TWW tool software as the debugging tool, the backend web management interface includes three modules: TWW login records, TWW account information, and version number management. The TWW login record module is used to store the login information of all users who have logged into TWW. The TWW account information module is used to store the usernames and passwords of all active after-sales personnel. The version number management module is used to store all uploaded versions of the TWW tool software.

[0106] Please refer to Figure 7 , which is a schematic diagram of the web management interface of the server provided in the embodiment of the present application Figure 1 ,It can be seen that the user has uploaded a total of 5 versions, namely v-0.0, v-1.0, v-1.1, v-1.2, and v-1.3.

[0107] Please refer to Figure 8 , which is a schematic diagram of the web management interface of the server provided in the embodiment of the present application Figure 2 As you can see, users can click "Version Number Management" to add the latest version information. The version number is "v-1.1", and the version switch is marked as "1", indicating that the debugging tool can be used regardless of whether the upgrade is made. The version description is "Added Unicom 4.0", and the download path is "static / wwteam-v1.0.zip".

[0108] Please refer to Figure 9 , which is a schematic diagram of the processing flow of the debugging tool provided in an embodiment of the present application.

[0109] S901, start the debugging tool.

[0110] S902, access the server to obtain the latest version information.

[0111] S903, determine whether an upgrade is needed.

[0112] If the version switch in the latest version information is 0, it is determined that an upgrade is needed, and S905 is continued. If the version switch in the latest version information is 1, it is determined that an upgrade is not needed, and S904 is continued.

[0113] S904, pop up an upgrade website, save the current version, and manually upgrade next time.

[0114] The debugging tool pops up the download address of the latest version, as shown in FIG. 5, the user clicks the "copy" button, and the current version is saved, and the user manually upgrades next time. Figure 5

[0115] S905, automatically upgrade.

[0116] The debugging tool automatically downloads the latest version according to the download path in the latest version information, upgrades, and forcibly restarts to complete the upgrade.

[0117] S906, enter the login interface.

[0118] The debugging tool enters the login interface, and a login box is popped up, as shown in FIG. 6. Figure 3

[0119] S907, send a login request for verification.

[0120] After the user inputs the username and password in the login interface, the debugging tool sends a login request to the server.

[0121] S908, determine whether the verification is successful.

[0122] If the debugging tool receives a verification failure message, it is determined that the verification fails, and S909 is continued. If the debugging tool receives a verification success message, it is determined that the verification is successful, and S910 is continued.

[0123] S909, pop up a prompt information of login failure.

[0124] S910, enter the main interface.

[0125] S911, start timing.

[0126] S912, determine whether 1 hour has been exceeded.

[0127] ​​If it has exceeded 1 hour, S906 is executed again to enter the login interface. If it has not exceeded 1 hour, S910 is executed again to enter the main interface.

[0128] In summary, the present invention also provides a method for logging into a debugging tool, which has the following beneficial effects:

[0129] (1) Centralized management and monitoring: By introducing a server to deploy backend service programs and establishing a database, all login and operation records of after-sales personnel are centrally managed and monitored, ensuring the transparency and traceability of tool use.

[0130] (2) Enhanced security: The backend service program interacts with the front-end tool software to ensure that only authorized users can log in and use the tool. Each time a user logs in, the system performs a strict authentication process, including verifying the user's username and password as well as the device's identification information, to ensure that the terminal device used to use the tool is company property.

[0131] (3) Real-time permission management: The permissions of departing employees will be removed immediately, ensuring that they cannot continue to use the tool, eliminating potential security risks.

[0132] (4) Dynamic authentication mechanism: Within 1 hour after each login (the time can be set), the system will perform repeated identity authentication. If the authentication fails, the tool software will be automatically exited. This mechanism effectively solves the security risks caused by not closing the tool software after opening it.

[0133] (5) Version control and update: Through the background service program, the version upgrade of the tool software can be centrally controlled to ensure that all after-sales personnel use the same tool version, thereby improving work efficiency and safety.

[0134] (6) User behavior audit: The login record database records the time and operation records of each login in detail, which is convenient for auditing and tracking, and helps to detect and handle abnormal behavior in a timely manner.

[0135] Based on the same invention concept, please continue to refer to Figure 1 , the embodiment of the present application further provides a debugging tool login system, including a server and multiple terminal devices, each terminal device is installed with a debugging tool; wherein:

[0136] The debugging tool is configured to send a login request to the server in response to a user's login operation in the login box; the login request includes a target user name and target password entered by the user, and the IP address of the target device where the debugging tool is located;

[0137] The server is used to determine whether the target username exists in the authorized personnel table stored in the database. The authorized personnel table includes the usernames of all the company's after-sales personnel, the password associated with each username, and the city where each username was employed.

[0138] The server is further configured to determine whether the password associated with the target user name is the same as the target password if it is determined that the target user name exists in the authorized personnel table;

[0139] The server is further configured to, if it is determined that the password associated with the target user name is the same as the target password, determine the city of the target device based on the IP address of the target device, and determine whether the city of the target device is the same as the employment city associated with the target user name;

[0140] The server is further configured to send a verification success message to the debugging tool if it is determined that the city where the target device is located is the same as the employment city associated with the target username.

[0141] It should be noted that each module in the login system of the debugging tool in this embodiment corresponds one-to-one to each step in the login method of the debugging tool in the aforementioned embodiment. Therefore, the specific implementation of this embodiment can refer to the implementation of the login method of the aforementioned debugging tool, and will not be repeated here.

[0142] In addition, in one embodiment, the present application also provides a computer device, which includes a processor, a memory, and a computer program stored in the memory, and the computer program implements the aforementioned debugging tool login method when executed by the processor.

[0143] In addition, in one embodiment, the present application further provides a computer storage medium, on which a computer program is stored. When the computer program is executed by a processor, the computer program implements the aforementioned login method of the debugging tool.

[0144] In some embodiments, the computer-readable storage medium may be a memory device such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface mount memory, optical disk, or CD-ROM; or various devices including one or any combination of the above memories. The computer may be various computing devices including smart terminals and servers.

[0145] In some embodiments, executable instructions may be in the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0146] As an example, executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file that stores other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinating files (e.g., files storing one or more modules, subroutines, or code portions).

[0147] By way of example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

[0148] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.

[0149] The serial numbers of the above embodiments of the present application are for description only and do not indicate the advantages or disadvantages of the embodiments.

[0150] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, or of course by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory / random access memory, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a multimedia terminal device to execute the methods described in each embodiment of the present application.

[0151] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for logging into a debugging tool, characterized in that: The method comprises: The debugging tool responds to the user's login operation in the login box and sends a login request to the server; the login request includes the target user name and target password entered by the user and the IP address of the target device where the debugging tool is located; The server determines whether the target user name exists in the authorized personnel table pre-stored in the database; the authorized personnel table includes the user names of all the company's after-sales personnel, the password associated with each user name, and the employment city associated with each user name; If the server determines that the target user name exists in the authorized personnel table, determining whether the password associated with the target user name is the same as the target password; If the server determines that the password associated with the target user name is the same as the target password, the server determines the city where the target device is located based on the IP address of the target device, and determines whether the city where the target device is located is the same as the employment city associated with the target user name; If the server determines that the city where the target device is located is the same as the employment city associated with the target username, sending a verification success message to the debugging tool; The database also pre-stores an authorized device table, which includes identification information of all terminal devices authorized by the company; before the debugging tool responds to the user's login operation in the login box and sends a login request to the server, the method includes: The debugging tool sends the identification information of the target device to the server; If the server determines that the identification information of the target device exists in the authorized device table, sending a device authentication success message to the debugging tool; The debugging tool receives the device authentication success message and pops up a login box; Before the debugging tool sends the identification information of the target device to the server, the method includes: After being started, the debugging tool connects to the server via a uniform resource identifier and receives the latest version information returned by the server; The debugging tool determines whether an upgrade is required based on the version switch identifier in the latest version information; the version switch identifier is used to indicate whether the debugging tool must be upgraded before use; If the debugging tool determines that an upgrade is required, the version upgrade is performed according to the download path in the latest version information.

2. The method for logging into a debugging tool according to claim 1, wherein: If the server determines that the city where the target device is located is the same as the employment city associated with the target username, then after sending a verification success message to the debugging tool, the method further includes: The debugging tool receives the verification success message, loads the main interface including the core function module, starts timing, and pops up the login box again after a preset time.

3. The method for logging into a debugging tool according to claim 1, wherein: After the debugging tool determines whether an upgrade is required based on the version switch identifier in the latest version information, the method includes: If the debugging tool determines that no upgrade is required, the download path is displayed; The debugging tool saves the download path in the target device in response to a user's copy operation on the download path; In response to a manual upgrade operation by a user, the debugging tool reads the download path from the target device for upgrade.

4. The method for logging into a debugging tool according to claim 1, wherein: If the server determines that the city where the target device is located is the same as the employment city associated with the target username, then after sending a verification success message to the debugging tool, the method includes: The server counts the number of logins of the target user identified by the target user name within a preset period, and notifies the administrator if the number of logins is greater than a preset number.

5. The method for logging into a debugging tool according to claim 1, wherein: The debugging tool sends a login request to the server in response to the user's login operation in the login box, including: The debugging tool obtains a target user name and a target password input by the user in response to a login operation in the login box, and verifies whether the target user name and the target password conform to a preset format; If the debugging tool determines that the target user name and the target password conform to a preset format, a login request is sent to the server.

6. A debugging tool login system, characterized in that: For implementing the method according to any one of claims 1 to 5, the system comprises a server and a plurality of terminal devices, each terminal device being installed with a debugging tool; wherein: The debugging tool is used to send a login request to the server in response to the user's login operation in the login box; the login request includes the target user name and target password entered by the user, and the IP address of the target device where the debugging tool is located; The server is configured to determine whether the target user name exists in a table of authorized personnel pre-stored in a database; the table of authorized personnel includes the user names of all the company's after-sales personnel, the password associated with each user name, and the employment city associated with each user name; The server is further configured to, if it is determined that the target user name exists in the authorized personnel table, determine whether the password associated with the target user name is the same as the target password; The server is further configured to, if it is determined that the password associated with the target user name is the same as the target password, determine the city where the target device is located based on the IP address of the target device, and determine whether the city where the target device is located is the same as the employment city associated with the target user name; The server is further configured to send a verification success message to the debugging tool if it is determined that the city where the target device is located is the same as the employment city associated with the target user name.

7. A computer device, characterized in that: The computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the login method of the debugging tool according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the processor executes the computer program to implement the login method of the debugging tool according to any one of claims 1 to 5.

Images