CN111373780A

CN111373780A - Method for judging association relation between mobile phone number and application

Info

Publication number: CN111373780A
Application number: CN201780097035.3A
Authority: CN
Inventors: 郭帅; 喻念
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-11-21
Filing date: 2017-11-21
Publication date: 2020-07-03
Also published as: WO2019100223A1

Abstract

Based on factors such as security and user experience, the application program usually needs to associate a mobile phone number. The invention provides a method for judging the association relationship between a mobile phone number and an application program, and prompts a user to install, unbind the mobile phone number and the like based on the association relationship. The method is suitable for the scenes that the user does not change the mobile phone number when changing the mobile phone, does not change the mobile phone when changing the mobile phone number, and changes the mobile phone number and the mobile phone, so that the user can have better experience.

Description

Method for judging association relation between mobile phone number and application

The embodiment of the invention relates to the field of communication, in particular to a method for judging association relation between a mobile phone number and an application.

Background

Mobile terminals have become more and more versatile. Examples of such functions include data and voice communication, capturing images and video via a camera, recording audio, playing music files via a speaker system, and displaying images and video on a display. Some mobile terminals include additional functionality that supports game play, while other terminals are configured as multimedia players. As these functions become more diversified, the mobile terminal may support more complicated functions, such as capturing images or videos, reproducing music or video files, playing games, receiving broadcast signals, and the like.

With the increasing popularity of smart phones, users can download and install various APPs at will, such as Wechat, Facebook, and the like. For reasons such as security or user experience, a service provider often needs a user to provide personal information such as a phone number for binding, and the user often forgets the bound APP or unloads the bound APP, or has a situation of changing a mobile phone or changing a mobile phone number, and the user does not know an application program associated with the mobile phone number (other account numbers).

Disclosure of Invention

Based on the reasons, the invention provides a method for judging the association relationship between the mobile phone number and the application program, and provides various quick operations, so that a user has better experience.

In one aspect, an embodiment of the present invention provides a method, including: the first server may be a background server of the first application program, and the second server may store a correspondence between the service identifier of the first server and the first application program; a terminal device acquires a first signal, the first signal indicates the terminal device to send an association request to a first server, the terminal device can send a second signal to the first server, and the second signal comprises the association request; the first server acquires the second signal, and sends a third signal to a third server, wherein the third signal comprises a processing verification information request; a third server acquires the third signal, the third server generates first verification information, and the third server sends the first verification information to the terminal equipment, wherein the first verification information comprises a service identifier of the first server; the terminal equipment accesses the second server, and the terminal equipment can acquire the service identifier of the first server; the terminal device acquires the first verification information, and identifies a first application program through a service identifier of the first server contained in the first verification information, wherein a first mobile phone number of the terminal device receives the first verification information; the terminal device may associate the first mobile phone number with the first application. The embodiment can enable the terminal device to obtain the association relationship between the first number and the plurality of application programs.

In one possible design, the terminal device may send the association relationship between the first mobile phone number and the first application to the second server, so as to implement the timely backup of the association relationship.

The embodiment of the invention provides a method, which comprises the following steps: the first server can be a background server of the first application program, and the second server can store the association relationship between the transmission source of the first server and the first application program; the terminal equipment can acquire a first mobile phone number and can send the first mobile phone number to the first server; the first server acquires a first mobile phone number, and the first server sends the first mobile phone number to a third server; the third server receives a first mobile phone number, generates first verification information, and sends the first verification information to the first mobile phone number of the terminal device; the terminal equipment can access a second server to acquire a transmission source of the first server; the terminal device acquires the first verification information, and the terminal device identifies a first application program through a sending source of the first verification information, wherein a first mobile phone number of the terminal device receives the first verification information; the terminal device may associate the first mobile phone number with the first application. The embodiment can realize that the application program is identified by verifying the sending source of the information and the association relationship is established.

The embodiment of the invention provides a method which is characterized by comprising the following steps: the method comprises the steps that terminal equipment displays a first login interface of a first application program, wherein the terminal equipment stores an incidence relation between a first mobile phone number and the first application program; acquiring a second mobile phone number, and comparing the second mobile phone number with the first mobile phone number by the terminal equipment; and when the second mobile phone number is different from the first mobile phone number, the terminal equipment prompts the user that the first mobile phone number is associated with the first application program. The embodiment can remind the user of the mobile phone number of the associated application program.

In one possible design, when the second mobile phone number is different from the first mobile phone number, the terminal device allows the user to log in with the second mobile phone number and/or the first mobile phone number. So as to provide different login modes for users.

The embodiment of the invention provides a method which is characterized by comprising the following steps: the terminal device can display a first login interface of a first application program, and the terminal device stores an association relation between a first account and the first application program; acquiring a second account, wherein the second account is different from the first account; when the second account is not associated with the first application program, the terminal equipment prompts a user that the first account is associated with the first account, wherein the first account is associated with the second account through a third account. The user may be alerted to applications that have been associated with a different account number.

In one possible design, when the second account number is already associated with the first application program, the second account number is allowed to log in the first application program.

The embodiment of the invention provides a method which is characterized by comprising the following steps: displaying a first interface, wherein the terminal equipment stores the association relation between a first mobile phone number and a first application program, and the first application program is not installed on the terminal equipment; and acquiring a first operation aiming at the first interface, and downloading the first application program by the terminal equipment. To enable the user to download programs that have been associated but not installed.

In one possible design, a first operation for the first interface is acquired, and the terminal device jumps to a download interface of a third-party store. To enable a user to download an already associated but not installed program

In one possible design, a first operation for the first interface is acquired, and the terminal device downloads a plurality of application programs. To enable the user to download the already associated but not installed program at one time.

In one possible design, a second operation for the first interface is acquired, and the terminal device jumps to a login interface of a second application program, wherein the first mobile phone number is not associated with the second application program, and the second application program is installed on the terminal device. To enable the user to associate programs that have been installed but not associated.

In one possible design, a third gesture operation for the first interface is acquired, and the terminal device jumps to the second interface; acquiring authentication information input by a user on the second interface; when the authentication is successful, the first mobile phone number and the first application program are disassociated; so as to realize the disassociation of the mobile phone number and the application program.

In one possible design, a fourth operation for the first interface is acquired, and the terminal device jumps to a third interface; and acquiring a second mobile phone number, wherein the second mobile phone number is associated with the first application program, and the first mobile phone number is disassociated from the first application program, and the first mobile phone number is different from the second mobile phone number. So as to realize the replacement of the associated mobile phone number by the user.

The embodiment of the invention provides terminal equipment, which is characterized by comprising the following components: a processor; and a storage medium, wherein the storage medium stores instructions that cause the terminal device to perform the method described above.

An embodiment of the present invention provides a computer program product containing instructions, which is characterized by causing an electronic device to execute the above method when the computer program product runs on the electronic device.

An embodiment of the present invention provides a computer-readable storage medium, which includes instructions, and is characterized in that when the instructions are run on an electronic device, the instructions cause the terminal device to execute the above method.

It should be noted that the embodiments of the present invention can be combined arbitrarily to achieve different technical effects.

Through the scheme, the embodiment of the invention can realize that the user knows the application program related before the mobile phone number of the user after replacing the mobile phone, and allows the operations of installation, unbinding and the like; after the user changes the mobile phone number, the user can know the application program related to the original mobile phone number and allow the user to perform operations such as installation, unbinding and the like.

Drawings

Fig. 1 is a schematic diagram of a terminal device according to one possible embodiment of the present invention.

Fig. 2 is a block diagram illustrating a partial structure of a terminal device according to one possible embodiment of the present invention.

Fig. 3 is a diagram illustrating a first system for obtaining a phone number associated with an application according to one possible embodiment of the present invention.

Fig. 4 is a diagram illustrating a second system for obtaining a phone number associated with an application according to one possible embodiment of the present invention.

Fig. 5 is a first login interface provided in accordance with one possible embodiment of the present invention.

Fig. 6 is a second login interface provided in accordance with one possible embodiment of the present invention.

Fig. 7 is a binding phone number interface provided according to one possible embodiment of the present invention.

Fig. 8 is a diagram of a change bound phone number interface provided in accordance with one possible embodiment of the present invention.

Fig. 9 is a first flowchart for obtaining association between a mobile phone number and an application according to one possible embodiment of the present invention.

Fig. 10 is a diagram illustrating a third system for obtaining a phone number associated with an application according to one possible embodiment of the invention.

Fig. 11 is a diagram illustrating a fourth system for obtaining a phone number associated with an application according to one possible embodiment of the invention.

Fig. 12 is a diagram illustrating a fifth system for obtaining association between a phone number and an application according to one possible embodiment of the invention.

Fig. 13 is a second flowchart for obtaining association between a mobile phone number and an application according to one possible embodiment of the present invention.

Fig. 14-1 is a mobile phone number association application program interface provided according to one possible embodiment of the present invention.

Fig. 14-2 is a table of mobile phone number association application data provided in accordance with one possible embodiment of the present invention.

FIG. 15 is a first interface for installing an application provided in accordance with one possible embodiment of the present invention.

FIG. 16 is a second interface for installing an application provided in accordance with one possible embodiment of the present invention.

FIG. 17 is a third interface for installing an application provided in accordance with one possible embodiment of the present invention.

FIG. 18 is a flowchart of an installation application provided in accordance with one possible embodiment of the present invention.

Fig. 19 is a first interface for unbinding a phone number according to one possible embodiment of the present invention.

Fig. 20 is a second interface for unbinding a phone number according to one possible embodiment of the present invention.

Fig. 21 is a flowchart of unbinding a mobile phone number according to one possible embodiment of the present invention.

Fig. 22 is a first interface for replacing a bound phone number according to one possible embodiment of the invention.

Fig. 23 is a flowchart for updating a correspondence between a mobile phone number and a terminal device according to a possible implementation manner of the present invention.

Fig. 24-1 is a data table provided in accordance with one possible embodiment of the present invention, in which a mobile phone number is mapped by a cloud account and associated with an application program.

Fig. 24-2 is a data table provided by the cloud account mapping method according to one possible embodiment of the present invention, where the data table is formed by mapping a third-party application account with an application program.

FIG. 25 is a third login interface provided in accordance with one possible embodiment of the present invention.

Detailed Description

The terminal device 100 according to the embodiment of the present invention may include a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, a TV, a wearable device, an AR, a VR device, and the like.

Taking the terminal device 100 as a mobile phone as an example, fig. 2 is a block diagram illustrating a part of the structure of the mobile phone 100 according to an embodiment of the present invention. Referring to fig. 2, the handset 100 includes, among other components, RF (Radio Frequency) circuitry 110, memory 120, other input devices 130, a display 140, sensors 150, audio circuitry 160, an I/O subsystem 170, a processor 180, and a power supply 190. Those skilled in the art will appreciate that the handset configuration shown in fig. 2 is not intended to be limiting and may include more or fewer components than those shown, or may combine certain components, or split certain components, or arranged in different components. Those skilled in the art will appreciate that the display 140 is part of a User Interface (UI) and that the cell phone 100 may include more or fewer User interfaces than shown.

The following describes the components of the mobile phone 100 in detail with reference to fig. 2:

the RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, receives downlink information of a base station and then processes the received downlink information to the processor 180; in addition, the data for designing uplink is transmitted to the base station. Typically, the RF circuit includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, an LNA (Low Noise Amplifier), a duplexer, and the like. In addition, the RF circuitry 110 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), email, SMS (Short Messaging Service), and the like.

The memory 120 may be used to store software programs and modules, and the processor 180 executes various functional applications and data processing of the mobile phone 100 by operating the software programs and modules stored in the memory 120. The memory 120 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone 100, and the like. Further, the memory 120 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

Other input devices 130 may be used to receive entered numeric or character information and generate key signal inputs relating to user settings and function controls of the handset 100. In particular, other input devices 130 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, a light mouse (a light mouse is a touch-sensitive surface that does not display visual output, or is an extension of a touch-sensitive surface formed by a touch screen), and the like. The other input devices 130 are connected to other input device controllers 171 of the I/O subsystem 170 and are in signal communication with the processor 180 under the control of the other input device controllers 171.

The display screen 140 may be used to display information entered by or provided to the user as well as various menus of the handset 100 and may also accept user input. The display screen 140 may include a display panel 141 and a touch panel 142. The Display panel 141 may be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like. The touch panel 142, also referred to as a touch screen, a touch sensitive screen, etc., may collect contact or non-contact operations (e.g., operations performed by a user on or near the touch panel 142 using any suitable object or accessory such as a finger or a stylus, and may also include body sensing operations; including single-point control operations, multi-point control operations, etc.) on or near the touch panel 142, and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 142 may include two parts, i.e., a touch detection device and a touch controller. The touch detection device detects the touch direction and gesture of a user, detects signals brought by touch operation and transmits the signals to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into information that can be processed by the processor, sends the information to the processor 180, and receives and executes a command sent by the processor 180. In addition, the touch panel 142 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, a surface acoustic wave, and the like, and the touch panel 142 may also be implemented by any technology developed in the future. Further, the touch panel 142 may cover the display panel 141, a user may operate on or near the touch panel 142 covered on the display panel 141 according to the content displayed on the display panel 141 (the display content includes, but is not limited to, a soft keyboard, a virtual mouse, virtual keys, icons, etc.), the touch panel 142 detects a touch operation on or near the touch panel 142, and transmits the touch operation to the processor 180 through the I/O subsystem 170 to determine the type of touch event to determine a user input, and then the processor 180 provides a corresponding visual output on the display panel 141 through the I/O subsystem 170 according to the type of touch event. Although in fig. 2, the touch panel 142 and the display panel 141 are two separate components to implement the input and output functions of the mobile phone 100, in some embodiments, the touch panel 142 and the display panel 141 may be integrated to implement the input and output functions of the mobile phone 100.

The handset 100 may also include at least one sensor 150, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that adjusts the brightness of the display panel 141 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 141 and/or the backlight when the mobile phone 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone 100, further description is omitted here.

The audio circuitry 160, speaker 161, and microphone 162 may provide audio identification between the user and the handset 100. The audio circuit 160 may transmit the converted signal of the received audio data to the speaker 161, and convert the signal into a sound signal for output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signals into signals, which are received by the audio circuit 160 and converted into audio data, which are output to the RF circuit 108 for transmission to, for example, another cell phone, or to the memory 120 for further processing.

The I/O subsystem 170 controls input and output of external devices, which may include other devices, an input controller 171, a sensor controller 172, and a display controller 173. Optionally, one or more other input control device controllers 171 receive signals from and/or transmit signals to other input devices 130, and other input devices 130 may include physical buttons (push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, a light mouse (a light mouse is a touch-sensitive surface that does not display visual output, or is an extension of a touch-sensitive surface formed by a touch screen). It is noted that other input control device controllers 171 may be connected to any one or more of the above-described devices. The display controller 173 in the I/O subsystem 170 receives signals from the display screen 140 and/or sends signals to the display screen 140. After the display screen 140 detects the user input, the display controller 173 converts the detected user input into an interaction with the user interface object displayed on the display screen 140, i.e., realizes a human-machine interaction. The sensor controller 172 may receive signals from one or more sensors 150 and/or transmit signals to one or more sensors 150.

The processor 180 is a control center of the mobile phone 100, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the mobile phone 100 and processes data by operating or executing software programs and/or modules stored in the memory 120 and calling data stored in the memory 120, thereby performing overall monitoring of the mobile phone. Alternatively, processor 180 may include one or more processing units; preferably, the processor 180 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 180.

The handset 100 also includes a power supply 190 (e.g., a battery) for powering the various components, which may preferably be logically connected to the processor 180 via a power management system to manage charging, discharging, and power consumption via the power management system.

Although not shown, the mobile phone 100 may further include a camera, a bluetooth module, etc., which will not be described herein.

Fig. 3 is a schematic diagram of a system for obtaining an association relationship between a mobile phone number and an application according to a possible embodiment of the present invention, where the system structure is shown in fig. 3: the system comprises at least one terminal device (also called "terminal") 100, at least one mobile operator 110, at least one authentication information processing server 120, at least one application server 130.

The association in this embodiment may be binding an account of an application program by using a mobile phone number, and further, may also be extended to binding an application program by using a third party application account. In some embodiments, an application may be registered by using a mobile phone number, for example, during the registration process, verification needs to be completed through the mobile phone number, and after the verification is successful, the application server 130 in the background of the application automatically binds the mobile phone number with the application. In some embodiments, the application program may be a mobile phone number dynamic login application program, that is, the application program is logged in only by using the verification code generated by the verification information processing server 120 each time the application program is logged in without setting a login password. For example, the application program is not bound to the mobile phone number, the mobile phone number is input in the login interface, the "obtaining verification code" is clicked, the application program is accessed after the verification is successful, and further, the application server 130 also generates a user name corresponding to the mobile phone number. In some embodiments, after registering with the mailbox, the mobile phone number needs to be bound based on safety and user experience considerations. In some embodiments, the account generated by the application server 130 corresponds to the bound phone number in a one-to-one relationship, i.e., the access rights of the phone number login and the user name login are the same.

In some embodiments, the terminal device 100 is a desktop computer, in some embodiments the terminal device 100 is portable (e.g., a laptop, tablet, or handheld device), and in some implementations the terminal device 100 has a touch-sensitive display (also referred to as a "touchscreen"). In some embodiments, the terminal device 100 has a Graphical User Interface (GUI), one or more processors, memory, and one or more modules, programs or sets of instructions stored in the memory for performing a plurality of functions. In some embodiments, the user interacts with the user interface primarily through finger contacts and gestures on the touch screen. In some embodiments, the terminal device 100 is installed with an application client or can access an application website (also called "application web page version"), and in some embodiments, the terminal device 100 may store the association relationship between the mobile phone number and the application, for example, may store a data table established by the association relationship.

In some embodiments, the mobile operator 110 refers to a department that owns license plates, spectrum resources, and infrastructure of radio access and switching networks, and is mainly responsible for operation and maintenance of mobile transmission networks, ensuring network service quality, and providing a mobile data service platform and user authentication, management, etc., such as china mobile, china telecom, and china unicom. In some embodiments, the mobile operator 110 may also be a virtual network operator. In some embodiments, the mobile operator 110 mainly sends the short message verification code, the voice message, and other verification information to the terminal 100 to complete the binding operation. In some embodiments, the mobile operator 110 is not necessary, for example, instant messages may be sent to the terminal 100 through the application server 130.

In some embodiments, the terminal device 100 sends a request for mobile phone number binding application to the application server 130, for example, the request may be that the user clicks "acquire short message verification code" after inputting a mobile phone number in the application binding mobile phone number interface. In some embodiments, the application server 130 sends an instruction carrying the mobile phone number of the user to the verification information processing server 120 according to the request for binding the mobile phone number sent by the terminal device 100. In some embodiments, the instruction carrying the mobile phone number of the user may also be sent to the verification information processing server 120 by the terminal device 100. In some embodiments, the verification information processing server 120 may process the verification information, and the processing of the verification information may be at least one of generating a short message verification code, generating voice verification information, and determining whether the mobile phone number is compliant, an operator to which the mobile phone number belongs, and the like. In some embodiments, the authentication information processing server 120 transmits the generated authentication information to the terminal device 100 through the mobile operator 110. In some embodiments, the authentication information processing server 120 may also transmit the generated authentication information to the application server 130. In some embodiments, the verification information processing server 120 may compare the generated verification information with the verification information input by the user to complete the binding operation, for example, the terminal device 100 receives the verification information input by the user and sends the verification information to the application server 130, and the application server 130 sends the verification information to the verification information server 120.

In some embodiments, the application server 130 may be an application client or a backend server of an application website to provide data for access or invocation by the application client, website. In some embodiments, the terminal device 100 sends a request for mobile phone number binding application to the application server 130, for example, the request may be that the user clicks "get verification code" after inputting the mobile phone number in the application binding interface. In some embodiments, the application server 130 processes the verification information according to the request of the terminal device 100, and the processing of the verification information may be any one of generating a short message verification code, generating voice verification information, and determining whether the mobile phone number is compliant, an operator to which the mobile phone number belongs, and the like. In some embodiments, the application server 130 sends the generated authentication information to the terminal device 100 through the mobile operator 110, and further, the application server 130 may send the generated authentication information directly to the terminal device 100, for example, sending an instant message through an application. In some embodiments, the application server 130 receives the authentication information sent by the terminal device 100, for example, the authentication information may be input by the user in an interface of the application client after receiving the authentication information sent by the mobile operator 100, or the authentication information sent by the mobile operator 100 may be automatically populated by the terminal device 100 after receiving the authentication information sent by the mobile operator 100. In some embodiments, the application server 130 compares the verification information sent by the terminal device 100 with the generated verification information, and completes the binding operation after the verification is successful, for example, the terminal device 100 prompts the user "you have successfully bound the mobile phone number 1320000000".

In some embodiments, the terminal device 100 receives a request for mobile phone number binding application, for example, the request may be that the user clicks "get verification code" after inputting a mobile phone number in the application binding interface. In some embodiments, the application client may also process the verification information, and the processing of the verification information may be at least one of generating a short message verification code, generating voice verification information, and determining whether the mobile phone number is compliant, and an operator to which the mobile phone number belongs. In some embodiments, the client-generated authentication information may be stored in an area where the user has access rights. In some embodiments, the application client compares the authentication information received by the terminal device 100 with the authentication information generated by the application client, and completes the binding operation after the authentication is successful, for example, the terminal device 100 prompts the user "you have successfully bound the mobile phone number 1320000000".

In some embodiments, after the mobile phone number and the application successfully complete the binding operation, the application server 130 stores the binding relationship between the mobile phone number and the application. In some embodiments, the application server 130 may also send the mobile phone number and the application binding relationship to the terminal device 100, and the mobile phone number and the application binding relationship are stored locally by the terminal device 100. Further, the terminal device 100 may also send the mobile phone number and the application program binding relationship to the network server.

Fig. 3 shows a system for establishing an association relationship between a mobile phone number and an application according to one possible embodiment of the present invention, which operates as follows:

step 1: a terminal device 100 with an application program client receives a request of a user for binding a mobile phone number;

the terminal device 100 sends a request for binding the mobile phone number requested by the user to the application server 130;

step 2: after receiving the request, the application server 130 sends an instruction carrying the user telephone number to the authentication information processing server 120.

And step 3: after receiving the instruction carrying the user phone number, the verification information processing server 120 generates verification information and sends the generated verification information to the application server 130;

and 4, step 4: the authentication information processing server 130 transmits the generated authentication information to the mobile operator 110;

and 5: the mobile operator 110 sends the authentication information to the terminal device 100;

step 6: the terminal device 100 receives the authentication information, and after the user completes the input operation or the automatic input, the terminal device 100 transmits the input authentication information to the application server 130;

the application server 130 compares the verification information input by the user with the generated verification information, completes the binding operation after the comparison is successful, and stores the binding relationship between the mobile phone number and the application program.

Fig. 4 is a schematic diagram of a system for obtaining an association relationship between a mobile phone number and an application according to one possible embodiment of the present invention, where the system includes at least one terminal device (also referred to as "terminal") 100 and at least one application server 130.

The operation of the system shown in fig. 4 is as follows:

step 2: after receiving the request, the application server 130 in the client background generates authentication information and sends the generated authentication information to the terminal device 100.

And step 3: a user inputs authentication information received by the terminal device 100 on a client login interface;

the terminal device 100 sends the verification information input by the user to the application server 130, the application server 130 compares the generated verification information with the verification information input by the user, and the binding operation is completed after the verification is successful;

the application server 130 stores the binding relationship between the mobile phone number and the application.

Fig. 5 is a diagram illustrating an interface 110 for a mobile phone number dynamic login application according to one possible embodiment of the present invention. In some embodiments, if the mobile phone number does not bind the application, that is, the application server 130 does not store the association relationship between the mobile phone number and the application, and after the binding is successfully verified as shown in fig. 3, the application server 130 automatically generates an application account (for example, a user name with login authority) associated with the mobile phone number, so that the user can login in the user name or the mobile phone number in the next login manner. In some embodiments, if the mobile phone number is already bound to the application, that is, the application server 130 stores the association relationship between the mobile phone number and the application, the login operation is performed on the interface 110, and the login has the same access right as the user name login after the authentication is successful.

In some embodiments, the mobile phone number can still log in through the user name even after being unbound with the application program. In some embodiments, the interface 110 also provides an application registration entry, and the user can register through a mobile phone number (e.g., mailbox, other application account, etc.). In some embodiments, the interface 110 also provides other login methods, such as third party application account login, e.g., WeChat, QQ, Facebook, etc.

Fig. 6 is a diagram of an account password login interface 120 according to one possible embodiment of the present invention. In some embodiments, the account password login interface 120 may provide login manners such as a mobile phone number, a mailbox, and a user name, for example, after the login is successful by using the mobile phone number, the system may generate a user name corresponding to the mobile phone number, and the user may log in by using both the mobile phone number and the user name. Similarly, after the mailbox is used for registration, the system can also generate a user name corresponding to the mailbox, namely, the login can be carried out in two modes of the mailbox and the user name. In some embodiments, a user name may also be generated by registering a mobile phone number and a mailbox at the same time.

In some embodiments, when an application is registered with a mobile phone number, the system may default to binding the application with the mobile phone number at the time of registration, for example, a mobile phone number binding application is required during the registration process. In some embodiments, even if the user name is generated after the application is registered with the mobile phone number, but the mobile phone number is not bound, further, the mobile phone number binding operation is required.

In some embodiments, a password forgetting entry is also provided, and the password can be retrieved through a mobile phone number, a mailbox, a security problem and the like. In some embodiments, other means of logging in are also provided, such as third party application account logging in, for example, WeChat, QQ, Facebook, and the like. In some embodiments, the login interface 120 also provides a user registration entry, and the user can register through a mobile phone number (e.g., a mailbox, other application account number, etc.).

In some embodiments, the application server 130 will typically also associate a third party application account (e.g., wechat) with which to log in an application (e.g., internet music). In some embodiments, the application server 130 may also generate an application account corresponding to the third party application account, and further, may also log in with the third application account directly without generating an application account.

Fig. 7 is a diagram illustrating a mobile phone number binding interface 130 according to one possible embodiment of the present invention, which is used for a user to perform a mobile phone number binding operation (e.g., register in a mailbox) after registering an application program for security and user experience. In some embodiments, if the mobile phone number is bound to a certain login account, the system prompts that the mobile phone number input by a user is bound by other accounts, and provides a corresponding password recovery entry or a bound mobile phone number entry which is unbound or replaced.

For example, in a scenario of changing a mobile phone number, an original bound mobile phone number and a mobile phone number that needs to be newly bound are input, and a binding change operation can be completed after verification is successful, in which case, the original mobile phone number and the application program are unbound (i.e., the application program cannot be logged in through the original mobile phone number but can still be logged in through the original user name), and after the new mobile phone number is successfully bound, a new corresponding relationship is established between the new mobile phone number and the original user name, i.e., the application program can be logged in through two modes, i.e., the new mobile phone number and the original user name, and have the same access right.

Fig. 9 is a flowchart for obtaining an association relationship between a mobile phone number and an application according to one possible embodiment of the present invention, which includes the following steps:

step S100: the terminal device 100 having the application client receives the request for binding the mobile phone number and sends the request to the application server 130 in the background.

Step S110: after receiving the request, the background application server 130 sends an instruction to the verification information processing server 120, where the instruction includes information such as a mobile phone number of the user;

step S120: the authentication information processing server 120 processes the authentication information (e.g., generates authentication information, determines whether the content is compliant, whether the mobile phone number is compliant, the operator to which the mobile phone number belongs), and transmits the authentication information to the application server 130;

the authentication information processing server 120 transmits the generated authentication information to the terminal device 100 through the mobile operator 110.

Step S130: the terminal device 100 receives the verification information, and the user finishes inputting the verification information, and the terminal device 100 sends the verification information input by the user to the application server 130;

the application server 130 compares the input authentication information with the authentication information generated by the authentication information processing server 120, completes the binding operation after the comparison is successful, and stores the binding relationship between the mobile phone number and the application in the application server 130.

Fig. 10 is a schematic diagram of a system for obtaining association between a mobile phone number and an application according to one possible embodiment of the present invention, where the system includes at least one terminal device 100, at least one mobile operator 110, at least one authentication information processing server 120, at least one application server 130, and at least one network server 140.

In some embodiments, the network program server 140-1 obtains the service identification information of the authentication information sent by the application server 130, and the service identification information can be used for the terminal device 100 to determine the application name by receiving the authentication information. In some embodiments, the service identifier of the application server 130, which sends the authentication information, may be any one or more of a sending source of the authentication information (the short message sending source of the internet cloud music is 1069125295163), a MAC address, an IP address, a server name, and authentication information required for unbinding. In some embodiments, the obtaining manner may be collected by a terminal manufacturer or the service identifier information may be reported or disclosed by an application manufacturer. In some embodiments, network server 140-1 may also store the telephone number in terminal device 100, for example, uploaded to network server 140-1 by terminal device 100. In some embodiments, the mobile phone number may be read by reading msisdn (mobile Subscriber International ISDN number) information of the mobile phone SIM card.

In some embodiments, when the terminal device 100 receives the verification information, the verification information is uploaded to the web server 140-1, and the web server 140-1 compares the received verification information with the stored application service identification information to analyze the application name. In some embodiments, network server 140-1 may associate and store the parsed application name with the stored cell phone number (e.g., a binding data table of cell phone numbers and applications may be established). In some embodiments, web server 140-1 may associate the parsed application name with the stored cell phone number and send to web server 140-2.

In some embodiments, network server 140-1 may also store a telephone number in terminal device 100 (e.g., a cell phone number may be uploaded by terminal device 100). In some embodiments, the terminal device 100 sends the received verification information to the web server 140-1, and the web server 140-1 parses the application name from the stored application service identification information, and further, the parsing may be performed by text recognition, judgment by comparison with the verification information sending source, and the like. In some embodiments, the application name corresponding to the verification information may also be parsed by the terminal device 100. In some embodiments, the network server 140-1 associates and stores the parsed application name with the mobile phone number that is already stored (for example, a data table of the mobile phone number corresponding to the application may be established), and further, the terminal device 100 may associate the parsed application name with the mobile phone number and send the association relationship between the two to the network server 140-1.

In some embodiments, the terminal device 100 may store the already acquired association relationship between the local phone number and the application name in the terminal device 100.

In some embodiments, the servers that collect service identification information of the application server 140 and store the binding relationships of the application and the phone number may also be the same (i.e., 140-1 and 140-2 are the same servers).

As shown in fig. 10, the operation steps of obtaining the association relationship between the mobile phone number and the application program are as follows:

step A: two network servers 140-1 and 140-2 are added on the basis of fig. 3. Before the application is bound to the cell phone number, the service identification information of the application server 130 is stored by the web server 140-1, so that the terminal device 100 can recognize the application source of the authentication information.

And B: when the terminal device 100 receives the authentication information, the authentication information is judged according to the service identification information stored in the network server 140-1 in step a, and the corresponding application program name is analyzed.

And C: the terminal device 100 associates the acquired local phone number with the parsed application name (for example, a binding data table of the phone number and the application may be established), and sends the association relationship (for example, a data table of a corresponding relationship between the phone number and the application name) to the network server storage 140-2 (for example, upload to "hua yun" may be performed according to user requirements).

Step D: the association relationship between the mobile phone number and the application program may be updated automatically or according to a request of the user, and sent to the terminal device 100, and operations such as installation and unbinding may be performed according to the binding relationship.

Fig. 11 is a schematic diagram of a system for establishing an association relationship between a mobile phone number and an application according to one possible embodiment of the present invention. The system comprises at least one terminal device 100, at least one mobile operator 110, at least one authentication information processing server 120, at least one application server 130, at least one web server 140.

As shown in fig. 11, the steps of the system for acquiring the association relationship between the mobile phone number and the application program are as follows:

step A: the service identification information of the application server 130 is stored by the web server 140, so that the terminal device 100 can recognize the source of the authentication information.

And B: when the terminal device 100 receives the verification information, the verification information is uploaded to the network server 140, and the network server 140-1 compares and analyzes the received verification information with the stored application program service identification information to analyze the application program name. Meanwhile, the terminal device 100 acquires the mobile phone number and sends the mobile phone number to the network server 140, and the network server 140 may associate the parsed application name with the stored mobile phone number (for example, a binding data table between the mobile phone number and the application may be established) and store the association.

And C: the association relationship between the mobile phone number and the application program may be updated automatically or according to a request of the user, and sent to the terminal device 100, and operations such as installation and unbinding may be performed according to the binding relationship.

Fig. 12 is a schematic diagram of a system for establishing an association relationship between a mobile phone number and an application according to one possible embodiment of the present invention. The system comprises at least one terminal device 100, at least one mobile operator 110, at least one authentication information processing server 120, at least one application server 130, at least one web server 140.

Fig. 12 is a diagram for obtaining association between a mobile phone number and an application according to a possible embodiment of the present invention, and the basic principle is as follows:

step A: the web server 140 collects and stores service identification information of the application server 130.

And B: when the terminal device 100 collects the authentication information, the application name is parsed based on the service identification information stored in the web server 140.

The terminal device 100 obtains the phone number of the local device and performs an association operation with the parsed application program name (for example, a binding data table of the phone number and the application program may be established), and the obtained phone number and the parsed application program name are stored locally in the terminal device 100.

And C: the association relationship between the mobile phone number and the application program can be updated automatically or according to the request of the user, and the operations of installation, unbinding and the like can be performed according to the binding relationship.

It should be noted that the steps in this embodiment are not strictly sequential, and may be performed simultaneously or adjusted. Similarly, some of the functional implementations of the present embodiment may also be implemented by multiple devices or one device for each function.

Fig. 13 is a flowchart for obtaining an association relationship between a mobile phone number and an application program binding according to a possible implementation manner of the present invention, which includes the following steps:

step S200: the terminal device 100 acquires the verification information (e.g., a verification code short message);

step S210: judging whether the information originates from an application program according to the service identification information of each application program stored in the network server 140, if not, processing the information according to the common information, and if so, entering the next step;

step S220: analyzing the application program corresponding to the verification information;

step S230: the telephone number of the terminal device 100 (in the case of a multi-card, the mobile phone number that received the authentication information) and the program name that transmitted the authentication information are extracted, and the association relationship between the two is uploaded to the network server 140 or the terminal device 100.

Step S240: the association relationship may be updated according to a request of a user or automatically, and sent to the terminal device 100, and the user may perform operations such as installation and unbinding according to the association relationship.

According to one possible implementation mode of the invention, a method for installing an application program based on the association relationship between a mobile phone number and the application program is provided. Fig. 14-1 is a user interface 150 for processing association between a mobile phone number and an application program according to one possible embodiment of the present invention, where a data source of the binding relationship between the mobile phone number and the application program of the user interface 150 is provided by the network server 140 (for example, the mobile phone number and application program association data table provided in fig. 14-2), and the obtained binding relationship between the mobile phone number and the application program is transmitted to the terminal device 100. In some embodiments, the user knows the case of a certain mobile phone number bound application in the terminal 100, i.e. an application that is not currently installed but has been bound by the terminal 100, or an application that has been installed but not bound by the terminal 100, or an application that has been bound and has been installed by the terminal 100. In some embodiments, the operation of replacing the bound mobile phone can be performed on the bound application program. In some embodiments, the plurality of programs may also be unbundled, installed, bound, changed in bound number, and the like.

In some embodiments, if the terminal device 100 has installed an application program bound to the mobile phone number (e.g., card 1), such as the wechat (wechat) program in fig. 14-1, the "install application" control is in an inoperable state (shown by a dashed box), and the "unbind" control is in a highlighted state (i.e., operable). In some embodiments, if the terminal device 100 does not install an application program that has been bound to the local phone number, such as the "Facebook" program in fig. 14-1, the "install application" control is highlighted (i.e., operable), and the "unbind" control is highlighted (i.e., operable). In some embodiments, if the terminal device 100 has installed but not bound applications, such as the QQ program in fig. 14-1, the "bound" control is in a highlighted state (i.e., operable) and the "install application" control is in an inoperable state (shown in dashed boxes). In some embodiments, the operation of changing the mobile phone number may also be performed on the already bound application program, for example, the wechat, "Facebook" (Facebook) "and mailbox program in fig. 14-1, where the" change number "control assumes a highlighted state, that is, represents an" operable state ".

In some embodiments, the user may perform an installation operation on the bound but not installed application based on the mobile phone number provided by the user interface 150 and the binding relationship of the application. Such as clicking on the "install application" control of the "Facebook" program, an application marketplace (e.g., App Store, etc.) interface 160 (shown in fig. 15) for application downloads may be linked to. In some embodiments, the download interface 150 of the application store shown in fig. 15 is entered and the download operation is performed directly. In some embodiments, it may also be desirable to click an "install" control in interface 150.

In some embodiments, clicking on the "install application" control of the "Facebook" program may also directly perform the download operation on the current interface. As in fig. 16, the user can display the download progress directly at the current interface 150 without entering the application marketplace or application store for downloading.

In some embodiments, as shown in fig. 14-1, there may be scenarios where the terminal device 100 has installed the program but is not bound, such as a QQ program, and the user may click on the "bind" control, i.e., enter an interface where the QQ program is bound to a phone number (e.g., enter a bind interface as shown in fig. 8). In some embodiments, it is also possible to jump to an application client or a web page for binding. In some embodiments, if the mobile phone number that has already been bound is re-bound, the system will remind "the mobile phone number that you input has already been bound by other account", and provide the corresponding password to retrieve the entry or unbind, change the entry of the bound mobile phone number.

In some embodiments, a method of installing a plurality of applications is also provided. Clicking the button of 'install multiple applications' as shown in fig. 14-1, popping up the setting interface 170 of 'install multiple applications' as shown in fig. 17, and downloading and installing multiple applications by clicking the radio box or the full box of the application to be installed. In some embodiments, the application store download interface may automatically and continuously pop up. In some embodiments, the progress of the download of the current application (e.g., Facebook program download in fig. 16) may also be displayed in the interface shown in fig. 14-1.

Fig. 18 is a flowchart of installing an application based on a mobile phone number and an application binding relationship according to one possible embodiment of the present invention, which includes the following steps:

step S310: acquiring an association relation data table (for example, fig. 14-2) between the established telephone numbers and the application programs;

step S320: acquiring a local application program list of the terminal device 100;

step S330: comparing the association relation data table with the local application installation list, acquiring the state of the uninstalled but already-bound application (for example, the state also includes the installed but not-bound application and the already-bound and already-installed application), and displaying the state on the setting interface 150 (for example, the "install application" control presents an operable state);

step S340: click an "install" icon (uninstalled but bound application) in the settings interface 150 to download or jump to an application store to download.

The method for installing the application program based on the binding relationship between the mobile phone number and the application program provided by this embodiment may be applicable to a scenario in which the mobile phone is replaced but the phone number is not replaced, or a scenario in which the application program that has been bound but deleted is reused, or a scenario in which the application program that has been installed but not bound is installed, in the above case, the terminal device 100 reads the locally installed application program list and compares the mobile phone number stored in the network server 140-1 with the application program association data table (as shown in fig. 14-2), may obtain the uninstalled but bound application program, the installed but unbound application program, and the installed and installed application program, and the user may perform an "install application" operation on the bound but uninstalled application program, and may also perform a "unbind" operation on the uninstalled but bound application program, it is also possible to perform a "bind" operation on an installed but unbound application and to perform a "unbind" operation on an installed and bound application.

According to a possible implementation manner of the invention, a method for unbinding the mobile phone number based on the association relationship between the mobile phone number and the application program is also provided.

In some embodiments, the user may perform an operation of unbinding the bound application (including the application downloaded or not downloaded by the terminal device 100) based on the binding relationship between the mobile phone number and the application provided by the mobile phone number association program interface 150 (fig. 14-1). As shown in fig. 19, the terminal device 100 provides a setting interface 180 for unbinding the mobile phone number, and after the mobile phone number association program interface 150 clicks the "unbinding" button, the terminal device enters the unbound interface 180 for the corresponding application program. In some embodiments, unbinding requires authentication, including but not limited to: phone number verification, name verification, question verification, etc. In some embodiments, the terminal device 100 sends the authentication information input by the user to the application server 130, and the application server 130 compares the received authentication information with the authentication information when the user registers, and completes the unbinding operation after the authentication is successful.

In some embodiments, web server 140-1 stores authentication information needed to unbind applications. In some embodiments, the web server 140-1 transmits the authentication information input by the user to the application server 130, for example, the authentication information may be transmitted to the web server 140-1 through the terminal device 100. Further, the application server 130 compares the received authentication information with the authentication information obtained when the user is registered, and completes the unbinding operation after the authentication is successful. In some embodiments, if a plurality of applications are unbound, the web server 140-1 sends the authentication information input by the user to the application server 130 corresponding to the application that needs to be unbound. In some embodiments, the unbinding of the application may also be the deletion of the association between the application and the mobile phone number in the network server 140-1, for example, the deletion of the association between the application and the mobile phone number.

In some implementations, such as clicking on the "unbind" control of the mailbox program as shown in fig. 14-1, popping up the unbound interface 180 (as in fig. 19), entering a phone number verification, name verification, question verification, etc., and after the verification is successful, unbinding the application is achieved. In some embodiments, authentication of the unbinding interface 180 includes, but is not limited to, answering security questions, passcodes, fingerprinting, passwords, and the like.

In some embodiments, an already bound and installed application (e.g., the WeChat program in FIG. 14-1) may also be unbound. In some embodiments, unbinding may also jump to an application client or web page.

In some embodiments, a method for unbinding multiple applications is also provided, such as clicking a "unbind multiple applications" button shown in fig. 14-1, popping up a setting interface 190 for "unbinding multiple applications" shown in fig. 20, clicking a radio box of an application to be unbound or fully selecting all the bound applications, and clicking a "unbind" button, so as to automatically and continuously pop up an unbind verification interface 180 shown in fig. 19 or pop up the unbound verification interface only once.

Fig. 21 is a flowchart of unbinding an application based on the binding relationship between a mobile phone number and the application, including the following steps:

step S400: clicking a unbinding button corresponding to the application needing to be unbound on a mobile phone number binding application interface 150 (shown in figure 14-1);

step S410: the application server 130 service identification information is obtained from the web server 140, including authentication information that needs to be filled in by the user. Such as new mobile phone number, original mobile phone number, verification problem 1, verification problem 2;

step S420: entering a 'unbinding' setting interface 140, and inputting the identity verification information of the unbound application program;

step S420: the terminal device 100 sends the authentication information input by the user to the application server 130, the application server 130 compares the authentication information of the unbinding application with the information of the user during registration, and the unbinding operation is completed after the authentication is successful.

The method for unbinding the application based on the mobile phone number and the application binding relationship provided by this embodiment may be applicable to a scenario in which the mobile phone number is changed but the terminal is not changed (for example, binding with a new mobile phone number may be required), or a scenario in which the bound application is not wanted to be used again, or a scenario in which the application is not installed but bound (for example, a short message received by the application is deleted and not wanted to be received), in which case, the terminal device 100 reads the locally installed application list and compares the locally installed application list with the bound application list (for example, the data table in fig. 14-2) in the network server, and may obtain the uninstalled but bound application, the installed but unbound application, the bound and installed application, and the user may perform an "install application" operation on the bound but uninstalled application, the method can also perform the operation of unbinding the uninstalled but bound application program, the operation of binding the installed but unbound application program, and the operation of unbinding the installed and bound application program.

The embodiment also provides a method for updating the binding relationship between the mobile phone number and the application program.

In some embodiments, as shown in fig. 14-1, the user may manually update the binding relationship between the mobile phone number and the application program, click the "refresh" button, the terminal device 100 reads the locally installed application program list, and re-compares the locally installed application program list with the data table of the binding relationship between the mobile phone number and the terminal device stored in the server 140, and obtains the uninstalled but already bound application program, the installed but unbound application program, and the already bound and installed application program after comparison, so as to update the data of the interface 150 for the user to operate.

The embodiment also provides a method for replacing the bound mobile phone number by the application program.

As shown in fig. 8, an interface 140 for changing the bound phone number is provided, and a "change number" button corresponding to an application program requiring a change of the bound phone number is clicked in a phone number association program interface 150 (as shown in fig. 14-1), so that the interface 140 for changing the bound phone number is entered, the original phone number and the phone number requiring binding are input, and the operation of changing the bound number can be completed after verification.

In some embodiments, as shown in fig. 22, an interface 200 for performing a rebinding operation on a plurality of already associated applications is further provided, the "rebinding multiple applications" control in the mobile phone number association application interface 150 in fig. 14-1 is clicked, the interface 200 for performing a rebinding operation is entered, a single application requiring a rebinding operation can be selected, or an application requiring a rebinding operation can be selected completely, and the interface 140 for performing a rebinding operation shown in fig. 14-1 can be entered after the button for performing a rebinding operation is clicked. In some embodiments, the unbinding verification interface 140 as shown in FIG. 8 may be automatically and continuously ejected or the unbinding verification interface 140 may be ejected only once.

The method can be suitable for a scene that a user changes the mobile phone number, the new mobile phone number is bound and the new mobile phone number is bound again by removing the binding relation between the original mobile phone number and the application program, data (such as chat records and account names) in the application program are kept unchanged, and the user can still log in the application program through the user name and the new mobile phone number.

The embodiment provides a method for prompting a user to perform operations such as binding and installation based on the change of the relation between a mobile phone number and a terminal device.

In some embodiments, the International Mobile Equipment Identity (IMEI) of the terminal device 100 is unique and fixed, and the IMEI is colloquially called "Mobile phone serial number" and is stored in the EEPROM of the Mobile phone. In some embodiments, the terminal device 100 may obtain or read a local mobile phone number, for example, read msisdn (mobile Subscriber International ISDN number) information of a mobile phone SIM card. In some embodiments, the data table of the mobile phone number and the mobile phone serial number may be established and stored in the network server 140-1, and further, may be stored in the terminal device 100.

In some implementations, if it is detected that the relationship between the terminal device 100 and the phone number is changed (for example, the phone number is not changed by changing a number or the phone number is not changed by changing a number), specifically, the corresponding relationship between the IMEI code of the terminal device 100 and the phone number of the mobile phone is changed, the binding relationship between the phone number and the application program is triggered and updated, for example, a prompt "find the changed mobile phone, please perform a binding operation between the phone number and the application program" is made, and the user may enter the setting interface 150 shown in fig. 14-1 after confirming.

As shown in fig. 23, a flowchart is provided for prompting a user to perform an association operation based on a change in the relationship between a mobile phone number and a terminal device:

step S510: the mobile phone number (unique identifier) and the IMEI of the mobile phone terminal (unique identifier of the mobile phone) change. The number is not changed, or the number is not changed by changing the number, and the next step is carried out;

step S520: the terminal equipment prompts a user, such as 'finding out the changed mobile phone number, please bind the application to the mobile phone number';

step S530: and popping up a setting interface after the determination, such as the interface 140 of the mobile phone number association application program in the figure 14-1.

According to a possible implementation manner of the invention, a method for mapping the association relationship between the mobile phone number and the application program based on the cloud account is further provided. As shown in fig. 10, the method for mapping the association relationship between the mobile phone number and the application program based on the cloud account includes:

step A: the web server 140-1 stores service identification information of the application server 130 so that the terminal device 100 can recognize an application source of the authentication information.

And C: the terminal device 100 associates the acquired local phone number with the parsed application name, sends the association relation (for example, a data table of a correspondence between the phone number and the application name) to the network server storage 140-2, and the network server 140-2 performs a mapping operation on the table of the association between the phone number and the application name and the cloud account of the user (for example, the data table shown in fig. 24-1).

Step D: the association relationship can be updated according to the user's request or automatically, and sent to the terminal device 100, and the user can perform operations such as installation, unbinding and the like according to the association relationship

Wherein, in some embodiments, the network program server 140-1 obtains the service identifier of the authentication information sent by the application program server 130, and the service identifier can be used for the terminal device 100 to determine the application program name by receiving the authentication information. In some embodiments, the service identifier of the application server 130, which sends the authentication information, may be at least one of a sending source of the authentication information (the short message sending source of the internet cloud music is 1069125295163), a MAC address, an IP address, a server name, and authentication information required for unbinding. In some embodiments, the obtaining manner may be collected by a terminal manufacturer or the service identifier information may be reported or disclosed by an application manufacturer. In some embodiments, network server 140-1 may also store the telephone number in terminal device 100, for example, uploaded to network server 140-1 by terminal device 100. In some embodiments, the mobile phone number may be read by reading msisdn (mobile Subscriber International ISDN number) information of the mobile phone SIM card.

In some embodiments, when the terminal device 100 receives the verification information, the verification information is uploaded to the network server 140-1, and the network server 140-1 performs comparison analysis on the received verification information and the stored application service identification information to analyze the application name. In some embodiments, network server 140-1 may associate and store the parsed application name with the stored cell phone number (e.g., a binding data table of cell phone numbers and applications may be established). In some embodiments, web server 140-1 may associate the parsed application name with the stored cell phone number and send to web server 140-2. The network server 140-2 performs mapping operation (for example, may be a data table as shown in fig. 24-1) on the association relationship table of the mobile phone number and the application name and the cloud account (for example, the cloud account) of the user, in this scenario, the terminal device 100 logs in the cloud account, and the user may know the relationship between the mobile phone number and the application.

In step C, in some embodiments, the network server 140-1 may further store a phone number in the terminal device 100 (for example, a mobile phone number may be uploaded by the terminal device 100), and the terminal device 100 uploads the parsed application name to the network server 140-1 and associates and stores the application name with the stored mobile phone number.

In step D, in some embodiments, the terminal device 100 may store the acquired association relationship between the local phone number and the application name in the terminal device 100.

In some embodiments, as shown in fig. 24-1, the cloud account of the user may map a plurality of cell phone numbers with application associations. In some embodiments, as shown in fig. 24-2, the association relationship between the mobile phone number and the application program can also be extended to the association between the third party application program account number and the application program. Further, the cloud account of the user may be mapped with a relationship between the third party application account and the application association.

In some embodiments, as shown in fig. 25, an interface 210 (e.g., interface 130 in fig. 5) is provided to remind the user that an application that needs to be bound currently is already mapped by other mobile phone number binding interfaces 210 (e.g., interface 130 in fig. 5), such as cloud account number 123456@ huawei.com of the user to the association relationship between mobile phone number 1 and application 1 and the association relationship between mobile phone number 2 and application 2, and when the user needs to bind application 1 by using mobile phone number 2, the system reminds that "according to your hua account number 123456@ huawei.com, your mobile phone number 1320000000 has been bound to the application, whether to confirm that the current number is bound continuously" and provide an entry of "continuously binding" and "login using the bound mobile phone number".

The embodiment can be applied to a scenario that a user changes a mobile phone and changes a mobile phone number at the same time, the cloud account first maps the association relationship between the original mobile phone number and the application program, after a new terminal device of the user logs in the cloud account, the mobile phone number association application program interface 150 shown in fig. 14-1 is updated through the association relationship in the cloud account and the installation list of the local application program, then the cloud account maps the association relationship between the new mobile phone number and the application program, and the mobile phone number association application program interface 150 shown in fig. 14-1 is updated.

The embodiments of the present invention can be arbitrarily combined to achieve different technical effects. Transmitted in or as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. Taking this as an example but not limiting: computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, the method is simple. Any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a Digital Subscriber Line (DSL), or a wireless technology such as infrared, radio, and microwave, the coaxial cable, the fiber optic cable, the twisted pair, the DSL, or the wireless technology such as infrared, radio, and microwave are included in the fixation of the medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy Disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

In short, the above description is only an example of the technical solution of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalents, improvements and the like made in accordance with the disclosure of the present invention are intended to be included within the scope of the present invention.

Claims

A method, comprising:

the method comprises the steps that terminal equipment displays a first login interface of a first application program, wherein the terminal equipment stores an incidence relation between a first mobile phone number and the first application program;

acquiring a second mobile phone number, and comparing the second mobile phone number with the first mobile phone number by the terminal equipment;

and when the second mobile phone number is different from the first mobile phone number, the terminal equipment prompts the user that the first mobile phone number is associated with the first application program.
The method of claim 1, wherein:

and when the second mobile phone number is different from the first mobile phone number, the terminal equipment allows the user to log in by using the second mobile phone number and/or the first mobile phone number.
A method, comprising;

the method comprises the steps that terminal equipment displays a first login interface of a first application program, and incidence relation between a first account and the first application program is stored in the terminal equipment;

acquiring a second account, wherein the second account is different from the first account;

when the second account is not associated with the first application program, the terminal equipment prompts a user that the second account is associated with the first application program, wherein the first account is associated with the second account through a third account.
The method of claim 3, wherein:

and when the second account is associated with the first application program, the terminal equipment logs in the first application program by using the second account.
A method, comprising:

the method comprises the steps that terminal equipment displays a first interface, wherein the first interface comprises an icon of a first application program and a control used for downloading the first application program;

the terminal equipment stores an incidence relation between a first mobile phone number and a first application program, and the first application program is not installed on the terminal equipment;

and acquiring a first operation aiming at the first interface, and skipping to a downloading interface of the first application program by the terminal equipment.
The method of claim 5, further comprising:

the first interface comprises a second application program icon and a control for logging in a second application program;

and the first mobile phone number is not associated with the second application program, and the second application program is installed on the terminal equipment.

And acquiring a second operation aiming at the first interface, and skipping to a login interface of a second application program by the terminal equipment.
The method as recited in claim 5 or 6, further comprising:

the first interface comprises a control for jumping to the second interface;

acquiring a third operation aiming at the first interface, and skipping to the second interface by the terminal equipment;

acquiring authentication information input by a user on the second interface;

and when the authentication is successful, the first mobile phone number and the first application program are disassociated.
The method of any one of claims 5 or 6, further comprising:

the first interface comprises a control for jumping to a third interface;

acquiring a fourth operation aiming at the first interface, and skipping to a third interface by the terminal equipment;

and acquiring a second mobile phone number, wherein the second mobile phone number is associated with the first application program, and the first mobile phone number is disassociated from the first application program, and the first mobile phone number is different from the second mobile phone number.
A computer program product comprising instructions for causing an electronic device to perform the method according to any of claims 1-8 when the computer program product is run on the electronic device.
A computer-readable storage medium comprising instructions that, when executed on an electronic device, cause the electronic device to perform the method of any of claims 1-8.
A terminal device, comprising:

a processor; and

a storage medium having stored thereon instructions for causing the terminal device to perform the method of any one of claims 1-8.