TW201318396A - Method for online registration and verification - Google Patents

Abstract

Mobile phone numbers are now used for account verification in several large websites including Facebook, Google, and Yahoo. In the verification process, a verification code will be sent to the user's phone via text, and the code is entered into a webpage by the user to complete the verification. Some websites further require users to register with a mobile phone number, which is then used for login verification identical to the above verification process: a code is sent via text message and, when the user receives the message, is entered into a webpage. However, sending verification codes via texts incurs significant costs. The present invention provides a method to reduce the expense of sending large amount of text messages for website/mobile app operators. The method comprises the following steps: the user sends at least one set of information required for registration or verification via text to a server (in the existing method, the text message is sent by the server); a website or mobile app operator automatically receives the text through one or more servers, intercepts the sender's phone number and the content of the message, and saves to the server; after sending the text message, the user logs into the website (the registration process is completed when the text message is sent) or verifies the user's account. The method has the following advantages: (1) reducing operating costs for website/app operators, (2) simplifying the registration/verification process, and (3) ensuring user registration by matching each registering/verifying user with one mobile phone number.

Description

A network registration and authentication method

Internet, newsletter, server, website, application

Existing large websites, such as Facebook, Google, Yahoo, etc., use mobile phone numbers to enhance authentication. The principle is to send a text message to the user's mobile phone, which has an authentication code. After the user receives it, enter the authentication code. Going to the website to complete the certification. Further, some websites even require users to register with their mobile phone number and use it as the login ID. The principle is the same as above. They all send a newsletter with a set of passwords that the user receives. After that, go back to the website and enter your password.

Compared with traditional e-mail registration, mobile phone registration can effectively reduce the flood of registration, because most people only have a set of mobile numbers, but there may be more than two e-mail addresses.

However, the biggest disadvantage of using this method to strengthen authentication or registration is that website operators need to pay a large amount of newsletter costs, and an average of 1 to 3 yuan is required to send a newsletter.

In order to reduce the cost of sending a large amount of newsletters to the website (or mobile application) operators, we propose a novel method, that is, the user should send the newsletter to the server (the traditional method is transmitted to the user by the server). Contains at least one set of information required for registration or certification. The website or mobile application operator automatically receives the newsletter through one or more servers, intercepts the mobile phone number of the sent SMS and the contents of the newsletter, and stores it in the server. After sending the newsletter, you can return to the original website to log in (the registration is completed at the same time as the completion of the newsletter) or the authentication action. Advantages:

1 Reduce the operating costs of website (or mobile app) operators:

Effectively transfer the cost of sending the newsletter to the user. Since each user only needs to bear the cost of transmitting the newsletter, a letter of about 1~3 yuan is an affordable cost for the user.

2 Steps to simplify registration (or certification):

In the original method, the user needs to go to the website to fill in the mobile phone number, then accept the newsletter, and finally return to the website to fill in the newsletter content. There are three main steps. The proposed method allows the user to actively send the newsletter, and then go to the website to log in or Certification requires only two steps, reducing the complexity of registration or authentication.

3 Confirm that the website registrant (or certifier) is a mobile number user to prevent flooding registration:

By picking up the mobile phone number in the newsletter, you can confirm that the website registrant is the user of the mobile phone number to prevent flooding registration (ex: use multiple emails to register multiple accounts)

Embodiment 1:

1.

Device: (for text messaging) communication device (ex: mobile phone)

Action: The user enters a specific SMS content (ex: password, authentication code, email, username) and sends it to a certain group or groups of specific mobile numbers (or mobile phone code)

2.

Device: Server (the server is connected to one or more sets of mobile numbers above) (the server may have one or more)

Action: The server receives the SMS. The code on the server intercepts the required SMS content and the mobile phone number and stores it on the server (ex: database).

3.

Device: client interface (ex: website or mobile app)

Action: The user enters the transmitted newsletter data (ex: password, authentication code, etc.) to complete a specific purpose (ex: registration, authentication, etc.)

Embodiment 2:

1.

Device: (for text messaging) communication device (ex: mobile phone)

Action: The user enters a specific SMS content (ex: password, authentication code, email, username) and sends it to a certain group or groups of specific mobile numbers (or mobile phone code)

2.

Device: A server (the server is connected to one or more sets of mobile phone numbers above) (the server may be one or more)

Action: Receive the newsletter and forward it to the B server (the server may have one or more)

3.

Device: B server (the server may be one or more)

Action: Receive the SMS from the A server, the code on the B server captures the content of the SMS, and the mobile phone number is saved to the server (ex: database).

4.

Device: client interface (ex: website or mobile app)

Action: The user enters the transmitted newsletter data (ex: password, authentication code, etc.) to complete a specific purpose (ex: registration, authentication, etc.)

Claims (16)

A system for network registration or authentication, the system comprising at least: a communication device that allows a user to transmit a short message with a mobile phone number. The server can receive and process a short message from the communication device, and can receive and process the client from the client. Data. The client interface allows the user to transfer data to the server. For example, the system of claim 1 of the patent scope, wherein the communication device can be: a mobile phone, a backend server of a website that can transmit a newsletter. For example, the system of claim 1 of the patent scope, wherein the above server can be: a physical server, a virtual server. For example, in the system of claim 1, the client interface can be: website, mobile application, tablet device application, computer application. For example, in the system of claim 1, the server may be one or more, and the functions of the servers may be the same or different. The server receiving the short message does not need to know the mobile phone number in advance. For example, in the system of claim 1, the content of the above newsletter may be: password, authentication code, email, user name, gender, date of birth, student number, job number, identity card number, passport number, identity code. , machine code, chaotic digital, and other code with private information. For example, in the system of claim 1, the above newsletter may be one or more. A system for network registration or authentication, the system comprising at least: a communication device for allowing a user to transmit a short message with a mobile phone number. A server can receive and transfer a short message from a communication device, a B server, Receive and process data from the A server to receive and process data from the client. The client interface allows the user to transfer data to the server. For example, the system of claim 5, wherein the communication device can be: a mobile phone, a backend server of a website that can transmit a newsletter. For example, the system of claim 5, wherein the above server can be: a physical server, a virtual server. For example, the system of claim 5, wherein the client interface can be: website, mobile application, tablet device application, computer application. For example, in the system of claim 5, wherein the A server can be one or more, and the functions of the servers can be the same or different. The server receiving the newsletter does not need to know the mobile phone number in advance. For example, in the system of claim 5, wherein the B server can be one or more, and the functions of the servers can be the same or different. For example, the system of claim 5, wherein the above transfer method may be one or more times. For example, in the system of claim 5, the content of the above newsletter may be: password, authentication code, email, user name, gender, date of birth, student number, job number, identity card number, passport number, identity code. , machine code, chaotic digital, and other code with private information. For example, in the system of claim 5, the above newsletter may be one or more.