System login method, device, equipment and medium

By scanning the login identifier to generate a semantic message structure and using ECDSA signature verification, combined with blockchain node synchronization, the problem of static passwords being easily stolen is solved, and a secure and convenient system login experience is achieved.

CN116599676BActive Publication Date: 2026-06-05HANGZHOU DADAO YIYI TECH CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
HANGZHOU DADAO YIYI TECH CO LTD
Filing Date
2023-05-16
Publication Date
2026-06-05

Smart Images

  • Figure CN116599676B_ABST
    Figure CN116599676B_ABST
Patent Text Reader

Abstract

The application discloses a system login method and device, equipment and medium, and relates to the technical field of computers. The method is applied to a preset verification tool and comprises the following steps: scanning a current login identifier to obtain a corresponding semantic message structure; when a login request is detected, performing ECDSA signature on the message structure by using a preset private key to obtain a corresponding signature value; synchronizing the signature value to a block chain node, so that a server verifies the signature value obtained from the block chain node, obtains corresponding address information, determines a target user identity corresponding to the address information from a user identity library bound with the system in advance, and then sends a login token corresponding to the target user identity to a front end. Through the above scheme, the login identifier is scanned to obtain the semantic message structure, and the ECDSA signature verification is performed, so that more secure and more convenient system login can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to system login methods, apparatus, devices and media. Background Technology

[0002] The current login method for operating systems (Windows, Linux, etc.) or business systems mainly involves users entering a correct static password. However, this login method has some significant technical problems: First, users need to remember the static password. Once forgotten, users will be completely unable to log in to the operating system or business system. Second, the static password is stored in a file on the operating system or server, which is easily stolen, making the static password easy to crack.

[0003] In summary, how to achieve more secure and convenient system login is a problem that needs to be solved in this field. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a system login method, apparatus, device, and medium that can achieve a more secure and convenient system login. The specific solution is as follows:

[0005] In a first aspect, this application discloses a system login method applied to a preset verification tool, comprising:

[0006] Scan the current login identifier to obtain the corresponding semantic message structure;

[0007] When a login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value;

[0008] The signature value is synchronized to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end.

[0009] Optionally, scanning the current login identifier to obtain the corresponding semantic message structure includes:

[0010] The server determines whether the user's current login status is valid. If not, it generates a corresponding semantic message structure and sends the QR code link of the message structure to the front end so that the front end can display the corresponding QR code based on the QR code link.

[0011] The QR code displayed on the front end is scanned to obtain the corresponding message structure.

[0012] Optionally, after sending the login token corresponding to the target user's identity to the front end, the method further includes:

[0013] If the user's current login status is valid, then the front end communicates with the server based on the login token.

[0014] Optionally, the step of determining whether the user's current login status is valid via the server, and if not, generating a corresponding semantic message structure, includes:

[0015] The server determines whether the user's current login status is valid. If not, when the server receives a QR code display request from the front end, it generates a corresponding semantic message structure based on the current website domain, the timestamp of the QR code display request, the front end's device identifier, the preset login message, and a random sequence.

[0016] Optionally, when a login request is detected, performing an ECDSA signature on the message structure using a preset private key to obtain the corresponding signature value includes:

[0017] The message structure contains the current website domain name, the timestamp of the QR code display request, the front-end device identifier, the preset login message, and the random sequence, which are displayed so that the user can confirm whether to generate a login request.

[0018] When the login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value.

[0019] Optionally, synchronizing the signature value to the blockchain node includes:

[0020] The signature value is submitted to the transaction executor so that when the system is restored to online status, the transaction executor can synchronize the signature value and its associated transaction information to the first blockchain node connected to it.

[0021] The verified signature value and its associated transaction information are synchronized to the second blockchain node through the first blockchain node; wherein the second blockchain node is a chain node connected to the server.

[0022] Optionally, the server verifies the signature value obtained from the blockchain node, including:

[0023] The server listens to the second blockchain node. When it detects that there is transaction information containing login information in the second blockchain node, it verifies the signature value in the transaction information containing login information.

[0024] Secondly, this application discloses a system login device applied to a preset verification tool, comprising:

[0025] The message structure acquisition module is used to scan the current login identifier to obtain the corresponding semantic message structure;

[0026] The signature value acquisition module is used to perform ECDSA signature on the message structure using a preset private key when a login request is detected, so as to obtain the corresponding signature value.

[0027] The login module is used to synchronize the signature value to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end.

[0028] Thirdly, this application discloses an electronic device, including:

[0029] Memory, used to store computer programs;

[0030] A processor is configured to execute the computer program to implement the steps of the aforementioned disclosed system login method.

[0031] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the steps of the aforementioned disclosed system login method.

[0032] The beneficial effects of this application are as follows: The current login identifier is scanned to obtain the corresponding semantic message structure; when a login request is detected, the message structure is ECDSA-signed using a preset private key to obtain the corresponding signature value; the signature value is synchronized to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, and determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end. Therefore, this application only requires scanning the login identifier of each system using a preset verification tool to complete the relevant system login, which is more widespread and does not require downloading other tools corresponding to the system, making it more convenient; after scanning the login identifier, a semantic message structure can be obtained, allowing users to determine the corresponding login information, thereby improving the user experience; the corresponding ECDSA signature verification and blockchain node synchronization ensure that a unique target user identity and its corresponding login token are determined, eliminating the need for static passwords and enabling more secure and convenient system login. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0034] Figure 1 This application discloses a system login method flowchart;

[0035] Figure 2 This is a specific system login diagram disclosed in this application;

[0036] Figure 3 This application discloses a specific system login method flowchart;

[0037] Figure 4 This is a schematic diagram of a specific message structure disclosed in this application;

[0038] Figure 5 This is a flowchart of another specific system login method disclosed in this application;

[0039] Figure 6 This is a schematic diagram of a specific transaction information disclosed in this application;

[0040] Figure 7 This is a schematic diagram of the structure of a system login device disclosed in this application;

[0041] Figure 8 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0042] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0043] The current login method for operating systems (Windows, Linux, etc.) or business systems mainly involves users entering a correct static password. However, this login method has some significant technical problems: First, users need to remember the static password. Once forgotten, users will be completely unable to log in to the operating system or business system. Second, the static password is stored in a file on the operating system or server, which is easily stolen, making the static password easy to crack.

[0044] Therefore, this application provides a system login solution that enables a more secure and convenient system login.

[0045] See Figure 1 As shown in the figure, this application discloses a system login method applied to a preset verification tool, including:

[0046] Step S11: Scan the current login identifier to obtain the corresponding semantic message structure.

[0047] Understandably, before scanning the current login identifier, the preset verification tool needs to bind the user to the preset verification tool and generate a corresponding login identifier. For example, the preset verification tool could be a tool like DaoYiDun. Figure 2 The diagram illustrates a specific system login scenario. When a user enters the login interface on the front end but does not initiate a login request, the front end sends a request to the server to determine whether the user's current login status is valid. This request carries the current website domain, the timestamp of the login identifier display request, and the front end's device identifier, allowing the server to determine the user's current login status. If the server determines that the user's current login status is not valid (i.e., invalid), the server generates a corresponding semantic message structure based on the current website domain, the timestamp of the login identifier display request, the front end's device identifier, a preset login message, and a random sequence. The server then sends the login identifier link from this message structure to the front end. The front end displays the corresponding login identifier based on this link. In this way, a preset verification tool can scan the login identifier displayed on the front end to obtain the corresponding semantic message structure.

[0048] Step S12: When a login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value.

[0049] In this embodiment, the user determines whether to log in based on the semantic message structure. If the user decides to log in, a login request will be initiated. When the login request is detected, the message structure is signed using ECDSA (The Elliptic Curve Digital Signature Algorithm) with a preset private key to obtain the corresponding signature value.

[0050] Step S13: Synchronize the signature value to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end.

[0051] For example Figure 2 As shown, the preset verification tool notifies the server of user login confirmation in two ways. One is through blockchain synchronization, which can be completed in real time and also supports short-term offline operation. The signature value is synchronized to the blockchain node, and the server verifies the signature value obtained from the blockchain node. The other way is through real-time interaction with the server. This method requires sending the login request and signature value to the server in real time so that the server can confirm the signature.

[0052] After the server verifies the signature value using the corresponding public key, it will obtain the corresponding address information and determine the target user identity corresponding to the address information from the user identity database pre-bound to the system. Then, it will send the login token corresponding to the target user identity to the front end. When the user's login status is valid, the front end can communicate with the server based on the login token.

[0053] The beneficial effects of this application are as follows: The current login identifier is scanned to obtain the corresponding semantic message structure; when a login request is detected, the message structure is ECDSA-signed using a preset private key to obtain the corresponding signature value; the signature value is synchronized to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, and determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end. Therefore, this application only requires scanning the login identifier of each system using a preset verification tool to complete the relevant system login, which is more widespread and does not require downloading other tools corresponding to the system, making it more convenient; after scanning the login identifier, a semantic message structure can be obtained, allowing users to determine the corresponding login information, thereby improving the user experience; the corresponding ECDSA signature verification and blockchain node synchronization ensure that a unique target user identity and its corresponding login token are determined, eliminating the need for static passwords and enabling more secure and convenient system login.

[0054] See Figure 3 As shown in the figure, this application discloses a specific system login method applied to a preset verification tool, including:

[0055] Step S21: The server determines whether the user's current login status is valid. If not, it generates a corresponding semantic message structure and sends the QR code link of the message structure to the front end, so that the front end can display the corresponding QR code based on the QR code link; the QR code displayed by the front end is scanned to obtain the corresponding message structure.

[0056] In this embodiment, the step of determining whether the user's current login status is valid through the server, and generating a corresponding semantic message structure if not, includes: determining whether the user's current login status is valid through the server; if not, when the server receives a QR code display request from the front end, generating a corresponding semantic message structure based on the current website domain name, the timestamp of the QR code display request, the front end's device identifier, a preset login message, and a random sequence. For example... Figure 4 The diagram illustrates a specific message structure, which includes "domain: current website domain", "timestap: timestamp", "requested device ID: browser's user-agent", "fixed message: xxx website user requests your authorization to log in on the Daoyidun device", "random sequence: 4323243895243243298", and "request ID: 10001". The login identifier, for example, is a QR code.

[0057] Step S22: When a login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value.

[0058] In this embodiment, when a login request is detected, the message structure is ECDSA-signed using a preset private key to obtain a corresponding signature value. This includes displaying the current website domain, the timestamp of the QR code display request, the front-end device identifier, the preset login message, and the random sequence in the message structure so that the user can confirm whether to generate a login request. When the login request is detected, the message structure is ECDSA-signed using a preset private key to obtain a corresponding signature value. Displaying the current website domain, the timestamp of the QR code display request, the front-end device identifier, the preset login message, and the random sequence in the message structure allows the user to intuitively determine the relevant information to decide whether to log in. For example, when the user confirms to log in, they can click the "Confirm Login" button displayed on the front-end interface to generate a login request. After the login request is generated, the preset verification tool will use the preset private key to ECDSA-sign the message structure to obtain a corresponding signature value.

[0059] Step S23: Synchronize the signature value to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end.

[0060] In this embodiment, after sending the login token corresponding to the target user's identity to the front end, the method further includes: if the user's current login status is the valid status, then the front end communicates with the server based on the login token. It can be understood that obtaining the login token indicates successful login, thus allowing direct communication with the server based on the login token during the login validity period.

[0061] Therefore, the preset verification tool in this application can obtain and display a semantic message structure by scanning a QR code, allowing users to intuitively determine whether to initiate a login request based on the semantic message structure. This also allows users to know whether the login meets expectations, thus improving the user experience. This application also requires users to record their login password, preventing unauthorized access to the password. Therefore, it can improve the reliability of system login and make it more convenient.

[0062] See Figure 5As shown in the embodiment, this application discloses another specific system login method, applied to a preset verification tool, including:

[0063] Step S31: Scan the current login identifier to obtain the corresponding semantic message structure.

[0064] Step S32: When a login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value.

[0065] Step S33: Submit the signature value to the transaction executor so that when the system is restored to online status, the transaction executor can synchronize the signature value and its associated transaction information to the first blockchain node connected to it.

[0066] The pre-defined verification tool has a built-in transaction executor that connects to blockchain nodes. This executor can read information from the blockchain and supports interaction with blockchain nodes. Therefore, when a signature value is submitted to the transaction executor, the executor packages the signature value and its associated transaction information and synchronizes it to the first blockchain node it is connected to. It's important to note that if the device is currently offline (i.e., without network access), the transaction executor will continuously attempt to send the signature value and its associated transaction information so that when it reconnects to the network, the signature value and its associated transaction information are synchronized to the first blockchain node immediately.

[0067] Step S34: The verified signature value and its associated transaction information are synchronized to the second blockchain node through the first blockchain node; wherein, the second blockchain node is a chain node connected to the server; so that the server can listen to the second blockchain node, and when it detects that there is transaction information containing login information in the second blockchain node, it verifies the signature value in the transaction information containing login information to obtain the corresponding address information, and determines the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then sends the login token corresponding to the target user identity to the front end.

[0068] Understandably, after receiving the signature value and its associated transaction information, the first blockchain node will verify the signature value. Only after successful verification will it synchronize the signature value and its associated transaction information to other blockchain nodes, thus improving security and reliability. It is also understandable that the first blockchain node is connected to the transaction executor, while the second blockchain node is directly connected to the server; therefore, it is possible for the first and second blockchain nodes to be the same blockchain node.

[0069] In this embodiment, the server traverses the transactions on the blocks from the chain nodes directly connected to it, and listens for login event information, such as... Figure 6 The diagram illustrates a specific transaction information scenario. Upon detecting a user login-related event, the system verifies the transaction information. Once verification is successful, the login process is completed.

[0070] The server will obtain the signature value, use the public key used for signing to verify the signature, and obtain the corresponding address information. This address information represents the user's identity. Therefore, the server can determine the unique target user identity corresponding to the address information from the user identity database pre-bound to the system. The server will encrypt the user information, store it in the login token, and push it to the user's front-end login interface, enabling the front-end to communicate with the server based on the login token.

[0071] As can be seen, this application uses the blockchain signature algorithm to sign semantic data packets and package them into blockchain nodes. The server uses the blockchain node consensus mechanism to obtain the login-related transaction information packaged on the user's device. The server encrypts the user information, stores it in the login token, and pushes it to the user's front-end login interface to complete the authentication.

[0072] See Figure 7 As shown in the figure, this application discloses a system login device applied to a preset verification tool, including:

[0073] The message structure acquisition module 11 is used to scan the current login identifier to obtain the corresponding semantic message structure;

[0074] The signature value acquisition module 12 is used to perform ECDSA signature on the message structure using a preset private key when a login request is detected, so as to obtain the corresponding signature value.

[0075] The login module 13 is used to synchronize the signature value to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end.

[0076] The beneficial effects of this application are as follows: The current login identifier is scanned to obtain the corresponding semantic message structure; when a login request is detected, the message structure is ECDSA-signed using a preset private key to obtain the corresponding signature value; the signature value is synchronized to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, and determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end. Therefore, this application only requires scanning the login identifier of each system using a preset verification tool to complete the relevant system login, which is more widespread and does not require downloading other tools corresponding to the system, making it more convenient; after scanning the login identifier, a semantic message structure can be obtained, allowing users to determine the corresponding login information, thereby improving the user experience; the corresponding ECDSA signature verification and blockchain node synchronization ensure that a unique target user identity and its corresponding login token are determined, eliminating the need for static passwords and enabling more secure and convenient system login.

[0077] In some specific embodiments, the message structure acquisition module 11 includes:

[0078] The QR code display submodule is used to determine whether the user's current login status is valid through the server. If not, it generates a corresponding semantic message structure and sends the QR code link of the message structure to the front end so that the front end can display the corresponding QR code based on the QR code link.

[0079] The message structure acquisition unit is used to scan the QR code displayed on the front end to obtain the corresponding message structure.

[0080] In some specific embodiments, the system login device includes:

[0081] The communication unit is used to communicate with the server through the front end based on the login token if the user's current login status is the valid status.

[0082] In some specific embodiments, the QR code display submodule includes:

[0083] The message structure generation unit is used to determine whether the user's current login status is valid through the server. If not, when the server receives a QR code display request returned by the front end, it generates a corresponding semantic message structure based on the current website domain name, the timestamp of the QR code display request, the device identifier of the front end, the preset login message, and the random sequence.

[0084] In some specific embodiments, the signature value acquisition module 12 includes:

[0085] The login request confirmation unit is used to display the current website domain name, the timestamp of the QR code display request, the device identifier of the front end, the preset login message, and the random sequence in the message structure so that the user can confirm whether to generate a login request.

[0086] The signature value generation unit is used to perform ECDSA signature on the message structure using a preset private key when the login request is detected, so as to obtain the corresponding signature value.

[0087] In some specific embodiments, the login module 13 includes:

[0088] The first synchronization unit is used to submit the signature value to the transaction executor so that when the system is restored to online status, the transaction executor can synchronize the signature value and its associated transaction information to the first blockchain node connected to it.

[0089] The second synchronization unit is used to synchronize the verified signature value and its associated transaction information to the second blockchain node through the first blockchain node; wherein the second blockchain node is a chain node connected to the server.

[0090] In some specific embodiments, the login module 13 includes:

[0091] The verification unit is used for the server to listen to the second blockchain node. When it detects that there is transaction information containing login information in the second blockchain node, it verifies the signature value in the transaction information containing login information.

[0092] Furthermore, embodiments of this application also provide an electronic device. Figure 8 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0093] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Specifically, it may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 and applied to a preset verification tool to implement the following steps:

[0094] Scan the current login identifier to obtain the corresponding semantic message structure;

[0095] When a login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value;

[0096] The signature value is synchronized to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end.

[0097] In some specific embodiments, the processor executes a computer program stored in the memory, specifically implementing the following steps:

[0098] The server determines whether the user's current login status is valid. If not, it generates a corresponding semantic message structure and sends the QR code link of the message structure to the front end so that the front end can display the corresponding QR code based on the QR code link.

[0099] The QR code displayed on the front end is scanned to obtain the corresponding message structure.

[0100] In some specific embodiments, the processor executes a computer program stored in the memory, specifically implementing the following steps:

[0101] If the user's current login status is valid, then the front end communicates with the server based on the login token.

[0102] In some specific embodiments, the processor executes a computer program stored in the memory, specifically implementing the following steps:

[0103] The server determines whether the user's current login status is valid. If not, when the server receives a QR code display request from the front end, it generates a corresponding semantic message structure based on the current website domain, the timestamp of the QR code display request, the front end's device identifier, the preset login message, and a random sequence.

[0104] In some specific embodiments, the processor executes a computer program stored in the memory, specifically implementing the following steps:

[0105] The message structure contains the current website domain name, the timestamp of the QR code display request, the front-end device identifier, the preset login message, and the random sequence, which are displayed so that the user can confirm whether to generate a login request.

[0106] When the login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value.

[0107] In some specific embodiments, the processor executes a computer program stored in the memory, specifically implementing the following steps:

[0108] The signature value is submitted to the transaction executor so that when the system is restored to online status, the transaction executor can synchronize the signature value and its associated transaction information to the first blockchain node connected to it.

[0109] The verified signature value and its associated transaction information are synchronized to the second blockchain node through the first blockchain node; wherein the second blockchain node is a chain node connected to the server.

[0110] In some specific embodiments, the processor, by executing a computer program stored in the memory, may further include the following steps:

[0111] The server listens to the second blockchain node. When it detects that there is transaction information containing login information in the second blockchain node, it verifies the signature value in the transaction information containing login information.

[0112] In this embodiment, the power supply 23 is used to provide operating voltage for various hardware devices on the electronic device; the communication interface 24 can create a data transmission channel between the electronic device and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0113] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0114] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored on it include operating system 221, computer program 222 and data 223, etc., and the storage method can be temporary storage or permanent storage.

[0115] The operating system 221 manages and controls the various hardware devices and computer programs 222 on the electronic device to enable the processor 21 to perform calculations and processing on the massive amounts of data 223 in the memory 22. The operating system 221 can be Windows, Unix, Linux, etc. The computer program 222, in addition to including a computer program capable of performing the system login method executed by the electronic device as disclosed in any of the foregoing embodiments, may further include computer programs capable of performing other specific tasks. The data 223 may include data received by the electronic device from external devices, as well as data collected by its own input / output interface 25.

[0116] Furthermore, embodiments of this application also disclose a computer-readable storage medium storing a computer program. When the computer program is loaded and executed by a processor, it implements the method steps executed during the system login process disclosed in any of the foregoing embodiments.

[0117] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0118] The above provides a detailed description of a system login method, apparatus, device, and medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A system login method, characterized in that, Applied to preset verification tools, including: Scan the current login identifier to obtain the corresponding semantic message structure; When a login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value; The signature value is synchronized to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end. The step of synchronizing the signature value to the blockchain node includes: The signature value is submitted to the transaction executor. When the system returns to online, the transaction executor synchronizes the signature value and its associated transaction information to the first blockchain node connected to it. The first blockchain node then synchronizes the verified signature value and its associated transaction information to the second blockchain node, which is a chain node connected to the server. If the system is currently offline, the transaction executor will continuously attempt to send the signature value and its associated transaction information to the first blockchain node connected to it. The server verifies the signature value obtained from the blockchain node, including: The server listens to the second blockchain node. When it detects that there is transaction information containing login information in the second blockchain node, it verifies the signature value in the transaction information containing login information.

2. The system login method according to claim 1, characterized in that, The step of scanning the current login identifier to obtain the corresponding semantic message structure includes: The server determines whether the user's current login status is valid. If not, it generates a corresponding semantic message structure and sends the QR code link of the message structure to the front end so that the front end can display the corresponding QR code based on the QR code link. The QR code displayed on the front end is scanned to obtain the corresponding message structure.

3. The system login method according to claim 2, characterized in that, After sending the login token corresponding to the target user's identity to the front end, the process further includes: If the user's current login status is valid, then the front end communicates with the server based on the login token.

4. The system login method according to claim 2, characterized in that, The process involves the server determining whether the user's current login status is valid. If not, a corresponding semantic message structure is generated, including: The server determines whether the user's current login status is valid. If not, when the server receives a QR code display request from the front end, it generates a corresponding semantic message structure based on the current website domain, the timestamp of the QR code display request, the front end's device identifier, the preset login message, and a random sequence.

5. The system login method according to claim 4, characterized in that, When a login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value, including: The message structure contains the current website domain name, the timestamp of the QR code display request, the front-end device identifier, the preset login message, and the random sequence, which are displayed so that the user can confirm whether to generate a login request. When the login request is detected, the message structure is signed using a preset private key to obtain the corresponding signature value.

6. A system login device, characterized in that, Applied to preset verification tools, including: The message structure acquisition module is used to scan the current login identifier to obtain the corresponding semantic message structure; The signature value acquisition module is used to perform ECDSA signature on the message structure using a preset private key when a login request is detected, so as to obtain the corresponding signature value. The login module is used to synchronize the signature value to the blockchain node so that the server can verify the signature value obtained from the blockchain node, obtain the corresponding address information, determine the target user identity corresponding to the address information from the user identity database pre-bound to the system, and then send the login token corresponding to the target user identity to the front end. The login module is specifically used for: The signature value is submitted to the transaction executor. When the system returns to online, the transaction executor synchronizes the signature value and its associated transaction information to the first blockchain node connected to it. The first blockchain node then synchronizes the verified signature value and its associated transaction information to the second blockchain node, which is a chain node connected to the server. If the system is currently offline, the transaction executor will continuously attempt to send the signature value and its associated transaction information to the first blockchain node connected to it. The login module is specifically used for: The server listens to the second blockchain node. When it detects that there is transaction information containing login information in the second blockchain node, it verifies the signature value in the transaction information containing login information.

7. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the system login method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, Used to store a computer program; wherein, when the computer program is executed by a processor, it implements the steps of the system login method as described in any one of claims 1 to 5.