CN107318100B - Method, device and system for binding mobile phone number - Google Patents
Method, device and system for binding mobile phone number Download PDFInfo
- Publication number
- CN107318100B CN107318100B CN201710407291.XA CN201710407291A CN107318100B CN 107318100 B CN107318100 B CN 107318100B CN 201710407291 A CN201710407291 A CN 201710407291A CN 107318100 B CN107318100 B CN 107318100B
- Authority
- CN
- China
- Prior art keywords
- binding
- channel
- mobile phone
- phone number
- binding request
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method, a device and a system for binding a mobile phone number, wherein the method comprises the following steps: a terminal generates a binding request, wherein the binding request comprises a user account; the terminal sends the binding request to a server through a first channel, wherein the first channel is one of a short message channel and a data channel; the terminal generates an information abstract corresponding to the binding request; the terminal sends the information abstract corresponding to the binding request to the server through a second channel, the second channel is the other one of the short message channel and the data channel, the second channel is different from the first channel, and the server is used for establishing the binding relationship between the user account and the first mobile phone number when verifying that the binding request is matched with the information abstract, so that the user can complete the binding process only by triggering and generating the binding request, the operation of the user in the binding process is simplified, and the human-computer interaction efficiency is improved.
Description
Technical Field
The embodiment of the invention relates to the field of mobile terminals, in particular to a method, a device and a system for binding a mobile phone number.
Background
In a mobile terminal, many application programs need to bind a mobile phone number to a user account, and additional functions such as a verification code receiving function, a Short Message (SMS) pushing function, a Short Message control function and the like are realized through the mobile phone number.
In the related art, the process of binding a mobile phone number to a user account generally includes: the application program displays a registration user interface, and a mobile phone number input box, a verification code acquisition button, a verification code input box and a submission button are provided on the registration user interface; a user inputs a mobile phone number in a mobile phone number input box and clicks a verification code acquisition button; the application program sends the mobile phone number to the server, and the server sends a short message carrying a verification code to the mobile phone number; after checking the short message, the user inputs the verification code into the verification code input box and clicks a submission button; the application program sends the user account number, the mobile phone number and the verification code to the server, and the server establishes a binding relationship between the user account number and the mobile phone number when verifying that the mobile phone number is matched with the verification code.
The method needs four operation steps of inputting the mobile phone number by the user, clicking the submission button, inputting the verification code and clicking the submission button, and the man-machine interaction efficiency of the whole process is low.
Disclosure of Invention
In order to solve the problem of low human-computer interaction efficiency when a mobile phone number is bound for a user account in the related art, the embodiment of the invention provides a mobile phone number binding method, device and system. The technical scheme is as follows:
in a first aspect, an embodiment of the present invention provides a method for binding a mobile phone number, where the method includes:
a terminal generates a binding request, wherein the binding request comprises a user account;
the terminal sends the binding request to a server through a first channel, wherein the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through a short message of a first mobile phone number, and the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network;
the terminal generates an information abstract corresponding to the binding request;
the terminal sends the information abstract corresponding to the binding request to the server through a second channel, the second channel is one of the short message channel and the data channel, the second channel is different from the first channel, and the server is used for establishing a binding relationship between the user account and the first mobile phone number when verifying that the binding request is matched with the information abstract.
In an optional embodiment, the terminal generates a binding request, including:
the terminal receives a first trigger operation;
the terminal acquires the user account according to the first trigger operation;
and 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 method further includes:
the terminal acquires operation verification information;
the terminal generates the binding request according to the user account, and the binding request comprises the following steps:
and the terminal generates the binding request according to the user account and the operation verification information, wherein the operation verification information is used for verifying the validity of the binding process.
In an optional embodiment, the operation verification information includes: tickets and/or logon tokens;
the ticket is a ticket corresponding to the binding operation, the login token is a token generated after the user account is successfully logged in, and the login token has a valid period.
In a second aspect, an embodiment of the present invention provides a method for binding a mobile phone number, where the method includes:
receiving a binding request sent by a terminal through a first channel, wherein the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through short messages of a first mobile phone number, the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network, the binding request comprises a user account, and the first mobile phone number is a mobile phone number corresponding to the terminal;
receiving an information abstract of the binding request sent by the terminal through a second channel; the second channel is one of the short message channel and the data channel, and the second channel is different from the first channel;
verifying whether the binding request is matched with the information abstract of the binding request;
and when the binding request is matched with the information abstract, establishing a binding relationship between the user account and the first mobile phone number.
In an optional embodiment, before establishing the binding relationship between the user account and the first mobile phone number, the method further includes:
acquiring operation verification information from the binding request;
verifying the effectiveness of the binding process according to the operation verification information;
and when the binding process is effective, executing the step of establishing the binding relationship between the user account and the first mobile phone number.
In an alternative embodiment, the operation verification information includes a ticket;
the verifying the validity of the binding process according to the operation verification information includes:
and verifying whether the bill corresponds to the 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 includes:
verifying whether the valid time of the login token is expired.
In a third aspect, an embodiment of the present invention provides an apparatus for binding a mobile phone number, where the apparatus includes:
the generation module is used for generating a binding request, and the binding request comprises a user account;
the sending module is used for sending the binding request to a server through a first channel, wherein the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through a short message of a first mobile phone number, and the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network;
the generating module is further used for generating an information abstract corresponding to the binding request;
the sending module is further configured to send an information summary corresponding to the binding request to the server through a second channel, where the second channel is the other one of the short message channel and the data channel, 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 is matched with the information summary.
In an optional embodiment, the generating module is configured to receive a first trigger operation; acquiring the user account according to the first trigger operation; and generating the binding request according to the user account.
In an optional embodiment, the apparatus further comprises:
the acquisition module is used for acquiring operation verification information;
the generation 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: tickets and/or logon tokens;
the ticket is a ticket corresponding to the binding operation, the login token is a token generated after the user account is successfully logged in, and the login token has a valid period.
In a fourth aspect, an apparatus for binding a mobile phone number is provided, the apparatus comprising:
the device comprises a receiving module, a binding module and a sending module, wherein the receiving module is used for receiving a binding request sent by a terminal through a first channel, and the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through short messages of a first mobile phone number, the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network, the binding request comprises 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 an information summary of the binding request sent by the terminal through a second channel; 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 is also used for verifying whether the binding request is matched with the information abstract of the binding request;
and the binding module is used for establishing a binding relationship between the user account and the first mobile phone number when the binding request is matched with the information abstract.
In an optional embodiment, the apparatus further comprises:
an obtaining module, configured to obtain operation verification information from the binding request;
the verification module is also used for verifying the validity of the binding process according to the operation verification information;
and the binding module is also used for executing the step of establishing the binding relationship between the user account and the first mobile phone number when the binding process is effective.
In an alternative embodiment, the operation verification information includes a ticket;
and the verification module is used for verifying whether the bill corresponds to the binding operation.
In an optional embodiment, the operation verification information includes: a login token;
and the verification module is used for verifying whether the valid time of the login token is expired.
In a fifth aspect, a terminal is provided, where the terminal includes: a processor and a memory, the memory having stored therein at least one instruction, the instruction being loaded and executed by the processor to implement the method for binding a mobile phone number as described in the first aspect or any one of the optional implementations of the first aspect.
In a sixth aspect, a server is provided, which includes: a processor and a memory, the memory having stored therein at least one instruction, the instruction being loaded and executed by the processor to implement the method for binding a mobile phone number as described in the second aspect or any one of the optional implementations of the second aspect.
A seventh aspect provides a computer storage medium, where at least one instruction is stored, where the instruction is loaded and executed by a processor to implement the method for binding a mobile phone number as described in the first aspect or any one of the optional implementations of the first aspect.
In an eighth aspect, there is provided a computer storage medium having at least one instruction stored therein, where the instruction is loaded and executed by a processor to implement the method for binding a mobile phone number as described in the second aspect or any optional implementation manner of the second aspect.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
the short message service of the first mobile phone number is used as one channel, and the mobile communication network or the WiFi network is used as the other channel; and respectively sending the binding request and the message digest of the binding request to a server through respective channels, and establishing a binding relationship between the user account and the first mobile phone number by the server when the binding request is verified to be matched with the message digest. The user can complete the binding process of the user account and the first mobile phone number only by triggering and generating the binding request and automatically executing other steps by the terminal without requiring the user to request and input the verification code, so that the operation of the user in the binding process is simplified, and the human-computer interaction efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a system for binding mobile phone numbers according to various embodiments of the present invention;
fig. 2 is a flowchart of a method for binding a mobile phone number according to an embodiment of the present invention;
fig. 3 is a flowchart of a method for binding mobile phone numbers according to another embodiment of the present invention;
fig. 4 is a schematic interface diagram of the method for binding the mobile phone number according to the embodiment of fig. 3 in implementation;
fig. 5 is a block diagram illustrating an architecture of an apparatus for binding mobile phone numbers according to an embodiment of the present invention;
fig. 6 is a block diagram illustrating an architecture of an apparatus for binding mobile phone numbers according to another embodiment of the present invention;
fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Fig. 1 is a schematic structural diagram illustrating a system for binding mobile phone numbers according to an exemplary embodiment of the present invention. The system for binding the mobile phone number can be a system for providing services for the terminal through short messages, wherein the services comprise at least one of remote control, verification code verification and information push. The system for binding the mobile phone number comprises the following steps: a terminal 120 and a server 140.
The terminal 120 may 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, an MP4(Moving Picture Experts Group Audio Layer IV) player, a laptop computer, or the like.
Optionally, a predetermined application is run in the terminal 120, and the predetermined application includes at least one of the following functions: the function of remote control through short messages, the function of verification code verification through short messages and the function of information pushing through short messages. In the preset application program, different users are distinguished by user accounts, and each user account needs to be bound with a corresponding mobile phone number. Optionally, each user account may be bound to at least one cell phone number.
Alternatively, the terminal 120 is connected to and communicates with the server 140 through a wired network or a wireless network. On one hand, the server 140 and the terminal 120 may communicate with each other through a short message channel, where the short message channel is a channel for receiving and sending data through a short message service of a currently valid mobile phone number on the terminal 120, and is usually implemented by a Circuit Switching Domain (CS) in a mobile communication network; on the other hand, the server 140 and the terminal 120 may communicate with each other through a data channel, where the data channel is implemented by a Packet Switching Domain (PS) or a Wireless Fidelity (WiFi) network in the mobile communication network.
The server 140 is a background server of a predetermined application program, and the server 140 may be one server, a server cluster composed of a plurality of servers, or a cloud computing center. The server 140 has a function of directly transmitting and/or receiving a short message, or the server 140 has a function of transmitting and/or receiving a short message through a short message platform provided by a mobile operator.
Fig. 2 is a flowchart illustrating a method for binding a mobile phone number according to an exemplary embodiment of the present invention. The embodiment is illustrated by applying the method between the terminal 120 and the server 140 of the system shown in fig. 1. The method comprises the following steps:
step 201, a terminal generates a binding request, wherein the binding request comprises a user account;
the binding request is used for requesting the server to bind the user account and the mobile phone number. In different embodiments, the binding request may also have other names such as a registration request, an association request, and the like, which is not limited by this embodiment.
The binding request carries the 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 a binding request to a server through a first channel;
the first channel is one of a short message channel and a data channel. The short message channel is a channel for sending and/or receiving data through a short message service of a mobile phone number, and the data channel is a channel for sending and/or receiving data through a mobile communication network or a WiFi network.
Step 203, the server receives a binding request sent by the terminal through the first channel;
step 204, the terminal generates an information abstract corresponding to the binding request;
the Message Digest may be information obtained by calculating the binding request through MD5(Message Digest Algorithm, generation five), a hash Algorithm, other irreversible encryption Algorithm, or a signature Algorithm. Typically, the message digest corresponding to each binding request is unique.
Optionally, step 204 may be executed before step 202, and this embodiment does not limit the order between step 202 and step 204.
Step 205, the terminal sends the information abstract of the binding request to the server through a 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 the information summary corresponding to the binding request sent by the terminal through the second channel;
step 207, the server verifies whether the binding request and the information abstract are matched;
the message digest received by the server may be referred to as a first message digest.
Optionally, the server calculates a second information abstract according to the received binding request by the same algorithm as the terminal, and compares the first information abstract with the second information abstract; if the two message digests are completely the same, the binding request is considered to be matched with the message digests; if the two message digests are not identical or identical, the binding request and the message digest are considered to be mismatched.
And step 208, when the binding request is matched with the information abstract, 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. Or, the server acquires the user account from the binding request, acquires the first mobile phone number (namely 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, and step 202 may be executed simultaneously with step 205, or step 202 may be executed after step 205.
In the method for binding the mobile phone number provided by the embodiment, the short message service of the first mobile phone number is used as one channel, and the mobile communication network or the WiFi network is used as another channel; and respectively sending the binding request and the message digest of the binding request to a server through respective channels, and establishing a binding relationship between the user account and the first mobile phone number by the server when the binding request is verified to be matched with the message digest. The user can complete the binding process of the user account and the first mobile phone number only by triggering and generating the binding request and automatically executing other steps by the terminal without requiring the user to request and input the verification code, so that the operation of the user in the binding process is simplified, and the human-computer interaction efficiency is improved.
Fig. 3 is a flowchart illustrating a method for binding a mobile phone number according to another exemplary embodiment of the present invention. The embodiment is illustrated by applying the method between the terminal 120 and the server 140 in the system shown in fig. 1. The method comprises the following steps:
step 301, a terminal sends a login request to a server, wherein the login request carries a user account and a password;
when the terminal needs to communicate with the server, a login request is generated by using a pre-registered user account and a password, and the login request is sent to the server.
Illustratively, taking the predetermined application in the terminal as a find mobile phone program as an example, referring to the left diagram of fig. 4, the user inputs the user account number zhangsan @ xxx.com and the password in the input box 41 in the login interface of the find mobile phone program, and then clicks the "login" button 42, and 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 the password; and after the verification is successful, the login token is fed back to the terminal.
A login token (token) is a kind of digital token that is assigned to a terminal by a server when login is successful. The login token usually has a valid period (for example, within 10 minutes), and when the terminal subsequently communicates with the server, the login token needs to be carried in information so that the server recognizes that the terminal is in a valid login state.
And a corresponding relation exists among the user account, the login password and the login token. Table one schematically shows the correspondence.
Watch 1
| User name | Login password | Login token | Expiration date |
| Zhang three | 128568 | 1F4Gsdfa | 11:02-11:12 |
| Li four | 865986 | 5548asdf1 | 10:59-11:09 |
| Wangwu tea | 1155336 | 2146451af | 11:04-11:14 |
Correspondingly, the terminal stores the login token.
And after the terminal receives the login token, the terminal successfully logs in.
Step 303, the terminal receives a first trigger operation;
optionally, the first trigger operation is an operation for generating a binding request.
Referring to the right diagram of fig. 4 in combination, the terminal jumps from the login interface to the open search handset interface, and if the user wishes to open the search device function, the "open search handset" button 43 is clicked on the open search handset interface. The process of opening and searching for a 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 trigger operation;
the user account is an account registered in the server and used to identify the user identity. The operation verification information is used for verifying the validity of the binding process.
Optionally, the terminal further obtains a first mobile phone number, where the first mobile phone number is a mobile phone number corresponding to the terminal.
305, the terminal generates a binding request according to the user account and the operation verification information;
optionally, the operation verification information includes: tickets and/or login tokens (tokens). Where the ticket is a ticket corresponding to the binding process, the ticket may be a string, such as string a 1. The bill is used for indicating that the operation is a binding operation to the server; the first login token may be a token fed back by the server in step 302, or a token updated by the server after step 302, and the login token is generated after login is successful and has a validity period.
Optionally, the binding request is (user account, ticket, login token).
In one 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 sequences the user account, the first mobile phone number, and the operation verification information in sequence, and adds a comma between each two pieces of information to obtain a binding request (the user account, the first mobile phone number, the ticket, and the login token).
In another possible implementation manner, if the terminal further obtains the operation verification information, the binding request is (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 a server through a first channel;
illustratively, the terminal sends the binding request to the server through a data channel. Optionally, the terminal encrypts the binding request and then sends the encrypted binding request to the server.
Step 307, the server receives a binding request sent by the terminal through a first channel;
and the server receives the binding request sent by the terminal through the data channel. If the binding request is the information encrypted by the terminal, the server decrypts the binding request in the same way to obtain the specific content of the binding request.
308, the terminal generates an information abstract corresponding to the binding request;
in one embodiment, the Message Digest of the binding request is the information obtained by computing the binding request through MD5(Message Digest Algorithm generation v 5), a hash Algorithm, other irreversible encryption Algorithm, or a signature Algorithm. Typically, the message digest corresponding to each binding request is unique.
Step 309, the terminal sends the information abstract of the binding request to the server through a second channel;
illustratively, the terminal sends the information abstract to the server through a short message channel. The short message channel is a channel for the terminal to send data to the server through the short message service of the first mobile phone number.
The server can bind two short message service numbers on a short message platform provided by an operator in advance: the system comprises an uplink short message service number and a downlink short message service number, wherein the uplink short message service number is used for receiving short messages sent by a terminal, and the downlink short message service number is used for sending the short messages to the terminal. For example, the uplink short message service number is: 10600x, the downlink sms number is: 10602 x.
The terminal stores an uplink short message service number 10600x in advance, the terminal takes the first mobile phone number as a short message sender, the uplink short message service number 10600x as a short message receiver and the information summary as short message content to send a short message, and the short message platform forwards the short message to the server after receiving the short message.
Step 310, the server receives an information abstract corresponding to the binding request sent by the terminal through a second channel;
and the server receives the information abstract sent by the control terminal through the short message channel. Optionally, since the message digest is carried in a short message, the sender of the short message is a first mobile phone number, and the server stores the correspondence between the first mobile phone number and the message digest.
The message digest received by the server may be referred to as a first message digest.
Step 311, the server obtains the user account and the operation verification information from the binding request;
optionally, the server parses the binding request to obtain the user account, the ticket, and the login token.
Optionally, the server analyzes 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 to obtain the user account, the terminal identifier, the first phone number, the ticket, and the login token.
Step 312, the server detects whether the ticket is a ticket corresponding to the binding process;
since there may be a variety of operational processes between the terminal and the server: a binding process, a logout process and a SIM card replacing process, wherein different operation processes respectively correspond to respective bills, the server needs to detect whether the analyzed bill is the bill corresponding to the binding process, and if the bill is the bill corresponding to the binding process, the step 313 is entered; if the ticket is not a ticket corresponding to the binding process but a ticket corresponding to another process, another process (such as a logout process or an update process) is performed.
Step 313, when the ticket is the ticket corresponding to the binding process, the server detects whether the login token is in the valid period;
each login token has a certain validity period, such as 10 minutes, 30 minutes, 2 hours, etc.
The server detects whether the analyzed login token is in the valid period or not; if the time limit is valid, go to step 314; and if the time limit is not in the valid time limit, sending binding failure information to the terminal.
It should be noted that the execution sequence of step 312 and step 313 may be interchanged or executed in parallel, and step 314 is only entered if the detection results of step 312 and step 313 are both "yes".
Step 314, when the login token is in the valid period, the server verifies whether the binding request is matched with the information abstract;
optionally, the server calculates a second information abstract according to the received binding request by the same algorithm as the terminal, and compares the first information abstract with the second information abstract; if the two message digests are completely the same, the binding request is considered to be matched with the message digest, and the step 315 is entered; and if the two message digests are not completely the same or different, the binding request is not matched with the message digests, and 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 abstract, the server queries a corresponding binding request according to the first mobile phone number, and generates a second information abstract according to the queried binding request. Or the server does not store the corresponding relationship between the first mobile phone number and the first information abstract, and when the server only stores the first information abstract, the server generates corresponding second information abstract for all received binding requests (which can be within the latest period of time), inquires whether the second information abstract completely consistent with the first information abstract exists, and determines that the first mobile phone number and the second information abstract are matched if the second information abstract completely consistent with the first information abstract exists.
Step 315, when the binding request is matched with the information abstract, the server establishes a binding relationship between the user account and the first mobile phone number;
each terminal identification may bind at least one first mobile phone number. That is, the first phone number may be more than one.
In a possible embodiment, when the server opens the function of searching for the device for the terminal, the server simultaneously establishes a binding relationship between the user account, the terminal identifier and the first mobile phone number. Table two schematically shows the binding relationship.
Watch two
| User account number | Terminal identification (IMEI) | Mobile phone number |
| Zhang three | xxxxxx0601472104 | 134xxxx8888 |
| Li four | Xxxxxx121272105 | 135xxxx6666 |
| Li four | xxxxxx0701472234 | 186xxxx7777 |
In step 316, the server sends a binding success message to the terminal.
And after the terminal successfully opens the function of searching the mobile phone, the server sends a binding success message to the terminal. Optionally, the binding success message may be sent through a short message channel or a data channel.
After the server feeds back a successful binding message to the terminal, the terminal jumps from the opening of the searching mobile phone interface to the searching mobile phone function interface, the searching mobile phone function interface provides position display of the terminal in a map, the name of the terminal, namely 'Zhang three mobile phone' and the state of the terminal, namely 'on-line', and then a user can control the terminal to perform operations such as ringing, locking, data erasing and the like.
In the method provided by the embodiment, the short message service of the first mobile phone number is used as one channel, and the mobile communication network or the WiFi network is used as another channel; and respectively sending the binding request and the message digest of the binding request to a server through respective channels, and establishing a binding relationship between the user account and the first mobile phone number by the server when the binding request is verified to be matched with the message digest. The user can complete the binding process of the user account and the first mobile phone number only by triggering and generating the binding request and automatically executing other steps by the terminal.
In the method provided by the embodiment, the user only needs to trigger the first trigger operation in the binding process, and does not need to request the verification code and input the verification code, so that the operation of the user in the binding process is simplified, and the human-computer interaction efficiency is improved.
In the method provided by the embodiment, the validity of the binding process can be detected by the server by adding the operation verification information, and the user account and the first mobile phone number are bound only when the binding process is valid, so that the security of the binding process is improved.
The following are embodiments of the apparatus of the present invention that may be used to perform embodiments of the method of the present invention. For details which are not disclosed in the embodiments of the apparatus of the present invention, reference is made to the embodiments of the method of the present invention.
Fig. 5 is a block diagram of an apparatus for binding mobile phone numbers according to an exemplary embodiment of the present invention, which may be implemented by software, hardware or a combination of the two as all or a part of a terminal. The device comprises:
a generating module 510, configured to generate a binding request, where the binding request includes a user account;
a sending module 520, configured to send the binding request to a server through a first channel, 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 through a short message of a first mobile phone number, and the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network;
the generating module 510 is further configured to generate an information summary 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 through a second channel, where the second channel is the other one of the short message channel and the data channel, 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 is matched with the information digest.
In an optional embodiment, the generating module 510 is configured to receive a first trigger operation; acquiring the user account according to the first trigger operation; and generating the binding request according to the user account.
In an optional embodiment, the apparatus further comprises:
an obtaining module 530, 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 current binding process.
In an optional embodiment, the operation verification information includes: tickets and/or logon tokens;
the ticket is a ticket corresponding to the binding operation, the login token is a token generated after the user account is successfully logged in, and the login token has a valid period.
Fig. 6 is a block diagram illustrating an apparatus for binding mobile phone numbers according to another exemplary embodiment of the present invention. The apparatus may be implemented as all or part of a server in software, hardware, or a combination of both. The device comprises:
a receiving module 610, configured to receive a binding request sent by a terminal through a first channel, 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 through short messages of a first mobile phone number, the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network, the binding request comprises 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 an information summary of the binding request sent by the terminal through a second channel; 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 verifying module 620 is further configured to verify whether the binding request and the information digest of the binding request match;
a binding module 630, configured to establish a binding relationship between the user account and the first mobile phone number when the binding request matches the information digest.
In an optional embodiment, the apparatus further comprises:
an obtaining module 640, configured to obtain operation verification information from the binding request;
the verifying module 620 is further configured to verify the validity of the current binding process according to the operation verifying information;
the binding module 630 is further configured to execute the step of establishing a binding relationship between the user account and the first mobile phone number when the binding process is valid.
In an alternative embodiment, the operation verification information includes a ticket;
the verifying module 620 is configured to verify whether the ticket corresponds to a binding operation.
In an optional embodiment, the operation verification information includes: a login token;
the verifying module 620 is configured to verify whether the valid time of the login token expires.
It should be noted that: the device for binding a mobile phone number provided in the foregoing embodiment is only illustrated by dividing the functional modules when binding a mobile phone number, and in practical applications, the function distribution may be completed by different functional modules as needed, 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 apparatus for binding a mobile phone number and the method embodiment for binding a mobile phone number provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not described herein again.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
Fig. 7 is a diagram illustrating a structure of a terminal according to an exemplary embodiment of the present invention. 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, the memory 714 is connected to the processor 711 through the bus 715, the memory 714 is used for storing at least one instruction, and the processor 711 executes the instruction in the memory 714 to implement the steps of the method for binding the mobile phone numbers in the terminal side in the method embodiments shown in fig. 2 and fig. 3.
The receiver 712 and the transmitter 713 may be implemented as a communication component, which may be a communication chip that modulates and/or demodulates information and receives or transmits the information via a wireless signal.
Further, the memory 714 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The above structural illustration is only an illustrative illustration of the terminal, and the terminal may include more or fewer components, for example, the terminal may not include a receiver, or the terminal further includes other components such as a sensor, a display screen, and a power supply, and details are not described in this embodiment.
Embodiments of the present invention also provide a computer-readable medium, on which at least one instruction is stored, and the instruction, when executed by the processor 711, implements the steps of the method for binding mobile phone numbers at the terminal side in the method embodiments shown in fig. 2 and fig. 3.
Fig. 8 is a schematic structural diagram of a server provided in an exemplary embodiment of the present application, where 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 connected to the processor 811 through the bus 815, the memory 814 is used for storing at least one instruction, and the processor 811 implements the steps of the method for binding mobile phone numbers in the server side in the method embodiments shown in fig. 2 and fig. 3 when executing the instruction in the memory 814.
The receiver 812 and the transmitter 813 may be implemented as one communication component, which may be a piece of communication chip for modulating and/or demodulating information and receiving or transmitting the information through a wireless signal. In other embodiments, the receiver 812 and the transmitter 813 can be alternatively implemented as a network interface 816, and the server is connected to the short message sending platform through the network interface 816 to send and receive short messages through the short message sending platform.
Further, the memory 814 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The above structural illustration is only an illustrative illustration of the server, and the server may include more or fewer components, for example, the server further includes other components such as an I/O interface and a power supply, etc., which are not described in detail in this embodiment.
Embodiments of the present invention also provide a computer-readable medium, on which at least one instruction is stored, where the instruction, when executed by the processor 811, implements the steps of the method for binding a mobile phone number on the server side in the method embodiments shown in fig. 2 and fig. 3.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (21)
1. A method for binding a mobile phone number, the method comprising:
a terminal generates a binding request, wherein the binding request comprises a user account;
the terminal sends the binding request to a server through a first channel, wherein the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through a short message of a first mobile phone number, and the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network;
the terminal generates an information abstract corresponding to the binding request, wherein the information abstract is information obtained by calculating the binding request through an algorithm, and the algorithm comprises any one of the following items: a fifth generation MD5 of an information digest algorithm, a hash algorithm, an irreversible encryption algorithm and a signature algorithm;
and the terminal sends the information abstract corresponding to the binding request to the server through a second channel, wherein the second channel is one of the short message channel and the data channel, the second channel is different from the first channel, the server is used for calculating a target information abstract according to the algorithm for the received binding request, and the binding relationship between the user account and the first mobile phone number is established when the target information abstract is verified to be matched with the information abstract.
2. The method of claim 1, wherein the terminal generates a binding request, comprising:
the terminal receives a first trigger operation;
the terminal acquires the user account according to the first trigger operation;
and the terminal generates the binding request according to the user account.
3. The method of claim 2, wherein before the terminal generates the binding request according to the user account, the method further comprises:
the terminal acquires operation verification information;
the terminal generates the binding request according to the user account, and the binding request comprises the following steps:
and the terminal generates the binding request according to the user account and the operation verification information, wherein the operation verification information is used for verifying the validity of the binding process.
4. The method of claim 3, wherein the operation verification information comprises: tickets and/or logon tokens;
the ticket is a ticket corresponding to the binding operation, the login token is a token generated after the user account is successfully logged in, and the login token has a valid period.
5. A method for binding a mobile phone number, the method comprising:
receiving a binding request sent by a terminal through a first channel, wherein the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through short messages of a first mobile phone number, the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network, the binding request comprises a user account, and the first mobile phone number is a mobile phone number corresponding to the terminal;
receiving an information abstract of the binding request sent by the terminal through a second channel; the second channel is one of the short message channel and the data channel, the second channel is different from the first channel, the information summary refers to information obtained by calculating the binding request through an algorithm, and the algorithm includes any one of the following items: a fifth generation MD5 of an information digest algorithm, a hash algorithm, an irreversible encryption algorithm and a signature algorithm;
calculating a target information abstract according to the algorithm for the received binding request, and verifying whether the target information abstract is matched with the information abstract of the binding request;
and when the target information abstract is matched with the information abstract, establishing a binding relationship between the user account and the first mobile phone number.
6. The method of claim 5, wherein before establishing the binding relationship between the user account and the first mobile phone number, further comprising:
acquiring operation verification information from the binding request;
verifying the effectiveness of the binding process according to the operation verification information;
and when the binding process is effective, executing the step of establishing the binding relationship between the user account and the first mobile phone number.
7. The method of claim 6, wherein the operation verification information includes a ticket;
the verifying the validity of the binding process according to the operation verification information includes:
and verifying whether the bill corresponds to the binding operation.
8. The method of 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 includes:
verifying whether the valid time of the login token is expired.
9. An apparatus for binding a mobile phone number, the apparatus comprising:
the generation module is used for generating a binding request, and the binding request comprises a user account;
the sending module is used for sending the binding request to a server through a first channel, wherein the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through a short message of a first mobile phone number, and the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network;
the generating module is further configured to generate an information summary corresponding to the binding request, where the information summary refers to information obtained by calculating the binding request through an algorithm, and the algorithm includes any one of the following items: a fifth generation MD5 of an information digest algorithm, a hash algorithm, an irreversible encryption algorithm and a signature algorithm;
the sending module is further configured to send the information digest corresponding to the binding request to the server through a second channel, where the second channel is the other one of the short message channel and the data channel, and the server is configured to calculate a target information digest according to the algorithm for the received binding request, and establish a binding relationship between the user account and the first mobile phone number when it is verified that the target information digest matches the information digest.
10. The apparatus of claim 9, wherein the generating module is configured to receive a first trigger operation; acquiring the user account according to the first trigger operation; and generating the binding request according to the user account.
11. The apparatus of claim 10, further comprising:
the acquisition module is used for acquiring operation verification information;
the generation 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 of claim 11, wherein the operation verification information comprises: tickets and/or logon tokens;
the ticket is a ticket corresponding to the binding operation, the login token is a token generated after the user account is successfully logged in, and the login token has a valid period.
13. An apparatus for binding a mobile phone number, the apparatus comprising:
the device comprises a receiving module, a binding module and a sending module, wherein the receiving module is used for receiving a binding request sent by a terminal through a first channel, and the first channel is one of a short message channel and a data channel; the short message channel is a channel for sending data through short messages of a first mobile phone number, the data channel is a channel for sending data through a mobile communication network or a wireless fidelity network, the binding request comprises 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 an information summary of the binding request sent by the terminal through a second channel; the second channel is one of the short message channel and the data channel, the second channel is different from the first channel, the information summary refers to information obtained by calculating the binding request through an algorithm, and the algorithm includes any one of the following items: a fifth generation MD5 of an information digest algorithm, a hash algorithm, an irreversible encryption algorithm and a signature algorithm;
the verification module is also used for calculating a target information abstract according to the algorithm for the received binding request and verifying whether the target information abstract is matched with the information abstract of the binding request;
and the binding module is used for establishing a binding relationship between the user account and the first mobile phone number when the target information abstract is matched with the information abstract.
14. The apparatus of claim 13, further comprising:
an obtaining module, configured to obtain operation verification information from the binding request;
the verification module is also used for verifying the validity of the binding process according to the operation verification information;
and the binding module is also used for executing the step of establishing the binding relationship between the user account and the first mobile phone number when the binding process is effective.
15. The apparatus of claim 14, wherein the operation verification information comprises a ticket;
and the verification module is used for verifying whether the bill corresponds to the binding operation.
16. The apparatus of claim 14, wherein the operation verification information comprises: a login token;
and the verification module is used for verifying whether the valid time of the login token is expired.
17. A terminal, characterized in that the terminal comprises: a processor and a memory, the memory having stored therein at least one instruction that is loaded and executed by the processor to implement the method for binding a mobile phone number according to any one of claims 1 to 4.
18. A server, characterized in that the server comprises: a processor and a memory, the memory having stored therein at least one instruction that is loaded and executed by the processor to implement the method for binding a mobile phone number according to any one of claims 5 to 8.
19. A computer storage medium having stored therein at least one instruction which is loaded and executed by a processor to implement the method for binding a mobile phone number according to any one of claims 1 to 4.
20. A computer storage medium having stored therein at least one instruction which is loaded and executed by a processor to implement a method for binding a mobile phone number according to any one of claims 5 to 8.
21. A system for binding mobile phone numbers is characterized in that,
the system comprises a terminal and a server; the terminal comprising an apparatus as claimed in any of claims 9 to 12, and the server comprising an apparatus as claimed in any of claims 13 to 16;
or the like, or, alternatively,
the system comprising a terminal according to claim 17 and a server according to claim 18.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710407291.XA CN107318100B (en) | 2017-06-02 | 2017-06-02 | Method, device and system for binding mobile phone number |
| PCT/CN2018/088787 WO2018219260A1 (en) | 2017-06-02 | 2018-05-29 | Method, device and system for binding mobile phone number |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710407291.XA CN107318100B (en) | 2017-06-02 | 2017-06-02 | Method, device and system for binding mobile phone number |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107318100A CN107318100A (en) | 2017-11-03 |
| CN107318100B true CN107318100B (en) | 2020-01-14 |
Family
ID=60183968
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710407291.XA Active CN107318100B (en) | 2017-06-02 | 2017-06-02 | Method, device and system for binding mobile phone number |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107318100B (en) |
| WO (1) | WO2018219260A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107318100B (en) * | 2017-06-02 | 2020-01-14 | Oppo广东移动通信有限公司 | Method, device and system for binding mobile phone number |
| CN108923948A (en) * | 2018-08-01 | 2018-11-30 | 上海小蚁科技有限公司 | Camera binding method, device and its medium |
| CN111030984B (en) * | 2019-10-22 | 2022-08-19 | 上海泰宇信息技术股份有限公司 | Data safety transmission system and method |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102984261A (en) * | 2012-12-04 | 2013-03-20 | 中国联合网络通信集团有限公司 | Network service login method, equipment and system based on mobile telephone terminal |
| CN103152331A (en) * | 2013-02-07 | 2013-06-12 | 百度在线网络技术（北京）有限公司 | Method and system for logging in/registering through mobile terminal and cloud server |
| CN103313245A (en) * | 2013-05-28 | 2013-09-18 | 中国联合网络通信集团有限公司 | Network service access method, equipment and system based on mobile phone terminal |
| CN104717261A (en) * | 2013-12-17 | 2015-06-17 | 华为技术有限公司 | Login method and desktop management device |
| CN104954383A (en) * | 2015-06-24 | 2015-09-30 | 深圳市兰丁科技有限公司 | Application program login method and system |
| CN105812413A (en) * | 2014-12-29 | 2016-07-27 | 深圳市腾讯计算机系统有限公司 | Communication method and device |
| CN106453263A (en) * | 2016-09-19 | 2017-02-22 | 惠州Tcl移动通信有限公司 | Method and system of binding cellphone number with APP |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8478310B2 (en) * | 2006-10-05 | 2013-07-02 | Verizon Patent And Licensing Inc. | Short message service (SMS) data transfer |
| CN102299930B (en) * | 2011-09-19 | 2014-09-10 | 北京无限新锐网络科技有限公司 | Method for ensuring security of client software |
| CN103178906B (en) * | 2011-12-22 | 2018-04-17 | 国民技术股份有限公司 | Communication system and communication means |
| CN104917586B (en) * | 2014-03-11 | 2019-06-07 | 腾讯科技（深圳）有限公司 | Transmit method of calibration, the apparatus and system of data |
| CN105898728A (en) * | 2015-10-22 | 2016-08-24 | 乐视致新电子科技（天津）有限公司 | Mobile phone account member rights and interests binding method, mobile phone device, server and system |
| CN105848119A (en) * | 2016-03-22 | 2016-08-10 | 赵莉莉 | Method for providing short message reception confirmation display, mobile terminal, server and system |
| CN107318100B (en) * | 2017-06-02 | 2020-01-14 | Oppo广东移动通信有限公司 | Method, device and system for binding mobile phone number |
-
2017
- 2017-06-02 CN CN201710407291.XA patent/CN107318100B/en active Active
-
2018
- 2018-05-29 WO PCT/CN2018/088787 patent/WO2018219260A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102984261A (en) * | 2012-12-04 | 2013-03-20 | 中国联合网络通信集团有限公司 | Network service login method, equipment and system based on mobile telephone terminal |
| CN103152331A (en) * | 2013-02-07 | 2013-06-12 | 百度在线网络技术（北京）有限公司 | Method and system for logging in/registering through mobile terminal and cloud server |
| CN103313245A (en) * | 2013-05-28 | 2013-09-18 | 中国联合网络通信集团有限公司 | Network service access method, equipment and system based on mobile phone terminal |
| CN104717261A (en) * | 2013-12-17 | 2015-06-17 | 华为技术有限公司 | Login method and desktop management device |
| CN105812413A (en) * | 2014-12-29 | 2016-07-27 | 深圳市腾讯计算机系统有限公司 | Communication method and device |
| CN104954383A (en) * | 2015-06-24 | 2015-09-30 | 深圳市兰丁科技有限公司 | Application program login method and system |
| CN106453263A (en) * | 2016-09-19 | 2017-02-22 | 惠州Tcl移动通信有限公司 | Method and system of binding cellphone number with APP |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107318100A (en) | 2017-11-03 |
| WO2018219260A1 (en) | 2018-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103037312B (en) | Information push method and device | |
| CN108989346B (en) | Third-party valid identity escrow agile authentication access method based on account hiding | |
| CN103095457B (en) | A kind of login of application program, verification method | |
| CN107249004B (en) | Identity authentication method, device and client | |
| CN106790156B (en) | Intelligent device binding method and device | |
| CN102572815B (en) | Method, system and device for processing terminal application request | |
| CN107241336B (en) | Identity verification method and device | |
| CN110324815B (en) | One-number-multi-card opening method, server, terminal and block chain network system | |
| CN105007577A (en) | Virtual SIM card parameter management method, mobile terminal and server | |
| US11177963B2 (en) | Method for authenticating a user based on an image relation rule and corresponding first user device, server and system | |
| CN103107996A (en) | On-line download method and system of digital certificate and digital certificate issuing platform | |
| CN103297403A (en) | Method and system for achieving dynamic password authentication | |
| CN108259502A (en) | For obtaining the identification method of interface access rights, server-side and storage medium | |
| CN105450643A (en) | Network access authentication method, apparatus and system | |
| CN107318100B (en) | Method, device and system for binding mobile phone number | |
| CN107623907B (en) | eSIM card network locking method, terminal and network locking authentication server | |
| CN112559993A (en) | Identity authentication method, device and system and electronic equipment | |
| EP3851983B1 (en) | Authorization method, auxiliary authorization component, management server and computer readable medium | |
| CN104796255A (en) | A safety certification method, device and system for a client end | |
| CN108965324A (en) | A kind of anti-brush method of short message verification code, terminal, server, equipment and medium | |
| CN104219626A (en) | Identity authentication method and device | |
| CN114239072B (en) | Block chain node management method and block chain network | |
| CN110246053B (en) | Carrier binding changing method of power supply device and server thereof | |
| CN113472722A (en) | Data transmission method, storage medium, electronic device and automatic ticket selling and checking system | |
| CN106559386A (en) | A kind of authentication method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant after: OPPO Guangdong Mobile Communications Co., Ltd. Address before: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant before: Guangdong Opel Mobile Communications Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |