Login authentication method and device, electronic equipment and readable storage medium

Abstract

This application discloses a login authentication method, apparatus, electronic device, and readable storage medium. The login authentication method includes: receiving a first 5G message sent by a first terminal, wherein the first 5G message is used to instruct a second terminal to request login to a target service, and the first 5G message carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal; obtaining a second mobile phone number by performing data anonymization processing on the first mobile phone number; and sending the first user identifier and the second mobile phone number to a server corresponding to the target service for login authentication.

Description

Technical Field

[0001] This application relates to the field of login authentication, and more particularly to a login authentication method, apparatus, electronic device, and readable storage medium. Background Technology

[0002] In related technologies, a verification code is sent to the user's terminal by having the user enter their mobile phone number in the terminal's application or H5 page. After receiving the verification code, the user enters the received verification code in the application or H5 page to complete the login authentication.

[0003] However, using the above method for login authentication will expose the user's mobile phone number to a third party, which poses a security risk. Summary of the Invention

[0004] This application discloses a login authentication method, apparatus, electronic device, and readable storage medium that can prevent the user's mobile phone number from being exposed to third parties.

[0005] To solve the above problems, this application adopts the following technical solution:

[0006] In a first aspect, embodiments of this application disclose a login authentication method applied to a login authentication device, comprising: receiving a first 5G message sent by a first terminal, wherein the first 5G message is used to instruct a second terminal to request login to a target service, and the first 5G message carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal; obtaining a second mobile phone number by performing data anonymization processing on the first mobile phone number; and sending the first user identifier and the second mobile phone number to a server corresponding to the target service for login authentication.

[0007] Secondly, this application discloses a login authentication method applied to a login authentication device, comprising: receiving a first 5G message login request sent by a second terminal through a server corresponding to a target service, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, the first 5G message login request carries a second user identifier, the second user identifier being a user identifier determined by the second terminal based on historical login information corresponding to the target service; determining a service identifier corresponding to the second user identifier and a first mobile phone number corresponding to the second user identifier based on the second user identifier, wherein the first mobile phone number is a mobile phone number corresponding to the first terminal; sending a second 5G message to the first terminal, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, the second 5G message carrying a first message identifier corresponding to the second 5G message; receiving a target instruction sent by the first terminal in response to a received determination operation, wherein the target instruction carries the second message identifier; and, if the second message identifier is successfully authenticated based on the first message identifier, sending the second user identifier and the second mobile phone number to the server for login authentication, wherein the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number.

[0008] Thirdly, this application discloses a login authentication method applied to a server corresponding to a target service, comprising: receiving a first user identifier and a second mobile phone number sent by a login authentication device for identifying a second terminal, wherein the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to a first terminal; determining that the second terminal has successfully logged into the target service if the first user identifier is successfully authenticated based on a pre-generated user identifier; and sending first successful login information to the second terminal, wherein the first successful login information includes the second mobile phone number.

[0009] Fourthly, this application discloses a login authentication method applied to a server corresponding to a target service, comprising: receiving a second user identifier and a second mobile phone number sent by a login authentication device, wherein the second user identifier is a user identifier determined by a second terminal based on historical login information corresponding to the target service, the second mobile phone number is a mobile phone number obtained by data anonymization processing of a first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to a first terminal; determining that the second terminal has successfully logged into the target service if the second user identifier is successfully authenticated based on the pre-obtained user identifier; and sending third successful login information to the second terminal, wherein the third successful login information includes the second user identifier and the second mobile phone number.

[0010] Fifthly, this application discloses a login authentication method applied to a first terminal, comprising: in response to target data obtained from a second terminal, generating first login information corresponding to a target service, wherein the target data carries a service name corresponding to the target service, a first user identifier for identifying the second terminal, and a service identifier corresponding to the target service, and the first login information includes the service name, the first user identifier, and the service identifier; in response to a received confirmation operation on the first login information, sending a first 5G message to a login authentication device, wherein the first 5G message is used to instruct the second terminal to request login to the target service, and the first 5G message carries the first user identifier and a first mobile phone number corresponding to the first terminal.

[0011] Sixthly, this application discloses a login authentication method applied to a first terminal, comprising: in response to a received second 5G message sent by a login authentication device, generating second login information corresponding to the second 5G message, wherein the second 5G message is used to inquire whether to log in to a target service corresponding to a service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message; in response to a received confirmation operation on the second login information, sending a target instruction to the login authentication device, wherein the target instruction carries the second message identifier.

[0012] In a seventh aspect, this application discloses a login authentication method applied to a second terminal, comprising: responding to a received first operation on a 5G message login control, sending a second 5G message login request to a server corresponding to a target service, wherein the 5G message login control corresponds to the target service, and the second 5G message login request is used to instruct the second terminal to request login to the target service; receiving a first user identifier sent by the server; generating target data based on the first user identifier and displaying it, wherein the target data carries a service name corresponding to the target service, the first user identifier, and a service identifier corresponding to the target service.

[0013] Eighthly, this application discloses a login authentication method applied to a second terminal, comprising: responding to a received second operation on a 5G message login control, determining a second user identifier based on historical login information corresponding to a target service, wherein the 5G message login control corresponds to the target service; and sending a first 5G message login request to a server corresponding to the target service, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

[0014] Ninthly, this application discloses a login authentication device, comprising: a first receiving module, configured to receive a first 5G message sent by a first terminal, wherein the first 5G message is configured to instruct a second terminal to request login to a target service, and the first 5G message carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal; a processing module, configured to obtain a second mobile phone number by performing data anonymization processing on the first mobile phone number; and a first sending module, configured to send the first user identifier and the second mobile phone number to a server corresponding to the target service for login authentication.

[0015] Tenthly, this application discloses a login authentication device, comprising: a second receiving module, configured to receive a first 5G message login request sent by a second terminal through a server corresponding to a target service, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries a second user identifier, the second user identifier being a user identifier determined by the second terminal based on historical login information corresponding to the target service; a first determining module, configured to determine a service identifier corresponding to the second user identifier and a first mobile phone number corresponding to the second user identifier based on the second user identifier, wherein the first mobile phone number is a mobile phone number corresponding to a first terminal; and a second sending module, configured to... The second receiving module is further configured to receive a target instruction sent by the first terminal in response to a received confirmation operation, wherein the target instruction carries a second message identifier; the second sending module is further configured to send the second user identifier and the second mobile phone number to the server for login authentication if the second message identifier is successfully authenticated based on the first message identifier, wherein the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number.

[0016] Eleventhly, this application discloses a login authentication device applied to a server corresponding to a target service, comprising: a third receiving module, configured to receive a first user identifier and a second mobile phone number sent by the login authentication device for identifying a second terminal, wherein the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to a first terminal; a second determining module, configured to determine that the second terminal has successfully logged into the target service if the first user identifier is successfully authenticated based on a pre-generated user identifier; and a third sending module, configured to send first successful login information to the second terminal, wherein the first successful login information includes the second mobile phone number.

[0017] In a twelfth aspect, this application discloses a login authentication device applied to a server corresponding to a target service, comprising: a fourth receiving module, configured to receive a second user identifier and a second mobile phone number sent by the login authentication device, wherein the second user identifier is a user identifier determined by a second terminal based on historical login information corresponding to the target service, and the second mobile phone number is a mobile phone number obtained by data anonymization processing of a first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to a first terminal; a third determining module, configured to determine that the second terminal has successfully logged into the target service if the second user identifier is authenticated successfully based on a pre-obtained user identifier; and a fourth sending module, configured to send third successful login information to the second terminal, wherein the third successful login information includes the second user identifier and the second mobile phone number.

[0018] In a thirteenth aspect, this application discloses a login authentication device applied to a first terminal, comprising: a third generation module, configured to generate first login information corresponding to a target service in response to target data obtained from a second terminal, wherein the target data carries a service name corresponding to the target service, a first user identifier for identifying the second terminal, and a service identifier corresponding to the target service, and the first login information includes the service name, the first user identifier, and the service identifier; and a fifth sending module, configured to send a first 5G message to the login authentication device in response to a received confirmation operation on the first login information, wherein the first 5G message is used to instruct the second terminal to request login to the target service, and the first 5G message carries the first user identifier and a first mobile phone number corresponding to the first terminal.

[0019] In a fourteenth aspect, this application discloses a login authentication device applied to a first terminal, comprising: a fourth generation module, configured to generate second login information corresponding to the second 5G message in response to a received second 5G message sent by the login authentication device, wherein the second 5G message is used to inquire whether to log in to a target service corresponding to a service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message; and a sixth sending module, configured to send a target instruction to the login authentication device in response to a received confirmation operation on the second login information, wherein the target instruction carries the second message identifier.

[0020] In a fifteenth aspect, embodiments of this application disclose a login authentication device applied to a second terminal, comprising: a seventh sending module, configured to, in response to a received first operation on a 5G message login control, send a second 5G message login request to a server corresponding to a target service, wherein the 5G message login control corresponds to the target service, and the second 5G message login request is used to instruct the second terminal to request login to the target service; a seventh receiving module, configured to receive a first user identifier sent by the server; and a fifth generating module, configured to, based on the first user identifier, generate target data and display it, wherein the target data carries a service name corresponding to the target service, the first user identifier, and a service identifier corresponding to the target service.

[0021] In a sixteenth aspect, embodiments of this application disclose a login authentication device applied to a second terminal, comprising: a fourth determining module, configured to determine a second user identifier based on historical login information corresponding to a target service in response to a received second operation on a 5G message login control, wherein the 5G message login control corresponds to the target service; and an eighth sending module, configured to send a first 5G message login request to a server corresponding to the target service, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

[0022] In a seventeenth aspect, embodiments of this application provide an electronic device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions being executed by the processor to implement the steps of the methods described in the first, second, third, fourth, fifth, sixth, seventh, or eighth aspects.

[0023] In an eighteenth aspect, embodiments of this application provide a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the methods described in the first, second, third, fourth, fifth, sixth, seventh, or eighth aspects.

[0024] In a nineteenth aspect, embodiments of this application provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the steps of the methods described in the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, sixth aspect, seventh aspect, or eighth aspect.

[0025] The technical solution adopted in this application can achieve the following beneficial effects:

[0026] This application provides a login authentication method. The login authentication device receives a first 5G message sent by a first terminal. The first 5G message is used to instruct a second terminal to request login to a target service. The first 5G message carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal. Then, the second mobile phone number is obtained by performing data anonymization processing on the first mobile phone number. The first user identifier and the second mobile phone number are sent to the server corresponding to the target service for login authentication. This method can avoid exposing the user's mobile phone number to a third party, thereby reducing security risks. Attached Figure Description

[0027] Figure 1 This is a flowchart illustrating the first login authentication method disclosed in the embodiments of this application;

[0028] Figure 2 This is a flowchart illustrating the second login authentication method disclosed in the embodiments of this application;

[0029] Figure 3 This is a flowchart illustrating the third login authentication method disclosed in the embodiments of this application;

[0030] Figure 4 This is a flowchart illustrating the fourth login authentication method disclosed in the embodiments of this application;

[0031] Figure 5 This is a flowchart illustrating the fifth login authentication method disclosed in the embodiments of this application;

[0032] Figure 6 This is a schematic diagram of the first type of first terminal display interface disclosed in the embodiments of this application;

[0033] Figure 7 This is a flowchart illustrating the sixth login authentication method disclosed in the embodiments of this application;

[0034] Figure 8 This is a schematic diagram of a second type of first terminal display interface disclosed in an embodiment of this application;

[0035] Figure 9 This is a flowchart illustrating the seventh login authentication method disclosed in the embodiments of this application;

[0036] Figure 10 This is a schematic diagram of the first type of second terminal display interface disclosed in the embodiments of this application;

[0037] Figure 11 This is a flowchart illustrating the eighth login authentication method disclosed in the embodiments of this application;

[0038] Figure 12This is a schematic diagram of a second type of second terminal display interface disclosed in an embodiment of this application;

[0039] Figure 13 This is a flowchart of the first login authentication system disclosed in the embodiments of this application;

[0040] Figure 14 This is a flowchart of the second login authentication system disclosed in the embodiments of this application;

[0041] Figure 15 This is a schematic diagram of the structure of the first login authentication device disclosed in the embodiments of this application;

[0042] Figure 16 This is a schematic diagram of the structure of the second login authentication device disclosed in the embodiments of this application;

[0043] Figure 17 This is a schematic diagram of the third login authentication device disclosed in the embodiments of this application;

[0044] Figure 18 This is a schematic diagram of the structure of the fourth login authentication device disclosed in the embodiments of this application;

[0045] Figure 19 This is a schematic diagram of the structure of the fifth login authentication device disclosed in the embodiments of this application;

[0046] Figure 20 This is a schematic diagram of the sixth login authentication device disclosed in the embodiments of this application;

[0047] Figure 21 This is a schematic diagram of the structure of the seventh login authentication device disclosed in the embodiments of this application;

[0048] Figure 22 This is a schematic diagram of the structure of the eighth login authentication device disclosed in the embodiments of this application;

[0049] Figure 23 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of this application. Detailed Implementation

[0050] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0051] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the electrically connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0052] The login authentication method, apparatus, electronic device, and readable storage medium disclosed in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0053] This application discloses a login authentication method, applied to a login authentication device. Figure 1 This is a flowchart illustrating the first login authentication method disclosed in an embodiment of this application. Figure 1 As shown, the method includes the following steps:

[0054] S120: Receive the first 5G message sent by the first terminal.

[0055] The first 5G message is used to instruct the second terminal to request login to the target service. The first 5G message carries a first user identifier (UUID) for identifying the second terminal and a first mobile phone number corresponding to the first terminal.

[0056] In this application, the first terminal can first send the first 5G message to the 5GMC (5G Message Center). After receiving the first 5G message, the 5GMC then sends the first 5G message to the login authentication device through the MaaP (Messaging as a Platform) platform.

[0057] It should be noted that the target business in this application can be a target application or an H5 page of a browser, and this application does not impose specific restrictions on it.

[0058] S140. The second mobile phone number is obtained by performing data anonymization processing on the first mobile phone number.

[0059] After receiving the first 5G message, the login authentication device can parse the first 5G message to obtain the first user identifier (UUID) for identifying the second terminal and the first mobile phone number corresponding to the first terminal. Then, by performing data anonymization processing on the first mobile phone number, the second mobile phone number can be obtained. For example, if the first mobile phone number is 12345678901, the second mobile phone number obtained after data anonymization processing can be 123****8901.

[0060] S160. Send the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication.

[0061] After obtaining the second mobile phone number by performing data anonymization processing on the first mobile phone number, the login authentication device sends the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication.

[0062] Because the solution adopted in this application sends the first user identifier UUID and the anonymized mobile phone number to the server corresponding to the target business for login authentication, it can avoid exposing the user's mobile phone number to third parties.

[0063] This application provides a login authentication method. The login authentication device receives a first 5G message sent by a first terminal. The first 5G message is used to instruct a second terminal to request login to a target service. The first 5G message carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal. Then, the second mobile phone number is obtained by performing data anonymization processing on the first mobile phone number. The first user identifier and the second mobile phone number are sent to the server corresponding to the target service for login authentication. This method can avoid exposing the user's mobile phone number to a third party, thereby reducing security risks.

[0064] In one implementation, the first 5G message further carries the service name of the target service and a service identifier corresponding to the target service. Before sending the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication, the method may further include: if the authentication of the service identifier and the service name is successful based on pre-set information, generating a second user identifier based on the first user identifier and the first mobile phone number; the step of sending the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication may include: sending the first user identifier, the second mobile phone number, and the second user identifier to the server corresponding to the target service for login authentication.

[0065] In this application, after receiving the first 5G message sent by the first terminal, the login authentication device parses the first 5G message to obtain the first user identifier UUID used to identify the second terminal, the first mobile phone number corresponding to the first terminal, the service name of the target service, and the service identifier corresponding to the target service. Based on the name and identifier of the service information registered in the authentication system on the login authentication device, it determines whether the correspondence between the service identifier and the service name is correct, and whether the service identifier and service name match the name and identifier of the service information registered in the authentication system on the login authentication device. If it is confirmed that they match and the correspondence is correct, the authentication of the service identifier and service name is successful. Based on the first user identifier UUID and the first mobile phone number, a second user identifier openID is generated and used as the ID provided externally. Then, the first user identifier UUID, the second mobile phone number, and the second user identifier openID are sent to the server corresponding to the target service for login authentication.

[0066] It should be noted that the login authentication device's database can record the association between the first mobile phone number and the second user identifier, representing the user's login and registration information. Additionally, the login authentication device's database can also record the service name of the target service, the service identifier corresponding to the target service, the first user identifier, the first mobile phone number, the second mobile phone number, and the correspondence between the second user identifier.

[0067] In one implementation, before sending the first user identifier, the second mobile phone number, and the second user identifier to the server corresponding to the target service for login authentication, the method may further include: generating a verification token based on the service identifier; the step of sending the first user identifier, the second mobile phone number, and the second user identifier to the server corresponding to the target service for login authentication includes: sending the first user identifier, the second mobile phone number, the second user identifier, and the verification token to the server corresponding to the target service for login authentication.

[0068] It should be noted that the verification token generated based on the business identifier can be a string of random numbers, and the verification token can have an expiration date.

[0069] In this application, the first user identifier UUID, the second mobile phone number, the second user identifier openID, and the verification token can be sent to the server corresponding to the target business for login authentication.

[0070] In this embodiment, the login authentication method described above can be a login authentication method for the first login of a second terminal to the target service.

[0071] This application discloses a login authentication method, applied to a login authentication device. Figure 2 This is a flowchart illustrating the second login authentication method disclosed in an embodiment of this application. Figure 2 As shown, the method includes the following steps:

[0072] S210: Receive the first 5G message login request sent by the second terminal through the server corresponding to the target service.

[0073] The first 5G message login request is used to instruct the second terminal to request login to the target service. The first 5G message login request carries a second user identifier openID, which is a user identifier determined by the second terminal based on historical login information corresponding to the target service.

[0074] In this application, the historical login information corresponding to the target service can be the most recent historical login information corresponding to the target service stored locally on the second terminal, that is, the first 5G message login request carries the user identifier of the most recent login to the target service on the second terminal.

[0075] S220. Based on the second user identifier, determine the service identifier corresponding to the second user identifier and the first mobile phone number corresponding to the second user identifier, wherein the first mobile phone number is the mobile phone number corresponding to the first terminal.

[0076] The login authentication device pre-stores the correspondence between user identifiers, service identifiers, and the first mobile phone number.

[0077] S230. Send a second 5G message to the first terminal, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message.

[0078] S240. Receive the target instruction sent by the first terminal in response to the received determination operation, wherein the target instruction carries a second message identifier.

[0079] That is, after the first terminal receives the operation that determines the second terminal to log in to the target service corresponding to the service identifier, it sends the target instruction to the login authentication device.

[0080] S250. If the authentication of the second message identifier based on the first message identifier is successful, the second user identifier and the second mobile phone number are sent to the server for login authentication, wherein the second mobile phone number is a mobile phone number obtained by performing data anonymization processing on the first mobile phone number.

[0081] It should be noted that if the second message identifier matches the first message identifier, the authentication is successful, and the second user identifier and the second mobile phone number are sent to the server for login authentication.

[0082] Because the solution adopted in this application sends the second user identifier and the de-identified mobile phone number to the server corresponding to the target business for login authentication, it can avoid exposing the user's mobile phone number to third parties.

[0083] This application provides a login authentication method. The login authentication device receives a first 5G message login request sent by a second terminal through a server corresponding to a target service. The first 5G message login request instructs the second terminal to request login to the target service. The first 5G message login request carries a second user identifier, which is a user identifier determined by the second terminal based on historical login information corresponding to the target service. Then, based on the second user identifier, a service identifier corresponding to the second user identifier and a first mobile phone number corresponding to the second user identifier are determined. This first mobile phone number is the mobile phone number corresponding to the first terminal. A second 5G message is sent to the first terminal, which inquires whether to log in to the target service corresponding to the service identifier on the second terminal. The second 5G message carries a first message identifier. Then, the login authentication device receives a target instruction sent by the first terminal in response to a received confirmation operation. This target instruction carries the second message identifier. If the login authentication device successfully authenticates the second message identifier based on the first message identifier, it sends the second user identifier and the second mobile phone number obtained by data anonymization of the first mobile phone number to the server for login authentication. This avoids exposing the user's mobile phone number to a third party, thereby reducing security risks.

[0084] In this embodiment, the login authentication method described above can be a login authentication method for situations where the second terminal is not logging into the target service for the first time.

[0085] This application discloses a login authentication method, applied to a server corresponding to a target business. Figure 3 This is a flowchart illustrating the third login authentication method disclosed in the embodiments of this application. Figure 3 As shown, the method includes the following steps:

[0086] S320: Receives a first user identifier and a second mobile phone number sent by the login authentication device to identify the second terminal.

[0087] The second mobile phone number is obtained by de-identifying the first mobile phone number, and the first mobile phone number is the mobile phone number corresponding to the first terminal.

[0088] S340. If the authentication of the first user identifier based on the pre-generated user identifier is successful, it is determined that the second terminal has successfully logged into the target service.

[0089] It should be noted that the pre-generated user identifier here is the user identifier generated by the server after receiving the second 5G message login request sent by the second terminal. The second 5G message login request is used to instruct the second terminal to request login to the target service.

[0090] If the first user identifier matches the pre-generated user identifier, the first user identifier is authenticated, the server determines that the second terminal has successfully logged into the target service, and records the second mobile phone number.

[0091] S360. Send first successful login information to the second terminal, wherein the first successful login information includes the second mobile phone number.

[0092] After receiving the first successful login information from the server, the second terminal is redirected to the page indicating successful login.

[0093] This application provides a login authentication method. By receiving a first user identifier and a second mobile phone number sent by a login authentication device from a server corresponding to the target service, and if the first user identifier is successfully authenticated based on the pre-generated user identifier, it is determined that the second terminal has successfully logged into the target service. First successful login information including the second mobile phone number is then sent to the second terminal. This method can avoid exposing the user's mobile phone number to a third party, thereby reducing security risks.

[0094] In one implementation, receiving the first user identifier and second mobile phone number sent by the login authentication device for identifying the second terminal may include: receiving the first user identifier, second mobile phone number, and second user identifier sent by the login authentication device for identifying the second terminal, wherein the second user identifier is a user identifier generated by the login authentication device based on the first user identifier and the first mobile phone number, and the first successful login information also includes the second user identifier. If the first user identifier matches a pre-generated user identifier, authentication of the first user identifier is successful, the server determines that the second terminal has successfully logged into the target service, records the second mobile phone number and the second user identifier, uses the second user identifier as the ID of the logged-in user, and the server sends first successful login information including the second mobile phone number and the second user identifier to the second terminal.

[0095] In one implementation, receiving the first user identifier, second mobile phone number, and second user identifier sent by the login authentication device for identifying the second terminal may include: receiving the first user identifier, second mobile phone number, second user identifier, and verification token sent by the login authentication device for identifying the second terminal, wherein the verification token is generated by the login authentication device based on a service identifier corresponding to the target service. If the first user identifier matches a pre-generated user identifier, authentication of the first user identifier is successful. The server determines that the second terminal has successfully logged into the target service, records the second mobile phone number, second user identifier, and verification token, uses the second user identifier as the logged-in user's ID, and sends first successful login information including the second mobile phone number and second user identifier to the second terminal.

[0096] In this embodiment of the application, before receiving the first user identifier and the second mobile phone number sent by the login authentication device for identifying the second terminal, the method may further include: receiving a second 5G message login request sent by the second terminal, wherein the second 5G message login request is used to instruct the second terminal to request login to the target service; and in response to the second 5G message login request, generating a first user identifier and sending it to the second terminal.

[0097] In one implementation, after determining that the second terminal has successfully logged into the target service, the process may further include: sending second successful login information to the first terminal through the login authentication device, wherein the second successful login information includes the service name of the target service. That is, the server also sends the second successful login information to the first terminal through the login authentication device to notify the first terminal that the second terminal has successfully logged into the target service. For example, the second successful login information could be "Congratulations, you have successfully logged in to <service application name>. You can switch back to the original page or click the login button."

[0098] In this embodiment, the login authentication method described above can be a login authentication method for the first login of a second terminal to the target service.

[0099] This application discloses a login authentication method, applied to a server corresponding to a target business. Figure 4 This is a flowchart illustrating the fourth login authentication method disclosed in the embodiments of this application. Figure 4 As shown, the method includes the following steps:

[0100] S420 receives the second user identifier and second mobile phone number sent by the login authentication device.

[0101] Wherein, the second user identifier is a user identifier determined by the second terminal based on historical login information corresponding to the target service, the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal.

[0102] S440. If the second user identifier is successfully authenticated based on the pre-obtained user identifier, it is determined that the second terminal has successfully logged into the target service.

[0103] If the second user identifier matches the pre-acquired user identifier, the second user identifier is authenticated and the server determines that the second terminal has successfully logged into the target service, and records the second user identifier and the second mobile phone number.

[0104] It should be noted that the user identifier obtained in advance here can be the second user identifier carried in the first 5G message login request received.

[0105] S460. Send a third successful login message to the second terminal, wherein the third successful login message includes the second user identifier and the second mobile phone number.

[0106] After receiving the third successful login information from the server, the second terminal is redirected to the page indicating successful login.

[0107] This application provides a login authentication method. A server corresponding to a target service receives a second user identifier and a second mobile phone number sent by a login authentication device. The second user identifier is a user identifier determined by a second terminal based on historical login information corresponding to the target service. The second mobile phone number is a mobile phone number obtained by de-identifying a first mobile phone number. The first mobile phone number is a mobile phone number corresponding to a first terminal. If the server successfully authenticates the second user identifier based on the pre-obtained user identifier, it determines that the second terminal has successfully logged into the target service and sends third successful login information including the second user identifier and the second mobile phone number to the second terminal. This method can avoid exposing the user's mobile phone number to a third party, thereby reducing security risks.

[0108] In this embodiment of the application, before receiving the second user identifier and the second mobile phone number sent by the login authentication device, the method may further include: receiving a first 5G message login request sent by the second terminal, and sending the first 5G message login request to the login authentication device, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

[0109] In this embodiment of the application, after determining that the second terminal has successfully logged into the target service, the process may further include: sending second successful login information to the first terminal through the login authentication device, wherein the second successful login information includes the service name of the target service. That is, the server also notifies the first terminal that the second terminal has successfully logged into the target service by sending the second successful login information to the first terminal through the login authentication device.

[0110] In this embodiment, the login authentication method described above can be a login authentication method for situations where the second terminal is not logging into the target service for the first time.

[0111] This application discloses a login authentication method applied to a first terminal. Figure 5 This is a flowchart illustrating the fifth login authentication method disclosed in the embodiments of this application. Figure 5 As shown, the method includes the following steps:

[0112] S520: In response to the target data obtained from the second terminal, generate the first login information corresponding to the target service.

[0113] In one implementation, in response to target data obtained from a second terminal, first login information corresponding to the target service is generated on the target chatbot page of the 5G message.

[0114] The target data carries a chatbot identifier, a business name corresponding to the target business, a first user identifier for identifying the second terminal, and a business identifier corresponding to the target business. The target chatbot is the chatbot corresponding to the chatbot identifier. The first login information includes the business name, the first user identifier, and the business identifier.

[0115] In this application, the first terminal is a terminal that supports 5G messaging.

[0116] For example, the first login information generated by the first terminal on the 5G messaging page, corresponding to the target service, can be as follows: Figure 6 As shown, Figure 6 In the context of "XX application," the application name is the business name, "iufad7" is the first user identifier, and "fkj32aij349p8" is the business identifier. Additionally, the first login information may include controls, which can be, for example... Figure 6 The "Send" control shown can also be a floating button named "Auto Login <Business Name>".

[0117] S540. In response to the received confirmation operation of the first login information, send a first 5G message to the login authentication device.

[0118] The first 5G message is used to instruct the second terminal to request login to the target service. The first 5G message carries the first user identifier and the first mobile phone number corresponding to the first terminal. Additionally, the first 5G message may also carry the service name of the target service and the service identifier corresponding to the target service.

[0119] For example, the operation of determining the first login information can be performed on... Figure 6 The click operation of the "Send" control in the text.

[0120] This application provides a login authentication method. A first terminal, in response to target data obtained from a second terminal, generates first login information corresponding to a target service. Upon receiving a confirmation operation on the first login information, the first terminal sends a first 5G message to a login authentication device. The first 5G message instructs the second terminal to request login to the target service. The first 5G message carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal. The login authentication device obtains a second mobile phone number after data anonymization of the first mobile phone number and sends the first user identifier and the second mobile phone number to a server corresponding to the target service for login authentication. This method avoids exposing the user's mobile phone number to third parties, thereby reducing security risks.

[0121] In one implementation, after sending the first 5G message to the login authentication device, the method may further include: receiving and displaying second successful login information sent by the server corresponding to the target service through the login authentication device, wherein the second successful login information includes the service name, thereby prompting the user corresponding to the first terminal to successfully log in to the target service via the second terminal.

[0122] In this embodiment, the login authentication method described above can be a login authentication method for the first login of a second terminal to the target service.

[0123] This application discloses a login authentication method applied to a first terminal. Figure 7 This is a flowchart illustrating the sixth login authentication method disclosed in the embodiments of this application. Figure 7 As shown, the method includes the following steps:

[0124] S720: In response to the second 5G message sent by the login authentication device, generate second login information corresponding to the second 5G message.

[0125] The second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message.

[0126] For example, in response to the second 5G message sent by the login authentication device, second login information corresponding to the second 5G message is generated on the target chatbot page of the 5G message.

[0127] For example, the second login information generated on the target chatbot page of the 5G message, corresponding to the second 5G message, can be as follows: Figure 8 As shown, the second login information can be presented in the form of a message card, and the second login information can also include a "Click to Log In" control.

[0128] S740. In response to the received confirmation operation of the second login information, a target instruction is sent to the login authentication device, wherein the target instruction carries a second message identifier.

[0129] For example, the operation of determining the second login information can be performed on... Figure 8 Clicking the "Click to Log In" control in the middle.

[0130] This application provides a login authentication method. A first terminal, in response to a received second 5G message from a login authentication device, generates second login information corresponding to the second 5G message. The second 5G message inquires whether to log in to a target service corresponding to a service identifier on the second terminal. The second 5G message carries a first message identifier corresponding to the second 5G message. In response to a received confirmation operation on the second login information, the first terminal sends a target instruction to the login authentication device. This target instruction carries the second message identifier. If the login authentication device successfully authenticates the second message identifier based on the first message identifier, it sends a second user identifier and a second mobile phone number to a server for login authentication. This method avoids exposing the user's mobile phone number to third parties, thereby reducing security risks.

[0131] In one implementation, after sending the target instruction to the login authentication device, the method may further include: receiving and displaying second successful login information sent by the server corresponding to the target service through the login authentication device, wherein the second successful login information includes the service name of the target service, thereby prompting the user corresponding to the first terminal to successfully log in to the target service via the second terminal.

[0132] In this embodiment, the login authentication method described above can be a login authentication method for situations where the second terminal is not logging into the target service for the first time.

[0133] This application discloses a login authentication method applied to a second terminal. Figure 9 This is a flowchart illustrating the seventh login authentication method disclosed in the embodiments of this application. Figure 9 As shown, the method includes the following steps:

[0134] S920. In response to the received first operation on the 5G message login control, a second 5G message login request is sent to the server corresponding to the target service, wherein the 5G message login control corresponds to the target service, and the second 5G message login request is used to instruct the second terminal to request login to the target service.

[0135] In this application, the first operation on the 5G message login control can be a click operation on the 5G message login control.

[0136] S940, Receive the first user identifier sent by the server.

[0137] S960. Based on the first user identifier, generate target data and display it, wherein the target data carries a service name corresponding to the target service, the first user identifier, and a service identifier corresponding to the target service. The target data may also carry a chatbot identifier.

[0138] In this application, a corresponding deeplink can be assembled based on the first user identifier, a pre-configured chatbot identifier, the business name of the target business, and the business identifier corresponding to the target business. The deeplink format is sms:XX%40botplatform.rcs.chinamobile.com?body=YY, where XX represents the chatbot identifier and YY represents the URL (Uniform Resource Locator) encoding of "automatic login <business name>, automatic authentication code is <first user identifier & business identifier>". After obtaining the deeplink, a QR code is generated based on the deeplink and displayed as target data, such as... Figure 10 As shown.

[0139] It should be noted that the authentication code in this application is similar to the verification code in the prior art.

[0140] This application provides a login authentication method. A second terminal, in response to a received first operation on a 5G message login control, sends a second 5G message login request to a server corresponding to a target service. The 5G message login control corresponds to the target service, and the second 5G message login request instructs the second terminal to request login to the target service. The second terminal receives a first user identifier sent by the server, generates and displays target data based on the first user identifier, and generates first login information corresponding to the target service based on the target data obtained from the second terminal. In response to a received confirmation operation on the first login information, the first terminal sends a first 5G message to a login authentication device. The first 5G message instructs the second terminal to request login to the target service and carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal. The login authentication device obtains a second mobile phone number after data anonymization of the first mobile phone number and sends the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication. This method avoids exposing the user's mobile phone number to a third party, thereby reducing security risks.

[0141] In this embodiment of the application, after generating and displaying the target data, the method may further include: receiving first successful login information sent by the server, wherein the first successful login information includes a second mobile phone number, the second mobile phone number is a mobile phone number obtained by performing data anonymization processing on the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal; in response to receiving the first successful login information, displaying a page after the target service has been successfully logged in.

[0142] In one implementation, the first successful login information may further include a second user identifier, wherein the second user identifier is a user identifier generated by the login authentication device based on the first user identifier and the first mobile phone number.

[0143] In this embodiment, the login authentication method described above can be a login authentication method for the first login of a second terminal to the target service.

[0144] This application discloses a login authentication method applied to a second terminal. Figure 11 This is a flowchart illustrating the eighth login authentication method disclosed in the embodiments of this application. Figure 11 As shown, the method includes the following steps:

[0145] S1120. In response to the received second operation on the 5G message login control, determine a second user identifier based on historical login information corresponding to the target service, wherein the 5G message login control corresponds to the target service.

[0146] For example, the 5G message login control can be as follows: Figure 12 The "5G Message Login" control shown can be used by the second terminal to obtain the device's historical login information corresponding to the target service in the last time when the second terminal receives a click operation on the "5G Message Login" control, and then parse it to obtain the second user identifier.

[0147] S1140. Send a first 5G message login request to the server corresponding to the target service, wherein the first 5G message login request is used to instruct the second terminal to request to log in to the target service, and the first 5G message login request carries the second user identifier.

[0148] This application provides a login authentication method. A second terminal, in response to a received second operation on a 5G message login control, determines a second user identifier based on historical login information corresponding to a target service. This 5G message login control corresponds to the target service. Then, it sends a first 5G message login request to a server corresponding to the target service. This first 5G message login request instructs the second terminal to request login to the target service. The first 5G message login request carries the second user identifier. The server sends the first 5G message login request to a login authentication device. Based on the second user identifier, the login authentication device determines a service identifier corresponding to the second user identifier and a first mobile phone number corresponding to the second user identifier. This first mobile phone number is... The mobile phone number corresponding to the first terminal sends a second 5G message to the first terminal. This second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal. The second 5G message carries a first message identifier corresponding to the second 5G message. Then, the login authentication device receives the target instruction sent by the first terminal in response to the received confirmation operation. This target instruction carries the second message identifier. If the login authentication device successfully authenticates the second message identifier based on the first message identifier, it sends the second user identifier and the second mobile phone number obtained by data anonymization processing of the first mobile phone number to the server for login authentication. This can avoid exposing the user's mobile phone number to a third party, thereby reducing security risks.

[0149] In one implementation, after sending the first 5G message login request to the server corresponding to the target service, the method may further include: receiving third successful login information sent by the server, wherein the third successful login information includes the second user identifier and the second mobile phone number, the second mobile phone number being a mobile phone number obtained by data anonymization processing of the first mobile phone number, and the first mobile phone number being a mobile phone number corresponding to the first terminal; and in response to the received third successful login information, displaying a page showing the successful login to the target service.

[0150] In this embodiment, the login authentication method described above can be a login authentication method for situations where the second terminal is not logging into the target service for the first time.

[0151] It should be noted that the first terminal mentioned in this application can be a mobile phone, and the second terminal can be a computer, tablet, mobile phone, etc. This application does not impose specific restrictions on this.

[0152] This application discloses a login authentication system, including a login authentication device, a server corresponding to the target service, a first terminal, a second terminal, a MaaP, and a 5GMC.

[0153] When the second terminal is the first time logging into the target service, such as Figure 13 As shown, the execution flow of the login authentication system is as follows:

[0154] S1-S3: The second terminal receives the 5G message login selected by the user in the target service (application login interface or browser H5 login page), switches to the third-party login page, and sends a second 5G message login request to the server corresponding to the target service, and maintains a long connection for the request. The second 5G message login request is used to instruct the second terminal to request login to the target service.

[0155] It should be noted that the second 5G message login request can be an HTTP login request.

[0156] S4: After receiving the second 5G message login request sent by the second terminal, the server generates a random first user identifier (UUID), saves it, and sends it to the second terminal.

[0157] S5: The second terminal assembles the corresponding deeplink based on the first user identifier UUID, the pre-configured chatbot identifier chatbotId, the target service's name, and the corresponding service identifier. After obtaining the deeplink, it generates a QR code based on the deeplink and displays it as target data, such as... Figure 10 As shown.

[0158] The deeplink format is sms:XX%40botplatform.rcs.chinamobile.com?body=YY, where XX represents the chatbot identifier chatbotId, and YY represents the URL encoding of "automatic login <business name>, automatic authentication code is <first user identifier & business identifier>".

[0159] S6: The first terminal receives the user's operation to open the 5G messaging application, and the first terminal scans the QR code displayed on the second terminal.

[0160] S7-S8: After the 5G messaging application parses the QR code content as a deeplink, it jumps to the Chatbot corresponding to the chatbotId and generates the first login information corresponding to the target service.

[0161] The first login information includes the service name, the first user identifier, and the service identifier, for example, such as... Figure 6 As shown, the first login information can be "Automatic login <business name>, automatic login authentication code is <first user identifier & business identifier>" and a "send" control, or the first login information can be a floating button named "Automatic login <business name>".

[0162] S9-S11: The first terminal receives the user's click operation on the "send" control or the floating button, and the first terminal sends the first 5G message to the 5GMC. After receiving the first 5G message, the 5GMC forwards the first 5G message to the MaaP platform.

[0163] The first 5G message carries the first user identifier, the first mobile phone number corresponding to the first terminal, the service name of the target service, and the service identifier corresponding to the target service.

[0164] S12: After the MaaP platform identifies the chatbot as the authentication login chatbot based on the chatbotId of the first 5G message from the uplink, it forwards the first 5G message to the login authentication device.

[0165] S13-S14: After receiving the first 5G message, the login authentication device parses the first 5G message and extracts the first user identifier (UUID), the first mobile phone number corresponding to the first terminal, the service name of the target service, and the service identifier corresponding to the target service according to the prescribed format. Based on the name and identifier of the service information registered in the authentication system on the login authentication device, it determines whether the correspondence between the service identifier and the service name is correct, and whether the service identifier and service name match the name and identifier of the service information registered in the authentication system on the login authentication device. If they match and the correspondence is correct, the authentication of the service identifier and service name is successful. Based on the first user identifier (UUID) and the first mobile phone number, a second user identifier (openID) is generated and used as the ID provided externally. Furthermore, the database of the login authentication device can record the association between the first mobile phone number and the second user identifier, representing the user's login registration information. Simultaneously, the login authentication device can also generate a verification token with a validity period based on the service identifier.

[0166] S15: The login authentication device sends the first user identifier UUID, the second mobile phone number obtained after de-identifying the first mobile phone number, the second user identifier openID, and the verification token to the server for login authentication.

[0167] S16: The server authenticates the first user identifier sent in S15 based on the first user identifier generated in S4. If they match, the server determines that the second terminal has successfully logged into the target service, records the second mobile phone number, the second user identifier, and the verification token, and uses the second user identifier as the ID of the logged-in user.

[0168] S17-S18: The server sends first successful login information to the second terminal via the long-lived connection. This first successful login information includes the second mobile phone number and the second user identifier. Upon receiving the first successful login information, the second terminal automatically redirects to the page indicating successful login.

[0169] S19-S22: The server sends a second successful login message to the first terminal through the login authentication device. This second successful login message includes the service name of the target service. For example, the second successful login message could be "Congratulations, you have successfully logged in <service name>. You can switch back to the original page or click the login button." Furthermore, the second successful login message may also include a deeplink for the target service. This deeplink information needs to be pre-registered and stored in the login authentication device. Additionally, the deeplink may carry the verification token mentioned above.

[0170] A deeplink can be an HTTP page or a third-party application, for example:

[0171] The page's deeplink: https: / / www.baidu.com?token=XXX

[0172] Deep link for third-party applications: weixin: / / XXX?token=XXX

[0173] S23: After the first terminal receives the second successful login information sent by the login authentication device via 5G message, it displays it to the user. The displayed content may also include a button to open the login success page.

[0174] If the second terminal is not the first time logging into the target service, such as Figure 14 As shown, the execution flow of the login authentication system is as follows:

[0175] S1-S3: The second terminal receives the 5G message login selected by the user in the target service (application login interface or browser H5 login page), obtains the device's local historical login information from the last time, parses it to obtain the second user identifier, and then sends the first 5G message login request to the server. The first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

[0176] S4: After receiving the first 5G message login request sent by the second terminal, the server sends the first 5G message login request to the login authentication device.

[0177] S5: The login authentication device determines the service identifier and the first mobile phone number corresponding to the second user identifier based on the second user identifier carried in the first 5G message login request.

[0178] S6-S8: The login authentication device sends a second 5G message to the first terminal. The second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal. The second 5G message carries a first message identifier corresponding to the second 5G message.

[0179] S9-S10: The first terminal receives the second 5G message, displays a notification pop-up, and, as follows: Figure 8 As shown, in the Chatbot corresponding to chatbotId, a second login information corresponding to the second 5G message is generated. The second login information also includes a "Click to Log In" control.

[0180] S11-S14: The first terminal receives the user's click operation on the "Click to Login" control. The first terminal sequentially sends the target instruction to the login authentication device through the 5GMC and MaaP platforms. The target instruction carries a second message identifier.

[0181] S15-S16: The login authentication device receives the target instruction, obtains the second message identifier by parsing the target instruction, authenticates the second message identifier based on the first message identifier in S8, and if a match is found, queries the second user identifier and the second mobile phone number corresponding to the first message identifier, and sends the second user identifier and the second mobile phone number to the server for login authentication.

[0182] S17: The server authenticates the second user identifier sent in S16 based on the second user identifier obtained in S4. If they match, the server determines that the second terminal has successfully logged into the target service and records the second mobile phone number and the second user identifier.

[0183] S18-S19: The server sends a third successful login message to the second terminal. This message includes the second mobile phone number and the second user identifier. Upon receiving the third successful login message, the second terminal automatically redirects to the page indicating successful login.

[0184] S20-S23: The server sends a second successful login message to the first terminal through the login authentication device. This second successful login message includes the service name of the target service. For example, the second successful login message could be "Congratulations, you have successfully logged in <service name>. You can switch back to the original page or click the login button." Furthermore, the second successful login message may also include the deeplink of the target service. This deeplink information needs to be pre-registered and stored in the login authentication device. Additionally, the deeplink may carry the verification token mentioned above.

[0185] A deeplink can be an HTTP page or a third-party application, for example:

[0186] The page's deeplink: https: / / www.baidu.com?token=XXX

[0187] Deep link for third-party applications: weixin: / / XXX?token=XXX

[0188] S24: After the first terminal receives the second successful login information sent by the login authentication device via 5G message, it displays it to the user. The displayed content may also include a button to open the login success page.

[0189] The solution disclosed in this application uses 5G messaging for login authentication, which does not require authorization from third-party applications and can perform login authentication in either Wi-Fi or mobile network environments, thus having a wide range of applications.

[0190] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0191] Figure 15 This is a schematic diagram of the structure of the first login authentication device disclosed in the embodiments of this application. Figure 15 As shown, the login authentication device 1500 includes: a first receiving module 1510, a processing module 1520, and a first sending module 1530.

[0192] In this application, the first receiving module 1510 is used to receive a first 5G message sent by a first terminal, wherein the first 5G message is used to instruct a second terminal to request login to a target service, and the first 5G message carries a first user identifier for identifying the second terminal and a first mobile phone number corresponding to the first terminal; the processing module 1520 is used to obtain a second mobile phone number by performing data anonymization processing on the first mobile phone number; and the first sending module 1530 is used to send the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication.

[0193] In one implementation, the first 5G message further carries the service name of the target service and a service identifier corresponding to the target service. The device further includes: a first generation module, configured to generate a second user identifier based on the first user identifier and the first mobile phone number, provided that the authentication of the service identifier and the service name based on pre-set information is successful before sending the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication; the first sending module 1530 sending the first user identifier and the second mobile phone number to the server corresponding to the target service for login authentication includes: sending the first user identifier, the second mobile phone number, and the second user identifier to the server corresponding to the target service for login authentication.

[0194] In one implementation, the first generating module is further configured to generate a verification token based on the service identifier before sending the first user identifier, the second mobile phone number, and the second user identifier to the server corresponding to the target service for login authentication; the first sending module 1530 sending the first user identifier, the second mobile phone number, and the second user identifier to the server corresponding to the target service for login authentication includes: sending the first user identifier, the second mobile phone number, the second user identifier, and the verification token to the server corresponding to the target service for login authentication.

[0195] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0196] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0197] Figure 16 This is a schematic diagram of the structure of the second login authentication device disclosed in the embodiments of this application. Figure 16As shown, the login authentication device 1600 includes: a second receiving module 1610, a first determining module 1620, and a second sending module 1630.

[0198] In this application, the second receiving module 1610 is configured to receive a first 5G message login request sent by the second terminal through a server corresponding to the target service, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries a second user identifier, the second user identifier being a user identifier determined by the second terminal based on historical login information corresponding to the target service; the first determining module 1620 is configured to determine a service identifier corresponding to the second user identifier and a first mobile phone number corresponding to the second user identifier based on the second user identifier, wherein the first mobile phone number is a mobile phone number corresponding to the first terminal; the second sending module 1630 is configured to send to the first terminal The second 5G message is sent, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message; the second receiving module 1610 is further used to receive a target instruction sent by the first terminal in response to the received confirmation operation, wherein the target instruction carries a second message identifier; the second sending module 1630 is further used to send the second user identifier and the second mobile phone number to the server for login authentication if the second message identifier is authenticated based on the first message identifier, wherein the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number.

[0199] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0200] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0201] Figure 17 This is a schematic diagram of the third login authentication device disclosed in the embodiments of this application. Figure 17 As shown, the login authentication device 1700 includes: a third receiving module 1710, a second determining module 1720, and a third sending module 1730. This device is applied to a server corresponding to the target service.

[0202] In this application, the third receiving module 1710 is used to receive a first user identifier and a second mobile phone number sent by the login authentication device for identifying the second terminal, wherein the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal; the second determining module 1720 is used to determine that the second terminal has successfully logged into the target service if the authentication of the first user identifier based on the pre-generated user identifier is successful; the third sending module 1730 is used to send first successful login information to the second terminal, wherein the first successful login information includes the second mobile phone number.

[0203] In one implementation, the third receiving module 1710 receives a first user identifier and a second mobile phone number sent by the login authentication device for identifying the second terminal, including: receiving the first user identifier, the second mobile phone number and the second user identifier sent by the login authentication device for identifying the second terminal, wherein the second user identifier is a user identifier generated by the login authentication device based on the first user identifier and the first mobile phone number, and the first successful login information also includes the second user identifier.

[0204] In one implementation, the above apparatus further includes: the third receiving module 1710, which is further configured to receive a second 5G message login request sent by the second terminal before receiving the first user identifier and the second mobile phone number sent by the login authentication device for identifying the second terminal, wherein the second 5G message login request is used to instruct the second terminal to request login to the target service; and a second generating module, which is configured to generate a first user identifier and send it to the second terminal in response to the second 5G message login request.

[0205] In one implementation, the third sending module 1730 is further configured to send second successful login information to the first terminal through the login authentication device after determining that the second terminal has successfully logged into the target service, wherein the second successful login information includes the service name of the target service.

[0206] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0207] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0208] Figure 18 This is a schematic diagram of the structure of the fourth login authentication device disclosed in the embodiments of this application. Figure 18As shown, the login authentication device 1800 includes: a fourth receiving module 1810, a third determining module 1820, and a fourth sending module 1830. This device is applied to a server corresponding to the target service.

[0209] In this application, the fourth receiving module 1810 is used to receive a second user identifier and a second mobile phone number sent by the login authentication device, wherein the second user identifier is a user identifier determined by the second terminal based on historical login information corresponding to the target service, and the second mobile phone number is a mobile phone number obtained by data anonymization processing of the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal; the third determining module 1820 is used to determine that the second terminal has successfully logged into the target service if the second user identifier is successfully authenticated based on the pre-acquired user identifier; the fourth sending module 1830 is used to send third successful login information to the second terminal, wherein the third successful login information includes the second user identifier and the second mobile phone number.

[0210] In one implementation, the fourth receiving module 1810 is further configured to receive a first 5G message login request sent by the second terminal before receiving the second user identifier and the second mobile phone number sent by the login authentication device, and send the first 5G message login request to the login authentication device, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

[0211] In one implementation, the fourth sending module 1830 is further configured to send second successful login information to the first terminal through the login authentication device after determining that the second terminal has successfully logged into the target service, wherein the second successful login information includes the service name of the target service.

[0212] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0213] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0214] Figure 19 This is a schematic diagram of the structure of the fifth login authentication device disclosed in the embodiments of this application. Figure 19 As shown, the login authentication device 1900 includes a third generation module 1910 and a fifth sending module 1920. This device is used in the first terminal.

[0215] In this application, the third generation module 1910 is used to generate first login information corresponding to a target service in response to target data obtained from the second terminal. The target data carries a service name corresponding to the target service, a first user identifier for identifying the second terminal, and a service identifier corresponding to the target service. The first login information includes the service name, the first user identifier, and the service identifier. The fifth sending module 1920 is used to send a first 5G message to the login authentication device in response to a received confirmation operation on the first login information. The first 5G message instructs the second terminal to request login to the target service. The first 5G message carries the first user identifier and a first mobile phone number corresponding to the first terminal.

[0216] In one implementation, the device further includes a fifth receiving module, configured to receive and display second successful login information sent by a server corresponding to the target service through the login authentication device after the first 5G message is sent to the login authentication device, wherein the second successful login information includes the service name.

[0217] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0218] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0219] Figure 20 This is a schematic diagram of the sixth login authentication device disclosed in the embodiments of this application. Figure 20 As shown, the login authentication device 2000 includes a fourth generation module 2010 and a sixth sending module 2020. This device is used in the first terminal.

[0220] In this application, the fourth generation module 2010 is used to generate second login information corresponding to the second 5G message in response to the received second 5G message sent by the login authentication device, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message; the sixth sending module 2020 is used to send a target instruction to the login authentication device in response to the received confirmation operation of the second login information, wherein the target instruction carries a second message identifier.

[0221] In one implementation, the apparatus further includes a sixth receiving module, configured to receive and display second successful login information sent by a server corresponding to the target service through the login authentication device after the target instruction is sent to the login authentication device, wherein the second successful login information includes the service name of the target service.

[0222] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0223] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0224] Figure 21 This is a schematic diagram of the structure of the seventh login authentication device disclosed in the embodiments of this application. Figure 21 As shown, the login authentication device 2100 includes a seventh sending module 2110, a seventh receiving module 2120, and a fifth generating module 2130. This device is used in a second terminal.

[0225] In this application, the seventh sending module 2110 is used to send a second 5G message login request to a server corresponding to the target service in response to a received first operation on the 5G message login control, wherein the 5G message login control corresponds to the target service, and the second 5G message login request is used to instruct the second terminal to request login to the target service; the seventh receiving module 2120 receives a first user identifier sent by the server; and the fifth generating module 2130 is used to generate target data based on the first user identifier and display it, wherein the target data carries a service name corresponding to the target service, the first user identifier, and a service identifier corresponding to the target service.

[0226] In one implementation, the apparatus further includes: the seventh receiving module 2120, which is further configured to receive first successful login information sent by the server after the target data is generated and displayed, wherein the first successful login information includes a second mobile phone number, the second mobile phone number is a mobile phone number obtained by performing data anonymization processing on the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal; and a first display module, which is configured to display a page after the target service login is successful in response to the received first successful login information.

[0227] In one implementation, the first successful login information further includes a second user identifier, wherein the second user identifier is a user identifier generated by the login authentication device based on the first user identifier and the first mobile phone number.

[0228] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0229] The login authentication method provided in this application can be executed by a login authentication device. This application uses the example of a login authentication device executing the login authentication method to illustrate the login authentication device provided in this application.

[0230] Figure 22 This is a schematic diagram of the structure of the eighth login authentication device disclosed in the embodiments of this application. Figure 22 As shown, the login authentication device 2200 includes a fourth determining module 2210 and an eighth sending module 2220. This device is used in a second terminal.

[0231] In this application, the fourth determining module 2210 is used to determine a second user identifier based on historical login information corresponding to the target service in response to a received second operation on the 5G message login control, wherein the 5G message login control corresponds to the target service; the eighth sending module 2220 is used to send a first 5G message login request to the server corresponding to the target service, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

[0232] In one implementation, the apparatus further includes: an eighth receiving module, configured to receive third successful login information sent by the server after sending a first 5G message login request to the server corresponding to the target service, wherein the third successful login information includes a second user identifier and a second mobile phone number, the second mobile phone number being a mobile phone number obtained by data anonymization processing of a first mobile phone number, and the first mobile phone number being a mobile phone number corresponding to a first terminal; and a second display module, configured to display a page after successful login to the target service in response to the received third successful login information.

[0233] The login authentication device provided in this application embodiment can implement all the processes implemented in the login authentication method embodiment, and will not be described again here to avoid repetition.

[0234] Optionally, such as Figure 23As shown, this application embodiment also provides an electronic device 2300, including a processor 2301 and a memory 2302. The memory 2302 stores a program or instructions that can run on the processor 2301. When the program or instructions are executed by the processor 2301, they implement the various steps of the above-described login authentication method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0235] It should be noted that the electronic devices in the embodiments of this application include mobile electronic devices and non-mobile electronic devices.

[0236] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described login authentication method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0237] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0238] This application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions that, when executed by a computer, cause the computer to perform the steps of the login authentication method described above.

[0239] The above embodiments of this application focus on describing the differences between the various embodiments. As long as the different optimization features between the various embodiments are not contradictory, they can be combined to form a better embodiment. For the sake of brevity, they will not be described in detail here.

[0240] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of this application should be included within the scope of the claims of this application.

Claims

1. A login authentication method characterized by, Applied to login authentication devices, including: The system receives a first 5G message login request sent by a second terminal through a server corresponding to a target service. The first 5G message login request is used to instruct the second terminal to request login to the target service. The first 5G message login request carries a second user identifier, which is a user identifier determined by the second terminal based on historical login information corresponding to the target service. Based on the second user identifier, a service identifier corresponding to the second user identifier and a first mobile phone number corresponding to the second user identifier are determined, wherein the first mobile phone number is a mobile phone number corresponding to the first terminal; Send a second 5G message to the first terminal, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message; The first terminal receives a target instruction sent in response to a received determination operation, wherein the target instruction carries a second message identifier. If the authentication of the second message identifier based on the first message identifier is successful, the second user identifier and the second mobile phone number are sent to the server for login authentication, wherein the second mobile phone number is a mobile phone number obtained by de-identifying the first mobile phone number.

2. A login authentication method characterized by, Servers used in relation to the target business include: The system receives a second user identifier and a second mobile phone number sent by the login authentication device as described in claim 1, wherein the second user identifier is a user identifier determined by the second terminal based on historical login information corresponding to the target service, the second mobile phone number is a mobile phone number obtained by performing data desensitization processing on the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal; If the second user identifier is successfully authenticated based on the pre-obtained user identifier, it is determined that the second terminal has successfully logged into the target service; Send a third successful login message to the second terminal, wherein the third successful login message includes the second user identifier and the second mobile phone number.

3. The method of claim 2, wherein, Before receiving the second user identifier and second mobile phone number sent by the login authentication device, the following is also included: The system receives a first 5G message login request sent by a second terminal and sends the first 5G message login request to a login authentication device. The first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries a second user identifier.

4. The method of claim 2, wherein, After determining that the second terminal has successfully logged into the target service, the process further includes: The login authentication device sends a second successful login message to the first terminal, wherein the second successful login message includes the service name of the target service.

5. A login authentication method characterized by, Applied to the first terminal, including: In response to the second 5G message sent by the login authentication device as described in claim 1, second login information corresponding to the second 5G message is generated, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message; In response to the received confirmation operation of the second login information, a target instruction is sent to the login authentication device, wherein the target instruction carries a second message identifier.

6. The method of claim 5, wherein, After sending the target instruction to the login authentication device, the method further includes: Receive and display the second successful login information sent by the server corresponding to the target service through the login authentication device, wherein the second successful login information includes the service name of the target service.

7. A login authentication method characterized by, Applied to the second terminal, including: In response to the received second operation on the 5G message login control, a second user identifier is determined based on historical login information corresponding to the target service, wherein the 5G message login control corresponds to the target service; A first 5G message login request is sent to the server corresponding to the target service, causing the server to send the first 5G message login request to the login authentication device as described in claim 1, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

8. The method of claim 7, wherein, After sending the first 5G message login request to the server corresponding to the target service, the method further includes: The system receives a third successful login message sent by the server, wherein the third successful login message includes the second user identifier and the second mobile phone number, the second mobile phone number is a mobile phone number obtained by performing data anonymization processing on the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal; In response to the received third successful login information, the page after successful login to the target service is displayed.

9. A login authentication apparatus characterized by comprising: include: The second receiving module is configured to receive a first 5G message login request sent by the second terminal through a server corresponding to the target service. The first 5G message login request is used to instruct the second terminal to request login to the target service. The first 5G message login request carries a second user identifier, which is a user identifier determined by the second terminal based on historical login information corresponding to the target service. The first determining module is used to determine, based on the second user identifier, a service identifier corresponding to the second user identifier and a first mobile phone number corresponding to the second user identifier, wherein the first mobile phone number is a mobile phone number corresponding to the first terminal; The second sending module is used to send a second 5G message to the first terminal, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message; The second receiving module is further configured to receive a target instruction sent by the first terminal in response to a received determination operation, wherein the target instruction carries a second message identifier; The second sending module is further configured to send the second user identifier and the second mobile phone number to the server for login authentication if the second message identifier is successfully authenticated based on the first message identifier, wherein the second mobile phone number is a mobile phone number obtained by performing data anonymization processing on the first mobile phone number.

10. A login authentication device, characterized in that, Servers used in relation to the target business include: The fourth receiving module is used to receive the second user identifier and the second mobile phone number sent by the login authentication device as described in claim 9, wherein the second user identifier is a user identifier determined by the second terminal based on historical login information corresponding to the target service, the second mobile phone number is a mobile phone number obtained by performing data desensitization processing on the first mobile phone number, and the first mobile phone number is a mobile phone number corresponding to the first terminal; The third determining module is used to determine that the second terminal has successfully logged into the target service if the second user identifier is successfully authenticated based on the pre-acquired user identifier. The fourth sending module is used to send third successful login information to the second terminal, wherein the third successful login information includes the second user identifier and the second mobile phone number.

11. A login authentication apparatus characterized by comprising: Applied to the first terminal, including: The fourth generation module is used to generate second login information corresponding to the second 5G message in response to the second 5G message sent by the login authentication device as described in claim 9, wherein the second 5G message is used to inquire whether to log in to the target service corresponding to the service identifier on the second terminal, and the second 5G message carries a first message identifier corresponding to the second 5G message. The sixth sending module is used to send a target instruction to the login authentication device in response to the received confirmation operation of the second login information, wherein the target instruction carries a second message identifier.

12. A login authentication apparatus characterized by comprising: Applied to the second terminal, including: The fourth determining module is used to determine a second user identifier based on historical login information corresponding to the target service in response to the received second operation on the 5G message login control, wherein the 5G message login control corresponds to the target service; The eighth sending module is used to send a first 5G message login request to the server corresponding to the target service, so that the server sends the first 5G message login request to the login authentication device as described in claim 9, wherein the first 5G message login request is used to instruct the second terminal to request login to the target service, and the first 5G message login request carries the second user identifier.

13. An electronic device, comprising: It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the login authentication method as described in any one of claims 1-8.

14. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the login authentication method as described in any one of claims 1-8.

15. A computer program product, characterised in that, The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions that, when executed by a computer, cause the computer to perform the steps of the login authentication method as described in any one of claims 1-8.

Images