WO2022242478A1 - 账户注册处理的方法及装置 - Google Patents

账户注册处理的方法及装置 Download PDF

Info

Publication number
WO2022242478A1
WO2022242478A1 PCT/CN2022/091543 CN2022091543W WO2022242478A1 WO 2022242478 A1 WO2022242478 A1 WO 2022242478A1 CN 2022091543 W CN2022091543 W CN 2022091543W WO 2022242478 A1 WO2022242478 A1 WO 2022242478A1
Authority
WO
WIPO (PCT)
Prior art keywords
registration
information
invitation
terminal
user
Prior art date
Application number
PCT/CN2022/091543
Other languages
English (en)
French (fr)
Inventor
郭小成
姜明宇
余锐锐
叶玥
孙志强
何世伟
任雪
Original Assignee
支付宝(杭州)信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝(杭州)信息技术有限公司 filed Critical 支付宝(杭州)信息技术有限公司
Publication of WO2022242478A1 publication Critical patent/WO2022242478A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2117—User registration

Definitions

  • This document relates to the technical field of data processing, and in particular to an account registration processing method and device.
  • the account registration processing method applied to a server, includes: receiving the contact information of the target user submitted by the first terminal, and returning an information collection page to the first terminal. An invitation is generated according to the registration information submitted by the first terminal and entered on the information collection page, and an invitation link generated based on the invitation is sent to the second terminal based on the contact information. After the invitation link is triggered, the display configuration parameters of the target user are determined according to the registration information. If receiving a registration confirmation instruction submitted by the second terminal after performing information display based on the display configuration parameters, perform account registration based on the registration information, and send a registration result to the first terminal.
  • One or more embodiments of this specification provide a second account registration processing method, applied to the first terminal, including: submitting the contact information of the target user to the server through an initial page, and receiving an information collection page returned by the server. Entering the registration information of the target user through the information collection page and submitting it to the server. receiving a registration result returned by the server after performing registration processing based on the registration information.
  • One or more embodiments of this specification provide a third account registration processing method, applied to a second terminal, including: receiving an invitation link sent by a server. After the invitation link is triggered, a registration confirmation page generated based on the display configuration information and the registration information of the target user submitted by the initiating user is displayed. Submit a registration confirmation instruction to the server after the registration confirmation control configured on the registration confirmation page is triggered.
  • One or more embodiments of this specification provide a first account registration processing device, running on a server, including: a contact information receiving module, configured to receive the contact information of the target user submitted by the first terminal, and send the information to the first terminal Return to the information collection page.
  • the invitation sheet generation module is configured to generate an invitation sheet based on the registration information entered on the information collection page submitted by the first terminal, and send an invitation link generated based on the invitation sheet to the second terminal based on the contact information .
  • the parameter determination module is configured to determine the display configuration parameters of the target user according to the registration information after the invitation link is triggered.
  • the account registration module is configured to perform account registration based on the registration information and send a registration result to the first terminal upon receiving the registration confirmation instruction submitted by the second terminal after performing information display based on the display configuration parameters .
  • One or more embodiments of this specification provide a second account registration processing device, running on the first terminal, including: a contact information submission module, configured to submit the contact information of the target user to the server through the initial page, and receive the The information collection page returned by the server.
  • the registration information submitting module is configured to enter the registration information of the target user through the information collection page and submit it to the server.
  • the registration result receiving module is configured to receive the registration result returned by the server after performing registration processing based on the registration information.
  • a third account registration processing apparatus which runs on a second terminal and includes: a receiving module configured to receive an invitation link sent by a server.
  • the display module is configured to display a registration confirmation page generated based on the display configuration information and the registration information of the target user submitted by the initiating user after the invitation link is triggered.
  • the submission module is configured to submit a registration confirmation instruction to the server after the registration confirmation control configured on the registration confirmation page is triggered.
  • One or more embodiments of the present specification provide a first account registration processing device, running on a server, including: a processor; and a memory configured to store computer-executable instructions, when the computer-executable instructions are executed
  • the processor is configured to: receive the contact information of the target user submitted by the first terminal, and return an information collection page to the first terminal.
  • An invitation is generated according to the registration information submitted by the first terminal and entered on the information collection page, and an invitation link generated based on the invitation is sent to the second terminal based on the contact information.
  • the display configuration parameters of the target user are determined according to the registration information. If receiving a registration confirmation instruction submitted by the second terminal after performing information display based on the display configuration parameters, perform account registration based on the registration information, and send a registration result to the first terminal.
  • One or more embodiments of the present specification provide a second account registration processing device, running on the first terminal, including: a processor; and a memory configured to store computer-executable instructions, the computer-executable instructions being executed During execution, the processor: submits the contact information of the target user to the server through the initial page, and receives the information collection page returned by the server. Entering the registration information of the target user through the information collection page and submitting it to the server. receiving a registration result returned by the server after performing registration processing based on the registration information.
  • One or more embodiments of this specification provide a third account registration processing device, running on a second terminal, including: a processor; and a memory configured to store computer-executable instructions, the computer-executable instructions being executed When executed, the processor is enabled to: receive the invitation link sent by the server. After the invitation link is triggered, a registration confirmation page generated based on the display configuration information and the registration information of the target user submitted by the initiating user is displayed. Submit a registration confirmation instruction to the server after the registration confirmation control configured on the registration confirmation page is triggered.
  • One or more embodiments of this specification provide a first storage medium, which is used to store computer-executable instructions.
  • the following process is implemented: receiving the contact information of the target user submitted by the first terminal, returning an information collection page to the first terminal.
  • An invitation is generated according to the registration information submitted by the first terminal and entered on the information collection page, and an invitation link generated based on the invitation is sent to the second terminal based on the contact information.
  • the display configuration parameters of the target user are determined according to the registration information. If receiving a registration confirmation instruction submitted by the second terminal after performing information display based on the display configuration parameters, perform account registration based on the registration information, and send a registration result to the first terminal.
  • One or more embodiments of this specification provide a second storage medium, which is used to store computer-executable instructions.
  • the computer-executable instructions When executed, the following process is implemented: submitting the contact information of the target user to the server through the initial page, And receive the information collection page returned by the server. Entering the registration information of the target user through the information collection page and submitting it to the server. receiving a registration result returned by the server after performing registration processing based on the registration information.
  • One or more embodiments of this specification provide a third storage medium, which is used for storing computer-executable instructions, and the computer-executable instructions implement the following process when executed: receiving the invitation link sent by the server. After the invitation link is triggered, a registration confirmation page generated based on the display configuration information and the registration information of the target user submitted by the initiating user is displayed. Submit a registration confirmation instruction to the server after the registration confirmation control configured on the registration confirmation page is triggered.
  • Fig. 1 is a processing flowchart of the first account registration processing method provided by one or more embodiments of this specification;
  • FIG. 2 is a schematic diagram of a scene of an account registration processing method provided by one or more embodiments of this specification;
  • Fig. 3 is a schematic diagram of an initial page provided by one or more embodiments of this specification.
  • Fig. 4 is a schematic diagram of an information collection page provided by one or more embodiments of this specification.
  • Fig. 5 is a schematic diagram of a waiting reminder page provided by one or more embodiments of this specification.
  • Fig. 6 is a schematic diagram of a registration confirmation page provided by one or more embodiments of this specification.
  • FIG. 7 is a processing flowchart of the first invitation processing flow provided by one or more embodiments of this specification.
  • Fig. 8 is a processing flow chart of the first registration processing flow provided by one or more embodiments of this specification.
  • Fig. 9 is a sequence diagram of an account registration processing method applied to an invitation registration scenario provided by one or more embodiments of this specification.
  • Fig. 10 is a processing flowchart of the second account registration processing method provided by one or more embodiments of this specification.
  • Fig. 11 is a processing flowchart of the second invitation processing flow provided by one or more embodiments of this specification.
  • Fig. 12 is a processing flowchart of a third account registration processing method provided by one or more embodiments of this specification.
  • Fig. 13 is a processing flowchart of the second registration processing flow provided by one or more embodiments of this specification.
  • Fig. 14 is a schematic diagram of a first account registration processing device provided by one or more embodiments of this specification.
  • Fig. 15 is a schematic diagram of a second account registration processing device provided by one or more embodiments of this specification.
  • Fig. 16 is a schematic diagram of a third account registration processing device provided by one or more embodiments of this specification.
  • Fig. 17 is a schematic structural diagram of a first account registration processing device provided by one or more embodiments of this specification.
  • Fig. 18 is a schematic structural diagram of a second account registration processing device provided by one or more embodiments of this specification.
  • Fig. 19 is a schematic structural diagram of a third account registration processing device provided by one or more embodiments of this specification.
  • Embodiment of the first account registration processing method provided in this specification refer to FIG. 1, which shows a processing flow chart of an account registration processing method provided in this embodiment, and refer to FIG. 2, which shows the processing flow chart of an account registration processing method provided in this embodiment
  • FIG. 3 shows a schematic diagram of an initial page provided by this embodiment.
  • FIG. 4 it shows a schematic diagram of an information collection page provided by this embodiment.
  • FIG. 5 shows a schematic diagram of a waiting reminder page provided by this embodiment
  • Figure 6 shows a schematic diagram of a registration confirmation page provided by this embodiment
  • Figure 7 shows a schematic diagram of this embodiment
  • a processing flow chart of an invitation processing flow is provided, refer to FIG. 8, which shows a processing flow chart of a registration processing flow provided by this embodiment, and refer to FIG. 9, which shows a processing flow chart of a registration processing flow provided by this embodiment.
  • the account registration processing method provided in this embodiment is applied to a server, and specifically includes steps S102 to S108.
  • Step S102 receiving the contact information of the target user submitted by the first terminal, and returning an information collection page to the first terminal.
  • the execution subject of the account registration processing method provided in this embodiment is a server.
  • This specification provides an account registration processing method embodiment in which the execution subject is the first terminal, and an account registration processing method in which the execution subject is the second terminal.
  • This implementation The account registration processing method applied to the server provided in this example cooperates with the account registration processing method applied to the first terminal and the account registration processing method applied to the second terminal provided in the following method embodiments. Therefore, To read this embodiment, please refer to the corresponding content of the following method embodiment.
  • the scenario in the schematic diagram of a scenario of an account registration processing method provided in this embodiment includes: a first terminal of an initiating user, a server, and a second terminal of a target user.
  • the first terminal and the second terminal may be a mobile phone, a tablet computer, a desktop computer, a portable notebook computer, a smart watch, etc. (only a mobile phone is shown in FIG. 2 ).
  • the server may be an independent server or a server cluster composed of multiple servers.
  • the inviting user fills in the registration information on behalf of the inviting user during the invitation registration process, and the invited user only needs to confirm to realize the account registration of the invited user.
  • the server receives the invited user’s submitted information.
  • the contact information of the inviting user and return the information collection page to the inviting user then generate an invitation form based on the registration information of the invited user submitted by the inviting user, and send an invitation generated based on the identification of the invitation form to the invited user according to the contact information of the invited user Link, after the invited user triggers the invitation link, display information to the invited user based on the determined display configuration parameters, and perform account registration according to the registration confirmation instruction submitted by the invited user based on the information display, and send the registration result to the inviting user after registration
  • the operation process of the invited user is reduced, and the operation threshold of the invited user is lowered.
  • the registration result is fed back to the inviting user, so that the inviting user invites the invited user to open more services or reminds the inviting user to register according to the registration result reason of failure.
  • the first terminal described in this embodiment includes the user terminal of the inviting user (initiating user), the inviting user is a user who has registered for an account; the inviting user submits the mobile phone number of the invited user through the first terminal to complete the invitation to the invited user.
  • the user's account is registered, the invited user is the target user, and the user terminal of the invited user is the second terminal.
  • the inviting user and the invited user may be users having a relationship of relatives and friends.
  • the initiating user uses the first terminal to submit the contact information of the target user to the server through the initial page.
  • the contact information is processed. Verification, the information collection page is returned to the first terminal only when the verification is passed.
  • the following steps are performed: receiving the contact method, verifying whether the target user meets the registration conditions based on the contact information; if so, performing the operation of returning the information collection page to the first terminal; if not, sending reminder information to the first terminal based on the verification failure type .
  • the process of verifying whether the target user meets the registration conditions based on the contact information it is checked whether the contact information has been registered, and whether the contact information is marked as a blacklist; if the target user does not meet the registration conditions, then the The first terminal sends relevant reasons, so as to improve the initiating user's perception of the verification result.
  • the inviting user submits the contact information of the invited elderly user through the initial page shown in Figure 3 on the inviting terminal. If not, input the contact information into the trusted algorithm for credible verification. If the verification result output by the trusted algorithm is verified, return the information collection page shown in Figure 4 to the inviting terminal.
  • the inviting user can view the address book and select a friend from the address book by triggering 301, and the inviting terminal will submit the contact information to the server after detecting that the "next step" control is triggered; the inviting terminal will invite the user after displaying the information collection page in Figure 4 Enter the name and ID of the elderly user, and when the inviting terminal detects that the "Confirm” control is triggered, it will submit the registration information of the elderly user consisting of the name and ID to the server.
  • inviting target users to register accounts is to achieve marketing effects by making more users participate in the service.
  • there are still threshold problems for target users in the account registration process so the success rate of inviting special groups is low.
  • the initiating user he cannot perceive the registration problems encountered by the target user in the account registration and the specific reasons, and it takes time to communicate repeatedly.
  • the initiating user when the initiating user fills in the registration information of the target user through the information collection page, in order to improve registration efficiency and avoid registration failure due to the format of the registration information filled in by the initiating user not meeting the format conditions, the initiating user The registration information of the target user filled in needs to be checked for legality.
  • the first terminal performs the following steps in the process of collecting registration information: collect the information collection page and enter the registration information; check whether the format of the registration information meets the format conditions; if so, submit the registration information when it is detected that the confirmation control configured on the information collection page is triggered; if not, display the format reminder, and Reminding the initiating user to which the first terminal belongs to re-enter the registration information.
  • the first terminal detects whether the registration information entered by the user meets the format conditions, and if so, submits the initiation to the server when it detects that the confirmation control configured on the information collection page is triggered. If the registration information entered by the user does not match, a format reminder will be displayed to remind the initiating user to re-enter the registration information according to the displayed format reminder.
  • the initiating user when the initiating user invites the target user to register an account, the initiating user submits the contact information of the target user to the server through the first terminal; the server checks whether the contact information meets the registration invitation conditions; The first terminal sends reminder information; if yes, returns an information collection page to the first terminal; the first terminal submits the registration information of the target user to the server through the information collection page.
  • Step S104 generating an invitation form based on the registration information entered on the information collection page submitted by the first terminal, and sending an invitation link generated based on the invitation form to the second terminal based on the contact information.
  • the invitation sheet is generated according to the registration information and the identity information of the initiating user.
  • the invitation sheet also includes the invitation status and the registration response result.
  • the invitation status in the invitation sheet includes waiting (WAITING), pending confirmation (PENDING), registering ( REGISTERING), registration success (SUCCESS) and/or registration failure (FAIL); if the invitation status is "FAIL", add the reason for registration failure in the registration response result.
  • an invitation sheet is generated according to the identity information of the initiating user and the registration information of the target user, and an invitation link is generated according to the invitation sheet and sent to the second terminal of the target user.
  • the server creates an invitation form based on the registration information, and creates an invitation link according to the invitation form identification of the invitation form and sends it to the second terminal of the target user; in an optional implementation mode provided in this embodiment, based on the contact information
  • the following steps are performed: generating the invitation link according to the invitation form identifier of the invitation form; sending a registration reminder carrying the invitation link to the target user based on the contact information, and sending a waiting reminder that the registration reminder has been sent to the first terminal.
  • an invitation form is created, an invitation link is generated according to the identification of the invitation form, and a registration reminder carrying the invitation link is sent to the second terminal based on the contact information.
  • the identity information associated with the user account is queried, and based on the account ID of the inviting person and the old age information submitted by the inviting user through the inviting terminal through the information collection page as shown in Figure 4 Create an invitation form as shown in Table 1 with the name and identity registration information of the user "User B".
  • the invitation status is "WAITING”.
  • the inviting user In order for the inviting user to be aware of the progress of the invitation in a timely manner, after sending a short message to the elderly user "User B", the inviting user is sent a waiting reminder page as shown in Figure 5.
  • the inviting user can send a portable short message to the elderly user through the waiting reminder. Linked SMS.
  • the waiting reminder page sent to the inviting user contains the specific content of the invitation SMS sent to the elderly user "User B", and the "send SMS again" control is configured. If the invitation link in the invitation message is not triggered, the invitation message can be sent to the elderly user "User B" again by triggering the "send message again” control.
  • a viewing reminder including the identification of the invitation is sent to the initiating user's first terminal.
  • the initiating user checks the invitation status in the following manner: based on the invitation identification of the invitation, sending a reminder to the first terminal to check the invitation; After the viewing reminder is triggered, query the invitation status recorded in the invitation form and send it to the first terminal. Specifically, after the initiating user submits an access request for viewing reminders, the invitation status in the corresponding invitation form is checked according to the invitation form identifier carried in the access request and sent to the initiating user.
  • Step S106 after the invitation link is triggered, the presentation configuration parameters of the target user are determined according to the registration information.
  • the display configuration parameters include displaying the registration information to the target user, such as font size and display text on the display page.
  • the displayed page style is determined. For example, for the elderly over 60 years old, use the large-character version of the page and render the information that the elderly are interested in. Guide the copywriting to strengthen the willingness of the elderly to register.
  • the following steps are performed: after the invitation link is triggered, according to the invitation link Read the record content of the invitation form by the invitation form identifier carried in the invitation form; parse the identity certificate identification of the target user in the record content to obtain the user characteristic type of the target user; input the user characteristic type into parameter configuration
  • the algorithm performs parameter configuration to obtain the display configuration parameters.
  • the user feature type (such as: user first feature, user second feature, etc.) of the target user is obtained, and the user feature type is input into the parameter configuration algorithm.
  • the type determines the display font size and display copy in the process of displaying registration information to target users. For example, according to the access request for the invitation link submitted by the elderly user "User B", the information recorded in the corresponding invitation form is queried according to the invitation form identifier in the invitation link, and the queried identity of the elderly user is analyzed to obtain The elderly user "User B" is a male, 63 years old. Input the two user characteristics of male and 63 years old into the parameter configuration algorithm, and the display font size output by the parameter configuration algorithm is large font size, and the guide copy is "Register to view stock trends ".
  • the registration confirmation page is rendered based on the display configuration parameters and the record information in the invitation form, and displayed through the second terminal of the target user.
  • the following steps are performed: based on the display configuration parameters, rendering the registration confirmation page including the registration information and the identity identifier in the identity information; rendering the registration confirmation page Presentation is performed through the second terminal; wherein, the identity information is the identity information read based on the account information of the first terminal and having an associated relationship with the account information.
  • the rendering of the registration confirmation page can be completed by the server.
  • the server generates the registration confirmation page according to the obtained display configuration parameters and sends it to the second terminal, so that the second terminal renders the registration confirmation page.
  • Display in addition, the registration confirmation page can also be rendered by the second terminal.
  • the server obtains the display configuration parameters, it sends the display configuration parameters and record information to the second terminal, and the second terminal renders the registration page according to the display configuration parameters and record information. Confirmation page and display.
  • Elderly users can submit a registration confirmation request by triggering the "Confirmation, direct registration with local number” control configured on the registration confirmation page after confirming that the name, contact information, and identification are correct.
  • the registration confirmation page contains the name of user A, including the name, mobile phone number and identification of the elderly user "user B", and also renders a guide copy for the elderly user "user B” "register to view stock trends” .
  • the server when the server detects that the invitation link is triggered, it reads the record information in the invitation form according to the invitation form identifier; the server parses the identity document identifier in the record information to obtain the user characteristic type of the target user; the server will The user feature type input parameter configuration algorithm performs parameter configuration to obtain the display configuration parameters for the target user; the server renders the information display page based on the display configuration parameters and record information; the server sends the information display page to the second terminal, so that the second terminal sends Target user display: the server obtains the target user's registration confirmation reminder of the record information submitted by the second terminal, performs account registration based on the registration confirmation reminder, and sends the registration result to the first terminal, so that the first terminal displays it to the initiating user.
  • Step S108 if receiving a registration confirmation instruction submitted by the second terminal after performing information display based on the display configuration parameters, perform account registration based on the registration information, and send a registration result to the first terminal.
  • account registration is performed based on the contact information and registration information of the target user.
  • Account registration is performed in the following manner: generate an account identifier based on an account identifier generation algorithm; establish an association relationship between the account identifier, the registration information and the contact information; send the account identifier to the target through the second terminal user sent.
  • account identifier generation algorithm uses the account identifier generation algorithm to generate the account identifier, and then establish the association relationship between the account identifier and the target user's contact information and registration information, so as to assign the account identifier to the target user; in addition, in the process of account registration It is also possible to input the contact information and registration information of the target user into the account identifier generation algorithm, obtain the account identifier associated with the contact information and registration information output by the account identifier generation algorithm, and determine the account identifier as the account identifier of the target user.
  • the target user when the target user registers successfully or fails to register, update the invitation form and send the updated registration result to the first terminal; in an optional implementation mode provided in this embodiment , after account registration, first update the invitation status in the invitation form according to the registration result, and then send the registration result to the first terminal based on the invitation status; wherein, if the registration result is a registration If successful, update the registration result of successful registration to the invitation form; if the registration result is failed registration, read the reason for registration failure, and update the reason for registration failure with the registration result of failed registration to the said invitation.
  • the invitation status in the invitation form is updated to "SUCCESS", and a reminder of successful registration is sent to the first terminal to guide the initiating user to add the user account of the target user as a friend or invite the target user to open an update account.
  • Multi-service if the registration fails, update the invitation status in the invitation form to "FAIL”, update the registration response result to the failure reason, and send a reminder of the registration failure including the failure reason to the first terminal, and guide the initiating user to try to use other ways to invite.
  • the invitation form ID can be concatenated in the original notification link to generate a short link, and the registration result can be sent to the initiating user through an internal message;
  • the initiating user requests access to the short link, based on the invitation ID in the access request, the invitation status in the invitation is queried, and the invitation status is displayed to the initiating user.
  • FIG. 7 a processing flowchart of an invitation processing flow, which specifically includes the following steps S702 to S712. It should be noted that the invitation processing flow provided by this embodiment cooperates with the following invitation processing flow applied to the first terminal during execution.
  • Step S702 acquiring the contact information of the elderly user submitted by the inviting user through the first terminal.
  • Step S704 call the registration record table to check whether the contact information has been registered; if yes, send a reminder to the inviting user that the user has been registered; if not, execute steps S706 to S712.
  • Step S706 inputting the contact information into a credible algorithm for credible verification, and obtaining a verification result.
  • Step S708 if the verification result is that the verification is passed, then return the information collection page to the first terminal.
  • Step S710 acquiring the registration information of the elderly user submitted by the inviting user through the first terminal.
  • Step S712 creating an invitation form according to the registration information and the identity information of the inviting user.
  • FIG. 8 a processing flow chart of a registration processing flow, which specifically includes the following steps S802 to S814. It should be noted that the registration processing flow provided by this embodiment cooperates with the following registration processing flow applied to the second terminal during execution.
  • step S802 an invitation link is generated according to the identification of the invitation and sent to the second terminal of the elderly user.
  • Step S804 when it is detected that the second terminal submits an access request for the invitation link, read the record information in the invitation slip according to the invitation slip identifier in the access request.
  • Step S806 analyzing the identity document identifier in the record information to obtain the user feature type of the elderly user.
  • Step S808 inputting the user feature type into the parameter configuration algorithm for parameter configuration to obtain display configuration parameters.
  • Step S810 sending the display configuration parameters and record information to the second terminal, so that the second terminal renders the registration confirmation page and displays it.
  • Step S812 if the registration confirmation instruction submitted by the second terminal is received, account registration is performed based on the registration information and contact information of the elderly user.
  • Step S814 if the registration is successful, assign a user account associated with the elderly user's contact information and registration information to the second terminal.
  • Step S908 the server creates an invitation form according to the registration information of the elderly user and the identity of the inviting user.
  • the first terminal submits the contact information of the elderly user to the server; the first terminal receives the information collection page returned by the server; and the first terminal submits the registration information of the elderly user to the server based on the information collection page.
  • step S910 the server generates an invitation link according to the invitation identifier of the invitation and sends it to the second terminal, and sends a waiting reminder to the first terminal after sending the invitation link to the second terminal.
  • the second terminal submits an access request for the invitation link to the server.
  • Step S914 read the record information in the invitation according to the invitation identifier carried in the access request.
  • Step S916 analyzing the ID card identification of the elderly user, and determining display configuration parameters according to the type of user characteristics obtained through analysis.
  • Step S918 sending the registration information of the elderly user and the identity of the inviting user included in the display configuration parameters and record information to the second terminal.
  • the second terminal renders and displays the registration confirmation page including the registration information and the ID according to the presentation configuration; the second terminal submits a registration confirmation instruction for the registration information to the server.
  • Step S924 perform account registration according to the registration confirmation instruction, and send the registration result to the first terminal.
  • the account registration processing method first receives the contact information of the target user submitted by the first terminal, returns the information collection page to the first terminal, and then enters the information based on the information collection page submitted by the first terminal.
  • the registration information generates an invitation form, and sends the invitation link generated based on the invitation form to the second terminal based on the contact information, and then determines the display configuration parameters of the target user according to the registration information after the invitation link is triggered;
  • the registration confirmation instruction submitted after configuring the parameters for information display registers the account based on the registration information, and sends the registration result to the first terminal. In this way, by inviting users to register and invite, special groups need to be executed in the account registration process operation, lowering the account registration threshold.
  • Embodiment of the second account registration processing method provided in this specification refer to FIG. 10 , which shows a processing flow chart of an account registration processing method provided in this embodiment, and refer to FIG. 2 , which shows the processing flow chart provided in this embodiment.
  • FIG. 10 shows a processing flow chart of an account registration processing method provided in this embodiment
  • FIG. 2 shows the processing flow chart provided in this embodiment.
  • a schematic diagram of a scenario of an account registration processing method. Referring to FIG. 3 it shows a schematic diagram of an initial page provided by this embodiment.
  • FIG. 4 it shows a schematic diagram of an information collection page provided by this embodiment.
  • FIG. 5 shows a schematic diagram of a waiting reminder page provided by this embodiment, referring to Figure 6, which shows a schematic diagram of a registration confirmation page provided by this embodiment, referring to Figure 9, which shows a schematic diagram of this embodiment
  • a sequence diagram of an account registration processing method applied to an invitation registration scenario is provided.
  • FIG. 11 it shows a processing flowchart of an invitation processing flow provided by this embodiment.
  • the account registration processing method provided in this embodiment is applied to a first terminal, and specifically includes steps S1002 to S1006.
  • Step S1002 submit the target user's contact information to the server through the initial page, and receive the information collection page returned by the server.
  • the inviting user fills in the registration information on behalf of the inviting user, and the invited user only needs to confirm to realize the account registration of the invited user.
  • the server receives the invited user’s information submitted by the inviting user Contact information and return the information collection page to the inviting user, and then generate an invitation form based on the registration information of the invited user submitted by the inviting user, and send an invitation link based on the identification of the invitation form to the invited user according to the contact information of the invited user.
  • the information is displayed to the invited user based on the determined display configuration parameters, and the account registration is performed according to the registration confirmation instruction submitted by the invited user based on the information display, and the registration result is sent to the inviting user after registration.
  • the operation process of the invited user is reduced, and the operation threshold of the invited user is lowered.
  • the registration result is fed back to the inviting user in a timely manner, so that the inviting user can invite the invited user to open more services according to the registration result or remind the inviting user of failure to register reason.
  • the first terminal described in this embodiment includes the user terminal of the inviting user (initiating user), and the inviting user is a user who has registered for an account; the inviting user submits the mobile phone number of the invited user through the first terminal to complete the registration of the invited user. account registration, the invited user is the target user, and the user terminal of the invited user is the second terminal.
  • the scenario in the schematic diagram of a scenario of an account registration processing method provided in this embodiment includes: a first terminal of an initiating user, a server, and a second terminal of a target user.
  • the first terminal and the second terminal may be a mobile phone, a tablet computer, a desktop computer, a portable notebook computer, a smart watch, etc. (only a mobile phone is shown in FIG. 2 ).
  • the server may be an independent server or a server cluster composed of multiple servers.
  • the initiating user uses the first terminal to submit the contact information of the target user to the server through the initial page.
  • the server receives the contact information of the target user submitted by the first terminal, it The verification is carried out, and the information collection page can be returned to the first terminal only when the verification is passed.
  • the server performs the following steps: receiving the contact information, and verifying whether the target user satisfies the registration requirements based on the contact information. Condition: if yes, perform the operation of returning an information collection page to the first terminal; if not, send reminder information to the first terminal based on the verification failure type.
  • the server checks whether the contact information has been registered, and verifies whether the contact information is marked as a blacklist; if the target user does not meet the registration conditions, then The relevant reason is sent to the first terminal, so as to improve the initiator user's awareness of the verification result.
  • the inviting user submits the contact information of the invited elderly user through the initial page shown in Figure 3 on the inviting terminal. If not, input the contact information into the trusted algorithm for credible verification, and if the verification result output by the trusted algorithm is verified, return the information collection page shown in Figure 4 to the inviting terminal.
  • the inviting user can view the address book and select a friend from the address book by triggering 301, and the inviting terminal will submit the contact information to the server after detecting that the "next step" control is triggered; the inviting terminal is displaying the information collection page in Figure 4 Finally, invite the user to enter the name and identity of the elderly user, and the inviting terminal will submit the registration information of the elderly user consisting of the name and the identity to the server when it detects that the "confirmation" control is triggered.
  • Step S1004 input the registration information of the target user through the information collection page and submit it to the server.
  • inviting target users to register accounts is to achieve marketing effects through sharing.
  • There is still a threshold problem for target users in the account registration process so the success rate of inviting special groups is low, and as the initiator, they cannot perceive It takes time and repeated communication for the registration problems and specific reasons that target users encounter during account registration.
  • the target user's account registration is completed by the initiating user filling in the registration information for the target user.
  • the first terminal performs the following steps in the process of collecting registration information: collect the information entered on the information collection page. Registration information; check whether the format of the registration information meets the format conditions; if so, submit the registration information when it is detected that the confirmation control configured on the information collection page is triggered; if not, display a format reminder to remind the The initiating user to which the first terminal belongs re-enters the registration information.
  • the first terminal detects whether the registration information entered by the user meets the format conditions, and if so, submits the initiation to the server when it detects that the confirmation control configured on the information collection page is triggered. If the registration information entered by the user does not match, a format reminder will be displayed to remind the initiating user to re-enter the registration information according to the displayed format reminder.
  • the server After receiving the registration information, the server generates an invitation form according to the registration information entered on the information collection page submitted by the first terminal, and sends an invitation link generated based on the invitation form to the second terminal based on the contact information.
  • the invitation sheet is generated according to the registration information and the identity information of the initiating user.
  • the invitation sheet also includes the invitation status and the registration response result.
  • the invitation status in the invitation sheet includes waiting (WAITING), pending confirmation (PENDING), registering ( REGISTERING), registration success (SUCCESS) and/or registration failure (FAIL); if the invitation status is "FAIL", add the reason for registration failure in the registration response result.
  • the server after receiving the registration information submitted by the first terminal, the server generates an invitation form according to the identity information of the initiating user and the registration information of the target user, and generates an invitation link according to the invitation form and sends it to the second terminal of the target user.
  • the server performs the following steps: generating the invitation link according to the invitation identification of the invitation; sending an invitation link carrying the invitation to the target user based on the contact information Linked registration reminders, and sending a waiting reminder that the registration reminders have been sent to the first terminal.
  • the server After receiving the contact information submitted by the first terminal, the server reads the identity information associated with the user account through the user account associated with the first terminal, and based on the identity information of the initiating user and the registration of the target user An invitation form is created based on the information, an invitation link is generated according to the identification of the invitation form, and a registration reminder carrying the invitation link is sent to the second terminal based on the contact information.
  • the server queries the identity information associated with the user account according to the user account of the inviting user associated with the inviting terminal, and based on the name "User A" of the inviting user determined according to the inviter's account ID and the inviting user through the inviting terminal.
  • the registration information of the name and identity of the elderly user "User B" submitted on the information collection page shown in Figure 4 creates an invitation form as shown in Table 1.
  • the invitation status is "WAITING".
  • the invitation ID is spliced in the link, and then a short link is generated, and the short link is sent to the elderly user "User B" by SMS or other means.
  • the inviting user In order for the inviting user to be aware of the progress of the invitation in a timely manner, after sending a short message to the elderly user "User B", the inviting user is sent a waiting reminder page as shown in Figure 5.
  • the inviting user can send a portable short message to the elderly user through the waiting reminder. Linked SMS.
  • the waiting reminder page sent to the inviting user contains the specific content of the invitation SMS sent to the elderly user "User B", and the "send SMS again" control is configured. If the invitation link in the invitation message is not triggered, the invitation message can be sent to the elderly user "User B" again by triggering the "send message again” control.
  • the server sends a viewing reminder including the identification of the invitation to the first terminal of the initiating user.
  • the initiating user checks the status of the invitation in the following manner: based on the invitation ID of the invitation, a reminder to check the invitation is sent to the first terminal; after the reminder is triggered, query the The invitation status recorded in the invitation form is sent to the first terminal.
  • an invitation reminder carrying an invitation identifier sent by the server is received; after the invitation reminder is triggered, the invitation status recorded in the invitation is acquired.
  • the initiating user submits an access request for viewing the reminder, check the invitation status in the corresponding invitation form according to the invitation form identifier carried in the access request and send it to the initiating user.
  • the server After sending the invitation link to the second terminal, the server determines the display configuration parameters of the target user according to the registration information after the invitation link is triggered.
  • the display configuration parameters include displaying the registration information to the target user, such as font size and display text on the display page.
  • the server identifies the user feature type in the registration information, and determines the page style to be displayed. For example, for the elderly over 60 years old, use the large-character version of the page and render the information that the elderly are interested in. Guide the copywriting to strengthen the willingness of the elderly to register.
  • the server performs the following steps: after the invitation link is triggered, read the invitation form according to the invitation form identifier carried in the invitation link
  • the record content of the target user is parsed to obtain the user feature type of the target user by parsing the identity certificate of the target user in the record content; the user feature type is input into a parameter configuration algorithm for parameter configuration to obtain the display configuration parameters.
  • the server obtains the user feature type of the target user (such as: user first feature, user second feature, etc.)
  • the feature type determines the display font size and display copy in the process of displaying the registration information to the target user.
  • the server After the server obtains the access request for the invitation link submitted by the elderly user "User B", it queries the information recorded in the corresponding invitation form according to the invitation form identification in the invitation link, and performs the query of the elderly user's identity identification.
  • the analysis shows that the elderly user "User B” is a male, 63 years old, and the two user characteristics of male and 63 years old are input into the parameter configuration algorithm, and the type of display font size output by the obtained parameter configuration algorithm is large font size, and the guide copy is "registration can View stock trends".
  • the server after obtaining the display configuration parameters output by the parameter configuration algorithm, the server renders the registration confirmation page based on the display configuration parameters and the record information in the invitation form, and displays it through the second terminal of the target user.
  • the server After obtaining the display configuration parameters , the server performs the following steps: based on the display configuration parameters, rendering the registration confirmation page including the registration information and the identity identifier in the identity information; displaying the registration confirmation page through the second terminal; wherein,
  • the identity information is the identity information read based on the account information of the first terminal and having an association relationship with the account information.
  • the rendering of the registration confirmation page can be completed by the server.
  • the server generates the registration confirmation page according to the obtained display configuration parameters and sends it to the second terminal, so that the second terminal renders the registration confirmation page.
  • Display in addition, the registration confirmation page can also be rendered by the second terminal.
  • the server obtains the display configuration parameters, it sends the display configuration parameters and record information to the second terminal, and the second terminal renders the registration page according to the display configuration parameters and record information. Confirmation page and display.
  • the elderly user can submit a registration confirmation request by triggering the "confirmation, direct registration with local number” control configured on the registration confirmation page.
  • the registration confirmation page contains the name of user A, including the name, mobile phone number and identification of the elderly user "user B".
  • the elderly user "user B” "register to view stock trends” .
  • the server updates the invitation status in the invitation form to "PENDING"; after the target user submits the registration confirmation instruction through the registration confirmation page, the server updates the invitation status in the invitation form to " REGISTERING"; for the initiating user to view.
  • the server receives a registration confirmation instruction submitted by the second terminal after displaying information based on the display configuration parameters, it performs account registration based on the registration information, and sends the registration result to the first terminal.
  • the server After obtaining the registration confirmation request submitted by the target user through the registration confirmation page displayed by the second terminal, the server performs account registration based on the contact information and registration information of the target user. ; establishing an association relationship between the account identifier, the registration information and the contact information; sending the account identifier to the target user through the second terminal.
  • account identifier generation algorithm uses the account identifier generation algorithm to generate the account identifier, and then establish the association relationship between the account identifier and the target user's contact information and registration information, so as to assign the account identifier to the target user; in addition, in the process of account registration It is also possible to input the contact information and registration information of the target user into the account identifier generation algorithm, obtain the account identifier associated with the contact information and registration information output by the account identifier generation algorithm, and determine the account identifier as the account identifier of the target user.
  • the server updates the invitation form and sends the updated registration result to the first terminal;
  • the registration result updates the invitation status in the invitation form, and then sends the registration result to the first terminal based on the invitation status; wherein, if the registration result is a successful registration, the registration result of the successful registration Updating to the invitation form; if the registration result is registration failure, read the reason for registration failure, and update the reason for registration failure and the registration result of the registration failure to the invitation form.
  • the invitation status in the invitation form is updated to "SUCCESS", and a reminder of successful registration is sent to the first terminal to guide the initiating user to add the user account of the target user as a friend or invite the target user to open an update account.
  • Multi-service if the registration fails, update the invitation status in the invitation form to "FAIL”, update the registration response result to the failure reason, and send a reminder of the registration failure including the failure reason to the first terminal, and guide the initiating user to try to use other ways to invite.
  • the invitation form ID can be concatenated in the original notification link to generate a short link, and the registration result can be sent to the initiating user through an internal message;
  • the initiating user requests access to the short link, based on the invitation ID in the access request, the invitation status in the invitation is queried, and the invitation status is displayed to the initiating user.
  • Step S1006 receiving a registration result returned by the server after performing registration processing based on the registration information.
  • the initiating user when the initiating user invites the target user to register an account, the initiating user submits the contact information of the target user to the server through the first terminal; the server checks whether the contact information meets the registration invitation conditions; The first terminal sends reminder information; if so, then return the information collection page to the first terminal; the first terminal submits the registration information of the target user to the server through the information collection page; the server creates an invitation sheet based on the registration information, and according to the invitation sheet of the invitation sheet
  • the identification creates an invitation link and sends it to the second terminal of the target user; when the server detects that the invitation link is triggered, it reads the record information in the invitation form according to the invitation form identification; the server parses the identity certificate identification in the record information to obtain the target user
  • the user feature type the server inputs the user feature type into the parameter configuration algorithm for parameter configuration, and obtains the display configuration parameters for the target user; the server renders the information display page based on the display configuration parameters and record information; the server sends the information display page to the
  • FIG. 11 a processing flowchart of an invitation processing flow, specifically including the following steps S1102 to S1108. It should be noted that the invitation processing flow provided by this embodiment cooperates with the above-mentioned invitation processing flow applied to the server during execution.
  • Step S1102 submitting the contact information of the elderly user to the server.
  • Step S1104 obtaining the information collection page returned by the server after passing the verification.
  • Step S1106 verify whether the registration information entered by the invited user based on the information collection page meets the format requirements; if yes, execute step S1108; if not, display a format reminder to guide the invited user to re-enter.
  • Step S1108 when it is detected that the user is invited to trigger the confirmation control configured on the information collection page, the registration information is submitted to the server.
  • Step S902 submitting the contact information of the elderly user to the server.
  • Step S904 receiving the information collection page returned by the server.
  • Step S906 submit the registration information of the elderly user to the server based on the information collection page.
  • the server creates an invitation form according to the registration information of the elderly user and the identity of the inviting user; generates an invitation link according to the invitation form identification of the invitation form and sends it to the second terminal, and sends the invitation link to the first terminal after sending the invitation link to the second terminal
  • the terminal sends a waiting reminder; the second terminal submits an access request for the invitation link to the server; the server reads the record information in the invitation form according to the invitation form identification carried in the access request; parses the ID card identification of the elderly user, and obtains the
  • the user feature type determines the display configuration parameters; the display configuration parameters and the registration information of the elderly user in the recorded information and the identity of the invited user are sent to the second terminal; the second terminal renders the registration confirmation containing the registration information and the identity according to the display configuration and display the page; the second terminal submits a registration confirmation instruction for the registration information to the server; the server registers the account according to the registration confirmation instruction, and sends the registration result to the first terminal.
  • the account registration processing method provided by this embodiment first submits the contact information of the target user to the server through the initial page, and receives the information collection page returned by the server, and then enters the registration information of the target user through the information collection page and submits the information to the server.
  • the server submits, and finally receives the registration result returned by the server after registration processing based on the registration information, so that the target user is invited to register for an account by filling in the contact information and registration information of the target user.
  • the third embodiment of the account registration processing method provided in this specification refer to Figure 12, which shows a processing flow chart of an account registration processing method provided in this embodiment, and refer to Figure 2, which shows a processing flow chart of an account registration processing method provided in this embodiment.
  • FIG. 3 which shows a schematic diagram of an initial page provided by this embodiment
  • FIG. 4 which shows a schematic diagram of an information collection page provided by this embodiment
  • FIG. 5 which shows It shows a schematic diagram of a waiting reminder page provided by this embodiment.
  • FIG. 6 it shows a schematic diagram of a registration confirmation page provided by this embodiment.
  • FIG. 9 shows a schematic diagram of a registration confirmation page provided by this embodiment.
  • FIG. 13 shows a processing flow chart of a registration processing flow provided by this embodiment.
  • the account registration processing method provided in this embodiment is applied to the second terminal, and specifically includes steps S1202 to S1206.
  • Step S1202 receiving the invitation link sent by the server.
  • the inviting user fills in the registration information on behalf of the inviting user, and the invited user only needs to confirm to realize the account registration of the invited user.
  • the server receives the invited user’s information submitted by the inviting user Contact information and return the information collection page to the inviting user, and then generate an invitation form based on the registration information of the invited user submitted by the inviting user, and send an invitation link based on the identification of the invitation form to the invited user according to the contact information of the invited user.
  • the information is displayed to the invited user based on the determined display configuration parameters, and the account registration is performed according to the registration confirmation instruction submitted by the invited user based on the information display, and the registration result is sent to the inviting user after registration.
  • the operation process of the invited user is reduced, and the operation threshold of the invited user is lowered.
  • the registration result is fed back to the inviting user in a timely manner, so that the inviting user can invite the invited user to open more services according to the registration result or remind the inviting user of failure to register reason.
  • the first terminal described in this embodiment includes the user terminal of the inviting user (initiating user), and the inviting user is a user who has registered for an account; the inviting user submits the mobile phone number of the invited user through the first terminal to complete the registration of the invited user. account registration, the invited user is the target user, and the user terminal of the invited user is the second terminal.
  • the scenario in the schematic diagram of a scenario of an account registration processing method provided in this embodiment includes: a first terminal of an initiating user, a server, and a second terminal of a target user.
  • the first terminal and the second terminal may be a mobile phone, a tablet computer, a desktop computer, a portable notebook computer, a smart watch, etc. (only a mobile phone is shown in FIG. 2 ).
  • the server may be an independent server or a server cluster composed of multiple servers.
  • the initiating user uses the first terminal to submit the contact information of the target user to the server through the initial page.
  • the server receives the contact information of the target user submitted by the first terminal, it The verification is carried out, and the information collection page can be returned to the first terminal only when the verification is passed.
  • the server performs the following steps: receiving the contact information, and verifying whether the target user satisfies the registration requirements based on the contact information. Condition: if yes, perform the operation of returning an information collection page to the first terminal; if not, send reminder information to the first terminal based on the verification failure type.
  • the server checks whether the contact information has been registered, and verifies whether the contact information is marked as a blacklist; if the target user does not meet the registration conditions, then The relevant reason is sent to the first terminal, so as to improve the initiator user's awareness of the verification result.
  • the inviting user submits the contact information of the invited elderly user through the initial page shown in Figure 3 on the inviting terminal. If not, input the contact information into the trusted algorithm for credible verification, and if the verification result output by the trusted algorithm is verified, return the information collection page shown in Figure 4 to the inviting terminal.
  • the inviting user can view the address book and select a friend from the address book by triggering 301, and the inviting terminal will submit the contact information to the server after detecting that the "next step" control is triggered; the inviting terminal is displaying the information collection page in Figure 4 Finally, invite the user to enter the name and identity of the elderly user, and the inviting terminal will submit the registration information of the elderly user consisting of the name and the identity to the server when it detects that the "confirmation" control is triggered.
  • inviting target users to register accounts is to achieve marketing effects through sharing.
  • There is still a threshold problem for target users in the account registration process so the success rate of inviting special groups is low, and as the initiator, they cannot perceive It takes time and repeated communication for the registration problems and specific reasons that target users encounter during account registration.
  • the target user's account registration is completed by the initiating user filling in the registration information for the target user.
  • the first terminal performs the following steps in the process of collecting registration information: collect the information entered on the information collection page. Registration information; check whether the format of the registration information meets the format conditions; if so, submit the registration information when it is detected that the confirmation control configured on the information collection page is triggered; if not, display a format reminder to remind the The initiating user to which the first terminal belongs re-enters the registration information.
  • the first terminal detects whether the registration information entered by the user meets the format conditions, and if so, submits the initiation to the server when it detects that the confirmation control configured on the information collection page is triggered. If the registration information entered by the user does not match, a format reminder will be displayed to remind the initiating user to re-enter the registration information according to the displayed format reminder.
  • the server After receiving the registration information, the server generates an invitation form according to the registration information entered on the information collection page submitted by the first terminal, and sends an invitation link generated based on the invitation form to the second terminal based on the contact information.
  • the invitation sheet is generated according to the registration information and the identity information of the initiating user.
  • the invitation sheet also includes the invitation status and the registration response result.
  • the invitation status in the invitation sheet includes waiting (WAITING), pending confirmation (PENDING), registering ( REGISTERING), registration success (SUCCESS) and/or registration failure (FAIL); if the invitation status is "FAIL", add the reason for registration failure in the registration response result.
  • the server after receiving the registration information submitted by the first terminal, the server generates an invitation form according to the identity information of the initiating user and the registration information of the target user, and generates an invitation link according to the invitation form and sends it to the second terminal of the target user.
  • the server performs the following steps: generating the invitation link according to the invitation identification of the invitation; sending an invitation link carrying the invitation to the target user based on the contact information Linked registration reminders, and sending a waiting reminder that the registration reminders have been sent to the first terminal.
  • the server After receiving the contact information submitted by the first terminal, the server reads the identity information associated with the user account through the user account associated with the first terminal, and based on the identity information of the initiating user and the registration of the target user An invitation form is created based on the information, an invitation link is generated according to the identification of the invitation form, and a registration reminder carrying the invitation link is sent to the second terminal based on the contact information.
  • the server queries the identity information associated with the user account according to the user account of the inviting user associated with the inviting terminal, and based on the inviting user's account ID of the inviting user and the inviting user through the inviting terminal through the information collection as shown in Figure 4 Create an invitation form as shown in Table 1 with the registration information of the name and identity of the elderly user "User B" submitted on the page.
  • the invitation status is "WAITING”
  • the invitation form ID is spliced in the original invitation link, and the regeneration Create a short link, and send the short link to the elderly user "User B" by SMS or other means.
  • the inviting user In order for the inviting user to be aware of the progress of the invitation in a timely manner, after sending a short message to the elderly user "User B", the inviting user is sent a waiting reminder page as shown in Figure 5.
  • the inviting user can send a portable short message to the elderly user through the waiting reminder. Linked invitation text message.
  • the waiting reminder page sent to the inviting user contains the specific content of the invitation SMS sent to the elderly user "User B", and the "send SMS again" control is configured. If the invitation link in the invitation message is not triggered, the invitation message can be sent to the elderly user "User B" again by triggering the "send message again” control.
  • the server sends a viewing reminder including the identification of the invitation to the first terminal of the initiating user.
  • the initiating user checks the status of the invitation in the following manner: based on the invitation ID of the invitation, a reminder to check the invitation is sent to the first terminal; after the reminder is triggered, query the The invitation status recorded in the invitation form is sent to the first terminal.
  • an invitation reminder carrying an invitation identifier sent by the server is received; after the invitation reminder is triggered, the invitation status recorded in the invitation is acquired.
  • the initiating user submits an access request for viewing the reminder, check the invitation status in the corresponding invitation form according to the invitation form identifier carried in the access request and send it to the initiating user.
  • Step S1204 after the invitation link is triggered, display a registration confirmation page generated based on the presentation configuration information and the registration information of the target user submitted by the initiating user.
  • the server After sending the invitation link to the second terminal, the server determines the display configuration parameters of the target user according to the registration information after the invitation link is triggered.
  • the display configuration parameters include displaying the registration information to the target user, such as font size and display text on the display page.
  • the server identifies the user feature type in the registration information, and determines the page style to be displayed. For example, for the elderly over 60 years old, use the large-character version of the page and render the information that the elderly are interested in. Guide the copywriting to strengthen the willingness of the elderly to register.
  • the server performs the following steps: after the invitation link is triggered, read the invitation form according to the invitation form identifier carried in the invitation link
  • the record content of the target user is parsed to obtain the user feature type of the target user by parsing the identity certificate of the target user in the record content; the user feature type is input into a parameter configuration algorithm for parameter configuration to obtain the display configuration parameters.
  • the server obtains the user feature type of the target user (such as: user first feature, user second feature, etc.)
  • the feature type determines the display font size and display copy in the process of displaying the registration information to the target user.
  • the server After the server obtains the access request for the invitation link submitted by the elderly user "User B", it queries the information recorded in the corresponding invitation form according to the invitation form identification in the invitation link, and performs the query of the elderly user's identity identification.
  • the analysis shows that the elderly user "User B” is a male, 63 years old, and the two user characteristics of male and 63 years old are input into the parameter configuration algorithm, and the type of display font size output by the obtained parameter configuration algorithm is large font size, and the guide copy is "registration can View stock trends".
  • the server after obtaining the display configuration parameters output by the parameter configuration algorithm, the server renders the registration confirmation page based on the display configuration parameters and the record information in the invitation form, and displays it through the second terminal of the target user.
  • the server After obtaining the display configuration parameters , the server performs the following steps: based on the display configuration parameters, rendering the registration confirmation page including the registration information and the identity identifier in the identity information; displaying the registration confirmation page through the second terminal; wherein,
  • the identity information is the identity information read based on the account information of the first terminal and having an association relationship with the account information.
  • the rendering of the registration confirmation page can be completed by the server.
  • the server generates the registration confirmation page according to the obtained display configuration parameters and sends it to the second terminal, so that the second terminal renders the registration confirmation page.
  • Display in addition, the registration confirmation page can also be rendered by the second terminal.
  • the server obtains the display configuration parameters, it sends the display configuration parameters and record information to the second terminal, and the second terminal renders the registration page according to the display configuration parameters and record information. Confirmation page and display.
  • the elderly user can submit a registration confirmation request by triggering the "confirmation, direct registration with local number” control configured on the registration confirmation page.
  • the registration confirmation page contains the name of user A, including the name, mobile phone number and identification of the elderly user "user B".
  • the elderly user "user B” "register to view stock trends” .
  • the server updates the invitation status in the invitation form to "PENDING"; after the target user submits the registration confirmation instruction through the registration confirmation page, the server updates the invitation status in the invitation form to " REGISTERING"; for the initiating user to view.
  • Step S1206 submitting a registration confirmation instruction to the server after the registration confirmation control configured on the registration confirmation page is triggered.
  • the server receives a registration confirmation instruction submitted by the second terminal after displaying information based on the display configuration parameters, it performs account registration based on the registration information, and sends the registration result to the first terminal.
  • the server After obtaining the registration confirmation request submitted by the target user through the registration confirmation page displayed by the second terminal, the server performs account registration based on the contact information and registration information of the target user. ; establishing an association relationship between the account identifier, the registration information and the contact information; sending the account identifier to the target user through the second terminal.
  • account identifier generation algorithm uses the account identifier generation algorithm to generate the account identifier, and then establish the association relationship between the account identifier and the target user's contact information and registration information, so as to assign the account identifier to the target user; in addition, in the process of account registration It is also possible to input the contact information and registration information of the target user into the account identifier generation algorithm, obtain the account identifier associated with the contact information and registration information output by the account identifier generation algorithm, and determine the account identifier as the account identifier of the target user.
  • the server updates the invitation form and sends the updated registration result to the first terminal;
  • the registration result updates the invitation status in the invitation form, and then sends the registration result to the first terminal based on the invitation status; wherein, if the registration result is a successful registration, the registration result of the successful registration Updating to the invitation form; if the registration result is registration failure, read the reason for registration failure, and update the reason for registration failure and the registration result of the registration failure to the invitation form.
  • the invitation status in the invitation form is updated to "SUCCESS", and a reminder of successful registration is sent to the first terminal to guide the initiating user to add the user account of the target user as a friend or invite the target user to open an update account.
  • Multi-service if the registration fails, update the invitation status in the invitation form to "FAIL”, update the registration response result to the failure reason, and send a reminder of the registration failure including the failure reason to the first terminal, and guide the initiating user to try to use other ways to invite.
  • the invitation form ID can be concatenated in the original notification link to generate a short link, and the registration result can be sent to the initiating user through an internal message;
  • the initiating user requests access to the short link, based on the invitation ID in the access request, the invitation status in the invitation is queried, and the invitation status is displayed to the initiating user.
  • the server receives the registration confirmation instruction, and the registration result of the account registration based on the registration information is that the registration is successful, then the account identifier sent by the server is received. and show.
  • the initiating user when the initiating user invites the target user to register an account, the initiating user submits the contact information of the target user to the server through the first terminal; the server checks whether the contact information meets the registration invitation conditions; The first terminal sends reminder information; if so, then return the information collection page to the first terminal; the first terminal submits the registration information of the target user to the server through the information collection page; the server creates an invitation sheet based on the registration information, and according to the invitation sheet of the invitation sheet
  • the identification creates an invitation link and sends it to the second terminal of the target user; when the server detects that the invitation link is triggered, it reads the record information in the invitation form according to the invitation form identification; the server parses the identity certificate identification in the record information to obtain the target user
  • the user feature type the server inputs the user feature type into the parameter configuration algorithm for parameter configuration, and obtains the display configuration parameters for the target user; the server renders the information display page based on the display configuration parameters and record information; the server sends the information display page to the
  • FIG. 13 a processing flow chart of a registration processing flow, which specifically includes the following steps S1302 to S1312. It should be noted that the registration processing flow provided by this embodiment cooperates with the above registration processing flow applied to the server during execution.
  • Step S1302 receiving the invitation link generated by the invitation form identifier sent by the server.
  • Step S1304 submitting an access request for the invitation link to the server after detecting that the invitation link is triggered.
  • Step S1306 receiving display configuration parameters and record information sent by the server.
  • Step S1308 rendering and displaying the registration confirmation page including the record information based on the display configuration parameters.
  • Step S1310 submitting a registration confirmation instruction to the server after detecting that the confirmation control on the registration confirmation page is triggered.
  • Step S1312 receiving the user account associated with the contact information and registration information of the elderly user sent by the server.
  • Step S912 the second terminal submits an access request for the invitation link to the server.
  • the first terminal submits the contact information of the elderly user to the server; the first terminal receives the information collection page returned by the server; the first terminal submits the registration information of the elderly user to the server based on the information collection page; and the identity of the inviting user to create an invitation form; the server generates an invitation link according to the invitation form identification of the invitation form and sends it to the second terminal, and sends a waiting reminder to the first terminal after sending the invitation link to the second terminal.
  • the server reads the record information in the invitation form according to the invitation form identification carried in the access request; parses the ID card identification of the elderly user, and determines the display configuration parameters according to the type of user characteristics obtained by the analysis; the configuration parameters and record information will be displayed
  • the registration information of the elderly user and the identity of the invited user in the information are sent to the second terminal.
  • step S920 the second terminal renders and displays a registration confirmation page including registration information and an identity according to the display configuration.
  • step S922 the second terminal submits a registration confirmation instruction for the registration information to the server.
  • the server performs account registration according to the registration confirmation instruction, and sends the registration result to the first terminal.
  • the account registration processing method provided by this embodiment first receives the invitation link sent by the server, and then displays the registration confirmation generated based on the display configuration information and the registration information of the target user submitted by the initiating user after the invitation link is triggered. page, and finally submit the registration confirmation command to the server after the registration confirmation control configured on the registration confirmation page is triggered, so that the target user can register for the account only by submitting the registration confirmation command, which improves the simplicity of account registration.
  • the first embodiment of the account registration processing device provided in this specification is as follows: In the above-mentioned embodiment, an account registration processing method applied to the server is provided, and correspondingly, an account registration processing device is also provided , running on the server, which will be described below with reference to the accompanying drawings.
  • FIG. 14 it shows a schematic diagram of an account registration processing device provided in this embodiment.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are illustrative only.
  • This embodiment provides an account registration processing device, running on a server, including: a contact information receiving module 1402 configured to receive the contact information of the target user submitted by the first terminal, and return an information collection page to the first terminal;
  • the ticket generating module 1404 is configured to generate an invitation ticket based on the registration information entered on the information collection page submitted by the first terminal, and send an invitation link generated based on the invitation ticket to the second terminal based on the contact information
  • the parameter determination module 1406 is configured to determine the display configuration parameters of the target user according to the registration information after the invitation link is triggered;
  • the account registration module 1408 is configured to receive the second terminal based on the The registration confirmation instruction submitted after the information display of the display configuration parameters is performed, the account registration is performed based on the registration information, and the registration result is sent to the first terminal.
  • the second embodiment of the account registration processing device provided in this specification is as follows: In the above-mentioned embodiment, an account registration processing method applied to the first terminal is provided, and correspondingly, an account registration processing method is also provided. The processing device runs on the first terminal, which will be described below with reference to the accompanying drawings.
  • FIG. 15 it shows a schematic diagram of an account registration processing device provided in this embodiment.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are illustrative only.
  • This embodiment provides an account registration processing device, running on the first terminal, including: a contact information submission module 1502 configured to submit the contact information of the target user to the server through the initial page, and receive the information collection page returned by the server
  • the registration information submission module 1504 is configured to enter the registration information of the target user through the information collection page and submit it to the server;
  • the registration result receiving module 1506 is configured to receive the registration information from the server based on the registration information Registration result returned after registration processing.
  • the third embodiment of the account registration processing device provided in this specification is as follows: In the above embodiments, an account registration processing method applied to the second terminal is provided, and correspondingly, an account registration processing method is also provided. The processing device runs on the second terminal, which will be described below with reference to the accompanying drawings.
  • FIG. 16 it shows a schematic diagram of an account registration processing device provided in this embodiment.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are illustrative only.
  • This embodiment provides an account registration processing device, running on a second terminal, including: a receiving module 1602 configured to receive an invitation link sent by a server; a display module 1604 configured to display an invitation link after the invitation link is triggered A registration confirmation page generated based on the display configuration information and the registration information of the target user submitted by the initiating user; the submission module 1606 is configured to submit a registration confirmation instruction to the server after the registration confirmation control configured on the registration confirmation page is triggered.
  • the first embodiment of the account registration processing device provided in this specification is as follows: Corresponding to the account registration processing method applied to the server described above, based on the same technical concept, one or more embodiments of this specification also provide an account registration A processing device runs on a server, and the account registration processing device is used to execute the account registration processing method provided above.
  • FIG. 17 is a schematic structural diagram of the first account registration processing device provided by one or more embodiments of this specification.
  • An account registration processing device runs on a server, including: as shown in Figure 17, the account registration processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 1701 and a storage 1702.
  • the storage 1702 may store one or more stored application programs or data. Wherein, the storage 1702 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 1702 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the account registration processing device.
  • the processor 1701 may be configured to communicate with the memory 1702, and execute a series of computer-executable instructions in the memory 1702 on the account registration processing device.
  • the account registration processing device may also include one or more power sources 1703, one or more wired or wireless network interfaces 1704, one or more input/output interfaces 1705, one or more keyboards 1706, and the like.
  • the account registration processing device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and Each module may include a series of computer-executable instructions in the account registration processing device, and configured to be executed by one or more processors.
  • the one or more programs include computer-executable instructions for performing the following: receiving the first The contact information of the target user submitted by the terminal returns an information collection page to the first terminal; an invitation is generated based on the registration information entered on the information collection page submitted by the first terminal, and an invitation is sent to the second terminal based on the contact information
  • the second terminal sends an invitation link generated based on the invitation form; after the invitation link is triggered, the display configuration parameters of the target user are determined according to the registration information;
  • the registration confirmation instruction submitted after information presentation is used to register an account based on the registration information, and send a registration result to the first terminal.
  • the second embodiment of the account registration processing device provided in this specification is as follows: Corresponding to the account registration processing method applied to the first terminal described above, based on the same technical concept, one or more embodiments of this specification also provide a The account registration processing device runs on the first terminal, and the account registration processing device is used to execute the account registration processing method provided above.
  • Figure 18 is a schematic structural diagram of the second account registration processing device provided by one or more embodiments of this specification .
  • An account registration processing device runs on the first terminal, including: as shown in Figure 18, the account registration processing device may have relatively large differences due to different configurations or performances, and may include one or more than one
  • the memory 1802 may store one or more storage application programs or data. Wherein, the storage 1802 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 1802 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the account registration processing device.
  • the processor 1801 may be configured to communicate with the memory 1802, and execute a series of computer-executable instructions in the memory 1802 on the account registration processing device.
  • the account registration processing device may also include one or more power sources 1803, one or more wired or wireless network interfaces 1804, one or more input/output interfaces 1805, one or more keyboards 1806, and the like.
  • the account registration processing device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and Each module may include a series of computer-executable instructions in the account registration processing device, and configured to be executed by one or more processors.
  • the one or more programs include computer-executable instructions for performing the following: through the initial page Submit the contact information of the target user to the server, and receive the information collection page returned by the server; enter the registration information of the target user through the information collection page and submit it to the server; receive the registration information from the server based on the registration information Registration result returned after registration processing.
  • the third embodiment of the account registration processing device provided in this specification is as follows: Corresponding to the account registration processing method applied to the second terminal described above, based on the same technical concept, one or more embodiments of this specification also provide a The account registration processing device runs on the second terminal. The account registration processing device is used to execute the account registration processing method provided above.
  • FIG. 19 is a schematic structural diagram of the third account registration processing device provided by one or more embodiments of this specification. .
  • An account registration processing device runs on the second terminal, including: as shown in Figure 19, the account registration processing device may have relatively large differences due to different configurations or performances, and may include one or more than one A processor 1901 and a memory 1902.
  • One or more storage application programs or data may be stored in the memory 1902.
  • the storage 1902 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 1902 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the account registration processing device.
  • the processor 1901 may be configured to communicate with the memory 1902, and execute a series of computer-executable instructions in the memory 1902 on the account registration processing device.
  • the account registration processing device may also include one or more power sources 1903, one or more wired or wireless network interfaces 1904, one or more input/output interfaces 1905, one or more keyboards 1906, etc.
  • the account registration processing device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and Each module may include a series of computer-executable instructions in the account registration processing device, and configured to be executed by one or more processors.
  • the one or more programs include computer-executable instructions for performing the following: receiving server sent an invitation link; after the invitation link is triggered, display a registration confirmation page generated based on the display configuration information and the registration information of the target user submitted by the initiating user; after the registration confirmation control configured on the registration confirmation page is triggered, send a message to all The server submits the registration confirmation instruction.
  • the first embodiment of the storage medium provided in this specification is as follows: corresponding to the account registration processing method described above, it is applied to a server. Based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
  • the storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed, the following process is implemented: receiving the contact information of the target user submitted by the first terminal, and returning information to the first terminal collection page; generate an invitation form based on the registration information entered on the information collection page submitted by the first terminal, and send an invitation link generated based on the invitation form to the second terminal based on the contact information; After the link is triggered, the display configuration parameters of the target user are determined according to the registration information; if a registration confirmation instruction submitted by the second terminal after information display based on the display configuration parameters is received, account registration is performed based on the registration information. register, and send a registration result to the first terminal.
  • the second embodiment of the storage medium provided in this specification is as follows: corresponding to the account registration processing method described above, it is applied to the first terminal. Based on the same technical concept, one or more embodiments of this specification also provide a storage medium .
  • the storage medium provided in this embodiment is used to store computer-executable instructions, and the computer-executable instructions implement the following process when executed: submit the contact information of the target user to the server through the initial page, and receive the information returned by the server A collection page; input the registration information of the target user through the information collection page and submit it to the server; receive a registration result returned by the server after performing registration processing based on the registration information.
  • the third embodiment of the storage medium provided in this specification is as follows: corresponding to the account registration processing method described above, it is applied to the second terminal. Based on the same technical concept, one or more embodiments of this specification also provide a storage medium .
  • the storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed, the following process is implemented: receiving the invitation link sent by the server; after the invitation link is triggered, displaying the configuration based on the presentation Information and the registration confirmation page generated by the target user’s registration information submitted by the initiating user; after the registration confirmation control configured on the registration confirmation page is triggered, a registration confirmation instruction is submitted to the server.
  • the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvement in method flow).
  • improvements in many current method flows can be regarded as the direct improvement of the hardware circuit structure.
  • Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules.
  • a Programmable Logic Device such as a Field Programmable Gate Array (FPGA)
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory.
  • controller in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, means for realizing various functions can be regarded as a structure within both a software module realizing a method and a hardware component.
  • a typical implementing device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.
  • one or more embodiments of this specification 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 present 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, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in computer-readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer-readable media including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information.
  • 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 Disc (DVD) or other optical storage, Magnetic tape cartridge, tape disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
  • computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • program modules may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种账户注册处理方法及装置，所述方法包括：接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页（S102）；根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接（S104）；在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数（S106）；若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果（S108）。

Description

账户注册处理的方法及装置 技术领域
本文件涉及数据处理技术领域，尤其涉及一种账户注册处理方法及装置。
背景技术
随着信息技术和互联网技术的快速发展，在线服务得到了广泛的应用，互联网给用户的生活、工作带来了极大的便利。用户可以通过互联网购物、娱乐、***事物，一般的，用户在进行在线办理服务时，需要在相应的应用程序客户端或者网站进行账户注册，注册过程中需要用户输入手机号、短信验证码等验证信息，为了保证进行账户注册的用户为安全且有效的用户，对于用户注册过程中信息的管理具有十分重要的意义。
发明内容
本说明书一个或多个实施例提供了第一种账户注册处理方法。所述账户注册处理方法，应用于服务器，包括：接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页。根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接。在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数。若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
本说明书一个或多个实施例提供了第二种账户注册处理方法，应用于第一终端，包括：通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页。通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交。接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
本说明书一个或多个实施例提供了第三种账户注册处理方法，应用于第二终端，包括：接收服务器发送的邀请链接。在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页。在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
本说明书一个或多个实施例提供了第一种账户注册处理装置，运行于服务器，包括：联系方式接收模块，被配置为接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页。邀请单生成模块，被配置为根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接。参数确定模块，被配置为在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数。账户注册模块，被配置为若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
本说明书一个或多个实施例提供了第二种账户注册处理装置，运行于第一终端，包括：联系方式提交模块，被配置为通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页。注册信息提交模块，被配置为通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交。注册结果接收模块，被配置为接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
本说明书一个或多个实施例提供了第三种账户注册处理装置，运行于第二终端，包括：接收模块，被配置为接收服务器发送的邀请链接。展示模块，被配置为在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页。提交模块，被配置为在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
本说明书一个或多个实施例提供了第一种账户注册处理设备，运行于服务器，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：接收第一终端提交的目标用户的联系方式，向所述第一终端返回 信息采集页。根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接。在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数。若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
本说明书一个或多个实施例提供了第二种账户注册处理设备，运行于第一终端，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页。通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交。接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
本说明书一个或多个实施例提供了第三种账户注册处理设备，运行于第二终端，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：接收服务器发送的邀请链接。在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页。在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
本说明书一个或多个实施例提供了第一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页。根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接。在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数。若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
本说明书一个或多个实施例提供了第二种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页。通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交。接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
本说明书一个或多个实施例提供了第三种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：接收服务器发送的邀请链接。在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页。在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
附图说明
为了更清楚地说明本说明书一个或多个实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图；
图1为本说明书一个或多个实施例提供的第一种账户注册处理方法处理流程图；
图2为本说明书一个或多个实施例提供的一种账户注册处理方法的场景示意图；
图3为本说明书一个或多个实施例提供的一种初始页面示意图；
图4为本说明书一个或多个实施例提供的一种信息采集页示意图；
图5为本说明书一个或多个实施例提供的一种等待提醒页示意图；
图6为本说明书一个或多个实施例提供的一种注册确认页示意图；
图7为本说明书一个或多个实施例提供的第一种邀请处理流程的处理流程图；
图8为本说明书一个或多个实施例提供的第一种注册处理流程的处理流程图；
图9为本说明书一个或多个实施例提供的一种应用于邀请注册场景的账户注册处理 方法时序图；
图10为本说明书一个或多个实施例提供的第二种账户注册处理方法处理流程图；
图11为本说明书一个或多个实施例提供的第二种邀请处理流程的处理流程图；
图12为本说明书一个或多个实施例提供的第三种账户注册处理方法处理流程图；
图13为本说明书一个或多个实施例提供的第二种注册处理流程的处理流程图；
图14为本说明书一个或多个实施例提供的第一种账户注册处理装置示意图；
图15为本说明书一个或多个实施例提供的第二种账户注册处理装置示意图；
图16为本说明书一个或多个实施例提供的第三种账户注册处理装置示意图；
图17为本说明书一个或多个实施例提供的第一种账户注册处理设备的结构示意图；
图18为本说明书一个或多个实施例提供的第二种账户注册处理设备的结构示意图；
图19为本说明书一个或多个实施例提供的第三种账户注册处理设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
本说明书提供的第一种账户注册处理方法实施例：参照图1，其示出了本实施例提供的一种账户注册处理方法处理流程图，参照图2，其示出了本实施例提供的一种账户注册处理方法的场景示意图，参照图3，其示出了本实施例提供的一种初始页面示意图，参照图4，其示出了本实施例提供的一种信息采集页示意图，参照图5，其示出了本实施例提供的一种等待提醒页示意图，参照图6，其示出了本实施例提供的一种注册确认页示意图，参照图7，其示出了本实施例提供的一种邀请处理流程的处理流程图，参照图8，其示出了本实施例提供的一种注册处理流程的处理流程图，参照图9，其示出了本实施例提供的一种应用于邀请注册场景的账户注册处理方法时序图。
参照图1，本实施例提供的账户注册处理方法，应用于服务器，具体包括步骤S102至步骤S108。
步骤S102，接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页。
本实施例提供的账户注册处理方法的执行主体为服务器，本说明书提供一种账户注册处理方法实施例的执行主体为第一终端，一种账户注册处理方法的执行主体为第二终端，本实施例提供的应用于服务器的账户注册处理方法，与下述方法实施例提供的应用于第一终端的账户注册处理方法、应用于第二终端的账户注册处理方法在执行过程中相互配合，因此，阅读本实施例请对照下述方法实施例的相应内容。
如图2所示，本实施例提供的一种账户注册处理方法的场景示意图中的场景包括：发起用户的第一终端、服务器和目标用户的第二终端。其中，第一终端和第二终端可以为手机、平板电脑、台式计算机、便携笔记本式计算机、智能手表等(图2中仅示出手机)。服务器，可以是独立的服务器，也可以是由多个服务器组成的服务器集群。
实际应用中，特殊用户在特殊场景中，通过用户终端填写信息具有一定的困难，例如老年用户可能由于记忆力或视觉能力下降，对于信息的理解和辨识的能力较差，在用户账户的注册过程中对于填写注册信息存在一定的困难。本实施例提供的账户注册处理方法，在邀请注册的过程中由邀请用户代为填写注册信息，被邀请用户只需要确认即可实现被邀请用户的账户注册，具体的，服务器接收邀请用户提交的被邀请用户的联系方式并向邀请用户返回信息采集页，再根据邀请用户提交的被邀请用户的注册信息生成邀请单，并根据被邀请用户的联系方式向被邀请用户发送基于邀请单标识生成的邀请链接，在被邀请用户触发邀请链接后基于确定的展示配置参数向被邀请用户进行信息展示，并 根据被邀请用户基于信息展示提交的注册确认指令进行账户注册，在注册后向邀请用户发送注册结果，以此减少了被邀请用户的操作流程，降低了被邀请用户的操作门槛，此外，向邀请用户反馈注册结果，以使邀请用户根据注册结果邀请被邀请用户开通更多服务或者提醒邀请用户注册失败的原因。
本实施例所述第一终端，包括邀请用户(发起用户)的用户终端，该邀请用户为已经进行账户注册的用户；邀请用户通过第一终端提交被邀请用户的手机号码，以完成对被邀请用户的账户注册，被邀请用户即为所述目标用户，被邀请用户的用户终端为第二终端。其中，邀请用户与被邀请用户可以是具有亲友关系的用户。
具体实施时，发起用户利用第一终端通过初始页面向服务器提交目标用户的联系方式，为了保证目标用户的安全性，在接收到第一终端提交的目标用户的联系方式后，对该联系方式进行核验，在核验通过的情况下才向第一终端返回信息采集页，本实施例提供的一种可选实施方式中，在向第一终端返回信息采集页之前，执行如下步骤：接收所述联系方式，基于所述联系方式核验所述目标用户是否满足注册条件；若是，执行所述向所述第一终端返回信息采集页操作；若否，基于核验失败类型向所述第一终端发送提醒信息。
具体的，基于联系方式核验目标用户是否满足注册条件的过程中，核验该联系方式是否已经被注册，并且核验该联系方式是否被标记为黑灰名单；如果该目标用户不满足注册条件，则向第一终端发送相关原因，以提升发起用户对核验结果的感知程度。
例如，邀请用户通过邀请终端上如图3所示的初始页面提交被邀请的老年用户的联系方式，服务器获取到该联系方式后，在注册记录表中查询是否存在该联系方式的注册记录，若否，则将该联系方式输入可信算法中进行可信校验，若可信算法输出的校验结果为校验通过，则向邀请终端返回如图4所示的信息采集页需要说明的是，邀请用户可通过触发301查看通讯录并从通讯录选择好友，邀请终端在检测到“下一步”控件被触发则向服务器提交联系方式；邀请终端在展示图4的信息采集页后，邀请用户录入老年用户的姓名以及身份标识，邀请终端在检测到“确认”控件被触发则向服务器提交由姓名和身份标识组成的老年用户的注册信息。
实际应用中，邀请目标用户进行账户注册是通过使更多用户参与服务以实现营销效果，在此过程中依然存在目标用户在账户注册过程中的门槛问题，所以对特殊人群的邀请成功率较低，而且作为发起用户，无法感知到目标用户在账户注册中遇到的注册问题以及具体原因，需要花费时间反复沟通。
具体实施时，本实施例在发起用户通过信息采集页填写目标用户的注册信息的过程中，为了提升注册效率，避免由于发起用户填写的注册信息的格式不符合格式条件导致注册失败，对发起用户填写的目标用户的注册信息，要进行合法性校验，本实施例提供的一种可选实施方式中，第一终端在采集注册信息的过程中，执行如下步骤：采集所述信息采集页录入的所述注册信息；校验所述注册信息的格式是否符合格式条件；若是，在检测到所述信息采集页配置的确认控件被触发时提交所述注册信息；若否，展示格式提醒，以提醒所述第一终端所属的发起用户重新录入所述注册信息。
具体的，在发起用户填写注册信息的过程中，第一终端检测用户录入的注册信息是否符合格式条件，若符合，则在检测到信息采集页面配置的确认控件被触发的情况下向服务器提交发起用户录入的注册信息，若不符合，则展示格式提醒，以提醒发起用户按照展示的格式提醒重新录入注册信息。
如图2所示，在发起用户邀请目标用户进行账户注册时，发起用户通过第一终端向服务器提交目标用户的联系方式；服务器核验联系方式是否满足注册邀请条件；若否，基于核验失败类型向第一终端发送提醒信息；若是，则向第一终端返回信息采集页；第一终端通过信息采集页向服务器提交目标用户的注册信息。
步骤S104，根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请 单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接。
所述邀请单，根据注册信息以及发起用户的身份信息生成，邀请单中还包括邀请状态以及注册响应结果，邀请单中的邀请状态包括等待中(WAITING)、待确认(PENDING)、注册中(REGISTERING)、注册成功(SUCCESS)和/或注册失败(FAIL)；若邀请状态为“FAIL”，则在注册响应结果中添加注册失败原因。
具体实施时，接收到第一终端提交的注册信息后，根据发起用户的身份信息和目标用户的注册信息生成邀请单，根据邀请单生成邀请链接向目标用户的第二终端发送。如图2所示，服务器基于注册信息创建邀请单，并根据邀请单的邀请单标识创建邀请链接向目标用户的第二终端发送；本实施例提供的一种可选实施方式中，基于联系方式向第二终端发送邀请链接的过程中，执行如下步骤：根据所述邀请单的邀请单标识生成所述邀请链接；基于所述联系方式向所述目标用户发送携带所述邀请链接的注册提醒，并向所述第一终端发送所述注册提醒已发送的等待提醒。
具体的，在接收到第一终端提交的联系方式后，通过与第一终端关联的用户账户读取与该用户账户具有关联关系的身份信息，并基于发起用户的身份信息和目标用户的注册信息创建邀请单，再根据邀请单标识生成邀请链接，基于联系方式向第二终端发送携带邀请链接的注册提醒。
例如，根据与邀请终端关联的邀请用户的用户账户查询与该用户账户具有关联关系的身份信息，并基于邀请人账户ID与邀请用户通过邀请终端通过如图4所示的信息采集页提交的老年用户“用户B”的姓名和身份标识的注册信息创建如表1所示的邀请单，邀请单创建时，邀请状态为“WAITING”，在原始邀请链接中拼接邀请单ID，再生成短链接，将该短链接通过短信等方式发送给老年用户“用户B”。为了使邀请用户能够及时感知到邀请进度，在向老年用户“用户B”发送短信后，向邀请用户发送如图5所示的等待提醒页，邀请用户可通过该等待提醒向老年用户发送携带短链接的短信。
Figure PCTCN2022091543-appb-000001
表1
如图5所示，向邀请用户发送的等待提醒页中包含向老年用户“用户B”发送的邀请短信的具体内容，并配置“再次发送短信”控件，在老年用户“用户B”在一定时间内未触发邀请短信中的邀请链接，则可通过触发“再次发送短信”控件再次向老年用户“用户B”发送邀请短信。
需要说明的是，在邀请单创建后，为了使发起用户对能够随时查看邀请单的邀请状态，向发起用户的第一终端发送包含邀请单标识的查看提醒。本实施例提供的一种可选实施方式中，发起用户通过如下方式查看邀请状态：基于所述邀请单的邀请单标识，向所述第一终端发送对所述邀请单的查看提醒；在所述查看提醒被触发后，查询所述邀请单中记录的邀请状态并向所述第一终端发送。具体的，在发起用户提交针对查看提醒的访问请求后，根据访问请求中携带的邀请单标识查看对应的邀请单中的邀请状态并向发起用户发送。
步骤S106，在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数。
所述展示配置参数，包括向所述目标用户展示所述注册信息是展示页面中的字体大小以及展示文案等。
具体实施时，在目标用户触发邀请链接后，通过识别注册信息中的用户特征类型，确定展示的页面样式，例如超过60岁以上的老年人，利用大字版的页面，并渲染老年人感兴趣的引导文案，强化老年人的注册意愿。本实施例提供的一种可选实施方式中， 在邀请链接被触发后根据注册信息确定目标用户的展示配置参数的过程中，执行如下步骤：在所述邀请链接被触发后根据所述邀请链接中携带的邀请单标识读取所述邀请单的记录内容；解析所述记录内容中所述目标用户的身份证件标识，获得所述目标用户的用户特征类型；将所述用户特征类型输入参数配置算法进行参数配置，获得所述展示配置参数。
具体的，通过解析目标用户的身份证件标识，获得目标用户的用户特征类型(如：用户第一特征、用户第二特征等)，将用户特征类型输入参数配置算法中，参数配置算法根据用户特征类型确定向目标用户进行注册信息的展示的过程中的展示字号以及展示文案。例如，根据老年用户“用户B”提交的对邀请链接的访问请求，根据该邀请链接中的邀请单标识查询对应的邀请单中记录的信息，将查询到的老年用户的身份标识进行解析，获得老年用户“用户B”为男性，63岁，将男性、63岁这两个用户特征输入参数配置算法中，获得参数配置算法输出的展示字号类型为大字号，引导文案为“注册可查看股票趋势”。
具体实施时，在获得参数配置算法输出的展示配置参数后，基于展示配置参数以及邀请单中的记录信息渲染注册确认页，并通过目标用户的第二终端进行展示，本实施例提供的一种可选实施方式中，在获得展示配置参数后，执行如下步骤：基于所述展示配置参数，渲染包含所述注册信息以及身份信息中的身份标识的所述注册确认页；将所述注册确认页通过所述第二终端进行展示；其中，所述身份信息为基于所述第一终端的账户信息读取的与所述账户信息具有关联关系的身份信息。
需要说明的是，对于注册确认页的渲染，可以由服务器来完成，具体的，服务器根据获得的展示配置参数，生成注册确认页并向第二终端发送，以使第二终端将注册确认页进行展示；此外，也可以由第二终端渲染注册确认页，具体的，服务器获得展示配置参数后，将展示配置参数以及记录信息向第二终端发送，第二终端根据展示配置参数以及记录信息渲染注册确认页并展示。
如图6所示，在获取到根据老年用户“用户B”的用户第一特征以及用户第二特征确定的展示配置参数后，将展示配置参数，根据邀请人账户ID确定的邀请用户的姓名“用户A”以及老年用户“用户B”的姓名、联系方式以及身份标识向老年用户“用户B”的被邀请终端发送，被邀请终端根据上述信息渲染出注册确认页并展示。此外，在进行账户注册过程中，需要获取对于服务隐私协议的授权指令，为了进一步简化操作流程，在注册确认页中渲染对服务隐私协议的授权提醒。老年用户在确认姓名、联系方式以及身份标识正确后，可通过触发注册确认页中配置的“确认，本机号码直接注册”控件提交注册确认请求。其中，注册确认页中包含用户A的姓名，包含老年用户“用户B”的姓名，手机号以及身份标识，此外，还渲染有对老年用户“用户B”的引导文案“注册可查看股票趋势”。
需要说明的是，在目标用户访问邀请链接之后，将邀请单中的邀请状态更新为“PENDING”；在目标用户通过注册确认页提交注册确认指令后，将邀请单中的邀请状态更新为“REGISTERING”；以便发起用户进行查看。
如图2所示，服务器在检测到邀请链接被触发的情况下，根据邀请单标识读取邀请单中的记录信息；服务器解析记录信息中的身份证件标识获得目标用户的用户特征类型；服务器将用户特征类型输入参数配置算法进行参数配置，获得针对目标用户的展示配置参数；服务器基于展示配置参数与记录信息渲染信息展示页；服务器将信息展示页向第二终端发送，以使第二终端向目标用户展示；服务器获取第二终端提交的目标用户对记录信息的注册确认提醒，基于注册确认提醒进行账户注册，并将注册结果向第一终端发送，以使第一终端向发起用户展示。
步骤S108，若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
具体实施时，在获取到目标用户通过第二终端展示的注册确认页提交注册确认请求 后，基于目标用户的联系方式与注册信息进行账户注册，本实施例提供的一种可选实施方式中，通过如下方式进行账户注册：基于账户标识生成算法生成账户标识；建立所述账户标识与所述注册信息以及所述联系方式的关联关系；将所述账户标识通过所述第二终端向所述目标用户发送。
具体的，利用账户标识生成算法生成账户标识，再建立账户标识与目标用户的联系方式以及注册信息之间的关联关系，以将该账户标识分配给目标用户；此外，在进行账户注册的过程中，还可以将目标用户的联系方式以及注册信息输入账户标识生成算法，获得账户标识生成算法输出的与联系方式以及注册信息具有关联关系的账户标识，将该账户标识确定为目标用户的账户标识。
为了提升发起用户对邀请进度的感知程度，当目标用户注册成功或注册失败后，更新邀请单，并将更新后的注册结果向第一终端发送；本实施例提供的一种可选实施方式中，在进行账户注册之后，首先根据所述注册结果更新所述邀请单中的邀请状态，再基于所述邀请状态向所述第一终端发送所述注册结果；其中，若所述注册结果为注册成功，则将所述注册成功的注册结果更新至所述邀请单；若所述注册结果为注册失败，则读取注册失败原因，并将所述注册失败原因与所述注册失败的注册结果更新至所述邀请单。
具体的，若注册成功，则将邀请单中的邀请状态更新为“SUCCESS”，并向第一终端发送注册成功的提醒，以引导发起用户添加目标用户的用户账户为好友或者邀请目标用户开通更多服务；若注册失败，则将邀请单中的邀请状态更新为“FAIL”，将注册响应结果更新为失败原因，并向第一终端发送包含失败原因的注册失败的提醒，引导发起用户尝试利用其他方式进行邀请。需要说明的是，在向发起用户发送注册结果的提醒时，可在原始通知链接中拼接邀请单ID，再生成短链接，通过站内信等的方式向发起用户发送注册结果；其中，若检测到发起用户对该短链接的访问请求，则基于该访问请求中的邀请单ID，查询该邀请单中的邀请状态，并将该邀请状态向发起用户展示。
下述为本实施例提供的一种邀请处理流程，参见图7，一种邀请处理流程的处理流程图，具体包括下述步骤S702至步骤S712。需要说明的是，本实施例提供的邀请处理流程，在执行过程中与下述应用于第一终端的邀请处理流程相互配合。
步骤S702，获取邀请用户通过第一终端提交的老年用户的联系方式。
步骤S704，调用注册记录表查询该联系方式是否已经被注册；若是，向邀请用户发送用户已注册提醒；若否，执行步骤S706至步骤S712。
步骤S706，将该联系方式输入可信算法进行可信校验，获取校验结果。
步骤S708，若校验结果为校验通过，则向第一终端返回信息采集页。
步骤S710，获取邀请用户通过第一终端提交的老年用户的注册信息。
步骤S712，根据注册信息以及邀请用户的身份信息创建邀请单。
下述为本实施例提供的一种注册处理流程，参见图8，一种注册处理流程的处理流程图，具体包括下述步骤S802至步骤S814。需要说明的是，本实施例提供的注册处理流程，在执行过程中与下述应用于第二终端的注册处理流程相互配合。
步骤S802，根据邀请单标识生成邀请链接并向老年用户的第二终端发送。
步骤S804，在检测到第二终端提交对邀请链接的访问请求时，根据访问请求中的邀请单标识读取邀请单中的记录信息。
步骤S806，解析记录信息中的身份证件标识，获得老年用户的用户特征类型。
步骤S808，将用户特征类型输入参数配置算法进行参数配置，获得展示配置参数。
步骤S810，将展示配置参数以及记录信息向第二终端发送，以使第二终端渲染注册确认页并展示。
步骤S812，若接收到第二终端提交的注册确认指令，基于老年用户的注册信息以及联系方式进行账户注册。
步骤S814，在注册成功的情况下向第二终端分配与老年用户的联系方式以及注册信 息具有关联关系的用户账户。
下述以本实施例提供的一种账户注册处理方法在邀请注册场景的应用为例，对本实施例提供的账户注册处理方法进行进一步说明，参见图9，应用于邀请注册场景的账户注册处理方法，包括如下步骤。
步骤S908，服务器根据老年用户的注册信息以及邀请用户的身份标识创建邀请单。
在此之前，第一终端向服务器提交老年用户的联系方式；第一终端接收服务器返回的信息采集页；第一终端基于信息采集页向服务器提交老年用户的注册信息。
步骤S910，服务器根据邀请单的邀请单标识生成邀请链接并向第二终端发送，在向第二终端发送邀请链接后向第一终端发送等待提醒。
此后，第二终端向服务器提交对邀请链接的访问请求。
步骤S914，根据访问请求中携带的邀请单标识读取邀请单中的记录信息。
步骤S916，解析老年用户的身份证件标识，并根据解析获得的用户特征类型确定展示配置参数。
步骤S918，将展示配置参数以及记录信息中的老年用户的注册信息以及邀请用户的身份标识向第二终端发送。
在此之后第二终端根据展示配置渲染包含注册信息以及身份标识的注册确认页并展示；第二终端向服务器提交针对注册信息的注册确认指令。
步骤S924，根据注册确认指令进行账户注册，并向第一终端发送注册结果。
综上所述，本实施例提供的账户注册处理方法，首先接收第一终端提交的目标用户的联系方式，并向第一终端返回信息采集页，然后根据第一终端提交的基于信息采集页录入的注册信息生成邀请单，并基于联系方式向第二终端发送基于邀请单生成的邀请链接，再在邀请链接被触发后根据注册信息确定目标用户的展示配置参数；若接收到第二终端基于展示配置参数进行信息展示后提交的注册确认指令，基于注册信息进行账户注册，并向第一终端发送注册结果，以此，通过由邀请用户进行注册邀请，减少特殊群体在账户注册流程中需要执行的操作，降低账户注册门槛。
本说明书提供的第二种账户注册处理方法实施例：参照图10，其示出了本实施例提供的一种账户注册处理方法处理流程图，参照图2，其示出了本实施例提供的一种账户注册处理方法的场景示意图，参照图3，其示出了本实施例提供的一种初始页面示意图，参照图4，其示出了本实施例提供的一种信息采集页示意图，参照图5，其示出了本实施例提供的一种等待提醒页示意图，参照图6，其示出了本实施例提供的一种注册确认页示意图，参照图9，其示出了本实施例提供的一种应用于邀请注册场景的账户注册处理方法时序图，参照图11，其示出了本实施例提供的一种邀请处理流程的处理流程图。
参照图10，本实施例提供的账户注册处理方法，应用于第一终端，具体包括步骤S1002至步骤S1006。
步骤S1002，通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页。
实际应用中，特殊群体(例如：老年人群)可能由于记忆力或视觉能力下降，对于信息的理解和辨识的能力较差，在用户账户的注册过程中对于填写注册信息存在一定的困难，本实施例提供的账户注册处理方法，在邀请注册的过程中由邀请用户代为填写注册信息，被邀请用户只需要确认即可实现被邀请用户的账户注册，具体的，服务器接收邀请用户提交的被邀请用户的联系方式并向邀请用户返回信息采集页，再根据邀请用户提交的被邀请用户的注册信息生成邀请单，并根据被邀请用户的联系方式向被邀请用户发送基于邀请单标识生成的邀请链接，在被邀请用户触发邀请链接后基于确定的展示配置参数向被邀请用户进行信息展示，并根据被邀请用户基于信息展示提交的注册确认指令进行账户注册，在注册后向邀请用户发送注册结果，以此减少了被邀请用户的操作流程，降低了被邀请用户的操作门槛，此外，及时向邀请用户反馈注册结果，以使邀请用 户根据注册结果邀请被邀请用户开通更多服务或者提醒邀请用户注册失败的原因。
本实施例所述第一终端包括邀请用户(发起用户)的用户终端，该邀请用户为已经进行账户注册的用户；邀请用户通过第一终端提交被邀请用户的手机号码，以完成对被邀请用户的账户注册，被邀请用户为所述目标用户，被邀请用户的用户终端为第二终端。
如图2所示，本实施例提供的一种账户注册处理方法的场景示意图中的场景包括：发起用户的第一终端、服务器和目标用户的第二终端。其中，第一终端和第二终端可以为手机、平板电脑、台式计算机、便携笔记本式计算机、智能手表等(图2中仅示出手机)。服务器，可以是独立的服务器，也可以是由多个服务器组成的服务器集群。
具体实施时，发起用户利用第一终端通过初始页面向服务器提交目标用户的联系方式，为了保证目标用户的安全性，服务器在接收到第一终端提交的目标用户的联系方式后，对该联系方式进行核验，在核验通过的情况下才能向第一终端返回信息采集页，在接收信息采集页之前，服务器执行如下步骤：接收所述联系方式，基于所述联系方式核验所述目标用户是否满足注册条件；若是，执行所述向所述第一终端返回信息采集页操作；若否，基于核验失败类型向所述第一终端发送提醒信息。
具体的，服务器基于联系方式核验目标用户是否满足注册条件的过程中，核验该联系方式是否已经被注册，并且核验该联系方式是否被标记为黑灰名单；如果该目标用户不满足注册条件，则向第一终端发送相关原因，以提升发起用户对核验结果的感知程度。
例如，邀请用户通过邀请终端上如图3所示的初始页面提交被邀请的老年用户的联系方式，服务器获取到该联系方式后，在注册记录表中查询是否存在该联系方式的注册记录，若否，则将该联系方式输入可信算法中进行可信校验，若可信算法输出的校验结果为校验通过，则向邀请终端返回如图4所示的信息采集页。需要说明的是，邀请用户可通过触发301查看通讯录并从通讯录选择好友，邀请终端在检测到“下一步”控件被触发则向服务器提交联系方式；邀请终端在展示图4的信息采集页后，邀请用户录入老年用户的姓名以及身份标识，邀请终端在检测到“确认”控件被触发则向服务器提交由姓名和身份标识组成的老年用户的注册信息。
步骤S1004，通过所述信息采集页录入目标用户的注册信息并向所述服务器提交。
实际应用中，邀请目标用户进行账户注册是通过分享以实现营销效果，依然存在目标用户在账户注册过程中的门槛问题，所以对特殊人群的邀请成功率较低，且作为发起用户，无法感知到目标用户在账户注册中遇到的注册问题及具体原因，需要花费时间反复沟通。本实施例通过由发起用户为目标用户代填注册信息以完成目标用户的账户注册。
具体实施时，在发起用户通过信息采集页填写目标用户的注册信息的过程中，为了提升注册效率，避免由于发起用户填写的注册信息的格式不符合格式条件导致注册失败，对发起用户填写的目标用户的注册信息，要进行合法性校验，本实施例提供的一种可选实施方式中，第一终端在采集注册信息的过程中，执行如下步骤：采集所述信息采集页录入的所述注册信息；校验所述注册信息的格式是否符合格式条件；若是，在检测到所述信息采集页配置的确认控件被触发时提交所述注册信息；若否，展示格式提醒，以提醒所述第一终端所属的发起用户重新录入所述注册信息。
具体的，在发起用户填写注册信息的过程中，第一终端检测用户录入的注册信息是否符合格式条件，若符合，则在检测到信息采集页面配置的确认控件被触发的情况下向服务器提交发起用户录入的注册信息，若不符合，则展示格式提醒，以提醒发起用户按照展示的格式提醒重新录入注册信息。
服务器在接收到注册信息后，根据第一终端提交的基于信息采集页录入的注册信息生成邀请单，并基于联系方式向第二终端发送基于邀请单生成的邀请链接。所述邀请单，根据注册信息以及发起用户的身份信息生成，邀请单中还包括邀请状态以及注册响应结果，邀请单中的邀请状态包括等待中(WAITING)、待确认(PENDING)、注册中(REGISTERING)、注册成功(SUCCESS)和/或注册失败(FAIL)；若邀请状态为“FAIL”， 则在注册响应结果中添加注册失败原因。
具体实施时，服务器接收到第一终端提交的注册信息后，根据发起用户的身份信息和目标用户的注册信息生成邀请单，根据邀请单生成邀请链接向目标用户的第二终端发送。在基于联系方式向第二终端发送邀请链接的过程中，服务器执行如下步骤：根据所述邀请单的邀请单标识生成所述邀请链接；基于所述联系方式向所述目标用户发送携带所述邀请链接的注册提醒，并向所述第一终端发送所述注册提醒已发送的等待提醒。
具体的，服务器在接收到第一终端提交的联系方式后，通过与第一终端关联的用户账户读取与该用户账户具有关联关系的身份信息，并基于发起用户的身份信息和目标用户的注册信息创建邀请单，再根据邀请单标识生成邀请链接，基于联系方式向第二终端发送携带邀请链接的注册提醒。
例如，服务器根据与邀请终端关联的邀请用户的用户账户查询与该用户账户具有关联关系的身份信息，并基于根据邀请人账户ID确定的邀请用户的姓名“用户A”与邀请用户通过邀请终端通过如图4所示的信息采集页提交的老年用户“用户B”的姓名和身份标识的注册信息创建如表1所示的邀请单，邀请单创建初期，邀请状态为“WAITING”，在原始邀请链接中拼接邀请单ID，再生成短链接，将该短链接通过短信等方式发送给老年用户“用户B”。为了使邀请用户能够及时感知到邀请进度，在向老年用户“用户B”发送短信后，向邀请用户发送如图5所示的等待提醒页，邀请用户可通过该等待提醒向老年用户发送携带短链接的短信。
Figure PCTCN2022091543-appb-000002
表1
如图5所示，向邀请用户发送的等待提醒页中包含向老年用户“用户B”发送的邀请短信的具体内容，并配置“再次发送短信”控件，在老年用户“用户B”在一定时间内未触发邀请短信中的邀请链接，则可通过触发“再次发送短信”控件再次向老年用户“用户B”发送邀请短信。
需要说明的是，在邀请单创建后，为了使发起用户对能够随时查看邀请单的邀请状态，服务器向发起用户的第一终端发送包含邀请单标识的查看提醒。具体的，发起用户通过如下方式查看邀请状态：基于所述邀请单的邀请单标识，向所述第一终端发送对所述邀请单的查看提醒；在所述查看提醒被触发后，查询所述邀请单中记录的邀请状态并向所述第一终端发送。本实施例提供的一种可选实施方式中，接收所述服务器发送的携带邀请单标识的邀请单提醒；在所述邀请单提醒被触发后，获取所述邀请单中记录的邀请状态。在发起用户提交针对查看提醒的访问请求后，根据访问请求中携带的邀请单标识查看对应的邀请单中的邀请状态并向发起用户发送。
向第二终端发送邀请链接后，服务器在邀请链接被触发后根据所述注册信息确定目标用户的展示配置参数。所述展示配置参数，包括向所述目标用户展示所述注册信息是展示页面中的字体大小以及展示文案等。
具体实施时，在目标用户触发邀请链接后，服务器识别注册信息中的用户特征类型，确定展示的页面样式，例如超过60岁以上的老年人，利用大字版的页面，并渲染老年人感兴趣的引导文案，强化老年人的注册意愿。在邀请链接被触发后根据注册信息确定目标用户的展示配置参数的过程中，服务器执行如下步骤：在所述邀请链接被触发后根据所述邀请链接中携带的邀请单标识读取所述邀请单的记录内容；解析所述记录内容中所述目标用户的身份证件标识，获得所述目标用户的用户特征类型；将所述用户特征类型输入参数配置算法进行参数配置，获得所述展示配置参数。
具体的，服务器通过解析目标用户的身份证件标识，获得目标用户的用户特征类型 (如：用户第一特征、用户第二特征等)，将用户特征类型输入参数配置算法中，参数配置算法根据用户特征类型确定向目标用户进行注册信息的展示的过程中的展示字号以及展示文案。
例如，服务器获取到老年用户“用户B”提交的对邀请链接的访问请求后，根据该邀请链接中的邀请单标识查询对应的邀请单中记录的信息，将查询到的老年用户的身份标识进行解析，获得老年用户“用户B”为男性，63岁，将男性、63岁这两个用户特征输入参数配置算法中，获得参数配置算法输出的展示字号类型为大字号，引导文案为“注册可查看股票趋势”。
具体实施时，服务器在获得参数配置算法输出的展示配置参数后，基于展示配置参数以及邀请单中的记录信息渲染注册确认页，并通过目标用户的第二终端进行展示，在获得展示配置参数后，服务器执行如下步骤：基于所述展示配置参数，渲染包含所述注册信息以及身份信息中的身份标识的所述注册确认页；将所述注册确认页通过所述第二终端进行展示；其中，所述身份信息为基于所述第一终端的账户信息读取的与所述账户信息具有关联关系的身份信息。
需要说明的是，对于注册确认页的渲染，可以由服务器来完成，具体的，服务器根据获得的展示配置参数，生成注册确认页并向第二终端发送，以使第二终端将注册确认页进行展示；此外，也可以由第二终端渲染注册确认页，具体的，服务器获得展示配置参数后，将展示配置参数以及记录信息向第二终端发送，第二终端根据展示配置参数以及记录信息渲染注册确认页并展示。
如图6所示，服务器在获取到根据老年用户“用户B”的用户第一特征及用户第二特征确定的展示配置参数后，将展示配置参数，根据邀请人账户ID确定的邀请用户的姓名“用户A”及老年用户“用户B”的姓名、联系方式以及身份标识向老年用户“用户B”的被邀请终端发送，被邀请终端根据上述信息渲染出注册确认页并展示。此外，在进行账户注册过程中，需要获取对于服务隐私协议的授权指令，为了进一步简化操作流程，在注册确认页中渲染对服务隐私协议的授权提醒。老年用户在确认姓名、联系方式及身份标识正确后，可通过触发注册确认页中配置的“确认，本机号码直接注册”控件提交注册确认请求。其中，注册确认页中包含用户A的姓名，包含老年用户“用户B”的姓名，手机号及身份标识，此外，还渲染有对老年用户“用户B”的引导文案“注册可查看股票趋势”。
需要说明的是，在目标用户访问邀请链接之后，服务器将邀请单中的邀请状态更新为“PENDING”；在目标用户通过注册确认页提交注册确认指令后，将邀请单中的邀请状态更新为“REGISTERING”；以便发起用户进行查看。
具体实施时，服务器若接收到第二终端基于展示配置参数进行信息展示后提交的注册确认指令，基于注册信息进行账户注册，并向第一终端发送注册结果。服务器在获取到目标用户通过第二终端展示的注册确认页提交注册确认请求后，基于目标用户的联系方式与注册信息进行账户注册，服务器通过如下方式进行账户注册：基于账户标识生成算法生成账户标识；建立所述账户标识与所述注册信息以及所述联系方式的关联关系；将所述账户标识通过所述第二终端向所述目标用户发送。
具体的，利用账户标识生成算法生成账户标识，再建立账户标识与目标用户的联系方式以及注册信息之间的关联关系，以将该账户标识分配给目标用户；此外，在进行账户注册的过程中，还可以将目标用户的联系方式以及注册信息输入账户标识生成算法，获得账户标识生成算法输出的与联系方式以及注册信息具有关联关系的账户标识，将该账户标识确定为目标用户的账户标识。
为了提升发起用户对邀请进度的感知程度，当目标用户注册成功或注册失败后，服务器更新邀请单，并将更新后的注册结果向第一终端发送；在进行账户注册之后，服务器首先根据所述注册结果更新所述邀请单中的邀请状态，再基于所述邀请状态向所述第一终端发送所述注册结果；其中，若所述注册结果为注册成功，则将所述注册成功的注 册结果更新至所述邀请单；若所述注册结果为注册失败，则读取注册失败原因，并将所述注册失败原因与所述注册失败的注册结果更新至所述邀请单。
具体的，若注册成功，则将邀请单中的邀请状态更新为“SUCCESS”，并向第一终端发送注册成功的提醒，以引导发起用户添加目标用户的用户账户为好友或者邀请目标用户开通更多服务；若注册失败，则将邀请单中的邀请状态更新为“FAIL”，将注册响应结果更新为失败原因，并向第一终端发送包含失败原因的注册失败的提醒，引导发起用户尝试利用其他方式进行邀请。需要说明的是，在向发起用户发送注册结果的提醒时，可在原始通知链接中拼接邀请单ID，再生成短链接，通过站内信等的方式向发起用户发送注册结果；其中，若检测到发起用户对该短链接的访问请求，则基于该访问请求中的邀请单ID，查询该邀请单中的邀请状态，并将该邀请状态向发起用户展示。
步骤S1006，接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
如图2所示，在发起用户邀请目标用户进行账户注册时，发起用户通过第一终端向服务器提交目标用户的联系方式；服务器核验联系方式是否满足注册邀请条件；若否，基于核验失败类型向第一终端发送提醒信息；若是，则向第一终端返回信息采集页；第一终端通过信息采集页向服务器提交目标用户的注册信息；服务器基于注册信息创建邀请单，并根据邀请单的邀请单标识创建邀请链接向目标用户的第二终端发送；服务器在检测到邀请链接被触发的情况下，根据邀请单标识读取邀请单中的记录信息；服务器解析记录信息中的身份证件标识获得目标用户的用户特征类型；服务器将用户特征类型输入参数配置算法进行参数配置，获得针对目标用户的展示配置参数；服务器基于展示配置参数与记录信息渲染信息展示页；服务器将信息展示页向第二终端发送，以使第二终端向目标用户展示；服务器获取第二终端提交的目标用户对记录信息的注册确认提醒，基于注册确认提醒进行账户注册，并将注册结果向第一终端发送，以使第一终端向发起用户展示。
下述为本实施例提供的一种邀请处理流程，参见图11，一种邀请处理流程的处理流程图，具体包括下述步骤S1102至步骤S1108。需要说明的是，本实施例提供的邀请处理流程，在执行过程中与上述应用于服务器的邀请处理流程相互配合。
步骤S1102，向服务器提交老年用户的联系方式。
步骤S1104，获取服务器核验通过后返回的信息采集页。
步骤S1106，校验邀请用户基于信息采集页录入的注册信息是否符合格式条件；若是，则执行步骤S1108；若否，展示格式提醒，以引导邀请用户重新录入。
步骤S1108，在检测到邀请用户触发信息采集页配置的确认控件时向服务器提交注册信息。
下述以本实施例提供的一种账户注册处理方法在邀请注册场景的应用为例，对本实施例提供的账户注册处理方法进行进一步说明，参见图9，应用于邀请注册场景的账户注册处理方法，包括如下步骤。
步骤S902，向服务器提交老年用户的联系方式。
步骤S904，接收服务器返回的信息采集页。
步骤S906，基于信息采集页向服务器提交老年用户的注册信息。
在此之后，服务器根据老年用户的注册信息以及邀请用户的身份标识创建邀请单；根据邀请单的邀请单标识生成邀请链接并向第二终端发送，在向第二终端发送邀请链接后向第一终端发送等待提醒；第二终端向服务器提交对邀请链接的访问请求；服务器根据访问请求中携带的邀请单标识读取邀请单中的记录信息；解析老年用户的身份证件标识，并根据解析获得的用户特征类型确定展示配置参数；将展示配置参数以及记录信息中的老年用户的注册信息以及邀请用户的身份标识向第二终端发送；第二终端根据展示配置渲染包含注册信息以及身份标识的注册确认页并展示；第二终端向服务器提交针对注册信息的注册确认指令；服务器根据注册确认指令进行账户注册，并向第一终端发送 注册结果。
综上所述，本实施例提供的账户注册处理方法，首先通过初始页面向服务器提交目标用户的联系方式，并接收服务器返回的信息采集页，然后通过信息采集页录入目标用户的注册信息并向服务器提交，最后接收服务器基于注册信息进行注册处理后返回的注册结果，以此，通过填写目标用户的联系方式和注册信息以邀请目标用户进行账户注册。
本说明书提供的第三种账户注册处理方法实施例：参照图12，其示出本实施例提供的一种账户注册处理方法处理流程图，参照图2，其示出本实施例提供的一种账户注册处理方法的场景示意图，参照图3，其示出本实施例提供的一种初始页面示意图，参照图4，其示出本实施例提供的一种信息采集页示意图，参照图5，其示出本实施例提供的一种等待提醒页示意图，参照图6，其示出本实施例提供的一种注册确认页示意图，参照图9，其示出本实施例提供的一种应用于邀请注册场景的账户注册处理方法时序图，参照图13，其示出本实施例提供的一种注册处理流程的处理流程图。
参照图12，本实施例提供的账户注册处理方法，应用于第二终端，具体包括步骤S1202至步骤S1206。
步骤S1202，接收服务器发送的邀请链接。
实际应用中，特殊群体(例如：老年人群)可能由于记忆力或视觉能力下降，对于信息的理解和辨识的能力较差，在用户账户的注册过程中对于填写注册信息存在一定的困难，本实施例提供的账户注册处理方法，在邀请注册的过程中由邀请用户代为填写注册信息，被邀请用户只需要确认即可实现被邀请用户的账户注册，具体的，服务器接收邀请用户提交的被邀请用户的联系方式并向邀请用户返回信息采集页，再根据邀请用户提交的被邀请用户的注册信息生成邀请单，并根据被邀请用户的联系方式向被邀请用户发送基于邀请单标识生成的邀请链接，在被邀请用户触发邀请链接后基于确定的展示配置参数向被邀请用户进行信息展示，并根据被邀请用户基于信息展示提交的注册确认指令进行账户注册，在注册后向邀请用户发送注册结果，以此减少了被邀请用户的操作流程，降低了被邀请用户的操作门槛，此外，及时向邀请用户反馈注册结果，以使邀请用户根据注册结果邀请被邀请用户开通更多服务或者提醒邀请用户注册失败的原因。
本实施例所述第一终端包括邀请用户(发起用户)的用户终端，该邀请用户为已经进行账户注册的用户；邀请用户通过第一终端提交被邀请用户的手机号码，以完成对被邀请用户的账户注册，被邀请用户为所述目标用户，被邀请用户的用户终端为第二终端。
如图2所示，本实施例提供的一种账户注册处理方法的场景示意图中的场景包括：发起用户的第一终端、服务器和目标用户的第二终端。其中，第一终端和第二终端可以为手机、平板电脑、台式计算机、便携笔记本式计算机、智能手表等(图2中仅示出手机)。服务器，可以是独立的服务器，也可以是由多个服务器组成的服务器集群。
具体实施时，发起用户利用第一终端通过初始页面向服务器提交目标用户的联系方式，为了保证目标用户的安全性，服务器在接收到第一终端提交的目标用户的联系方式后，对该联系方式进行核验，在核验通过的情况下才能向第一终端返回信息采集页，在接收信息采集页之前，服务器执行如下步骤：接收所述联系方式，基于所述联系方式核验所述目标用户是否满足注册条件；若是，执行所述向所述第一终端返回信息采集页操作；若否，基于核验失败类型向所述第一终端发送提醒信息。
具体的，服务器基于联系方式核验目标用户是否满足注册条件的过程中，核验该联系方式是否已经被注册，并且核验该联系方式是否被标记为黑灰名单；如果该目标用户不满足注册条件，则向第一终端发送相关原因，以提升发起用户对核验结果的感知程度。
例如，邀请用户通过邀请终端上如图3所示的初始页面提交被邀请的老年用户的联系方式，服务器获取到该联系方式后，在注册记录表中查询是否存在该联系方式的注册记录，若否，则将该联系方式输入可信算法中进行可信校验，若可信算法输出的校验结果为校验通过，则向邀请终端返回如图4所示的信息采集页。需要说明的是，邀请用户 可通过触发301查看通讯录并从通讯录选择好友，邀请终端在检测到“下一步”控件被触发则向服务器提交联系方式；邀请终端在展示图4的信息采集页后，邀请用户录入老年用户的姓名以及身份标识，邀请终端在检测到“确认”控件被触发则向服务器提交由姓名和身份标识组成的老年用户的注册信息。
实际应用中，邀请目标用户进行账户注册是通过分享以实现营销效果，依然存在目标用户在账户注册过程中的门槛问题，所以对特殊人群的邀请成功率较低，且作为发起用户，无法感知到目标用户在账户注册中遇到的注册问题及具体原因，需要花费时间反复沟通。本实施例通过由发起用户为目标用户代填注册信息以完成目标用户的账户注册。
具体实施时，在发起用户通过信息采集页填写目标用户的注册信息的过程中，为了提升注册效率，避免由于发起用户填写的注册信息的格式不符合格式条件导致注册失败，对发起用户填写的目标用户的注册信息，要进行合法性校验，本实施例提供的一种可选实施方式中，第一终端在采集注册信息的过程中，执行如下步骤：采集所述信息采集页录入的所述注册信息；校验所述注册信息的格式是否符合格式条件；若是，在检测到所述信息采集页配置的确认控件被触发时提交所述注册信息；若否，展示格式提醒，以提醒所述第一终端所属的发起用户重新录入所述注册信息。
具体的，在发起用户填写注册信息的过程中，第一终端检测用户录入的注册信息是否符合格式条件，若符合，则在检测到信息采集页面配置的确认控件被触发的情况下向服务器提交发起用户录入的注册信息，若不符合，则展示格式提醒，以提醒发起用户按照展示的格式提醒重新录入注册信息。
服务器在接收到注册信息后，根据第一终端提交的基于信息采集页录入的注册信息生成邀请单，并基于联系方式向第二终端发送基于邀请单生成的邀请链接。所述邀请单，根据注册信息以及发起用户的身份信息生成，邀请单中还包括邀请状态以及注册响应结果，邀请单中的邀请状态包括等待中(WAITING)、待确认(PENDING)、注册中(REGISTERING)、注册成功(SUCCESS)和/或注册失败(FAIL)；若邀请状态为“FAIL”，则在注册响应结果中添加注册失败原因。
具体实施时，服务器接收到第一终端提交的注册信息后，根据发起用户的身份信息和目标用户的注册信息生成邀请单，根据邀请单生成邀请链接向目标用户的第二终端发送。在基于联系方式向第二终端发送邀请链接的过程中，服务器执行如下步骤：根据所述邀请单的邀请单标识生成所述邀请链接；基于所述联系方式向所述目标用户发送携带所述邀请链接的注册提醒，并向所述第一终端发送所述注册提醒已发送的等待提醒。
具体的，服务器在接收到第一终端提交的联系方式后，通过与第一终端关联的用户账户读取与该用户账户具有关联关系的身份信息，并基于发起用户的身份信息和目标用户的注册信息创建邀请单，再根据邀请单标识生成邀请链接，基于联系方式向第二终端发送携带邀请链接的注册提醒。例如，服务器根据与邀请终端关联的邀请用户的用户账户查询与该用户账户具有关联关系的身份信息，并基于邀请用户的邀请人账户ID与邀请用户通过邀请终端通过如图4所示的信息采集页提交的老年用户“用户B”的姓名和身份标识的注册信息创建如表1所示的邀请单，邀请单创建初期，邀请状态为“WAITING”，在原始邀请链接中拼接邀请单ID，再生成短链接，将该短链接通过短信等方式发送给老年用户“用户B”。为了使邀请用户能够及时感知到邀请进度，在向老年用户“用户B”发送短信后，向邀请用户发送如图5所示的等待提醒页，邀请用户可通过该等待提醒向老年用户发送携带短链接的邀请短信。
Figure PCTCN2022091543-appb-000003
表1
如图5所示，向邀请用户发送的等待提醒页中包含向老年用户“用户B”发送的邀请短信的具体内容，并配置“再次发送短信”控件，在老年用户“用户B”在一定时间内未触发邀请短信中的邀请链接，则可通过触发“再次发送短信”控件再次向老年用户“用户B”发送邀请短信。
需要说明的是，在邀请单创建后，为了使发起用户对能够随时查看邀请单的邀请状态，服务器向发起用户的第一终端发送包含邀请单标识的查看提醒。具体的，发起用户通过如下方式查看邀请状态：基于所述邀请单的邀请单标识，向所述第一终端发送对所述邀请单的查看提醒；在所述查看提醒被触发后，查询所述邀请单中记录的邀请状态并向所述第一终端发送。本实施例提供的一种可选实施方式中，接收所述服务器发送的携带邀请单标识的邀请单提醒；在所述邀请单提醒被触发后，获取所述邀请单中记录的邀请状态。在发起用户提交针对查看提醒的访问请求后，根据访问请求中携带的邀请单标识查看对应的邀请单中的邀请状态并向发起用户发送。
步骤S1204，在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页。
向第二终端发送邀请链接后，服务器在邀请链接被触发后根据所述注册信息确定目标用户的展示配置参数。所述展示配置参数，包括向所述目标用户展示所述注册信息是展示页面中的字体大小以及展示文案等。
具体实施时，在目标用户触发邀请链接后，服务器识别注册信息中的用户特征类型，确定展示的页面样式，例如超过60岁以上的老年人，利用大字版的页面，并渲染老年人感兴趣的引导文案，强化老年人的注册意愿。在邀请链接被触发后根据注册信息确定目标用户的展示配置参数的过程中，服务器执行如下步骤：在所述邀请链接被触发后根据所述邀请链接中携带的邀请单标识读取所述邀请单的记录内容；解析所述记录内容中所述目标用户的身份证件标识，获得所述目标用户的用户特征类型；将所述用户特征类型输入参数配置算法进行参数配置，获得所述展示配置参数。
具体的，服务器通过解析目标用户的身份证件标识，获得目标用户的用户特征类型(如：用户第一特征、用户第二特征等)，将用户特征类型输入参数配置算法中，参数配置算法根据用户特征类型确定向目标用户进行注册信息的展示的过程中的展示字号以及展示文案。
例如，服务器获取到老年用户“用户B”提交的对邀请链接的访问请求后，根据该邀请链接中的邀请单标识查询对应的邀请单中记录的信息，将查询到的老年用户的身份标识进行解析，获得老年用户“用户B”为男性，63岁，将男性、63岁这两个用户特征输入参数配置算法中，获得参数配置算法输出的展示字号类型为大字号，引导文案为“注册可查看股票趋势”。
具体实施时，服务器在获得参数配置算法输出的展示配置参数后，基于展示配置参数以及邀请单中的记录信息渲染注册确认页，并通过目标用户的第二终端进行展示，在获得展示配置参数后，服务器执行如下步骤：基于所述展示配置参数，渲染包含所述注册信息以及身份信息中的身份标识的所述注册确认页；将所述注册确认页通过所述第二终端进行展示；其中，所述身份信息为基于所述第一终端的账户信息读取的与所述账户信息具有关联关系的身份信息。
需要说明的是，对于注册确认页的渲染，可以由服务器来完成，具体的，服务器根据获得的展示配置参数，生成注册确认页并向第二终端发送，以使第二终端将注册确认页进行展示；此外，也可以由第二终端渲染注册确认页，具体的，服务器获得展示配置参数后，将展示配置参数以及记录信息向第二终端发送，第二终端根据展示配置参数以及记录信息渲染注册确认页并展示。
如图6所示，服务器在获取到根据老年用户“用户B”的用户第一特征及用户第二特征确定的展示配置参数后，将展示配置参数，根据邀请人账户ID确定的邀请用户的姓 名“用户A”及老年用户“用户B”的姓名、联系方式以及身份标识向老年用户“用户B”的被邀请终端发送，被邀请终端根据上述信息渲染出注册确认页并展示。此外，在进行账户注册过程中，需要获取对于服务隐私协议的授权指令，为了进一步简化操作流程，在注册确认页中渲染对服务隐私协议的授权提醒。老年用户在确认姓名、联系方式及身份标识正确后，可通过触发注册确认页中配置的“确认，本机号码直接注册”控件提交注册确认请求。其中，注册确认页中包含用户A的姓名，包含老年用户“用户B”的姓名，手机号及身份标识，此外，还渲染有对老年用户“用户B”的引导文案“注册可查看股票趋势”。
需要说明的是，在目标用户访问邀请链接之后，服务器将邀请单中的邀请状态更新为“PENDING”；在目标用户通过注册确认页提交注册确认指令后，将邀请单中的邀请状态更新为“REGISTERING”；以便发起用户进行查看。
步骤S1206，在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
具体实施时，服务器若接收到第二终端基于展示配置参数进行信息展示后提交的注册确认指令，基于注册信息进行账户注册，并向第一终端发送注册结果。服务器在获取到目标用户通过第二终端展示的注册确认页提交注册确认请求后，基于目标用户的联系方式与注册信息进行账户注册，服务器通过如下方式进行账户注册：基于账户标识生成算法生成账户标识；建立所述账户标识与所述注册信息以及所述联系方式的关联关系；将所述账户标识通过所述第二终端向所述目标用户发送。
具体的，利用账户标识生成算法生成账户标识，再建立账户标识与目标用户的联系方式以及注册信息之间的关联关系，以将该账户标识分配给目标用户；此外，在进行账户注册的过程中，还可以将目标用户的联系方式以及注册信息输入账户标识生成算法，获得账户标识生成算法输出的与联系方式以及注册信息具有关联关系的账户标识，将该账户标识确定为目标用户的账户标识。
为了提升发起用户对邀请进度的感知程度，当目标用户注册成功或注册失败后，服务器更新邀请单，并将更新后的注册结果向第一终端发送；在进行账户注册之后，服务器首先根据所述注册结果更新所述邀请单中的邀请状态，再基于所述邀请状态向所述第一终端发送所述注册结果；其中，若所述注册结果为注册成功，则将所述注册成功的注册结果更新至所述邀请单；若所述注册结果为注册失败，则读取注册失败原因，并将所述注册失败原因与所述注册失败的注册结果更新至所述邀请单。
具体的，若注册成功，则将邀请单中的邀请状态更新为“SUCCESS”，并向第一终端发送注册成功的提醒，以引导发起用户添加目标用户的用户账户为好友或者邀请目标用户开通更多服务；若注册失败，则将邀请单中的邀请状态更新为“FAIL”，将注册响应结果更新为失败原因，并向第一终端发送包含失败原因的注册失败的提醒，引导发起用户尝试利用其他方式进行邀请。需要说明的是，在向发起用户发送注册结果的提醒时，可在原始通知链接中拼接邀请单ID，再生成短链接，通过站内信等的方式向发起用户发送注册结果；其中，若检测到发起用户对该短链接的访问请求，则基于该访问请求中的邀请单ID，查询该邀请单中的邀请状态，并将该邀请状态向发起用户展示。本实施例提供的一种可选实施方式中，若所述服务器在接收所述注册确认指令后，基于所述注册信息进行账户注册的注册结果为注册成功，则接收所述服务器发送的账户标识并展示。
如图2所示，在发起用户邀请目标用户进行账户注册时，发起用户通过第一终端向服务器提交目标用户的联系方式；服务器核验联系方式是否满足注册邀请条件；若否，基于核验失败类型向第一终端发送提醒信息；若是，则向第一终端返回信息采集页；第一终端通过信息采集页向服务器提交目标用户的注册信息；服务器基于注册信息创建邀请单，并根据邀请单的邀请单标识创建邀请链接向目标用户的第二终端发送；服务器在检测到邀请链接被触发的情况下，根据邀请单标识读取邀请单中的记录信息；服务器解析记录信息中的身份证件标识获得目标用户的用户特征类型；服务器将用户特征类型输 入参数配置算法进行参数配置，获得针对目标用户的展示配置参数；服务器基于展示配置参数与记录信息渲染信息展示页；服务器将信息展示页向第二终端发送，以使第二终端向目标用户展示；服务器获取第二终端提交的目标用户对记录信息的注册确认提醒，基于注册确认提醒进行账户注册，并将注册结果向第一终端发送，以使第一终端向发起用户展示。
下述为本实施例提供的一种注册处理流程，参见图13，一种注册处理流程的处理流程图，具体包括下述步骤S1302至步骤S1312。需要说明的是，本实施例提供的注册处理流程，在执行过程中与上述应用于服务器的注册处理流程相互配合。
步骤S1302，接收服务器发送的根据邀请单标识生成的邀请链接。
步骤S1304，在检测到邀请链接被触发后向服务器提交对邀请链接的访问请求。
步骤S1306，接收服务器发送的展示配置参数以及记录信息。
步骤S1308，基于展示配置参数渲染包含记录信息的注册确认页面并展示。
步骤S1310，在检测到注册确认页面的确认控件被触发后向服务器提交注册确认指令。
步骤S1312，接收服务器发送的与老年用户的联系方式以及注册信息具有关联关系的用户账户。
下述以本实施例提供的一种账户注册处理方法在邀请注册场景的应用为例，对本实施例提供的账户注册处理方法进行进一步说明，参见图9，应用于邀请注册场景的账户注册处理方法，包括如下步骤。
步骤S912，第二终端向服务器提交对邀请链接的访问请求。
在此之前，第一终端向服务器提交老年用户的联系方式；第一终端接收服务器返回的信息采集页；第一终端基于信息采集页向服务器提交老年用户的注册信息；服务器根据老年用户的注册信息以及邀请用户的身份标识创建邀请单；服务器根据邀请单的邀请单标识生成邀请链接并向第二终端发送，在向第二终端发送邀请链接后向第一终端发送等待提醒。
在此之后，服务器根据访问请求中携带的邀请单标识读取邀请单中的记录信息；解析老年用户的身份证件标识，并根据解析获得的用户特征类型确定展示配置参数；将展示配置参数以及记录信息中的老年用户的注册信息以及邀请用户的身份标识向第二终端发送。
步骤S920，第二终端根据展示配置渲染包含注册信息以及身份标识的注册确认页并展示。
步骤S922，第二终端向服务器提交针对注册信息的注册确认指令。
此后，服务器根据注册确认指令进行账户注册，并向第一终端发送注册结果。
综上所述，本实施例提供的账户注册处理方法，首先接收服务器发送的邀请链接，然后在邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页，最后在注册确认页配置的注册确认控件被触发后向服务器提交注册确认指令，以此，目标用户仅提交注册确认指令即可进行账户注册，提升账户注册的简便性。
本说明书提供的第一种账户注册处理装置实施例如下：在上述的实施例中，提供了一种应用于服务器的账户注册处理方法，与之相对应的，还提供了一种账户注册处理装置，运行于服务器，下面结合附图进行说明。
参照图14，其示出了本实施例提供的一种账户注册处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种账户注册处理装置，运行于服务器，包括：联系方式接收模块1402，被配置为接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采 集页；邀请单生成模块1404，被配置为根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接；参数确定模块1406，被配置为在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数；账户注册模块1408，被配置为若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
本说明书提供的第二种账户注册处理装置实施例如下：在上述的实施例中，提供了一种应用于第一终端的账户注册处理方法，与之相对应的，还提供了一种账户注册处理装置，运行于第一终端，下面结合附图进行说明。
参照图15，其示出了本实施例提供的一种账户注册处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种账户注册处理装置，运行于第一终端，包括：联系方式提交模块1502，被配置为通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页；注册信息提交模块1504，被配置为通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交；注册结果接收模块1506，被配置为接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
本说明书提供的第三种账户注册处理装置实施例如下：在上述的实施例中，提供了一种应用于第二终端的账户注册处理方法，与之相对应的，还提供了一种账户注册处理装置，运行于第二终端，下面结合附图进行说明。
参照图16，其示出了本实施例提供的一种账户注册处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种账户注册处理装置，运行于第二终端，包括：接收模块1602，被配置为接收服务器发送的邀请链接；展示模块1604，被配置为在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页；提交模块1606，被配置为在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
本说明书提供的第一种账户注册处理设备实施例如下：对应上述描述的一种应用于服务器的账户注册处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种账户注册处理设备，运行于服务器，该账户注册处理设备用于执行上述提供的账户注册处理方法，图17为本说明书一个或多个实施例提供的第一种账户注册处理设备的结构示意图。
本实施例提供的一种账户注册处理设备，运行于服务器，包括：如图17所示，账户注册处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器1701和存储器1702，存储器1702中可以存储有一个或一个以上存储应用程序或数据。其中，存储器1702可以是短暂存储或持久存储。存储在存储器1702的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括账户注册处理设备中的一系列计算机可执行指令。更进一步地，处理器1701可以设置为与存储器1702通信，在账户注册处理设备上执行存储器1702中的一系列计算机可执行指令。账户注册处理设备还可以包括一个或一个以上电源1703，一个或一个以上有线或无线网络接口1704，一个或一个以上输入/输出接口1705，一个或一个以上键盘1706等。
在一个具体的实施例中，账户注册处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对账户注册处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于 进行以下计算机可执行指令：接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页；根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接；在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数；若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
本说明书提供的第二种账户注册处理设备实施例如下：对应上述描述的一种应用于第一终端的账户注册处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种账户注册处理设备，运行于第一终端，该账户注册处理设备用于执行上述提供的账户注册处理方法，图18为本说明书一个或多个实施例提供的第二种账户注册处理设备的结构示意图。
本实施例提供的一种账户注册处理设备，运行于第一终端，包括：如图18所示，账户注册处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器1801和存储器1802，存储器1802中可以存储有一个或一个以上存储应用程序或数据。其中，存储器1802可以是短暂存储或持久存储。存储在存储器1802的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括账户注册处理设备中的一系列计算机可执行指令。更进一步地，处理器1801可以设置为与存储器1802通信，在账户注册处理设备上执行存储器1802中的一系列计算机可执行指令。账户注册处理设备还可以包括一个或一个以上电源1803，一个或一个以上有线或无线网络接口1804，一个或一个以上输入/输出接口1805，一个或一个以上键盘1806等。
在一个具体的实施例中，账户注册处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对账户注册处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页；通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交；接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
本说明书提供的第三种账户注册处理设备实施例如下：对应上述描述的一种应用于第二终端的账户注册处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种账户注册处理设备，运行于第二终端，该账户注册处理设备用于执行上述提供的账户注册处理方法，图19为本说明书一个或多个实施例提供的第三种账户注册处理设备的结构示意图。
本实施例提供的一种账户注册处理设备，运行于第二终端，包括：如图19所示，账户注册处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器1901和存储器1902，存储器1902中可以存储有一个或一个以上存储应用程序或数据。其中，存储器1902可以是短暂存储或持久存储。存储在存储器1902的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括账户注册处理设备中的一系列计算机可执行指令。更进一步地，处理器1901可以设置为与存储器1902通信，在账户注册处理设备上执行存储器1902中的一系列计算机可执行指令。账户注册处理设备还可以包括一个或一个以上电源1903，一个或一个以上有线或无线网络接口1904，一个或一个以上输入/输出接口1905，一个或一个以上键盘1906等。
在一个具体的实施例中，账户注册处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对账户注册处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：接收服务器发送的邀请链接；在所述邀请链接被触发后， 展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页；在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
本说明书提供的第一种存储介质实施例如下：对应上述描述的一种账户注册处理方法，应用于服务器，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页；根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接；在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数；若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于账户注册处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书提供的第二种存储介质实施例如下：对应上述描述的一种账户注册处理方法，应用于第一终端，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页；通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交；接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于账户注册处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书提供的第三种存储介质实施例如下：对应上述描述的一种账户注册处理方法，应用于第二终端，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：接收服务器发送的邀请链接；在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页；在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于账户注册处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪30年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field  Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字***“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的***、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书一个或多个实施例可提供为方法、***或计算机程序产品。因此，本说明书一个或多个实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本说明书可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书是参照根据本说明书实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框 或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于***实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本文件的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本文件可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围之内。

Claims (25)

  1. 一种账户注册处理方法，应用于服务器，包括：
    接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页；
    根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接；
    在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数；
    若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
  2. 根据权利要求1所述的账户注册处理方法，所述接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页，包括：
    接收所述联系方式，基于所述联系方式核验所述目标用户是否满足注册条件；
    若是，执行所述向所述第一终端返回信息采集页操作；
    若否，基于核验失败类型向所述第一终端发送提醒信息。
  3. 根据权利要求1所述的账户注册处理方法，所述基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接，包括：
    根据所述邀请单的邀请单标识生成所述邀请链接；
    基于所述联系方式向所述目标用户发送携带所述邀请链接的注册提醒，并向所述第一终端发送所述注册提醒已发送的等待提醒。
  4. 根据权利要求1所述的账户注册处理方法，所述在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数，包括：
    在所述邀请链接被触发后根据所述邀请链接中携带的邀请单标识读取所述邀请单的记录内容；
    解析所述记录内容中所述目标用户的身份证件标识，获得所述目标用户的用户特征类型；
    将所述用户特征类型输入参数配置算法进行参数配置，获得所述展示配置参数。
  5. 根据权利要求1所述的账户注册处理方法，还包括：所述在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数步骤执行之后，且所述若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果步骤执行之前，还包括：
    基于所述展示配置参数，渲染包含所述注册信息以及身份信息中的身份标识的所述注册确认页；
    将所述注册确认页通过所述第二终端进行展示；
    其中，所述身份信息为基于所述第一终端的账户信息读取的与所述账户信息具有关联关系的身份信息。
  6. 根据权利要求1所述的账户注册处理方法，所述基于所述注册信息进行账户注册，包括：
    基于账户标识生成算法生成账户标识；
    建立所述账户标识与所述注册信息以及所述联系方式的关联关系；
    将所述账户标识通过所述第二终端向所述目标用户发送。
  7. 根据权利要求1所述的账户注册处理方法，还包括：
    基于所述邀请单的邀请单标识，向所述第一终端发送对所述邀请单的查看提醒；
    在所述查看提醒被触发后，查询所述邀请单中记录的邀请状态并向所述第一终端发送。
  8. 根据权利要求1所述的账户注册处理方法，所述第一终端在提交所述注册信息之前，执行如下步骤：
    采集所述信息采集页录入的所述注册信息；
    校验所述注册信息的格式是否符合格式条件；
    若是，在检测到所述信息采集页配置的确认控件被触发时提交所述注册信息；
    若否，展示格式提醒，以提醒所述第一终端所属的发起用户重新录入所述注册信息。
  9. 根据权利要求1所述的账户注册处理方法，所述向所述第一终端发送注册结果，包括：
    根据所述注册结果更新所述邀请单中的邀请状态；
    基于所述邀请状态向所述第一终端发送所述注册结果；
    其中，若所述注册结果为注册成功，则将所述注册成功的注册结果更新至所述邀请单；若所述注册结果为注册失败，则读取注册失败原因，并将所述注册失败原因与所述注册失败的注册结果更新至所述邀请单。
  10. 一种账户注册处理方法，应用于第一终端，包括：
    通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页；
    通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交；
    接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
  11. 根据权利要求10所述的账户注册处理方法，还包括：
    接收所述服务器发送的携带邀请单标识的邀请单提醒；
    在所述邀请单提醒被触发后，获取所述邀请单中记录的邀请状态。
  12. 根据权利要求10所述的账户注册处理方法，所述通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交，包括：
    采集所述信息采集页录入的所述注册信息；
    核验所述注册信息的格式是否符合格式条件；
    若是，在检测到所述信息采集页配置的确认控件被触发时上传所述注册信息；
    若否，展示格式提醒。
  13. 一种账户注册处理方法，应用于第二终端，包括：
    接收服务器发送的邀请链接；
    在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页；
    在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
  14. 根据权利要求13所述的账户注册处理方法，所述展示配置信息，采用如下方式获得：
    根据所述邀请链接中携带的邀请单标识读取所述邀请单的记录内容；
    解析所述记录内容中所述目标用户的身份证件标识，获得所述目标用户的关键特征信息；
    将所述关键特征信息输入参数配置算法进行参数配置，获得所述展示配置参数。
  15. 根据权利要求13所述的账户注册处理方法，所述注册确认页，通过如下方式生成：
    基于所述展示配置参数，渲染包含所述注册信息以及身份信息中的身份标识的所述注册确认页并展示；
    其中，所述身份信息为提交所述注册信息的发起用户的身份信息。
  16. 根据权利要求13所述的账户注册处理方法，还包括：
    若所述服务器在接收所述注册确认指令后，基于所述注册信息进行账户注册的注册结果为注册成功，则接收所述服务器发送的账户标识并展示。
  17. 一种账户注册处理装置，运行于服务器，包括：
    联系方式接收模块，被配置为接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页；
    邀请单生成模块，被配置为根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接；
    参数确定模块，被配置为在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数；
    账户注册模块，被配置为若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
  18. 一种账户注册处理装置，运行于第一终端，包括：
    联系方式提交模块，被配置为通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页；
    注册信息提交模块，被配置为通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交；
    注册结果接收模块，被配置为接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
  19. 一种账户注册处理装置，运行于第二终端，包括：
    接收模块，被配置为接收服务器发送的邀请链接；
    展示模块，被配置为在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页；
    提交模块，被配置为在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
  20. 一种账户注册处理设备，运行于服务器，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页；
    根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接；
    在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数；
    若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
  21. 一种账户注册处理设备，运行于第一终端，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页；
    通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交；
    接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
  22. 一种账户注册处理设备，运行于第二终端，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    接收服务器发送的邀请链接；
    在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页；
    在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
  23. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    接收第一终端提交的目标用户的联系方式，向所述第一终端返回信息采集页；
    根据所述第一终端提交的基于所述信息采集页录入的注册信息生成邀请单，并基于所述联系方式向第二终端发送基于所述邀请单生成的邀请链接；
    在所述邀请链接被触发后根据所述注册信息确定所述目标用户的展示配置参数；
    若接收到所述第二终端基于所述展示配置参数进行信息展示后提交的注册确认指令，基于所述注册信息进行账户注册，并向所述第一终端发送注册结果。
  24. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    通过初始页面向服务器提交目标用户的联系方式，并接收所述服务器返回的信息采集页；
    通过所述信息采集页录入所述目标用户的注册信息并向所述服务器提交；
    接收所述服务器基于所述注册信息进行注册处理后返回的注册结果。
  25. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    接收服务器发送的邀请链接；
    在所述邀请链接被触发后，展示基于展示配置信息以及发起用户提交的目标用户的注册信息生成的注册确认页；
    在所述注册确认页配置的注册确认控件被触发后向所述服务器提交注册确认指令。
PCT/CN2022/091543 2021-05-21 2022-05-07 账户注册处理的方法及装置 WO2022242478A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110556719.3 2021-05-21
CN202110556719.3A CN113221080A (zh) 2021-05-21 2021-05-21 账户注册处理方法及装置

Publications (1)

Publication Number Publication Date
WO2022242478A1 true WO2022242478A1 (zh) 2022-11-24

Family

ID=77093705

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091543 WO2022242478A1 (zh) 2021-05-21 2022-05-07 账户注册处理的方法及装置

Country Status (2)

Country Link
CN (1) CN113221080A (zh)
WO (1) WO2022242478A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113221080A (zh) * 2021-05-21 2021-08-06 支付宝(杭州)信息技术有限公司 账户注册处理方法及装置

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8023927B1 (en) * 2006-06-29 2011-09-20 Google Inc. Abuse-resistant method of registering user accounts with an online service
CN103139192A (zh) * 2011-11-24 2013-06-05 北京千橡网景科技发展有限公司 推荐注册方法和***
US9043870B1 (en) * 2011-12-16 2015-05-26 Google Inc. Automated sign up based on existing online identity
CN105760435A (zh) * 2016-02-02 2016-07-13 浙江慧脑信息科技有限公司 一种通过短信推荐快速注册的方法
CN110807710A (zh) * 2019-09-26 2020-02-18 北京淇瑀信息科技有限公司 一种用户邀请好友的邀请数据管理方法和***
CN112738105A (zh) * 2017-04-14 2021-04-30 创新先进技术有限公司 邀请注册方法及装置
CN113221080A (zh) * 2021-05-21 2021-08-06 支付宝(杭州)信息技术有限公司 账户注册处理方法及装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8023927B1 (en) * 2006-06-29 2011-09-20 Google Inc. Abuse-resistant method of registering user accounts with an online service
CN103139192A (zh) * 2011-11-24 2013-06-05 北京千橡网景科技发展有限公司 推荐注册方法和***
US9043870B1 (en) * 2011-12-16 2015-05-26 Google Inc. Automated sign up based on existing online identity
CN105760435A (zh) * 2016-02-02 2016-07-13 浙江慧脑信息科技有限公司 一种通过短信推荐快速注册的方法
CN112738105A (zh) * 2017-04-14 2021-04-30 创新先进技术有限公司 邀请注册方法及装置
CN110807710A (zh) * 2019-09-26 2020-02-18 北京淇瑀信息科技有限公司 一种用户邀请好友的邀请数据管理方法和***
CN113221080A (zh) * 2021-05-21 2021-08-06 支付宝(杭州)信息技术有限公司 账户注册处理方法及装置

Also Published As

Publication number Publication date
CN113221080A (zh) 2021-08-06

Similar Documents

Publication Publication Date Title
US11303590B2 (en) Suggested responses based on message stickers
CN109831456B (zh) 消息推送方法、装置、设备及存储介质
KR102111194B1 (ko) 통신 세션에서의 가상 어시스턴트
WO2019223390A1 (zh) 一种授权引导的数据处理方法、装置、处理设备及***
US20190303088A1 (en) Transferring an application interface from one device to another device
JP6707270B2 (ja) サービス処理方法および装置
EP2869252A1 (en) Method and device for displaying information
US11449682B2 (en) Adjusting chatbot conversation to user personality and mood
US11556698B2 (en) Augmenting textual explanations with complete discourse trees
TW201909012A (zh) 資訊驗證處理方法、裝置、系統、客戶端及伺服器
KR20170100175A (ko) 전자 장치 및 전자 장치의 동작 방법
US10699104B2 (en) Image obtaining based on emotional status
US9313284B2 (en) Smart posting with data analytics and semantic analysis to improve a message posted to a social media service
CN107016055B (zh) 用于挖掘实体别名的方法、设备及电子设备
WO2023000952A1 (zh) 基于邮箱的票据处理
WO2022242478A1 (zh) 账户注册处理的方法及装置
CN115867905A (zh) 旅行情况下基于增强现实的语音翻译
CN108449255B (zh) 评论交互方法、设备、客户端装置及电子设备
US20240045899A1 (en) Icon based tagging
US20180255173A1 (en) Information pushing method and apparatus, and terminal and server
CN106549860B (zh) 信息获取方法和装置
US10387566B2 (en) Assisting with written communication style based on recipient dress style
WO2023000954A1 (zh) 票据处理
US20160154948A1 (en) Managing companionship data
CN111367898B (zh) 数据处理方法、装置、***、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22803802

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22803802

Country of ref document: EP

Kind code of ref document: A1