CN107426711B - Method, device and system for binding or unbinding mobile phone number - Google Patents

Method, device and system for binding or unbinding mobile phone number Download PDF

Info

Publication number
CN107426711B
CN107426711B CN201710559942.7A CN201710559942A CN107426711B CN 107426711 B CN107426711 B CN 107426711B CN 201710559942 A CN201710559942 A CN 201710559942A CN 107426711 B CN107426711 B CN 107426711B
Authority
CN
China
Prior art keywords
mobile phone
phone number
user terminal
verification code
binding
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201710559942.7A
Other languages
Chinese (zh)
Other versions
CN107426711A (en
Inventor
郑灿锐
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Shiyuan Electronics Thecnology Co Ltd
Guangzhou Shirui Electronics Co Ltd
Original Assignee
Guangzhou Shiyuan Electronics Thecnology Co Ltd
Guangzhou Shirui Electronics Co Ltd
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 Guangzhou Shiyuan Electronics Thecnology Co Ltd, Guangzhou Shirui Electronics Co Ltd filed Critical Guangzhou Shiyuan Electronics Thecnology Co Ltd
Priority to CN201710559942.7A priority Critical patent/CN107426711B/en
Publication of CN107426711A publication Critical patent/CN107426711A/en
Application granted granted Critical
Publication of CN107426711B publication Critical patent/CN107426711B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • H04W4/14Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/18Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Abstract

The invention relates to a method, a device and a system for binding or unbinding a mobile phone number. The method comprises the following steps: a first user terminal sends a request for binding or unbinding a first mobile phone number, an application server receives the request and generates a first verification code for the first mobile phone number, and the first verification code is sent to the first user terminal through a non-operator network; the second user terminal sends a verification short message to the application server through an operator network, wherein the verification short message comprises a second verification code; the application server acquires the mobile phone number and a second verification code of the short message sending party according to the verification short message; and comparing the mobile phone number and the second verification code of the short message sender with the mobile phone number to be bound or unbound and the first verification code respectively, and if the mobile phone number to be bound or unbound and the first verification code are consistent, binding or unbinding the mobile phone number to be bound or unbound. The invention can solve the problem that the mobile phone number cannot be bound or unbound caused by the unsubscribing factor of the user.

Description

Method, device and system for binding or unbinding mobile phone number
Technical Field
The invention relates to the technical field of mobile terminals, in particular to a method, a device and a system for binding or unbinding a mobile phone number.
Background
In the era of mobile internet, there are situations where multiple application accounts bind or unbind mobile phone numbers, for example: the websites or application software which need to be logged in, such as banks, payment treasures, WeChat and the like, need to be bound or unbound between the user account and the mobile phone number.
The existing application account number is bound with a mobile phone number in the following mode: the user sends the mobile phone number to be bound to the application account management server; the application account management server generates a random verification code and sends the random verification code to a mobile phone number user to be bound through a mobile operator network of a third party; the user receives the verification short message and sends the verification code back to the application account management server; the application account management server records the association relationship between the user account and the mobile phone number; and the application account management server sends the service identification code and the mobile phone number to an operator server of the third party, and the operator server of the third party associates the mobile phone number of the user with the bound application service identification code. The process of unbinding a phone number is similar to the process of binding a phone number.
However, if the user requests the mobile operator of the third party to unsubscribe the relevant application service message, the operator server of the third party will not send the verification code generated by the application service to the user any more, and the user cannot receive the verification code; because the user cannot correctly receive the verification code, the binding or unbinding of the related application account and the mobile phone number cannot be realized.
Disclosure of Invention
Based on the method, the device and the system for binding or unbinding the mobile phone number, the problem that the mobile phone number cannot be bound or unbound due to the unsubscribing factor of the user can be solved.
The invention comprises the following scheme:
a method of binding or unbinding a mobile number, comprising:
receiving a request of a first user terminal for binding or unbinding a mobile phone number, and obtaining a first mobile phone number to be bound or unbound according to the request;
generating a first verification code for the first mobile phone number, and sending the first verification code to the first user terminal through a non-operator network;
receiving a verification short message sent by a second user terminal through an operator network, wherein the verification short message comprises a second verification code; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message;
and comparing the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively, and binding or unbinding the first mobile phone number if the comparison results are consistent.
A method for requesting to bind or unbind a mobile phone number, comprising:
sending a request for binding or unbinding the mobile phone number, wherein the request information comprises a first mobile phone number to be bound or unbound;
receiving a first verification code sent by an application server through a non-operator network, wherein the first verification code is a verification code generated by the application server for binding or unbinding the first mobile phone number;
and sending a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code.
A method of binding or unbinding a mobile number, comprising:
a first user terminal sends a request for binding or unbinding a mobile phone number, wherein the request comprises a first mobile phone number to be bound or unbound;
the application server receives the request, generates a first verification code for the first mobile phone number, and sends the first verification code to the first user terminal through a non-operator network;
the second user terminal sends a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code;
the application server acquires the mobile phone number of the short message sender and the second verification code according to the verification short message; and comparing the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively, and if the mobile phone number and the second verification code are consistent, binding or unbinding the first mobile phone number.
An apparatus for binding or unbinding a mobile number, comprising:
the request receiving module is used for receiving a request of binding or unbinding the mobile phone number by the first user terminal and acquiring the mobile phone number to be bound or unbound;
a verification code returning module, configured to generate a first verification code for the first mobile phone number, and send the first verification code to the first user terminal through a non-operator network;
the short message receiving and identifying module is used for receiving a verification short message sent by a second user terminal through an operator network, wherein the verification short message comprises a second verification code; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message; and the number of the first and second groups,
and the binding or unbinding control module is used for comparing the mobile phone number and the second verification code of the short message sending party with the first mobile phone number and the first verification code respectively, and binding or unbinding the first mobile phone number if the comparison results are consistent.
An apparatus for requesting to bind or unbind a phone number, comprising:
the request initiating module is used for sending a request for binding or unbinding the mobile phone number, and the request information comprises a first mobile phone number to be bound or unbound;
the verification code receiving module is used for receiving a first verification code sent by an application server through a non-operator network, wherein the first verification code is a verification code generated by the application server for binding or unbinding the first mobile phone number; and the number of the first and second groups,
and the short message sending module is used for sending a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code.
A system for binding or unbinding a mobile phone number comprises a first user terminal, a second user terminal and an application server,
the first user terminal includes:
the request initiating module is used for sending a request for binding or unbinding the mobile phone number to the application server, wherein the request comprises a first mobile phone number to be bound or unbound; and the number of the first and second groups,
the verification code receiving module is used for receiving a first verification code sent by the application server through a non-operator network;
the second user terminal includes:
the short message sending module is used for sending a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code;
the application server includes:
the request receiving module is used for receiving a request of binding or unbinding the mobile phone number by the first user terminal and acquiring the mobile phone number to be bound or unbound;
a verification code returning module, configured to generate a first verification code for the first mobile phone number, and send the first verification code to the first user terminal through a non-operator network;
the short message receiving and identifying module is used for receiving a verification short message sent by a second user terminal through an operator network, wherein the verification short message comprises a second verification code; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message; and the number of the first and second groups,
and the binding or unbinding control module is used for comparing the mobile phone number and the second verification code of the short message sending party with the first mobile phone number and the first verification code respectively, and binding or unbinding the first mobile phone number if the comparison results are consistent.
A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, carries out the steps of any of the methods described above.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of any of the methods described above when executing the program.
According to the technical scheme, a first user terminal sends a request for binding or unbinding a first mobile phone number, an application server receives the request, generates a first verification code for the first mobile phone number and sends the first verification code to the first user terminal through a non-operator network; the second user terminal sends a verification short message to the application server through an operator network, wherein the verification short message comprises a second verification code; the application server acquires the mobile phone number and a second verification code of the short message sending party according to the verification short message; and binding or unbinding the first mobile phone number according to the comparison result between the mobile phone number of the short message sender and the first mobile phone number and the comparison result between the second verification code and the first verification code. Therefore, the problem that the mobile phone number cannot be bound or unbound caused by the user unsubscribing the application service can be solved.
Drawings
Fig. 1 is a schematic flow chart of a method of binding or unbinding a mobile phone number according to an embodiment;
fig. 2 is an application scenario diagram of a method for binding or unbinding a mobile phone number according to an embodiment;
fig. 3 is a schematic flow chart of a method for binding or unbinding a mobile phone number at an application server side according to an embodiment;
fig. 4 is a schematic flow chart of a method for requesting, by a user terminal, to bind or unbind a mobile phone number according to an embodiment;
fig. 5 is a schematic structural diagram of a system for binding or unbinding a mobile phone number according to an embodiment;
fig. 6 is a schematic structural diagram of an apparatus for binding or unbinding a mobile phone number according to an embodiment;
fig. 7 is a schematic structural diagram of an apparatus for requesting to bind or unbind a mobile phone number according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Although the steps in the present invention are arranged by using reference numbers, the order of the steps is not limited, and the relative order of the steps can be adjusted unless the order of the steps is explicitly stated or other steps are required for the execution of a certain step.
Fig. 1 is a schematic flow chart of a method of binding or unbinding a mobile phone number according to an embodiment; in this embodiment, the subject involved in the method includes an application server, a user terminal and an operator server, where the application server may be any application server that requires a user to bind or unbind a mobile phone number, including but not limited to a bank, a pay bank, a WeChat, and the like.
With reference to fig. 1 and fig. 2, the method for binding or unbinding a mobile phone number in this embodiment includes the steps of:
and S11, the first user terminal sends a request for binding or unbinding the mobile phone number, wherein the request comprises the first mobile phone number to be bound or unbound.
And S12, the application server receives the request, generates a first verification code for the first mobile phone number, and sends the first verification code to the first user terminal through a non-operator network.
And S13, the second user terminal sends a verification short message to the application server through the operator network according to the first verification code, wherein the verification short message comprises a second verification code.
The first user terminal can be a terminal such as a mobile phone and the like which is accessed to an operator network, namely a terminal capable of communicating with an operator server, or a terminal such as a computer and the like which is connected with an application server network; the second user terminal must then fulfil the conditions for accessing the operator network. Therefore, when the first user terminal is a type of terminal, the first user terminal and the second user terminal can be the same terminal; when the first user terminal is a class ii terminal, it may be a different terminal from the second user terminal. In a preferred embodiment, the first user terminal and the second user terminal are both a class terminal and are the same terminal; for example, both are mobile phones.
S14, the application server obtains the mobile phone number of the short message sender and the second verification code according to the verification short message; and comparing the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively, and if the mobile phone number and the second verification code are consistent, binding or unbinding the first mobile phone number.
In general, since the verification short message is sent by the second user terminal, the mobile phone number of the short message sender may be understood as the mobile phone number of the second user terminal. Of course, if the second user terminal corresponds to more than two mobile phone numbers, the mobile phone number of the short message sender needs to be specifically identified according to the verification short message.
In the process of binding or unbinding the mobile phone number, the verification code (i.e. the first verification code) generated by the application server corresponds to the mobile phone number to be bound or unbound, so that whether the verification code returned by the user is consistent with the first verification code or not is checked, and meanwhile, whether the mobile phone number of the verification short message sent by the user through the second user terminal is consistent with the mobile phone number to be bound or unbound is also checked. And only when the two are consistent, indicating that the valid user returns correct verification code information, and the condition for binding or unbinding the mobile phone number is met, so that the association relationship between the mobile phone number and the application account is established or removed, and the binding or unbinding is successful.
In step S11, if the first user terminal is a terminal of the aforementioned type, the request for binding or unbinding the mobile phone number may be sent to the application server through the carrier network (usually, the application server is in communication with the carrier server), or the request for binding or unbinding the mobile phone number may be sent to the application server through the non-carrier network. If the first user terminal is the above-mentioned two types of terminals, the request for binding or unbinding the mobile phone number is generally sent to the application server through the non-operator network, for example, the request for binding or unbinding the mobile phone number is sent to the application server through the internet/internet through a button such as "end binding or unbinding the mobile phone number" in the relevant web page.
For example: if the first user terminal and the second user terminal are the same mobile phone, entering a bound mobile phone number interface, inputting a mobile phone number, clicking the bound mobile phone number, receiving information containing the verification code and the application service number (namely the application service identification number), and then, displaying a button to prompt that the verification code is sent to the server; and if the user clicks the button, the user enters a short message interface, the receiver is the application service number, and the content of the short message is the received verification code. Then the user clicks to send the short message, the short message is sent to the application server through the operator network, then the mobile phone returns to the binding mobile phone number interface, and the prompt message of successful binding or failed binding can be seen after a while.
For example: if the first user terminal is the second-class terminal and the second user terminal is a mobile phone, the user enters a mobile phone binding interface of a web or an application program based on the first user terminal, inputs a mobile phone number, clicks the binding mobile phone number, prompts the interface to send the XXX authentication code to the AAA, and uses the mobile phone to send a short message containing the XXX authentication code to the AAA of a receiver. And then, a prompt of successful binding or failed binding can be seen in a short time on a binding mobile phone interface of the first user terminal.
In an optional embodiment, the application server generates only one first verification code for each mobile phone number to be bound or unbound. The first verification code may be a digital verification code, and the number of bits of the digital verification code may be determined on a case-by-case basis, such as a 4-bit or 6-bit digital verification code. In addition, the first verification code may also be other forms of verification codes, such as character form, character + number form, literal form, etc., which may be determined on a case-by-case basis. Because the application server sends the verification code to the first user terminal through the non-operator network, the user terminal cannot normally receive the first verification code due to the interference of the quality of the operator network or the previous unsubscription operation of the user.
In an optional embodiment, the application service identification number is registered in the operator server in advance for the application server, and the application service identification number is used for identifying different application servers by the operator server. Correspondingly, the step S12 further includes that the application server sends the application service identification number, registered by the application server in the operator server, to the first user terminal through the non-operator network. Accordingly, in step S13, the second user terminal may send the verification short message to the application server through the operator network based on the application service identification number.
In an optional embodiment, the first user terminal and the second user terminal are both terminals capable of accessing to the operator network, and are the same terminal. At this time, the implementation manner of sending a verification short message to the operator server by the second user terminal according to the first verification code may be: and after receiving the first verification code and the application service identification number of the application server, the second user terminal automatically acquires the first verification code and the application service identification number, automatically fills the first verification code into a short message content frame after entering a short message editing interface, and automatically fills the application service identification number into an item frame of a short message receiving party. And then sending the short message according to the user operation. By the method, the operation of the user can be simplified, and the binding or unbinding failure caused by the input error of the user is also avoided. Preferably, after receiving the first verification code, the second user terminal performs the following steps: and detecting and confirming the user operation of sending the verification code, and entering a short message editing interface when detecting the user operation. When the user confirms that the verification short message needs to be sent, the second user terminal enters a short message editing interface and carries out the automatic filling; otherwise, the short message editing interface is not entered, and the automatic filling is not performed; therefore, misoperation can be prevented, and user information is leaked.
In an optional embodiment, after the application server binds or unbinds the first mobile phone number, the application server further sends a message that the binding or unbinding is successful to the first user terminal through a non-operator network. In addition, the method for binding or unbinding the mobile phone number further comprises the following steps: after the application server compares the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively, if any comparison result is inconsistent, a message of binding or unbinding failure is sent to the first user terminal through a non-operator network. Preferably, the message contains the reason for the binding or unbinding failure, such as: wrong verification code, overtime, inconsistent mobile phone numbers and the like. Since the second user terminal does not receive the reply short message returned by the operator server after sending the verification short message, the application server is required to actively return the state information of the mobile phone number binding or unbinding to the first user terminal so as to inform the user of the result of the binding or unbinding request.
In an optional embodiment, the method for binding or unbinding the mobile phone number further includes, after the first mobile phone number is bound or unbound, sending the first mobile phone number, the application service identification number of the application server, and the state information of this binding or unbound to an operator server through the application server, so that the operator server associates the first mobile phone number with the application service identification number, or the operator server disassociates the first mobile phone number from the application service identification number. Therefore, the user can find back the password or the user name through the mobile phone number, and other users can be prevented from stealing the information of the user through the mobile phone number after the user stops using the mobile phone number.
By the method of the embodiment, the first user terminal sends a request for binding or unbinding the first mobile phone number, the application server receives the request, generates the first verification code for the first mobile phone number, and sends the first verification code to the first user terminal through the non-operator network; the second user terminal sends a verification short message to the application server through an operator network, wherein the verification short message comprises a second verification code; the application server acquires the mobile phone number and a second verification code of the short message sending party according to the verification short message; and comparing the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively, and if the mobile phone number and the second verification code are consistent, binding or unbinding the first mobile phone number. Therefore, the problem that the mobile phone number cannot be bound or unbound caused by the user unsubscribing factor can be solved. In addition, for an application server provider, short message cost does not need to be paid, and when a large number of mobile phone numbers are bound or unbound, the cost is saved.
FIG. 3 is a schematic flow chart diagram of a method of binding or unbinding a mobile number according to another embodiment; in this embodiment, the application server side is taken as an example for explanation, and the application server may be any application server that requires a user to bind or unbind a mobile phone number function, including but not limited to a bank, a pay bank, a WeChat, and the like.
As shown in fig. 3, the method for binding or unbinding a mobile phone number in this embodiment includes the steps of:
and S31, receiving a request of the first user terminal for binding or unbinding the mobile phone number, and obtaining the first mobile phone number to be bound or unbound according to the request.
And S32, generating a first verification code for the first mobile phone number, and sending the first verification code to the first user terminal through a non-operator network.
S33, receiving a verification short message sent by a second user terminal through an operator network, wherein the verification short message comprises a second verification code; and obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message.
In this embodiment, the first user terminal may be a terminal such as a mobile phone that can access an operator network, that is, a first-class terminal that can communicate with an operator server, or a second-class terminal that is connected to an application server network, such as a computer; the second user terminal must then fulfil the conditions for accessing the operator network. When the first user terminal is a terminal of one type, the first user terminal and the second user terminal can be the same terminal; when the first user terminal is a second type terminal, it is generally different from the second user terminal. In a preferred embodiment, the first user terminal and the second user terminal are both a type of terminal and are the same terminal, such as a mobile phone.
The application server is connected with the operator server in a communication mode, so that the application server can receive the verification short message sent by the second user terminal through the operator network. The verification short message may be sent by the first user terminal in step S31; or may be transmitted by other second user terminals.
It is to be understood that the second verification code may be different from the first verification code or the first verification code; the mobile phone number of the short message sending party can be a first mobile phone number to be bound or unbound, and can also be other mobile phone numbers.
S34, comparing the mobile phone number and the second identifying code of the short message sender with the first mobile phone number and the first identifying code respectively, and binding or unbinding the first mobile phone number if the comparison result is consistent.
In this step, the mobile phone number of the short message sender is compared with the first mobile phone number, the second verification code is compared with the first verification code, and if the two comparison results are consistent, the first mobile phone number is bound or unbound. Otherwise, the application server may send a binding or unbinding failure message to the first user terminal through the non-operator network when the mobile phone number binding or unbinding fails.
In an optional embodiment, the application server generates only one first verification code for each mobile phone number to be bound or unbound. The first verification code may be a digital verification code, and the number of bits of the digital verification code may be determined on a case-by-case basis, such as a 4-bit or 6-bit digital verification code. In addition, the first verification code may also be other forms of verification codes, such as character form, character + number form, literal form, etc., which may be determined on a case-by-case basis. The application server sends the verification code to the first user terminal through the non-operator network, so that the user terminal is not interfered by the quality of the operator network or the first verification code cannot be normally received due to the user's previous unsubscription operation.
In an optional embodiment, the binding the first mobile phone number refers to: establishing association between the first mobile phone number and a user account managed by an application server, and storing association information; the unbinding of the first mobile phone number refers to: and releasing the association between the first mobile phone number and the user account managed by the application server, and deleting the corresponding association information. Preferably, after the application server binds or unbinds the first mobile phone number, the application server further sends a message that the binding or unbinding is successful to the first user terminal through a non-operator network.
In an optional embodiment, the application service identification number registered by the application server in the operator server can be preset. Correspondingly, the step S32 of sending the first verification code to the first user terminal through the non-operator network may further include: sending the application service identification number I to the first user terminal through a non-operator network; the step S13 may include receiving, by the operator network, the verification short message sent by the second user terminal based on the application service identification number.
By the method for binding or unbinding the mobile phone number in the embodiment, the application server generates a first verification code after receiving a request for binding or unbinding the mobile phone number from the user terminal, and sends the first verification code to the first user terminal through the non-operator network; then, receiving a verification short message sent by a second user terminal through an operator network to obtain a mobile phone number of a short message sending party and the second verification code; and comparing the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively to judge whether to bind or unbind the first mobile phone number. Based on the method for binding or unbinding the mobile phone number in the embodiment, the user terminal can normally receive the verification code, and the application server side can be ensured to normally execute the binding or unbinding of the mobile phone number. In addition, for an application server provider, short message cost does not need to be paid, and when a large number of mobile phone numbers are bound or unbound, the cost is saved.
Fig. 4 is a flowchart illustrating a method for requesting to bind or unbind a mobile phone number according to an embodiment of the present invention, where in this embodiment, corresponding to the case where the first user terminal and the second user terminal are the same terminal in the first embodiment, the method for requesting to bind or unbind a mobile phone number according to this embodiment is described by taking the same terminal as an example, where the same terminal is a terminal that can access an operator network, such as a mobile phone and a tablet computer, and the same terminal can also be connected to an application server network.
As shown in fig. 4, the method for requesting to bind or unbind a mobile phone number in this embodiment includes the steps of:
s41, sending a request for binding or unbinding the mobile phone number, wherein the request information comprises the first mobile phone number to be bound or unbound.
And S42, receiving a first verification code sent by the application server through the non-operator network, wherein the first verification code is generated by the application server for binding or unbinding the first mobile phone number.
The application server can be any application server which needs a user to bind or unbind a mobile phone number, including but not limited to banks, payment treasures, WeChat and the like. At an application server end, the first verification code and the first mobile phone number have a corresponding relation.
S43, sending a verification short message to the application server through the operator network according to the first verification code, wherein the verification short message comprises a second verification code.
In an optional embodiment, after sending the request for binding or unbinding the mobile phone number, the user terminal further includes: and receiving an application service identification number, which is sent by an application server and registered by the application server in an operator server, through a non-operator network. Correspondingly, the sending of the verification short message to the application server through the operator network according to the first verification code specifically includes: and after receiving the first verification code and the application service identification number, acquiring the first verification code and the application service identification number, automatically filling the first verification code into a short message content frame after the user terminal enters a short message editing interface, and automatically filling the application service identification number into an item frame of a short message receiver. Preferably, after receiving the first verification code and the application service identification number, the user terminal detects a user operation for confirming sending of the verification code, and enters a short message editing interface when detecting the corresponding user operation. When the user confirms that the verification short message needs to be sent, the user enters a short message editing interface and performs the automatic filling; otherwise, the short message editing interface is not entered, and the automatic filling is not performed; therefore, misoperation can be prevented, and user information is leaked.
In an alternative embodiment, the method further comprises the steps of: receiving binding or unbinding state information sent by the application server through a non-operator network; the binding or unbinding state information includes information that binding or unbinding is successful, or binding or unbinding failure information. The application server obtains the mobile phone number of the short message sending party and the second verification code according to the received verification short message, compares the mobile phone number of the short message sending party and the second verification code with the first mobile phone number and the first verification code respectively, binds or unbinds the first mobile phone number if the mobile phone number of the short message sending party and the second verification code are consistent with each other, and returns a message of successful binding or unbinding to the user terminal through the non-operator network. If any comparison result is inconsistent, the binding or unbinding of the mobile phone number is not executed, a binding or unbinding failure message is returned to the user terminal through the non-operator network, and a failure reason can be returned at the same time.
By the method for requesting to bind or unbind the mobile phone number according to the embodiment, after the user terminal sends the request for binding or unbinding the first mobile phone number to the application server, the user terminal can receive the first verification code sent by the application server through the non-operator network, wherein the first verification code is the verification code generated by the application server for binding or unbinding the first mobile phone number; and then, sending a verification short message to the application server through the operator network, wherein the verification short message contains a second verification code, and receiving the binding or unbinding state information returned by the application server through the non-operator network. Because the operator server cannot send information to the user terminal due to the user unsubscribe operation, but the user terminal can send information to the operator server, the user can normally receive the verification code generated by the application server through the method for requesting the binding or unbinding of the mobile phone number of the user terminal in the embodiment, and the step of normally executing the binding or unbinding of the mobile phone number by the application server side is further ensured.
It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present invention is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present invention.
Based on the same idea as the method for binding or unbinding the mobile phone number in the embodiment, the invention also provides a device for binding or unbinding the mobile phone number, and the device can be used for executing the method for binding or unbinding the mobile phone number. For convenience of description, in the structural schematic diagram of the embodiment of the apparatus for binding or unbinding the mobile phone number, only the part related to the embodiment of the present invention is shown, and those skilled in the art will understand that the illustrated structure does not constitute a limitation to the apparatus, and may include more or less components than those illustrated, or combine some components, or arrange different components.
Fig. 5 is a schematic structural diagram of a system for binding or unbinding a mobile phone number according to an embodiment of the present invention, and as shown in fig. 5, the system for binding or unbinding a mobile phone number according to the embodiment includes: a first user terminal 10, a second user terminal 20 and an application server 30,
the first user terminal 10 comprises:
a request initiating module, configured to send a request for binding or unbinding a mobile phone number to the application server 30, where the request includes a first mobile phone number to be bound or unbound; and the number of the first and second groups,
and an identifying code receiving module, configured to receive, through a non-operator network, the first identifying code sent by the application server 30.
The second user terminal 20 includes:
a short message sending module, configured to send a verification short message to the application server 30 through an operator network according to the first verification code, where the verification short message includes a second verification code;
the application server 30 includes:
a request receiving module, configured to receive a request for binding or unbinding a mobile phone number by the first user terminal 10, and acquire a mobile phone number to be bound or unbound;
a verification code returning module, configured to generate a first verification code for the first mobile phone number, and send the first verification code to the first user terminal 10 through a non-operator network;
the short message receiving and identifying module is used for receiving a verification short message sent by a second user terminal through an operator network, wherein the verification short message comprises a second verification code; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message; and the number of the first and second groups,
and the binding or unbinding control module is used for comparing the mobile phone number and the second verification code of the short message sending party with the first mobile phone number and the first verification code respectively, and binding or unbinding the first mobile phone number if the comparison results are consistent.
In an optional embodiment, in the system for binding or unbinding a mobile phone number, the first user terminal 10 is a terminal, such as a computer, connected to the application server 30 via a network; the second user terminal 20 is a terminal, such as a handset, that is capable of accessing the operator network.
In another alternative embodiment, in the system for binding or unbinding the phone number, the first user terminal 10 and the second user terminal 20 are the same terminal, and can access to the operator network and can be connected to the application server 30 through a network. For example, the first user terminal 10 and the second user terminal 20 refer to the same mobile phone.
In an optional embodiment, in the application server 30, the binding or unbinding control module is further configured to send a message that the binding or unbinding is successful to the first user terminal 10 through a non-operator network after the first mobile phone number is bound or unbound; and a message for sending a binding or unbinding failure to the first user terminal 10 through a non-operator network if any comparison result is inconsistent.
Fig. 6 is a schematic structural diagram of a device for binding or unbinding a mobile phone number according to an embodiment of the present invention, where the device can be applied to any application server that needs to bind or unbind a mobile phone number. As shown in fig. 6, the apparatus for binding or unbinding a mobile phone number according to this embodiment includes:
a request receiving module 601, configured to receive a request for binding or unbinding a mobile phone number by a first user terminal, and acquire a mobile phone number to be bound or unbound;
a verification code returning module 602, configured to generate a first verification code for the first mobile phone number, and send the first verification code to the first user terminal through a non-operator network;
a short message receiving and identifying module 603, configured to receive, through an operator network, a verification short message sent by a second user terminal, where the verification short message includes a second verification code; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message; and the number of the first and second groups,
and a binding or unbinding control module 604, configured to compare the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code, respectively, and bind or unbind the first mobile phone number if the comparison results are consistent.
In an optional embodiment, the binding or unbinding control module 604 is further configured to send a message that the binding or unbinding is successful to the first user terminal through a non-operator network after the first mobile phone number is bound or unbound.
Optionally, the binding or unbinding control module 604 is further configured to send a binding or unbinding failure message to the first user terminal through a non-operator network if any comparison result is inconsistent.
Fig. 7 is a schematic structural diagram of a device for requesting to bind or unbind a mobile phone number according to an embodiment of the present invention, where the device may be applied to a terminal capable of accessing an operator network. As shown in fig. 7, the apparatus for requesting to bind or unbind a mobile phone number according to this embodiment includes:
a request initiating module 701, configured to send a request for binding or unbinding a mobile phone number, where the request information includes a first mobile phone number to be bound or unbound;
a verification code receiving module 702, configured to receive, through a non-operator network, a first verification code sent by an application server, where the first verification code is a verification code generated by the application server for binding or unbinding the first mobile phone number; and the number of the first and second groups,
the short message sending module 703 is configured to send a verification short message to the application server through an operator network according to the first verification code, where the verification short message includes a second verification code.
In an optional embodiment, the verification code receiving module 702 is further configured to receive, through a non-operator network, an application service identification number, sent by an application server, registered by the application server at an operator server. The short message sending module 703 is configured to obtain the first verification code and the application service identification number after receiving the first verification code and the application service identification number, automatically fill the first verification code into a short message content box after entering a short message editing interface, and automatically fill the application service identification number into an item box of a short message recipient.
Optionally, the apparatus for requesting to bind or unbind a mobile phone number further includes: the binding or unbinding state receiving module is used for receiving the binding or unbinding state information sent by the application server through the non-operator network; the binding or unbinding state information includes binding or unbinding success or binding or unbinding failure.
It should be noted that in the embodiment of the system/apparatus for binding or unbinding a mobile phone number in the foregoing example, because the contents of information interaction, execution process, and the like between the modules are based on the same concept as the foregoing method embodiment of the present invention, the technical effect brought by the embodiment is the same as the foregoing method embodiment of the present invention, and specific contents may refer to the description in the method embodiment of the present invention, and are not described herein again.
In addition, in the above embodiment of the system/apparatus for binding or unbinding a mobile phone number, the logical division of each program module is only an example, and in practical applications, the above function allocation may be completed by different program modules according to needs, for example, due to the configuration requirements of corresponding hardware or the convenience of implementation of software, that is, the internal structure of the system/apparatus for binding or unbinding a mobile phone number is divided into different program modules to complete all or part of the above described functions.
It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by a computer program, which is stored in a computer readable storage medium and sold or used as a stand-alone product. The program, when executed, may perform all or a portion of the steps of the embodiments of the methods described above. In addition, the storage medium may be provided in a computer device, and the computer device further includes a processor, and when the processor executes the program in the storage medium, all or part of the steps of the embodiments of the methods described above can be implemented. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments. It will be understood that the terms "first," "second," and the like as used herein, are used herein to distinguish one object from another, but the objects are not limited by the terms; in addition, the case where "first" and "second" are directed to the same object is not excluded.
The above-described examples merely represent several embodiments of the present invention and should not be construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (14)

1. A method for binding or unbinding a mobile phone number, comprising:
receiving a request of a first user terminal for binding or unbinding a mobile phone number, and obtaining a first mobile phone number to be bound or unbound according to the request;
generating a first verification code for the first mobile phone number, and sending the first verification code to the first user terminal through a non-operator network;
receiving a verification short message sent by a second user terminal through an operator network, wherein the verification short message comprises a second verification code; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message;
comparing the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively, and binding or unbinding the first mobile phone number if the comparison results are consistent; if any comparison result is inconsistent, sending a binding failure or unbinding failure message to the first user terminal through a non-operator network, wherein the binding failure or unbinding failure message contains failure reason information;
after the first mobile phone number is bound or unbound, sending a message of successful binding or unbinding to the first user terminal through a non-operator network; sending the first mobile phone number, the application service identification number of the application server and the current binding or unbinding state information to an operator server together so that the operator server end associates the first mobile phone number with the application service identification number or releases the association between the first mobile phone number and the application service identification number;
the first user terminal and the second user terminal are different terminals, and the first user terminal is a terminal at least accessed to a non-operator network; the second user terminal is a terminal accessing to an operator network.
2. The method of binding or unbinding the mobile number as in claim 1, wherein binding or unbinding the first mobile number comprises: establishing association between the first mobile phone number and a user account managed by an application server, and storing association information; or, the first mobile phone number is disassociated from the user account managed by the application server, and corresponding association information is deleted.
3. The method for binding or unbinding the phone number according to claim 1 or 2, wherein the step of sending the first verification code to the first user terminal through the non-operator network further comprises:
and sending the application service identification number registered by the application server in the operator server to the first user terminal through a non-operator network.
4. A method for requesting to bind or unbind a mobile phone number, comprising:
a first user terminal sends a request for binding or unbinding a mobile phone number, wherein the request information comprises a first mobile phone number to be bound or unbound;
a first user terminal receives a first verification code sent by an application server through a non-operator network, wherein the first verification code is a verification code generated by the application server for binding or unbinding the first mobile phone number;
the first user terminal sends a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code and is used for triggering the application server to compare the mobile phone number and the second verification code of a short message sender with the first mobile phone number and the first verification code respectively, and if the comparison result is consistent, the first mobile phone number is bound or unbound; if any comparison result is inconsistent, sending a binding failure or unbinding failure message to the first user terminal through a non-operator network, wherein the binding failure or unbinding failure message contains failure reason information; after the first mobile phone number is bound or unbound, the first mobile phone number, the application service identification number of the application server and the current binding or unbound state information are sent to an operator server together, so that the operator server end associates the first mobile phone number with the application service identification number or releases the association of the first mobile phone number and the application service identification number;
the first user terminal receives a successful binding or unbinding message sent by the application server through a non-operator network, wherein the successful binding or unbinding message is sent by the application server after the first mobile phone number is bound or unbound; or, receiving a binding failure or unbinding failure message sent by the application server through a non-operator network;
the first user terminal is a terminal at least accessed to a non-operator network.
5. The method for requesting the binding or unbinding of the mobile phone number as claimed in claim 4, further comprising, after sending the request for binding or unbinding the mobile phone number:
receiving an application service identification number which is sent by an application server and registered by the application server in an operator server through a non-operator network;
the sending a verification short message to the application server through an operator network according to the first verification code comprises:
after receiving the first verification code and the application service identification number, acquiring the first verification code and the application service identification number, automatically filling the first verification code into a short message content frame after entering a short message editing interface, and automatically filling the application service identification number into an item frame of a short message receiving party.
6. The method of claim 5, wherein after receiving the first authentication code, performing the following steps:
and detecting and confirming the user operation of sending the verification code, and entering a short message editing interface when detecting the user operation.
7. A method for binding or unbinding a mobile phone number, comprising:
a first user terminal sends a request for binding or unbinding a mobile phone number, wherein the request comprises a first mobile phone number to be bound or unbound;
the application server receives the request, generates a first verification code for the first mobile phone number, and sends the first verification code to the first user terminal through a non-operator network;
the second user terminal sends a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code;
the application server acquires the mobile phone number of the short message sender and the second verification code according to the verification short message; comparing the mobile phone number and the second verification code of the short message sender with the first mobile phone number and the first verification code respectively, and if the mobile phone number and the second verification code are consistent, binding or unbinding the first mobile phone number; if any comparison result is inconsistent, sending a binding failure or unbinding failure message to the first user terminal through a non-operator network, wherein the binding failure or unbinding failure message contains failure reason information; after the first mobile phone number is bound or unbound, sending a message of successful binding or unbinding to the first user terminal through a non-operator network; sending the first mobile phone number, the application service identification number of the application server and the current binding or unbinding state information to an operator server together so that the operator server end associates the first mobile phone number with the application service identification number or releases the association between the first mobile phone number and the application service identification number;
the first user terminal and the second user terminal are different terminals or the same terminal, and the first user terminal is a terminal at least accessed to a non-operator network; the second user terminal is a terminal accessing to an operator network.
8. The method of binding or unbinding the mobile phone number as claimed in claim 7, wherein the application server sends the first authentication code and the application service identification number one registered by the application server at the operator server to the first user terminal through a non-operator network.
9. The method of claim 8, wherein when the first user terminal and the second user terminal are the same terminal, the second user terminal sends a verification short message to the operator server according to the first verification code, comprising:
and after receiving the first verification code and the application service identification number, the second user terminal acquires the first verification code and the application service identification number, automatically fills the first verification code into a short message content box and automatically fills the application service identification number into an item box of a short message receiving party after entering a short message editing interface.
10. An apparatus for binding or unbinding a mobile phone number, comprising:
the request receiving module is used for receiving a request of binding or unbinding the mobile phone number of the first user terminal and acquiring the first mobile phone number to be bound or unbound;
a verification code returning module, configured to generate a first verification code for the first mobile phone number, and send the first verification code to the first user terminal through a non-operator network;
the short message receiving and identifying module is used for receiving a verification short message sent by a second user terminal through an operator network, wherein the verification short message comprises a second verification code; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message; and the number of the first and second groups,
the binding or unbinding control module is used for comparing the mobile phone number and the second verification code of the short message sending party with the first mobile phone number and the first verification code respectively, and binding or unbinding the first mobile phone number if the comparison results are consistent; the first user terminal is further configured to send a binding or unbinding failure message to the first user terminal through a non-operator network if any comparison result is inconsistent, where the binding failure or unbinding failure message includes failure cause information;
the binding or unbinding control module is further configured to send a message that the binding or unbinding is successful to the first user terminal through a non-operator network after the first mobile phone number is bound or unbound; sending the first mobile phone number, the application service identification number of the application server and the current binding or unbinding state information to an operator server together so that the operator server end associates the first mobile phone number with the application service identification number or releases the association between the first mobile phone number and the application service identification number;
the first user terminal and the second user terminal are different terminals, and the first user terminal is a terminal at least accessed to a non-operator network; the second user terminal is a terminal accessing to an operator network.
11. An apparatus for requesting to bind or unbind a phone number, comprising:
the request initiating module is used for enabling the first user terminal to send a request for binding or unbinding the mobile phone number, and the request information comprises the first mobile phone number to be bound or unbound;
the verification code receiving module is used for enabling the first user terminal to receive a first verification code sent by an application server through a non-operator network, wherein the first verification code is a verification code generated by the application server for binding or unbinding the first mobile phone number; and the number of the first and second groups,
the short message sending module is used for enabling the first user terminal to send a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code and is used for triggering the application server to compare the mobile phone number and the second verification code of the short message sending party with the first mobile phone number and the first verification code respectively, if the comparison results are consistent, the first mobile phone number is bound or unbound, if any comparison result is inconsistent, a binding or unbinding failure message is sent to the first user terminal through a non-operator network, and the binding failure or unbinding failure message comprises failure reason information; after the first mobile phone number is bound or unbound, the first mobile phone number, the application service identification number of the application server and the current binding or unbound state information are sent to an operator server together, so that the operator server end associates the first mobile phone number with the application service identification number or releases the association between the first mobile phone number and the application service identification number;
a result receiving module, configured to receive, through a non-operator network, a message that is sent by the application server and that is successfully bound or unbound, where the message that is successfully bound or unbound is sent by the application server after the first mobile phone number is bound or unbound;
the first user terminal is a terminal at least accessed to a non-operator network.
12. A system for binding or unbinding a mobile phone number is characterized by comprising a first user terminal, a second user terminal and an application server, wherein the first user terminal and the second user terminal are different terminals or the same terminal, and the first user terminal is a terminal at least accessed to a non-operator network; the second user terminal is a terminal accessed to an operator network;
the first user terminal includes:
the request initiating module is used for sending a request for binding or unbinding the mobile phone number to the application server, wherein the request comprises a first mobile phone number to be bound or unbound; and the number of the first and second groups,
the verification code receiving module is used for receiving a first verification code sent by the application server through a non-operator network;
the second user terminal includes:
the short message sending module is used for sending a verification short message to the application server through an operator network according to the first verification code, wherein the verification short message comprises a second verification code;
the application server includes:
the request receiving module is used for receiving a request of binding or unbinding the mobile phone number by the first user terminal and acquiring the mobile phone number to be bound or unbound;
a verification code returning module, configured to generate a first verification code for the first mobile phone number, and send the first verification code to the first user terminal through a non-operator network;
the short message receiving and identifying module is used for receiving the verification short message sent by the second user terminal through the operator network; obtaining the mobile phone number of the short message sender and the second verification code according to the verification short message; and the number of the first and second groups,
the binding or unbinding control module is used for comparing the mobile phone number and the second verification code of the short message sending party with the first mobile phone number and the first verification code respectively, and binding or unbinding the first mobile phone number if the comparison results are consistent; if any comparison result is inconsistent, sending a binding or unbinding failure message to the first user terminal through a non-operator network, wherein the binding failure or unbinding failure message contains failure reason information; after the first mobile phone number is bound or unbound, sending a message of successful binding or unbinding to the first user terminal through a non-operator network; and sending the first mobile phone number, the application service identification number of the application server and the current binding or unbinding state information to an operator server together so that the operator server end associates the first mobile phone number with the application service identification number or releases the association of the first mobile phone number with the application service identification number.
13. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 3;
alternatively, the program is adapted to carry out the steps of the method of any of claims 4 to 6 when executed by a processor.
14. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor,
the processor, when executing the program, implementing the steps of the method of any of claims 1 to 3;
alternatively, the processor implements the steps of the method of any one of claims 4 to 6 when executing the program.
CN201710559942.7A 2017-07-10 2017-07-10 Method, device and system for binding or unbinding mobile phone number Active CN107426711B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710559942.7A CN107426711B (en) 2017-07-10 2017-07-10 Method, device and system for binding or unbinding mobile phone number

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710559942.7A CN107426711B (en) 2017-07-10 2017-07-10 Method, device and system for binding or unbinding mobile phone number

Publications (2)

Publication Number Publication Date
CN107426711A CN107426711A (en) 2017-12-01
CN107426711B true CN107426711B (en) 2021-01-08

Family

ID=60427852

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710559942.7A Active CN107426711B (en) 2017-07-10 2017-07-10 Method, device and system for binding or unbinding mobile phone number

Country Status (1)

Country Link
CN (1) CN107426711B (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108810833B (en) * 2018-05-18 2021-11-02 努比亚技术有限公司 Mobile phone number binding information management method and device and computer readable storage medium
CN109120798B (en) * 2018-09-30 2021-01-08 维沃移动通信有限公司 Identification processing method of bound application and mobile terminal
CN110391913B (en) * 2019-08-05 2022-08-23 斑马网络技术有限公司 Vehicle binding method and device
CN111224785A (en) * 2019-12-19 2020-06-02 秒针信息技术有限公司 Binding method and device of voice equipment, storage medium and electronic device
CN111583451A (en) * 2020-04-09 2020-08-25 惠州拓邦电气技术有限公司 Identity verification method and device of electronic lock, computer equipment and storage medium
CN111756703A (en) * 2020-06-03 2020-10-09 拉扎斯网络科技(上海)有限公司 Debugging interface management method and device and electronic equipment
CN113873523A (en) * 2020-06-15 2021-12-31 广州汽车集团股份有限公司 Method and device for removing vehicle binding relationship and related equipment
CN112532653B (en) * 2020-12-22 2022-06-07 富途网络科技(深圳)有限公司 Method and device for managing third-party account
CN113038399A (en) * 2021-04-14 2021-06-25 广州讯鸿网络技术有限公司 Method, electronic device and storage medium for quickly verifying user identity through 5G message
CN113378221B (en) * 2021-06-11 2022-09-23 上海妙一生物科技有限公司 Account information processing method and device
CN117592021A (en) * 2022-08-19 2024-02-23 荣耀终端有限公司 Account login method and electronic equipment

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103746792A (en) * 2013-12-31 2014-04-23 郑盈盈 Binding, unbinding and binding updating method for third-party application account and mobile phone number
CN105072082A (en) * 2015-06-30 2015-11-18 小米科技有限责任公司 Method and device for transmitting verification code

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103685384A (en) * 2012-09-12 2014-03-26 中兴通讯股份有限公司 User authentication method and device for preventing malicious harassment
CN105072112A (en) * 2015-08-07 2015-11-18 中国联合网络通信集团有限公司 Identity authentication method and identity authentication device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103746792A (en) * 2013-12-31 2014-04-23 郑盈盈 Binding, unbinding and binding updating method for third-party application account and mobile phone number
CN105072082A (en) * 2015-06-30 2015-11-18 小米科技有限责任公司 Method and device for transmitting verification code

Also Published As

Publication number Publication date
CN107426711A (en) 2017-12-01

Similar Documents

Publication Publication Date Title
CN107426711B (en) Method, device and system for binding or unbinding mobile phone number
US8064583B1 (en) Multiple data store authentication
US9578027B1 (en) Multiple data store authentication
CN108234505B (en) Account login method and system
US8055558B2 (en) Method and system for authentication via communication terminal using short message
CN105207996B (en) Account merging method and device
CN106302308B (en) Trust login method and device
CN110519154B (en) Data transmission method, device, equipment and computer readable storage medium
CN108933789B (en) Method for preventing personal information leakage and third-party application server
CN107438054B (en) Method and system for realizing menu information control based on public platform
CN108650098B (en) Method and device for user-defined verification mode
US20060069783A1 (en) Program, method and device for managing information shared among components, recording medium and communication apparatus
CN109992940B (en) Identity verification method, device and system and identity verification server
CN113761509B (en) iframe verification login method and device
CN114707976A (en) Payment method, user terminal, device, equipment, system and medium
CN104270357A (en) Service information sending method and device
CN113794999A (en) Short message distribution method, device and storage medium
CN101500235B (en) Off-line authentication method, off-line authentication system and mobile terminal
CN115529154A (en) Login management method, login management device, electronic device and readable storage medium
CN115310958A (en) Payment method, device, equipment, system and medium based on 5G message application
CN107566422A (en) A kind of verification method of third party user
CN115018612A (en) Business processing method and device based on bank counter
CN114238927A (en) Business system login method, system, device, computer equipment and storage medium
CN114445204A (en) Cloud-plus-end-based tax control equipment service processing method and system
CN115640565A (en) Data processing method, data processing device, computer equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant