CN113572827A

CN113572827A - Registration processing method and device

Info

Publication number: CN113572827A
Application number: CN202110789653.2A
Authority: CN
Inventors: 耿浩; 苏千秋; 沈凌楠; 陈重远; 施冬梅; 许觅秋; 高俊树; 巩鑫
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: AlipayCom Co ltd
Priority date: 2021-07-13
Filing date: 2021-07-13
Publication date: 2021-10-29
Anticipated expiration: 2041-07-13
Also published as: CN113572827B

Abstract

The embodiment of the specification provides a registration processing method and a registration processing device, wherein the registration processing method comprises the following steps: responding to the registration call of the third-party server, generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal; according to the protocol signing instruction submitted by the user terminal, signing the authorization protocol corresponding to each protocol access entrance; and sending the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing so as to register the user according to the user information.

Description

Registration processing method and device

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a registration processing method and apparatus.

Background

With the development of internet and information technology, the living habits of users are greatly changed, the experience and the handling of a plurality of off-line services can be handled on line, in order to maintain the rights and interests of the users and organizations, the responsibility and obligation of both parties need to be divided, and the signing of an on-line agreement needs to be carried out. Furthermore, with the increasing popularity of informatization, services are no longer just a single simple system or a single complex system, and may also involve multi-party platform interfacing. Therefore, how to realize the multi-party transmission of the user information under the condition of ensuring the security of the user information becomes a problem which is increasingly valued by the user and the multi-party platform.

Disclosure of Invention

One or more embodiments of the present specification provide a registration processing method. The registration processing method comprises the following steps: and generating an agreement signing page containing a plurality of agreement access entries in response to the registration call of the third-party server and sending the agreement signing page to the user terminal. And signing the authorization protocol corresponding to each protocol access entry according to the protocol signing instruction submitted by the user terminal. And sending the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing so as to register the user according to the user information.

One or more embodiments of the present specification provide another registration processing method, including: and displaying the first service page through the sub-application according to an access instruction submitted by a user aiming at the sub-application in the host application. And if the registration instruction of the user for the sub-application is detected, submitting the registration instruction to a third-party server of the sub-application. And receiving and displaying the protocol signing page sent by the application server of the host application. And acquiring an agreement signing instruction of the user, submitting the agreement signing instruction to the application server, and displaying a second service page based on the sub-application after the registration is completed.

One or more embodiments of the present specification provide a registration processing apparatus including: and the page generation module is configured to generate and send an agreement signing page containing a plurality of agreement access entries to the user terminal in response to the registration call of the third-party server. And the signing processing module is configured to sign the authorization protocol corresponding to each protocol access entrance according to the protocol signing instruction submitted by the user terminal. And the information sending module is configured to send the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing so as to perform user registration according to the user information.

One or more embodiments of the present specification provide another registration processing apparatus, including: and the first page presentation module is configured to present the first service page through the sub-application according to an access instruction submitted by a user for the sub-application in the host application. And the registration instruction submitting module is configured to submit the registration instruction to a third-party server of the sub-application if the registration instruction of the user for the sub-application is detected. And the signed page display module is configured to receive and display the protocol signed page transmitted by the application server of the host application. And the second page display module is configured to acquire an agreement signing instruction of the user, submit the agreement signing instruction to the application server, and display a second service page based on the sub-application after the registration is completed.

One or more embodiments of the present specification provide a registration processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and generating an agreement signing page containing a plurality of agreement access entries in response to the registration call of the third-party server and sending the agreement signing page to the user terminal. And signing the authorization protocol corresponding to each protocol access entry according to the protocol signing instruction submitted by the user terminal. And sending the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing so as to register the user according to the user information.

One or more embodiments of the present specification provide another registration processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and displaying the first service page through the sub-application according to an access instruction submitted by a user aiming at the sub-application in the host application. And if the registration instruction of the user for the sub-application is detected, submitting the registration instruction to a third-party server of the sub-application. And receiving and displaying the protocol signing page sent by the application server of the host application. And acquiring an agreement signing instruction of the user, submitting the agreement signing instruction to the application server, and displaying a second service page based on the sub-application after the registration is completed.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following: and generating an agreement signing page containing a plurality of agreement access entries in response to the registration call of the third-party server and sending the agreement signing page to the user terminal. And signing the authorization protocol corresponding to each protocol access entry according to the protocol signing instruction submitted by the user terminal. And sending the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing so as to register the user according to the user information.

One or more embodiments of the present specification provide another storage medium storing computer-executable instructions that, when executed, implement the following: and displaying the first service page through the sub-application according to an access instruction submitted by a user aiming at the sub-application in the host application. And if the registration instruction of the user for the sub-application is detected, submitting the registration instruction to a third-party server of the sub-application. And receiving and displaying the protocol signing page sent by the application server of the host application. And acquiring an agreement signing instruction of the user, submitting the agreement signing instruction to the application server, and displaying a second service page based on the sub-application after the registration is completed.

Drawings

In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise;

fig. 1 is a flowchart of a registration processing method according to one or more embodiments of the present disclosure;

FIG. 2 is a schematic diagram of an agreement signing page provided by one or more embodiments of the present specification;

FIG. 3 is a schematic diagram of a message verification alert page provided in one or more embodiments of the present description;

fig. 4 is a flowchart illustrating a registration processing method applied to a network car booking service scenario according to one or more embodiments of the present disclosure;

FIG. 5 is a flowchart of another method for processing registration processing according to one or more embodiments of the present disclosure;

fig. 6 is a flowchart illustrating a registration processing method applied to a network appointment service scenario according to one or more embodiments of the present disclosure;

fig. 7 is a schematic diagram of a registration processing apparatus according to one or more embodiments of the present disclosure;

fig. 8 is a schematic diagram of another registration processing apparatus provided in one or more embodiments of the present disclosure;

fig. 9 is a schematic structural diagram of a registration processing apparatus according to one or more embodiments of the present specification;

fig. 10 is a schematic structural diagram of another registration processing apparatus according to one or more embodiments of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

An embodiment of a registration processing method provided in this specification:

referring to fig. 1, which shows a processing flow chart of a registration processing method provided in this embodiment, referring to fig. 2, which shows a schematic diagram of an agreement signing page provided in this embodiment, referring to fig. 3, which shows a schematic diagram of a message verification reminding page provided in this embodiment, referring to fig. 4, which shows a processing flow chart of a registration processing method applied to a network appointment service scenario provided in this embodiment.

Referring to fig. 1, the registration processing method provided in this embodiment specifically includes steps S102 to S106.

Step S102, responding to the register call of the third-party server, generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal.

In the registration processing method provided by this embodiment, in the process of performing user registration through a sub-application in a host application, an application server of the host application displays a page including an information authorization protocol and a service authorization protocol to a user, so that the user can authorize by one key, after obtaining a protocol signing instruction of the user, signs the information authorization protocol and the service authorization protocol, generates corresponding authorization tokens according to the authorization protocols, and sends the obtained user information to a third-party server of the sub-application according to the information authorization token, so that the third-party server performs user registration based on the user information, sends the service authorization token to the third-party server, so that the third-party server sends a service processing request according to the service authorization token, thereby implementing one-key registration authorization of the user, and improving the perception degree of the user to the sub-application in the host application, and the user experience is improved.

In this embodiment, a user may access a sub-application in a host application through the host application and perform a service application through the sub-application. The sub-applications include a program module or a service module which is borne by the host application and runs in dependence on the host application, for example, a vehicle reservation applet which is loaded and run by a third party payment application, and a user can register and reserve a vehicle by accessing the vehicle reservation applet in the third party payment application. The third-party server is a sub-application server, such as a vehicle reservation server of a small program providing the online car booking service.

The registration processing method provided in this embodiment is applied to an application server, that is: the server hosting the application, the registration processing method provided by another method embodiment provided below, is applied to the user terminal, that is: the user terminal running the host application, the registration processing method provided by this embodiment and the registration processing method provided by another method embodiment described below are mutually matched in the execution process, so that please refer to the corresponding contents of the another method embodiment described below in this embodiment.

Optionally, the multiple authorization protocols corresponding to the multiple protocol access entries include: a message authorization protocol and at least one service authorization protocol. The information authorization protocol comprises an authorization instruction for transmitting the user information to the third-party server; the service authorization instruction comprises an authorization instruction for user service information required to be utilized in a service process; for example: a withholding authorization protocol, a location reading authorization protocol, etc.

In practical applications, when a user uses a service application, the user needs to register in order to ensure the information security of the user and improve the service experience of the user, and also in order to improve the effectiveness and convenience of service management.

In specific implementation, a user accesses a sub-application in a host application through a user terminal, the sub-application displays a service home page to the user, the user can submit a service request through the service home page, in order to guarantee information security of the user and improve convenience of service management, loss of the service application caused by malicious requests of the user is avoided, and the user can be provided with service after registration. After the service home page is displayed to the user, the user can submit a service request through the service home page, the third-party server of the sub-application needs to judge whether the user is a registered user or not under the condition that the service request is received, and if the user is not registered, the application server of the host application is called to register the user after a registration instruction is obtained. In the embodiment, a user terminal displays a first service page through a sub-application according to an access instruction submitted by a user aiming at the sub-application in a host application; the first service page comprises a service home page displayed through the sub-application when the user accesses the sub-application, and also comprises a service request page of the sub-application. And if the registration instruction of the user for the sub-application is detected, submitting the registration instruction to a third-party server of the sub-application.

Specifically, in the process of submitting a registration instruction, a user terminal firstly collects a service request of the user for the sub-application and submits the service request to the third-party server; then receiving and displaying the registration prompt sent by the third-party server; and finally, collecting a registration instruction entered by the user through the registration prompt and submitting the registration instruction to the third-party server.

Further, in order to determine whether a user submitting an access request is a new user, the third-party server obtains a registration instruction by cooperating with the user terminal, in an optional implementation manner provided in this embodiment, the following manner is specifically adopted to determine whether the user is a new user:

inquiring whether the user is a registered user of the sub-application or not according to a service request submitted by the user through the sub-application;

if so, performing service processing based on the service request;

if not, displaying a registration prompt through the sub-application, and initiating the registration call after acquiring a registration instruction submitted by the user.

Specifically, a user submits an access instruction to a sub-application in a host application through a user terminal, and when the user terminal detects that the user accesses the sub-application in the host application, a first service page is displayed through the sub-application according to the access instruction submitted by the user aiming at the sub-application in the host application; if the service request of the user for the sub-application is collected, submitting the service request to a third-party server of the sub-application, judging whether the user is a registered user of the sub-application or not by the third-party server, and if not, displaying a registration prompt to the user through the sub-application; and the user terminal submits to the third-party server when detecting the registration instruction of the user, and the third-party server calls the application server of the host application to cooperate with the user registration after receiving the registration instruction.

For example, in the third-party payment application, a sub-application of the car appointment service is loaded. The method comprises the steps that a user terminal obtains a network car booking service submitting access instruction of a user in a third-party payment application, and a service home page of the network car booking service is displayed to the user; when the service request submitted by the user through the home page of the user is collected, the service request is sent to a car booking server of the car booking service, the car booking server inquires whether the user has a registration identifier or not according to the service request, and if not, registration reminding is displayed to the user through sub-application of the car booking service; and the user terminal submits the registration instruction to the online car appointment server when detecting the registration instruction submitted by the user for the registration prompt, and the online car appointment server calls a payment server of the third-party payment application to acquire the authorization of the user according to the registration instruction.

In order to ensure the effectiveness of the user and avoid the loss of the service application caused by the user registration for the user with an abnormal state, in an optional implementation manner provided in this embodiment, before generating and sending the protocol signing page including a plurality of protocol access entries to the user terminal, the following manner is adopted to perform the trust verification on the user:

responding to registration call of the third-party server of the sub-application, transmitting the user identification of the user carried by the registration call into a trusted identification interface for trusted identification, and acquiring a returned identification result;

judging whether the identification result meets a credible condition or not;

if yes, executing the process of generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal;

if not, sending a message verification prompt containing verification information to the user terminal through the host application;

after detecting the communication data sent by the third-party communication platform, verifying whether a source communication address in the communication data is the communication address of the user and/or verifying whether the communication data carries the verification information;

if not, no processing is carried out.

And the communication data is sent after the third-party communication platform detects that the target communication address is accessed.

Specifically, the target communication address is a communication address specified by an application server of the host application. The communication data comprises a source communication address, verification information and a target communication address of the user read based on the user identification; responding to the calling of the third-party server, calling a trusted identification interface to perform trusted identification, and acquiring a returned identification result; judging whether the credibility result is smaller than a credibility threshold value, if so, generating a protocol signing page comprising a plurality of protocol access entries and sending the protocol signing page to the user terminal; if the value is larger than or equal to the credibility threshold value, sending a message verification prompt containing verification information to the user terminal through the host application so as to authenticate the source communication address of the user, and generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal after the authentication is passed.

In this embodiment, after sending the message authentication prompt to the user terminal, the user terminal performs the following steps:

receiving and displaying a message verification prompt which is sent by the application server and contains verification information;

sending a communication request to a third-party communication platform according to the verification information input by the user and a sending instruction submitted after the target communication address;

the communication request comprises communication data consisting of the verification information, the target communication address and the source communication address of the user.

For example, in response to registration call of a third-party server, a user identifier of a user is input into a trusted identification interface for trusted identification, and a returned identification result is obtained; if the identification result is smaller than the credible threshold, generating a protocol signing page shown in figure 2 and sending the protocol signing page to the user terminal; if the identification result is greater than or equal to the credible threshold, generating a message verification prompt based on the verification information, the source communication number of the user and the specified target communication number, sending the message verification prompt to the user terminal through the host application, receiving the message verification prompt by the user terminal, displaying a message verification prompt page shown in the figure 3, and sending a short message containing the verification information to the target communication number through the source communication number by the user. According to communication data sent by a communication operation platform after detecting that a target communication number is accessed, verifying whether a source communication number in the communication data is a source communication number of a user or not and verifying whether the communication data carries verification information or not; if yes, the agreement signing page shown in fig. 2 is displayed to the user, and if not, no processing is performed.

In the process, after a protocol signing page containing a plurality of protocol access inlets is generated and sent to the user terminal through the host application, the user terminal receives and displays the protocol signing page sent by the application server of the host application, acquires a protocol signing instruction of the user and submits the protocol signing instruction to the application server.

It should be noted that, the protocol signing page needs to render and sign a guide diagram and/or text of the service authorization protocol, so as to guide the user to sign the service authorization protocol; as shown in fig. 2, the agreement signing page configuration authorization component 201 and the agreement signing control 202 also render access entries of the information authorization protocol and the service authorization protocol, and a user can view protocol contents by triggering the information authorization protocol or the service authorization protocol. Wherein, after the authorization component 201 is triggered, it indicates that the user determines that the service authorization agreement is signed. Specifically, if the user triggers the agreement signing control 202 on the basis of selecting the authorization component 201, it indicates that the user submits a signing instruction for the information authorization agreement and the service authorization agreement; if the user triggers the agreement signing control 202 on the basis of not selecting the authorization component 201, indicating that the user submits a signing instruction aiming at the information authorization agreement; if the user does not trigger the agreement signing control 202 on the basis of selecting the authorization component 201, the user is indicated to submit a signing instruction for the service authorization agreement.

And step S104, according to the protocol signing instruction submitted by the user terminal, signing the authorization protocol corresponding to each protocol access entrance.

The multiple authorization protocols corresponding to the multiple protocol access entries provided by this embodiment include: an information authorization protocol and at least one service authorization protocol, in an optional implementation manner provided by this embodiment, in a process of signing an authorization protocol corresponding to each protocol access entry, signing the information authorization protocol based on the user identifier, and signing the at least one service authorization protocol based on user service information.

In specific implementation, in order to further control the abnormal user, signing preprocessing can be performed after the user triggers the authorization component. Based on that, in an optional implementation manner provided in this embodiment, in a process of signing an authorization protocol corresponding to each protocol access entry according to a protocol signing instruction submitted by the user terminal, the following operations are performed:

if a preprocessing instruction sent by the user terminal is received, signing preprocessing of the at least one service authorization agreement is carried out; the preprocessing instruction is submitted after the user terminal detects that an authorization component configured by the agreement signing page is selected;

if the preprocessing is successful, signing the information authorization agreement according to the agreement signing instruction;

and if the preprocessing fails, sending a preprocessing failure prompt to the user terminal so that the user terminal receives the preprocessing failure prompt sent by the application server and displays the preprocessing failure prompt through the host application.

Specifically, if a preprocessing instruction submitted by a user terminal after detecting that an authorization component configured by an agreement signing page is triggered is received, signing preprocessing is carried out on a service authorization agreement; if the preprocessing is successful, generating a service authorization token based on the protocol identification of the service authorization protocol, and signing the information authorization protocol when detecting a protocol signing instruction submitted by the user terminal after a protocol signing control configured on a protocol signing page is triggered; and if the preprocessing fails, sending a preprocessing failure prompt to the user terminal so that the user terminal can display the failure prompt and cancel the selection of the authorization component. The user may re-select the authorization component.

As shown in fig. 2, if the configured authorization component 201 is selected, receiving a preprocessing instruction submitted by the user terminal, performing signature preprocessing on the service authorization agreement based on the preprocessing instruction, and if the preprocessing is successful, generating a service authorization token based on the agreement identifier of the signed service authorization agreement; receiving a protocol signing instruction submitted by a user terminal after a user triggers the protocol signing control 202; and signing the information authorization protocol according to the protocol signing instruction, and generating an information authorization token according to the signed protocol identifier of the information authorization protocol.

In order to improve convenience of providing services for a user by subsequent sub-applications and enable a third-party server to acquire user information for user registration, after signing and processing an authorization protocol corresponding to each protocol access entry, the user information and a service authorization token need to be sent to the third-party server.

In an optional implementation manner provided by this embodiment, after signing the service authorization agreement, the following operations are performed:

sending at least one service authorization token obtained after signing processing of the at least one service authorization agreement to the third-party server; the third-party server performs service processing according to one or more of the at least one service authorization token;

wherein any one of the at least one service authorization token is generated according to a protocol identifier of a corresponding service authorization protocol.

And step S106, sending the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing, so as to register the user according to the user information.

The multiple authorization protocols corresponding to the multiple protocol access entries provided in the foregoing embodiment include: the method comprises the steps that in the process of sending acquired user information to the third-party server according to at least one of a plurality of authorization tokens acquired after signing processing, the user information is firstly read according to a user identifier of a user, and then the user information is sent to the third-party server based on the information authorization token acquired after signing processing of the information authorization protocol.

It should be noted that, after signing the information authorization protocol and the service authorization protocol, the user information required for the user registration of the third-party server is sent to the third-party server based on the information authorization protocol, and the service authorization token is sent to the third-party server. And sending the user information to the third-party server based on the information authorization token so that the third-party server performs user registration based on the user information. And sending the service authorization token to the third-party server so that the third-party server calls the application server to perform service processing based on the service authorization token. After the third-party server registers the user, if the registration fails, a failure prompt is sent to the user terminal through the sub-application; and if the registration is successful, sending a success prompt to the user terminal through the sub-application so that the user terminal can display the second service page. The second service page may be the first service page, or may be a service page based on the first service page and a successful page rendering.

In specific implementation, after the service authorization token is sent to the third-party server, the third-party server may invoke the application server to perform service processing according to the service authorization token. In an optional implementation manner provided by this embodiment, the service processing request of the third-party server is responded by adopting the following manner:

receiving a service processing request sent by the third-party server;

reading user service information recorded in a service authorization protocol corresponding to the target service authorization token according to the target service authorization token carried in the service processing request;

and performing service processing based on the user service information and the processing information carried in the service processing request, and sending a service processing response to the third-party server.

For example, a withholding processing request sent by the third-party server is received, a withholding channel recorded in the withholding authorization protocol is read according to a withholding authorization token carried in the withholding processing request, withholding processing is performed on withholding cost in the withholding processing request based on the withholding channel, and a withholding processing result is sent to the third-party server.

In addition, when the user submits the agreement signing instruction and fails to send the user information and the service authorization token to the third-party server due to various reasons, the information authorization token and the service authorization token are stored, so that the information authorization token and the service authorization token can be obtained when the user is registered and called next time, and the user does not need to re-authorize. Based on this, in an optional implementation manner provided in this embodiment, when a secondary registration call is obtained, first, whether the information authorization token and the at least one service authorization token of the user are stored is queried according to the secondary registration call of the third-party server; if so, sending the user information to the third-party server based on the information authorization token, and sending the at least one service authorization token to the third-party server; if not, generating an agreement signing page containing a plurality of agreement access entries and sending the agreement signing page to the user terminal.

The following further describes the registration processing method provided in this embodiment by taking an application of the registration processing method provided in this embodiment in a car-booking service scenario of the internet as an example, and referring to fig. 4, the registration processing method applied in the car-booking service scenario of the internet specifically includes steps S402 to S416.

Step S402, responding to the calling of the vehicle reservation server, transmitting the user identification into the trusted identification interface for trusted identification, and acquiring a returned identification result.

Step S404, judging whether the identification result meets a credible condition;

if yes, go to step S406 to step S408;

and if not, sending a message verification prompt carrying verification information to the user terminal.

Step S406, generating a protocol signing page of the access entrance containing the information authorization protocol and the withholding authorization protocol, and issuing the page to the user terminal.

Step S408, signing preprocessing is carried out on the withholding authorization protocol according to the preprocessing instruction submitted by the user terminal;

if the preprocessing is successful, executing step S410 to step S416;

and if the preprocessing fails, sending a preprocessing failure prompt to the user terminal.

And step S410, generating a withholding authorization token based on the signed protocol identification of the withholding authorization protocol.

Step S412, acquiring the agreement signing instruction submitted by the user terminal, and signing the information authorization agreement according to the agreement signing instruction.

And step S414, generating an information authorization token according to the signed protocol identifier of the information authorization protocol.

In step S416, the withholding authorization token is sent to the vehicle reservation server, and the read user information is sent to the vehicle reservation server based on the information authorization token.

After that, the vehicle reservation server performs a user registration process of the vehicle reservation service for the user based on the user information after receiving the user information transmitted from the application server. In addition, in the process of payment processing of the vehicle reservation order of the user after the vehicle reservation server user successfully registers, the vehicle reservation order and the withholding authorization token are sent to the application server, the application server verifies the withholding authorization token, and the payment processing of the vehicle reservation order is carried out after the verification is passed.

In summary, in the registration processing method provided in this embodiment, a protocol signing page including a plurality of protocol access entries is generated and sent to a user terminal in response to registration invocation of a third-party server, then, according to a protocol signing instruction submitted by the user terminal, an authorization protocol corresponding to each protocol access entry is signed, and finally, according to at least one of a plurality of authorization tokens obtained after the signing processing, the obtained user information is sent to the third-party server to perform user registration according to the user information, so that one-key registration authorization is implemented, use experience of the user on sub-applications in the host application is improved, and identity security of the user performing the user registration is ensured by performing trusted identification on the user.

Another embodiment of a registration processing method provided in this specification:

referring to fig. 5, which shows a processing flow chart of a registration processing method provided in this embodiment, referring to fig. 2, which shows a schematic diagram of an agreement signing page provided in this embodiment, referring to fig. 3, which shows a schematic diagram of a message verification reminding page provided in this embodiment, referring to fig. 6, which shows a processing flow chart of a registration processing method applied to a network appointment service scenario provided in this embodiment.

Referring to fig. 5, the registration processing method provided in this embodiment specifically includes steps S502 to S508.

Step S502, according to an access instruction submitted by a user aiming at the sub application in the host application, a first service page is displayed through the sub application.

In practical applications, in some service industries, such as the network appointment industry. The authorization of the identity information of the user and the authorization of the deduction service are realized as two processes, and the user information needs to be actively input by the user.

In this embodiment, a user may access a sub-application in a host application through the host application, and perform a service application through the sub-application, where the host application includes an application capable of bearing the sub-application, such as a third party payment application. The first service page comprises a service home page displayed through the sub-application when the user accesses the sub-application, and also comprises a service request page of the sub-application.

In specific implementation, a user accesses a sub-application in a host application through a user terminal, the sub-application displays a service home page to the user, the user can submit a service request through the service home page, in order to guarantee information security of the user and improve convenience of service management, loss of the service application caused by malicious requests of the user is avoided, and the user can be provided with service after registration. After the service home page is displayed to the user, the user can submit a service request through the service home page, the third-party server of the sub-application needs to judge whether the user is a registered user or not under the condition that the service request is received, and if the user is not registered, the application server of the host application is called to register the user after a registration instruction is obtained. In the embodiment, a first service page is displayed through a sub-application according to an access instruction submitted by a user aiming at the sub-application in a host application; if the registration instruction of the user for the sub-application is detected, the following step S504 is executed, and the registration instruction is submitted to the third-party server of the sub-application.

Step S504, submitting the registration instruction to the third-party server of the sub-application.

And the third-party server is a server of the sub-application in the host application.

In an optional implementation manner provided by this embodiment, the submission of the registration instruction is specifically performed in the following manner:

collecting the service request of the user for the sub-application and submitting the service request to the third-party server;

receiving and displaying a registration prompt sent by the third-party server;

and collecting a registration instruction entered by the user through the registration prompt and submitting the registration instruction to the third-party server.

Further, in order to determine whether the user submitting the access request is a new user, after acquiring the registration instruction, the third-party server determines whether the user is a new user by the following method: firstly, according to a service request submitted by the user through the sub-application, inquiring whether the user is a registered user of the sub-application; if so, performing service processing based on the service request; if not, displaying a registration prompt through the sub-application, and initiating the registration call after acquiring a registration instruction submitted by the user.

Specifically, when it is detected that a user accesses a sub-application in a host application, a first service page is displayed through the sub-application according to an access instruction submitted by the user for the sub-application in the host application; if the service request of the user for the sub-application is collected, submitting the service request to a third-party server of the sub-application, judging whether the user is a registered user of the sub-application or not by the third-party server, and if not, displaying a registration prompt to the user through the sub-application; and the user terminal submits to the third-party server when detecting the registration instruction of the user, and the third-party server calls the application server of the host application to cooperate with the user registration after receiving the registration instruction.

For example, in the third-party payment application, a sub-application of the car appointment service is loaded. Acquiring a network appointment service submission access instruction of a user in a third-party payment application, and displaying a service home page of the network appointment service to the user; when the service request submitted by the user through the home page of the user is collected, the service request is sent to a car booking server of the car booking service, the car booking server inquires whether the user has a registration identifier or not according to the service request, and if not, registration reminding is displayed to the user through sub-application of the car booking service; and the user terminal submits the registration instruction to the online car appointment server when detecting the registration instruction submitted by the user for the registration prompt, and the online car appointment server calls a payment server of the third-party payment application to acquire the authorization of the user according to the registration instruction.

In particular, since the user information belongs to the user privacy to a certain extent, the server of the host application needs to acquire the authorization of the user to transmit the user information to the third-party server to ensure the information security of the user.

Therefore, in order to ensure the information security and resource security of the user, the application server needs to acquire the protocol signing instruction of the user, and specifically, the application server generates and sends to the user terminal a protocol signing page containing a plurality of protocol access entries in response to the registration call of the third-party server. The plurality of authorization protocols corresponding to the plurality of protocol access entries include: a message authorization protocol and at least one service authorization protocol. The information authorization protocol comprises an authorization instruction for transmitting the user information to the third-party server; the service authorization instruction comprises an authorization instruction for user service information required to be utilized in a service process; for example: a withholding authorization protocol, a location reading authorization protocol, etc.

Further, in order to ensure the validity of the user and avoid the loss of service application caused by user registration of the user with an abnormal state, before the application server generates a protocol signing page including a plurality of protocol access entries and sends the protocol signing page to the user terminal, the application server needs to perform trusted verification on the user, in this embodiment, the application server performs trusted verification on the user in the following manner: responding to registration call of the third-party server of the sub-application, transmitting the user identification of the user carried by the registration call into a trusted identification interface for trusted identification, and acquiring a returned identification result; judging whether the identification result meets a credible condition or not; if yes, executing the process of generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal; if not, sending a message verification prompt containing verification information to the user terminal through the host application; after detecting the communication data sent by the third-party communication platform, verifying whether a source communication address in the communication data is the communication address of the user and/or verifying whether the communication data carries the verification information; if yes, executing the process of generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal; if not, no processing is carried out. And the communication data is sent after the third-party communication platform detects that the target communication address is accessed.

Specifically, the target communication address is a communication address specified by an application server of the host application. The communication data comprises a source communication address, verification information and a target communication address of the user read based on the user identification; the application server responds to the calling of the third-party server, calls the trusted identification interface to carry out trusted identification, and acquires a returned identification result; judging whether the credibility result is smaller than a credibility threshold value, if so, generating a protocol signing page comprising a plurality of protocol access entries and sending the protocol signing page to the user terminal; if the value is larger than or equal to the credibility threshold value, sending a message verification prompt containing verification information to the user terminal through the host application so as to authenticate the source communication address of the user, and generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal after the authentication is passed.

In this embodiment, after the message verification reminder is obtained, the following steps are performed:

For example, the application server responds to registration call of a third-party server, inputs the user identification of the user into a trusted identification interface for trusted identification, and acquires a returned identification result; if the identification result is smaller than the credible threshold, the user terminal receives and displays the protocol signing page shown in the figure 2; if the identification result is greater than or equal to the credible threshold, receiving a message verification prompt generated by the application server based on the verification information, the source communication number of the user and the specified target communication number through the host application, displaying a message verification prompt page as shown in fig. 3, and enabling the user to send a short message containing the verification information to the target communication number through the source communication number. The application server checks whether a source communication number in the communication data is a source communication number of a user according to the communication data sent by the communication operation platform after detecting that a target communication number is accessed, and checks whether the communication data carries verification information; if yes, showing the agreement signing page shown in FIG. 2 to the user; if not, no processing is carried out.

Step S506, receiving and displaying the protocol signing page issued by the application server of the host application.

Step S508, acquiring the agreement signing instruction of the user, submitting the agreement signing instruction to the application server, and displaying a second service page based on the sub-application after the registration is completed.

And submitting the protocol signing instruction to the application server after the protocol signing instruction of the user is obtained, so that the application server signs the authorization protocol corresponding to each protocol access entry, and sends the obtained user information to the third-party server according to at least one of a plurality of authorization tokens obtained after signing processing, so as to register the user according to the user information.

In particular, in order to further control the abnormal user, the application server may perform the pre-signing process after the user triggers the authorization component. In an optional implementation manner provided by this embodiment, the following manner is adopted to implement the preprocessing:

if the user is detected to select the authorization component configured by the agreement signing page, submitting a preprocessing instruction to the application server so that the application server performs signing preprocessing on the service authorization agreement;

and receiving a preprocessing failure prompt sent by the application server and displaying the preprocessing failure prompt through the host application.

Based on this, the application server executes the following operations in the process of signing and processing the authorization protocol corresponding to each protocol access entry according to the protocol signing instruction submitted by the user terminal:

Specifically, if the application server receives a preprocessing instruction submitted by the user terminal after detecting that an authorization component configured by the agreement signing page is triggered, signing preprocessing is carried out on the service authorization agreement; if the preprocessing is successful, generating a service authorization token based on the protocol identification of the service authorization protocol, and signing the information authorization protocol when detecting a protocol signing instruction submitted by the user terminal after a protocol signing control configured on a protocol signing page is triggered; and if the preprocessing fails, sending a preprocessing failure prompt to the user terminal so that the user terminal can display the failure prompt and cancel the selection of the authorization component. The user may re-select the authorization component.

As shown in fig. 2, if it is detected that the configured authorization component 201 is selected, a preprocessing instruction is submitted to the application server, so that the application server performs signature preprocessing on the service authorization agreement based on the preprocessing instruction, and if the preprocessing is successful, a service authorization token is generated based on the agreement identifier of the signed service authorization agreement; and if the configured protocol signing control 202 is triggered, submitting a protocol signing instruction to the application server so that the application server signs the information authorization protocol according to the protocol signing instruction and generates an information authorization token according to the signed protocol identifier of the information authorization protocol.

In order to improve convenience of providing services for a user by subsequent sub-applications and enable a third-party server to obtain user information for user registration, the application server needs to send the user information and a service authorization token to the third-party server after signing and processing an authorization protocol corresponding to each protocol access entry.

Based on this, after the application server signs the service authorization agreement, the following operations are executed:

The multiple authorization protocols corresponding to the multiple protocol access entries provided in the foregoing embodiment include: the method comprises an information authorization protocol and at least one service authorization protocol, wherein in the process that an application server sends acquired user information to a third-party server according to at least one of a plurality of authorization tokens acquired after signing processing, the application server firstly reads the user information according to a user identifier of a user, and then sends the user information to the third-party server based on the information authorization token acquired after signing processing of the information authorization protocol.

It should be noted that, after signing the information authorization protocol and the service authorization protocol, the application server sends, to the third-party server, the user information required for the third-party server to perform user registration based on the information authorization protocol, and sends the service authorization token to the third-party server. And sending the user information to the third-party server based on the information authorization token so that the third-party server performs user registration based on the user information. And sending the service authorization token to the third-party server so that the third-party server calls the application server to perform service processing based on the service authorization token. After the third-party server registers the user, if the registration fails, a failure prompt is sent to the user terminal through the sub-application; and if the registration is successful, sending a success prompt to the user terminal through the sub-application so that the user terminal can display the second service page. The second service page may be the first service page, or may be a service page based on the first service page and a successful page rendering.

In specific implementation, after the application server sends the service authorization token to the third-party server, the third-party server may invoke the application server to perform service processing according to the service authorization token. Specifically, the application server responds to the service processing request of the third-party server in the following way:

receiving a service processing request sent by the third-party server;

For example, the application server receives a withholding processing request sent by the third-party server, reads a withholding channel recorded in a withholding authorization protocol according to a withholding authorization token carried in the withholding processing request, carries out withholding processing on withholding cost in the withholding processing request based on the withholding channel, and sends a withholding processing result to the third-party server.

In addition, when the user submits the agreement signing instruction and fails to send the user information and the service authorization token to the third-party server due to various reasons, the information authorization token and the service authorization token are stored, so that the information authorization token and the service authorization token can be obtained when the user is registered and called next time, and the user does not need to re-authorize. Based on this, in this embodiment, when a secondary registration call is obtained, first, whether the information authorization token and the at least one service authorization token of the user are stored is queried according to the secondary registration call of the third-party server; if so, sending the user information to the third-party server based on the information authorization token, and sending the at least one service authorization token to the third-party server; if not, the user terminal receives and generates a protocol signing page containing a plurality of protocol access entries.

The following further describes the registration processing method provided in this embodiment by taking an application of the registration processing method provided in this embodiment in a car booking service scenario of the internet as an example, and referring to fig. 6, the registration processing method applied in the car booking service scenario of the internet specifically includes steps S602 to S614.

And step S602, displaying a service home page through the network car booking application according to an access instruction submitted by a user aiming at the network car booking application in the host application.

And step S604, collecting a service request of the user for the online car booking service and submitting the service request to the vehicle booking server.

And step S606, receiving and displaying the registration prompt sent by the vehicle reservation server, and submitting the registration prompt to the vehicle reservation server after acquiring the registration instruction of the user.

Step S608, receiving and displaying the agreement signing page sent by the host application and containing the information authorization protocol access entry and the token authorization protocol access entry.

Step S610, if an authorization component configured by the agreement signing page is detected, submitting a preprocessing instruction to an application server; so that the application server performs signature preprocessing on the withholding authorization protocol.

Step S612, if the protocol signing control configured by the protocol signing page is triggered, submitting a protocol signing instruction to an application server; so that the application server performs signing processing on the information authorization protocol.

And step S614, receiving and displaying the registration result issued by the vehicle reservation server after the registration is finished.

In summary, in the registration processing method provided in this embodiment, first, according to an access instruction submitted by a user for a sub-application in a host application, a first service page is displayed through the sub-application, and if a registration instruction for the sub-application by the user is detected, a registration instruction is submitted to a third-party server of the sub-application, then a protocol signing page issued by an application server of the host application is received and displayed, and finally, the protocol signing instruction of the user is obtained and submitted to the application server, and a second service page is displayed based on the sub-application after registration is completed.

An embodiment of a registration processing apparatus provided in this specification is as follows:

in the above embodiment, a registration processing method is provided, and a registration processing apparatus is provided, which is described below with reference to the accompanying drawings.

Referring to fig. 7, a schematic diagram of a registration processing apparatus provided in this embodiment is shown.

Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.

The present embodiment provides a registration processing apparatus, including:

a page generating module 702 configured to generate and send an agreement signing page including a plurality of agreement access entries to the user terminal in response to a registration call of the third-party server;

a signing processing module 704 configured to sign an authorization protocol corresponding to each protocol access entry according to a protocol signing instruction submitted by the user terminal;

and the information sending module 706 is configured to send the obtained user information to the third-party server according to at least one of the plurality of authorization tokens obtained after signing processing, so as to perform user registration according to the user information.

Another embodiment of a registration processing apparatus provided in this specification is as follows:

in the above embodiment, another registration processing method is provided, and correspondingly, another registration processing apparatus is also provided, which is described below with reference to the accompanying drawings.

Referring to fig. 8, a schematic diagram of a registration processing apparatus provided in this embodiment is shown.

The present embodiment provides a registration processing apparatus, including:

a first page presentation module 802 configured to present a first service page through a sub-application within a host application according to an access instruction submitted by a user for the sub-application;

a registration instruction submitting module 804 configured to submit the registration instruction to a third-party server of the sub-application if the registration instruction of the user for the sub-application is detected;

a signed page display module 806 configured to receive and display a protocol signed page issued by an application server of the host application;

and a second page presentation module 808, configured to obtain the agreement signing instruction of the user, submit the agreement signing instruction to the application server, and present a second service page based on the sub-application after the registration is completed.

corresponding to the above-described registration processing method, based on the same technical concept, one or more embodiments of the present specification further provide a registration processing apparatus for executing the above-described registration processing method, and fig. 9 is a schematic structural diagram of a registration processing apparatus provided in one or more embodiments of the present specification.

The registration processing device provided by the embodiment includes:

as shown in fig. 9, the registration processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 901 and a memory 902, where one or more stored applications or data may be stored in the memory 902. Memory 902 may be, among other things, transient storage or persistent storage. The application program stored in memory 902 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a registered processing device. Still further, the processor 901 may be configured to communicate with the memory 902 to execute a series of computer-executable instructions in the memory 902 on a registered processing device. The registration processing apparatus can also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input/output interfaces 905, one or more keyboards 906, and the like.

In one particular embodiment, the registration processing apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the registration processing apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:

responding to the registration call of the third-party server, generating a protocol signing page containing a plurality of protocol access entries and sending the protocol signing page to the user terminal;

according to the protocol signing instruction submitted by the user terminal, signing the authorization protocol corresponding to each protocol access entrance;

and sending the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing so as to register the user according to the user information.

corresponding to the above-described registration processing method, based on the same technical concept, one or more embodiments of the present specification further provide a registration processing apparatus for executing the above-described registration processing method, and fig. 10 is a schematic structural diagram of a registration processing apparatus provided in one or more embodiments of the present specification.

The registration processing device provided by the embodiment includes:

as shown in fig. 10, the registration processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 1001 and a memory 1002, and one or more stored applications or data may be stored in the memory 1002. Memory 1002 may be, among other things, transient storage or persistent storage. The application programs stored in memory 1002 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a registered processing device. Still further, the processor 1001 may be configured to communicate with the memory 1002 to execute a series of computer-executable instructions in the memory 1002 on a registered processing device. The registration processing apparatus may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input/output interfaces 1005, one or more keyboards 1006, etc.

displaying a first service page through a sub-application according to an access instruction submitted by a user aiming at the sub-application in a host application;

if the registration instruction of the user for the sub-application is detected, submitting the registration instruction to a third-party server of the sub-application;

receiving and displaying a protocol signing page issued by an application server of the host application;

and acquiring an agreement signing instruction of the user, submitting the agreement signing instruction to the application server, and displaying a second service page based on the sub-application after the registration is completed.

An embodiment of a storage medium provided in this specification is as follows:

on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the registration processing method described above.

The storage medium provided in this embodiment is used to store computer-executable instructions, and when executed, the computer-executable instructions implement the following processes:

It should be noted that the embodiment of the storage medium in this specification and the embodiment of the registration processing method in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the foregoing corresponding method, and repeated details are not described here.

Another storage medium embodiment provided in this specification is as follows:

in response to the above-described other registration processing method, based on the same technical concept, one or more embodiments of the present specification further provide a storage medium.

It should be noted that the embodiment of the storage medium in this specification and the embodiment of another registration processing method in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the foregoing corresponding method, and repeated details are not described here.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: the ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. A registration processing method, comprising:

2. The registration processing method of claim 1, wherein the plurality of authorization protocols corresponding to the plurality of protocol access entries comprises: an information authorization protocol and at least one service authorization protocol;

correspondingly, the signing processing of the authorization protocol corresponding to each protocol access entry includes:

and performing signing processing of the information authorization agreement based on the user identification, and performing signing processing of the at least one service authorization agreement based on the user service information.

3. The registration processing method according to claim 2, wherein the sending the obtained user information to the third-party server according to at least one of the plurality of authorization tokens obtained after the signing processing includes:

reading the user information according to the user identification of the user;

and sending the user information to the third-party server based on the information authorization token obtained after the signing processing of the information authorization agreement.

4. The registration processing method according to claim 2, after signing the authorization agreement corresponding to each protocol access entry, further comprising:

5. The registration processing method according to claim 2, wherein the signing processing of the authorization protocol corresponding to each protocol access entry according to the protocol signing instruction submitted by the user terminal includes:

6. The registration processing method according to claim 1, before generating and sending the agreement signing page containing the plurality of agreement access entries to the user terminal, further comprising:

judging whether the identification result meets a credible condition or not;

and if so, executing the process of generating the protocol signing page containing the plurality of protocol access entries and sending the protocol signing page to the user terminal.

7. The registration processing method according to claim 6, wherein if the execution result after the step of determining whether the identification result meets the trusted condition is negative, the following operations are executed:

sending a message verification prompt containing verification information to the user terminal through the host application;

8. The registration processing method of claim 1, wherein the third party server initiates the registration call as follows:

9. The registration processing method of claim 4, further comprising:

receiving a service processing request sent by the third-party server;

10. The registration processing method according to claim 4, after the signing processing step is executed for the authorization protocol corresponding to each protocol access entry according to the protocol signing instruction submitted by the user terminal, further comprising:

inquiring whether the information authorization token and the at least one service authorization token of the user are stored or not according to the secondary registration call of the third-party server;

and if so, sending the user information to the third-party server based on the information authorization token, and sending the at least one service authorization token to the third-party server.

11. A registration processing method, comprising:

12. The registration processing method of claim 11, wherein the registration instruction is submitted by:

receiving and displaying a registration prompt sent by the third-party server;

13. The registration processing method according to claim 11, wherein before the receiving and displaying the agreement signing page issued by the application server of the host application, the method further comprises:

14. The registration processing method of claim 11, wherein after the steps of receiving and displaying the agreement signing page issued by the application server of the host application are executed, and before the steps of obtaining and submitting the agreement signing instruction of the user to the application server and displaying the second service page based on the sub-application after the registration is completed are executed, the method further comprises:

15. A registration processing apparatus comprising:

the page generation module is configured to respond to registration call of the third-party server, generate a protocol signing page containing a plurality of protocol access entries and send the protocol signing page to the user terminal;

the signing processing module is configured to sign the authorization protocol corresponding to each protocol access entrance according to the protocol signing instruction submitted by the user terminal;

and the information sending module is configured to send the acquired user information to the third-party server according to at least one of the plurality of authorization tokens acquired after signing processing so as to perform user registration according to the user information.

16. A registration processing apparatus comprising:

the first page presentation module is configured to present a first service page through a sub-application in a host application according to an access instruction submitted by a user for the sub-application;

the registration instruction submitting module is configured to submit the registration instruction to a third-party server of the sub-application if the registration instruction of the user for the sub-application is detected;

the signing page display module is configured to receive and display a protocol signing page issued by an application server of the host application;

and the second page display module is configured to acquire an agreement signing instruction of the user, submit the agreement signing instruction to the application server, and display a second service page based on the sub-application after the registration is completed.

17. A registration processing apparatus comprising:

a processor; and the number of the first and second groups,

a memory configured to store computer-executable instructions that, when executed, cause the processor to:

18. A registration processing apparatus comprising:

a processor; and the number of the first and second groups,

19. A storage medium storing computer-executable instructions that when executed implement the following:

20. A storage medium storing computer-executable instructions that when executed implement the following: