Login method, system and equipment of debugging tool and medium

Abstract

The invention provides a login method and system of a debugging tool, equipment and a medium, relates to the technical field of equipment debugging, and is used for solving the problem that the leakage risk of an existing debugging tool is relatively high. The method comprises the steps that a server judges whether a target user name exists in an authorized personnel table or not; if the server determines that the target user name exists in the authorized personnel table, judging whether a password associated with the target user name is the same as the target password or not; if it is determined that the password associated with the target user name is the same as the target password, determining a city where the target device is located according to the IP address of the target device, and judging whether the city where the target device is located is the same as an entry city associated with the target user name; and if it is determined that the city where the target device is located is the same as the entry city associated with the target user name, sending a verification success message to the debugging tool. Through the pre-stored information of the after-sales personnel, the demission personnel are prevented from logging in the debugging tool, and the safety is improved.

Description

Technical Field

[0001] This application relates to the technical field of equipment debugging, and provides a login method, system, device and medium for a debugging tool. Background Art

[0002] During the installation, maintenance and troubleshooting of related equipment such as Fiber to the Room (FTTR) network, Passive Optical Network (PON), optical modem, fusion gateway, enterprise-government gateway, 4 / 5 Customer Premises Equipment (CPE), etc., the after-sales personnel of the company can use the debugging tool to test and optimize their equipment (such as an optical modem). The debugging tools used within the company are usually stand-alone versions and are easily copied and spread. Especially after the after-sales personnel leave the company, there is a relatively high risk. Summary of the Invention

[0003] This application provides a login method, system, device and medium for a debugging tool, which is used to solve the problem of relatively high leakage risk of the debugging tool in the prior art.

[0004] In a first aspect, a login method for a debugging tool is provided, including:

[0005] The debugging tool sends a login request to the server in response to a login operation of a user in a login box; the login request includes a target user name and a target password input by the user, and an IP address of the target device where the debugging tool is located;

[0006] The server determines whether the target user name exists in an authorized personnel table pre-stored in a database; the authorized personnel table includes the user names of all on-the-job after-sales personnel in the company, the passwords associated with each user name, and the cities of employment associated with each user name;

[0007] 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;

[0008] If the server determines that the password associated with the target user name is the same as the target password, it determines the city where the target device is located according to the IP address of the target device, and determines whether the city where the target device is located is the same as the city of employment 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 city of employment associated with the target user name, it sends a verification success message to the debugging tool.

[0010] Optionally, after the server determines that the city where the target device is located is the same as the onboarding city associated with the target username and sends 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 after a preset duration, pops up the login box again.

[0012] Optionally, the database also pre-stores an authorized device table, and the authorized device table includes the identification information of all terminal devices authorized by the company; before the debugging tool sends a login request to the server in response to a user's login operation in the login box, 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, it sends a device authentication success message to the debugging tool;

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

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

[0017] After the debugging tool starts, it connects to the server through 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 it can be used;

[0019] If the debugging tool determines that an upgrade is required, it performs a version upgrade 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 an upgrade is not required, it displays the download path;

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

[0023] The debugging tool reads the download path from the target device for upgrade in response to the user's manual upgrade operation.

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

[0025] The server counts the number of logins of the target user identified by the target user name within a preset period. If the number of logins is greater than a preset number, the administrator is notified.

[0026] Optionally, the debugging tool sends a login request to the server in response to a user's login operation in the login box, including:

[0027] The debugging tool, in response to a user's login operation in the login box, obtains the target user name and target password entered by the user, 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, a login request is sent to the server.

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

[0030] 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 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;

[0031] The server is configured to determine whether the target user name exists in the pre-stored authorized personnel table in the database; the authorized personnel table includes the user names of all on-the-job after-sales personnel in the company, the password associated with each user name, and the city where each user name is associated with the employment;

[0032] 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;

[0033] 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 according to the IP address of the target device, and determine whether the city where the target device is located is the same as the city where the target user name is associated with the employment;

[0034] The server is further configured to, 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 associated with the employment, send a verification success message to the debugging tool.

[0035] In a third aspect, the present application provides a computer device, which includes a memory and a processor. A computer program is stored in the memory, and the processor executes the computer program to implement the login method of the debugging tool described in the first aspect.

[0036] In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, and a processor executes the computer program to implement the login method of the debugging tool described in the first aspect.

[0037] Compared with the prior art, the beneficial effects of the present application are as follows:

[0038] The present application provides a login method for a debugging tool. The method includes: the debugging tool sends a login request to the server in response to a user's login operation in the login box; the login request includes the target username 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 username exists in the pre-stored authorized personnel table in the database; the authorized personnel table includes the usernames of all on-the-job after-sales personnel in the company, the password associated with each username, and the city of employment associated with each username; if the server determines that the target username exists in the authorized personnel table, it determines 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 determines the city where the target device is located according to the IP address of the target device, and determines whether the city where the target device is located is the same as the city of employment associated with the target username; if the server determines that the city where the target device is located is the same as the city of employment associated with the target username, it sends a verification success message to the debugging tool.

[0039] In the present application, by introducing a server to establish a database, the information of all on-the-job after-sales personnel is centrally managed and monitored, ensuring the transparency and traceability of the use of the debugging tool. The server in the background interacts with the debugging tool in the front end. Each time a user logs in, the server verifies the username and password, ensuring that only authorized on-the-job after-sales personnel can log in and use the debugging tool, preventing former employees from continuing to use the tool and improving the security of the tool. The server also verifies the city information of the target device where the tool is located to ensure that the city where the target device is located is the same as the city of employment associated with the username, which can prevent someone from logging in to the debugging tool remotely and effectively reduce the risk of account theft, further improving the security of the tool. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] To more clearly illustrate the technical solutions in the embodiments of the present application or in the related art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the related art. Obviously, the accompanying drawings in the following description are only the embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can also be obtained based on the provided drawings.

[0041] Figure 1 Schematic diagram of the application scenario provided by the embodiment of the present application;

[0042] Figure 2 Schematic flow chart of the login method of the debugging tool provided by the embodiment of the present application;

[0043] Figure 3 Schematic diagram of the login box provided by the embodiment of the present application;

[0044] Figure 4 Schematic diagram of the main interface provided by the embodiment of the present application;

[0045] Figure 5 Schematic diagram of the interface for popping up the download address of the upgraded version provided by the embodiment of the present application;

[0046] Figure 6 Schematic diagram of the interface for popping up the login box again provided by the embodiment of the present application;

[0047] Figure 7 Schematic diagram of the web management interface of the server provided by the embodiment of the present application Figure 1 ;

[0048] Figure 8 Schematic diagram of the web management interface of the server provided by the embodiment of the present application Figure 2 ;

[0049] Figure 9 Schematic flow chart of the processing of the debugging tool provided by the embodiment of the present application. Detailed implementation manners

[0050] To make the objectives, technical solutions and advantages of the present application more clearly understood, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of them. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application. Without conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily with each other. And although the logical order is shown in the flow chart, in some cases, the steps shown or described can be executed in a different order than here.

[0051] The existing debugging tools have the following problems:

[0052] 1. Security issues of the stand-alone version of the tool software: The original debugging tool within the company was a stand-alone version, which was easily copied and spread. Especially after an employee left the company, there was a relatively high security risk.

[0053] 2. Lack of centralized management and monitoring: The stand-alone version tools cannot be centrally managed, the usage of the tools cannot be monitored, and abnormal login behaviors cannot be detected and processed in a timely manner.

[0054] 3. Difficulty in version control: It is difficult to uniformly update and manage the stand-alone version tools, resulting in different versions of tools used by different after-sales personnel, which affects work efficiency and security.

[0055] 4. Permission management for departing employees: It is impossible to revoke the tool usage permissions of departing employees in a timely manner, posing potential security risks.

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

[0057] Among them, the terminal devices are, for example, mobile terminals, fixed terminals or portable terminals, such as mobile phones, sites, units, devices, multimedia computers, multimedia tablets, Internet nodes, communicators, desktop computers, notebook computers, tablet computers, personal communication system (PCS) devices, positioning devices or any combination thereof, including accessories and peripherals of these devices or any combination thereof.

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

[0059] It should be noted that Figure 1 taking two terminal devices as an example for the multiple terminal devices, actually the number of terminal devices is not limited. Each terminal device is installed with a debugging tool. The debugging tool is a TELNET login and instruction set tool, also known as the verification code calculation tool software (abbreviated as TWW software), and has the functions of decrypting the company's telnet login password and sending test instructions. For example, optical modem debugging tools, PON debugging tools, etc.

[0060] Based on Figure 1 the application scenario shown below, a login method for a debugging tool shown below will be introduced. Figure 2

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

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

[0063] Please refer to Figure 3 , which is a schematic diagram of the login box provided by the embodiment of the present application. Among them, the user name is the username, and the user password is the password.

[0064] In a possible embodiment, the specific steps of S201 are as follows:

[0065] In response to the user's login operation in the login box, the debugging tool obtains the target username and target password entered by the user, and verifies whether the target username and target password meet the preset format; if the debugging tool determines that the target username and target password meet the preset format, it 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 meet the preset format, for example, they cannot be empty, are greater than the preset length, and contain special characters. If the verification passes, a login request is sent to the server. If the verification fails, a reminder message is popped up. For example, "The username cannot be empty", "The password length cannot be less than 8 digits", "The password must contain at least one special character".

[0067] In the embodiment of the present application, by performing format verification at the front end by the debugging tool, the user experience can be quickly improved, ensuring that the data submitted to the server meets the basic format requirements, preventing the user from submitting data with incorrect formats to the server, reducing invalid login requests, thereby reducing the burden on the server and improving performance.

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

[0069] ​Specifically, there is a pre-stored authorized personnel table in the server's database. The authorized personnel table includes the usernames of all current after-sales personnel in the company, the passwords associated with each username, and the cities of employment associated with each username. If the server receives an employment notice for any person, it reads the person's position and city of employment from the employment notice. If the person's position is an after-sales personnel, it generates a username and password for the person and saves the person's information in an associated manner to the authorized personnel table. Among them, the information includes username, password, position, and city of employment. If the server receives a separation notice for any person, it checks whether the username of the person exists in the authorized personnel table. If it exists, it deletes the person's information from the authorized personnel table.

[0070] After the server receives a login request, it first parses the login request to obtain the target username, target password, and the IP address of the target device. Then it checks whether the target username exists in the authorized personnel table to determine whether the target user identified by the target username is a current after-sales personnel of the company.

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

[0072] In a possible embodiment, if the server determines that the target username 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 username 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 to obtain a hash value, and compares the 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 the password verification passes. 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 the 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 deduced from the hash value. In this way, even if the database is leaked, the attacker only obtains the hash value and cannot restore it to the original password, and the password itself will not be leaked, increasing the system security.

[0075] S204. If the server determines that the password associated with the target username is the same as the target password, it determines the city where the target device is located according to the IP address of the target device, and determines whether the city where the target device is located is the same as the city of employment associated with the target username.

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

[0077] S205. If the server determines that the city where the target device is located is the same as the city where the target username is employed, it 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 city where the target username is employed, it 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, it can load the main interface including the core function module, and the user can then operate on the main interface to use the debugging tool for debugging operations.

[0079] Please refer to Figure 4 , which is a schematic diagram of the main interface provided by the embodiment of the present application. It can be seen that the address of the server is 192.168.1.1. The user can enter a test command in the blank box of "Send Command" and then click the "Send Button" on the right to send a test command to the server.

[0080] In a possible embodiment, before executing S201, the method may further include the following steps:

[0081] 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, it 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 specific implementation process, there is also a pre-stored authorized device table in the database of the server. The authorized device table includes the identification information of all terminal devices authorized by the company; the identification information is used to uniquely identify each terminal device, such as the Media Access Control address (MAC address) and the Central Processing Unit identifier (CPU ID). The MAC address is used to uniquely identify the network interface card (NIC), and is usually embedded in the network card of the device by the hardware manufacturer during device production. The CPU ID is a characteristic value used to uniquely identify the CPU.

[0083] After the debugging tool of the target device is started, it can first obtain the identification information of the target device. After the server receives the device identification information sent by the debugging tool, it will compare it with the authorized device list pre-stored on the server. If the identification information of the target device is in the authorized device list, the server will send a device authentication success message to the debugging tool, and the device authentication success message is used to indicate that the target device has been authorized. If the identification information of the target device is not in the authorized device list, the server will send a device authentication failure message, and the device authentication failure message is used to indicate that the target device is not authorized.

[0084] In the embodiment of the present application, the device identification information is unique and difficult to forge. Before the user logs in, verifying the device identification can effectively prevent unauthorized devices from performing any operations. Only the devices that pass the verification can further perform user authentication, reducing potential security threats. Even if an attacker knows the username and password of the user, if the device is not authorized, it still cannot access the system, which can strengthen the security defense line of the system and prevent 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 the debugging tool is started, it connects to the server through a Uniform Resource Locator (URL) and receives the latest version information returned by the server; the debugging tool determines whether an upgrade is required according to the version switch identifier in the latest version information; the version switch identifier is used to indicate whether it is necessary to upgrade before the debugging tool can be used; if the debugging tool determines that an upgrade is required, it performs a version upgrade according to the download path in the latest version information.

[0087] In the specific implementation process, a Uniform Resource Locator (URL) is an 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 of the latest version, the version switch identifier, the version description, and the download path. The version switch identifier being 1 means that the debugging tool can be used whether it is upgraded or not, and Isopen being 0 means that it is necessary to upgrade before the debugging tool can be used. After the debugging tool receives the latest version information, if the version switch identifier is 0, it determines that an upgrade is required and performs a version upgrade and a forced restart 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, "explain": "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 embodiment of the present application, the server side can manage the version control and download path uniformly, which is convenient for managers to monitor and control the versions used by all after-sales personnel. Through server management, new versions can be quickly released to fix bugs or release new functions, and users do not need to update manually one by one. By upgrading only when necessary (when it is necessary to upgrade to use the debugging tool), rather than frequent forced upgrades, unnecessary downloads and update operations are reduced, saving network bandwidth and storage space.

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

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

[0094] In the specific implementation process, if the version switch identifier is 1, it is determined that there is no need to upgrade, and the download path is popped up. As Figure 5 shown, the upgrade version download address (i.e., the download path of the latest version) is "http: / / 113.125.60.254.8010 / static / wwteam-v1.3". When the user clicks the "Copy" button, the download path can be saved in the target device. The user can read the download path from the target device during idle time to manually upgrade the debugging tool.

[0095] In an embodiment of the present application, when it is confirmed that the debugging tool can be used without upgrading, displaying the download path instead of immediately upgrading and restarting helps avoid unnecessary network traffic and resource waste. Users can decide whether to download the update according to the specific situation, reducing the system burden. Some users may work in an environment with low network bandwidth or may not want to directly perform an online download under certain circumstances. By providing the 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 a possible embodiment, if the server determines that the target username does not exist in the authorized personnel list, or if the server determines that the password associated with the target username is different from the target password, or if the server determines that the city where the target device is located is different from the city where the target username is associated with the employment, the server sends a verification failure message to the debugging tool. If the debugging tool receives the verification failure message, a login failure prompt message will pop up, such as "Username does not exist", "Password error", "Abnormal 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 after waiting for a preset duration, pops up the login box again.

[0099] In the specific implementation process, each time the user successfully logs in to the debugging tool, the debugging tool starts timing. After waiting for a preset duration (such as 1 hour), the login box pops up again for verification. Please refer to Figure 6 , which is a schematic diagram of the login box popping up again provided by the embodiment of the present application. After the user re-enters the target username in the blank box corresponding to the user name and re-enters the target password in the blank box corresponding to the user password, the system will re-execute S201 - S205. If the user does not enter the username and password within the preset time period (such as 5 minutes), the debugging tool will automatically exit.

[0100] In an embodiment of the present application, 1 hour after each login, the debugging tool will repeat the authentication. If the authentication fails, the tool software will automatically exit. Even if the user's initial login passes the verification, the re-authentication after 1 hour ensures that the account is not controlled by an unauthorized third party during long-term use. It can also avoid the risk of the user leaving the device without closing the tool software after opening the tool software. Repeated authentication helps ensure that the user is still the same person during the operation process, especially during long working or interaction processes.

[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 username within a preset period. If the number of logins is greater than the preset number, it notifies the management personnel.

[0103] In the specific implementation process, after the server sends a verification success message to the debugging tool, it can record the current login information in the log. The login information includes the target username, 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 number of times the target username is recorded within a preset period (such as one day) is greater than the preset number (such as 10 times), it indicates that the user's login is abnormal, and the management personnel are notified by email. The management personnel can also log in to the background server by themselves to view the log information for review and judgment.

[0104] In the embodiment of the present application, when the number of logins of a user increases sharply, it may indicate that the account has been illegally accessed or misused. Counting the number of logins of the user and notifying the management personnel when it exceeds the preset number can help the management personnel intervene and check in a timely manner, improving the security of the system.

[0105] It should be noted that the server in the embodiment of the present application is deployed with a background server program. Taking the TWW tool software as an example of the debugging tool, the background web management interface includes three modules: TWW login record, TWW account, and version number management. The TWW login record module is used to save the login information of all personnel who have logged in to TWW. The TWW account module is used to save the usernames and passwords of all on-the-job after-sales personnel. The version number management module is used to save the versions of all uploaded 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 . It can be seen that when the user clicks "Version Number Management", the latest version information can be added. The version number is "v-1.1", the version switch identifier is "1", indicating that the debugging tool can be used whether it is upgraded or not. 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 the 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 required.

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

[0113] S904. Pop up the upgrade website, save the current version, and perform a manual upgrade next time.

[0114] The debugging tool will pop up the download address of the latest version. As Figure 5 shown, the user clicks the "Copy" button to save the current version and perform a manual upgrade when free next time.

[0115] S905. Automatically upgrade.

[0116] The debugging tool automatically downloads the latest version for upgrade according to the download path in the latest version information and forces a restart to complete the upgrade.

[0117] S906. Enter the login interface.

[0118] When the debugging tool enters the login interface, a login box will pop up. As Figure 3 shown.

[0119] S907. Send a login request for verification.

[0120] After the user enters the username and password in the login interface, the debugging tool will send 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 message for login failure.

[0124] S910. Enter the main interface.

[0125] S911. Start timing.

[0126] S912. Determine whether 1 hour has passed.

[0127] If it has exceeded 1 hour, then re - execute S906, that is, enter the login interface. If it has not exceeded 1 hour, then re - execute S910, that is, enter the main interface.

[0128] In summary, the embodiment of the present application also provides a login method for a debugging tool, which has the following beneficial effects:

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

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

[0131] (3) Real - time permission management: The permissions of the departed employees will be immediately removed to ensure that the departed employees 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 conduct 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 it is opened.

[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 version of the tool, improving work efficiency and security.

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

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

[0136] 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 username and target password entered by the user, and the IP address of the target device where the debugging tool is located;

[0137] A server for determining whether a target username exists in an authorized personnel table pre-stored in a database; the authorized personnel table includes the usernames of all current after-sales personnel in the company, the passwords associated with each username, and the cities of employment associated with each username.

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

[0139] The server is further configured to, if it is determined that the password associated with the target username 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 city of employment associated with the target username.

[0140] The server is further configured to, 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, send a verification success message to the debugging tool.

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

[0142] In addition, in one embodiment, the present application further provides a computer device, which includes a processor, a memory, and a computer program stored in the memory. When the computer program is run by the processor, it implements the foregoing login method of the debugging tool.

[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 run by the processor, it implements the foregoing login method of the debugging tool.

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

[0145] In some embodiments, the 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 being deployed as an independent program or being deployed as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0146] By way of example, executable instructions may or may not correspond to files in a file system, and may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program under discussion, or in multiple cooperating files (such as files that store one or more modules, subroutines, or portions of code).

[0147] By way of example, executable instructions may be deployed to execute on one computing device, or on multiple computing devices located 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 "including", "comprising", or any other variant thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that includes a series of elements includes not only those elements but also other elements not expressly listed, or elements that are inherent to such process, method, article, or system. Without further limitation, an element qualified by the statement "including a..." does not exclude the presence of additional identical elements in the process, method, article, or system that includes the element.

[0149] The serial numbers of the embodiments of the present application above are only for description and do not represent the superiority or inferiority of the embodiments.

[0150] From the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as a read-only memory / random access memory, magnetic disk, optical disc) and includes several instructions to enable a multimedia terminal device to execute the methods described in the various embodiments of the present application.

[0151] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application accordingly. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally 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 according to 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 user name, a verification success message is sent to the debugging tool.

2. The debugging tool login method according to claim 1, characterized in that: 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: 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 debugging tool login method according to claim 1, characterized in that: 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 sends a login request to the server in response to the user's login operation in the login box, 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.

4. The method for logging into a debugging tool according to claim 3, wherein: Before the debugging tool sends 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 according to 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 it can be used; 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.

5. The debugging tool login method according to claim 4, characterized in that: After the debugging tool determines whether an upgrade is required according to 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.

6. The debugging tool login method according to claim 1, characterized in that: 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 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.

7. The debugging tool login method according to claim 1, characterized in that: 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 responds to the user's login operation in the login box, obtains the target user name and target password input by the user, 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.

8. A debugging tool login system, characterized in that: It includes a server and multiple terminal devices, each of which is equipped with a debugging tool; among which: 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 used to determine 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; 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; The server is further configured to determine the city where the target device is located according to the IP address of the target device if it is determined that the password associated with the target user name is the same as the target password, and to 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.

9. A computer device, characterized in that: The computer device comprises 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 7.

10. 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 7.

Images