Authentication method, device, electronic equipment, system and chip

Abstract

The application provides an authentication method, device, electronic equipment, system and chip. The method comprises the following steps: receiving a login request from a user equipment by using a receiving device; performing a login operation by using an operating device based on the login request and generating login information, wherein the login information comprises a login credential and first permission information; receiving a service request from the user equipment by using the receiving device; and performing an operation on the service request based on the login information and the service request to obtain an execution result. The method can avoid linear permission verification and service processing under the premise of ensuring system security, and let the two operations run in parallel, thereby improving the response speed of the interface processing authentication request.

Description

Technical Field

[0001] This application relates to the technical fields of electronic communications and computer software, and in particular to authentication methods, devices, electronic equipment, systems and chips. Background Technology

[0002] Authentication refers to the process of verifying the authenticity of a claimant's declared identity and rights. It's a crucial link between upstream and downstream processes. Upstream, the system receives the output of permissions, verifies its authenticity, and then acquires the permissions, preparing for the next step of access control. Currently, most applications on mobile terminals require server authentication before use, such as games, communication applications, and quick payment applications. Existing application authentication schemes allow applications to send authentication requests directly to the authentication server through a configured Application Programming Interface (API). However, this scheme involves direct authentication between the authentication server and the application. After receiving the authentication request, the system initiates an authentication request to the permission system based on the token carried in the user's authentication request, parses the specific permissions corresponding to the token, and determines whether the system has permission to access the interface based on the role corresponding to the token. After the system checks and approves the permissions, it begins actual business processing.

[0003] In the existing API request process, the total response time is significantly affected by the token verification of the authentication system. This impact is particularly pronounced in distributed systems, causing not only slow authentication speeds but also increased costs. Therefore, how to avoid linear authorization verification and business processing without compromising the security of API authentication requests has become an urgent problem to be solved.

[0004] Patent CN108683690A discloses an authentication method, characterized by the following steps: an authentication device receives a service establishment request from a user equipment, the request carrying the user equipment's identity identifier; the authentication device determines the device group to which the user equipment belongs and the group authentication status of the device group based on the user equipment's identity identifier, wherein the device group includes multiple user equipments in the same security domain as the user equipment; and if the group authentication status is successful, the authentication device determines the user equipment's user authentication status as successful. This method only involves load balancing across various heterogeneous clusters and cannot save resources or reduce maintenance costs.

[0005] Based on this, this application provides authentication methods, devices, electronic devices, systems, and chips to improve the prior art. Summary of the Invention

[0006] The purpose of this application is to provide authentication methods, devices, electronic devices, systems, and chips that can avoid linear permission verification and business processing while ensuring system security, allowing the two to operate in parallel, thereby improving the response speed of the interface in processing authentication requests.

[0007] The objective of this application is achieved through the following technical solution:

[0008] Firstly, this application provides an authentication method, the method comprising:

[0009] Utilize the receiving device to receive login requests from the user's device;

[0010] Based on the login request, the operating device is used to perform a login operation and generate login information, which includes login credentials and first permission information.

[0011] The receiving device is used to receive service requests from user equipment;

[0012] Based on the login information and the business request, the business request is executed to obtain the execution result.

[0013] The beneficial effects of this technical solution are as follows: By utilizing a receiving device to receive login requests from user devices, the convenience of user login is improved. By operating the device to perform login operations and generate login information including login credentials and initial permission information, the security of user login is enhanced. Utilizing the receiving device to receive business requests from user devices enables efficient processing of business requests. Based on login information and business requests, operations are performed on the business requests to obtain execution results, improving the accuracy of business request processing. By centrally processing login requests and business requests, the utilization of server resources is optimized, improving system efficiency. This enhances the overall performance of the system, providing users with a safer and more convenient service experience, while also providing service providers with an efficient and reliable management method. It avoids linear permission verification and business processing while ensuring system security, allowing both to operate in parallel, thereby improving the response speed of the interface in processing authentication requests.

[0014] In some optional implementations, the method further includes:

[0015] Based on the login credentials, the first permission information is parsed out, and the first permission information and the login credentials are in one-to-one correspondence.

[0016] The beneficial effects of this technical solution are as follows: Based on login credentials, primary permission information is parsed out. There is a one-to-one correspondence between the primary permission information and the login credentials, meaning that each login credential accurately corresponds to specific permission information, avoiding permission confusion and inaccuracies. Parsing the login credentials allows for the rapid acquisition of the user's primary permission information without additional queries or calculations, thereby improving system processing efficiency. The one-to-one correspondence between permission information and login credentials makes permission management simpler and clearer, helping system administrators to set and manage user permissions.

[0017] In some optional implementations, based on the login request, the step of performing a login operation using an operating device and generating login information includes login credentials and permission information, including:

[0018] Determine whether the login request is preset login data;

[0019] If the login request is preset login data, then the login operation is performed using the operating device and the login information is generated;

[0020] If the login request is not the preset login data, a verification failure message is generated, which indicates that the login request failed.

[0021] The beneficial effects of this technical solution are as follows: it determines whether the login request is based on preset login data; if the login request is based on preset login data, it performs the login operation using the operating device and generates the login information; if the login request is not based on preset login data, it generates a verification failure message to indicate that the login request failed. By judging the login request, unauthorized login can be effectively prevented, improving system security. The preset data judgment process can be completed in a short time, which, compared to other complex verification methods, can complete the login operation faster and improve system processing efficiency. For legitimate users, the system can quickly complete the login operation and generate login information, reducing user waiting time and improving user experience. For illegitimate login requests, the system generates a verification failure message, clearly indicating login failure, making it easy for users to understand the reason for the login failure. By judging the preset data, the login verification management process can be simplified, making it easier for system administrators to set and manage login data.

[0022] In some optional implementations, the step of performing an operation on the service request based on the login information and the service request to obtain an execution result includes:

[0023] Based on the aforementioned business request, obtain the second permission information;

[0024] Detect whether the second permission information is preset trusted information;

[0025] If the second permission information is preset trust information, then the service request is executed to obtain the execution result;

[0026] Based on the execution result, determine whether the business request was successful;

[0027] If the service request fails, a first error message is generated;

[0028] If the business request is successful, the business operation is executed and business implementation information is generated.

[0029] The beneficial effects of this technical solution are as follows: First, based on the business request, second permission information is obtained, and then it is checked whether the second permission information is preset trusted information. If the second permission information is preset trusted information, the business request is executed to obtain the execution result. Based on the execution result, it is determined whether the business request was successful. If the business request is unsuccessful, a first error message is generated. If the business request is successful, the business operation is executed and business implementation information is generated. By obtaining the second permission information and checking whether it is preset trusted information, the legitimacy of the business request can be effectively verified, improving the system's security. For legitimate business requests, the system can quickly execute operations and generate business implementation information, reducing user waiting time and improving user experience. For illegitimate business requests or business request failures, the system generates a first error message, clearly indicating the problem with the business request, making it easier for users to understand and take appropriate measures.

[0030] In some optional implementations, the method further includes:

[0031] If the second permission information is preset trusted information, then check whether the second permission information is consistent with the first permission information;

[0032] When the second permission information is consistent with the first permission information, the business implementation information is saved;

[0033] If the second permission information is inconsistent with the first permission information, the business implementation information is deleted and a second error message is generated.

[0034] The beneficial effects of this technical solution are as follows: if the second permission information is preset trusted information, it checks whether the second permission information is consistent with the first permission information; when the second permission information is consistent with the first permission information, it saves the business implementation information; when the second permission information is inconsistent with the first permission information, it deletes the business implementation information and generates a second error message. By checking whether the second permission information is consistent with the first permission information in parallel, business processing and request verification can be performed simultaneously without sacrificing security, thereby improving the response speed of the interface.

[0035] In some optional implementations, the method further includes:

[0036] The service implementation information is transmitted to the user equipment using a transmission device.

[0037] The beneficial effect of this technical solution is that, through the transmission equipment, service implementation information can be transmitted from the data source to the user equipment quickly and accurately, greatly improving the efficiency of information transmission.

[0038] Secondly, this application provides an authentication device, the device including a processor configured to perform the following steps:

[0039] The login request module is used to receive login requests from user devices using the receiving device;

[0040] The login operation module is used to perform a login operation and generate login information using an operating device based on the login request. The login information includes login credentials and first permission information.

[0041] The service request module is used to receive service requests from user equipment using the receiving device;

[0042] The business operation module is used to perform operations on the business request based on the login information and the business request to obtain the execution result.

[0043] In some alternative implementations, the processor is further configured to perform the following steps:

[0044] Based on the login credentials, the first permission information is parsed out, and the first permission information and the login credentials are in one-to-one correspondence.

[0045] In some alternative implementations, the processor is configured to perform a login operation and generate login information using an operating device based on the login request in the following manner:

[0046] Determine whether the login request is preset login data;

[0047] If the login request is preset login data, then the login operation is performed using the operating device and the login information is generated;

[0048] If the login request is not the preset login data, a verification failure message is generated, which indicates that the login request failed.

[0049] In some optional implementations, the processor is configured to perform operations on the service request based on the login information and the service request to obtain an execution result:

[0050] Based on the aforementioned business request, obtain the second permission information;

[0051] Detect whether the second permission information is preset trusted information;

[0052] If the second permission information is preset trust information, then the service request is executed to obtain the execution result;

[0053] Based on the execution result, determine whether the business request was successful;

[0054] If the service request fails, a first error message is generated;

[0055] If the business request is successful, the business operation is executed and business implementation information is generated.

[0056] In some alternative implementations, the processor is further configured to perform the following steps:

[0057] If the second permission information is preset trusted information, then check whether the second permission information is consistent with the first permission information;

[0058] When the second permission information is consistent with the first permission information, the business implementation information is saved;

[0059] If the second permission information is inconsistent with the first permission information, the business implementation information is deleted and a second error message is generated.

[0060] In some alternative implementations, the processor is further configured to perform the following steps:

[0061] The service implementation information is transmitted to the user equipment using a transmission device.

[0062] Thirdly, this application provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of any of the above methods.

[0063] Fourthly, this application provides an authentication system, wherein the electronic device includes:

[0064] The aforementioned electronic devices;

[0065] Fifthly, this application provides a chip that stores a computer program, which, when executed by a processor, implements the steps of any of the above methods. Attached Figure Description

[0066] The present application will be further described below with reference to the accompanying drawings and embodiments.

[0067] Figure 1 A flowchart illustrating an authentication method provided in an embodiment of this application is shown.

[0068] Figure 2 This illustration shows a flowchart of a process for generating login information according to an embodiment of this application.

[0069] Figure 3 This document illustrates a flowchart of an embodiment of the present application for obtaining execution results.

[0070] Figure 4 A structural block diagram of an authentication device provided in an embodiment of this application is shown.

[0071] Figure 5 A structural framework diagram of an electronic device provided in an embodiment of this application is shown.

[0072] Figure 6 A schematic diagram of the structure of an authentication system provided in an embodiment of this application is shown.

[0073] Figure 7 A schematic diagram of the structure of a program product provided in an embodiment of this application is shown. Detailed Implementation

[0074] The embodiments of this application will be further described below with reference to the accompanying drawings and specific implementation methods. It should be noted that, without conflict, the various embodiments or technical features described below can be arbitrarily combined to form new implementation methods.

[0075] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, a and b and c, where a, b, and c can be single or multiple. It is worth noting that "at least one" can also be interpreted as "one or more".

[0076] It should also be noted that, in the embodiments of this application, the words "exemplary" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any implementation or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other implementations or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0077] Method Implementation Examples

[0078] See Figure 1 , Figure 1 A flowchart illustrating an authentication method provided in an embodiment of this application is shown.

[0079] This application provides an authentication method, the method comprising:

[0080] Step S101: Receive a login request from the user device using the receiving device;

[0081] Step S102: Based on the login request, perform a login operation using the operating device and generate login information, the login information including login credentials and first permission information;

[0082] Step S103: Receive a service request from a user equipment using the receiving device;

[0083] Step S104: Based on the login information and the service request, perform an operation on the service request to obtain the execution result.

[0084] Therefore, by utilizing a receiving device to receive login requests from user devices, the convenience of user login is improved. By operating the device to perform the login operation and generating login information including login credentials and initial access permissions, the security of user login is enhanced.

[0085] By utilizing a receiving device to receive service requests from user devices, efficient processing of these requests is achieved. Based on login information and the service request itself, operations are executed to obtain the results, improving the accuracy of service request processing. Centralized processing of login and service requests optimizes server resource utilization and enhances system efficiency.

[0086] It can improve the overall performance of the system, bring users a safer and more convenient service experience, and also bring service providers an efficient and reliable management method. It can avoid linear permission verification and business processing while ensuring system security, allowing the two to operate in parallel, thereby improving the response speed of the interface to handle authentication requests.

[0087] This application does not limit the type of user, which may be, for example, a mobile phone, tablet computer, laptop computer, desktop computer, smart wearable device, or a smart terminal device with a mouse, keyboard, microphone, camera, button, knob, slider, touchpad, stylus, etc.

[0088] In this embodiment, a login credential (token) is a mechanism for authentication between the client and the server. It is a string generated by the server and returned to the client to verify the user's login status. After a user successfully logs in, the server generates a token and sends it to the client, which stores it locally (e.g., in a cookie or local storage). In subsequent requests, the client needs to send this token to the server, which verifies the token's validity to determine if the user is logged in.

[0089] In this application embodiment, permission information (role) is a mechanism used in computer systems and applications to manage and allocate user permissions. In a system, permissions are typically assigned to different roles, rather than directly to users. Users acquire the permissions of a role by becoming a member of that role.

[0090] The embodiments of this application do not limit the login information, which may be, for example, a statement consisting of a username and a user code, such as "Zhang Dan, 13238103".

[0091] In some optional implementations, the method further includes:

[0092] Based on the login credentials, the first permission information is parsed out, and the first permission information and the login credentials are in one-to-one correspondence.

[0093] Therefore, based on the login credentials, the first-level permission information is parsed out. There is a one-to-one correspondence between the first-level permission information and the login credentials, meaning that each login credential accurately corresponds to specific permission information, avoiding permission confusion and inaccuracies. Parsing the login credentials can quickly obtain the user's first-level permission information without additional queries or calculations, thus improving system processing efficiency. The one-to-one correspondence between permission information and login credentials makes permission management simpler and clearer, helping system administrators to set and manage user permissions.

[0094] In some alternative implementations, login credentials can be parsed to obtain authorization information in the following way: First, the server needs to receive the login credentials sent by the client, which is typically a token, such as a JWT (JSON Web Token). Second, the server needs to verify the validity of this token. This typically includes checking whether the token has expired, been tampered with, and matches the sender's identity. If the token is successfully verified, the server will parse the information in the token, namely the first authorization information. For example, if JWT is used, a corresponding library may be needed to parse the JWT; if OAuth 2.0 is used, the corresponding API may need to be called to obtain the authorization information.

[0095] See Figure 2 , Figure 2 This illustration shows a flowchart of a process for generating login information according to an embodiment of this application.

[0096] In some optional implementations, based on the login request, the step of performing a login operation using an operating device and generating login information includes login credentials and permission information, including:

[0097] Step S201: Determine whether the login request is preset login data;

[0098] Step S202: If the login request is preset login data, then use the operating device to perform the login operation and generate the login information;

[0099] Step S203: If the login request is not the preset login data, a verification failure message is generated, which is used to indicate that the login request failed.

[0100] Therefore, it is determined whether the login request is preset login data; if the login request is preset login data, the login operation is performed using the operating device and the login information is generated; if the login request is not preset login data, a verification failure message is generated to indicate that the login request failed.

[0101] By evaluating login requests, unauthorized logins can be effectively prevented, improving system security. The pre-defined data evaluation process can be completed quickly, enabling faster login compared to other complex verification methods and improving system efficiency. For legitimate users, the system can rapidly complete the login process and generate login information, reducing user waiting time and enhancing user experience.

[0102] For invalid login requests, the system will generate a verification failure message, clearly indicating that the login failed, allowing users to understand the reason for the failure. By using preset data for verification, the login verification management process can be simplified, making it easier for system administrators to set and manage login data.

[0103] See Figure 3 , Figure 3 This illustration shows a flowchart of obtaining execution results according to an embodiment of this application.

[0104] In some optional implementations, the step of performing an operation on the service request based on the login information and the service request to obtain an execution result includes:

[0105] Step S301: Based on the business request, obtain the second permission information;

[0106] Step S302: Detect whether the second permission information is preset trusted information;

[0107] Step S303: If the second permission information is preset trust information, then perform an operation on the service request to obtain the execution result;

[0108] Step S304: Based on the execution result, determine whether the business request was successful;

[0109] Step S305: If the service request fails, generate a first error message;

[0110] Step S306: If the business request is successful, then execute the business operation and generate business implementation information.

[0111] Therefore, firstly, based on the business request, the second permission information is obtained, and then it is checked whether the second permission information is the preset trusted information; if the second permission information is the preset trusted information, the business request is executed to obtain the execution result; based on the execution result, it is determined whether the business request was successful.

[0112] If the business request fails, a first error message is generated; if the business request succeeds, the business operation is executed and business implementation information is generated. By obtaining the second permission information and checking whether it is preset trusted information, the legitimacy of the business request can be effectively verified, thus improving the system's security.

[0113] For legitimate business requests, the system can quickly execute operations and generate business implementation information, reducing user waiting time and improving user experience. For illegitimate business requests or failed business requests, the system will generate an initial error message, clearly indicating the problem with the business request, making it easier for users to understand and take appropriate measures.

[0114] In some optional implementations, the method further includes:

[0115] If the second permission information is preset trusted information, then check whether the second permission information is consistent with the first permission information;

[0116] When the second permission information is consistent with the first permission information, the business implementation information is saved;

[0117] If the second permission information is inconsistent with the first permission information, the business implementation information is deleted and a second error message is generated.

[0118] Therefore, if the second permission information is preset trusted information, it is checked whether the second permission information is consistent with the first permission information; if the second permission information is consistent with the first permission information, the business implementation information is saved.

[0119] If the second permission information is inconsistent with the first permission information, the business implementation information is deleted and a second error message is generated. By checking whether the second permission information is consistent with the first permission information in parallel, business processing and request verification can be performed simultaneously without sacrificing security, thereby improving the response speed of the interface.

[0120] In one specific embodiment, firstly, it is necessary to check whether the second permission information is preset trusted information according to the system's preset trusted information list. Next, it is determined whether the second permission information is consistent with the first permission information. If the second permission information is preset trusted information, it is necessary to compare whether the second permission information is consistent with the first permission information. This typically involves comparing various attributes of the permission information, such as permission type and permission scope. Thirdly, business implementation information is saved: if the second permission information is consistent with the first permission information, then the business implementation information needs to be saved to the system. Saving methods may include storing in a database, writing to a file, etc. Fourthly, business implementation information is deleted and a second error message is generated: if the second permission information is inconsistent with the first permission information, then the saved business implementation information needs to be deleted and a second error message is generated. The error message typically includes error codes and error messages, used to indicate the cause and location of the error.

[0121] In some optional implementations, the method further includes:

[0122] The service implementation information is transmitted to the user equipment using a transmission device.

[0123] Therefore, through the transmission equipment, service information can be transmitted quickly and accurately from the data source to the user equipment, greatly improving the efficiency of information transmission.

[0124] In one specific embodiment, appropriate transmission equipment can be prepared according to the selected transmission protocol. For example, if the HTTP protocol is selected, an HTTP server is needed; if the FTP protocol is selected, an FTP server is needed. To ensure transmission security, the business implementation information needs to be encrypted. Various encryption methods can be used, such as symmetric encryption and asymmetric encryption. A suitable encryption method is selected to encrypt the business implementation information. Transmission parameters are set according to the user device information. Transmission parameters include the target device address, transmission port, and transmission speed. Ensure the transmission parameters are set correctly so that the business implementation information can be successfully transmitted to the user device. After preparing the transmission equipment, encrypted business implementation information, and transmission parameters, the transmission process is started. The transmission equipment sends the encrypted business implementation information to the user device according to the set transmission parameters. After transmission is complete, the transmission result needs to be confirmed. This can be confirmed by checking transmission logs, receiving confirmation, etc., to verify whether the business implementation information has been successfully transmitted to the user device.

[0125] Device Examples

[0126] See Figure 4 , Figure 4 A structural block diagram of an authentication device provided in an embodiment of this application is shown.

[0127] This application also provides an authentication device, the specific implementation of which is consistent with the implementation method and the technical effects achieved in the above method embodiments, and some contents will not be repeated.

[0128] This application provides an authentication device, the device including a processor, the processor being configured to perform the following steps:

[0129] Login request module 101 is used to receive login requests from user devices using a receiving device;

[0130] The login operation module 102 is used to perform a login operation and generate login information using an operating device based on the login request. The login information includes login credentials and first permission information.

[0131] Service request module 103 is used to receive service requests from user equipment using the receiving device;

[0132] The business operation module 104 is used to perform operations on the business request based on the login information and the business request to obtain the execution result.

[0133] In some alternative implementations, the processor is further configured to perform the following steps:

[0134] Based on the login credentials, the first permission information is parsed out, and the first permission information and the login credentials are in one-to-one correspondence.

[0135] In some alternative implementations, the processor is configured to perform a login operation and generate login information using an operating device based on the login request in the following manner:

[0136] Determine whether the login request is preset login data;

[0137] If the login request is preset login data, then the login operation is performed using the operating device and the login information is generated;

[0138] If the login request is not the preset login data, a verification failure message is generated, which indicates that the login request failed.

[0139] In some optional implementations, the processor is configured to perform operations on the service request based on the login information and the service request to obtain an execution result:

[0140] Based on the aforementioned business request, obtain the second permission information;

[0141] Detect whether the second permission information is preset trusted information;

[0142] If the second permission information is preset trust information, then the service request is executed to obtain the execution result;

[0143] Based on the execution result, determine whether the business request was successful;

[0144] If the service request fails, a first error message is generated;

[0145] If the business request is successful, the business operation is executed and business implementation information is generated.

[0146] In some alternative implementations, the processor is further configured to perform the following steps:

[0147] If the second permission information is preset trusted information, then check whether the second permission information is consistent with the first permission information;

[0148] When the second permission information is consistent with the first permission information, the business implementation information is saved;

[0149] If the second permission information is inconsistent with the first permission information, the business implementation information is deleted and a second error message is generated.

[0150] In some alternative implementations, the processor is further configured to perform the following steps:

[0151] The service implementation information is transmitted to the user equipment using a transmission device.

[0152] Equipment Implementation Examples

[0153] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of any of the above methods. The specific implementation method and the technical effects achieved are the same as those described in the above method embodiments, and some contents will not be repeated.

[0154] See Figure 5 , Figure 5 A structural framework diagram of an electronic device provided in an embodiment of this application is shown.

[0155] The electronic device includes at least one memory 210, at least one processor 220, and a bus 230 connecting different platform systems.

[0156] The memory 210 may include a readable medium in the form of volatile memory, such as random access memory (RAM) 211 and / or cache memory 212, and may further include read-only memory (ROM) 213.

[0157] The memory 210 also stores a computer program, which can be executed by the processor 220 to enable the processor 220 to implement the steps of any of the above methods.

[0158] The memory 210 may also include a utility 214 having at least one program module 215, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0159] Accordingly, processor 220 can execute the aforementioned computer program, and can also execute utility 214.

[0160] The processor 220 may employ one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0161] Bus 230 can be one or more of several types of bus structures, including a memory bus or memory controller, peripheral bus, graphics acceleration port, processor, or a local bus using any bus structure with multiple bus structures.

[0162] The electronic device can also communicate with one or more external devices 240, such as a keyboard, pointing device, Bluetooth device, etc., and with one or more devices capable of interacting with the electronic device, and / or with any device that enables the electronic device to communicate with one or more other computing devices (e.g., a router, modem, etc.). This communication can be performed through input / output interface 250. Furthermore, the electronic device can communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 260. Network adapter 260 can communicate with other modules of the electronic device via bus 230. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms.

[0163] System Implementation Examples

[0164] See Figure 6 , Figure 6 A schematic diagram of the structure of an authentication system provided in an embodiment of this application is shown.

[0165] This application embodiment also provides an authentication system, the system comprising:

[0166] The aforementioned electronic devices.

[0167] Medium Examples

[0168] This application also provides a chip that stores a computer program. When the computer program is executed by a processor, it implements the steps of any of the above methods. The specific implementation method and the technical effects achieved are the same as those described in the above method embodiments, and some details will not be repeated.

[0169] See Figure 7 , Figure 7 A schematic diagram of the structure of a program product provided in an embodiment of this application is shown.

[0170] The program product is used to implement any of the methods described above. The program product may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In embodiments of this application, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device. The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0171] The chip may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The readable storage medium may also be any readable medium capable of sending, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, or any suitable combination thereof. The program code for performing the operations of this invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C, Python, or similar programming languages. The program code may be executed entirely on a user computing device, partially on a user device, as a standalone software package, partially on a user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing devices can be connected to user computing devices via any type of network, including local area networks (LANs) or wide area networks (WANs), or they can be connected to external computing devices (e.g., via the Internet using an Internet service provider).

[0172] This application describes the invention from the perspectives of purpose, performance, progress, and novelty, and it meets the functional enhancement and use requirements emphasized by the Patent Law. The above description and drawings are merely preferred embodiments of this application and are not intended to limit this application. Therefore, all structures, devices, features, etc., that are similar to or identical to those of this application, i.e., all equivalent substitutions or modifications made in accordance with the scope of this patent application, shall fall within the scope of protection of this patent application.

Claims

1. An authentication method, characterized in that, The method includes: Utilize the receiving device to receive login requests from the user's device; Based on the login request, the operating device is used to perform a login operation and generate login information, which includes login credentials and first permission information. The receiving device is used to receive service requests from user equipment; Based on the login information and the business request, the business request is executed to obtain the execution result; The step of performing an operation on the service request based on the login information and the service request to obtain an execution result includes: Based on the aforementioned business request, obtain the second permission information; Detect whether the second permission information is preset trusted information; If the second permission information is preset trust information, then the service request is executed to obtain the execution result; Based on the execution result, determine whether the business request was successful; If the service request fails, a first error message is generated; If the business request is successful, the business operation is executed and business implementation information is generated; If the second permission information is preset trusted information, then check whether the second permission information is consistent with the first permission information; When the second permission information is consistent with the first permission information, the business implementation information is saved; When the second permission information is inconsistent with the first permission information, the business implementation information is deleted and a second error message is generated.

2. The authentication method according to claim 1, characterized in that, The method further includes: parsing the first permission information based on the login credentials, wherein the first permission information and the login credentials are in one-to-one correspondence.

3. The authentication method according to claim 1, characterized in that, Based on the login request, the system uses an operating device to perform a login operation and generate login information, which includes login credentials and first permission information, including: Determine whether the login request is preset login data; If the login request is preset login data, then the login operation is performed using the operating device and the login information is generated; If the login request is not the preset login data, a verification failure message is generated, which indicates that the login request failed.

4. The authentication method according to claim 3, characterized in that, The method further includes: using a transmission device to transmit the service implementation information to the user equipment.

5. An authentication device, characterized in that, The apparatus includes a module that implements the authentication method according to any one of claims 1 to 4.

6. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the method according to any one of claims 1-4.

7. An authentication system, characterized in that, The authentication system includes: the electronic device as described in claim 6.

8. A chip, characterized in that, The chip stores a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1-4.

Images