WO2019210570A1 - 应用软件的账号注册方法、装置、设备及可读存储介质 - Google Patents

应用软件的账号注册方法、装置、设备及可读存储介质 Download PDF

Info

Publication number
WO2019210570A1
WO2019210570A1 PCT/CN2018/094107 CN2018094107W WO2019210570A1 WO 2019210570 A1 WO2019210570 A1 WO 2019210570A1 CN 2018094107 W CN2018094107 W CN 2018094107W WO 2019210570 A1 WO2019210570 A1 WO 2019210570A1
Authority
WO
WIPO (PCT)
Prior art keywords
registration
user
information
application software
identity information
Prior art date
Application number
PCT/CN2018/094107
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 WO2019210570A1 publication Critical patent/WO2019210570A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/108—Network architectures or network communication protocols for network security for controlling access to devices or network resources when the policy decisions are valid for a limited amount of time

Definitions

  • the main purpose of the application is to provide an application account registration method, device, device and readable storage medium, which aims to solve the problem that the registration of the application software in the prior art is performed by the user without authentication, and the application software is added. The risk of accessing users and the cost of user time.
  • the application provides an account registration method for an application software, and the account registration method of the application software includes the following steps:
  • the application further provides an account registration device of the application software, where the account registration device of the application software includes:
  • the determining module is configured to: when receiving the registration request initiated by the preset system interface, determine whether the user identity information corresponding to the registration request successfully passes the wind control check;
  • the registration module is configured to receive the user registration information input by the manual agent through the registration interface, and register the account of the application software.
  • the present application further provides an account registration device of an application software, where the account registration device of the application software includes: a memory, a processor, a communication bus, and an account registration of an application software stored on the memory. program;
  • the processor is configured to execute an account registration procedure of the application software to implement the following steps:
  • the present application also provides a readable storage medium storing one or more programs, the one or more programs being executable by one or more processors Used for:
  • FIG. 1 is a schematic flowchart of a first embodiment of an account registration method of an application software of the present application
  • FIG. 2 is a schematic diagram of functional modules of a first embodiment of an account registration device of an application software of the present application
  • FIG. 3 is a schematic structural diagram of a device in a hardware operating environment involved in a method according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of an application scenario of an account registration method of an application software of the present application
  • FIG. 5 is a schematic diagram of a registration process of an account registration method of an application software of the present application.
  • the application provides an account registration method of an application software.
  • FIG. 1 is a schematic flowchart diagram of a first embodiment of an account registration method of an application software according to the present application.
  • the account registration method of the application software includes:
  • Step S10 When receiving the registration request initiated by the preset system interface, determining whether the user identity information corresponding to the registration request successfully passes the wind control check;
  • the account registration method of the application software of the present application is applied to the registration server.
  • the registration server is respectively connected with the preset system and each user terminal having the registered application software requirement.
  • the user terminal is held by the user, and the preset system is provided by the registrar, and the artificial seat of the registrar can operate the preset system interface.
  • the manual agent is notified by means of telephone, short message or WeChat, and the manual agent queries the user identity information and the user registration information, and inputs the obtained user identity information and user registration information into the pre-preparation.
  • the corresponding input box of the system interface is transmitted to the registration server by the preset system, and when the user identity information is successfully verified by the wind control, the application software is registered by the registration server.
  • a registration trigger button of a plurality of different application softwares is set on the preset system interface, and the user informs the manual agent of the application software that needs to be registered, and the registration trigger button of the application software needs to be registered by the manual agent.
  • a trigger is triggered, and the request triggered by this trigger operation is a registration request.
  • the registration server When the registration server receives the registration request initiated by the manual agent through the preset system interface, it is determined whether the user identity information corresponding to the registration request successfully passes the wind control check.
  • the user identity information corresponding to the registration request is identity information possessed by the user who has the registered application requirement, and the identity information can represent the uniqueness of the user, such as the identity card number.
  • the wind control check is a process of verifying the user identity information by calling the preset air control system interface; the default wind control system is provided with a blacklist representing the risk user, and the ID number of each risk user in the blacklist is set.
  • Control verification assigning a verification failure identifier to the user identity information; and if the identity card number representing the user identity information does not exist in the blacklist, the user having the identity information of the user is a security user, and the identity information of the user is A verification success identifier is assigned to this user identity information through a risk check. Therefore, the user identity information is successfully passed through the risk check by using the type of the verification identifier carried in the user identity information.
  • the step of determining whether the user identity information corresponding to the registration request successfully passes the wind control verification includes:
  • Step S11 when receiving the registration request initiated by the preset system interface, outputting prompt information to prompt for inputting the user identity information;
  • the user when receiving the registration request initiated by the artificial agent on the preset system interface, the user jumps to the user identity information input interface, and displays a prompt message on the user identity information input interface to prompt for the user identity. information.
  • the user identity information input interface is provided with an input box and a virtual button for triggering the acquisition of the verification result, so as to obtain the verification result of the entered user identity information wind control check.
  • Step S12 Receive user identity information input based on the prompt information, and determine, according to the verification identifier carried in the user identity information, whether the user identity information successfully passes the wind control check.
  • the registration server After receiving the user identity information input by the prompt information, the registration server reads the verification identifier carried in the user identity information, and determines the type of the verification identifier, that is, the verification verification identifier is a verification success identifier. Still verify the failure identifier.
  • the verification identifier carries a field characterizing its type.
  • the user field "y" represents the verification success identifier
  • the "n" is used to represent the verification failure identifier; determining the type of the field carried by the user identifier determines the verification identifier. The type, and then based on this verification identifier, determines whether the user identity information successfully passed the wind control check.
  • Step S20 if the user identity information successfully passes the wind control check, determining the registered application software type according to the identifier in the registration request, and outputting a registration interface corresponding to the application software type to the preset system interface;
  • the verification identifier when it is determined by the verification identifier that the user identity information successfully passes the wind control check, that is, the verification identifier is the verification success identifier, it jumps to the registration interface of the registered application software.
  • the registration interface of different application software is preset in the registration server, and the registration corresponding to the application software required by the user needs to be determined. interface.
  • the registration trigger button of the plurality of different application softwares set on the preset system interface carries an identifier that represents different application software, such as the identifier triggering button carried in the registration trigger button for triggering the application software A. The identifier is sent to the registration server along with the registration request for the registration trigger button.
  • the identifier carried in the registration request is read, and the type of the registered application software is determined by the identifier, and then the registration interface corresponding to the application software type is invoked.
  • the registration interface is output to the preset system interface display to register the application software.
  • Step S30 Receive user registration information input by the manual agent through the registration interface, and register an account of the application software.
  • the registration interface of each application software includes a plurality of input boxes for inputting user registration information and a virtual button for triggering registration, and outputting a registration interface of the application software registered by the user to the display of the preset system.
  • the interface after the display interface is displayed, the manual agent inputs the basic information of the user notified by the user as the user registration information into the input box corresponding to the registration interface.
  • the user basic information includes but is not limited to the user name, user age, user gender, phone number, bank card number, account name, login password, etc., and the human agent inputs such user basic information as registration information into the corresponding input box. Enter the user name into the input interface of the registration interface where you need to enter the user's name.
  • the registration server registers the account of the application software according to the received user registration information, and assigns the account authority of the application software to the user registration information.
  • the account registration method of the application software of the embodiment when receiving the registration request initiated by the preset system interface, first determines whether the user identity information corresponding to the registration request successfully passes the wind control check; if the user identity information successfully passes The wind control check determines the registered application software type according to the identifier in the registration request, and outputs a registration interface corresponding to the application software type to the preset system interface; thereafter, the user registration information input by the manual agent through the registration interface is received, Register the account of the application software.
  • the solution only registers the account of the application software corresponding to the registration request of the user identity information successfully passed the wind control verification to ensure the security of the user accessed by the application software; and the manual agent passes the preset according to the user registration information provided by the user.
  • the registration interface in the system is registered to avoid user operation, which simplifies user operations and saves user time.
  • the step of registering the account of the application software includes:
  • Step S31 Obtain a registration requirement corresponding to the type of the registration application software, and compare the user registration information with the registration requirement to determine whether the user registration information satisfies the registration requirement.
  • the registration requirement of the registered application software type that is, the registration requirement corresponding to the type of the application software that the user needs to register
  • the registration requirement is related to the application software type, and the corresponding mapping relationship may be established for the two according to the registered application software.
  • Type to determine its corresponding registration requirement.
  • the entered user registration information is compared with the corresponding registration requirements to determine whether the user registration information satisfies the registration requirement.
  • the step of comparing the user registration information with the registration requirement and determining whether the user registration information meets the registration requirement includes:
  • Step S311 reading each field value in the user registration information, and each field value in the registration request corresponding to each field value in the registration information;
  • the user registration information entered into the registration interface is used to characterize different types of information that the user has, such as information characterizing the user's name, information characterizing the age, and information characterizing the bank card number.
  • This plurality of types of information is distinguished by field names, such as the user name being represented by the field name "m1" and the age being represented by the field name "m2".
  • the corresponding field name is used to represent the registration requirements of the same type of information, such as the registration requirement for age, which is characterized by the field name "m2".
  • the field names corresponding to different users have different field values. For example, the field value corresponding to the field name m2 of the user A has 29, and the field value corresponding to the field name m2 of the user A has 45.
  • the essence is to compare the field value information of the user with the field value required by the field value information in the registration request, and determine whether the field value information in the user registration information is satisfied.
  • the field value requirement corresponding to this field value information in the registration request Specifically, each field value in the user registration information and a field value corresponding to the field value in the user registration information in the registration request are read. For example, the user age 30 in the user registration information is read, and the field value 20 ⁇ 30 indicating the user's age requirement in the registration request.
  • the field value corresponding to the consistent field name is the self-segment value corresponding to each field value in the user registration information in the registration request, wherein each field value in the registration request is a requirement for each field value in the user registration information.
  • Step S312 comparing each field value in the associated user registration information with each field value in the registration request to determine whether the user registration information satisfies the registration requirement.
  • each field value in the user registration information After reading each field value in the user registration information and each field value corresponding to the registration request, comparing each field value in the user registration information with each field value in the registration request, determining the user registration Whether the information satisfies the target registration requirement, and the comparison is performed according to the correspondence between the two, such as the comparison between the age field values.
  • the field value used in the registration request to determine whether it satisfies the registration requirement may include a set of multiple options, or may be a single option; if multiple options are based on multiple options The logical relationship between the two is judged whether multiple options need to be satisfied at the same time or need to satisfy any one of them; for simultaneous satisfaction, it is determined whether the field value in the user registration information meets multiple option requirements of the field value in the target registration requirement; If any one is satisfied, it is determined whether the field value in the user registration information satisfies any requirement of the field value in the target registration requirement; if it is a single option, it directly determines whether the field value in the user registration information satisfies the field value requirement in the target registration request.
  • the field value of the field in the user registration information is m3
  • the field value corresponding to m3 in the registration request is M
  • M lists a plurality of supported banks, that is, multiple banks supported by the registered application software. Comparing m3 and M, judging whether m3 exists in M, comparing the input bank with a plurality of banks supported by the registration application, and judging whether the input bank is one of the supported banks.
  • Step S32 If the user registration information meets the registration requirement, register the application software, and send a prompt message for successful registration to the user terminal corresponding to the user registration information after the registration is completed, to prompt the The user terminal downloads and logs in the registered application software;
  • the application software is registered, and after the registration is completed, the user terminal corresponding to the user registration information is sent the prompt information for successful registration.
  • the user terminal corresponding to the user registration information may be determined by establishing communication with the operator of the mobile phone number in the user registration information. After the registration is completed, the user mobile phone number in the user registration information is read, and the operation of the mobile phone number of the user is determined. Business.
  • the request information is sent to the operator to request the operator to send the prompt information to the user's mobile phone number, and send the prompt information to the user terminal corresponding to the user registration information.
  • the prompt information includes downloading the website link of the registered application software, the registered account number and the password, so that the user terminal downloads the registered application software through the website link, and performs the login operation on the application software by using the account number and the password.
  • Step S33 If the user registration information does not meet the registration requirement, stop the registration of the application software, and send a prompt message of the registration failure to the user terminal corresponding to the user registration information, and the registration failure prompt
  • the information includes user registration information that does not meet the registration requirements.
  • the prompt information includes user registration information that does not meet the registration requirement, such as the bank that is entered does not meet the requirement, or the user does not meet the age requirement.
  • This user registration information that does not meet the registration requirements is the cause of the application registration failure, and is used as part of the prompt information to facilitate the user to know the reason for the registration failure.
  • the registration information can be modified, such as the bank does not meet the requirements; while others can not be modified, such as the user's age; for the registration failure caused by the user registration information that can be modified, provide modification
  • the option is used as part of the registration failure prompt to quickly modify the user registration information based on the registration failure prompt.
  • the step of sending the prompt information of the registration failure to the user terminal corresponding to the user registration information includes:
  • Step S34 Receive modification information input based on the registration failure prompt information, and replace the user registration information that does not satisfy the registration requirement with the modification information to form new user registration information, and execute the user registration information and the registration. A comparison is required to determine whether the user registration information satisfies the registration requirement.
  • the registration failure information includes the reason for the registration failure, that is, the user registration information that does not satisfy the registration requirement, and the range that can be modified by the user registration information and the user registration information that can be modified. If the registration fails due to the bank's unsatisfied requirements, the registration failure prompt message includes at least: the reason why the registration failure is that the entered bank is not within the range of the supportable bank, and what are the supportable banks that represent the scope of the modification, so that Prompt the user to change the entered bank to a supported bank. The user informs the human agent of the supportable bank that he has, and the artificial agent makes modifications to the entered bank.
  • the registration server receives the modification information input based on the registration failure prompt information, and replaces the user registration information that does not satisfy the registration requirement with the modification information to form a new user registration information. If the bank that does not meet the requirements is modified as a supported bank as described above, the new user registration information is compared with the corresponding registration request to determine whether the user registration information satisfies the registration requirement. That is, the field value of the newly modified user registration information is read, and it is determined whether the newly modified user registration information satisfies the corresponding registration requirement, and the user registration information is quickly modified according to the registration failure prompt information, and the maximum extent is Make sure that the account for the application is successfully registered.
  • the step of determining whether the user identity information successfully passes the wind control verification according to the verification identifier carried in the user identity information includes:
  • the verification identifier carried in the user identity information is a verification failure identifier, determining that the user identity information has not successfully passed the wind control check;
  • the blacklist representing the risk user in the preset risk control system may change with time, such as monitoring the user's risk behavior in the recent time period as a member of the blacklist, with the subsequent longer time Monitoring, this user no longer has risky behavior, then remove it from the blacklist.
  • the verification of the user identity information is time-sensitive due to the change of the blacklist.
  • the user identity information is consistent with the identity information of a member in the blacklist for a period of time, and the user identity information is not successfully passed the wind control check; Because the member is removed from the blacklist, the user identity information is no longer consistent with the identity information of a member of the blacklist, and the user identity information is successfully verified by the wind control.
  • the preset time is set, and the preset time is used as the monitoring time of the wind control verification result of the user identity information; in the process of verifying the user identity information, when the user identity information is read,
  • the type of the verification identifier is a verification failure identifier, and when the user identity information is not successfully passed the risk check, the verification result that may not be successfully passed the wind control check may be generated within the preset time, and the user identity information is generated.
  • the verification result cannot be changed; if the preset time is exceeded, the user identity information is re-evaluated by the wind control to re-determine whether the user identity information has the right to register the application software account. Therefore, the account registration method of the application software in this embodiment further includes the following steps:
  • step S20-1 if the user identity information fails to pass the wind control check, the verification time of the last risk check is read, and it is determined whether the time period from the check time to the current time is greater than a preset. time;
  • the verification time of the last risk check is read, and the verification time is that the user identity information is not successfully passed the wind control check.
  • Check result time point The time period from the verification time to the current time reflects the length of the generated verification result, compares the time period reflecting the length of time with the preset time, and determines whether the time period is greater than the preset time to determine whether the user identity is required. The information is re-tested for wind control.
  • Step S20-2 if the time period is greater than the preset time, calling the preset air control system interface to perform the wind control verification on the user identity information;
  • the generated user identity information does not successfully pass the verification result of the wind control check exceeds the monitoring time, that is, the generated verification result is no longer monitored, but needs to be User identity information is re-tested for wind control.
  • the preset air control system interface is invoked, and the user identity information is re-tested by the blacklist in the preset wind control system to re-determine whether the user identity information has the right to register the application software account.
  • Step S20-3 if the time period is less than or equal to the preset time, it is determined that the user identity information does not have the qualification of the registered application software account.
  • the generated user identity information fails to pass the verification result of the wind control check and the time does not exceed the monitoring time, and the generated verification result needs to be monitored to maintain the user identity.
  • the verification result of the information cannot be changed, and the user identity information still does not have the right to register the application software account to ensure the security of the user accessed by the application software.
  • the step of determining whether the user identity information successfully passes the wind control verification according to the verification identifier carried in the user identity information includes:
  • Step S13 if the verification identifier carried in the user identity information is a null value, determining that the user identity information has not been subjected to the wind control verification, and calling the preset air control system interface to start the wind on the user identity information.
  • the verification identifier is assigned; for the user identity information that has not been subjected to the wind control check, the verification identifier is not carried, and any parameter value cannot be read when the verification identifier carried in the user identity information is read, ie The content read is null. Therefore, before determining whether the user identity information successfully passes the wind control check, the verification identifier carried in the user identity information needs to be read, and it is determined whether the verification identifier is a null value.
  • the verification identifier carried in the user identity information is a null value
  • the preset air control system interface is invoked, and the user identity is determined by the blacklist in the preset risk control system.
  • the information initiates a wind control check to determine if the user identity information has permission to register an application account.
  • Step S14 if the wind control verification of the user identity information is successful, assigning a verification success identifier to the user identity information;
  • the preset wind control system interface is used to initiate the wind control verification on the user identity information, and it is determined that the user identity information does not exist in the blacklist in the preset risk control system, the wind control verification of the user identity information is performed. Successfully, the verification success identifier is assigned to the user identity information, and the user identity information has the authority to register the application software account, and the account of the application software can be registered by the manual agent.
  • Step S15 If the wind control verification of the user identity information fails, assigning a verification failure identifier to the user identity information.
  • the preset risk control system interface When the preset risk control system interface is used to initiate the wind control verification on the user identity information, and the user identity information is determined to exist in the blacklist in the preset risk control system, the wind control verification of the user identity information fails, and the user fails.
  • the user corresponding to the identity information may be a risk user; a verification failure identifier is assigned to the user identity information, and the user identity information does not have the authority to register the application software account, so as to avoid connecting the risk user to the application software.
  • the application provides an account registration device of an application software.
  • the account registration device of the application software includes:
  • the determining module 10 is configured to: when receiving the registration request initiated by the preset system interface, determine whether the user identity information corresponding to the registration request successfully passes the wind control check;
  • the determining module 20 is configured to: if the user identity information successfully passes the wind control check, determine the registered application software type according to the identifier in the registration request, and output a registration interface corresponding to the application software type to the Preset system interface;
  • the registration module 30 is configured to receive user registration information input by the manual agent through the registration interface, and register the account of the application software.
  • the determining module 10 when receiving the registration request initiated by the preset system interface, the determining module 10 first determines whether the user identity information corresponding to the registration request successfully passes the wind control check; if the user identity The information successfully passes the wind control check, and the determining module 20 determines the registered application software type according to the identifier in the registration request, and outputs a registration interface corresponding to the application software type to the preset system interface; thereafter, the registration module 30 receives the manual agent again. Register the account of the application software through the user registration information entered through the registration interface.
  • the solution only registers the account of the application software corresponding to the registration request of the user identity information successfully passed the wind control verification to ensure the security of the user accessed by the application software; and the manual agent passes the preset according to the user registration information provided by the user.
  • the registration interface in the system is registered to avoid user operation, which simplifies user operations and saves user time.
  • the registration module includes:
  • an obtaining unit configured to acquire a registration request corresponding to the type of the registration application, and compare the user registration information with the registration requirement to determine whether the user registration information meets the registration requirement;
  • a registration unit configured to: if the user registration information meets the registration requirement, register the application software, and send a prompt message to the user terminal corresponding to the user registration information after the registration is completed, to prompt The user terminal downloads and logs in the registered application software;
  • a prompting unit configured to stop the registration of the application software if the user registration information does not meet the registration requirement, and send the prompt information of the registration failure to the user terminal corresponding to the user registration information, where the registration fails.
  • the prompt information includes user registration information that does not meet the registration requirements.
  • the obtaining unit includes:
  • a reading subunit configured to read each field value in the user registration information, and each field value in the registration request corresponding to each field value in the user registration information;
  • the comparison subunit is configured to compare each field value in the user registration information with each field value in the registration requirement to determine whether the user registration information satisfies the registration requirement.
  • the registration module further includes:
  • a receiving unit configured to receive modification information input based on the registration failure prompt information, and replace the user registration information that does not satisfy the registration requirement with the modification information to form new user registration information, and execute the user registration information and the location
  • the registration request is compared to determine whether the user registration information satisfies the registration requirement.
  • the determining module includes:
  • An output unit configured to output a prompt message when prompted to input a registration request initiated by the preset system interface, to prompt to input user identity information
  • a determining unit configured to receive user identity information input based on the prompt information, and determine, according to the verification identifier carried in the user identity information, whether the user identity information successfully passes the wind control check.
  • the determining unit includes:
  • a determining subunit configured to determine that the user identity information has not successfully passed the wind control check if the verification identifier carried in the user identity information is a verification failure identifier
  • the device also includes:
  • a reading module configured to: if the user identity information fails to pass the wind control check, read the verification time of the last risk check, and determine whether the time period from the check time to the current time is greater than a pre- Set time
  • the determining module is configured to determine that the user identity information does not have the qualification of registering the application software account if the time period is less than or equal to the preset time.
  • the determining module is further configured to:
  • the verification identifier carried in the user identity information is a null value, determining that the user identity information has not been subjected to the wind control verification, and calling the preset air control system interface to initiate the wind control verification on the user identity information ;
  • a verification failure identifier is assigned to the user identity information.
  • the virtual function module of the account registration device of the application software is stored in the memory 1005 of the account registration device of the application software shown in FIG. 3, and when the processor 1001 executes the account registration program of the application software, the embodiment shown in FIG. 2 is implemented. The function of each module.
  • the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • FIG. 3 is a schematic structural diagram of a device in a hardware operating environment involved in a method according to an embodiment of the present application.
  • the account registration device of the application software of the embodiment of the present application may be a PC (personal computer) ), it can also be terminal devices such as smartphones, tablets, e-book readers, and portable computers.
  • the account registration device of the application software may include: a processor 1001, such as a CPU (Central) Processing Unit, central processing unit, memory 1005, communication bus 1002.
  • the communication bus 1002 is used to implement connection communication between the processor 1001 and the memory 1005.
  • the memory 1005 can be a high speed RAM (random Access memory, random access memory, or stable memory (non-volatile Memory), such as disk storage.
  • the memory 1005 can also optionally be a storage device independent of the aforementioned processor 1001.
  • the account registration device of the application software may further include a user interface, a network interface, a camera, and an RF (Radio).
  • RF Radio
  • the user interface may include a display, an input unit such as a keyboard, and the optional user interface may also include a standard wired interface, a wireless interface.
  • the network interface can optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).
  • the account registration device structure of the application software shown in FIG. 3 does not constitute a limitation on the account registration device of the application software, and may include more or less components than the illustration, or a combination of some Parts, or different parts.
  • the memory 1005 as a computer readable storage medium may include an operating system, a network communication module, and an account registration program of application software.
  • the operating system is a program that manages and controls the application software to register device hardware and software resources, and supports the application registration process of the application software and other software and/or programs.
  • the network communication module is used to implement communication between components within the memory 1005 and to communicate with other hardware and software in the account registration device of the application software.
  • the processor 1001 is configured to execute an account registration program of the application software stored in the memory 1005, and implement the steps in the embodiments of the account registration method of the application software.
  • the application provides a readable storage medium storing one or more programs, the one or more programs being further executable by one or more processors for implementing the application software described above
  • the account registration method is the steps in the various embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请公开一种应用软件的账号注册方法、装置、设备及可读存储介质，所述方法包括：当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。本方案仅对成功通过风控校验的用户身份信息对应注册请求进行应用软件的账号注册，确保应用软件所接入用户的安全性；且由人工坐席根据用户所提供的的用户注册信息进行注册，避免用户自行操作，节省了用户时间。

Description

应用软件的账号注册方法、装置、设备及可读存储介质
本申请要求于2018年05月02日提交中国专利局、申请号为201810412105.6、发明名称为“应用软件的账号注册方法、装置、设备及可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在申请中。
技术领域
本申请主要涉及应用软件技术领域，具体地说，涉及一种应用软件的账号注册方法、装置、设备及可读存储介质。
背景技术
目前市场上用户在使用应用软件时，通常都是先下载应用软件，再在应用软件上进行注册后登录使用；在注册过程中没有对用户身份校验的过程，对于某些安全性较高的金融***应用软件，可能将具有“洗黑钱”、“地下钱庄”等风险的用户接入，而引起金融***的风险；此外由用户自行注册，增加了用户的操作，尤其对于注册流程不熟悉的用户，需要花费较多时间操作；用户在经下载和注册操作后，若出现注册失败的情况，更是增加了用户的时间成本。
发明内容
本申请的主要目的是提供一种应用软件的账号注册方法、装置、设备及可读存储介质，旨在解决现有技术中应用软件的注册由用户不经过身份验证进行，而增加了应用软件所接入用户的风险以及用户时间成本的问题。
为实现上述目的，本申请提供一种应用软件的账号注册方法，所述应用软件的账号注册方法包括以下步骤：
当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
此外，为实现上述目的，本申请还提出一种应用软件的账号注册装置，所述应用软件的账号注册装置包括：
判断模块，用于当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
确定模块，用于若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
注册模块，用于接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
此外，为实现上述目的，本申请还提出一种应用软件的账号注册设备，所述应用软件的账号注册设备包括：存储器、处理器、通信总线以及存储在所述存储器上的应用软件的账号注册程序；
所述通信总线用于实现处理器和存储器之间的连接通信；
所述处理器用于执行所述应用软件的账号注册程序，以实现以下步骤：
当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
此外，为实现上述目的，本申请还提供一种可读存储介质，所述可读存储介质存储有一个或者一个以上程序，所述一个或者一个以上程序可被一个或者一个以上的处理器执行以用于：
当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
本实施例的应用软件的账号注册方法，当接收到预设***界面所发起的注册请求时，先判断与注册请求所对应的用户身份信息是否成功通过风控校验；如果用户身份信息成功通过风控校验，则根据注册请求中的标识符确定所注册应用软件类型，并输出与应用软件类型对应的注册界面到预设***界面；此后再接收人工坐席通过注册界面输入的用户注册信息，对应用软件的账号进行注册。本方案仅对成功通过风控校验的用户身份信息对应注册请求进行应用软件的账号注册，确保应用软件所接入用户的安全性；且由人工坐席根据用户所提供的用户注册信息通过预设***中注册界面进行注册，避免用户自行操作，简化了用户操作，节省了用户时间。
附图说明
图1是本申请的应用软件的账号注册方法第一实施例的流程示意图；
图2是本申请的应用软件的账号注册装置第一实施例的功能模块示意图；
图3是本申请实施例方法涉及的硬件运行环境的设备结构示意图；
图4是本申请的应用软件的账号注册方法应用场景示意图；
图5是本申请的应用软件的账号注册方法注册流程示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供一种应用软件的账号注册方法。
请参照图1，图1为本申请应用软件的账号注册方法第一实施例的流程示意图。在本实施例中，所述应用软件的账号注册方法包括：
步骤S10，当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
本申请的应用软件的账号注册方法应用于注册服务器，请参照图4，注册服务器分别与预设***、以及各个有注册应用软件需求的用户终端通信连接。用户终端为用户所持有，预设***为提供注册服务机构所拥有，注册服务机构的人工坐席可对预设***界面进行操作。当用户有对应用软件注册需求时，通过电话、短信或微信的方式告知人工坐席，人工坐席则问询用户身份信息和用户注册信息，并将所获知的用户身份信息和用户注册信息输入到预设***界面的对应输入框中，由预设***传输到注册服务器，在用户身份信息成功通过风控验证时，通过注册服务器对应用软件进行注册。具体地，请参照图5，预设***界面上设置有多个不同应用软件的注册触发按钮，用户告知人工坐席其所需要注册的应用软件，由人工坐席对此需要注册应用软件的注册触发按钮进行触发，此触发操作所触发的请求即为注册请求。
当注册服务器接收到此由人工坐席通过预设***界面所发起的注册请求时，判断与注册请求所对应的用户身份信息是否成功通过风控校验。与注册请求所对应的用户身份信息为有注册应用软件需求用户所具有的身份信息，此身份信息可表征用户唯一性，如身份证号码。风控校验为通过调用预设风控***接口，对用户身份信息进行校验的过程；预设风控***中设置有表征风险用户的黑名单，对黑名单中各风险用户的身份证号码进行查询，判断是否存在表征用户身份信息的身份证号码；如果黑名单中存在此表征用户身份信息的身份证号码，则说明具有此用户身份信息的用户为风险用户，此用户身份信息没有通过风控校验，对此用户身份信息分配校验失败标识符；而如果黑名单中不存在此表征用户身份信息的身份证号码，则说明具有此用户身份信息的用户为安全用户，此用户身份信息通过风险校验，对此用户身份信息分配校验成功标识符。从而通过用户身份信息中所携带的验证标识符类型即可确定用户身份信息是否成功通过风险校验，具体地，判断与注册请求所对应的用户身份信息是否成功通过风控校验的步骤包括：
步骤S11，当接收到预设***界面所发起的注册请求时，输出提示信息，以提示输入用户身份信息；
请进一步参照图5，当接收到由人工坐席在预设***界面所发起的注册请求时，跳转到用户身份信息输入界面，并在此用户身份信息输入界面显示提示信息，以提示输入用户身份信息。用户身份信息输入界面中设置有输入框以及触发获取校验结果的虚拟按钮，以便获取所输入的用户身份信息风控校验的校验结果。
步骤S12，接收基于所述提示信息输入的用户身份信息，并根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验。
在人工坐席查看到用户身份信息输入界面所显示的提示信息后，将用户告知的用户身份信息输入到用户身份信息输入界面中的输入框，并触发虚拟按键，将用户身份信息上传到注册服务器。注册服务器在接收到此基于提示信息所输入的用户身份信息后，读取用户身份信息中所携带的验证标识符，并判断此验证标识符的类型，即判断验证标识符为校验成功标识符还是校验失败标识符。验证标识符中携带有表征其类型的字段，如用户字段“y”表征校验成功标识符，而用“n”表征校验失败标识符；确定其所携带的字段类型即可确定验证标识符的类型，进而根据此验证标识符确定用户身份信息是否成功通过风控校验。
步骤S20，若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
进一步地，当通过验证标识符确定用户身份信息成功通过风控校验，即验证标识符为校验成功标识符时，跳转到所注册应用软件的注册界面。而考虑到不同类型的应用软件在注册时所需要的注册信息以及注册界面不一样，在注册服务器中预先设置有不同应用软件的注册界面，需要确定与用户所需求注册的应用软件所对应的注册界面。具体地，预设***界面上所设置的多个不同应用软件的注册触发按钮中携带有表征不同应用软件的标识符，如用于触发应用软件A的注册触发按钮中携带有标识符f1，此标识符随着注册触发按钮的注册请求一并发送到注册服务器。当用户身份信息成功通过风控校验时，则读取注册请求中所携带的标识符，通过此标识符确定所注册应用软件的类型，进而调用与此应用软件类型对应的注册界面，将此注册界面输出到预设***界面显示，以对应用软件进行账号注册。
步骤S30，接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
更进一步地，各应用软件的注册界面中包括用于输入用户注册信息的多个输入框以及触发注册的虚拟按键，在将用户需求注册的应用软件所具有的注册界面输出到预设***的显示界面，在显示界面显示后，人工坐席将用户告知的用户基本信息作为用户注册信息输入到注册界面所对应的输入框中。其中用户基本信息包括但不限于用户姓名、用户年龄、用户性别、电话号码、银行***、账号名、登录密码等，人工坐席将此类用户基本信息作为注册信息输入到对应的输入框中。即将用户姓名输入注册界面中需要输入用户姓名的输入框中，将电话号码输入注册界面中需要输入电话号码的输入框中。在注册界面中所需要填写的输入框中均填写信息后，点击触发虚拟按键，以将所填写的用户注册信息传输到注册服务器。由注册服务器根据所接收的用户注册信息，对应用软件的账户进行注册，为用户注册信息分配应用软件的账号权限。
本实施例的应用软件的账号注册方法，当接收到预设***界面所发起的注册请求时，先判断与注册请求所对应的用户身份信息是否成功通过风控校验；如果用户身份信息成功通过风控校验，则根据注册请求中的标识符确定所注册应用软件类型，并输出与应用软件类型对应的注册界面到预设***界面；此后再接收人工坐席通过注册界面输入的用户注册信息，对应用软件的账号进行注册。本方案仅对成功通过风控校验的用户身份信息对应注册请求进行应用软件的账号注册，确保应用软件所接入用户的安全性；且由人工坐席根据用户所提供的用户注册信息通过预设***中注册界面进行注册，避免用户自行操作，简化了用户操作，节省了用户时间。
进一步地，在本申请应用软件的账号注册方法另一实施例中，所述对所述应用软件的账号进行注册的步骤包括：
步骤S31，获取与所述注册应用软件类型对应的注册要求，并将所述用户注册信息和所述注册要求对比，以判断所述用户注册信息是否满足所述注册要求；
可理解地，不同类型的应用软件具有不同的注册要求，如要求账号名不能重复，密码不能全是数字、银行账户不能冻结等。获取所注册应用软件类型的注册要求，即与用户所需求注册的应用软件类型所对应的注册要求，注册要求与应用软件类型相关，可对两者建立对应的映射关系，以便根据所注册应用软件类型即可确定其对应的注册要求。此后将所输入的用户注册信息和对应的注册要求对比，判断用户注册信息是否满足注册要求。因所输入的用户注册信息包括多种，而应用软件中对各种用户注册信息的注册要求不一致，从而在对比时，将各种用户注册信息和其各自所对应的注册要求对比，判断各种用户注册信息是否均满足其各自对应的注册要求。其中将所述用户注册信息和注册要求对比，判断用户注册信息是否满足注册要求的步骤包括：
步骤S311，读取所述用户注册信息中的各字段值，以及与所述注册信息中的各字段值对应的所述注册要求中的各字段值；
进一步地，因输入到注册界面中的用户注册信息用于表征用户所具有的不同类型信息，如表征用户姓名的信息、表征年龄的信息、表征银行***的信息。此多种类型的信息用字段名进行区分，如用字段名“m1”表征用户姓名，用字段名“m2”表征年龄。在注册要求中用相应的字段名表征同一类型信息所具有的注册要求，如对于年龄的注册要求用字段名“m2”表征。不同的用户对应字段名具有不同的字段值，如用户A对应字段名m2所具有的字段值为29，而用户A对应字段名m2所具有的字段值为45。将用户注册信息和其对应的注册要求对比，其实质是将用户所具有的字段值信息和注册要求中此字段值信息所要求的字段值进行对比，判断用户注册信息中的字段值信息是否满足注册要求中与此字段值信息对应的字段值要求。具体地，读取用户注册信息中的各字段值，以及注册要求中与此用户注册信息中字段值对应的字段值。如读取到用户注册信息中的用户年龄30，以及注册要求中表征用户年龄要求的字段值20~30。读取时先确定用户注册信息中各字段值所属于的字段名，再将此字段名和注册要求中的各字段名对比，确定各注册要求的字段名中与字段值所属字段名一致的字段名。此一致的字段名所对应的字段值即为注册要求中与用户注册信息中的各字段值对应的自段值，其中注册要求中的各字段值是对用户注册信息中各字段值的要求。
步骤S312，将所属用户注册信息中的各字段值与所述注册要求中的各字段值进行对比，以判断所述用户注册信息是否满足所述注册要求。
更进一步地，在读取到用户注册信息中的各字段值和注册要求中对应的各字段值后，将此用户注册信息中的各字段值与注册要求中的各字段值对比，判断用户注册信息是否满足目标注册要求，其中对比按照两者之间的对应关系进行，如表征年龄字段值之间的对比。此外对于用户注册信息中某一具体字段值，注册要求中用于判断其是否满足注册要求的字段值可以包括多个选项的集合，也可以是单个选项；若是多个选项则根据多个选项之间的逻辑关系进行判断，即多个选项是需要同时满足还是需要满足任意一个；对于同时满足，则判断用户注册信息中的字段值是否同时满足目标注册要求中字段值的多个选项要求；对于满足任意一个，则判断用户注册信息中的字段值是否满足目标注册要求中字段值的任意一个要求；若是单个选项则直接判断用户注册信息中的字段值是否满足此目标注册要求中的字段值要求。如用户注册信息中字段名为银行的字段值为m3，注册要求中与m3对应的字段值为M，其中M中列举有所支持的多个银行，即注册应用软件所支持的多个银行。将m3和M对比，判断m3是否存在于M中，即将所输入的银行和注册应用软件所支持的多个银行对比，判断所输入的银行是否为所支持的多个银行之一。
步骤S32，若所述用户注册信息满足所述注册要求，对所述应用软件进行注册，并在注册完成后向所述用户注册信息所对应用户终端下发注册成功的提示信息，以提示所述用户终端对所述所注册应用软件进行下载并登录；
当用户注册信息和目标注册信息匹配，判断出用户注册信息满足注册要求时，则对应用软件进行注册，并在注册完成后向用户注册信息所对应用户终端下发注册成功的提示信息。其中与用户注册信息所对应用户终端可通过与用户注册信息中手机号码的运营商建立通信确定，在注册完成后，读取用户注册信息中的用户手机号码，并确定此用户手机号码所属的运营商。向此运营商发送请求信息，以请求运营商向用户手机号码发送提示信息，而将提示信息发送到与用户注册信息对应的用户终端。其中提示信息包括下载所注册应用软件的网址链接、注册的账号和密码，以便用户终端通过网址链接对所注册的应用软件进行下载，并通过账号和密码在应用软件上进行登录操作。
步骤S33，若所述用户注册信息不满足所述注册要求，停止对所述应用软件的注册，并向所述用户注册信息所对应用户终端下发注册失败的提示信息，所述注册失败的提示信息包括不满足注册要求的用户注册信息。
而当用户注册信息和目标注册信息不匹配，判断出用户注册信息不满足注册要求时，则停止应用软件的注册，并向用户注册信息所对应用户终端下发注册失败的提示信息。其中提示信息中包括不满足注册要求的用户注册信息，如所输入的银行不满足要求，或用户年龄不满足要求等。此不满足注册要求的用户注册信息为引起应用软件注册失败的原因，将其作为提示信息的一部分，便于用户知晓注册失败的原因。对于某些不满足注册要求的用户注册信息可进行修改，如银行不满足要求；而另一些则不可进行修改，如用户年龄；对于由可进行修改的用户注册信息所引起的注册失败，提供修改选项，并将其作为注册失败提示信息的一部分，以便根据注册失败提示信息对用户注册信息进行快速修改。具体地，向用户注册信息所对应用户终端下发注册失败的提示信息的步骤之后包括：
步骤S34，接收基于所述注册失败提示信息所输入的修改信息，并用所述修改信息替换不满足注册要求的用户注册信息以形成新的用户注册信息，执行将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求的步骤。
可理解地，因注册失败提示信息中包括引起注册失败的原因，即不满足注册要求的用户注册信息，以及可进行修改的用户注册信息和用户注册信息所能修改的范围。如由银行不满足要求而引起的注册失败，则注册失败提示信息至少包括：注册失败的原因为所输入银行不在可支持银行的范围内，以及表征所能修改范围的可支持银行有哪些，以便提示用户将所输入的银行修改为可支持的银行。用户将其所具有的可支持银行告知人工坐席，由人工坐席对所输入银行进行修改。注册服务器接收此基于注册失败提示信息所输入的修改信息，并用修改信息替换不满足注册要求的用户注册信息，形成新的用户注册信息。如上述将不满足要求的银行修改为支持的银行，用此新的用户注册信息和对应的注册要求对比，判断用户注册信息是否满足注册要求。即读取此新修改的用户注册信息的字段值，重新判断此新修改的用户注册信息是否满足其对应的注册要求，实现根据注册失败提示信息快速修改用户注册信息的同时，可在最大程度上确保对应用软件的账号注册成功。
进一步地，在本申请应用软件的账号注册方法另一实施例中，所述根据用户身份信息中所携带的验证标识符确定用户身份信息是否成功通过风控校验的步骤包括：
若所述用户身份信息中所携带的验证标识符为校验失败标识符，则判定所述用户身份信息没有成功通过风控校验；
可理解地，预设风控***中表征风险用户的黑名单会随着时间而变化，如在近期时段内监测到用户具有风险行为而将其作为黑名单中的成员，随着后续更长时间的监测，此用户不再有风险行为，则将其从黑名单中移出。因黑名单的变化而使用户身份信息的校验具有时效性，在一段时间内用户身份信息与黑名单中某一成员的身份信息一致，而使用户身份信息没有成功通过风控校验；后续因黑名单中将此成员移出，使用户身份信息不再与黑名单中某一成员的身份信息一致，用户身份信息成功通过风控校验。本实施例中设置预设时间，将此预设时间作为用户身份信息的风控校验结果的监控时间；在对用户身份信息进行校验过程中，当读取到用户身份信息中所携带的验证标识符的类型为校验失败标识符，判定用户身份信息没有成功通过风险校验时，可能所生成的没有成功通过风控校验的校验结果在此预设时间内，则用户身份信息的校验结果不能改变；而如果超出预设时间，则对用户身份信息重新进行风控校验，以重新确定用户身份信息是否具有注册应用软件账号的权限。从而本实施例的应用软件的账号注册方法还包括步骤：
步骤S20-1，若所述用户身份信息没有成功通过风控校验，则读取上一次进行风险校验的校验时间，并判断所述校验时间到当前时间的时间段是否大于预设时间；
具体地，当通过验证标识符确定用户身份信息没有成功通过风控校验时，读取上一次进行风险校验的校验时间，此校验时间即生成用户身份信息没有成功通过风控校验的校验结果时间点。此校验时间到当前时间的时间段反映所生成校验结果的时间长度，将此反映时间长度的时间段和预设时间比较，判断时间段是否大于预设时间，以确定是否需要对用户身份信息重新进行风控校验。
步骤S20-2，若所述时间段大于预设时间，则调用预设风控***接口对所述用户身份信息重新进行风控校验；
进一步地，当判断出时间段大于预设时间，所生成用户身份信息没有成功通过风控校验的校验结果时间超过监控时间，即不再对所生成的校验结果进行监控，而需要对用户身份信息重新进行风控校验。调用预设风控***接口，通过预设风控***中的黑名单对用户身份信息重新进行风控校验，以重新确定用户身份信息是否具有注册应用软件账号的权限。
步骤S20-3，若所述时间段小于或等于预设时间，则判定所述用户身份信息不具有注册应用软件账号的资质。
而当判断出时间段小于或等于预设时间，所生成用户身份信息没有成功通过风控校验的校验结果时间没有超过监控时间，仍然需要对所生成的校验结果进行监控，保持用户身份信息的校验结果不能改变，用户身份信息仍然不具有注册应用软件账号的权限，以确保应用软件所接入用户的安全性。
进一步地，在本申请应用软件的账号注册方法另一实施例中，所述根据用户身份信息中所携带的验证标识符确定用户身份信息是否成功通过风控校验的步骤之前包括：
步骤S13，若所述用户身份信息中所携带的验证标识符为空值，则判定所述用户身份信息尚未进行过风控校验，调用预设风控***接口对所述用户身份信息启动风控校验；
可理解地，在通过验证标识符确定用户身份信息是否成功通过风险校验之前，需要确保用户身份信息已经进行过风险校验；而只有对于进行过风险校验的用户身份信息，才会向其分配验证标识符；而对于尚未进行过风控校验的用户身份信息，则不携带有验证标识符，在读取用户身份信息中所携带的验证标识符时不能读取到任何参数值，即读取的内容为空值。从而在确定用户身份信息是否成功通过风控校验之前，需要读取用户身份信息中所携带的验证标识符，并判断此验证标识符是否为空值。当用户身份信息中所携带的验证标识符为空值，则判定用户身份信息尚未进行过风控校验，则调用预设风控***接口，通过预设风控***中的黑名单对用户身份信息启动风控校验，以确定用户身份信息是否具有注册应用软件账号的权限。
步骤S14，若所述用户身份信息的风控校验成功，向所述用户身份信息分配校验成功标识符；
进一步地，当调用预设风控***接口对用户身份信息启动风控校验，判断出用户身份信息不存在于预设风控***中的黑名单中，则说明用户身份信息的风控校验成功，向此用户身份信息分配校验成功标识符，表征用户身份信息具有注册应用软件账号的权限，可通过人工坐席对应用软件的账号进行注册。
步骤S15，若所述用户身份信息的风控校验失败，向所述用户身份信息分配校验失败标识符。
而当调用预设风控***接口对用户身份信息启动风控校验，判断出用户身份信息存在于预设风控***中的黑名单中，则说明用户身份信息的风控校验失败，用户身份信息对应的用户可能为风险用户；向此用户身份信息分配校验失败标识符，表征用户身份信息不具有注册应用软件账号的权限，以避免将风险用户接入应用软件。
此外，请参照图2，本申请提供一种应用软件的账号注册装置，在本申请应用软件的账号注册装置第一实施例中，所述应用软件的账号注册装置包括：
判断模块10，用于当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
确定模块20，用于若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
注册模块30，用于接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
本实施例的应用软件的账号注册装置，当接收到预设***界面所发起的注册请求时，判断模块10先判断与注册请求所对应的用户身份信息是否成功通过风控校验；如果用户身份信息成功通过风控校验，确定模块20则根据注册请求中的标识符确定所注册应用软件类型，并输出与应用软件类型对应的注册界面到预设***界面；此后注册模块30再接收人工坐席通过注册界面输入的用户注册信息，对应用软件的账号进行注册。本方案仅对成功通过风控校验的用户身份信息对应注册请求进行应用软件的账号注册，确保应用软件所接入用户的安全性；且由人工坐席根据用户所提供的用户注册信息通过预设***中注册界面进行注册，避免用户自行操作，简化了用户操作，节省了用户时间。
进一步地，在本申请应用软件的账号注册装置另一实施例中，所述注册模块包括：
获取单元，用于获取与所述注册应用软件类型对应的注册要求，并将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求；
注册单元，用于若所述用户注册信息满足所述注册要求，对所述应用软件进行注册，并在注册完成后向所述用户注册信息所对应用户终端下发注册成功的提示信息，以提示所述用户终端对所述所注册应用软件进行下载并登录；
提示单元，用于若所述用户注册信息不满足所述注册要求，停止对所述应用软件的注册，并向所述用户注册信息所对应用户终端下发注册失败的提示信息，所述注册失败的提示信息包括不满足注册要求的用户注册信息。
进一步地，在本申请应用软件的账号注册装置另一实施例中，所述获取单元包括：
读取子单元，用于读取所述用户注册信息中的各字段值，以及与所述用户注册信息中的各字段值对应的所述注册要求中的各字段值；
对比子单元，用于将所述用户注册信息中的各字段值与所述注册要求中的各字段值进行对比，以判断所述用户注册信息是否满足所述注册要求。
进一步地，在本申请应用软件的账号注册装置另一实施例中，所述注册模块还包括：
接收单元，用于接收基于所述注册失败提示信息所输入的修改信息，并用所述修改信息替换不满足注册要求的用户注册信息以形成新的用户注册信息，执行将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求的步骤。
进一步地，在本申请应用软件的账号注册装置另一实施例中，所述判断模块包括：
输出单元，用于当接收到预设***界面所发起的注册请求时，输出提示信息，以提示输入用户身份信息；
确定单元，用于接收基于所述提示信息输入的用户身份信息，并根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验。
进一步地，在本申请应用软件的账号注册装置另一实施例中，所述确定单元包括：
判定子单元，用于若所述用户身份信息中所携带的验证标识符为校验失败标识符，则判定所述用户身份信息没有成功通过风控校验；
所述装置还包括：
读取模块，用于若所述用户身份信息没有成功通过风控校验，则读取上一次进行风险校验的校验时间，并判断所述校验时间到当前时间的时间段是否大于预设时间；
调用模块，用于若所述时间段大于预设时间，则调用预设风控***接口对所述用户身份信息重新进行风控校验；
判定模块，用于若所述时间段小于或等于预设时间，则判定所述用户身份信息不具有注册应用软件账号的资质。
进一步地，在本申请应用软件的账号注册装置另一实施例中，所述判断模块还用于：
若所述用户身份信息中所携带的验证标识符为空值，则判定所述用户身份信息尚未进行过风控校验，调用预设风控***接口对所述用户身份信息启动风控校验；
若所述用户身份信息的风控校验成功，向所述用户身份信息分配校验成功标识符；
若所述用户身份信息的风控校验失败，向所述用户身份信息分配校验失败标识符。
其中，上述应用软件的账号注册装置的各虚拟功能模块存储于图3所示应用软件的账号注册设备的存储器1005中，处理器1001执行应用软件的账号注册程序时，实现图2所示实施例中各个模块的功能。
需要说明的是，本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
参照图3，图3是本申请实施例方法涉及的硬件运行环境的设备结构示意图。
本申请实施例应用软件的账号注册设备可以是PC( personal computer，个人计算机 )，也可以是智能手机、平板电脑、电子书阅读器、便携计算机等终端设备。
如图3所示，该应用软件的账号注册设备可以包括：处理器1001，例如CPU（Central Processing Unit，中央处理器），存储器1005，通信总线1002。其中，通信总线1002用于实现处理器1001和存储器1005之间的连接通信。存储器1005可以是高速RAM（random access memory，随机存取存储器），也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
可选地，该应用软件的账号注册设备还可以包括用户接口、网络接口、摄像头、RF（Radio Frequency，射频）电路，传感器、音频电路、WiFi（Wireless Fidelity，无线宽带）模块等等。用户接口可以包括显示屏（Display）、输入单元比如键盘（Keyboard），可选用户接口还可以包括标准的有线接口、无线接口。网络接口可选的可以包括标准的有线接口、无线接口（如WI-FI接口）。
本领域技术人员可以理解，图3中示出的应用软件的账号注册设备结构并不构成对应用软件的账号注册设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图3所示，作为一种计算机可读存储介质的存储器1005中可以包括操作***、网络通信模块以及应用软件的账号注册程序。操作***是管理和控制应用软件的账号注册设备硬件和软件资源的程序，支持应用软件的账号注册程序以及其它软件和/或程序的运行。网络通信模块用于实现存储器1005内部各组件之间的通信，以及与应用软件的账号注册设备中其它硬件和软件之间通信。
在图3所示的应用软件的账号注册设备中，处理器1001用于执行存储器1005中存储的应用软件的账号注册程序，实现上述应用软件的账号注册方法各实施例中的步骤。
本申请提供了一种可读存储介质，所述可读存储介质存储有一个或者一个以上程序，所述一个或者一个以上程序还可被一个或者一个以上的处理器执行以用于实现上述应用软件的账号注册方法各实施例中的步骤。
还需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在如上所述的一个可读存储介质（如ROM/RAM、磁碟、光盘）中，包括若干指令用以使得一台终端设备（可以是手机，计算机，服务器，或者网络设备等）执行本申请各个实施例所述的方法。
以上所述仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是在本申请的构思下，利用本申请说明书及附图内容所作的等效结构变换，或直接/间接运用在其他相关的技术领域均包括在本申请的专利保护范围内。

Claims (20)

  1. 一种应用软件的账号注册方法，其特征在于，所述应用软件的账号注册方法包括以下步骤：
    当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
    若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
    接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
  2. 如权利要求1所述的应用软件的账号注册方法，其特征在于，所述对所述应用软件的账号进行注册的步骤包括：
    获取与所述注册应用软件类型对应的注册要求，并将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求；
    若所述用户注册信息满足所述注册要求，对所述应用软件进行注册，并在注册完成后向所述用户注册信息所对应用户终端下发注册成功的提示信息，以提示所述用户终端对所述所注册应用软件进行下载并登录；
    若所述用户注册信息不满足所述注册要求，停止对所述应用软件的注册，并向所述用户注册信息所对应用户终端下发注册失败的提示信息，所述注册失败的提示信息包括不满足注册要求的用户注册信息。
  3. 如权利要求2所述的应用软件的账号注册方法，其特征在于，所述将所述用户注册信息和所述注册要求对比，以判断所述用户注册信息是否满足所述注册要求的步骤包括：
    读取所述用户注册信息中的各字段值，以及与所述用户注册信息中的各字段值对应的所述注册要求中的各字段值；
    将所述用户注册信息中的各字段值与所述注册要求中的各字段值进行对比，以判断所述用户注册信息是否满足所述注册要求。
  4. 如权利要求2所述的应用软件的账号注册方法，其特征在于，所述向所述用户注册信息所对应用户终端下发注册失败的提示信息的步骤之后包括：
    接收基于所述注册失败提示信息所输入的修改信息，并用所述修改信息替换不满足注册要求的用户注册信息以形成新的用户注册信息，执行将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求的步骤。
  5. 如权利要求1所述的应用软件的账号注册方法，其特征在于，所述当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验的步骤包括：
    当接收到预设***界面所发起的注册请求时，输出提示信息，以提示输入用户身份信息；
    接收基于所述提示信息输入的用户身份信息，并根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验。
  6. 如权利要求5所述的应用软件的账号注册方法，其特征在于，所述根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验的步骤包括：
    若所述用户身份信息中所携带的验证标识符为校验失败标识符，则判定所述用户身份信息没有成功通过风控校验；
    所述方法还包括：
    若所述用户身份信息没有成功通过风控校验，则读取上一次进行风险校验的校验时间，并判断所述校验时间到当前时间的时间段是否大于预设时间；
    若所述时间段大于预设时间，则调用预设风控***接口对所述用户身份信息重新进行风控校验；
    若所述时间段小于或等于预设时间，则判定所述用户身份信息不具有注册应用软件账号的资质。
  7. 如权利要求5所述的应用软件的账号注册方法，其特征在于，所述根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验的步骤之前包括：
    若所述用户身份信息中所携带的验证标识符为空值，则判定所述用户身份信息尚未进行过风控校验，调用预设风控***接口对所述用户身份信息启动风控校验；
    若所述用户身份信息的风控校验成功，向所述用户身份信息分配校验成功标识符；
    若所述用户身份信息的风控校验失败，向所述用户身份信息分配校验失败标识符。
  8. 一种应用软件的账号注册装置，其特征在于，所述应用软件的账号注册装置包括：
    判断模块，用于当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
    确定模块，用于若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
    注册模块，用于接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
  9. 一种应用软件的账号注册设备，其特征在于，所述应用软件的账号注册设备包括：存储器、处理器、通信总线以及存储在所述存储器上的应用软件的账号注册程序；
    所述通信总线用于实现处理器和存储器之间的连接通信；
    所述处理器用于执行所述应用软件的账号注册程序，以实现以下步骤：
    当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
    若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
    接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
  10. 如权利要求9所述的应用软件的账号注册设备，其特征在于，所述对所述应用软件的账号进行注册的步骤包括：
    获取与所述注册应用软件类型对应的注册要求，并将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求；
    若所述用户注册信息满足所述注册要求，对所述应用软件进行注册，并在注册完成后向所述用户注册信息所对应用户终端下发注册成功的提示信息，以提示所述用户终端对所述所注册应用软件进行下载并登录；
    若所述用户注册信息不满足所述注册要求，停止对所述应用软件的注册，并向所述用户注册信息所对应用户终端下发注册失败的提示信息，所述注册失败的提示信息包括不满足注册要求的用户注册信息。
  11. 如权利要求10所述的应用软件的账号注册设备，其特征在于，所述将所述用户注册信息和所述注册要求对比，以判断所述用户注册信息是否满足所述注册要求的步骤包括：
    读取所述用户注册信息中的各字段值，以及与所述用户注册信息中的各字段值对应的所述注册要求中的各字段值；
    将所述用户注册信息中的各字段值与所述注册要求中的各字段值进行对比，以判断所述用户注册信息是否满足所述注册要求。
  12. 如权利要求10所述的应用软件的账号注册设备，其特征在于，所述向所述用户注册信息所对应用户终端下发注册失败的提示信息的步骤之后包括：
    接收基于所述注册失败提示信息所输入的修改信息，并用所述修改信息替换不满足注册要求的用户注册信息以形成新的用户注册信息，执行将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求的步骤。
  13. 如权利要求9所述的应用软件的账号注册设备，其特征在于，所述当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验的步骤包括：
    当接收到预设***界面所发起的注册请求时，输出提示信息，以提示输入用户身份信息；
    接收基于所述提示信息输入的用户身份信息，并根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验。
  14. 如权利要求13所述的应用软件的账号注册设备，其特征在于，所述根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验的步骤包括：
    若所述用户身份信息中所携带的验证标识符为校验失败标识符，则判定所述用户身份信息没有成功通过风控校验；
    所述方法还包括：
    若所述用户身份信息没有成功通过风控校验，则读取上一次进行风险校验的校验时间，并判断所述校验时间到当前时间的时间段是否大于预设时间；
    若所述时间段大于预设时间，则调用预设风控***接口对所述用户身份信息重新进行风控校验；
    若所述时间段小于或等于预设时间，则判定所述用户身份信息不具有注册应用软件账号的资质。
  15. 一种可读存储介质，其特征在于，所述可读存储介质上存储有应用软件的账号注册程序，所述应用软件的账号注册程序被处理器执行，以实现以下步骤：
    当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验；
    若所述用户身份信息成功通过风控校验，则根据所述注册请求中的标识符确定所注册应用软件类型，并输出与所述应用软件类型对应的注册界面到所述预设***界面；
    接收人工坐席通过所述注册界面输入的用户注册信息，对所述应用软件的账号进行注册。
  16. 如权利要求15所述的可读存储介质，其特征在于，所述对所述应用软件的账号进行注册的步骤包括：
    获取与所述注册应用软件类型对应的注册要求，并将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求；
    若所述用户注册信息满足所述注册要求，对所述应用软件进行注册，并在注册完成后向所述用户注册信息所对应用户终端下发注册成功的提示信息，以提示所述用户终端对所述所注册应用软件进行下载并登录；
    若所述用户注册信息不满足所述注册要求，停止对所述应用软件的注册，并向所述用户注册信息所对应用户终端下发注册失败的提示信息，所述注册失败的提示信息包括不满足注册要求的用户注册信息。
  17. 如权利要求16所述的可读存储介质，其特征在于，所述将所述用户注册信息和所述注册要求对比，以判断所述用户注册信息是否满足所述注册要求的步骤包括：
    读取所述用户注册信息中的各字段值，以及与所述用户注册信息中的各字段值对应的所述注册要求中的各字段值；
    将所述用户注册信息中的各字段值与所述注册要求中的各字段值进行对比，以判断所述用户注册信息是否满足所述注册要求。
  18. 如权利要求16所述的可读存储介质，其特征在于，所述向所述用户注册信息所对应用户终端下发注册失败的提示信息的步骤之后包括：
    接收基于所述注册失败提示信息所输入的修改信息，并用所述修改信息替换不满足注册要求的用户注册信息以形成新的用户注册信息，执行将所述用户注册信息和所述注册要求进行对比，以判断所述用户注册信息是否满足所述注册要求的步骤。
  19. 如权利要求15所述的可读存储介质，其特征在于，所述当接收到预设***界面所发起的注册请求时，判断与所述注册请求所对应的用户身份信息是否成功通过风控校验的步骤包括：
    当接收到预设***界面所发起的注册请求时，输出提示信息，以提示输入用户身份信息；
    接收基于所述提示信息输入的用户身份信息，并根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验。
  20. 如权利要求19所述的可读存储介质，其特征在于，所述根据所述用户身份信息中所携带的验证标识符确定所述用户身份信息是否成功通过风控校验的步骤包括：
    若所述用户身份信息中所携带的验证标识符为校验失败标识符，则判定所述用户身份信息没有成功通过风控校验；
    所述方法还包括：
    若所述用户身份信息没有成功通过风控校验，则读取上一次进行风险校验的校验时间，并判断所述校验时间到当前时间的时间段是否大于预设时间；
    若所述时间段大于预设时间，则调用预设风控***接口对所述用户身份信息重新进行风控校验；
    若所述时间段小于或等于预设时间，则判定所述用户身份信息不具有注册应用软件账号的资质。
PCT/CN2018/094107 2018-05-02 2018-07-02 应用软件的账号注册方法、装置、设备及可读存储介质 WO2019210570A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810412105.6 2018-05-02
CN201810412105.6A CN108600242B (zh) 2018-05-02 2018-05-02 应用软件的账号注册方法、装置、设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2019210570A1 true WO2019210570A1 (zh) 2019-11-07

Family

ID=63620633

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094107 WO2019210570A1 (zh) 2018-05-02 2018-07-02 应用软件的账号注册方法、装置、设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN108600242B (zh)
WO (1) WO2019210570A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110020514B (zh) * 2018-12-12 2023-05-30 创新先进技术有限公司 账户代理注册方法和装置
CN115021961A (zh) * 2022-04-28 2022-09-06 广东电网有限责任公司 一种账号注册方法、装置、设备以及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2360893A1 (en) * 2010-02-16 2011-08-24 Alcatel Lucent A method, a system and devices for locating a representation in a communications network
CN102194177A (zh) * 2011-05-13 2011-09-21 南京柯富锐软件科技有限公司 一种用于在线支付风险控制的***
CN104683299A (zh) * 2013-11-28 2015-06-03 中兴通讯股份有限公司 一种软件注册的控制方法、认证服务器及终端
CN106161360A (zh) * 2015-04-02 2016-11-23 阿里巴巴集团控股有限公司 用户注册方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9225532B2 (en) * 2010-12-06 2015-12-29 Verizon Patent And Licensing Inc. Method and system for providing registration of an application instance
US8639921B1 (en) * 2011-06-30 2014-01-28 Amazon Technologies, Inc. Storage gateway security model
CN106600275B (zh) * 2015-10-14 2020-08-21 阿里巴巴集团控股有限公司 一种风险识别方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2360893A1 (en) * 2010-02-16 2011-08-24 Alcatel Lucent A method, a system and devices for locating a representation in a communications network
CN102194177A (zh) * 2011-05-13 2011-09-21 南京柯富锐软件科技有限公司 一种用于在线支付风险控制的***
CN104683299A (zh) * 2013-11-28 2015-06-03 中兴通讯股份有限公司 一种软件注册的控制方法、认证服务器及终端
CN106161360A (zh) * 2015-04-02 2016-11-23 阿里巴巴集团控股有限公司 用户注册方法及装置

Also Published As

Publication number Publication date
CN108600242A (zh) 2018-09-28
CN108600242B (zh) 2021-04-06

Similar Documents

Publication Publication Date Title
WO2019104877A1 (zh) 通过网站对接购买保险的方法、装置、设备及介质
WO2018210118A1 (zh) 智能家居的分享授权方法、服务器及可读存储介质
WO2019192085A1 (zh) 银企直联通信方法、装置、设备及计算机可读存储介质
WO2015172684A1 (en) Ap connection method, terminal, and server
WO2018205545A1 (zh) 数据生成方法、装置、终端及计算机可读存储介质
WO2015196960A1 (en) Method and system for checking security of url for mobile terminal
WO2018107610A1 (zh) 业务数据处理方法、***、设备及计算机可读存储介质
WO2019196213A1 (zh) 接口测试方法、装置、设备及计算机可读存储介质
WO2019037396A1 (zh) 账户清结算方法、装置、设备及存储介质
WO2019100604A1 (zh) 账户查询方法、装置、设备及计算机可读存储介质
WO2018228050A1 (zh) 防止敏感信息泄露的方法、装置及存储介质
WO2020224247A1 (zh) 基于区块链的数据溯源方法、装置、设备及可读存储介质
WO2015131803A1 (en) Application recommending method and system
WO2018227880A1 (zh) 数据比对方法、装置、设备及可读存储介质
WO2017041538A1 (zh) 终端用户界面的受控显示方法及装置
WO2019104876A1 (zh) 保险产品的推送方法、***、终端、客户终端及存储介质
WO2019100531A1 (zh) 数字签名生成、验证方法及其设备和存储介质
WO2017190450A1 (zh) 进程关闭方法及装置
WO2018076811A1 (zh) 数据分享方法、装置、存储介质及电子设备
WO2018233301A1 (zh) 产品推荐方法、装置、设备以及计算机可读存储介质
WO2019085301A1 (zh) 座机未接来电的反馈方法、装置、设备及可读存储介质
WO2014180149A1 (en) Method, system and computer storage medium for handling of account theft in online games
WO2019161597A1 (zh) 基于即时通讯的信息发送方法、装置、设备和存储介质
WO2018053963A1 (zh) 智能电视的***升级方法及装置
WO2019134218A1 (zh) 基于vtm的转账方法、装置、服务器和存储介质

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: 18917125

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 03/02/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18917125

Country of ref document: EP

Kind code of ref document: A1