WO2018219260A1 - Method, device and system for binding mobile phone number - Google Patents

Abstract

Disclosed are a method, device and system for binding a mobile phone number. The method comprises: a terminal generating a binding request, the binding request comprising a user account; the terminal sending the binding request to a server via a first channel, the first channel being one of a short message channel and a data channel; the terminal generating an information digest corresponding to the binding request; and the terminal sending the information digest corresponding to the binding request to the server via a second channel, the second channel being the other one of the short message channel and the data channel, and the second channel being different from the first channel. The server is used for establishing a binding relationship between the user account and the first mobile phone number when it is verified that the binding request matches the information digest, so as to enable a user to complete a binding process by merely triggering the generation of a binding request, thereby simplifying an operation of the user during the binding process and improving the efficiency of human-computer interaction.

Description

Method, device and system for binding mobile phone number

This application claims the priority of the Chinese patent application filed on June 2, 2017, the Chinese National Intellectual Property Office, the application number is 201710407291.X, and the invention name is "method, device and system for binding mobile phone numbers". The entire contents are incorporated herein by reference.

Technical field

The embodiments of the present invention relate to the field of mobile terminals, and in particular, to a method, an apparatus, and a system for binding a mobile phone number.

Background technique

In a mobile terminal, many applications need to bind a mobile phone number to a user account, and implement additional functions such as a verification code receiving function, a short message (Short Message, SMS) push function, and a short message control function through the mobile phone number.

In the related art, the process of binding a mobile phone number to a user account requires more steps, and the human-computer interaction efficiency of the entire process is low.

Summary of the invention

The embodiment of the present invention provides a mobile phone number binding method, device, and system, which can be used to solve the problem of low human-computer interaction efficiency when binding a mobile phone number to a user account in the related art. The technical solution is as follows:

In a first aspect, the embodiment of the present application provides a method for binding a mobile phone number, where the method includes:

The terminal generates a binding request, where the binding request includes a user account;

The terminal sends the binding request to the server through the first channel, where the first channel is one of a short message channel and a data channel; and the short message channel is a channel for sending data through the short message of the first mobile phone number. The data channel is a channel for transmitting data through a mobile communication network or a wireless fidelity network;

The terminal generates a message digest corresponding to the binding request;

Sending, by the terminal, the information digest corresponding to the binding request to the server by using a second channel, where the second channel is one of the short message channel and the data channel, and the second channel is The first channel is different, and the server is configured to establish a binding relationship between the user account and the first mobile phone number when verifying that the binding request matches the information digest.

In an optional embodiment, the terminal generates a binding request, including:

Receiving, by the terminal, a first triggering operation;

The terminal acquires the user account according to the first triggering operation;

The terminal generates the binding request according to the user account.

In an optional embodiment, before the terminal generates the binding request according to the user account, the terminal further includes:

The terminal acquires operation verification information;

The terminal generates the binding request according to the user account, including:

The terminal generates the binding request according to the user account and the operation verification information, where the operation verification information is used to verify the validity of the current binding process.

In an optional embodiment, the operation verification information includes: a ticket and/or a login token;

The ticket is a ticket corresponding to a binding operation, and the login token is a token generated after the user account is successfully logged in, and the login token has an expiration date.

In a second aspect, the embodiment of the present application provides a method for binding a mobile phone number, where the method includes:

Receiving, by the first channel, a binding request sent by the terminal, where the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data by using a short message of the first mobile phone number, the data channel Is a channel for transmitting data through a mobile communication network or a wireless fidelity network, where the binding request includes a user account, and the first mobile phone number is a mobile phone number corresponding to the terminal;

Receiving, by the second channel, a message digest of the binding request sent by the terminal; the second channel is one of the short message channel and the data channel, and the second channel is the first channel Different channels;

Verifying whether the binding request and the information digest of the binding request match;

When the binding request matches the information digest, the user account and the first mobile phone number are bound.

In an optional embodiment, before the binding of the user account and the first mobile phone number, the method further includes:

Obtaining operation verification information from the binding request;

Verifying the validity of the binding process according to the operation verification information;

When the binding process is valid, the step of establishing a binding relationship between the user account and the first mobile phone number is performed.

In an optional embodiment, the operation verification information includes: a ticket;

The verifying the validity of the binding process according to the operation verification information, including:

A ticket that verifies whether the ticket corresponds to a binding operation.

In an optional embodiment, the operation verification information includes: a login token;

The verifying the validity of the binding process according to the operation verification information, including:

Verify that the validity time of the login token has expired.

In a third aspect, an embodiment of the present application provides an apparatus for binding a mobile phone number, where the apparatus includes:

a generating module, configured to generate a binding request, where the binding request includes a user account;

a sending module, configured to send the binding request to the server by using a first channel, where the first channel is one of a short message channel and a data channel; and the short message channel is sent by using a short message of the first mobile phone number Channel, the data channel is a channel for transmitting data through a mobile communication network or a wireless fidelity network;

The generating module is further configured to generate a message digest corresponding to the binding request;

The sending module is further configured to send the information digest corresponding to the binding request to the server by using a second channel, where the second channel is another one of the short message channel and the data channel. The server is configured to establish a binding relationship between the user account and the first mobile phone number when verifying that the binding request matches the information digest.

In an optional embodiment, the generating module is configured to receive a first triggering operation, acquire the user account according to the first triggering operation, and generate the binding request according to the user account.

In an optional embodiment, the apparatus further includes:

An obtaining module, configured to obtain operation verification information;

The generating module is further configured to generate the binding request according to the user account and the operation verification information, where the operation verification information is used to verify the validity of the current binding process.

In an optional embodiment, the operation verification information includes: a ticket and/or a login token;

The ticket is a ticket corresponding to a binding operation, and the login token is a token generated after the user account is successfully logged in, and the login token has an expiration date.

In a fourth aspect, an apparatus for binding a mobile phone number is provided, the device comprising:

a receiving module, configured to receive, by using the first channel, a binding request sent by the terminal, where the first channel is one of a short message channel and a data channel; and the short message channel is a channel for sending data by using a short message of the first mobile phone number The data channel is a channel for transmitting data through a mobile communication network or a wireless fidelity network, the binding request includes a user account, and the first mobile phone number is a mobile phone number corresponding to the terminal;

The receiving module is further configured to receive, by using a second channel, a message digest of the binding request sent by the terminal; the second channel is one of the short message channel and the data channel, and the The second channel is different from the first channel;

The verification module is further configured to verify whether the binding information of the binding request and the binding request match;

And a binding module, configured to establish a binding relationship between the user account and the first mobile phone number when the binding request and the information digest match.

In an optional embodiment, the apparatus further includes:

An obtaining module, configured to obtain operation verification information from the binding request;

The verification module is further configured to verify the validity of the binding process according to the operation verification information;

The binding module is further configured to perform the step of establishing a binding relationship between the user account and the first mobile phone number when the current binding process is valid.

In an optional embodiment, the operation verification information includes: a ticket;

The verification module is configured to verify whether the ticket is a ticket corresponding to the binding operation.

In an optional embodiment, the operation verification information includes: a login token;

The verification module is configured to verify whether the valid time of the login token is expired.

In a fifth aspect, a terminal is provided, the terminal comprising: a processor and a memory, wherein the memory stores at least one instruction loaded by the processor and executed to implement the first aspect or the first A method for binding a mobile number as described in any of the alternative implementations.

In a sixth aspect, a server is provided, the server comprising: a processor and a memory, wherein the memory stores at least one instruction loaded by the processor and executed to implement the second aspect or the second A method for binding a mobile number as described in any of the alternative implementations.

In a seventh aspect, a computer storage medium is provided, wherein the storage medium stores at least one instruction that is loaded and executed by a processor to implement the first aspect or any of the alternative implementations of the first aspect The method used to bind the mobile phone number.

In an eighth aspect, a computer storage medium is provided, wherein the storage medium stores at least one instruction that is loaded and executed by a processor to implement the second aspect or any alternative implementation of the second aspect The method used to bind the mobile phone number.

It should be noted that the above first aspect, second aspect, and third aspect are only used to explain different aspects of the present application, but do not have a sequential definition or priority limiting function.

The beneficial effects brought by the technical solutions provided by the embodiments of the present application include at least:

The mobile communication network or the WiFi network is used as another channel by using the short message service of the first mobile phone number as a channel; the binding request and the message digest of the binding request are respectively sent to the server through respective channels, and the server is When the authentication binding request and the message digest match, the user account and the first mobile phone number are bound. The user only needs to trigger the generation of the binding request, and the other steps are automatically executed by the terminal, and the binding process between the user account and the first mobile phone number can be completed, and the user does not need to request the verification code and input the verification code, which simplifies the binding of the user. The operation in the process improves the efficiency of human-computer interaction.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a schematic structural diagram of a system for binding a mobile phone number according to various embodiments of the present application;

2 is a flowchart of a method for binding a mobile phone number according to an embodiment of the present application;

3 is a flowchart of a method for binding a mobile phone number according to another embodiment of the present application;

FIG. 4 is a schematic diagram of an interface for implementing a method for binding a mobile phone number according to an embodiment of FIG. 3;

FIG. 5 is a structural block diagram of an apparatus for binding a mobile phone number according to an embodiment of the present application; FIG.

6 is a structural block diagram of an apparatus for binding a mobile phone number according to another embodiment of the present application;

FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a server according to an embodiment of the present application.

detailed description

In order to make the objects, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The process of binding a mobile phone number to a user account in the related art generally includes: the application displays a registered user interface, and the registered user interface provides a mobile phone number input box, a verification code button, a verification code input box, and a submit button; the user is in the mobile phone. Enter the mobile phone number in the number input box and click the verification code to get the button; the application sends the mobile phone number to the server, and the server sends a short message carrying the verification code to the mobile phone number; after viewing the short message, the user inputs the verification code. Verify the code input box and click the submit button; the application sends the user account, mobile phone number and verification code to the server. When the server verifies that the mobile phone number and the verification code match, the server establishes a binding relationship between the user account and the mobile phone number.

The above method requires the user to input a mobile phone number, click a submit button, input a verification code, and click a submit button in a total of four operation steps, and the human-computer interaction efficiency of the whole process is low. Therefore, the embodiments of the present application provide the following embodiments.

FIG. 1 is a schematic structural diagram of a system for binding a mobile phone number according to an exemplary embodiment of the present application. The system for binding a mobile phone number may be a system having a service for providing a terminal by using a short message, and the service includes at least one of remote control, verification code verification, and information push. The system for binding a mobile phone number includes: a terminal 120 and a server 140.

The terminal 120 can be a mobile phone, a tablet computer, a wearable electronic device, an e-book reader, an MP3 (Moving Picture Experts Group Audio Layer III) player, and an MP4 (Moving Picture Experts Group Audio Layer IV). Dynamic image experts compress standard audio layers 4) terminals such as players and laptops.

Optionally, the terminal 120 runs a predetermined application, and the predetermined application includes at least one of the following functions: a remote control function by using a short message, a verification code verification function by using a short message, and information through a short message. Push function. Different users are distinguished by user accounts in the predetermined application, and each user account needs to be bound to its corresponding mobile phone number. Optionally, each user account can be bound to at least one mobile phone number.

Optionally, the terminal 120 is connected to and communicates with the server 140 via a wired network or a wireless network. On the one hand, the server 140 and the terminal 120 can communicate through the short message channel, and the short message channel is a channel for transmitting and receiving data through the short message service of the currently valid mobile phone number on the terminal 120, usually by a circuit switching domain in the mobile communication network ( Circuit Switching Domain (CS) is implemented; on the other hand, the server 140 and the terminal 120 can communicate through a data channel, which is a Packet Switching Domain (PS) or Wireless Fidelity (Wireless Fidelity) in the mobile communication network. Fidelity, WiFi) network implementation channel.

The server 140 is a background server of a predetermined application, and the server 140 may be a server, a server cluster composed of multiple servers, or a cloud computing center. The server 140 has a function of directly transmitting short messages and/or receiving short messages, or the server 140 has a function of transmitting and/or receiving short messages through a short message platform provided by a mobile operator.

2 is a flow chart of a method for binding a mobile phone number, shown in an exemplary embodiment of the present application. This embodiment is exemplified by the method being applied between the terminal 120 of the system shown in FIG. 1 and the server 140. The method includes:

Step 201: The terminal generates a binding request, where the binding request includes a user account.

The binding request is used to request the server to bind the user account and the mobile phone number. In other embodiments, the binding request may also have other names such as a registration request, an association request, and the like, which is not limited in this embodiment.

The binding request carries a user account. Optionally, the binding request further carries a first mobile phone number to be bound, where the first mobile phone number is a mobile phone number corresponding to the terminal. In different embodiments, the information content carried by the binding request may be different.

Step 202: The terminal sends the binding request to the server through the first channel.

The first channel is one of a short message channel and a data channel. The short message channel is a channel for transmitting and/or receiving data through a short message service of a mobile number, which is a channel for transmitting and/or receiving data through a mobile communication network or a WiFi network.

Step 203: The server receives, by using the first channel, a binding request sent by the terminal.

Step 204: The terminal generates a message digest corresponding to the binding request.

The information digest may be information obtained by calculating a binding request by using MD5 (Message Digest Algorithm 5, information digest algorithm fifth generation), a hash algorithm, other irreversible encryption algorithms, or a signature algorithm. Usually, the summary of the information corresponding to each binding request is unique.

Optionally, step 204 may be performed before step 202. This embodiment does not limit the sequence between step 202 and step 204.

Step 205: The terminal sends the information digest of the binding request to the server through the second channel.

The second channel is one of a short message channel and a data channel, and the second channel is different from the first channel.

Step 206: The server receives, by using the second channel, a message digest corresponding to the binding request sent by the terminal.

Step 207: The server verifies whether the binding request and the information digest match.

A summary of the information received by the server may be referred to as a first information digest.

Optionally, the server calculates the second information digest according to the same algorithm as the terminal, and compares the first information digest with the second information digest; if the two information digests are identical, the binding is considered The request matches the message digest; if the two message digests are not identical or completely different, the binding request is considered to not match the message digest.

Step 208: When the binding request and the information digest match, the server establishes a binding relationship between the user account and the first mobile phone number.

Optionally, the server obtains the user account and the first mobile phone number from the binding request, and binds the user account and the first mobile phone number. Alternatively, the server obtains the user account from the binding request, obtains the first mobile phone number (that is, the sender of the short message) from the short message received by the short message channel, and then binds the user account with the first mobile phone number.

In this embodiment, the context of the two sending steps shown in step 202 and step 205 is not limited. Step 202 may be performed simultaneously with step 205, and step 202 may be performed after 205.

In the method for binding a mobile phone number provided by this embodiment, the mobile communication network or the WiFi network is regarded as another channel by using the short message service of the first mobile phone number as a channel; the binding request and the binding are The requested message digest is sent to the server through the respective channels. When the server matches the authentication binding request and the information digest, the server establishes a binding relationship between the user account and the first mobile phone number. The user only needs to trigger the generation of the binding request, and the other steps are automatically executed by the terminal, and the binding process between the user account and the first mobile phone number can be completed, and the user does not need to request the verification code and input the verification code, which simplifies the binding of the user. The operation in the process improves the efficiency of human-computer interaction.

3 is a flow chart of a method for binding a mobile phone number, shown in another exemplary embodiment of the present application. This embodiment is exemplified by the method applied to the terminal 120 and the server 140 in the system shown in FIG. The method includes:

Step 301: The terminal sends a login request to the server, where the login request carries a user account and a password;

When the terminal needs to communicate with the server, the login request is generated using the pre-registered user account and password, and the login request is sent to the server.

Illustratively, taking the predetermined application in the terminal as a search for a mobile phone program, referring to the left side diagram of FIG. 4, the user inputs the user account zhangsan@xxx.com and the input box 41 in the login interface of the search for the mobile phone program. After the password is clicked on the "Login" button 42, the terminal sends a login request to the server.

Correspondingly, the server receives the login request sent by the terminal.

Step 302: The server verifies the user account and password; and after the verification succeeds, the login token is fed back to the terminal.

A token is a digital token assigned to a terminal by a server when the login is successful. The login token usually has an expiration date (for example, within 10 minutes). When the terminal subsequently communicates with the server, the login token needs to be carried in the information, so that the server recognizes that the terminal is in a valid login state.

There is a correspondence between the user account, login password, and login token. Table 1 schematically shows the correspondence.

Table I

username	login password	Login token token	Validity period
Zhang San	128568	1F4Gsdfa	11:02-11:12
Li Si	865986	5548asdf1	10:59-11:09
Wang Wu	1155336	2146451af	11:04-11:14

Correspondingly, the terminal stores the login token.

After receiving the login token, the terminal successfully logs in.

Step 303: The terminal receives the first triggering operation.

Optionally, the first triggering operation is an operation for generating a binding request.

Referring to the right side diagram of FIG. 4, the terminal jumps from the login interface to open the search for the mobile phone interface. If the user wishes to open the search device function, click the "Open Phone Search" button 43 when the search for the mobile phone interface is opened. The process of opening the search for the mobile phone can be regarded as a binding process of binding the user account and the first mobile phone number.

Step 304: The terminal acquires a user account and operation verification information according to the first triggering operation.

A user account is an account that is registered in the server and is used to identify the user. Operational verification information is used to verify the validity of this binding process.

Optionally, the terminal further acquires the first mobile phone number, where the first mobile phone number is the mobile phone number corresponding to the terminal.

Step 305: The terminal generates a binding request according to the user account and the operation verification information.

Optionally, the operation verification information includes: a ticket and/or a login token. The ticket is a ticket corresponding to the binding process, and the ticket can be a string, such as the string A1. The ticket is used to indicate to the server that the operation is a binding operation; the login token is a token generated after the login is successful and the login token has an expiration date, and the first login token may be feedback from the server in step 302. The token may also be a token that was updated by the server after step 302.

Optionally, the binding request = (user account, ticket, login token).

In a possible implementation manner, if the terminal further acquires the first mobile phone number, the terminal generates a binding request according to the user account, the first mobile phone number, and the operation verification information. For example, the terminal sequentially sorts the user account, the first mobile phone number, and the operation verification information, and adds a comma between each two information to obtain a binding request=(user account, first mobile phone number, ticket, login token).

In another possible implementation manner, if the terminal also obtains the operation verification information, the binding request=(user account, terminal identifier, first mobile phone number, ticket, login token). When the terminal is a mobile phone, the terminal identifier may be an IMEI (International Mobile Equipment Identity).

Step 306: The terminal sends the binding request to the server through the first channel.

Schematically, the terminal sends a binding request to the server through the data channel. Optionally, the terminal encrypts the binding request and then sends the binding request to the server.

Step 307: The server receives the binding request sent by the terminal by using the first channel.

The server receives the binding request sent by the terminal through the data channel. If the binding request is information encrypted by the terminal, the server decrypts the binding request in the same manner to obtain the specific content of the binding request.

Step 308, the terminal generates a message digest corresponding to the binding request.

In an embodiment, the information digest of the binding request is obtained by calculating a binding request by using MD5 (Message Digest Algorithm 5, information digest algorithm fifth generation), a hash algorithm, other irreversible encryption algorithm, or a signature algorithm. . Usually, the summary of the information corresponding to each binding request is unique.

Step 309: The terminal sends the information digest of the binding request to the server through the second channel.

Schematically, the terminal sends a message digest to the server via the short message channel. The short message channel is a channel through which the terminal sends data to the server through the short message service of the first mobile number.

The server may bind two SMS service numbers in advance on the SMS platform provided by the operator: an uplink short message service number and a downlink short message service number, the uplink short message service number is used to receive the short message sent by the terminal, and the downlink short message service number is used to The terminal sends a short message. For example, the uplink short message service number is: 10600x, and the downlink short message service number is: 10602x.

The terminal stores the uplink short message service number 10600x in advance, and the terminal uses the first mobile phone number as the short message sender, the uplink short message service number 10600x as the short message recipient, and the message summary as the short message content to send the short message, and the short message platform receives the message. Forward to the server after the SMS.

Step 310: The server receives, by using the second channel, a message digest corresponding to the binding request sent by the terminal.

The server receives the summary of the information sent by the control terminal through the short message channel. Optionally, since the information digest is carried in the short message, the sender of the short message is the first mobile phone number, and the server saves the correspondence between the first mobile phone number and the information digest.

A summary of the information received by the server may be referred to as a first information digest.

Step 311: The server obtains a user account and operation verification information from the binding request, where the operation verification information includes a ticket and/or a login token.

This embodiment is exemplified by the operation verification information including the ticket and the login token.

Optionally, the server parses the binding request to obtain a user account, a ticket, and a login token.

Optionally, the server parses the binding request to obtain a user account, a first mobile phone number, a ticket, and a login token.

Optionally, the server parses the binding request, and obtains a user account, a terminal identifier, a first mobile phone number, a ticket, and a login token.

Step 312: The server detects whether the ticket is a ticket corresponding to the binding process.

Because there may be multiple operations between the terminal and the server: the binding process, the logout process, and the process of replacing the SIM card, different operations respectively correspond to the respective tickets, and the server needs to detect whether the parsed ticket is corresponding to the binding process. If the ticket is a ticket corresponding to the binding process, proceed to step 313; if the ticket is not a ticket corresponding to the binding process, but a ticket corresponding to other processes, perform other processes (such as a logout process or update) process).

Step 313: When the ticket is a ticket corresponding to the binding process, the server detects whether the login token is in an expiration date;

Each login token has a certain expiration date, such as 10 minutes, 30 minutes, 2 hours, and so on.

The server detects whether the parsed token is in an expiration date; if it is in the expiration date, it proceeds to step 314; if it is not in the expiration, sends a binding failure message to the terminal.

It should be noted that the execution order of step 312 and step 313 may be interchanged or performed in parallel. Only when the detection results of step 312 and step 313 are both "YES", step 314 is entered.

Step 314, when the login token is in the expiration date, the server verifies whether the binding request and the information digest match;

Optionally, the server calculates the second information digest according to the same algorithm as the terminal, and compares the first information digest with the second information digest; if the two information digests are identical, the binding is considered The request matches the information digest, and the process proceeds to step 315. If the two information digests are not identical or completely different, the binding request and the information digest are not matched, and the binding failure information is fed back to the terminal.

Optionally, if the server stores the correspondence between the first mobile phone number and the first information digest, the server queries the corresponding binding request according to the first mobile phone number, and generates a second information digest according to the queried binding request. Or, the server does not store the correspondence between the first mobile phone number and the first information digest, and when the server stores only the first information digest, all binding requests received by the server (which may be in the latest time period) are A second information digest is generated to query whether there is a second information digest that is completely consistent with the first information digest. If there is a completely identical second information digest, it is determined that the two match.

Step 315: When the binding request and the information digest match, the server establishes a binding relationship between the user account and the first mobile phone number.

Each terminal identifier can be bound to at least one first mobile number. That is, the first mobile number can be more than one.

In a possible embodiment, when the server opens the function of finding the device, the server establishes a binding relationship between the user account, the terminal identifier, and the first mobile phone number. Table 2 schematically shows the binding relationship.

Table II

user account	Terminal Identification (IMEI)	phone number
Zhang San	Xxxxxx0601472104	134xxxx8888
Li Si	Xxxxxx121272105	135xxxx6666
Li Si	Xxxxxx0701472234	186xxxx7777

In step 316, the server sends a binding success message to the terminal.

After the terminal successfully opens the search for the mobile phone function, the server sends a binding success message to the terminal. Optionally, the binding success message can be sent through a short message channel or a data channel.

Referring to FIG. 4C, after the server feeds back the binding success message to the terminal, the terminal jumps from the open search mobile phone interface to the search mobile phone function interface, and the search mobile phone function interface provides the location display of the terminal in the map, and the terminal name is “Zhang San”. The mobile phone and the status "online", after which, the user can control the terminal to ring, lock, erase data and other operations.

In the method provided in this embodiment, the short message service of the first mobile phone number is used as a channel, and the mobile communication network or the WiFi network is used as another channel; the binding request and the message digest of the binding request are respectively passed through respective The channel is sent to the server, and the server establishes a binding relationship between the user account and the first mobile phone number when the verification binding request and the message summary match. The user only needs to trigger the generation of the binding request, and the other steps are automatically executed by the terminal, and the binding process between the user account and the first mobile phone number can be completed.

In the method provided in this embodiment, the user only needs to trigger the first triggering operation in the binding process, and does not require the user to request the verification code and input the verification code, which simplifies the operation of the user in the binding process and improves the person. Machine interaction efficiency.

In the method provided in this embodiment, by adding the operation verification information, the server can detect the validity of the binding process, and only when the binding process is valid, the user account and the first mobile phone number are performed. Binding improves the security of the binding process.

The following is an embodiment of the apparatus of the present application, which may be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

FIG. 5 is a block diagram of an apparatus for binding a mobile phone number provided by an exemplary embodiment of the present application, which may be implemented as all or part of a terminal by software, hardware, or a combination of both. The device includes:

The generating module 510 is configured to generate a binding request, where the binding request includes a user account;

The sending module 520 is configured to send the binding request to the server by using a first channel, where the first channel is one of a short message channel and a data channel, and the short message channel is sent by using a short message of the first mobile phone number a channel of data, which is a channel for transmitting data through a mobile communication network or a wireless fidelity network;

The generating module 510 is further configured to generate a message digest corresponding to the binding request.

The sending module 520 is further configured to send the information digest corresponding to the binding request to the server by using a second channel, where the second channel is another one of the short message channel and the data channel, The server is configured to establish a binding relationship between the user account and the first mobile phone number when verifying that the binding request matches the information digest.

In an optional embodiment, the generating module 510 is configured to receive a first triggering operation, acquire the user account according to the first triggering operation, and generate the binding request according to the user account.

In an optional embodiment, the apparatus further includes:

The obtaining module 530 is configured to obtain operation verification information.

The generating module 510 is further configured to generate the binding request according to the user account and the operation verification information, where the operation verification information is used to verify the validity of the binding process.

In an optional embodiment, the operation verification information includes: a ticket and/or a login token;

The ticket is a ticket corresponding to a binding operation, and the login token is a token generated after the user account is successfully logged in, and the login token has an expiration date.

The generating module 510 can be implemented by a processor executing a program, and the sending module 520 can be implemented by a processor controlling a transmitter. The transmitter has short message transmission capability and/or data network transmission capability. The obtaining module 530 may be implemented by a processor executing a program, or the obtaining module 530 may be implemented by a processor executing a program.

FIG. 6 shows a block diagram of an apparatus for binding a mobile number provided by another exemplary embodiment of the present application. The device can be implemented as all or part of a server by software, hardware or a combination of both. The device includes:

The receiving module 610 is configured to receive, by using the first channel, a binding request sent by the terminal, where the first channel is one of a short message channel and a data channel, and the short message channel is sent by using a short message of the first mobile phone number. a channel, the data channel is a channel for transmitting data through a mobile communication network or a wireless fidelity network, the binding request includes a user account, and the first mobile phone number is a mobile phone number corresponding to the terminal;

The receiving module 610 is further configured to receive, by using a second channel, a message digest of the binding request sent by the terminal, where the second channel is one of the short message channel and the data channel, and The second channel is different from the first channel;

The verification module 620 is further configured to verify whether the binding information of the binding request and the binding request match;

The binding module 630 is configured to establish a binding relationship between the user account and the first mobile phone number when the binding request and the information digest match.

In an optional embodiment, the apparatus further includes:

The obtaining module 640 is configured to obtain operation verification information from the binding request.

The verification module 620 is further configured to verify the validity of the binding process according to the operation verification information;

The binding module 630 is further configured to perform the step of establishing a binding relationship between the user account and the first mobile phone number when the current binding process is valid.

In an optional embodiment, the operation verification information includes: a ticket;

The verification module 620 is configured to verify whether the ticket is a ticket corresponding to the binding operation.

In an optional embodiment, the operation verification information includes: a login token;

The verification module 620 is configured to verify whether the valid time of the login token is expired.

The receiving module 610 can be implemented by a processor control receiver, which has short message receiving capability and/or data network receiving capability. The foregoing verifying module 620 can be implemented by a processor executing a program. The transmitter has short message transmission capability and/or data network transmission capability. The binding module 630 can be implemented by a processor executing a program.

It should be noted that, when the device for binding a mobile phone number provided by the foregoing embodiment is bound to the mobile phone number, only the division of each functional module is used as an example. In an actual application, the foregoing function may be allocated according to requirements. Different functional modules are completed, that is, the internal structure of the terminal or the server is divided into different functional modules to complete all or part of the functions described above. In addition, the device for binding a mobile phone number provided by the foregoing embodiment is the same as the method for binding a mobile phone number. The specific implementation process is described in detail in the method embodiment, and details are not described herein again.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

FIG. 7 is a schematic structural diagram of a terminal involved in an exemplary embodiment of the present application. The terminal includes: the terminal includes: a processor 711, a receiver 712, a transmitter 713, a memory 714, and a bus 715.

The processor 711 includes one or more processing cores, and the memory 714 is coupled to the processor 711 via a bus 715 for storing at least one instruction, and the processor 711 executing the instructions in the memory 714 to implement the methods illustrated in FIGS. 2 and 3. The steps of the method for binding a mobile phone number on the terminal side in the embodiment.

Receiver 712 and transmitter 713 can be implemented as a communication component, which can be a communication chip for modulating and/or demodulating information and receiving or transmitting the information over a wireless signal.

Moreover, memory 714 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable In addition to Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.

The foregoing structure is only a schematic description of the terminal, and the terminal may include more or fewer components, for example, the terminal may not include the receiver, or the terminal further includes other components such as a sensor, a display screen, a power supply, etc., this embodiment does not Let me repeat.

The embodiment of the present application further provides a computer readable medium, where the at least one instruction is stored, and when the instruction is executed by the processor 711, the terminal side of the method embodiment shown in FIG. 2 and FIG. 3 is used to bind the mobile phone number. The steps of the method.

FIG. 8 is a schematic structural diagram of a server provided by an exemplary embodiment of the present application. The server includes a processor 811, a receiver 812, a transmitter 813, a memory 814, a bus 815, and a network interface 816.

The processor 811 includes one or more processing cores. The memory 814 is coupled to the processor 811 via a bus 815 for storing at least one instruction, and the processor 811 executing the instructions in the memory 814 to implement the methods illustrated in FIGS. 2 and 3. The steps of the method for binding a mobile phone number on the server side in the embodiment.

Receiver 812 and transmitter 813 can be implemented as a communication component, which can be a communication chip for modulating and/or demodulating information and receiving or transmitting the information over a wireless signal. In other embodiments, the receiver 812 and the transmitter 813 can alternatively be implemented as a network interface 816 through which the server is connected to the short message transmitting platform to send and receive short messages through the short message transmitting platform.

Moreover, memory 814 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable In addition to Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.

The above structure is only for the schematic description of the server, the server may include more or less components, such as the server also includes other components such as an I/O interface such as a keyboard and a mouse, a power supply, and the like, which will not be described in this embodiment. .

The embodiment of the present application further provides a computer readable medium, where the at least one instruction is stored, and when the instruction is executed by the processor 811, the server side for binding the mobile phone number in the method embodiment shown in FIG. 2 and FIG. 3 is implemented. The steps of the method.

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above is only the preferred embodiment of the present application, and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application are included in the protection of the present application. Within the scope.

Claims (21)

1. A method for binding a mobile phone number, the method comprising:

   The terminal generates a binding request, where the binding request includes a user account;

   The terminal sends the binding request to the server through the first channel, where the first channel is one of a short message channel and a data channel; and the short message channel is a channel for sending data through the short message of the first mobile phone number. The data channel is a channel for transmitting data through a mobile communication network or a wireless fidelity network;

   The terminal generates a message digest corresponding to the binding request;

   Sending, by the terminal, the information digest corresponding to the binding request to the server by using a second channel, where the second channel is one of the short message channel and the data channel, and the second channel is The first channel is different, and the server is configured to establish a binding relationship between the user account and the first mobile phone number when verifying that the binding request matches the information digest.
2. The method according to claim 1, wherein the terminal generates a binding request, including:

   Receiving, by the terminal, a first triggering operation;

   The terminal acquires the user account according to the first triggering operation;

   The terminal generates the binding request according to the user account.
3. The method according to claim 2, wherein before the terminal generates the binding request according to the user account, the method further includes:

   The terminal acquires operation verification information;

   The terminal generates the binding request according to the user account, including:

   The terminal generates the binding request according to the user account and the operation verification information, where the operation verification information is used to verify the validity of the current binding process.
4. The method according to claim 3, wherein the operation verification information comprises: a ticket and/or a login token;

   The ticket is a ticket corresponding to a binding operation, and the login token is a token generated after the user account is successfully logged in, and the login token has an expiration date.
5. A method for binding a mobile phone number, the method comprising:

   Receiving, by the first channel, a binding request sent by the terminal, where the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data by using a short message of the first mobile phone number, the data channel Is a channel for transmitting data through a mobile communication network or a wireless fidelity network, where the binding request includes a user account, and the first mobile phone number is a mobile phone number corresponding to the terminal;

   Receiving, by the second channel, a message digest of the binding request sent by the terminal; the second channel is one of the short message channel and the data channel, and the second channel is the first channel Different channels;

   Verifying whether the binding request and the information digest of the binding request match;

   When the binding request matches the information digest, the user account and the first mobile phone number are bound.
6. The method according to claim 5, wherein before the establishing a binding relationship between the user account and the first mobile phone number, the method further includes:

   Obtaining operation verification information from the binding request;

   Verifying the validity of the binding process according to the operation verification information;

   When the binding process is valid, the step of establishing a binding relationship between the user account and the first mobile phone number is performed.
7. The method according to claim 6, wherein the operation verification information comprises: a ticket;

   The verifying the validity of the binding process according to the operation verification information, including:

   A ticket that verifies whether the ticket corresponds to a binding operation.
8. The method according to claim 6, wherein the operation verification information comprises: a login token;

   The verifying the validity of the binding process according to the operation verification information, including:

   Verify that the validity time of the login token has expired.
9. A device for binding a mobile phone number, the device comprising:

   a generating module, configured to generate a binding request, where the binding request includes a user account;

   a sending module, configured to send the binding request to the server by using a first channel, where the first channel is one of a short message channel and a data channel; and the short message channel is sent by using a short message of the first mobile phone number Channel, the data channel is a channel for transmitting data through a mobile communication network or a wireless fidelity network;

   The generating module is further configured to generate a message digest corresponding to the binding request;

   The sending module is further configured to send the information digest corresponding to the binding request to the server by using a second channel, where the second channel is another one of the short message channel and the data channel. The server is configured to establish a binding relationship between the user account and the first mobile phone number when verifying that the binding request matches the information digest.
10. The device according to claim 9, wherein the generating module is configured to receive a first triggering operation, acquire the user account according to the first triggering operation, and generate the binding request according to the user account. .
11. The device according to claim 10, wherein the device further comprises:

    An obtaining module, configured to obtain operation verification information;

    The generating module is further configured to generate the binding request according to the user account and the operation verification information, where the operation verification information is used to verify the validity of the current binding process.
12. The apparatus according to claim 11, wherein the operation verification information comprises: a ticket and/or a login token;

    The ticket is a ticket corresponding to a binding operation, and the login token is a token generated after the user account is successfully logged in, and the login token has an expiration date.
13. A device for binding a mobile phone number, the device comprising:

    a receiving module, configured to receive, by using the first channel, a binding request sent by the terminal, where the first channel is one of a short message channel and a data channel; and the short message channel is a channel for sending data by using a short message of the first mobile phone number The data channel is a channel for transmitting data through a mobile communication network or a wireless fidelity network, the binding request includes a user account, and the first mobile phone number is a mobile phone number corresponding to the terminal;

    The receiving module is further configured to receive, by using a second channel, a message digest of the binding request sent by the terminal; the second channel is one of the short message channel and the data channel, and the The second channel is different from the first channel;

    The verification module is further configured to verify whether the binding information of the binding request and the binding request match;

    And a binding module, configured to establish a binding relationship between the user account and the first mobile phone number when the binding request and the information digest match.
14. The device according to claim 13, wherein the device further comprises:

    An obtaining module, configured to obtain operation verification information from the binding request;

    The verification module is further configured to verify the validity of the binding process according to the operation verification information;

    The binding module is further configured to perform the step of establishing a binding relationship between the user account and the first mobile phone number when the current binding process is valid.
15. The device according to claim 14, wherein the operation verification information comprises: a ticket;

    The verification module is configured to verify whether the ticket is a ticket corresponding to the binding operation.
16. The apparatus according to claim 14, wherein the operation verification information comprises: a login token;

    The verification module is configured to verify whether the valid time of the login token is expired.
17. A terminal, comprising: a processor and a memory, wherein the memory stores at least one instruction loaded by the processor and executed to implement any of claims 1 to 4 The method used to bind the mobile phone number.
18. A server, comprising: a processor and a memory, wherein the memory stores at least one instruction loaded by the processor and executed to implement any of claims 5-8 The method used to bind the mobile phone number.
19. A computer storage medium, characterized in that at least one instruction is stored in the storage medium, the instruction being loaded and executed by a processor to implement the binding of a mobile phone number according to any one of claims 1 to 4. method.
20. A computer storage medium, characterized in that the storage medium stores at least one instruction, the instruction being loaded and executed by a processor to implement the binding of a mobile phone number according to any one of claims 5 to 8. method.
21. A system for binding a mobile phone number, characterized in that the system comprises a terminal and a server;

    The terminal comprises the apparatus according to any one of claims 5 to 12, the server comprising the apparatus according to any one of claims 13 to 16;

    or,

    The terminal comprises the terminal of claim 17, the server comprising the server of claim 18.

Images