Communication authentication method, device, electronic device, storage medium and program product

Abstract

The present invention relates to a communication authentication method, device, electronic device, storage medium and program product, including a service management device on an operator side receiving a one-key anonymous login request sent by a mobile application APP through a software development kit SDK; sending a number acquisition request to a number acquisition capability device on an operator side based on the one-key anonymous login request; receiving a target mobile phone number of a target user sent by the number acquisition capability device on the operator side based on the number acquisition request; determining a target UAID corresponding to the target mobile phone number based on the target mobile phone number and a correspondence between the mobile phone number and a unified anonymous identifier UAID stored in a database of the service management device on the operator side; sending the target UAID to the mobile terminal APP through the SDK; and determining a target mobile phone number corresponding to the target UAID based on the target UAID and a correspondence between the mobile phone number and the UAID stored in the database; and executing a communication task corresponding to the communication request based on the target mobile phone number. The method takes into account both convenience and security.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a communication authentication method, device, electronic equipment, storage medium and program product. Background Art

[0002] Applications (APPs) usually use an account and password system to verify the identity of users. In this case, users need to remember their account and password, which is a burden for those who forget or do not like to manage many accounts and passwords. Therefore, most APPs now use a one-click login method using a mobile phone number to reduce the burden on users. APP-related companies can also send text messages to users by obtaining their mobile phone numbers to carry out marketing promotion activities. However, in recent years, mobile phone number leaks have occurred frequently, and spam text messages and harassing calls have caused great trouble to users, and users' personal privacy security has been seriously threatened. Therefore, the existing communication authentication method cannot take into account both convenience and security. Summary of the invention

[0003] The present invention is intended to provide a communication authentication method, device, electronic device, storage medium and program product to solve the deficiencies in the prior art. The technical problem to be solved by the present invention is achieved through the following technical solutions.

[0004] According to a first aspect of the present disclosure, a communication authentication method is provided, which is performed by a service management device on an operator side, and the method includes:

[0005] Receiving a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries identification information of a target user;

[0006] Based on the one-key anonymous login request, a number acquisition request is sent to a number acquisition capability device on the operator side, wherein the number acquisition request carries the identification information of the target user;

[0007] Receiving the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request;

[0008] Determine the target UAID corresponding to the target mobile phone number based on the target mobile phone number and the correspondence between the mobile phone number and the unified anonymous identifier UAID stored in the database of the service management device on the operator side;

[0009] Send the target UAID to the mobile APP through the SDK, so that the mobile APP completes the login authentication process based on the target UAID;

[0010] After sending the target UAID to the mobile APP through the SDK so that the mobile APP completes the login authentication process based on the target UAID, the method further includes:

[0011] Receive a communication request sent by the APP management device, wherein the communication request carries the target UAID and an authorization agreement signed by the target user;

[0012] Based on the communication request, a verification request is sent to the blockchain authorization evidence storage device, wherein the verification request carries the target UAID and the authorization agreement signed by the target user;

[0013] Upon receiving a verification success message sent by the blockchain authorization evidence storage device based on the verification request, determining a target mobile phone number corresponding to the target UAID based on the target UAID and the correspondence between the mobile phone number and the UAID stored in the database of the operator-side service management device;

[0014] Based on the target mobile phone number, executing a communication task corresponding to the communication request;

[0015] Sending the communication task execution result to the APP management device;

[0016] Send a communication task to the blockchain authorized evidence storage device to execute the evidence storage.

[0017] Furthermore, before receiving the one-key anonymous login request sent by the mobile application APP through the software development kit SDK, the method also includes:

[0018] Receiving, through the SDK, a one-key anonymous registration request sent by the mobile terminal APP, wherein the one-key anonymous registration request carries identification information of the target user;

[0019] Based on the one-key anonymous registration request, sending a number acquisition request to a number acquisition capability device on the operator side, wherein the number acquisition request carries the identification information of the target user;

[0020] Receiving the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request;

[0021] Calculate the target UAID based on the target data and the target mobile phone number;

[0022] Storing the correspondence between the target mobile phone number and the target UAID in a database of the service management device on the operator side;

[0023] Send the target UAID to the mobile APP through the SDK, so that the mobile APP completes the registration and authentication process based on the target UAID;

[0024] Receiving the target UAID and the authorization agreement signed by the target user sent by the APP management device;

[0025] Obtain the target UAID evidence based on the target UAID and the generation time of the target UAID, and obtain the target authorization agreement evidence based on the authorization agreement signed by the target user;

[0026] The target UAID certificate and the target authorization agreement certificate are sent to the blockchain authorization certificate device.

[0027] Further, the target data includes an isolation value and a current timestamp corresponding to the mobile APP;

[0028] The calculating the target UAID based on the target data and the target mobile phone number includes:

[0029] The isolation value corresponding to the mobile APP and the target mobile phone number are concatenated to obtain the first source data;

[0030] Obtaining stage data based on the first source data;

[0031] Concatenate the stage data and the current timestamp to obtain second source data;

[0032] A target UAID is obtained based on the second source data.

[0033] Furthermore, the communication request also carries communication content. When the communication request is a text message sending request, the communication content is text message content.

[0034] The executing a communication task corresponding to the communication request based on the target mobile phone number includes:

[0035] Generate an anonymous subscription SMS based on the SMS template and the SMS content, and send the anonymous subscription SMS to the terminal device corresponding to the target mobile phone number through the SMS gateway;

[0036] The sending the communication task execution result to the APP management device includes:

[0037] Send a text message to the APP management device to send the result.

[0038] Further, in the case where the communication request is a telephone call request, executing the communication task corresponding to the communication request based on the target mobile phone number includes:

[0039] Sending an intermediate number acquisition request to an intermediate number management device, wherein the intermediate number acquisition request carries the target mobile phone number;

[0040] Receiving a target intermediate number successfully bound to the target mobile phone number and sent by the intermediate number management device based on the intermediate number acquisition request;

[0041] The sending the communication task execution result to the APP management device includes:

[0042] The target intermediate number is sent to the APP management device.

[0043] According to a second aspect of the present disclosure, a communication authentication method is provided, which is performed by an APP management device, and the method includes:

[0044] When the mobile terminal APP responds to the login operation of the target user, receiving the target UAID sent by the mobile terminal APP;

[0045] Query whether the target UAID is stored in the database of the APP management device;

[0046] If the target UAID is stored in the database of the APP management device, sending an authorization login message to the mobile terminal APP;

[0047] In the case where the target UAID is stored in the database of the APP management device, after sending an authorization login message to the mobile terminal APP, the method further includes:

[0048] Sending a communication request to the service management device at the operator side, wherein the communication request carries the target UAID and the authorization agreement signed by the target user;

[0049] Receive a communication task execution result corresponding to the communication request sent by the operator-side service management device.

[0050] Furthermore, when the mobile terminal APP responds to the login operation of the target user, before receiving the target UAID sent by the mobile terminal APP, the method further includes:

[0051] When the mobile terminal APP responds to the registration operation of the target user, receiving the target UAID sent by the mobile terminal APP and the authorization agreement signed by the target user;

[0052] Storing the target UAID in a database of the APP management device;

[0053] The target UAID and the authorization agreement signed by the target user are sent to the service management device at the operator side.

[0054] Furthermore, the communication request also carries communication content. When the communication request is a text message sending request, the communication content is text message content.

[0055] The receiving the communication task execution result corresponding to the communication request sent by the operator-side service management device includes:

[0056] Receive a text message sending result corresponding to the text message sending request sent by the operator-side service management device.

[0057] Further, in the case that the communication request is a telephone call request, the receiving the communication task execution result corresponding to the communication request sent by the operator-side service management device includes:

[0058] Receive a target intermediate number corresponding to the telephone call request sent by the operator-side service management device.

[0059] According to a third aspect of the present disclosure, a communication authentication device is provided, which is applied to a service management device on an operator side, and the device includes:

[0060] A first sending module is used to receive a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries identification information of a target user;

[0061] A second sending module is used to send a number acquisition request to the operator-side number acquisition capability device based on the one-key anonymous login request, wherein the number acquisition request carries the identification information of the target user;

[0062] A first receiving module is used to receive the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request;

[0063] A first determination module, configured to determine a target UAID corresponding to the target mobile phone number based on the target mobile phone number and a correspondence between mobile phone numbers and unified anonymous identifiers UAIDs stored in a database of the service management device on the operator side;

[0064] The third sending module is used to send the target UAID to the mobile terminal APP through the SDK, so that the mobile terminal APP completes the login authentication process based on the target UAID;

[0065] The device also includes:

[0066] A fifth receiving module, configured to receive a communication request sent by the APP management device, wherein the communication request carries the target UAID and the authorization agreement signed by the target user;

[0067] A seventh sending module is used to send a verification request to the blockchain authorization evidence storage device based on the communication request, wherein the verification request carries the target UAID and the authorization agreement signed by the target user;

[0068] A sixth receiving module, configured to determine, upon receiving a verification success message sent by the blockchain authorization evidence storage device based on the verification request, a target mobile phone number corresponding to the target UAID based on the target UAID and a correspondence between mobile phone numbers and UAIDs stored in a database of the operator-side service management device;

[0069] A first execution module, configured to execute a communication task corresponding to the communication request based on the target mobile phone number;

[0070] An eighth sending module, used to send the communication task execution result to the APP management device;

[0071] The ninth sending module is used to send a communication task to the blockchain authorized evidence storage device to execute the evidence.

[0072] According to a fourth aspect of the present disclosure, a communication authentication device is provided, which is applied to an APP management device, and the device includes:

[0073] A sixth receiving module, configured to receive a target UAID sent by the mobile terminal APP when the mobile terminal APP responds to a login operation of the target user;

[0074] A first query module, used to query whether the target UAID is stored in the database of the APP management device;

[0075] A tenth sending module, configured to send an authorization login message to the mobile terminal APP if the target UAID is stored in the database of the APP management device;

[0076] The device also includes:

[0077] A twelfth sending module, configured to send a communication request to the service management device on the operator side, wherein the communication request carries the target UAID and the authorization agreement signed by the target user;

[0078] An eighth receiving module is used to receive a communication task execution result corresponding to the communication request sent by the operator-side service management device.

[0079] According to a fifth aspect of the present disclosure, an electronic device is provided. The electronic device includes: a memory and a processor, wherein a computer program is stored in the memory, and the method is implemented when the processor executes the computer program.

[0080] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program implements the method when executed by a processor.

[0081] According to a seventh aspect of the present disclosure, a computer program product is provided, comprising computer instructions, which implement the method when executed by a processor.

[0082] The embodiments of the present invention include the following advantages:

[0083] The communication authentication method, system, device and related equipment provided by the embodiments of the present invention include: an operator-side service management device receives a one-key anonymous login request sent by a mobile application APP through a software development kit SDK; based on the one-key anonymous login request, sends a number acquisition request to an operator-side number acquisition capability device; receives a target mobile phone number of a target user sent by the operator-side number acquisition capability device based on the number acquisition request; based on the target mobile phone number and the correspondence between the mobile phone number and the unified anonymous identifier UAID stored in the database of the operator-side service management device, determines the target UAID corresponding to the target mobile phone number; sends the target UAI to the mobile APP through the SDK D, so that the mobile APP completes the login authentication process based on the target UAID; receives the communication request sent by the APP management device; based on the communication request, sends a verification request to the blockchain authorization evidence storage device; in the case of receiving the verification success message sent by the blockchain authorization evidence storage device based on the verification request, based on the target UAID and the correspondence between the mobile phone number and UAID stored in the database of the operator-side service management device, determine the target mobile phone number corresponding to the target UAID; based on the target mobile phone number, execute the communication task corresponding to the communication request; send the communication task execution result to the APP management device; send the communication task execution evidence to the blockchain authorization evidence storage device. In this embodiment, UAID is used for one-click login. Compared with account and password registration, users do not need to remember complicated account passwords, nor do they need to bear the fraud risk caused by password leakage; compared with one-click mobile phone number login, users do not need to expose their mobile phone numbers to the mobile APP, and privacy is guaranteed. Therefore, this communication authentication method takes into account both convenience and security. In addition, if the company where the mobile APP is located needs to initiate a marketing campaign to the APP users by phone, the service management device on the operator side will send the target intermediate number that is successfully bound to the target mobile phone number to the APP management device, so that the mobile APP-related company can carry out marketing promotion activities to the target users through the target intermediate number, while avoiding exposing the user's real mobile phone number to the mobile APP, thereby further protecting the user's privacy and security. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] Figure 1 It is one of the flow charts of steps of a communication authentication method embodiment of the present invention;

[0085] Figure 2 This is a second flow chart of a communication authentication method embodiment of the present invention;

[0086] Figure 3 This is a flow chart of steps of an embodiment of a communication authentication method of the present invention;

[0087] Figure 4This is a sixth step flow chart of a communication authentication method embodiment of the present invention;

[0088] Figure 5 This is the seventh step flow chart of a communication authentication method embodiment of the present invention;

[0089] Figure 6 It is a structural schematic diagram of an embodiment of a communication authentication system of the present invention;

[0090] Figure 7 It is one of the structural schematic diagrams of an embodiment of a communication authentication device of the present invention;

[0091] Figure 8 This is a second structural diagram of a communication authentication device embodiment of the present invention;

[0092] Fig. 9 It is a structural schematic diagram of an electronic device of the present invention. DETAILED DESCRIPTION

[0093] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0094] Figure 1 A flow chart of a communication authentication method 100 according to an embodiment of the present disclosure is shown. The method is executed by a service management device on an operator side. Specifically, the method 100 includes:

[0095] S101, receiving a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries identification information of a target user;

[0096] In some embodiments, the mobile APPs are mainly to C APPs in weak login scenarios. Weak login scenarios mainly refer to that users do not need a strict login process when using these APPs and can simply log in. For example, users can log in through a mobile phone number verification code instead of requiring a complex password; to C APPs mainly refer to that these APPs are mainly oriented to consumers (C-end customers) rather than corporate users, that is, they are usually targeted at mass users.

[0097] The target user launches the mobile APP and requests a one-click anonymous login. The mobile APP calls the Software Development Kit (SDK), which is provided by the operator and integrates some application programming interface (API) access functions and parameters that interact with the operator's service management equipment. The SDK sends a one-click anonymous login request to the operator's service management equipment through the API interface. The one-click anonymous login request carries the target user's identification information (such as some mobile traffic information and Internet Protocol (IP) information, etc.).

[0098] In some embodiments, before receiving the one-key anonymous login request sent by the mobile application APP through the software development kit SDK, the method further includes:

[0099] Receiving, through the SDK, a one-key anonymous registration request sent by the mobile terminal APP, wherein the one-key anonymous registration request carries identification information of the target user;

[0100] Based on the one-key anonymous registration request, sending a number acquisition request to a number acquisition capability device on the operator side, wherein the number acquisition request carries the identification information of the target user;

[0101] Receiving the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request;

[0102] Calculate the target UAID based on the target data and the target mobile phone number;

[0103] Storing the correspondence between the target mobile phone number and the target UAID in a database of the service management device on the operator side;

[0104] The target UAID is sent to the mobile APP through the SDK, so that the mobile APP completes the registration and authentication process based on the target UAID.

[0105] Before the target user requests a one-click anonymous login from the mobile APP, he / she needs to register anonymously and sign the authorization agreement. The mobile APP calls the SDK, and the SDK sends a one-click anonymous login request to the operator-side service management device through the API interface. The one-click anonymous login request carries the target user's identification information. The operator-side service management device accesses the operator-side number acquisition capability device based on the one-click anonymous registration request. The operator-side number acquisition capability device returns the target user's real mobile phone number (that is, the target mobile phone number mentioned above) based on the target user's identification information.

[0106] The service management device on the operator side can use the MD5 digest algorithm to calculate the target mobile phone number and target data (mainly control data and timestamp) to obtain the target unified anonymous identifier (Uniform Anonymous Identifier, UAID), and store the corresponding relationship between the target mobile phone number and the target UAID in the database of the service management device on the operator side. It should be noted that in the prior art, the UAID is not stored, and the MD5 digest algorithm is an irreversible algorithm, so the mobile phone number cannot be reversed through the UAID.

[0107] The operator-side service management device sends the target UAID to the mobile APP through the SDK, and then the mobile APP sends the target UAID and the authorization agreement signed by the target user to the APP management device. The APP management device stores the target UAID in its database as the account name of the target user, and sends the target UAID and the authorization agreement signed by the target user to the operator-side service management device.

[0108] In the above embodiment, the service management device on the operator side assists the mobile terminal APP to complete the one-click anonymous registration process of the target user. Compared with the account and password registration, the one-click registration using UAID does not require users to remember complicated account passwords, nor does it require users to bear the fraud risk caused by password leakage; compared with the one-click mobile phone number registration, users do not need to expose their mobile phone numbers to the mobile terminal APP, and their privacy is protected. Therefore, this registration method takes into account both convenience and security, and provides users with a better experience.

[0109] In some embodiments, after sending the target UAID to the mobile APP through the SDK so that the mobile APP completes the registration and authentication process based on the target UAID, the method further includes:

[0110] Receiving the target UAID and the authorization agreement signed by the target user sent by the APP management device;

[0111] Obtain the target UAID evidence based on the target UAID and the generation time of the target UAID, and obtain the target authorization agreement evidence based on the authorization agreement signed by the target user;

[0112] The target UAID certificate and the target authorization agreement certificate are sent to the blockchain authorization certificate device.

[0113] After the mobile APP completes the registration and authentication process based on the target UAID, the service management device on the operator side receives the target UAID and the authorization agreement signed by the target user sent by the APP management device. The service management device on the operator side performs MD5 digest calculation based on the target UAID and the generation time of the target UAID (which can be queried in the database of the service management device on the operator side). The calculated digest value is the target UAID evidence, and performs MD5 digest calculation on the authorization agreement signed by the target user. The calculated digest value is the target authorization agreement evidence.

[0114] Afterwards, the service management device on the operator side sends the target UAID evidence and the target authorization agreement evidence to the blockchain authorization evidence device for on-chain storage.

[0115] In the above embodiment, the service management device on the operator side sends the target UAID evidence and the target authorization agreement evidence to the blockchain authorization evidence device for on-chain storage, which is conducive to the subsequent verification of the user's login request, thereby improving the security of the user's login. In addition, if disputes or disputes occur in the future, these evidences can be used as evidence of the compliance of mobile APP activities, thereby facilitating the resolution of disputes.

[0116] In some embodiments, the target data includes an isolation value and a current timestamp corresponding to the mobile APP;

[0117] The calculating the target UAID based on the target data and the target mobile phone number includes:

[0118] The isolation value corresponding to the mobile APP and the target mobile phone number are concatenated to obtain the first source data;

[0119] Obtaining stage data based on the first source data;

[0120] Concatenate the stage data and the current timestamp to obtain second source data;

[0121] A target UAID is obtained based on the second source data.

[0122] The service management device on the operator side concatenates the isolation value corresponding to the mobile APP and the target mobile phone number to obtain the source data of the stage data (i.e., the first source data mentioned above), and then uses the MD5 digest algorithm to calculate the first source data to obtain the digest value (i.e., the stage data mentioned above). The current timestamp refers to the timestamp when the service management device on the operator side calculates the target UAID. The service management device on the operator side concatenates the stage data and the current timestamp to obtain the source data of the target UAID (i.e., the second source data mentioned above), and then uses the MD5 algorithm to calculate the second source data to obtain the digest value (i.e., the target UAID mentioned above).

[0123] In the above embodiment, the original mobile phone number is not directly stored or transmitted, but is processed by MD5 hashing to avoid direct exposure of the user's sensitive information.

[0124] S102: Based on the one-key anonymous login request, send a number acquisition request to a number acquisition capability device on the operator side, wherein the number acquisition request carries identification information of the target user;

[0125] In some embodiments, after receiving a one-click anonymous login request initiated by a user on a mobile APP, the operator-side service management device will send a request to the operator-side number capability device to obtain a phone number. This request will include the identification information of the target user so that the operator-side number capability device can find the target user's number from multiple numbers.

[0126] S103, receiving the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request;

[0127] In some embodiments, when the number acquisition capability device on the operator side finds the target mobile phone number of the target user, the target mobile phone number is sent to the service management device on the operator side.

[0128] S104, determining a target UAID corresponding to the target mobile phone number based on the target mobile phone number and the correspondence between the mobile phone number and the unified anonymous identifier UAID stored in the database of the service management device on the operator side;

[0129] In some embodiments, most users will complete the one-key anonymous registration process before sending a one-key anonymous login request to the mobile APP (the registration process is described in detail in the above embodiments). During the one-key anonymous registration process, the operator-side service management device will store the corresponding relationship between the user's mobile phone number and UAID in its database. Therefore, when the target user logs in, the operator-side management device can query the database based on the target mobile phone number of the target user to determine the target UAID corresponding to the target mobile phone number.

[0130] S105. Send the target UAID to the mobile APP through the SDK, so that the mobile APP completes the login authentication process based on the target UAID.

[0131] In some embodiments, the operator-side service management device sends the target UAID to the mobile APP through the SDK, and the mobile APP subsequently sends the target UAID to the APP management device. When the APP management device verifies that the target UAID is a legitimate account, the target user can be authorized to log in to the mobile APP.

[0132] S106. Receive a communication request sent by the APP management device, where the communication request carries the target UAID and an authorization agreement signed by the target user;

[0133] S107. Based on the communication request, send a verification request to the blockchain authorization evidence storage device, where the verification request carries the target UAID and the authorization agreement signed by the target user;

[0134] S108. Upon receiving a verification success message sent by the blockchain authorization evidence storage device based on the verification request, determine a target mobile phone number corresponding to the target UAID based on the target UAID and the correspondence between the mobile phone number and the UAID stored in the database of the operator-side service management device;

[0135] S109, executing a communication task corresponding to the communication request based on the target mobile phone number;

[0136] S1010. Send the communication task execution result to the APP management device.

[0137] S1011. Send a communication task to the blockchain authorized evidence storage device to execute the evidence storage.

[0138] If the enterprise where the mobile APP is located needs to launch a marketing campaign for APP users, the APP management device will start the anonymous subscription contact process. Specifically: the APP management device sends a communication request (such as a text message sending request or a phone call request) to the operator-side service management device. The communication request will carry the target UAID of the target user and the authorization agreement signed by the target user. The operator-side service management device accesses the blockchain authorization evidence storage device to verify the validity of the target UAID and the authorization agreement signed by the target user. When the blockchain authorization evidence storage device determines that the target UAID evidence corresponding to the target UAID and the target authorization agreement evidence corresponding to the authorization agreement signed by the target user are stored on the device, a verification success message is sent to the operator-side service management device.

[0139] After receiving the verification success message, the service management device on the operator side determines the target mobile phone number corresponding to the target UAID based on the target UAID and the correspondence between the mobile phone number and the UAID stored in its database. Then, the target mobile phone number is used to perform the corresponding communication task and the execution result is returned to the APP management device. For example, a marketing SMS is sent to the terminal where the target mobile phone number is located, and the result that the SMS has been sent is notified to the APP management device.

[0140] In the above embodiment, the service management device on the operator side determines the target mobile phone number of the target user according to the target UAID, and then executes the corresponding communication task based on the target mobile phone number, avoiding exposing the user's mobile phone number to the mobile APP, thereby protecting the user's privacy and security. After the service management device on the operator side sends the communication task execution result to the APP management device, it will also upload the communication task execution evidence to the blockchain authorization evidence storage device. If disputes or disputes occur in the future, these evidences can be used as evidence of the compliance of the mobile APP activities, thereby facilitating the resolution of disputes.

[0141] In some embodiments, the communication request also carries communication content. When the communication request is a text message sending request, the communication content is text message content.

[0142] The executing a communication task corresponding to the communication request based on the target mobile phone number includes:

[0143] Generate an anonymous subscription SMS based on the SMS template and the SMS content, and send the anonymous subscription SMS to the terminal device corresponding to the target mobile phone number through the SMS gateway;

[0144] The sending the communication task execution result to the APP management device includes:

[0145] Send a text message to the APP management device to send the result.

[0146] If the enterprise where the mobile APP is located needs to launch a marketing campaign for APP users via SMS, the APP management device will send an SMS sending request to the operator-side service management device. In addition to the target UAID of the target user and the authorization agreement signed by the target user, the SMS sending request will also carry the SMS content. The operator-side service management device assembles an anonymous subscription SMS based on the SMS template and the SMS content. The operator-side service management device sends the anonymous subscription SMS to the terminal device corresponding to the target mobile phone number through the SMS gateway to achieve business promotion, and informs the APP management device of the result of the SMS sending.

[0147] In the above embodiment, the service management device on the operator side determines the target mobile phone number of the target user according to the target UAID, and then sends an anonymous subscription SMS based on the target mobile phone number, thereby avoiding exposing the user's mobile phone number to the mobile terminal APP, thereby protecting the user's privacy security.

[0148] In some embodiments, when the communication request is a telephone call request, executing the communication task corresponding to the communication request based on the target mobile phone number includes:

[0149] Sending an intermediate number acquisition request to an intermediate number management device, wherein the intermediate number acquisition request carries the target mobile phone number;

[0150] Receiving a target intermediate number successfully bound to the target mobile phone number and sent by the intermediate number management device based on the intermediate number acquisition request;

[0151] The sending the communication task execution result to the APP management device includes:

[0152] The target intermediate number is sent to the APP management device.

[0153] If the company where the mobile APP is located needs to initiate a marketing campaign to the APP users by phone, the APP management device will send a phone call request to the operator-side service management device. At this time, the operator-side service management device will access the intermediate number management device, request to obtain the target intermediate number bound to the target phone number, and send the target intermediate number to the APP management device. Then the relevant company personnel can make calls through the target intermediate number to achieve business promotion. After the call ends, the target intermediate number and the target mobile phone number are immediately unbound.

[0154] In the above embodiment, the service management device on the operator side sends the target intermediate number that is successfully bound to the target mobile phone number to the APP management device, so that the mobile APP-related companies can carry out marketing promotion activities to the target users through the target intermediate number, while avoiding exposing the user's real mobile phone number to the mobile APP, thereby further protecting the user's privacy and security.

[0155] According to an embodiment of the present disclosure, the service management device on the operator side receives a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries identification information of a target user; based on the one-key anonymous login request, a number acquisition request is sent to a number acquisition capability device on the operator side, wherein the number acquisition request carries identification information of the target user;

[0156] Receive the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request; determine the target UAID corresponding to the target mobile phone number based on the target mobile phone number and the correspondence between the mobile phone number and the unified anonymous identifier UAID stored in the database of the operator-side service management device; send the target UAID to the mobile terminal APP through the SDK, so that the mobile terminal APP completes the login authentication process based on the target UAID; receive the communication request sent by the APP management device; send a verification request to the blockchain authorization evidence storage device based on the communication request; in the case of receiving the verification success message sent by the blockchain authorization evidence storage device based on the verification request, determine the target mobile phone number corresponding to the target UAID based on the target UAID and the correspondence between the mobile phone number and the UAID stored in the database of the operator-side service management device; based on the target mobile phone number, execute the communication task corresponding to the communication request; send the communication task execution result to the APP management device; send the communication task execution evidence to the blockchain authorization evidence storage device. In this embodiment, the operator-side service management device assists the mobile terminal APP in completing the one-key anonymous login process of the target user. Compared with account and password registration, users do not need to remember complicated account and password, nor do they need to bear the risk of fraud caused by password leakage. Compared with one-click mobile phone number login, users do not need to expose their mobile phone numbers to the mobile APP, and their privacy is guaranteed. Therefore, this communication authentication method takes into account both convenience and security, and provides users with a better experience. In addition, if the company where the mobile APP is located needs to initiate a marketing campaign to the APP users by phone, the service management device on the operator side will send the target intermediate number that is successfully bound to the target mobile phone number to the APP management device, so that the mobile APP-related companies can perform marketing and promotion activities to the target users through the target intermediate number, while avoiding exposing the user's real mobile phone number to the mobile APP, thereby further protecting the user's privacy.

[0157] Figure 2 A flow chart of a communication authentication method 200 according to an embodiment of the present disclosure is shown. The method is executed by an APP management device. Specifically, the method 200 includes:

[0158] S201. When the mobile terminal APP responds to a login operation of a target user, receiving a target UAID sent by the mobile terminal APP;

[0159] In some embodiments, when the mobile terminal APP responds to the login operation of the target user, before receiving the target UAID sent by the mobile terminal APP, the method further includes:

[0160] When the mobile terminal APP responds to the registration operation of the target user, receiving the target UAID sent by the mobile terminal APP and the authorization agreement signed by the target user;

[0161] Storing the target UAID in a database of the APP management device;

[0162] The target UAID and the authorization agreement signed by the target user are sent to the service management device at the operator side.

[0163] S202, querying whether the target UAID is stored in the database of the APP management device;

[0164] S203: When the target UAID is stored in the database of the APP management device, send an authorization login message to the mobile terminal APP.

[0165] S204: Send a communication request to the service management device at the operator side, where the communication request carries the target UAID and the authorization agreement signed by the target user;

[0166] S205: Receive a communication task execution result corresponding to the communication request sent by the operator-side service management device.

[0167] In some embodiments, the communication request also carries communication content. When the communication request is a text message sending request, the communication content is text message content.

[0168] The receiving the communication task execution result corresponding to the communication request sent by the operator-side service management device includes:

[0169] Receive a text message sending result corresponding to the text message sending request sent by the operator-side service management device.

[0170] In some embodiments, when the communication request is a telephone call request, the receiving the communication task execution result corresponding to the communication request sent by the operator-side service management device includes:

[0171] Receive a target intermediate number corresponding to the telephone call request sent by the operator-side service management device.

[0172] It should be noted that this embodiment is Figure 1 The implementation method of the corresponding APP management device in the embodiment shown in the figure can be found in the specific implementation method of the APP management device in the embodiment shown in the figure. Figure 1 In order to avoid repeated description, the relevant description of the embodiment shown will not be repeated in this embodiment, and the same beneficial effects can still be achieved.

[0173] See also Figure 3 , Figure 3 This is a flow chart of steps of a communication authentication method embodiment of the present invention, which is mainly related to the registration authentication process:

[0174] (1) The target user launches the mobile APP and first signs the authorization agreement, which means that the target user agrees to authorize the implementation of subsequent one-click anonymous registration, one-click anonymous login and anonymous communication services. Then, when using the mobile APP for the first time, a one-click anonymous registration request is initiated.

[0175] (2) The mobile APP sends a one-click anonymous registration request to the operator's service management device through the SDK. The one-click anonymous registration request carries the identification information of the target user.

[0176] (3) Based on the one-click anonymous registration request, the service management device on the operator side sends a number acquisition request to the number acquisition capability device on the operator side, where the number acquisition request carries the identification information of the target user.

[0177] (4) The operator-side number acquisition capability device sends the target mobile phone number of the target user to the operator-side service management device based on the number acquisition request.

[0178] (5) The service management device on the operator side calculates the target UAID based on the target data and the target mobile phone number, and stores the corresponding relationship between the target mobile phone number and the target UAID in the database of the service management device on the operator side.

[0179] (6) The service management device on the operator side sends the target UAID to the mobile APP through the SDK.

[0180] (7) The mobile APP sends the target UAID and the authorization agreement signed by the target user to the APP management device.

[0181] (8) The APP management device stores the target UAID in its database as the target user’s account name.

[0182] (9) The APP management device sends the target UAID and the authorization agreement signed by the target user to the operator-side service management device.

[0183] (10) The service management device on the operator side obtains the target UAID evidence based on the target UAID and the generation time of the target UAID, and obtains the target authorization agreement evidence based on the authorization agreement signed by the target user.

[0184] (11) The service management device on the operator side sends the target UAID proof and the target authorization agreement proof to the blockchain authorization proof device.

[0185] See also Figure 4 , Figure 4 This is a flow chart of steps of a communication authentication method embodiment of the present invention, which is mainly related to the login authentication process:

[0186] (1) The target user launches the mobile app and initiates a one-click anonymous login request.

[0187] (2) The mobile APP sends a one-click anonymous login request to the operator's service management device through the SDK. The one-click anonymous login request carries the identification information of the target user.

[0188] (3) Based on the one-key anonymous login request, the service management device on the operator side sends a number acquisition request to the number acquisition capability device on the operator side, where the number acquisition request carries the identification information of the target user.

[0189] (4) The operator-side number acquisition capability device sends the target mobile phone number of the target user to the operator-side service management device based on the number acquisition request.

[0190] (5) The service management device on the operator side determines the target UAID corresponding to the target mobile phone number based on the target mobile phone number and the correspondence between the mobile phone number and the unified anonymous identifier UAID stored in its database.

[0191] (6) The service management device on the operator side sends the target UAID to the mobile APP through the SDK.

[0192] (7) The mobile APP sends the target UAID to the APP management device.

[0193] (8) The APP management device queries its database to see whether the target UAID is a legitimate account, that is, whether the target UAID is stored in its database.

[0194] (9) After confirming that the target UAID is a legitimate account, send an authorization login message to the mobile APP to allow the target user to log in to the APP.

[0195] See also Figure 5 , Figure 5 This is a flow chart of steps of an embodiment of a communication authentication method of the present invention, which is mainly related to the subscription authentication process:

[0196] (1) Mobile APP initiates marketing activities.

[0197] (2) The APP management device sends a communication request to the operator's service management device. The communication request carries the target UAID and the authorization agreement signed by the target user.

[0198] (3) Based on the communication request, the service management device on the operator side sends a verification request to the blockchain authorization evidence storage device, and the verification request carries the target UAID and the authorization agreement signed by the target user.

[0199] (4) The blockchain authorization evidence device sends a verification success message to the operator-side service management device based on the verification request and the stored target UAID evidence and target authorization protocol evidence.

[0200] (5) The service management device on the operator side determines the target mobile phone number corresponding to the target UAID based on the target UAID and the correspondence between mobile phone numbers and UAIDs stored in its database.

[0201] (6) If the communication request is a text message sending request, the communication request also carries communication content, which is the text message content. The service management device on the operator side generates an anonymous subscription text message based on the text message template and the text message content, and sends the anonymous subscription text message to the terminal device corresponding to the target mobile phone number through the text message gateway.

[0202] (7) The service management device on the operator side sends a text message to the APP management device to inform it of the result.

[0203] (8) When the communication request is a telephone call request, the service management device on the operator side sends an intermediate number acquisition request to the intermediate number management device, and the intermediate number acquisition request carries the target mobile phone number.

[0204] (9) The intermediate number management device sends the target intermediate number that is successfully bound to the target mobile phone number to the operator-side service management device.

[0205] (10) The service management device on the operator side sends the target intermediate number to the APP management device.

[0206] (11) The APP management device sends the target intermediate number to the mobile APP, so that the mobile APP company can conduct telephone marketing promotion through the target intermediate number.

[0207] (12) After the call ends, the target intermediate number and the target mobile phone number are unlinked.

[0208] (13) The service management device on the operator side sends the SMS or phone call evidence to the blockchain authorization evidence device.

[0209] In the above disclosed embodiments, the operator-side service management device, APP management device, operator-side number acquisition capability device and blockchain authorization evidence storage device and other devices jointly complete the various processes of the above communication authentication. Compared with account and password registration, users do not need to remember complicated account passwords, nor do they need to bear the fraud risk caused by password leakage, nor do they need to install additional software tools and additional configurations by using UAID for one-click authentication and communication between mobile APP and target users. Compared with one-click mobile phone number login, the two have the same authority because they are both endorsed by operators, but users do not need to expose their mobile phone numbers to mobile APP, privacy is guaranteed, convenience and security are taken into account, and users are provided with a better experience.

[0210] In addition, based on blockchain technology, a blockchain authorized evidence storage device is constructed. The important evidence of the above-mentioned communication authentication process will be stored on the chain to the blockchain authorized evidence storage device as evidence of the compliance of the mobile APP behavior, which is conducive to the resolution of subsequent disputes.

[0211] More importantly, the service management device on the operator side calculates the target mobile phone number and target data (mainly control data and timestamp) based on the MD5 digest algorithm to obtain the target UAID, and stores the corresponding relationship between the target mobile phone number and the target UAID in the database of the service management device on the operator side. In the prior art, the UAID is not stored, and the MD5 digest algorithm is an irreversible algorithm, so the mobile phone number cannot be reversed through the UAID. This application can reversely query the mobile phone number through the UAID based on the information stored in the database.

[0212] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the present disclosure is not limited by the order of the actions described, because according to the present disclosure, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present disclosure.

[0213] The above is an introduction to the method embodiment. The following is a further explanation of the scheme described in the present disclosure through system and device embodiments.

[0214] See also Figure 6 , Figure 6 This is a structural diagram of a communication authentication system of the present invention, which mainly includes an operator-side service management device, an APP management device, an operator-side number acquisition capability device, and a blockchain authorization evidence storage device, wherein:

[0215] The operator-side service management device is used to receive a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries the identification information of the target user; based on the one-key anonymous login request, send a number acquisition request to the operator-side number acquisition capability device, wherein the number acquisition request carries the identification information of the target user; receive the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request; determine the target UAID corresponding to the target mobile phone number based on the target mobile phone number and the correspondence between the mobile phone number and the unified anonymous identifier UAID stored in the database of the operator-side service management device; send the target UAID to the mobile APP through the SDK, so that the mobile APP completes the login authentication process based on the target UAID;

[0216] The APP management device is used to receive the target UAID sent by the mobile terminal APP when the mobile terminal APP responds to the login operation of the target user; query whether the target UAID is stored in the database of the APP management device; and send an authorization login message to the mobile terminal APP when the target UAID is stored in the database of the APP management device;

[0217] The operator-side number acquisition capability device is used to receive a number acquisition request sent by the operator-side service management device; based on the number acquisition request, send the target mobile phone number of the target user to the operator-side service management device;

[0218] The blockchain authorization evidence device is used to receive the target UAID evidence and the target authorization agreement evidence sent by the operator-side service management device.

[0219] Figure 7 A block diagram of a communication authentication device 700 according to an embodiment of the present disclosure is shown, which is applied to a service management device on an operator side. The device 700 includes:

[0220] The first sending module 701 is used to receive a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries identification information of a target user;

[0221] The second sending module 702 is used to send a number acquisition request to the operator-side number acquisition capability device based on the one-key anonymous login request, where the number acquisition request carries the identification information of the target user;

[0222] The first receiving module 703 is used to receive the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request;

[0223] A first determination module 704 is configured to determine a target UAID corresponding to the target mobile phone number based on the target mobile phone number and a correspondence between mobile phone numbers and unified anonymous identifiers UAIDs stored in a database of the service management device on the operator side;

[0224] The third sending module 705 is used to send the target UAID to the mobile terminal APP through the SDK, so that the mobile terminal APP completes the login authentication process based on the target UAID.

[0225] The device also includes:

[0226] The fifth receiving module 706 is configured to receive a communication request sent by the APP management device, wherein the communication request carries the target UAID and the authorization agreement signed by the target user;

[0227] The seventh sending module 707 is used to send a verification request to the blockchain authorization evidence storage device based on the communication request, where the verification request carries the target UAID and the authorization agreement signed by the target user;

[0228] The sixth receiving module 708 is used to determine the target mobile phone number corresponding to the target UAID based on the target UAID and the correspondence between the mobile phone number and the UAID stored in the database of the operator-side service management device when receiving the verification success message sent by the blockchain authorization evidence storage device based on the verification request;

[0229] A first execution module 709, configured to execute a communication task corresponding to the communication request based on the target mobile phone number;

[0230] The eighth sending module 7010 is used to send the communication task execution result to the APP management device;

[0231] The ninth sending module 7011 is used to send the communication task execution evidence to the blockchain authorized evidence storage device.

[0232] In some embodiments, the apparatus further comprises:

[0233] A second receiving module is used to receive a one-key anonymous registration request sent by a mobile terminal APP through the SDK, wherein the one-key anonymous registration request carries identification information of a target user;

[0234] A fourth sending module, configured to send a number acquisition request to a number acquisition capability device on the operator side based on the one-key anonymous registration request, wherein the number acquisition request carries identification information of the target user;

[0235] A third receiving module is used to receive the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request;

[0236] A first calculation module, configured to calculate a target UAID based on the target data and the target mobile phone number;

[0237] A first storage module, configured to store the correspondence between the target mobile phone number and the target UAID in a database of the service management device on the operator side;

[0238] A fifth sending module, configured to send the target UAID to the mobile terminal APP through the SDK, so that the mobile terminal APP completes the registration and authentication process based on the target UAID;

[0239] A fourth receiving module, configured to receive the target UAID sent by the APP management device and the authorization agreement signed by the target user;

[0240] A first processing module is used to obtain a target UAID evidence according to a target UAID and a generation time of the target UAID, and obtain a target authorization agreement evidence according to an authorization agreement signed by the target user;

[0241] The sixth sending module is used to send the target UAID evidence and the target authorization agreement evidence to the blockchain authorization evidence device.

[0242] In some embodiments, the target data includes an isolation value and a current timestamp corresponding to the mobile APP;

[0243] The first calculation module includes:

[0244] A first concatenation unit is used to concatenate the isolation value corresponding to the mobile terminal APP and the target mobile phone number to obtain first source data;

[0245] A first calculation unit, configured to obtain stage data based on the first source data;

[0246] A second splicing unit, used for splicing the stage data and the current timestamp to obtain second source data;

[0247] The second calculation unit is configured to obtain a target UAID based on the second source data.

[0248] In some embodiments, the communication request also carries communication content. When the communication request is a text message sending request, the communication content is text message content.

[0249] The first execution module includes:

[0250] A first sending unit, configured to generate an anonymous subscription SMS based on an SMS template and the SMS content, and send the anonymous subscription SMS to a terminal device corresponding to the target mobile phone number through an SMS gateway;

[0251] The eighth sending module includes:

[0252] The second sending unit is used to send a text message sending result to the APP management device.

[0253] In some embodiments, when the communication request is a telephone call request, the first execution module includes:

[0254] A third sending unit is used to send an intermediate number acquisition request to the intermediate number management device, wherein the intermediate number acquisition request carries the target mobile phone number;

[0255] A first receiving unit is used to receive a target intermediate number that is successfully bound to the target mobile phone number and is sent by the intermediate number management device based on the intermediate number acquisition request;

[0256] The eighth sending module includes:

[0257] The fourth sending unit is used to send the target intermediate number to the APP management device.

[0258] Figure 8 A block diagram of a communication authentication device 800 according to an embodiment of the present disclosure is shown, which is applied to an APP management device. The device 800 includes:

[0259] The sixth receiving module 801 is configured to receive the target UAID sent by the mobile terminal APP when the mobile terminal APP responds to the login operation of the target user;

[0260] The first query module 802 is used to query whether the target UAID is stored in the database of the APP management device;

[0261] A tenth sending module 803 is configured to send an authorization login message to the mobile terminal APP if the target UAID is stored in the database of the APP management device;

[0262] The device also includes:

[0263] A twelfth sending module 804 is used to send a communication request to the service management device on the operator side, wherein the communication request carries the target UAID and the authorization agreement signed by the target user;

[0264] The eighth receiving module 805 is used to receive the communication task execution result corresponding to the communication request sent by the operator-side service management device.

[0265] In some embodiments, the apparatus further comprises:

[0266] a seventh receiving module, configured to receive, when the mobile terminal APP responds to the registration operation of the target user, the target UAID sent by the mobile terminal APP and the authorization agreement signed by the target user;

[0267] A second storage module, configured to store the target UAID in a database of the APP management device;

[0268] The eleventh sending module is used to send the target UAID and the authorization agreement signed by the target user to the service management device at the operator side.

[0269] In some embodiments, the communication request also carries communication content. When the communication request is a text message sending request, the communication content is text message content.

[0270] The eighth receiving module comprises:

[0271] The second receiving unit is used to receive the SMS sending result corresponding to the SMS sending request sent by the operator-side service management device.

[0272] In some embodiments, when the communication request is a telephone call request, the eighth receiving module includes:

[0273] The third receiving unit is used to receive the target intermediate number corresponding to the telephone call request sent by the operator-side service management device.

[0274] Fig. 9 An example of a physical structure diagram of an electronic device is shown. The electronic device may be a smart terminal, and its internal structure diagram may be as follows: Fig. 9 As shown. The electronic device includes a processor, a memory and a network interface connected via a system bus. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, the above-mentioned communication authentication method is implemented.

[0275] On the other hand, the present invention also provides a computer storage medium storing a computer program, which implements the above communication authentication method when executed by a processor.

[0276] In another aspect, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium, and when the processor executes the computer instructions, the above communication authentication method is implemented.

[0277] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided by the present invention can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory.

[0278] By way of illustration and not limitation, Random Access Memory (RAM) is available in many forms, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus Direct RAM (RDRAM), Direct Rambus Dynamic RAM (DRDRAM), and Rambus Dynamic RAM (RDRAM).

[0279] It should be noted that the above detailed descriptions are exemplary and are intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present application belongs.

[0280] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should also be understood that when the terms "comprise" and / or "include" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0281] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0282] In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or inherent to these processes, methods, products, or apparatuses.

[0283] For ease of description, spatially relative terms, such as "above", "above", "on the upper surface of", "above", etc., may be used herein to describe the spatial positional relationship between a device or feature and other devices or features as shown in the figure. It should be understood that spatially relative terms are intended to include different orientations of the device in use or operation in addition to the orientation described in the figure. For example, if the device in the accompanying drawings is inverted, the device described as "above other devices or structures" or "above other devices or structures" will be positioned as "below other devices or structures" or "below other devices or structures". Thus, the exemplary term "above" may include both "above" and "below". The device may also be positioned in other different ways, such as rotated 90 degrees or in other orientations, and the spatially relative descriptions used herein are interpreted accordingly.

[0284] In the above detailed description, reference is made to the accompanying drawings, which form a part of this document. In the accompanying drawings, similar symbols typically identify similar components unless the context indicates otherwise. The illustrated embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be used, and other changes may be made, without departing from the spirit or scope of the subject matter presented herein.

[0285] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A communication authentication method, characterized in that: The method is performed by a service management device at an operator side, and includes: Receiving a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries identification information of a target user; Based on the one-key anonymous login request, a number acquisition request is sent to a number acquisition capability device on the operator side, wherein the number acquisition request carries the identification information of the target user; Receiving the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request; Determine the target UAID corresponding to the target mobile phone number based on the target mobile phone number and the correspondence between the mobile phone number and the unified anonymous identifier UAID stored in the database of the service management device on the operator side; Send the target UAID to the mobile APP through the SDK, so that the mobile APP completes the login authentication process based on the target UAID; After sending the target UAID to the mobile APP through the SDK so that the mobile APP completes the login authentication process based on the target UAID, the method further includes: Receive a communication request sent by the APP management device, wherein the communication request carries the target UAID and an authorization agreement signed by the target user; Based on the communication request, a verification request is sent to the blockchain authorization evidence storage device, wherein the verification request carries the target UAID and the authorization agreement signed by the target user; Upon receiving a verification success message sent by the blockchain authorization evidence storage device based on the verification request, determining a target mobile phone number corresponding to the target UAID based on the target UAID and a correspondence between mobile phone numbers and UAIDs stored in a database of the operator-side service management device; Based on the target mobile phone number, executing a communication task corresponding to the communication request; Sending the communication task execution result to the APP management device; Sending a communication task to the blockchain authorized evidence storage device to perform evidence storage; Before receiving the one-key anonymous login request sent by the mobile application APP through the software development kit SDK, the method also includes: Receiving, through the SDK, a one-key anonymous registration request sent by the mobile terminal APP, wherein the one-key anonymous registration request carries identification information of the target user; Based on the one-key anonymous registration request, sending a number acquisition request to a number acquisition capability device on the operator side, wherein the number acquisition request carries the identification information of the target user; Receiving the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request; Calculate the target UAID based on the target data and the target mobile phone number; Storing the correspondence between the target mobile phone number and the target UAID in a database of the service management device on the operator side; Send the target UAID to the mobile APP through the SDK, so that the mobile APP completes the registration and authentication process based on the target UAID; Receiving the target UAID and the authorization agreement signed by the target user sent by the APP management device; Obtain the target UAID evidence based on the target UAID and the generation time of the target UAID, and obtain the target authorization agreement evidence based on the authorization agreement signed by the target user; The target UAID certificate and the target authorization agreement certificate are sent to the blockchain authorization certificate device.

2. A communication authentication method, characterized in that: Executed by an APP management device, the method includes: When the mobile terminal APP responds to the login operation of the target user, receiving the target UAID sent by the mobile terminal APP; Query whether the target UAID is stored in the database of the APP management device; If the target UAID is stored in the database of the APP management device, sending an authorization login message to the mobile terminal APP; In the case where the target UAID is stored in the database of the APP management device, after sending an authorization login message to the mobile terminal APP, the method further includes: Sending a communication request to the service management device at the operator side, wherein the communication request carries the target UAID and the authorization agreement signed by the target user; receiving a communication task execution result corresponding to the communication request sent by the service management device at the operator side; In the case where the mobile terminal APP responds to the login operation of the target user, before receiving the target UAID sent by the mobile terminal APP, the method further includes: When the mobile terminal APP responds to the registration operation of the target user, receiving the target UAID sent by the mobile terminal APP and the authorization agreement signed by the target user; Storing the target UAID in a database of the APP management device; The target UAID and the authorization agreement signed by the target user are sent to the service management device at the operator side.

3. A communication authentication device, characterized in that: Applied to a service management device on an operator side, the device is used to implement the communication authentication method according to claim 1, and the device comprises: A first sending module is used to receive a one-key anonymous login request sent by a mobile application APP through a software development kit SDK, wherein the one-key anonymous login request carries identification information of a target user; A second sending module is used to send a number acquisition request to the operator-side number acquisition capability device based on the one-key anonymous login request, wherein the number acquisition request carries the identification information of the target user; A first receiving module is used to receive the target mobile phone number of the target user sent by the operator-side number acquisition capability device based on the number acquisition request; A first determination module is used to determine a target UAID corresponding to the target mobile phone number based on the target mobile phone number and a correspondence between the mobile phone number and the unified anonymous identifier UAID stored in a database of the service management device on the operator side; The third sending module is used to send the target UAID to the mobile terminal APP through the SDK, so that the mobile terminal APP completes the login authentication process based on the target UAID; The device also includes: A fifth receiving module, configured to receive a communication request sent by the APP management device, wherein the communication request carries the target UAID and the authorization agreement signed by the target user; A seventh sending module is used to send a verification request to the blockchain authorization evidence storage device based on the communication request, wherein the verification request carries the target UAID and the authorization agreement signed by the target user; A sixth receiving module, configured to determine a target mobile phone number corresponding to the target UAID based on the target UAID and the correspondence between the mobile phone number and the UAID stored in the database of the operator-side service management device, upon receiving a verification success message sent by the blockchain authorization evidence storage device based on the verification request; A first execution module, configured to execute a communication task corresponding to the communication request based on the target mobile phone number; An eighth sending module, used to send the communication task execution result to the APP management device; The ninth sending module is used to send a communication task to the blockchain authorized evidence storage device to execute the evidence.

4. A communication authentication device, characterized in that: Applied to an APP management device, the device is used to implement the communication authentication method according to claim 2, and the device includes: A sixth receiving module, configured to receive a target UAID sent by the mobile terminal APP when the mobile terminal APP responds to a login operation of the target user; A first query module, used to query whether the target UAID is stored in the database of the APP management device; A tenth sending module, configured to send an authorization login message to the mobile terminal APP if the target UAID is stored in the database of the APP management device; The device also includes: A twelfth sending module, configured to send a communication request to the service management device on the operator side, wherein the communication request carries the target UAID and the authorization agreement signed by the target user; An eighth receiving module is used to receive a communication task execution result corresponding to the communication request sent by the operator-side service management device.

5. An electronic device, characterized in that: The invention comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the communication authentication method as claimed in claim 1 when executed by the processor, or implements the steps of the communication authentication method as claimed in claim 2 when executed by the processor.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the steps of the communication authentication method according to claim 1 are implemented, or when the computer program is executed by the processor, the steps of the communication authentication method according to claim 2 are implemented.

7. A computer program product, characterized in that The method comprises computer instructions, which implement the steps of the communication authentication method according to claim 1 when the computer instructions are executed by a processor, or implement the steps of the communication authentication method according to claim 2 when the computer instructions are executed by the processor.

Images