WO2019100223A1 - 判定手机号码与应用关联关系的方法 - Google Patents

判定手机号码与应用关联关系的方法 Download PDF

Info

Publication number
WO2019100223A1
WO2019100223A1 PCT/CN2017/112208 CN2017112208W WO2019100223A1 WO 2019100223 A1 WO2019100223 A1 WO 2019100223A1 CN 2017112208 W CN2017112208 W CN 2017112208W WO 2019100223 A1 WO2019100223 A1 WO 2019100223A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
mobile phone
phone number
terminal device
interface
Prior art date
Application number
PCT/CN2017/112208
Other languages
English (en)
French (fr)
Inventor
郭帅
喻念
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/112208 priority Critical patent/WO2019100223A1/zh
Priority to CN201780097035.3A priority patent/CN111373780A/zh
Publication of WO2019100223A1 publication Critical patent/WO2019100223A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a method for determining a relationship between a mobile phone number and an application.
  • Mobile terminals have become more and more multifunctional. Examples of such functions include data and voice communications, 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 to support game play, while other terminals are configured as multimedia players. As these functions become more diverse, mobile terminals can support more complex functions such as taking images or videos, reproducing music or video files, playing games, receiving broadcast signals, and the like.
  • the present invention provides a method for determining a relationship between a mobile phone number and an application, and provides various shortcut operations to provide a better experience for the user.
  • the embodiment of the present invention provides a method, including: the first server may be a background server of the first application, and the second server may store a correspondence between the service identifier of the first server and the first application; Receiving, by the terminal device, the first signal, the first signal indicating that the terminal device sends an association request to the first server, the terminal device may send a second signal to the first server, where the second signal includes the Correlating the request; the first server acquires the second signal, the first server sends a third signal to the third server, the third signal includes processing a verification information request; and the 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 device, where the first verification information includes a service identifier of the first server; The device accesses the second server, and the terminal device may obtain the service identifier of the first server; the terminal device acquires The first verification information identifies the first application by the service identifier of the first server included in the first verification information, where the
  • the terminal device may send an association relationship between the first mobile phone number and the first application to the second server, so as to implement timely backup of the association relationship.
  • the embodiment of the present invention provides a method, including: the first server may be a background server of the first application, and the second server may store an association relationship between the sending source of the first server and the first application;
  • the device may obtain the first mobile phone number, and the terminal device may send the first mobile phone number to the first server; the first server acquires the first mobile phone number, and the first server sends the first mobile phone number to the third server
  • the third server receives the first mobile phone number, the third server generates first verification information, and the third server sends the first verification information to the first mobile phone number of the terminal device;
  • the terminal The device may access the second server to obtain the sending source of the first server;
  • the terminal device obtains the first verification information, and the terminal device identifies the first application by using the sending source of the first verification information a program, wherein the first mobile phone number of the terminal device receives the first verification information;
  • the terminal device may be associated Said first phone number and the first application.
  • the application can be identified by the source of the verification information,
  • An embodiment of the present invention provides a method, including: displaying, by a terminal device, a first login interface of a first application, where the terminal device stores a first mobile phone number and the first application Correlation relationship; obtaining the second mobile phone number, the terminal device comparing the second mobile phone number with the first mobile phone number; when the second mobile phone number is different from the first mobile phone number, The terminal device prompts the user that the first mobile phone number has been associated with the first application. This embodiment can remind the user of the mobile phone number of the application that has been associated.
  • the terminal device when the second mobile phone number is different from the first mobile phone number, the terminal device allows the user to log in using the second mobile phone number and/or the first mobile phone number. To achieve different login methods for users.
  • the embodiment of the present invention provides a method, the method includes: the terminal device can display a first login interface of the first application, and the terminal device stores an association between the first account and the first application.
  • the second account is obtained, wherein the second account is different from the first account; when the second account is not associated with the first application, the terminal device prompts the user to use the first account
  • the first account is already associated, wherein the first account is associated with the second account by a third account. Users can be reminded of applications that have been associated with different accounts.
  • the second account when the second account has been associated with the first application, the second account is allowed to log in to the first application.
  • An embodiment of the present invention provides a method, including: displaying a first interface, where the terminal device stores a first mobile phone number and a first application association relationship, and the terminal device does not install the first application. a program: obtaining a first operation for the first interface, the terminal device performing a download operation on the first application. To enable users to download programs that are already associated but not installed.
  • the first operation for the first interface is obtained, and the terminal device jumps to the download interface of the third party store.
  • the terminal device jumps to the download interface of the third party store.
  • a first operation for the first interface is obtained, and the terminal device downloads a plurality of applications. To enable users to download programs that are already associated but not installed at one time.
  • the terminal device obtains a second operation for the first interface, the terminal device jumps to a login interface of the second application, wherein the first mobile phone number is not associated with the second application a program, and the terminal device is installed with the second application.
  • the terminal device is installed with the second application.
  • the terminal device jumps to the second interface; acquiring authentication information input by the user on the second interface; After the authentication succeeds, the first mobile phone number is disassociated from the first application; the mobile phone number is disassociated from the application.
  • the fourth operation is obtained for the first interface, the terminal device jumps to the third interface; the second mobile phone number is acquired, and the second mobile phone number is associated with the first application.
  • the first mobile phone number is disassociated from the first application, wherein the first mobile phone number is different from the second mobile phone number. To enable users to replace the associated mobile phone number.
  • An embodiment of the present invention provides a terminal device, including: a processor; and a storage medium, wherein the storage medium stores an instruction, and the instruction causes the terminal device to perform the foregoing method.
  • Embodiments of the present invention provide a computer program product comprising instructions, wherein when the computer program product runs on an electronic device, the terminal device is caused to perform the above method.
  • the embodiment of the invention provides a computer readable storage medium, comprising instructions, wherein when the instruction is run on an electronic device, the terminal device is caused to perform the above method.
  • the embodiment of the present invention can realize the operation that the user has associated with the mobile phone number after the user replaces the mobile phone, and allows installation, unbinding, etc.; after the user replaces the mobile phone number, the original can be known.
  • the mobile phone number is associated with the application and allows installation, unbinding, etc.
  • FIG. 1 is a schematic diagram of a terminal device according to a possible implementation manner of the present invention.
  • FIG. 2 is a block diagram showing a partial structure of a terminal device provided by a possible embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a first system for acquiring a phone number associated with an application according to a possible embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a second system for obtaining a phone number associated with an application according to a possible embodiment of the present invention.
  • FIG. 5 is a first login interface provided in accordance with a possible embodiment of the present invention.
  • FIG. 6 is a second login interface provided according to a possible implementation of the present invention.
  • FIG. 7 is a binding mobile phone number interface provided according to a possible implementation of the present invention.
  • FIG. 8 is a diagram of a replacement binding mobile number interface provided according to a possible embodiment of the present invention.
  • FIG. 9 is a first flowchart of obtaining a mobile phone number and an application association according to a possible embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a third system for obtaining a phone number associated with an application according to a possible embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a fourth system for acquiring a phone number associated with an application according to a possible embodiment of the present invention.
  • FIG. 12 is a schematic diagram of a fifth system for obtaining a phone number associated with an application according to a possible embodiment of the present invention.
  • FIG. 13 is a second flowchart of acquiring a mobile phone number and an application according to a possible embodiment of the present invention.
  • FIG. 14-1 is a mobile phone number association application interface provided according to a possible implementation manner of the present invention.
  • 14-2 is a mobile phone number association application data table provided in accordance with a possible embodiment of the present invention.
  • FIG. 15 is a first interface of an installation application provided according to a possible embodiment of the present invention.
  • FIG. 16 is a second interface of installing an application provided according to a possible embodiment of the present invention.
  • FIG. 17 is a third interface of an installation application provided according to a possible embodiment of the present invention.
  • FIG. 19 is a first interface for unbinding a mobile phone number according to a possible implementation of the present invention.
  • FIG. 20 is a second interface for unbinding a mobile phone number according to a possible implementation of the present invention.
  • 21 is a flow chart of unbinding a mobile phone number according to a possible implementation of the present invention.
  • FIG. 22 is a first interface for replacing a bound mobile phone number according to a possible implementation of the present invention.
  • FIG. 23 is a flowchart of updating a correspondence between a mobile phone number and a terminal device according to a possible implementation manner of the present invention.
  • Figure 24-1 shows a data table associated with an application associated with a cloud account mapping mobile number provided in accordance with one possible embodiment of the present invention.
  • Figure 24-2 shows a data table associated with a cloud account mapping third party application account and an application according to a possible embodiment of the present invention.
  • Figure 25 is a third login interface provided in accordance with one possible embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a terminal device provided according to a possible embodiment of the present invention.
  • the terminal device 100 may include a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), an in-vehicle computer, a TV, a wearable device, an AR, and a VR device. Wait.
  • a PDA Personal Digital Assistant
  • POS Point of Sales
  • FIG. 2 is a block diagram showing a part of the structure of the mobile phone 100 related to the embodiment of the present invention.
  • the mobile phone 100 includes an RF (Radio Frequency) circuit 110, a memory 120, other input devices 130, a display screen 140, a sensor 150, an audio circuit 160, an I/O subsystem 170, a processor 180, and a power supply. 190 and other components.
  • RF Radio Frequency
  • the structure of the mobile phone shown in FIG. 2 does not constitute a limitation to the mobile phone, and may include more or less components than those illustrated, or combine some components, or split some components, or Different parts are arranged.
  • display 140 is a User Interface (UI) and that handset 100 may include more or fewer user interfaces than illustrated.
  • UI User Interface
  • the components of the mobile phone 100 will be specifically described below with reference to FIG. 2:
  • the RF circuit 110 can be used for transmitting and receiving information or during a call, and receiving and transmitting the signal. Specifically, after receiving the downlink information of the base station, the processor 180 processes the data. In addition, the uplink data is designed to be sent to the base station.
  • RF circuits include, but are not limited to, an antenna, at least one amplifier, a transceiver, a coupler, an LNA (Low Noise Amplifier), a duplexer, and the like.
  • RF circuitry 110 can also communicate with the network and other devices via wireless communication.
  • the wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access). , Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), e-mail, SMS (Short Messaging Service), and the like.
  • the memory 120 can 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 running software programs and modules stored in the memory 120.
  • the memory 120 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application 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 be stored. Data created according to the use of the mobile phone 100 (such as audio data, phone book, etc.).
  • memory 120 can include high speed random access memory, and can 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 can be used to receive input numeric or character information, as well as generate key signal inputs related to user settings and function controls of the handset 100.
  • other input devices 130 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and light mice (the light mouse is not sensitive to display visual output).
  • function keys such as volume control buttons, switch buttons, etc.
  • trackballs mice, joysticks, and light mice (the light mouse is not sensitive to display visual output).
  • Other input devices 130 are coupled to other input device controllers 171 of I/O subsystem 170 for signal interaction with processor 180 under the control of other device input controllers 171.
  • the display screen 140 can be used to display information input by the user or information provided to the user as well as various menus of the mobile phone 100, and can also accept user input.
  • the specific display screen 140 may include a display panel 141 and a touch panel 142.
  • the display panel 141 can be configured by using 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., can collect contact or non-contact operations on or near the user (eg, the user uses any suitable object or accessory such as a finger, a stylus, etc. on the touch panel 142.
  • the operation in the vicinity of the touch panel 142 may also include a somatosensory operation; the operation includes a single-point control operation, a multi-point control operation, and the like, and drives the corresponding connection device according to a preset program.
  • the touch panel 142 may include two parts: a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation and posture of the user, and detects a signal brought by the touch operation, and transmits a signal to the touch controller; the touch controller receives the touch information from the touch detection device, and converts the signal into a processor. The processed information is sent to the processor 180 and can receive commands from the processor 180 and execute them.
  • the touch panel 142 can be implemented by using various types such as resistive, capacitive, infrared, and surface acoustic waves, and the touch panel 142 can be implemented by any technology developed in the future.
  • the touch panel 142 can cover the display panel 141, and the user can display the content according to the display panel 141 (the display content includes, but is not limited to, a soft keyboard, a virtual mouse, a virtual button, an icon, etc.) on the display panel 141. The operation is performed on or near the covered touch panel 142. After the touch panel 142 detects a touch operation on or near it, the touch panel 142 transmits to the processor 180 through the I/O subsystem 170 to determine the type of the touch event to determine the user input.
  • the processor 180 then provides a corresponding visual output on the display panel 141 via the I/O subsystem 170 in accordance with the type of touch event.
  • the touch panel 142 and the display panel 141 are two separate components to implement the input and input functions of the mobile phone 100, in some embodiments, the touch panel 142 may be integrated with the display panel 141. The input and output functions of the mobile phone 100 are implemented.
  • the handset 100 can also include at least one type of sensor 150, such as a light sensor, motion sensor, and other sensors.
  • the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 141 according to the brightness of the ambient light, and the proximity sensor may close the display panel 141 when the mobile phone 100 moves to the ear. / or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.
  • the mobile phone 100 can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors, here Let me repeat.
  • the audio circuit 160, the speaker 161, and the microphone 162 can provide an audio identity between the user and the handset 100.
  • the audio circuit 160 can transmit the converted audio data to the speaker 161 for conversion to the sound signal output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into a signal, which is received by the audio circuit 160.
  • the audio data is converted to audio data, which is then output to the RF circuit 108 for transmission to, for example, another mobile phone, or the audio data is output to the memory 120 for further processing.
  • the I/O subsystem 170 is used to control external devices for input and output, and may include other device input controllers 171, sensor controllers 172, and display controllers 173.
  • one or more other input control device controllers 171 receive signals from other input devices 130 and/or send signals to other input devices 130.
  • Other input devices 130 may include physical buttons (press buttons, rocker buttons, etc.) , dial, slide switch, joystick, click wheel, light mouse (light mouse is a touch-sensitive surface that does not display visual output, or an extension of a touch-sensitive surface formed by a touch screen). It is worth noting that other input control device controllers 171 can be connected to any one or more of the above devices.
  • Display controller 173 in I/O subsystem 170 receives signals from display 140 and/or transmits signals to display 140. After display screen 140 detects user input, display controller 173 converts the detected user input into an interaction with a user interface object displayed on display screen 140, That is to achieve human-computer interaction.
  • Sensor controller 172 can receive signals from one or more sensors 150 and/or send signals to one or more sensors 150.
  • the processor 180 is the control center of the handset 100, connecting various portions of the entire handset with various interfaces and lines, by running or executing software programs and/or modules stored in the memory 120, and recalling data stored in the memory 120, The various functions and processing data of the mobile phone 100 are executed to perform overall monitoring of the mobile phone.
  • the processor 180 may include one or more processing units; preferably, the processor 180 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like.
  • the modem processor primarily handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 180.
  • the handset 100 also includes a power source 190 (such as a battery) that supplies power to the various components.
  • a power source 190 such as a battery
  • the power source can be logically coupled to the processor 180 via a power management system to manage functions such as charging, discharging, and power consumption through the power management system.
  • the mobile phone 100 may further include a camera, a Bluetooth module, and the like, and details are not 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 implementation manner of the present invention.
  • the system structure is as shown in FIG. 3: the system includes at least one terminal device (also referred to as a “terminal”). 100.
  • At least one mobile operator 110 At least one authentication information processing server 120, and at least one application server 130.
  • the "association" in this embodiment may be that the account number of an application is bound by using the mobile phone number, and further, the third-party application account may be extended to bind an application.
  • an application may be registered by using a mobile phone number. For example, in the process of registration, the verification needs to be completed by using the mobile phone number. After the verification is successful, the application server 130 in the background of the application automatically uses the mobile phone number and the application. Program binding. In some embodiments, it may be a mobile phone number dynamic login application, that is, there is no need to set a login password, and each time the application is logged in, only the verification code generated by the verification information processing server 120 is used to log in.
  • the mobile phone number is not bound to the application, the mobile phone number is input on the login interface, and the “acquisition verification code” is clicked, and the application is accessed after the verification is successful.
  • the application server 130 also generates a user corresponding to the mobile phone number. name.
  • the mobile phone number needs to be bound based on security and user experience considerations.
  • the account generated by the application server 130 has a one-to-one correspondence with the bound mobile phone number, that is, the access rights of the mobile phone number login and the user name login are the same.
  • the terminal device 100 is a desktop computer, and in some embodiments, the terminal device 100 is portable (eg, a laptop, tablet, or handheld device), and in some implementations, the terminal device 100 device Has a touch sensitive display (also known as a "touch screen").
  • 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 memory for performing multiple functions. .
  • GUI graphical user interface
  • the user interacts with the user interface primarily through finger contacts and gestures on the touch screen.
  • the terminal device 100 is installed with an application client or has access to an application website (also referred to as an "application web version").
  • the terminal device 100 can store between the mobile number and the application. The association relationship, for example, can store a data table established by the relationship between the two.
  • the mobile operator 110 refers to a department that owns a mobile service license, a spectrum resource, and a wireless access and switching network infrastructure, and is mainly responsible for the operation and maintenance of the mobile transmission network, guarantees the quality of the network service, and provides mobile data.
  • Business platform and user authentication, management, etc. for example, China Mobile, China Telecom, and China Unicom.
  • mobile operator 110 may also be a virtual network operator.
  • the mobile operator 110 mainly sends verification information such as a short message verification code and voice information to the terminal 100 to complete the binding operation.
  • the mobile operator 110 is not necessary, for example, the instant messaging information can be sent to the terminal 100 through the application server 130.
  • the terminal device 100 sends a request for the mobile phone number binding application to the application server 130.
  • the request may be after the user inputs the mobile phone number in the application binding mobile phone number interface, and clicks “Get SMS verification code”. ".
  • the application server 130 sends an instruction carrying the user's mobile number to the verification information processing server 120 in accordance with the request to bind the mobile number transmitted by the terminal device 100.
  • the instruction carrying the user's mobile number may also be sent by the terminal device 100 to the verification information processing server 120.
  • the verification information processing server 120 may process the verification information, and the processing verification information may be at least one of generating a short message verification code, voice verification information, and determining whether the mobile phone number is compliant, the operator to which the mobile phone number belongs, and the like.
  • the verification information processing server 120 transmits the generated verification information to the terminal device 100 through the mobile operator 110.
  • the verification information processing server 120 can also send the generated verification information to the application server 130.
  • 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. The application server 130 then sends the verification information to the verification information server 120.
  • the application server 130 can be an application client or a background server of an application website to serve application clients, website access, or call data.
  • the terminal device 100 sends a request for the mobile number binding application to the application server 130.
  • the request may be that the user clicks “Get Verification Code” after inputting the mobile phone number in the application binding interface.
  • the application server 130 processes the verification information according to the request of the terminal device 100, and the processing verification information may be an SMS verification code, voice verification information, and whether the mobile phone number is compliant, the carrier to which the mobile phone number belongs, and the like.
  • the application server 130 sends the generated verification information to the terminal device 100 through the mobile operator 110.
  • the application server 130 may directly send the generated verification information directly to the terminal device 100, for example, Send an instant message through the app.
  • the application server 130 receives the verification information sent by the terminal device 100, for example, may be input by the user in the interface of the application client after receiving the verification information sent by the mobile operator 100, and may also be The terminal device 100 automatically fills in after receiving the verification information sent by the mobile operator 100.
  • 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 succeeds. For example, the terminal device 100 prompts the user that “you have successfully bound the mobile phone number 1320000000. ".
  • the terminal device 100 receives a request for a mobile phone number binding application.
  • the request may be that the user clicks “Get Verification Code” after inputting the mobile phone number in the application binding interface.
  • the verification information may also be processed by the application client, and the processing verification information may be at least one of generating a short message verification code, voice verification information, and determining whether the mobile phone number is compliant, the operator to which the mobile phone number belongs, and the like.
  • the authentication information generated by the client may be stored in an area in which the user has access rights.
  • the application client compares the verification information received by the terminal device 100 with the verification information generated by the application client, and completes the binding operation after the verification succeeds. For example, the terminal device 100 prompts the user that “you have successfully tied. Set the mobile phone number 1320000000".
  • the application server 130 stores the above mobile phone number and application binding relationship. 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 terminal device 100 stores it locally. Further, the terminal device 100 can also send the mobile phone number and the application binding relationship to the network server.
  • the system for establishing a relationship between a mobile phone number and an application according to a possible implementation manner of the present invention as shown in FIG. 3 is as follows:
  • Step 1 The terminal device 100 having the application client receives a request for the user to bind the mobile phone number
  • the terminal device 100 sends a request for binding the mobile phone number to the application server 130;
  • Step 2 After receiving the request, the application server 130 transmits an instruction carrying the user's telephone number to the verification information processing server 120.
  • Step 3 After the verification information processing server 120 receives the instruction carrying the user's telephone number, generate verification information, and send the generated verification information to the application server 130;
  • Step 4 The verification information processing server 130 sends the generated verification information to the mobile operator 110;
  • Step 5 The mobile operator 110 sends the verification information to the terminal device 100;
  • Step 6 The terminal device 100 receives the verification information, after the user completes the input operation or automatically inputs, the terminal device 100 sends the input verification 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.
  • the system includes at least one terminal device (also referred to as “terminal”) 100, and at least one application server 130. .
  • Step 1 The terminal device 100 having the application client receives a request for the user to bind the mobile phone number
  • the terminal device 100 sends a request for binding the mobile phone number to the application server 130;
  • Step 2 After receiving the request, the application server 130 in the client background generates verification information, and sends the generated verification information to the terminal device 100.
  • Step 3 The user inputs the verification information received by the terminal device 100 on the client login interface.
  • the terminal device 100 sends the verification information input by the user to the application server 130, and the application server 130 compares the generated verification information with the verification information input by the user, and completes the binding operation after the verification succeeds;
  • the application server 130 stores the binding relationship between the mobile phone number and the application.
  • FIG. 5 is an interface 110 of a mobile phone number dynamic login application according to a possible embodiment of the present invention.
  • the application server 130 does not store the association relationship between the mobile phone number and the application, and after the authentication is successful according to the binding mode as shown in FIG. 3, the application server 130 is successful.
  • An application account associated with the mobile phone number (for example, a user name with login authority) is automatically generated, so that the user can log in by using the user name or the mobile phone number for the next login.
  • the application server 130 stores the association relationship between the mobile phone number and the application, and performs a login operation at the interface 110, and the login has the same access right as the user name login. .
  • the interface 110 also provides an application registration portal, which can be registered by the user via a mobile number (also a mailbox, other application account, etc.).
  • the interface 110 also provides other login methods, such as third party application account logins such as WeChat, QQ, and Facebook.
  • FIG. 6 is an account password login interface 120 provided according to a possible implementation manner of the present invention.
  • the account password login interface 120 can provide a login method such as a mobile phone number, a mailbox, a user name, etc., for example, using a mobile phone number.
  • the system can generate a user name corresponding to the mobile phone number, and the user can log in by using the mobile phone number and the user name.
  • the system can also generate a username corresponding to the mailbox, that is, you can log in through the mailbox and the user name.
  • the system when the application is registered with the mobile phone number, the system will bind the application to the mobile phone number at the time of registration by default, for example, the mobile phone number binding application is required during the registration process. In some embodiments, even after the application is registered with the mobile phone number, for example, the username is generated, but the mobile phone number is not bound, and further, the mobile phone number binding operation is required.
  • a "forgot password" entry is also provided, and the password can be retrieved by means of a mobile phone number, a mailbox, a security question, and the like.
  • other ways to log in such as WeChat, QQ, Facebook, etc., are also logged in.
  • the login interface 120 also provides a user registration portal, and the user can register via a mobile phone number (which can also be a mailbox, other application account, etc.).
  • the application server 130 (eg, Netease Cloud Music) is logged using a third party application account (eg, WeChat), which is typically also associated with the application server 130.
  • the application server 130 may also generate an application account corresponding to the third-party application account. Further, the application server 130 may directly log in with the third application account without generating an application account.
  • the binding mobile phone number interface 130 is provided according to a possible implementation manner of the present invention.
  • the mobile phone number binding operation is required based on security, user experience, and the like (for example, when registering with the email address) ).
  • the system will prompt “the mobile phone number you entered has been bound by another account”, and provide the corresponding password to retrieve the entry or unbind or replace. Bind the phone number entry.
  • FIG. 8 is an interface 140 for an application to replace a bound mobile phone number according to a possible implementation of the present invention.
  • an original bound mobile phone number and a mobile phone that needs a new binding After the number is verified, the binding operation can be completed.
  • the original mobile phone number is unbound from the application (that is, the original mobile phone number cannot be used to log in to the application, but the original user name can still be logged in).
  • the new mobile phone number After the new mobile phone number is successfully bound, the new mobile phone number establishes a new correspondence with the original user name, that is, the new mobile phone number and the original user name can be used to log in to the application, and have the same access rights.
  • FIG. 9 is a flowchart of obtaining a relationship between a mobile phone number and an application according to a possible implementation manner of the present invention, and the steps are as follows:
  • Step S100 The terminal device 100 having the application client receives the binding mobile phone number request and sends the request to the background application server 130.
  • 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 the mobile phone number of the user;
  • Step S120 The verification information processing server 120 processes the verification information (for example, generates verification information, determines whether the content is compliant, whether the mobile phone number is compliant, the operator to which the mobile phone number belongs), and sends the verification information to the application server 130;
  • the verification information processing server 120 transmits the generated verification information to the terminal device 100 through the mobile operator 110.
  • Step S130 the terminal device 100 receives the verification information, the user completes the input 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 verification information with the verification information generated by the verification 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 acquiring a mobile phone number and an application association relationship according to a possible embodiment of the present invention.
  • 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, at least one web server 140.
  • the network program server 140-1 obtains service identification information that the application server 130 sends the verification information, and the service identification information can be used by the terminal device 100 to determine the application name by receiving the verification information.
  • the service identifier of the application server 130 that sends the verification information may be the source of the verification information (the source of the short message of the Netease cloud music is 1069125295163), the MAC address, the IP address, the server name, and the unbundling required. Authentication information, etc., or any one or more of them.
  • the manner of obtaining may be by collecting by the terminal manufacturer or by the application vendor to report or disclose the service identification information and the like.
  • the web server 140-1 may also store a phone number in the terminal device 100, such as uploaded by the terminal device 100 to the web server 140-1.
  • the method of reading the mobile phone number may be by reading the MSISDN (Mobile Subscriber International ISDN number) information of the mobile phone SIM card.
  • the verification information 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 compares the received verification information with the stored application service identification information. Parse the application name.
  • the web server 140-1 may associate the parsed application name with the stored mobile phone number (eg, a binding data table of the mobile phone number and application may be established) and stored. In some embodiments, the web server 140-1 can associate the parsed application name with the stored mobile number and send it to the web server 140-2.
  • the web server 140-1 may also store a phone number in the terminal device 100 (eg, the mobile phone number may be uploaded by the terminal device 100).
  • the terminal device 100 transmits the received verification information to the network server 140-1, and the network server 140-1 parses the application name according to the stored application service identification information. Further, the parsing manner may be text recognition. It is judged by comparing the source of the verification information.
  • the application name corresponding to the verification information may also be parsed by the terminal device 100.
  • the web server 140-1 associates the parsed application name with the already stored mobile phone number (eg, may establish a data table corresponding to the application number of the mobile phone number), and may further store the terminal number. The device 100 associates the parsed application name with the mobile phone number and sends the association relationship between the two to the network server 140-1.
  • the terminal device 100 may store the association relationship between the local phone number that has been acquired and the application name in the terminal device 100.
  • the server identifying the service identification information of the application server 140 and the server storing the application-to-phone number binding relationship may also be the same (ie, 140-1 and 140-2 are the same server).
  • the steps for obtaining the mobile phone number and application association system are as follows:
  • Step A Two network servers 140-1 and 140-2 are added on the basis of FIG. Before the mobile phone number binding application, the network server 140-1 stores the service identification information of the application server 130, so that the terminal device 100 can recognize the application source of the verification information.
  • Step B When the terminal device 100 receives the verification information, it determines the verification information according to the service identification information stored in the network server 140-1 in step A, and parses out the corresponding application name.
  • Step C The terminal device 100 associates the obtained local mobile phone number with the parsed application name (for example, a binding data table of the mobile phone number and the application may be established), and the association relationship is
  • the data table which may be a correspondence between the mobile phone number and the application name, is sent to the network server storage 140-2 (for example, it can be uploaded to the "Huawei Cloud" according to the user's needs).
  • Step D The association relationship between the mobile phone number and the application program may be automatically updated according to the user's request, and sent to the terminal device 100, and the operations such as installing and unbinding may be performed according to the binding relationship.
  • FIG. 11 is a schematic diagram of a system for establishing a relationship between a mobile phone number and an application according to a possible implementation manner of the present invention.
  • 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.
  • the steps of the system for obtaining the association relationship between the mobile phone number and the application are as follows:
  • Step A The service identifier information of the application server 130 is stored by the network server 140, so that the terminal device 100 can recognize the source of the verification information.
  • Step B When the terminal device 100 receives the verification information, upload the verification information to the network server 140, and the network server 140-1 compares the received verification information with the stored application service identification information, and parses the application name. . At the same time, the terminal device 100 acquires the mobile phone number and sends it to the network server 140, and the network server 140 can associate the parsed application name with the stored mobile phone number (for example, a binding data table of the mobile phone number and the application can be established). storage.
  • the terminal device 100 acquires the mobile phone number and sends it to the network server 140, and the network server 140 can associate the parsed application name with the stored mobile phone number (for example, a binding data table of the mobile phone number and the application can be established). storage.
  • Step C The association relationship between the mobile phone number and the application program may be automatically updated according to the user's request, and sent to the terminal device 100, and the operations such as installing and unbinding may be performed according to the binding relationship.
  • FIG. 12 is a schematic diagram of a system for establishing a relationship between a mobile phone number and an application according to a possible implementation manner of the present invention.
  • 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.
  • FIG. 12 is a schematic diagram of the relationship between acquiring a mobile phone number and an application according to a possible embodiment of the present invention, and the basic principle thereof is as follows:
  • Step A The web server 140 collects and stores the service identification information of the application server 130.
  • Step B When the terminal device 100 collects the verification information, the application name is parsed according to the service identification information stored by the network server 140.
  • the terminal device 100 acquires an association operation between the telephone number of the local device and the parsed application name (for example, a binding data table of the mobile phone number and the application program can be established) and is stored locally in the terminal device 100.
  • the parsed application name for example, a binding data table of the mobile phone number and the application program can be established
  • Step C According to the user's request or automatically update the association relationship between the mobile phone number and the application, the installation and unbinding can be performed according to the binding relationship.
  • FIG. 13 is a flowchart of obtaining an association relationship between a mobile phone number and an application binding according to a possible implementation manner of the present invention, and the steps are as follows:
  • Step S200 The terminal device 100 acquires verification class information (for example, a verification code short message);
  • Step S210 determining, according to the service identification information of each application stored in the network server 140, whether the information is derived from an application, if not, processing according to ordinary information, and if it is determined that the information is from the application, entering the next One step
  • Step S220 Parsing an application corresponding to the verification information
  • Step S230 extracting the telephone number of the terminal device 100 (in the case of multiple cards, may be the mobile phone number receiving the verification information) and the program name of transmitting the verification information, and uploading the association relationship between the two to the network server 140 or In the terminal device 100.
  • Step S240 The association relationship may be automatically updated according to the request of the user, and sent to the terminal device 100, and the user may perform operations such as installation and unbinding according to the association relationship.
  • a method for installing an application based on a mobile phone number and an application association relationship is provided.
  • 14-1 is a user interface 150 for processing a mobile phone number and an application association relationship according to a possible implementation manner of the present invention.
  • the data source of the mobile phone number and application binding relationship of the user interface 150 is determined by the network server 140.
  • the mobile phone number and the application associated data table are provided (as shown in FIG. 14-2), and the binding relationship between the obtained mobile phone number and the application is transmitted to the terminal device 100.
  • the user knows that a certain mobile phone number in the terminal 100 is bound to the application, that is, an application that is not installed by the current terminal 100 but has been bound, or an application that is installed but not bound by the terminal 100.
  • an application that the terminal 100 has bound and has installed may also be performed on the already bound application.
  • operations such as unbinding, installing, binding, and replacing a binding number may also be performed on multiple programs.
  • the terminal device 100 has installed an application bound to a local mobile number (eg, card 1), such as the Wechat program in FIG. 14-1, at this time, "Install Application”
  • the control is inoperable (indicated by a dashed box in the figure), and the Unbundle control is highlighted (ie, operational).
  • the terminal device 100 does not install an application that has been bound to the local mobile phone number, such as the "Facebook” program in Figure 14-1, the "Install Application” control is highlighted at this time. Status (ie, operational), and the Unbind control is highlighted (i.e., operational).
  • the terminal device 100 has installed but not bound an application, such as the QQ program in Figure 14-1, the "Binding" control is now highlighted (ie, operational), and " The Install Application control renders an inoperable state (indicated by a dashed box in the figure).
  • the operation of replacing the mobile phone number may also be performed on the already bound application, for example, WeChat, "Facebook", and the mail program in FIG. 14-1, where the "Replace Number" control is presented.
  • the highlighted state means "operable state”.
  • the user can 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 application binding relationship. If you click on the "Install Application” control of the "Facebook” program, you can link to the application market (for example, App Store, etc.) interface 160 (as shown in Figure 15) downloaded by the application. In some embodiments, entering the download interface 150 of the application store shown in FIG. 15 directly performs the download operation. In some embodiments, it is also desirable to click on the "Install" control in interface 150.
  • clicking on the "Install Application” control of the "Facebook” program can also directly download the operation on the current interface. As shown in FIG. 16, the user can display the download progress directly on the current interface 150 without entering the application market or the application store for downloading.
  • FIG. 14-1 there may be a scenario in which the terminal device 100 has installed the program but is not bound, for example, a QQ program, and the user can click the “Binding” control, that is, the QQ program is bound to the phone number.
  • Interface for example, enter the binding interface as shown in Figure 8.
  • the system will remind “the mobile phone number you entered has been bound by another account”, and provide the corresponding password to retrieve the portal or unbind. Replace the bound mobile phone number entry.
  • a method of installing multiple applications is also provided. Click the "Install Multiple Applications” button as shown in Figure 14-1, and the setting interface 170 of "Install Multiple Applications” as shown in Figure 17 pops up. Click the radio button or the checkbox to install the application. Multiple application download and install operations are available.
  • the application store download interface can be popped up automatically and continuously.
  • the download progress of the current application eg, Facebook program download in FIG. 16 may also be displayed on 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 a possible implementation manner of the present invention, the steps of which are as follows:
  • Step S310 Acquire an association relationship data table between the established phone number and the application (for example, FIG. 14-2);
  • Step S320 Acquire a list of applications local to the terminal device 100;
  • Step S330 Compare the associated relationship data table with the local application installation list to obtain an un-installed but already bound application state (for example, an application that is already installed but not bound, already bound and already installed) An application) and displayed on the settings interface 150 (eg, the "Install Application” control renders an operational state);
  • an un-installed but already bound application state for example, an application that is already installed but not bound, already bound and already installed
  • An application displayed on the settings interface 150 (eg, the "Install Application” control renders an operational state);
  • Step S340 Click the "Install" icon (uninstalled but already bound application) in the setting interface 150 to download or jump to the application store for downloading.
  • the method for installing an application based on a mobile phone number and an application binding relationship may be applicable to a scenario in which a mobile phone is replaced but a phone number is not replaced, or a scenario in which an already bound but deleted application is used again, or In the scenario where the application is installed but not bound, in the above case, the terminal device 100 reads the locally installed application list and the mobile phone number and application associated data table stored in the network server 140-1 (see Figure 14-2).
  • the "Install Application” operation can also "unbind” the un-installed but already bound application, and can also "bind” the installed but unbound application, or The installed and bound application performs an "unbind” operation.
  • a method for unbinding a mobile phone number based on a mobile phone number and an application association relationship is further provided.
  • the user may unbind the already bound application based on the mobile phone number associated with the application number of the mobile phone number associated with the program interface 150 (as shown in FIG. 14-1) (including the terminal device). 100 downloads or undownloaded applications). As shown in FIG. 19, the terminal device 100 provides a setting interface 180 for unbinding the mobile phone number. After clicking the "unbind" button on the mobile phone number association program interface 150, the terminal device 100 enters the unbinding interface 180 of the corresponding application.
  • unbinding requires authentication, including but not limited to: phone number verification, name verification, problem verification, and the like.
  • the terminal device 100 sends the verification 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 is registered, and completes the unbinding after the verification succeeds. operating.
  • web server 140-1 stores the authentication information required to unbind the application.
  • the web server 140-1 sends the authentication information entered by the user to the application server 130, for example, to the web server 140-1 via the terminal device 100.
  • the application server 130 compares the received authentication information with the identity verification information when the user registers, and completes the unbinding operation after the verification succeeds.
  • the web server 140-1 separately transmits the verification information input by the user to the application server 130 corresponding to the application to be unbound.
  • unbinding the application is also It may be that the association between the application in the web server 140-1 and the mobile phone number is deleted, for example, the association relationship between the application and the mobile phone number is deleted.
  • the unbinding interface 180 is popped up (as shown in Figure 19), and the phone number verification, name verification, problem verification, etc. are entered, and the verification is successful. After that, the implementation unbinds the application.
  • the authentication of the unbind interface 180 includes, but is not limited to, answering security questions, verification codes, fingerprints, passwords, and the like.
  • an application that has been bound and installed can also be unbound.
  • unbinding can also jump to an application client or web page.
  • a method for unbinding a plurality of applications is also provided, such as clicking the "unbind multiple applications" button shown in FIG. 14-1, and popping up as shown in FIG.
  • Application settings interface 190 click the radio button that needs to unbind the application or select all the bound applications, click the "release” button, and the unbundling as shown in Figure 19 can be automatically and continuously popped up.
  • the verification interface 180 may simply pop up an unbinding verification interface.
  • FIG. 21 is a flowchart of unbinding an application based on a mobile phone number and an application binding relationship, and the steps are as follows:
  • Step S400 "On the mobile phone number binding application” interface 150 (as shown in FIG. 14-1), click the "unbind” button corresponding to the application to be unbound;
  • Step S410 Obtain the service identifier information of the application server 130 from the network server 140, including identity verification information that needs to be filled in by the user.
  • identity verification information such as new mobile phone number, original mobile phone number, verification question 1, verification question 2;
  • Step S420 Enter the "unbinding" setting interface 140, and input the identity verification information of the unbind application;
  • Step S420 The authentication information input by the user is sent by the terminal device 100 to the application server 130, and the application server 130 compares the verification information of the unbind application with the information when the user registers, and completes the unbinding after the verification succeeds. operating.
  • the method for unbinding an application based on a mobile phone number and an application binding relationship may be applicable to a scenario in which a mobile phone number is replaced but the terminal is not replaced (for example, a new mobile phone number may be required to be bound), or Reusing the already bound application, or the scenario that is not installed but has been bound to the application (for example, has been deleted and does not want to receive the short message received by the application), in the above case, the terminal device 100 reads the local The installed application list is compared with the list of applications bound in the web server (for example, the data table in Figure 14-2) to get unmounted but bound applications, installed but unbound applications An application that has been bound and installed, the user can "install the application” operation on the application that is already bound but not installed, and can also "unbind” the application that is not installed but has been bound. You can also "bind" an already installed but unbound application, and you can also install and bind the application. Use the program to "unbind" the operation.
  • This embodiment also provides a method for updating a binding relationship between a mobile phone number and an application.
  • the user can manually update the binding relationship between the mobile phone number and the application, click the “Refresh” button, and the terminal device 100 reads the locally installed application list and stores it in the The mobile phone number in the server 140 is re-compared with the data table of the binding relationship of the terminal device. After comparison, the un-installed but bound application, the installed but unbound application, the bound and installed are obtained. The application updates the data of the interface 150 for the user to operate.
  • This embodiment also provides a method for an application to replace a bound mobile phone number.
  • an interface 140 for replacing the bound mobile phone number is provided.
  • the "replace number" button corresponding to the application that needs to replace the bound mobile phone number is clicked. , then enter the replacement tie Set the mobile phone number interface 140, enter the original mobile phone number, the mobile phone number to be bound, and complete the replacement binding number operation after verification.
  • an interface 200 for performing a tie-over operation on a plurality of already associated applications is also provided.
  • Clicking on the "bind multiple applications" in the mobile phone number association application interface 150 in FIG. 14-1 is performed.
  • the control enters and replaces multiple application interfaces 200, and can select a single application that needs to be replaced or select an application that needs to be replaced. Click the “change the binding” button to enter the replacement binding shown in Figure 14-1.
  • the mobile phone interface 140 is set.
  • the unbundling verification interface 140 as shown in FIG. 8 may be automatically and continuously popped out or the unbinding verification interface 140 may only be popped once.
  • This method can be applied to the scenario where the user replaces the mobile phone number, and needs to use the binding relationship between the original mobile phone number and the application, bind the new mobile phone number, re-bind the new mobile phone number, and the data in the application (for example). , chat history, account name) remains unchanged, users can still log in to the application by username, new mobile number.
  • This embodiment provides a method for prompting a user to perform binding, installation, and the like based on a change in a relationship between a mobile phone number and a terminal device.
  • the International Mobile Equipment Identity (IMEI) of the terminal device 100 is unique and fixed.
  • the IMEI is commonly referred to as a “mobile phone serial number” and is stored in the EEPROM of the mobile phone.
  • the terminal device 100 can acquire or read the mobile phone number of the local device, for example, the MSISDN (Mobile Subscriber International ISDN number) information of the mobile phone SIM card.
  • the mobile phone number and the mobile phone serial number may be built into a data table and stored in the network server 140-1, and further, may also be stored in the terminal device 100.
  • the IMEI code of the terminal device 100 and the phone of the mobile phone If the corresponding relationship of the number changes, trigger and update the binding relationship between the mobile phone number and the application. For example, when prompted to find that the mobile phone has been replaced, please bind the mobile phone number to the application. After the user confirms, the user can enter the following figure.
  • a flow chart for prompting the user to perform an association operation based on a change in the relationship between the mobile phone number and the terminal device is provided:
  • Step S510 The mobile phone number (unique identification) and the IMEI of the mobile phone terminal (the unique identifier of the mobile phone) are changed. That is, change the number without changing the machine, or change the machine without changing the number, go to the next step;
  • Step S520 The terminal device prompts the user, for example, “I found that the mobile phone number has been replaced, please bind the mobile phone number to the application”;
  • Step S530 After determining the pop-up setting interface, as shown in the "Mobile Phone Number Association Application" interface 140 of FIG. 14-1.
  • a method for mapping a mobile phone number to an application association relationship based on a cloud account is also provided. As shown in FIG. 10, the method for mapping a mobile phone number to an application based on a cloud account is as follows:
  • Step A The web server 140-1 stores the service identification information of the application server 130, so that the terminal device 100 can recognize the application source of the verification information.
  • Step B When the terminal device 100 receives the verification information, it determines the verification information according to the service identification information stored in the network server 140-1 in step A, and parses out the corresponding application name.
  • Step C The terminal device 100 associates the already acquired local mobile phone number with the parsed application name, and sends the association relationship (for example, a data table corresponding to the correspondence between the mobile phone number and the application name).
  • the web server 140-2 maps the mobile phone number and the application name association relationship table with the user's cloud account (for example, may be a data table as shown in FIG. 24-1).
  • Step D The association relationship may be automatically updated according to the request of the user, and sent to the terminal device 100, and the user may perform operations such as installing and unbinding according to the association relationship.
  • the network program server 140-1 obtains a service identifier that the application server 130 sends the verification information, and the service identifier can be used by the terminal device 100 to determine the application name by receiving the verification information.
  • the service identifier of the application server 130 that sends the verification information may be the source of the verification information (the source of the short message of the Netease cloud music is 1069125295163), the MAC address, the IP address, the server name, and the unbundling required. At least one of authentication information, etc.
  • the manner of obtaining may be by collecting by the terminal manufacturer or by the application vendor to report or disclose the service identification information and the like.
  • the web server 140-1 may also store a phone number in the terminal device 100, such as uploaded by the terminal device 100 to the web server 140-1.
  • the method of reading the mobile phone number may be by reading the MSISDN (Mobile Subscriber International ISDN number) information of the mobile phone SIM card.
  • Step B in some embodiments, when the terminal device 100 receives the verification information, uploading the verification information to the network server 140-1, and the network server 140-1 will receive the verification information and the stored application service identification information. Perform a comparative analysis to resolve the application name.
  • the web server 140-1 may associate the parsed application name with the stored mobile phone number (eg, a binding data table of the mobile phone number and application may be established) and stored.
  • the web server 140-1 can associate the parsed application name with the stored mobile number and send it to the web server 140-2.
  • the network server 140-2 performs a mapping operation between the mobile phone number and the application name association relationship table and the user's cloud account (for example, a Huawei account) (for example, may be a data table as shown in FIG. 24-1).
  • the terminal device 100 logs in to the cloud account, and the user can know the relationship between the mobile phone number and the application.
  • the network server 140-1 may further store a phone number in the terminal device 100 (for example, the mobile phone number may be uploaded by the terminal device 100), and the terminal device 100 uploads the parsed application name to The web server 140-1 is associated with and stored with the already stored mobile number.
  • the terminal device 100 may store the association relationship between the local phone number that has been acquired and the application name in the terminal device 100.
  • the server identifying the service identification information of the application server 140 and the server storing the application-to-phone number binding relationship may also be the same (ie, 140-1 and 140-2 are the same server).
  • the user's cloud account can map multiple mobile phone numbers to application associations.
  • the association of the mobile number with the application can also be extended to associate the third party application account with the application. Further, the user's cloud account can be mapped to the relationship associated with the third-party application account and the application.
  • an application is provided to remind the user that the currently bound application has been bound by another mobile phone number interface 210 (eg, interface 130 of FIG. 5), such as the user's cloud account 123456@huawei.com Map the relationship between the mobile phone number 1 and the application 1 and the relationship between the mobile phone number 2 and the application 2.
  • the system will remind "according to your Huawei account 123456@huawei.com Display, your mobile phone number 1320000000 has been bound to the application, whether to confirm the current number continues to bind" and provide the "continue binding", "login using the already bound mobile phone number” entry.
  • This embodiment can be applied to a scenario in which a user changes a mobile phone and simultaneously changes a mobile phone number.
  • the cloud account first maps the association relationship between the original mobile phone number and the application, and the new terminal device of the user logs in to the cloud account and then associates the relationship in the cloud account.
  • update the mobile phone number associated with the application interface 150 as shown in Figure 14-1 and then the cloud account The relationship between the new mobile phone number and the application is mapped, and the mobile phone number associated application interface 150 shown in FIG. 14-1 is updated.
  • Embodiments of the present invention can be arbitrarily combined to achieve different technical effects.
  • the transmission is performed in one or more instructions or code on a computer readable medium or as 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 location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure.
  • Any connection may suitably be a computer readable medium.
  • a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Telephone Function (AREA)

Abstract

基于安全、用户体验等因素考虑，应用程序通常都需要关联手机号码。本发明提供一种判断手机号码与应用程序关联关系的方法，并基于这种关联关系提示用户进行安装、解除绑定手机号码等。适用于用户换手机不换手机号码、换手机号码不换手机以及更换手机号码与手机的场景下，使用户能有更好地体验。

Description

判定手机号码与应用关联关系的方法
本发明实施例涉及通信领域，尤其涉及一种判定手机号码与应用关联关系的方法。
背景技术
移动终端已经变得越来越多功能化。这些功能的示例包括数据和语音通信、经由相机拍摄图像和视频、记录音频、经由扬声器系统播放音乐文件以及在显示器上显示图像和视频。一些移动终端包括支持玩游戏的附加功能，而其它终端被配置成多媒体播放器。随着这些功能变得更多样化，移动终端可支持更复杂的功能，例如拍摄图像或视频、再现音乐或视频文件、玩游戏、接收广播信号等。
随着智能型手机的不断普及，用户可以任意的下载安装各种APP，例如Wechat、Facebook等。为了安全或者用户体验等原因，服务商往往需要用户提供电话号码等个人信息进行绑定，而用户常常忘记已经绑定的APP或者卸载已经绑定的APP，又或者存在更换手机或者更换手机号码的情况，用户不知道手机号码(其他账号)已经关联的应用程序。
发明内容
基于上述原因，本发明提供一种判定手机号码与应用程序关联关系的方法，并提供各种快捷操作，使用户有更佳的体验。
一方面，本发明实施例提供了一种方法，包括：第一服务器可以是第一应用程序的后台服务器，第二服务器可以存储第一服务器的服务标识与所述第一应用程序的对应关系；终端设备获取到第一信号，所述第一信号指示所述终端设备向第一服务器发送关联请求，所述终端设备可以发送第二信号至所述第一服务器，所述第二信号包括所述关联请求；第一服务器获取到所述第二信号，所述第一服务器发送第三信号至第三服务器，所述第三信号包括处理验证信息请求；第三服务器获取到所述第三信号，所述第三服务器生成第一验证信息，所述第三服务器将所述第一验证信息发送至所述终端设备，其中所述第一验证信息包括所述第一服务器的服务标识；所述终端设备访问所述第二服务器，终端设备可以获取到所述第一服务器的服务标识；所述终端设备获取到所述第一验证信息，通过所述第一验证信息中所包含的所述第一服务器的服务标识识别出第一应用程序，其中，所述终端设备的第一手机号码接收到所述第一验证信息；所述终端设备可以关联所述第一手机号码与所述第一应用程序。本实施例可以使终端设备能够获得第一号码与多个应用程序的关联关系。
在一个可能的设计中，所述终端设备可以将第一手机号码与所述第一应用程序的关联关系发送至第二服务器，以实现所述关联关系及时备份。
本发明实施例提供了一种方法，包括：所述第一服务器可以是第一应用程序的后台服务器，第二服务器可以存储第一服务器的发送源与所述第一应用程序的关联关系；终端设备可以获取到第一手机号码，终端设备可以将第一手机号码发送至第一服务器；所述第一服务器获取到第一手机号码，所述第一服务器将第一手机号码发送至第三服务器；所述第三服务器接收第一手机号码，所述第三服务器生成第一验证信息，所述第三服务器将第一验证信息发送至所述终端设备的所述第一手机号码；所述终端设备可以访问第二服务器，获取到所述第一服务器的发送源；所述终端设备获取到所述第一验证信息，所述终端设备通过所述第一验证信息的发送源识别出第一应用程序，其中，所述终端设备的第一手机号码接收到所述第一验证信息；所述终端设备可以关联所述第一手机号码与所述第一应用程序。本实施例可以实现通过验证信息的发送源来识别应用程序，并建立关联关系。
本发明实施例提供了一种方法，其特征在于，包括：终端设备显示第一应用程序的第一登录界面，其中，所述终端设备存储有第一手机号码与所述第一应用程序之间的关联关系；获取到第二手机号码，所述终端设备将所述第二手机号码与所述第一手机号码进行对比；当所述第二手机号不同于所述第一手机号码时，所述终端设备提示用户所述第一手机号码已经关联所述第一应用程序。本实施例可以提醒用户已经关联过的应用程序的手机号码。
在一个可能的设计中，当所述第二手机号不同于第一手机号码时，所述终端设备允许用户利用所述第二手机号码登录和/或第一手机号码登录。以实现提供用户不同的登录方式。
本发明实施例提供了一种方法，其特征在于，包括：终端设备可以显示第一应用程序的第一登录界面，所述终端设备存储有第一账号与所述第一应用程序之间的关联关系；获取到第二账号，其中，所述第二账号不同于所述第一账号；当所述第二账号没有关联所述第一应用程序时，所述终端设备提示用户所述第一账号已经关联所述第一账号，其中，所述第一账号与所述第二账号通过第三账号关联。可以提醒用户已经用不同的账号关联过的应用程序。
在一个可能的设计中，当所述第二账号已经关联所述第一应用程序，允许所述第二账号登录所述第一应用程序。
本发明实施例提供了一种方法，其特征在于，包括：显示第一界面，所述终端设备存储有第一手机号码与第一应用程序关联关系，所述终端设备没有安装所述第一应用程序；获取到针对所述第一界面的第一操作，所述终端设备进行对所述第一应用程序的下载操作。以实现用户能够下载已经关联但是未安装的程序。
在一个可能的设计中，获取到针对所述第一界面的第一操作，所述终端设备跳转至第三方商店的下载界面。以实现用户能够下载已经关联但是未安装的程序
在一个可能的设计中，获取到针对所述第一界面的第一操作，所述终端设备对多个应用程序进行下载。以实现用户能够一次下载已经关联但是未安装的程序。
在一个可能的设计中，获取到针对所述第一界面的第二操作，所述终端设备跳转至第二应用程序的登录界面，其中，所述第一手机号码没有关联所述第二应用程序，且所述终端设备安装有所述第二应用程序。以实现用户能够关联已经安装但是未关联的程序。
在一个可能的设计中，获取到针对所述第一界面的第三手势操作，所述终端设备跳转至所述第二界面；获取到用户在所述第二界面输入的鉴权信息；当鉴权成功后，所述第一手机号码与所述第一应用程序解除关联关系；以实现手机号码与应用程序解除关联关系。
一个可能的设计中，获取到针对所述第一界面的第四操作，所述终端设备跳转至第三界面；获取到第二手机号码，所述第二手机号码关联所述第一应用程序，所述第一手机号码与所述第一应用程序解除关联关系，其中，第一手机号码不同于第二手机号码。以实现用户更换关联的手机号码。
本发明实施例提供了一种终端设备，其特征在于，包括：处理器；及存储介质，其中，所述存储介质存储有指令，所述指令使得所述终端设备执行上述的方法。
本发明实施例提供了一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在电子设备上运行时，使得所述终端设备执行上述的方法。
本发明实施例提供了一种计算机可读存储介质，包括指令，其特征在于，当所述指令在电子设备上运行时，使得所述终端设备执行上述的方法。
值得一提的是，本发明的实施例可以任意组合来达成不同的技术效果。
通过上述方案，本发明的实施例能够通过实现用户在更换手机后，知道自己的手机号码之前关联过的应用程序，并允许进行安装、解绑等操作；在用户更换手机号码后，能够知道原来的手机号码关联过的应用程序，并允许进行安装、解绑等操作。
附图说明
图1为根据本发明一种可能的实施方式提供的终端设备示意图。
图2示出的是本发明一种可能的实施方式提供的终端设备的部分结构的框图。
图3为根据本发明一种可能的实施方式提供的获取电话号码与应用程序关联的第一系统示意图。
图4为根据本发明一种可能的实施方式提供的获取电话号码与应用程序关联的第二系统示意图。
图5为根据本发明一种可能的实施方式提供的第一登录界面。
图6为根据本发明一种可能的实施方式提供的第二登录界面。
图7为根据本发明一种可能的实施方式提供的绑定手机号码界面。
图8为根据本发明一种可能的实施方式提供的更换绑定手机号码界面。
图9为根据本发明一种可能的实施方式提供的获取手机号码与应用程序关联的第一流程图。
图10为根据本发明根据本发明一种可能的实施方式提供的获取电话号码与应用程序关联的第三系统示意图。
图11为根据本发明根据本发明一种可能的实施方式提供的获取电话号码与应用程序关联的第四系统示意图。
图12为根据本发明根据本发明一种可能的实施方式提供的获取电话号码与应用程序关联的第五系统示意图。
图13为根据本发明一种可能的实施方式提供的获取手机号码与应用程序关联的第二流程图。
图14-1为根据本发明一种可能的实施方式提供的手机号码关联应用程序界面。
图14-2为根据本发明一种可能的实施方式提供的手机号码关联应用程序数据表。
图15为根据本发明一种可能的实施方式提供的安装应用程序第一界面。
图16为根据本发明一种可能的实施方式提供的安装应用程序第二界面。
图17为根据本发明一种可能的实施方式提供的安装应用程序第三界面。
图18为根据本发明一种可能的实施方式提供的安装应用程序流程图。
图19为根据本发明一种可能的实施方式提供的解除绑定手机号码的第一界面。
图20为根据本发明一种可能的实施方式提供的解除绑定手机号码的第二界面。
图21为根据本发明一种可能的实施方式提供的解除绑定手机号码的流程图。
图22为根据本发明一种可能的实施方式提供的更换绑定手机号码的第一界面。
图23为根据本发明一种可能的实施方式提供的更新手机号码与终端设备对应关系的流程图。
图24-1根据本发明一种可能的实施方式提供的云账号映射手机号码与应用程序关联的数据表。
图24-2根据本发明一种可能的实施方式提供的云账号映射第三方应用账号与应用程序关联的数据表。
图25为根据本发明一种可能的实施方式提供的第三登录界面。
具体实施方式
图1为根据本发明一种可能的实施方式提供的终端设备的示意图。
本发明实施例涉及的终端设备100可以包括手机、平板电脑、PDA(Personal Digital Assistant，个人数字助理)、POS(Point of Sales，销售终端)、车载电脑、TV、可穿戴设备、AR、VR设备等。
以终端设备100为手机为例，图2示出的是与本发明实施例相关的手机100的部分结构的框图。参考图2，手机100包括、RF(Radio Frequency，射频)电路110、存储器120、其他输入设备130、显示屏140、传感器150、音频电路160、I/O子系统170、处理器180、以及电源190等部件。本领域技术人员可以理解，图2中示出的手机结构并不构成对手机的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。本领领域技术人员可以理解显示屏140属于用户界面(UI，User Interface)，且手机100可以包括比图示更多或者更少的用户界面。
下面结合图2对手机100的各个构成部件进行具体的介绍：
RF电路110可用于收发信息或通话过程中，信号的接收和发送，特别地，将基站的下行信息接收后，给处理器180处理；另外，将设计上行的数据发送给基站。通常，RF电路包括但不限于天线、至少一个放大器、收发信机、耦合器、LNA(Low Noise Amplifier，低噪声放大器)、双工器等。此外，RF电路110还可以通过无线通信与网络和其他设备通信。所述无线通信可以使用任一通信标准或协议，包括但不限于GSM(Global System of Mobile communication，全球移动通讯系统)、GPRS(General Packet Radio Service，通用分组无线服务)、CDMA(Code Division Multiple Access，码分多址)、WCDMA(Wideband Code Division Multiple Access,宽带码分多址)、LTE(Long Term Evolution,长期演进)、电子邮件、SMS(Short Messaging Service，短消息服务)等。
存储器120可用于存储软件程序以及模块，处理器180通过运行存储在存储器120的软件程序以及模块，从而执行手机100的各种功能应用以及数据处理。存储器120可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图象播放功能等)等；存储数据区可存储根据手机100的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器120可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
其他输入设备130可用于接收输入的数字或字符信息，以及产生与手机100的用户设置以及功能控制有关的键信号输入。具体地，其他输入设备130可包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆、光鼠(光鼠是不显示可视输出的触摸敏感表面，或者是由触摸屏形成的触摸敏感表面的延伸)等中的一种或多种。其他输入设备130与I/O子系统170的其他输入设备控制器171相连接，在其他设备输入控制器171的控制下与处理器180进行信号交互。
显示屏140可用于显示由用户输入的信息或提供给用户的信息以及手机100的各种菜单，还可以接受用户输入。具体的显示屏140可包括显示面板141，以及触控面板142。其中显示面板141可以采用LCD(Liquid Crystal Display，液晶显示器)、OLED(Organic Light-Emitting Diode,有机发光二极管)等形式来配置显示面板141。触控面板142，也称为触摸屏、触敏屏等，可收集用户在其上或附近的接触或者非接触操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板142上或在触控面板142附近的操作，也可以包括体感操作；该操作包括单点控制操作、多点控制操作等操作类型。)，并根据预先设定的程式驱动相应的连接装置。可选的，触控面板142可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位、姿势，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成处理器能够处理的信息，再送给处理器180，并能接收处理器180发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板142，也可以采用未来发展的任何技术实现触控面板142。进一步的，触控面板142可覆盖显示面板141，用户可以根据显示面板141显示的内容(该显示内容包括但不限于，软键盘、虚拟鼠标、虚拟按键、图标等等)，在显示面板141上覆盖的触控面板142上或者附近进行操作，触控面板142检测到在其上或附近的触摸操作后，通过I/O子系统170传送给处理器180以确定触摸事件的类型以确定用户输入，随后处理器180根据触摸事件的类型通过I/O子系统170在显示面板141上提供相应的视觉输出。虽然在图2中，触控面板142与显示面板141是作为两个独立的部件来实现手机100的输入和输入功能，但是在某些实施例中，可以将触控面板142与显示面板141集成而实现手机100的输入和输出功能。
手机100还可包括至少一种传感器150，比如光传感器、运动传感器以及其他传感器。具体地，光传感器可包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板141的亮度，接近传感器可在手机100移动到耳边时，关闭显示面板141和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别手机姿态的应用(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；至于手机100还可配置的陀螺仪、气压计、湿度计、温度计、红外线传感器等其他传感器，在此不再赘述。
音频电路160、扬声器161，麦克风162可提供用户与手机100之间的音频身份标识。音频电路160可将接收到的音频数据转换后的信号，传输到扬声器161，由扬声器161转换为声音信号输出；另一方面，麦克风162将收集的声音信号转换为信号，由音频电路160接收后转换为音频数据，再将音频数据输出至RF电路108以发送给比如另一手机，或者将音频数据输出至存储器120以便进一步处理。
I/O子系统170用来控制输入输出的外部设备，可以包括其他设备输入控制器171、传感器控制器172、显示控制器173。可选的，一个或多个其他输入控制设备控制器171从其他输入设备130接收信号和/或者向其他输入设备130发送信号，其他输入设备130可以包括物理按钮(按压按钮、摇臂按钮等)、拨号盘、滑动开关、操纵杆、点击滚轮、光鼠(光鼠是不显示可视输出的触摸敏感表面，或者是由触摸屏形成的触摸敏感表面的延伸)。值得说明的是，其他输入控制设备控制器171可以与任一个或者多个上述设备连接。所述I/O子系统170中的显示控制器173从显示屏140接收信号和/或者向显示屏140发送信号。显示屏140检测到用户输入后，显示控制器173将检测到的用户输入转换为与显示在显示屏140上的用户界面对象的交互， 即实现人机交互。传感器控制器172可以从一个或者多个传感器150接收信号和/或者向一个或者多个传感器150发送信号。
处理器180是手机100的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在存储器120内的软件程序和/或模块，以及调用存储在存储器120内的数据，执行手机100的各种功能和处理数据，从而对手机进行整体监控。可选的，处理器180可包括一个或多个处理单元；优选的，处理器180可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器180中。
手机100还包括给各个部件供电的电源190(比如电池)，优选的，电源可以通过电源管理系统与处理器180逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗等功能。
尽管未示出，手机100还可以包括摄像头、蓝牙模块等，在此不再赘述。
图3为根据本发明一种可能的实施方式提供的获取手机号码与应用程序之间关联关系的系统示意图，系统结构如图3所示：该系统包括至少一个终端设备(也称“终端”)100，至少一个移动运营商110，至少一个验证信息处理服务器120，至少一个应用程序服务器130。
本实施例中的“关联”，可以是利用手机号码绑定某一应用程序的账号，进一步地，也可以扩展到第三方应用账号绑定某一应用程序。在一些实施例中，可以是利用手机号码注册某一应用程序，例如，在注册的过程中需要通过手机号码完成验证，验证成功后，与应用程序后台的应用程序服务器130自动将手机号码与应用程序绑定。在一些实施例中，可以是手机号码动态登录应用程序，即无需设置登录密码，每次登录应用程序时只需利用验证信息处理服务器120生成的验证码登录。例如，手机号码没有绑定该应用程序，在登录界面输入手机号码，并点击“获取验证码”，验证成功后访问该应用程序，进一步地，应用程序服务器130也会生成与手机号码对应的用户名。在一些实施例中，可以是利用邮箱注册后，基于安全、用户体验的考虑，需要绑定手机号码。在一些实施例，应用程序服务器130生成的账号与绑定的手机号码是一一对应关系，即手机号码登录与用户名登录的访问权限是相同的。
在一些实施例中，该终端设备100是台式计算机，在一些实施例中，该终端设备100是便携式的(例如，笔记本电脑、平板电脑或手持设备)，在一些实施中，该终端设备100设备具有触敏显示器(也称为“触摸屏”)。在一些实施例中，该终端设备100具有图形用户界面(GUI)、一个或者多个处理器、存储器和一个或多个模块、被存储在存储器中以用于执行多个功能的程序或指令集。在一些实施例中，用户主要通过触摸屏上的手指接触和手势与用户界面进行交互。在一些实施例中，终端设备100安装有应用程序客户端或者能够访问应用程序网站(也称“应用程序网页版”)，在一些实施例中，终端设备100可以存储手机号码与应用程序之间的关联关系，例如，可以存储由二者关联关系建立的数据表。
在一些实施例中，移动运营商110是指拥有移动业务牌照、频谱资源以及无线接入与交换网络基础设施的部门，主要负责移动传输网络的运营和维护，保障网络业务质量，以及提供移动数据业务平台和用户认证、管理等等，例如可以是中国移动、中国电信以及中国联通。在一些实施例中，移动运营商110还可以是虚拟网络运营商。在一些实施例中，移动运营商110主要是将短信验证码、语音信息等验证信息发送至终端100，以完成绑定操作。在一些 实施例中，移动运营商110是非必须的，例如，可以通过应用程序服务器130发送即时信息至终端100。
在一些实施例中，终端设备100发送手机号码绑定应用程序的请求至应用程序服务器130，例如，该请求可以是用户在应用程序绑定手机号码界面输入手机号码后，点击“获取短信验证码”。在一些实施例中，根据终端设备100发送的绑定手机号码的请求，应用程序服务器130将携带有用户手机号码的指令发送至验证信息处理服务器120。在一些实施例中，携带有用户手机号码的指令也可以是由终端设备100发送至验证信息处理服务器120。在一些实施例中，验证信息处理服务器120可以处理验证信息，处理验证信息可以是生成短信验证码、语音验证信息以及判断手机号码是否合规、手机号码所属的运营商等其中至少一个。在一些实施例中，验证信息处理服务器120将生成的验证信息通过移动运营商110发送至终端设备100。在一些实施例中，验证信息处理服务器120还可以将生成的验证信息发送至应用程序服务器130。在一些实施例中，验证信息处理服务器120可以将生成的验证信息与用户输入的验证信息进行对比，以完成绑定操作，例如，终端设备100接收到用户输入的验证信息后发送至应用程序服务器130，应用程序服务器130再将验证信息发送至验证信息服务器120。
在一些实施例中，应用程序服务器130可以是应用程序客户端或者应用程序网站的后台服务器，以供应用程序客户端、网站访问或者调用数据。在一些实施例中，终端设备100发送手机号码绑定应用程序的请求至应用程序服务器130，例如，该请求可以是用户在应用程序绑定界面输入手机号码后，点击“获取验证码”。在一些实施例中，应用程序服务器130根据终端设备100的请求处理验证信息，处理验证信息可以是生成短信验证码、语音验证信息以及判断手机号码是否合规、手机号码所属的运营商等其中任一项。在一些实施例中，应用程序服务器130将生成的验证信息通过移动运营商110发送至终端设备100，进一步地，应用程序服务器130还可以直接将生成的验证信息直接发送至终端设备100，例如，通过应用程序发送即时消息。在一些实施例中，应用程序服务器130接收到终端设备100发送的验证信息，例如，可以是由用户在接收到移动运营商100发来的验证信息后在应用程序客户端的界面中输入，还可以是终端设备100在接收到移动运营商100发来的验证信息后自动填充。在一些实施例中，应用程序服务器130将终端设备100发送的验证信息与生成的验证信息进行对比，验证成功后完成绑定操作，例如，终端设备100提示用户“您已经成功绑定手机号1320000000”。
在一些实施例中，终端设备100接收到手机号码绑定应用程序的请求，例如，该请求可以是用户在应用程序绑定界面输入手机号码后点击“获取验证码”。在一些实施例，也可以由应用程序客户端处理验证信息，处理验证信息可以是生成短信验证码、语音验证信息以及判断手机号码是否合规、手机号码所属的运营商等其中至少一项。在一些实施例中，客户端生成的验证信息可以存储在用户具有访问权限的区域。在一些实施例中，应用程序客户端将终端设备100接收到验证信息与应用程序客户端生成的验证信息进行对比，验证成功后完成绑定操作，例如，终端设备100提示用户“您已经成功绑定手机号1320000000”。
在一些实施例中，当手机号码与应用程序成功完成绑定操作后，应用程序服务器130将存储上述手机号码与应用程序绑定关系。在一些实施例中，应用程序服务器130也可以将手机号码与应用程序绑定关系发送至终端设备100中，由终端设备100存储于本地。进一步地，终端设备100也可以将手机号码与应用程序绑定关系发送至网络服务器中。
如图3所示的根据本发明一种可能的实施方式提供的建立手机号码与应用程序之间关联关系的系统，其运行步骤如下：
步骤1：具有应用程序客户端的终端设备100接收到用户请求绑定手机号码的请求；
终端设备100将用户请求绑定手机号码的请求发送至应用程序服务器130；
步骤2：应用程序服务器130接收到请求后，发送携带有用户电话号码的指令至验证信息处理服务器120。
步骤3：验证信息处理服务器120收到携带有用户电话号码的指令后，生成验证信息，并将生成的验证信息发送至应用程序服务器130；
步骤4：验证信息处理服务器130将生成的验证信息发送至移动运营商110；
步骤5：移动运营商110将验证信息发送至终端设备100；
步骤6：终端设备100接收到验证信息，由用户完成输入操作或自动输入后，终端设备100将输入的验证信息发送至应用程序服务器130；
应用程序服务器130将用户输入的验证信息与生成的验证信息进行对比，对比成功后完成绑定操作，并存储手机号码与应用程序的绑定关系。
图4为根据本发明一种可能的实施方式提供的获取手机号码与应用程序之间关联关系的系统示意图,该系统包括至少一个终端设备(也称“终端”)100，至少一个应用程序服务器130。
如图4所示系统的运行步骤如下：
步骤1：具有应用程序客户端的终端设备100接收到用户请求绑定手机号码的请求；
终端设备100将用户请求绑定手机号码的请求发送至应用程序服务器130；
步骤2：客户端后台的应用程序服务器130接收到请求后，生成验证信息，并将生成的验证信息发送至终端设备100。
步骤3：用户在客户端登录界面输入终端设备100接收到的验证信息；
终端设备100将用户输入的验证信息发送至应用程序服务器130，应用程序服务器130根据生成的验证信息与用户输入的验证信息进行比对，验证成功后完成绑定操作；
应用程序服务器130存储手机号码与应用程序之间的绑定关系。
如图5为根据本发明一种可能的实施方式提供的手机号码动态登录应用程序的界面110。在一些实施例中，如果手机号码没有绑定应用程序，即应用程序服务器130中没有存储手机号码与应用程序的关联关系，按照如图3所示的绑定方式验证成功后，应用程序服务器130会自动生成一个与该手机号码关联的应用程序账号(例如，可以是具有登录权限的用户名)，以便用户下次登录可以采用用户名或者手机号码两种登录方式。在一些实施例中，如果手机号码已经绑定应用程序，即应用程序服务器130存储有手机号码与应用程序的关联关系，在界面110进行登录操作，验证成功后具有同用户名登录相同的访问权限。
在一些实施例中，即使手机号码与应用程序解除绑定关系后，仍然可以通过用户名登录。在一些实施例中，该界面110还提供应用程序注册入口，用户可以通过手机号码(还可以是邮箱、其他应用账号等)进行注册。在一些实施例中，该界面110还提供其他登录方式，例如微信、QQ、Facebook等第三方应用程序账号登录。
如图6为根据本发明一种可能的实施方式提供的账号密码登录界面120。在一些实施例中，账号密码登录界面120可以提供手机号码、邮箱、用户名等登录方式，例如利用手机号码 注册成功后，系统可以生成一个与该手机号码对应的用户名，用户可以通过手机号码与用户名两种方式进行登录。同样，利用邮箱注册后，系统也可以生成一个与该邮箱对应的用户名，即可以通过邮箱与用户名两种方式进行登录。在一些实施例中，也可以同时利用手机号码与邮箱进行注册生成一个用户名。
在一些实施例，利用手机号码注册应用程序时，系统会默认将该应用程序与注册时的手机号码进行绑定，例如，在注册过程中需要进行手机号码绑定应用程序。在一些实施例中，即使利用手机号码注册应用程序后，例如生成了用户名，但未绑定手机号码，进一步地，也需要进行绑定手机号码操作。
在一些实施例中，还提供“忘记密码”入口，可以通过手机号码、邮箱、安全问题等方式找回密码。在一些实施例中，还提供其他方式登录，例如微信、QQ、Facebook等第三方应用程序账号登录。在一些实施例中，登录界面120还提供用户注册入口，用户可以通过手机号码(还可以是邮箱、其他应用账号等)进行注册。
在一些实施例，利用第三方应用程序账号(例如，微信)登录应用程序(例如，网易云音乐)，应用程序服务器130通常也会关联该第三方应用程序账号。在一些实施例，应用程序服务器130也可以生成与该第三方应用程序账号对应的应用程序账号，进一步地，也可以直接用第三应用账号登录而不用生成应用程序账号。
如图7为根据本发明一种可能的实施方式提供的绑定手机号码界面130，基于安全、用户体验等原因，需要用户注册应用程序后进行绑定手机号码操作(例如，用邮箱注册登录时)。在一些实施例，如果该手机号码已经绑定了某一登录账号，系统便会提示“您输入的手机号码已经被其他账号绑定”，并提供相应的密码找回入口或者解除绑定、更换绑定手机号码入口。
如图8为根据本发明一种可能的实施方式提供的应用程序更换绑定手机号码的界面140，例如，在换手机号码的场景下，输入原绑定的手机号码以及需要新绑定的手机号码，验证成功后即可完成换绑操作，在此种情况下，原手机号码与应用程序解除绑定关系(即不能通过原手机号登录到应用程序，但仍可以通过原用户名登录)，新的手机号绑定成功后，新手机号与原用户名建立新的对应关系，即可以通过新手机号码与原用户名两种方式登录应用程序，且具有相同的访问权限。
如图9为根据本发明一种可能的实施方式提供的获取手机号码与应用程序关联关系的流程图，步骤如下：
步骤S100：具有应用程序客户端的终端设备100接收到绑定手机号码请求，并将该请求发送至后台的应用程序服务器130。
步骤S110：后台的应用程序服务器130接收到请求后，发送指令至验证信息处理服务器120，其中，指令包括用户的手机号码等信息；
步骤S120：验证信息处理服务器120处理验证信息(例如，生成验证信息、判断内容是否合规、手机号码是否合规、手机号码所属的运营商)，并将验证信息发送给应用程序服务器130；
验证信息处理服务器120将生成的验证信息通过移动运营商110发送至终端设备100。
步骤S130：终端设备100收到验证信息，由用户完成输入验证信息，终端设备100将用户输入的验证信息发送至应用程序服务器130；
应用程序服务器130将输入的验证信息与验证信息处理服务器120生成的验证信息进行对比，对比成功后完成绑定操作，并将手机号码与应用程序的绑定关系存储在应用程序服务器130中。
图10为根据本发明一种可能的实施方式提供的获取手机号码与应用程序关联关系的系统示意图，该系统至少包括一个终端设备100、至少一个移动运营商110、至少一个验证信息处理服务器120、至少一个应用程序服务器130、至少一个网络服务器140。
在一些实施例中，网络程序服务器140-1获取应用程序服务器130发送验证信息的服务标识信息，该服务标识信息可以用于终端设备100通过接收验证信息来判断应用程序名称。在一些实施例中，应用程序服务器130的发送验证信息的服务标识可以是验证信息的发送源(网易云音乐的短信发送源为1069125295163)、MAC地址、IP地址、服务器名称、解绑所需要的身份验证信息等其中任一项或者多项。在一些实施例中，获取的方式可以通过由终端厂商收集或者应用程序厂商上报或公开服务标识信息等。在一些实施例中，网络服务器140-1还可以存储终端设备100中的电话号码，例如由终端设备100上传至网络服务器140-1。在一些实施例中，读取手机号码的方式可以是通过读取手机SIM卡的MSISDN(Mobile Subscriber International ISDN number)信息。
在一些实施例中，在终端设备100收到验证信息时，将验证信息上传至网络服务器140-1，网络服务器140-1将收到的验证信息与存储的应用程序服务标识信息进行对比分析，解析出应用程序名。在一些实施例中，网络服务器140-1可以将解析出的应用程序名与存储的手机号码进行关联(例如，可以建立手机号码与应用程序的绑定数据表)并存储。在一些实施例中，网络服务器140-1可以将解析出的应用程序名与存储的手机号码进行关联并发送至网络服务器140-2。
在一些实施例中，网络服务器140-1还可以存储终端设备100中的电话号码(例如，可以由终端设备100上传手机号码)。在一些实施例中，终端设备100将受到的验证信息发送至网络服务器140-1，网络服务器140-1根据存储的应用程序服务标识信息解析出应用程序名，进一步地，解析的方式可以文本识别、通过比对验证信息发送源来判断等方式。在一些实施例中，也可以由终端设备100解析出验证信息对应的应用程序名称。在一些实施例中，网络服务器140-1将解析出的应用程序名与已经存储的手机号码关联(例如，可以建立手机号码与应用程序对应的数据表)并存储，进一步地，也可以由终端设备100将解析出的应用程序名于手机号码关联，并将二者的关联关系发送至网络服务器140-1。
在一些实施例中，终端设备100将已经获取到的本机电话号码与应用程序名的关联关系可以存储在终端设备100中。
在一些实施例中，收集应用程序服务器140的服务标识信息和存储应用程序与电话号码绑定关系的服务器也可以是相同的(即140-1和140-2是同一服务器)。
如图10所示，获取手机号码与应用程序关联关系系统的操作步骤如下：
步骤A：在图3的基础上了增加两个网络服务器140-1以及140-2。在手机号码绑定应用程序之前，由网络服务器140-1存储应用程序服务器130的服务标识信息，使终端设备100能够识别到验证信息的应用程序来源。
步骤B：在终端设备100收到验证信息时，根据步骤A存储在网络服务器140-1中的服务标识信息对验证信息进行判断，解析出对应的应用程序名。
步骤C：终端设备100将已经获取到的本机手机号码与上述解析出的应用程序名的进行关联(例如，可以建立手机号码与应用程序的绑定数据表)，对将上述关联关系(例如，可以是手机号码与应用程序名称对应关系的数据表)发送至网络服务器存储140-2(例如：可以根据用户需求上传至“华为云”)。
步骤D：可以根据用户的请求或者自动更新手机号码与应用程序的关联关系，并发送至终端设备100，可以根据绑定关系进行安装、解除绑定等操作。
图11为根据本发明一种可能的实施方式提供的手机号码与应用程序建立关联关系的系统示意图。该系统至少包括一个终端设备100、至少一个移动运营商110、至少一个验证信息处理服务器120、至少一个应用程序服务器130、至少一个网络服务器140。
如图11所示，该获取手机号码与应用程序关联关系的系统的步骤如下：
步骤A：由网络服务器140存储应用程序服务器130的服务标识信息，使终端设备100能够识别到验证信息的来源。
步骤B：在终端设备100收到验证信息时，将验证信息上传至网络服务器140，网络服务器140-1将收到的验证信息与存储的应用程序服务标识信息进行对比分析，解析出应用程序名。同时，终端设备100获取手机号码并发送至网络服务器140，网络服务器140可以将解析出的应用程序名与存储的手机号码进行关联(例如，可以建立手机号码与应用程序的绑定数据表)并存储。
步骤C：可以根据用户的请求或者自动更新手机号码与应用程序的关联关系，并发送至终端设备100，可以根据绑定关系进行安装、解除绑定等操作。
图12为根据本发明一种可能的实施方式提供的手机号码与应用程序建立关联关系的系统示意图。该系统至少包括一个终端设备100、至少一个移动运营商110、至少一个验证信息处理服务器120、至少一个应用程序服务器130、至少一个网络服务器140。
图12为根据本发明一种可能的实施方式提供的获取手机号码与应用程序关联关系的，其基本原理如图：
步骤A：网络服务器140收集并存储应用程序服务器130的服务标识信息。
步骤B：终端设备100收集到验证信息时，根据网络服务器140存储的服务标识信息解析应用程序名。
终端设备100获取本机的电话号码与解析出的应用程序名进行关联操作(例如，可以建立手机号码与应用程序的绑定数据表)，并存储在终端设备100本地。
步骤C：可以根据用户的请求或者自动更新手机号码与应用程序的关联关系，可以根据绑定关系进行安装、解除绑定等操作。
值得说明的是，本实施例的上述步骤并非是严格按照顺序，也可以是同时进行或者调整。同样，本实施例的一些功能实现也可以由多个设备来实现或者一个设备对个功能。
图13为根据本发明一种可能的实施方式提供的获取手机号码与应用程序绑定二者关联关系的流程图，其步骤如下：
步骤S200：终端设备100获取到验证类信息(例如，验证码短信)；
步骤S210：根据网络服务器140中存储的各应用程序的服务标识信息判断该信息是否源自于某一应用程序，如果不是则按照普通的信息处理，如果判断该信息来源于应用程序，则进入下一步；
步骤S220：解析出该验证信息对应的应用程序；
步骤S230：提取本终端设备100的电话号码(在多卡的情况下，可以是收到验证信息的手机号码)以及发送验证信息的程序名，并将二者的关联关系上传至网络服务器140或者终端设备100中。
步骤S240：可以根据用户的请求或者自动更新关联关系，并发送至终端设备100，用户可以根据关联关系进行安装、解除绑定等操作。
根据本发明一种可能的实施方式提供一种基于手机号码与应用程序关联关系安装应用程序的方法。图14-1为根据本发明一种可能的实施方式提供的处理手机号码与应用程序关联关系的用户界面150，该用户界面150的手机号码与应用程序绑定关系的数据来源是由网络服务器140提供(如图14-2提供的手机号码与应用程序关联数据表)，即将获取到的手机号码与应用程序的绑定关系传输至终端设备100中。在一些实施例中，用户知道终端100中的某一手机号码绑定应用程序的情况，即当前终端100未安装的但已经绑定的应用程序、或者终端100已经安装但未绑定的应用程序、或者终端100已经绑定且已经安装的应用程序。在一些实施例中，还可以对已经绑定的应用程序进行更换绑定手机的操作。在一些实施例中，还可以对多个程序进行解绑、安装、绑定、更换绑定号码等操作。
在一些实施例中，如果该终端设备100已经安装了与本机手机号码(例如，卡1)绑定的应用程序，如图14-1中的微信(wechat)程序，此时“安装应用”控件是不可操作状态(图中以虚线框表示)，而“解除绑定”控件呈现高亮状态(即可操作)。在一些实施例中，如果终端设备100未安装已经与本机手机号码绑定的应用程序，如图14-1中的“脸书(Facebook)”程序，此时“安装应用”控件呈现高亮状态(即可操作)，且“解除绑定”控件呈现高亮状态(即可操作)。在一些实施例中，如果终端设备100已经安装了但未绑定的应用程序，如图14-1中的QQ程序，此时“绑定”控件呈现高亮状态(即可操作)，而“安装应用”控件呈现不可操作状态(图中以虚线框表示)。在一些实施例中，还可以对已经绑定的应用程序进行更换手机号码的操作，例如，图14-1中微信、“脸书(Facebook)”、邮箱程序，此时“更换号码”控件呈现高亮状态，即表示“可操作状态”。
在一些实施例中，用户可以基于用户界面150提供的手机号码与应用程序绑定关系，对绑定但未安装的应用程序进行安装操作。如点击“脸书(Facebook)”程序的“安装应用”控件，则可以链接到应用程序下载的应用市场(例如，App Store等)界面160(如图15所示)。在一些实施例中，进入到图15所示的应用程序商店的下载界面150，直接进行下载操作。在一些实施例中，还需要在界面150中点击“安装”控件。
在一些实施例中，点击“脸书(Facebook)”程序的“安装应用”控件，也可以直接在当前界面进项下载操作。如图16，用户可以直接在当前界面150显示下载进度，而不用进入应用市场或者应用商店进行下载。
在一些实施例中，如图14-1，可能存在终端设备100已经安装该程序但未绑定场景，例如QQ程序，用户可以点击“绑定”控件，即进入QQ程序与电话号码绑定的界面(例如，进入如图8所示的绑定界面)。在一些实施例中，也可以跳转至应用程序客户端或者网页进行绑定操作。在一些实施例中，如果对已经绑定过的手机号码进行重新绑定时，系统会提醒“您输入的手机号码已经被其他账号绑定”，并提供相应的密码找回入口或者解除绑定、更换绑定手机号码入口。
在一些实施例中，还提供一种安装多个应用的方法。点击如图14-1中所示的“安装多个应用”按钮，弹出如图17的“安装多个应用”的设置界面170，通过点击需要安装应用程序的单选框或者全选框，即可进行多个应用程序下载安装操作。在一些实施例中，可以自动且连续的弹出应用程序商店下载界面。在一些实施例中，也可以在图14-1所示界面显示当前应用程序的下载进度(例如，图16中的Facebook程序下载)。
图18为根据本发明一种可能的实施方式提供的基于手机号码与应用程序绑定关系安装应用程序的流程图，其步骤如下：
步骤S310：获取已经建立的电话号码与应用程序之间的关联关系数据表(例如，图14-2)；
步骤S320：获取终端设备100本地的应用程序列表；
步骤S330：将关联关系数据表与本地应用程序安装列表对比后获取未安装的但已经绑定的应用程序状态(例如，还包括已经安装但未绑定的应用程序、已经绑定且已经安装的应用程序)，并显示于设置界面150(例如，“安装应用”控件呈现可操作状态)；
步骤S340：点击设置界面150中的“安装”图标(未安装的但已经绑定的应用程序)，进行下载或者跳转至应用商店进行下载。
本实施例提供的基于手机号码与应用程序绑定关系安装应用程序的方法可以适用于更换手机但没有更换电话号码的场景，或者再次使用已经绑定过的但已经删除的应用程序的场景，或者已经安装但未绑定应用程序的场景，在上述情况下，终端设备100读取本地安装的应用程序列表与网络服务器140-1中存储的手机号码与应用程序关联数据表(如图14-2)进行对比，可以获取未安装的但已经绑定的应用程序、已经安装但未绑定的应用程序、已经绑定且已经安装的应用程序，用户可以对已经绑定但是未安装的应用程序进行“安装应用”操作，还可以对未安装但已经绑定的应用程序进行“解除绑定”操作，还可以对已经安装的但未绑定的应用程序进行“绑定”操作，还可以对已经安装的且绑定的应用程序进行“解除绑定”操作。
根据本发明一种可能的实施方式还提供一种基于手机号码与应用程序关联关系解绑手机号码的方法。
在一些实施例中，用户可以基于手机号码关联程序界面150(如图14-1)提供的手机号码与应用程序绑定关系，对已经绑定的应用程序进行解除绑定的操作(包括终端设备100下载或者未下载的应用程序)。如图19，终端设备100提供一种解除绑定手机号码的设置界面180，在手机号码关联程序界面150点击“解除绑定”按钮后，进入对应应用程序的解除绑定界面180。在一些实施例中，解除绑定需要进行身份验证，验证的方式包括但不限于：电话号码验证、姓名验证、问题验证等。在一些实施例中，终端设备100将用户输入的验证信息发送至应用程序服务器130，应用程序服务器130将接收到身份验证信息与用户注册时的身份验证信息进行对比，验证成功后完成解除绑定操作。
在一些实施例中，网络服务器140-1存储有解绑应用程序所需要的身份验证信息。在一些实施例，网络服务器140-1将用户输入的身份验证信息发送至应用程序服务器130，例如，可以通过终端设备100发送至网络服务器140-1。进一步地，应用程序服务器130将接收到身份验证信息与用户注册时的身份验证信息进行对比，验证成功后完成解除绑定操作。在一些实施例中，如果是解绑多个应用程序，网络服务器140-1将用户输入的验证信息分别发送至需要解绑的应用程序所对应的应用程序服务器130。在一些实施例中，解除应用程序的绑定关系也 可以是删除网络服务器140-1中的应用程序与手机号码的关联关系，例如，删除应用程序与手机号码之间的关联关系。
在一些实施中，如点击如图14-1所示邮箱程序的“解除绑定”控件，弹出解除绑定界面180(如图19)，输入电话号码验证、姓名验证、问题验证等，验证成功后，实现解除绑定该应用程序。在一些实施例中，解除绑定界面180的身份验证包括但不限于回答安全问题、验证码、指纹识别、密码等。
在一些实施例中，也可以对已经绑定且安装的应用程序(例如，图14-1中的微信程序)进行解除绑定。在一些实施例中，解除绑定也可以跳转至应用程序客户端或者网页。
在一些实施例中，还提供一种解除绑定多个应用的方法，如点击图14-1中所示的“解绑多个应用”按钮，弹出如图20所示的“解绑多个应用”的设置界面190，单击需要解除绑定应用的单选框或者全选所有已经绑定的应用程序，点击“解除”按钮，即可自动且连续地弹出如图19所示的解除绑定验证界面180或者只需弹出一次解除绑定验证界面。
图21为基于手机号码与应用程序绑定关系解除绑定应用程序的流程图，其步骤如下：
步骤S400：“在手机号码绑定应用程序”界面150(如图14-1所示)点击需要解绑应用程序对应的“解绑”按钮；
步骤S410：从网络服务器140获取该应用程序服务器130服务标识信息，包括需要用户填写的身份验证信息。如新手机号码、原手机号码、验证问题1、验证问题2；
步骤S420：进入“解除绑定”设置界面140，输入解绑应用程序的身份验证信息；
步骤S420：将用户输入的身份验证信息由终端设备100发送至应用程序服务器130，应用程序服务器130将解除绑定应用程序的验证信息同用户注册时的信息进行对比，验证成功后完成解除绑定操作。
本实施例提供的基于手机号码与应用程序绑定关系解除绑定应用程序的方法可以适用于更换手机号码但没有更换终端(例如，可能需要用新的手机号码来绑定)的场景，或者不想再次使用已经绑定的应用程序，或者未安装但已经绑定应用程序(例如，已经删除且不想收到该应用程序收到的短息)的场景，在上述情况下，终端设备100读取本地安装的应用程序列表与网络服务器中绑定的应用程序列表(例如图14-2的数据表)进行对比，可以获取未安装的但已经绑定的应用程序、已经安装但未绑定的应用程序、已经绑定且已经安装的应用程序，用户可以对已经绑定但是未安装的应用程序进行“安装应用”操作，还可以对未安装但已经绑定的应用程序进行“解除绑定”操作，还可以对已经安装的但未绑定的应用程序进行“绑定”操作，还可以对已经安装的且绑定的应用程序进行“解除绑定”操作。
本实施例还提供一种更新手机号码与应用程序绑定关系的方法。
在一些实施例中，如图14-1所示，用户可以手动更新手机号码与应用程序的绑定关系，点击“刷新”按钮，终端设备100读取本地安装的应用程序列表，并与存储在服务器140中的手机号码与终端设备绑定关系的数据表进行重新对比，对比后获取未安装的但已经绑定的应用程序、已经安装但未绑定的应用程序、已经绑定且已经安装的应用程序，以更新界面150的数据供用户进行操作。
本实施例还提供一种应用程序更换绑定手机号码的方法。
如图8所示，提供一种更换绑定手机号码的界面140，在手机号码关联程序界面150(如图14-1)中点击需要更换绑定手机号码的应用程序对应的“更换号码”按钮，则进入更换绑 定手机号码的界面140，输入原手机号码、需要绑定的手机号码，验证后即可完成更换绑定号码操作。
在一些实施例中，如图22，还提供对多个已经关联的应用程序进行换绑操作的界面200，点击图14-1中的手机号码关联应用界面150中的“换绑多个应用”控件，进入到换绑多个应用界面200，可以选中单个需要换绑的应用程序或者全选需要换绑的应用程序，点击“换绑”按钮后，可以进入图14-1所示的更换绑定手机界面140。在一些实施例中，可以自动且连续地弹出如图8所示的解除绑定验证界面140或者只需弹出一次解除绑定验证界面140。
本方法可以适用于用户更换手机号码的场景，需要利用解除原手机号码与应用程序的绑定关系，而绑定新的手机号码，重新绑定新的手机号码，该应用程序中的数据(例如，聊天记录、账户名)保持不变，用户仍然可以通过用户名、新手机号码登录该应用程序。
本实施例提供一种基于手机号码与终端设备关系的改变来进行提示用户进行绑定、安装等操作的方法。
在一些实施例中，终端设备100的国际移动设备识别码(International Mobile Equipment Identity，IMEI)是唯一且固定的，IMEI俗称“手机串号”，存储在手机的EEPROM里。在一些实施例中，终端设备100可以获取或者读取到本机的手机号码，例如读取手机SIM卡的MSISDN(Mobile Subscriber International ISDN number)信息。在一些实施例中，可以将手机号码与手机串号建立数据表，并存储在网络服务器140-1，进一步地，还可以存储在终端设备100中。
在一些实施中，如果检测到终端设备100与手机号码之间的关系发生了改变(例如，换号不换机或者换机不换号)，具体地，终端设备100的IMEI码与手机的电话号码的对应关系发生改变，则触发并更新手机号码与应用程序的绑定关系，例如做提示“发现已更换手机，请进行手机号码与应用程序绑定操作”，用户确认后可以进入如图14-1所示的设置界面150。
如图23所示，提供基于手机号码与终端设备关系的改变来进行提示用户进行关联操作的流程图：
步骤S510：手机号码(唯一标识)与手机终端的IMEI(手机的唯一标识)发生改变。即换号不换机，或换机不换号，进入下一步；
步骤S520：终端设备提示用户，如“发现已更换手机号，请对手机号码绑定应用”；
步骤S530：确定后弹出设置界面，如图14-1“手机号码关联应用程序”界面140中。
根据本发明一种可能的实施方式还提供一种基于云账号映射手机号码与应用程序关联关系的方法。如图10所示，该基于云账号映射手机号码与应用程序关联关系的方法如下：
步骤A：网络服务器140-1存储应用程序服务器130的服务标识信息，使终端设备100能够识别到验证信息的应用程序来源。
步骤B：在终端设备100收到验证信息时，根据步骤A存储在网络服务器140-1中的服务标识信息对验证信息进行判断，解析出对应的应用程序名。
步骤C：终端设备100将已经获取到的本机手机号码与上述解析出的应用程序名的进行关联，对将上述关联关系(例如，可以是手机号码与应用程序名称对应关系的数据表)发送至网络服务器存储140-2，网络服务器140-2将该手机号码与应用程序名关联关系表与用户的云账号进行映射操作(例如，可以是如图24-1所示的数据表)。
步骤D：可以根据用户的请求或者自动更新关联关系，并发送至终端设备100，用户可以根据关联关系进行安装、解除绑定等操作
其中步骤A，在一些实施例中，网络程序服务器140-1获取应用程序服务器130发送验证信息的服务标识，该服务标识可以用于终端设备100通过接收验证信息来判断应用程序名称。在一些实施例中，应用程序服务器130的发送验证信息的服务标识可以是验证信息的发送源(网易云音乐的短信发送源为1069125295163)、MAC地址、IP地址、服务器名称、解绑所需要的身份验证信息等其中至少一项。在一些实施例中，获取的方式可以通过由终端厂商收集或者应用程序厂商上报或公开服务标识信息等。在一些实施例中，网络服务器140-1还可以存储终端设备100中的电话号码，例如由终端设备100上传至网络服务器140-1。在一些实施例中，读取手机号码的方式可以是通过读取手机SIM卡的MSISDN(Mobile Subscriber International ISDN number)信息。
其中步骤B，在一些实施例中，在终端设备100收到验证信息时，将验证信息上传至网络服务器140-1，网络服务器140-1将收到的验证信息与存储的应用程序服务标识信息进行对比分析，解析出应用程序名。在一些实施例中，网络服务器140-1可以将解析出的应用程序名与存储的手机号码进行关联(例如，可以建立手机号码与应用程序的绑定数据表)并存储。在一些实施例中，网络服务器140-1可以将解析出的应用程序名与存储的手机号码进行关联并发送至网络服务器140-2。网络服务器140-2将该手机号码与应用程序名关联关系表与用户的云账号(例如，华为账号)进行映射操作(例如，可以是如图24-1所示的数据表)，在此种场景下，终端设备100登录云账号，用户即可以知道手机号码与应用程序之间的关系。
其中步骤C，在一些实施例中，网络服务器140-1还可以存储终端设备100中的电话号码(例如，可以由终端设备100上传手机号码)，终端设备100将解析出的应用程序名上传至网络服务器140-1并与已经存储的手机号码关联并存储。
其中步骤D，在一些实施例中，终端设备100将已经获取到的本机电话号码与应用程序名的关联关系可以存储在终端设备100中。
在一些实施例中，收集应用程序服务器140的服务标识信息和存储应用程序与电话号码绑定关系的服务器也可以是相同的(即140-1和140-2是同一服务器)。
在一些实施例中，如图24-1所示，用户的云账号可以映射多个手机号码与应用程序关联关系。在一些实施例中，如图24-2，手机号码与应用程序的关联关系也可以扩展到第三方应用程序账号与应用程序关联。进一步地，用户的云账号可以与第三方应用程序账号与应用程序关联的关系进行映射。
在一些实施例中，如图25，提供一种提醒用户当前需要绑定的应用程序已经由其他手机号码绑定界面210(例如，图5界面130)，例如用户的云账号123456@huawei.com映射手机号码1与应用程序1的关联关系以及手机号码2与应用程序2的关联关系，用户需要利用手机号码2绑定应用程序1时，系统会提醒“根据您的华为账号123456@huawei.com显示，您的手机号1320000000已经绑定过该应用程序，是否确认当前号码继续绑定”并提供“继续绑定”、“使用已经绑定的手机号码登录”的入口。
本实施例可以适用于用户换手机同时又换手机号的场景，云账号首先映射了原手机号码与应用程序的关联关系，用户的新的终端设备登录云账号后，通过云账号中的关联关系与本地应用程序的安装列表，更新如图14-1所示的手机号码关联应用程序界面150，然后云账号 映射新的手机号码与应用程序的关联关系，更新如图14-1所示的手机号码关联应用程序界面150。
本发明的各实施方式可以任意进行组合，以实现不同的技术效果。在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本发明所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本发明技术方案的实施例而已，并非用于限定本发明的保护范围。凡根据本发明的揭露，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (11)

  1. 一种方法，其特征在于，包括：
    终端设备显示第一应用程序的第一登录界面，其中，所述终端设备存储有第一手机号码与所述第一应用程序之间的关联关系；
    获取到第二手机号码，所述终端设备将所述第二手机号码与所述第一手机号码进行对比；
    当所述第二手机号不同于所述第一手机号码时，所述终端设备提示用户所述第一手机号码已经关联所述第一应用程序。
  2. 根据权利要求1中所述的方法，其特征在于：
    当所述第二手机号不同于第一手机号码时，所述终端设备允许用户利用所述第二手机号码登录和/或第一手机号码登录。
  3. 一种方法，其特征在于，包括；
    终端设备显示第一应用程序的第一登录界面，所述终端设备存储有第一账号与所述第一应用程序之间的关联关系；
    获取到第二账号，其中，所述第二账号不同于所述第一账号；
    当所述第二账号没有关联所述第一应用程序时，所述终端设备提示用户所述第二账号已经关联所述第一应用程序，其中，所述第一账号与所述第二账号通过第三账号关联。
  4. 如权利要求3所述的方法，其特征在于：
    当所述第二账号已经关联所述第一应用程序，所述终端设备使用所述第二账号登录所述第一应用程序。
  5. 一种方法，其特征在于，包括：
    终端设备显示第一界面，所述第一界面包含有第一应用程序的图标，以及用于下载所述第一应用程序的控件；
    其中，所述终端设备存储有第一手机号码与第一应用程序关联关系，所述终端设备没有安装所述第一应用程序；
    获取到针对所述第一界面的第一操作，所述终端设备跳转至所述第一应用程序的下载界面。
  6. 如权利要求5所述的方法，其特征在于，进一步包括：
    所述第一界面包含有第二应用程序图标，以及用于登陆第二应用程序的控件；
    其中，所述第一手机号码没有关联所述第二应用程序，且所述终端设备安装有所述第二应用程序。
    获取到针对所述第一界面的第二操作，所述终端设备跳转至第二应用程序的登录界面。
  7. 如权利要求5或6中所述的方法，其特征在于，进一步包括：
    所述第一界面包含有跳转至第二界面的控件；
    获取到针对所述第一界面的第三操作，所述终端设备跳转至所述第二界面；
    获取到用户在所述第二界面输入的鉴权信息；
    当鉴权成功时，所述第一手机号码与所述第一应用程序解除关联关系。
  8. 如权利要求5或6中任一项所述的方法，其特征在于，进一步包括：
    所述第一界面包含有跳转至第三界面的控件；
    获取到针对所述第一界面的第四操作，所述终端设备跳转至第三界面；
    获取到第二手机号码，所述第二手机号码关联所述第一应用程序，所述第一手机号码与所述第一应用程序解除关联关系，其中，第一手机号码不同于第二手机号码。
  9. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在电子设备上运行时，使得所述电子设备执行如权利要求1-8中任一项所述的方法。
  10. 一种计算机可读存储介质，包括指令，其特征在于，当所述指令在电子设备上运行时，使得所述电子设备执行如权利要求1-8中任一项所述的方法。
  11. 一种终端设备，包括：
    处理器；及
    存储介质，其中，所述存储介质存储有指令，所述指令使得所述终端设备执行权利要求1-8中任一项所述的方法。
PCT/CN2017/112208 2017-11-21 2017-11-21 判定手机号码与应用关联关系的方法 WO2019100223A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2017/112208 WO2019100223A1 (zh) 2017-11-21 2017-11-21 判定手机号码与应用关联关系的方法
CN201780097035.3A CN111373780A (zh) 2017-11-21 2017-11-21 判定手机号码与应用关联关系的方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/112208 WO2019100223A1 (zh) 2017-11-21 2017-11-21 判定手机号码与应用关联关系的方法

Publications (1)

Publication Number Publication Date
WO2019100223A1 true WO2019100223A1 (zh) 2019-05-31

Family

ID=66631315

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/112208 WO2019100223A1 (zh) 2017-11-21 2017-11-21 判定手机号码与应用关联关系的方法

Country Status (2)

Country Link
CN (1) CN111373780A (zh)
WO (1) WO2019100223A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101959179A (zh) * 2009-07-17 2011-01-26 华为技术有限公司 一种提供移动终端应用程序的方法、服务器和移动终端
CN102722400A (zh) * 2012-04-24 2012-10-10 北京小米科技有限责任公司 一种关联移动终端通信录和应用程序的方法、系统及im
EP2990955A1 (en) * 2013-04-26 2016-03-02 KPI Solutions Co., Ltd. Program, information processing terminal, and information processing method
CN105554733A (zh) * 2015-12-17 2016-05-04 北京乐动卓越科技有限公司 手机应用程序注册方法和装置
CN106534119A (zh) * 2016-11-09 2017-03-22 福建中金在线信息科技有限公司 一种客户端软件登录信息的提示方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104320756B (zh) * 2014-11-18 2018-09-14 广东欧珀移动通信有限公司 一种账号信息的变更方法及装置
CN105472596A (zh) * 2015-11-23 2016-04-06 小米科技有限责任公司 通信号码的绑定方法、装置及终端
CN107040497B (zh) * 2016-02-03 2020-07-03 阿里巴巴集团控股有限公司 网络账号防盗方法及装置
CN105897873A (zh) * 2016-04-01 2016-08-24 努比亚技术有限公司 一种更换绑定手机号的装置和方法
CN107154971A (zh) * 2017-04-28 2017-09-12 珠海市魅族科技有限公司 一种应用下载方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101959179A (zh) * 2009-07-17 2011-01-26 华为技术有限公司 一种提供移动终端应用程序的方法、服务器和移动终端
CN102722400A (zh) * 2012-04-24 2012-10-10 北京小米科技有限责任公司 一种关联移动终端通信录和应用程序的方法、系统及im
EP2990955A1 (en) * 2013-04-26 2016-03-02 KPI Solutions Co., Ltd. Program, information processing terminal, and information processing method
CN105554733A (zh) * 2015-12-17 2016-05-04 北京乐动卓越科技有限公司 手机应用程序注册方法和装置
CN106534119A (zh) * 2016-11-09 2017-03-22 福建中金在线信息科技有限公司 一种客户端软件登录信息的提示方法及装置

Also Published As

Publication number Publication date
CN111373780A (zh) 2020-07-03

Similar Documents

Publication Publication Date Title
US10057627B2 (en) Method, apparatus and system for displaying bullet screen information
EP3389230A2 (en) System for providing dialog content
WO2016150270A1 (zh) 群组会话消息处理方法和装置
CN106126174B (zh) 一种场景音效的控制方法、及电子设备
CN108156508B (zh) 弹幕信息处理的方法、装置、移动终端、服务器及系统
WO2015035947A1 (zh) 一种实现无卡手机的方法、手机和服务器
CN108834132B (zh) 一种数据传输方法及设备和相关介质产品
WO2018049893A1 (zh) 数据传输方法及终端设备
WO2017193496A1 (zh) 应用数据的处理方法、装置和终端设备
JP2017521899A (ja) インタラクティブ情報を獲得するための方法、端末、サーバ、およびシステム
CN106843868B (zh) 一种多账号登录的方法、装置以及移动终端
WO2015010466A1 (zh) 信息显示方法、装置和移动终端
WO2017215661A1 (zh) 一种场景音效的控制方法、及电子设备
WO2018049894A1 (zh) 数据传输方法及设备
WO2021078215A1 (zh) 一种云游戏跨终端切换的方法和相关装置
WO2018161540A1 (zh) 指纹注册方法及相关产品
US9965733B2 (en) Method, apparatus, and communication system for updating user data based on a completion status of a combination of business task and conversation task
CN109495638B (zh) 一种信息显示方法及终端
CN104573437A (zh) 信息认证方法、装置和终端
CN107277031A (zh) 一种网络视频下载方法、装置、存储介质和终端
CN107765954B (zh) 一种应用程序图标更新方法、移动终端及服务器
US20160308879A1 (en) Application-Based Service Providing Method, Apparatus, and System
WO2015062234A1 (zh) 移动终端资源处理方法、装置和设备
CN108270764B (zh) 一种应用登陆方法、服务器及移动端
CN109728918B (zh) 虚拟物品发送方法、虚拟物品接收方法、装置及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17932679

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17932679

Country of ref document: EP

Kind code of ref document: A1