WO2015027823A1

WO2015027823A1 - Method, binding server, terminal, and system for binding multiple terminals

Info

Publication number: WO2015027823A1
Application number: PCT/CN2014/084376
Authority: WO
Inventors: Xuemin Ma; Xuechao LI; Zifeng Shang
Original assignee: Tencent Technology (Shenzhen) Company Limited
Priority date: 2013-08-29
Filing date: 2014-08-14
Publication date: 2015-03-05
Also published as: CN104426962A; CN104426962B

Abstract

Methods, binding servers, terminals, and systems for binding multiple terminals are provided herein. In an exemplary method implemented by a binding server, device information of a first terminal is obtained. A URL corresponding to the device information of the first terminal is generated. 2D code data containing the URL are generated and sent to the first terminal. A connection request sent by a second terminal is received. The connection request carries device information of the second terminal and a URL. It is determined whether the URL carried in the connection request matches the generated URL. When the URL carried in the connection request matches the generated URL, a binding relationship between the first terminal and the second terminal is established. A binding-success message is sent to the first terminal and the second terminal. The binding-success message carries the device information of the first terminal and the second terminal.

Description

METHOD, BINDING SERVER, TERMINAL, AND SYSTEM FOR BINDING

MULTIPLE TERMINALS

CROSS-REFERENCES TO RELATED APPLICATIONS

[0001] This application claims priority to Chinese Patent Application

No.201310386121.X, filed on August 29, 2013, the entire content of which is incorporated hereinby reference.

FIELD OF THE DISCLOSURE

[0002] The present disclosure generally relates tothe field of communication technology and, more particularly, relates to methods, binding servers, terminals, and systems for binding multiple terminals.

BACKGROUND

[0003] With rapid development of communication technology, terminals such as smart phone, tablet computer, PC (personal computer), etc. havehad significant development. Various terminals can support usage of certain identical application programs. For example, a mobile phone and a PC can often be bound to support the usage of certain identical application programs. When the PC uses an application program, the mobile phone that is bound with the PC can use the same application program at the same time. Thus, dataof the same application program can be simultaneously presented to different users.

[0004] Conventionally, a method for binding multiple terminals can include the following process.First, by registering an account, a user obtainsthe permission to use a certain application program.Next, using account information of theregistered account, such as user name and password, the user logs in the application program on each terminal. The userthen sendsattribute information of the terminal having the application programto a binding server, and sends the account information to the binding server. Finally, according to the account information sent by each terminal, the bindingserver binds the terminals having the same account information.

[0005] However, the conventional method for binding multiple terminals has to rely on an account system of the application program that is used by terminals. The user has to register the account in order to use the application program. In addition, the binding of multiple terminals can only be achieved by logging in the application program using the same account information simultaneously on each terminal. The operation is thus burdensome.

BRIEF SUMMARY OF THE DISCLOSURE

[0006] One aspect of the present disclosure includes methods for binding multiple terminals implemented by a binding server. In an exemplary method, device information of a first terminal can be obtained. A uniform resource locator (URL) corresponding to the device information of the first terminal can be generated. Two-dimensional (2D) code data containing the URL can be generated. The 2D code data can be sent to the first terminal. A connection request sent by a second terminal can be received. The connection request can carry device information of the second terminal and a URL. It can be determined whether the URL carried in the connection request matches the generated URL. When the URL carried in the connection request matches the generated URL, a binding relationship between the first terminal and the second terminal can be established. A binding-success message can be sent to the first terminal and the second terminal. The binding-success message can carry the device information of the first terminal and the second terminal.

[0007] Another aspect of the present disclosure includes methods for binding multiple terminals. In an exemplary method,device information of a first terminal can be uploadedto a binding server. After the binding server generates a URL corresponding to the device

information of the first terminal and returns 2D code data containing the URL, the 2D code data containing the URL can be received. After a second terminal scans the 2D code data and uploads, to the binding server, the URL contained in the 2D code data and device information of the second terminal, a binding-success message returned by the binding server can be received. The binding-success message can carry the device information of the second terminal. [0008] Another aspect of the present disclosure includes systems for binding multiple terminals. An exemplary system can include a binding server. Thebinding server can include an obtaining module, a first generating module, a second generating module, a first sending module, a receiving module, a determining module, a first establishing module, and a second sending module. The obtaining module can be configured to obtain device information of a first terminal. The first generating module can be configured to generate a URL corresponding to the device information of the first terminal. The second generating module can be configured to generate 2D code data that contain the URL. The first sending module can be configured to send the 2D code data to the first terminal. The receiving module can be configured to receive a connection request sent by a second terminal. The connection request can carry device information of the second terminal and a URL. The determining module can be configured to determine whether the URL carried in the connection request matches the generated URL. The first establishing module can be configured to, when the URL carried in the connection request matches the generated URL, establish a binding relationship between the first terminal and the second terminal. The second sending module can be configured to send a binding-success message to the first terminal and the second terminal. The binding-success message can carry the device information of the first terminal and the second terminal.

[0009] Other aspects of the present disclosure can be understood by those skilled in the art in light of the description, the claims, and the drawings of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The following drawings are merely examples for illustrative purposes according to various disclosed embodiments and are not intended to limit the scope of the disclosure.

[0011 ] FIG. 1 depicts an exemplary environment for implementing a method for binding multiple terminals in accordance with various disclosed embodiments;

[0012] FIG. 2 depicts aflow diagram of an exemplary method for binding multiple terminalsin accordance with various disclosed embodiments;

[0013] FIG. 3 depicts a flow diagram of another exemplary method for binding multiple terminals in accordance with various disclosed embodiments;

[0014] FIG. 4 depicts a flow diagram of another exemplary method for binding multiple terminals in accordance with various disclosed embodiments;

[0015] FIG. 5 depicts a flow diagram of another exemplary method for binding multiple terminals in accordance with various disclosed embodiments;

[0016] FIG. 6 depicts exemplary 2D code data in accordance with various disclosed embodiments; [0017] FIG. 7 depicts displaying of a binding relationship in accordance with various disclosed embodiments;

[0018] FIG. 8 depicts astructure diagram of an exemplary binding server in accordance with various disclosed embodiments;

[0019] FIG. 9 depicts a structure diagram of an exemplary terminal in accordance with various disclosed embodiments;

[0020] FIG. 10 depicts a structure diagram of another exemplary terminal in accordance with various disclosed embodiments;

[0021] FIG. 11 depicts a structure diagram of an exemplary system for binding multiple terminals in accordance with various disclosed embodiments;

[0022] FIG. 12 depicts a structure diagram of another exemplary terminal in accordance with various disclosed embodiments;

[0023] FIG. 13 depicts a structure diagram of another exemplary terminal in accordance with various disclosed embodiments;

[0024] FIG. 14 depicts an exemplary method for binding multiple terminals in accordance with various disclosed embodiments;

[0025] FIG. 15 depicts exemplary 2D code data in accordance with various disclosed embodiments; and

[0026] FIG. 16 depicts displaying of a binding relationship in accordance with various disclosed embodiments. DETAILED DESCRIPTION

[0027] Reference will now be made in detail to exemplary embodiments of the disclosure, which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

[0028] The present disclosure can address certain problems inserver technology and terminal device technology. Using the server as disclosed, a server can establish a binding relationship between multiple terminals without having to use account information.

[0029] Various embodiments providemethods, binding servers, terminals, and systems for binding multiple terminals. FIG. 1 depicts an exemplary environment for implementing a method for binding multiple terminals in accordance with various disclosed embodiments. As shown in FIG. 1, the environment can includea binding server 103, a terminal 101, and a terminal 102. The terminal 101 orthe terminal 102 can includea smart phone, a tablet PC, an e- book reader, an MP3 (Moving Picture Experts Group Audio Layer III) player, an MP4 (Moving Picture Experts Group Audio Layer IV) player, a portable laptop computer,a desktop computer, orthe like. The terminal 101 and the terminal 102 can be electronic devices of the same type, or of different types. In the environment as shown in FIG.l, the binding server 103 can

communicate with the terminal 101 and the terminal 102 via a wired network or a wireless network. Further, binding of the terminal 101 and the terminal 102 can be achieved via the binding server 103. The binding server 103 can include any appropriate server computer that is used for implementing the method for binding multiple terminals according to various

embodiments.

[0030] For illustrative purposes, only the terminal 101 and the terminal 102 are shown in FIG. 1. However, more terminals can be included in the environment, in addition to the terminal 101 and the terminal 102. In the exemplary methods depicted in various embodiments as disclosed herein, the terminal 101 can be referred to as the first terminal, the terminal 102 can be referred to as the second terminal, and binding of the terminal 101 and the terminal 102 can be achieved via the binding server 103.

[0031] Various embodimentsprovide a method for binding multiple terminals. In one embodiment, the method can be implemented by a binding server as shown in FIG. 1. FIG. 2 depicts a flow diagram of an exemplary method for binding multiple terminals in accordance with various disclosed embodiments. As shown in FIG. 2, the method can include the following exemplary process.

[0032] In Step 201, device information of a first terminal is obtained, to generate a uniform resource locator (URL) corresponding to the device information of the first terminal.

[0033] In Step 202, two-dimensional (2D) code data, i.e., 2D barcode data or QR code data, that contains the URL is generated and sent tothe first terminal.In various embodiments, the 2D code data can include a 2D barcode (i.e., a 2D barcode or a QR code).

[0034] In Step 203, a connection request sent by a second terminal is received, the connection request carrying device information of the second terminal anda URL.

[0035] In Step 204, it is determined whether the URL carried in the connection request matches the generated URL.

[0036] Optionally, after the URL corresponding to the device information of the first terminal is generated, the method can further include the following process. A mapping relationship between the generated URL and the device information of the first terminal can be established and stored. The stored mapping relationship can record the mapping relationship between a URL and device information of a terminal, i.e., can indicate a URL has a mapping relationship or maps to device information of a terminal.

[0037] The determining of whether the URL carried in the connection request matches the generated URL can include the following process. The URL carried in the connection request can be looked up and found in the stored mapping relationship. That is, the binding server can search the stored mapping relationship for the URL carried in the connection request. When the URL carried in the connection requestis found, it can be determined that the URL carried in the connection request matches the generated URL.

[0038] In Step 205, when the URL carried in the connection request matches the generated URL, a binding relationship between the first terminal and the second terminal is established. A binding-success message can be sent to the first terminal and the second terminal. The binding-success messagecan carry the device information of the bound terminal(s).

[0039] Optionally, after the binding relationship between the first terminal and the second terminal is established, the method can further include the following process. The device information of the second terminal can be added to the mapping relationship between the generated URL and the device information of the first terminal.

[0040] In one embodiment, the method can be implemented by a first terminal. FIG. 3 depicts a flow diagram of another exemplary method for binding multiple terminals in accordance with various disclosed embodiments. As shown in FIG. 3, the method can include the following exemplary process.

[0041] In Step 301, device information is uploaded to a binding server. The binding server can generate a URL corresponding to the device information of the first terminal, and can return 2D code data containing the URL to the first terminal. The first terminal thus receives the 2D code data containing the URL. In various embodiments, the device information uploaded to the binding server by the first terminal can include the device information of the first terminal.

[0042] In Step 302, after a second terminal scansthe 2D code data and uploads, to the binding server, the URL contained in the 2D code data and device information of the second terminal, a binding-success messagereturned by the binding server is received. The binding- success message can carry the device information of the second terminal.

[0043] Optionally, after the first terminal receives the 2D code data containing the URL that is returned by the binding server after the binding server generates the URL corresponding to the device information of the first terminal, the method can further include the following process. The received 2D code data can be displayed.

[0044] Optionally, after the binding-success message returned by the binding server is received, the method can further include the following process. According to the device information of the second terminal carried in the binding-success message, a binding

relationshipcan be displayed.

[0045] In one embodiment, the method can be implemented by a second terminal. FIG. 4 depicts a flow diagram of another exemplary method for binding multiple terminals in accordance with various disclosed embodiments. As shown in FIG. 4, the method can include the following exemplary process.

[0046] In Step 401, 2D code datacorresponding to a first terminal is scanned, to obtaina URL or URL information contained in the 2D code data. The 2D code data can be 2D code data that contains a URL and is previously generated by a binding server after the binding server generates the URL corresponding to device information of a first terminal. [0047] In Step 402, a connection request can be sent to the binding server, the connection request carrying the URL and the device information of the second terminal.

[0048] In Step 403, a binding-success message returned by the binding server is received. The binding-success message can carry the device information of the first terminal.

[0049] Optionally, after the binding-success message returned by the binding server is received, the method can further include the following process. According to the device information of the first terminal carried in the binding-success message, a binding relationship can be displayed.

[0050] In the methods provided by various disclosed embodiments, a URLcorresponding to device information of a first terminal can be generated by a binding server. 2D code data containing the URL can be generated and sent to the first terminal. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process forbinding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[0051] By combining the various other embodiments (e.g., as shown in FIGS. 2-4) and the environmentas shown in FIG. 1 , a method for binding multiple terminals is provided. FIG. 5 depicts a flow diagram of another exemplary method for binding multiple terminals in accordance with various disclosed embodiments. As shown in FIG. 5, the method can include the following exemplary process.

[0052] In Step 501, a first terminal uploads device information of the first terminal to a binding server. For example, after the first terminal establishes a connection or a communication connection with the binding server in the environment as shown in FIG. 1 , the first terminal can upload its own device information to the binding server.

[0053] The method for the first terminal to upload its own device information to the binding server is not limited in the present disclosure. For example, during actual

implementation, the first terminal can encode the device information. Thus, the encoded device information can comply with an http (hypertext transport protocol) request method. According, the first terminal can send to the binding server an http request that carries the device information, to achieve the sending of the device information to the binding server.

[0054] Content of the device information of the first terminal is not limited in the present disclosure. The device information can be used by the binding server to identify the first terminal. For example, the device information of the first terminal can include, but is not limited to, the name, the GUID (Globally Unique Identifier), the IMEI (International Mobile Equipment Identity), and the like, of the first terminal. Optionally, the device information uploaded to the binding server by the first terminal can further include information the current status of the first terminal. The current statuscan include, but is not limited to,an "online" status, or an "offline" status. The "online" status can indicate that the first terminal is currently in a status of being visible to other terminals. The "offline" status can indicate that the first terminal is currently in a status of being not visible to other terminals, i.e., an invisible status.

[0055] In Step 502, the binding server obtains the device information of the first terminal, and generatesan URL corresponding to the device information of the first terminal.

[0056] For example, after the first terminal uploads the device information of the first terminal to the binding server, the binding server can obtain the device information of the first terminal. The method for the binding server to obtain the device information of the first terminal is not limited in the present disclosure. For example, during actual implementation,when the first terminal uploads the device information of the first terminal to the binding server via sending to the binding server an http request carrying the device information, the binding server can parse the http request to obtain the device information of the first terminal.

[0057] After the binding server obtains the device information of the first terminal, the binding server can generate an URL corresponding to the device information of the first terminal. The method for the binding server to generate the URL corresponding to the device information of the first terminal is not limited in the present disclosure.

[0058] In one example, during actual implementation, the binding servercan directly generate a URL containing the device information of the first terminal, such that the URL can correspond to the device information of the first terminal. For example, the binding server can generate the URL corresponding to the device information of the first terminal according to information including the protocol type and/or the port number by which the first terminal communicates with the binding server, the storage path of the device information of the first terminal on the binding server, and/or the like.

[0059] In another example, the binding server can randomly assign an arbitrary URL for the first terminal, and the first terminal can just be used for corresponding to the device information of the first terminal. The method for randomly assigningan arbitrary URL for the first terminal, and the assigned URL,are not limited in the present disclosure.

[0060] Optionally, after the binding server generates the URL corresponding to the device information of the first terminal, the method can further include the follow process. A mapping relationship between the generated URL and the device information of the first terminal can be established and stored on the binding server. The method for the binding server to establish and store the mapping relationship between the generated URL and the device information of the first terminal is not limited in the present disclosure. For example, during actual implementation, the binding server can establish a mapping relationship table in the internal storage structure of the binding server, to record the correspondence relationship between the generated URL and the device information of the first terminal.

[0061] In Step 503, the binding server generates 2D code data containing the URL, and sends the 2D code data to the first terminal. For example, after the binding server generates the URL corresponding to the device information of the first terminal, in order for other terminal(s) to obtain the URL relatively easily, 2D code data containing the URL can be further generated. The method for the binding server to generate the 2D code data containing the URL is not limited in the present disclosure. For example, during actual implementation, the 2D code data containing the URL can be generated by a 2D-code generating tool, or a 2D-code generator.

[0062] Furthermore, after the binding server generates the 2D code data containing the URL, the binding server can send the 2D code data to the first terminal, such that the first terminal can obtain the 2D code data of the URL corresponding to the device information of the first terminal.

[0063] In Step 504, the first terminal receives the 2D code data containing the URL that is returned by the binding server, and displays the 2D code data.For example, when the first terminal receives the 2D code data that is returned by the binding server and that contains the URL corresponding to the device information of the first terminal, the first terminal can display the 2D code data. The method for the first terminal to display the 2D code data is not limited in the present disclosure. For example, FIG. 6 depicts exemplary 2D code data in accordance with various disclosed embodiments. The first terminal can display the received 2D code data as shown in FIG. 6. The time at which the first terminal displays the 2D code data is not limited in the present disclosure. For example, the first terminal can display the 2D code data during the launching or starting of a certain application program.

[0064] In Step 505, a second terminal scans the 2D code data corresponding to the first terminal, to obtain the URL contained in the 2D code data, and sends to the binding server a connection requestcarrying the URL and the device information of the second terminal. By scanning the 2D code data corresponding to the first terminal, the second terminal canobtain the URL contained in the 2D code data. The method for the second terminal to obtain the contained URL by scanning the 2D code data corresponding to the first terminal, in the 2D code data is not limited in the present disclosure.

[0065] In various embodiments, in order to enable the second terminal to obtain the URL contained in the 2D code data by scanning the 2D code data corresponding to the first terminal, a scanning tool or a scanner that supports 2D code data (i.e., a 2D-code-data scanner) can be installed on the second terminal. Thus, the 2D code data corresponding to the first terminal can be scanned by the 2D-code-datascanner, to obtain the URL contained in the 2D code data.

[0066] After the second terminal obtains the URL contained in the 2D code data by scanning the 2D code data corresponding to the first terminal, the second terminal can send to the binding server a connection request carrying the URL and the device information of the second terminal. Thus, according to the connection request, the binding server can determine whether to bind the second terminal with the first terminal. The method for the second terminal to send to the binding server the connection request carrying the URL and the device information of the second terminal is not limited in the present disclosure. For example, during actual implementation, the second terminal can send the connection request to the binding server by sending an http request.

[0067] Content of the device information of the second terminal is not limited in the present disclosure. For example, the device information of the second terminal can include, but is not limited to, the name, the GUID, the IMEI, and the like, of the second terminal.

[0068] In Step 506, the binding server receives the connection request that is sent by the second terminal and that carries the URL and the device information of the second terminal. The binding server determines whether the URL carried in the connection request matches the URL corresponding to the device information of the first terminal and generated by the binding server. When the URL carried in the connection request matches the URL corresponding to the device information of the first terminal and generated by the binding server, Step 507 can be performed.

[0069] After the binding server receives the connection request sent by the second terminal, the binding server can parsethe connection request to obtain the URL carried in the connection request. The binding server can thus determine whether the URL carried in the connection request matches the URL corresponding to the device information of the first terminal and generated by the binding server.

[0070] Optionally, during the determining by the binding server of whether the URL carried in the connection request matches the URL corresponding to the device information of the first terminal and generated by the binding server, the binding server can look for and find the URL carried in the connection request, in the stored mapping relationship between the device information of the first terminal and the URL corresponding to the device information of the first terminal. That is, the binding server can search the stored mapping relationship for the URL carried in the connection request. When the URL carried in the connection request is found, it can be determined that the URL carried in the connection request matches the URL corresponding to the device information of the first terminal and generated by the binding server. A binding relationship between the first terminal and the second terminal can be established. When the URL carried in the connection request is not found, it can be determined that the URL carried in the connection request does not match the URL corresponding to the device information of the first terminal and generated by the binding server.

[0071 ] The method for the binding server to find the URL carried in the connection request in the stored mapping relationship between the device information of the first terminal and the corresponding URL is not limited in the present disclosure. For example, during actual implementation, when the binding server store the generated URL corresponding to the device information of the first terminal, the binding server can establish a mapping relationship table in the internal storage structure of the binding server. The mapping relationship table can contain mapping relationship between various terminals and the respective URLs corresponding to each of the various terminals. Thus, at this time, the binding server can compare the URL carried in the connection request with the URLs recorded in the mapping relationship tableone by one, to find, in the mapping relationship table, the URL carried in the connection request.

[0072] During this step, when the mapping relationship table stored on the binding server has a URL consistent with the URL carried in the connection request, it can be determined that the URL carried in the connection request matches the URL corresponding to the device information of the first terminal and generated by the binding server. Accordingly, the binding relationship between the first terminal and the second terminal can be established.

[0073] Optionally, after the binding serverestablishes the binding relationship between the first terminal and the second terminal, the method can further include the following process.The device information of the second terminal can be added to the mapping relationship between the device information of the first terminal and the URL corresponding to the device information of the first terminal, in order to clearly establish the correspondence

relationshipbetween the device information of the terminals having the binding relationship therebetween. The method for adding the device information of the second terminal to the mapping relationship between the device information of the first terminal and the corresponding URL is not limited in the present disclosure. For example, during actual implementation, the binding server can add the device information of the second terminal to the mapping relationship table stored on the binding server.

[0074] In Step 507, the binding server establishes the binding relationship between the first terminal and the second terminal, and sends a binding-success message to the first terminal and the second terminal. The binding-success message can carry the device information of the terminal(s) that is bound.

[0075] Afterthe binding relationship between the first terminal and the second terminal is established, the binding server can send the binding-success message to the first terminal and the second terminal, respectively, in order to confirm with the first terminal and the second terminal that the first terminal and the second terminal are bound with each other. The binding-success message can carry the device information of the terminal that is bound, such that a terminal that is bound with another terminal can be notified of the device information of the another terminal.

[0076] For example, the binding-success message sent by the binding server to the first terminal can carry the device information of the second terminal. The binding-success message sent by the binding server to the second terminal can carry the device information of the first terminal. That is, the binding-success message sent by the binding server to one terminal can carry the device information of other terminal(s) that are bound with the one terminal.

[0077] Optionally, after the first terminal and a second terminalreceive the binding- success message sent by the binding server, the provided method can further include the following process. According to the device information of the first terminal carried in the binding-success message, the second terminal can display the binding relationship. According to the device information of the second terminal carried in the binding-success message, the first terminal can display the binding relationship. The method for the second terminal to display the binding relationship according to the device information of the first terminal carried in the binding-success message is not limited in the present disclosure. For example, FIG. 7 depicts displaying of a binding relationship in accordance with various disclosed embodiments. The binding relationship can be displayed as shown in FIG. 7. Similarly, the method for the first terminal to display the binding relationship according to the device information of the second terminal carried in the binding-success message is not limited in the present disclosure. For example, the binding relationship can be displayed as shown in FIG. 7.

[0078] The displayed binding relationship can include part or all of the device information of oneor more terminals, and a notification indicating that the one or more terminals have a binding relationship with the terminal currently displaying the user interface. In the example shown in FIG. 7, the binding relationship is displayed on a current terminal. The displayed binding relationshipcan include part or all of the device information of a terminal, e.g., 'lisa-iphone'. Thedisplayed binding relationship canfurther include 'bound', which means theterminal (i.e., lisa-iphone) has a binding relationship with the current terminal that is displaying the user interface. [0079] In addition, the user interface can further display options for the user of the current terminal. One option as shown in FIG. 7 is 'bind with another device'. When the user selects this option, the user can use the terminal to scan the 2D code displayed on another device, to proceed with various appropriate steps to be bound with another terminal. Another options as shown in FIG. 7 is 'generate 2D code'. When the user selects this option, the user can send device information of the terminal to the binding server, receive 2D code data generating by the binding server that contains a URL corresponding to the device information, to proceed with various appropriate steps to be bound with another terminal.

[0080] Although, in the processes described above according to various embodiments, the second terminal establishes a binding relationship with the first terminal by scanning the 2D code data corresponding to the first terminal, during actual implementation, the first terminal can establish a binding relationship with the second terminal by scanning the 2D code data corresponding to the second terminal. Any one terminal can establish a binding relationship with a certain terminal by scanning the 2D code data corresponding to the certain terminal. Similarly, any one terminal can establish a binding relationship with another terminal or other terminals by scanning the 2D code data corresponding to another terminal or other terminals, using the method as depicted in accordance with various embodiments.

[0081] In the methods according to various embodiments, a URL corresponding to device information of a first terminal can be generated by a binding server. 2D code data containing the URL can be generated and sent to the first terminal. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[0082] Various embodiments provide a binding server. The binding server can be used for executing the functions of the binding server as disclosed above in various embodiments, e.g., as shown in FIGS. 2-7. FIG. 8 depicts a structure diagram of an exemplary binding server in accordance with various disclosed embodiments. As shown in FIG. 8, the binding server can include an obtaining module 801, a first generating module 802, a second generating module 803, a first sending module 804, a receiving module 805, a determining module 806, a first establishing module 807, and/or a second sending module 808. Certain modules may be omitted and other modules may be included.

[0083] The obtaining module 801 is configured to obtain device information of a first terminal.The first generating module 802 is configured to generate a URL corresponding to the device information of the first terminal.

[0084] The second generating module 803 is configured to generate 2D code data that contain the URL.The first sending module 804 is configured to send the 2D code data to the first terminal.

[0085] The receiving module 805 is configured to receive a connection request sent by a second terminal, the connection request carrying device information of the second terminal and a URL.The determining module 806 is configured to determine whether the URL carried in the connection request matches the generated URL.

[0086] The first establishing module 807 is configured to, when the URL carried in the connection request matches the generated URL, establish a binding relationship between the first terminal and the second terminal.The second sending module 808 is configured to send a binding-success message to the first terminal and the second terminal. The binding-success message can carry the device information of the bound terminal(s).

[0087] Optionally, the binding server can further include a second establishing module and/or a storing module.

[0088] The second establishing module is configured to establish a mapping relationship between the generated URL and the device information of the first terminal. The storing module is configured to storethe mapping relationship between the generated URL and the device information of the first terminal that is established by the second establishing module.

[0089] The determining module 806 can be further configured to look up and find, in the mapping relationshipstored by the storing module, the URL carried in the connection request. That is, the binding server can search the stored mapping relationship for the URL carried in the connection request.When the URL carried in the connection request is found, the determining module 806 can determine that the URL carried in the connection request matches the generated URL.

[0090] Optionally, the binding server can further include an adding module. Theadding module is configured to add the device information of the second terminal to the mapping relationship between the generated URL and the device information of the first terminal.

[0091 ] Using the binding server according to various embodiments, a URL

corresponding to device information of a first terminal can be generated. 2D code data containing the URL can be generated and sent to the first terminal. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[0092] Various embodiments provide a terminal. The terminal can be used for executing the functions of the first terminal as disclosed above in various embodiments, e.g., as shown in FIGS. 2-7. FIG. 9 depicts a structure diagram of an exemplary terminal in accordance with various disclosed embodiments. The terminal can include an uploading module 901, a first receiving module 902, and/or a second receiving module 903. Certain modules may be omitted and other modules may be included.

[0093] The uploading module 901 is configured to upload device information to a binding server. The first receiving module 902 is configured to, after the binding server generates a URL corresponding to the device information of the first terminal, receive 2D code data containing the URL that is returned by the binding server.

[0094] The second receiving module 903 is configured to, after a second terminal scans the 2D code data and uploads to the binding server the URL contained in the 2D code data and device information of the second terminal, receive a binding-success message returned by the binding server that indicates successful binding with the second terminal. The binding-success message can carry the device information of the second terminal.

[0095] Optionally, the terminal can further include a first displaying module configured to display the received 2D code data.

[0096] Optionally, the terminal can further include a second displaying module configured to displaya binding relationship, according to the device information of the second terminal carried in the binding-success message. [0097] Using the terminal according to various embodiments, after device information of the first terminal is uploaded to a binding server, 2D code data that is sent by the binding server and contains a URL corresponding to the device information of the first terminal can be received. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[0098] Various embodiments provide a terminal. The terminal can be used for executing the functions of the second terminal as disclosed above in various embodiments, e.g., as shown in FIGS. 2-7. FIG. 10 depicts a structure diagram of another exemplary terminal in accordance with various disclosed embodiments. The terminal can include a scanning module 1001, a sending module 1002, and/or a receiving module 1003. Certain modules may be omitted and other modules may be included.

[0099] The scanning module 1001 is configured to scan 2D code data corresponding to a first terminal, to obtain a URL contained in the 2D code data. The 2D code data can be 2D code data that contains a URL and is generated by a binding server after the binding server generates the URL corresponding to device information of the first terminal.

[00100] The sending module 1002 is configured to send a connection request to the binding server, the connection request carrying the URL and the device information of the second terminal. [00101] The receiving module 1003 is configured to receive a binding-success message returned by the binding server. The binding-success message can carry the device information of the first terminal.

[00102] Optionally, the terminal can further include a displaying module configured to display a binding relationshipaccording to the device information of the first terminal carried in the binding-success message.

[00103] Using the terminal according to various embodiments, a second terminal can achieve the binding with a first terminal, by scanning 2D code data that is generated by a binding server and contains a URL corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00104] FIG. 11 depicts a structure diagram of an exemplary system for binding multiple terminals in accordance with various disclosed embodiments. Referring to FIG. 11 , the system for binding multiple terminals can include a first terminal 1101, a binding server 1102, and/or a second terminal 1103.

[00105] Thebinding server 1102 can include the binding server provided above in various embodiments, e.g., as shown in FIG. 8. The first terminal 1101 can include the terminal provided above in various embodiments, e.g., as shown in FIG. 9. The second terminal 1103 can include the terminal provided above in various embodiments, e.g., as shown in FIG. 10.

[00106] Using the system for binding multiple terminals according to various

embodiments, a binding server can generate a URL corresponding to device information of a first terminal, generate 2D code data containing the URL, and send the 2D code data to the first terminal. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00107] FIG. 12 depicts a structure diagram of another exemplary terminal in accordance with various disclosed embodiments. Theexemplary terminal 1200 as shown in FIG. 12 can be used for implementing the method for binding multiple terminals as described above in accordance with various disclosed embodiments. In various embodiments, the exemplary terminal 1200 can be used as a first terminal, for implementing the method for binding multiple terminals.

[00108] As shown in FIG. 12, the exemplary terminal 1200 can include an RF (Radio Frequency) circuit 110, a storage device 120 including one or more computer-readable storage media, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a WiFi (Wireless Fidelity) module 170, a processor 180 including one or more processing cores, a power supply 190, and/or other components. In various embodiments, the terminal(s) described herein can include more or less components as depicted in FIG. 12. Certain components/parts can be omitted, combined, rearranged, replaced, and/or added.

[00109] The RF circuit 110 can be used for sending/receiving signal during

sending/receiving information or communication. In particular, after downlink information is received from a base station, such downlink information can be processed by the one or more processors 180. Further, the data related to the uplink can be sent to the base station. Generally, the RF circuit 110 can include, but be not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a subscriberidentity module (SIM) card, a transceiver, a coupler, LNA (Low Noise Amplifier), a duplexer, etc. In addition, the RF circuit 110 can communicate with other devices via a wireless communication network. The wireless communication can use any communication standards or protocols, including but not limited to, GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access), WCDMA (Wideband encode Division Multiple Access), LTE (Long Term Evolution), e-mail, SMS (Short Messaging Service), and/or the like.

[00110] The storage device 120 can be used for storing software programs and modules. By running software programs and modules stored in the storage device 120, the processor 180 can perform various functional applications and data processing. The storage device 120 can include a program storage area and a data storage area. The program storage area can store the operating system, applications (such as sound playback, image playback, etc.) required by at least one function. The data storage area can store data (e.g., audio data, phone book, etc.) created when using the terminal. In addition, the storage device 120 can include a high-speed random access memory and/or a non-volatile memory. For example, the storage device 120 can include at least one magnetic disk memory device, flash memory device, and/or other volatile solid-state memory elements. Accordingly, the storage device 120 can further include a memory controller to provide the processor 180 and the input unit 130 with access to the storage device 120.

[0011 1] The input unit 130 can be used to receive inputted numeric or character information, and to generate signal input related to the user settings and function controls, the signal input including, e.g., keyboard, mouse, joystick, optical an/or trackball signal input.

Specifically, the input unit 130 can include a touch-sensitive surface 131 and other input device(s) 132. The touch-sensitive surface 131 , also known as a touch screen or touch control panel, can collect touch operations that a user conducts on or near the touch-sensitive surface 131. For example, a user can use a finger, a stylus, and any other suitable object or attachment on the touch-sensitive surface 131 or on an area near the touch-sensitive surface 131. The touch- sensitive surface 131 can drive a connecting device based on a preset program. Optionally, the touch-sensitive surface 131 can include a touch detection device and a touch controller. The touch detection device can detect user's touch position, detect a signal due to a touch operation, and send the signal to the touch controller. The touch controller can receive touch information from the touch detection device, convert the touch information into contact coordinates to send to the processor 180, and receive commands sent from the processor 180 to execute.

Furthermore, the touch-sensitive surface 131 can be realized by resistive, capacitive, infrared surface acoustic wave, and/or other types of surface touch. In addition to the touch-sensitive surface 131, the input unit 130 can also include other input device(s) 132. Specifically, the other input device(s) 132 can include, but be not limited to, a physical keyboard, function keys (e.g., as volume control buttons, switch buttons, and the like), a trackball, a mouse, an operating lever, or a combination thereof.

[00112] The display unit 140 can be used to display information inputted by the user, information provided to the user, and a variety of graphical user interfaces of the terminal 1200. These graphical user interfaces can be formed by images, text, icons, videos, and/or any combinations thereof. The display unit 140 can include a display panel 141 configured by, e.g., LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), etc. Further, the touch- sensitive surface 131 can cover the display panel 141. When the touch-sensitive surface 131 detects a touch operation on or near the touch sensitive surface, the touch operation can be sent to the processor 180 to determine the type of the touch operation. According to the type of the touch operation, the processor 180 can provide visual output on the display panel 141. Although in FIG. 12 the touch-sensitive surface 131 and the display panel 141 are shown as two separate components to achieve input and output functions, in certain embodiments, the touch-sensitive surface 131 and the display panel 141 can be integrated to perform input and output functions.

[00113] The terminal 1200 in FIG. 12 can further include at least one sensor 150, such as optical sensors, motion sensors, and other suitable sensors. Specifically, the optical sensors can include an ambient optical sensor and a proximity sensor. The ambient optical sensor can adjust brightness of the display panel 141 according to the brightness of ambient light. The proximity sensor can turn off the display panel 141 and/or backlighting, when the terminal 1200 moves to an ear. As a type of motion sensor, a gravity sensor can detect amount of an acceleration in each direction (e.g., including three axis) and detect magnitude and direction of gravity when stationary. The gravity sensor can be used to identify phone posture (for example, switching between horizontal and vertical screens, related games, magnetometer posture calibration, etc.), and/or vibration recognition related functions (e.g., pedometer, percussion, etc.). The terminal 1200 can also be configured with, e.g., a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and/or other sensors.

[00114] The audio circuit 160 can include an audio output device 161 such as a speakerand an audio input device 162 such as a microphone, and can provide an audio interface between the user and terminal 1200. The audio circuit 160 can transmit an electrical signal converted from the received audio data to the speaker 161 to convert into audio signal output. On the other hand, the microphone 162 can convert the collected sound signal to an electrical signal, which can be received by the audio circuit 160 to convert into audio data. The audio data can be outputted to the processor 180 for processing and then use the RF circuit 110 to transmit to, e.g., another terminal. Alternatively, the audio data can be outputted to the storage device 120 for further processing. The audio circuit 160 can also include an earplug jack to provide communications between the peripheral headset and the terminal 1200.

[00115] WiFi is a short-range wireless transmission technology. The terminal 1200 can use the WiFi module 170 to help users send/receive emails, browse websites, access streaming media, etc. The WiFi module 170 can provide users with a wireless or wired broadband Internet access. In various embodiments, the WiFi module 170 can be configured within or outside of the terminal 1200 as depicted in FIG. 12. Further, although the WiFi module 170 is shown in FIG. 12, the WiFi module 170 is not an essential component of the terminal 1200. The various methods, servers and terminals according to various embodiments can be implemented when the WiFi module is omitted.

[00116] The processor 180 can be a control center of the mobile terminal 1200. By using a variety of interfaces and circuits to connect various parts, e.g., within a terminal such as a mobile phone,the processor 180 can run or execute software programs and/or modules stored in the storage device 120, call the stored data in the storage device 120, and/or perform various functions and data processing of the terminal 1200, in order to monitor the overall terminal.

Optionally, the processor 180 can include one or more processing cores. In one embodiment, the processor 180 can integrate application processor with a modulation and demodulation processor. The application processor is mainly used to process operating system, user interface, and application programs. The modulation and demodulation processor is mainly used to process wireless communications. In various embodiments, the modulation and demodulation processor may or may not be integrated into the processor 180. [00117] The terminal 1200 can further include a power supply 190 (such as a battery) to power various components of the terminal. In one embodiment, the power supply can be connected to the processor 180 via the power management system, and thus use the power management system to manage charging, discharging, and/or power management functions. The power supply 190 can also include one or more DC or AC power supplies, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and/or any other suitable components.

[00118] Although not shown in FIG. 12, the terminal 1200 can further include a camera, a Bluetooth module, a scanner, etc. without limitations.

[00119] In one embodiment, the display unit 140 of the terminal 1200 can include a touch screen. The terminal 1200 can include the storage device 120, and one or more programs stored on the storage device 120. The one or more programs can be configured in order to be executed by the processor(s) 180. The one or more programscan contain coded instruction used for executing the following operations. Device information can be uploaded to a binding server. After the binding server generates a URL corresponding to the device information of the first terminal, 2D code data containing the URL that is returned by the binding server can be received. After a second terminal scans the 2D code data and uploads to the binding server the URL contained in the 2D code data and device information of the second terminal, a binding-success message returned by the binding server, which indicates successful binding with the second terminal, can be received. The binding-success message can carry the device information of the second terminal.

[00120] Optionally, the storage device 120 on the terminal 1200 can include coded instruction used for executing the following operations. After the 2D code data containing the URL that is returned by the binding server after the binding server generates the URL corresponding to the device information of the first terminal, the received 2D code data can be displayed.

[00121] Optionally, the storage device 120 on the terminal 1200 can include coded instruction used for executing the following operations. After the binding-success message returned by the binding server is received, a binding relationship can be displayed, according to the device information of the second terminal carried in the binding-success message.

[00122] Using the terminal according to various embodiments, after device information of the first terminal is uploaded to a binding server, 2D code data that is sent by the binding server and contains a URL corresponding to the device information of the first terminal can be received. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00123] Various embodiments also provide a (non-transitory) computer-readable storage medium. The computer-readable storage medium can include acomputer-readable storage medium contained in the storage device as described above in various embodiments, e.g., as shown in FIG. 12. Alternatively, the computer-readable storage medium can include a computer-readable storage medium that is standalone and is not assembled into the computer system of a terminal. The computer-readable storage medium can store one or more programs. The one or more programs can be executed by one or more processors to execute the method for binding multiple terminals. The method can include the following exemplary process. The exemplary process can be implemented on a first terminal, which is to be bound with a second terminal. Device information can be uploaded to a binding server. After the binding server generates a URL corresponding to the device information of the first terminal, 2D code data containing the URL that is returned by the binding server can be received. After a second terminal scans the 2D code data and uploads to the binding server the URL contained in the 2D code data and device information of the second terminal, a binding-success message returned by the binding server, which indicates successful binding with the second terminal, can be received. The binding-success message can carry the device information of the second terminal.

[00124] Optionally, the computer-readable storage medium can include coded instruction used for executing the following operations. After the 2D code data containing the URL that is returned by the binding server after the binding server generates the URL corresponding to the device information of the first terminal, the received 2D code data can be displayed.

[00125] Optionally, the computer-readable storage medium can include coded instruction used for executing the following operations. After the binding-success message returned by the binding server is received, a binding relationship can be displayed, according to the device information of the second terminal carried in the binding-success message.

[00126] Using the computer-readable storage medium according to various embodiments, after device information of the first terminal is uploaded to a binding server, 2D code data that is sent by the binding server and contains a URL corresponding to the device information of the first terminal can be received. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00127] Various embodimentsprovide a graphical user interface. The graphical user interface can be implemented on a terminal. The terminal can include a first terminal, which is to be bound with a second terminal. Device information can be uploaded to a binding server. The terminal can include a touch screen display, a memory (i.e., storage device), and one or more processors for executing one or more programs. The graphical user interface can include the following process. In other words, the graphical user interface can include any appropriate graphical elements such that a user can interact with the terminal to implement the following process.

[00128] Device information of a first terminal can be uploaded to a binding server. After the binding server generates a URL corresponding to the device information of the first terminal, 2D code data containing the URL that is returned by the binding server can be received. After a second terminal scans the 2D code data and uploads to the binding server the URL contained in the 2D code data and device information of the second terminal, a binding-success message returned by the binding server, which indicates successful binding with the second terminal, can be received. The binding-success message can carry the device information of the second terminal.

[00129] Using the graphical user interface according to various embodiments, after device information of the first terminal is uploaded to a binding server, 2D code data that is sent by the binding server and contains a URL corresponding to the device information of the first terminal can be received. Thus, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00130] FIG. 13 depicts a structure diagram of another exemplary terminal in accordance with various disclosed embodiments. The exemplary terminal 1300 as shown in FIG. 13 can be used for implementing the method for binding multiple terminals as described above in accordance with various disclosed embodiments. In various embodiments, the exemplary terminal 1300 can be used as a second terminal, for implementing the method for binding multiple terminals.

[00131] As shown in FIG. 13, the exemplary terminal 1300 can include an RF (Radio Frequency) circuit 110, a storage device 120 including one or more computer-readable storage media, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a WiFi (Wireless Fidelity) module 170, a processor 180 including one or more processing cores, a power supply 190, and/or other components. In various embodiments, the terminal(s) described herein can include more or less components as depicted in FIG. 13. Certain components/parts can be omitted, combined, rearranged, replaced, and/or added. The components of the terminal 1300 can be similar to or the same as the components of the terminal 1200 as described in various disclosed embodiments, e.g., as shown in FIG. 12.

[00132] In one embodiment, the display unit 140 of the terminal 1300 can include a touch screen. The terminal 1300 can include the storage device 120, and one or more programs stored on the storage device 120. The one or more programs can beexecuted by the processor(s) 180by appropriately configuring the terminal 1300. The one or more programs can contain coded instructions used for executing the following operations. 2D code data corresponding to a first terminal can be scanned, to obtain a URL contained in the 2D code data. The 2D code data can be 2D code data that contains a URL and is generated by a binding server after the binding server generates the URL corresponding to device information of the first terminal. A connection request can be sent to the binding server, the connection request carrying the URL and the device information of the second terminal. A binding-success message returned by the binding server can be received. The binding-success message can carry the device information of the first terminal.

[00133] Optionally, the storage device 120 on the terminal 1300 can include coded instructions used for executing the following operations. After the binding-success message returned by the binding server is received, a binding relationship can be displayed according to the device information of the first terminal carried in the binding-success message.

[00134] Using the terminal according to various embodiments, a second terminal can achieve the binding with a first terminal, by scanning 2D code data that is generated by a binding server and contains a URL corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00135] Various embodiments also provide a (non-transitory) computer-readable storage medium. The computer-readable storage medium can include a computer-readable storage medium contained in the storage device as described above in various embodiments, e.g., as shown in FIG. 13. Alternatively, the computer-readable storage medium can include a computer-readable storage medium that is standalone and is not assembled into the computer system of a terminal. The computer-readable storage medium can store one or more programs. The one or more programs can be executed by one or more processors to execute the method for binding multiple terminals. The method can include the following exemplary process. The exemplary process can be implemented on a second terminal, which is to be bound with a first terminal. Device information can be uploaded to a binding server. 2D code data corresponding to a first terminal can be scanned, to obtain a URL contained in the 2D code data. The 2D code data can be 2D code data that contains a URL and is generated by a binding server after the binding server generates the URL corresponding to device information of the first terminal. A connection request can be sent to the binding server, the connection request carrying the URL and the device information of the second terminal. A binding-success message returned by the binding server can be received. The binding-success message can carry the device information of the first terminal.

[00136] Optionally, the computer-readable storage medium can include coded instructions used for executing the following operations. After the binding-success message returned by the binding server is received, a binding relationship can be displayed according to the device information of the first terminal carried in the binding-success message.

[00137] Using the computer-readable storage medium according to various embodiments, a second terminal can achieve the binding with a first terminal, by scanning 2D code data that is generated by a binding server and contains a URL corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00138] Various embodiments provide a graphical user interface. The graphical user interface can be implemented on a terminal. The terminal can include a second terminal, which is to be bound with a first terminal. The terminal can include a touch screen display, a memory (i.e., storage device), and one or more processors for executing one or more programs. The graphical user interface can include the following process. In other words, the graphical user interface can include any appropriate graphical elements such that a user can interact with the terminal to implement the following process.

[00139] 2D code data corresponding to a first terminal can be scanned, to obtain a URL contained in the 2D code data. The 2D code data can be 2D code data that contains a URL and is generated by a binding server after the binding server generates the URL corresponding to device information of the first terminal. A connection request can be sent to the binding server, the connection request carrying the URL and the device information of the second terminal. A binding-success message returned by the binding server can be received. The binding-success message can carry the device information of the first terminal.

[00140] Using the graphical user interface according to various embodiments, a second terminal can achieve the binding with a first terminal, by scanning 2D code data that is generated by a binding server and contains a URL corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

[00141] Further, various embodiments provide a binding server. The binding server can be implemented on a computer system. The computer system can be similar to or the same as the computer system as depicted in various embodiments, e.g., as shown in FIGS. 12 or 13. The Certain modules in FIGS. 12 or 13 can be optional and is not essential for achieving the functions of the disclosed binding server. The binding server can include a storage device, and one or more programs stored on the storage device. The one or more programs can be executed by the processor(s) by appropriately configuring the binding server.The one or more programs can contain coded instructions used for executing the operations as disclosed various

embodiments, e.g., as shown in FIG. 2.

[00142] During the implementing of binding multiple terminals, the functional modules of the binding server, the first terminal, and the second terminal are divided merely for illustrative purposes. During actual implementation, according to actual needs, the functions described above can be assigned to different functional modules to be implemented. That is, the internal structure of the binding server, the first terminal, and the second terminal can be divided into functional modules different from the modules as shown various embodiments such as the modules shown in FIGS. 8-10, in order to accomplish partor all of the functionsas described above.

[00143] In certain embodiments, a method for binding multiple terminals is provided. FIG. 14 depicts an exemplary method for binding multiple terminals in accordance with various disclosed embodiments. As shown in FIG. 14, the method can include the following process.

[00144] In Step 1, on a terminal A, a user selects an option for binding devices. The terminal A can send device attribute information to a binding server. The device attribute information can include the name of the device (i.e., terminal A), unique identifier of the device, current state of the terminal, and/or the like. The unique identifier of the device can include a GUID when the device is a personal computer (PC), or an IMEI when the device is a mobile phone.

[00145] In Step 2, the terminal A fills out device attribute fields, to encode device attributedata. The terminal A can then send the device attributedata to the device-binding server (i.e., binding server), using an http request method. [00146] In Step 3, according to the device attributedataof terminal A, the binding server generates a URL. Meanwhile, the binding server can establish a mapping relationship between the URL and the device attribute information of the terminal A, and storethe mapping relationship.

[00147] In Step 4, the binding server can generate 2D code datacorresponding tothe URL, and return the 2D code datato the terminal A.

[00148] In Step 5, the terminal A obtains the 2D code datareturned by the binding server, and displays the 2D code data to the user. FIG. 15 depicts exemplary 2D code data in accordance with various disclosed embodiments. The 2D code data can be as shown in FIG. 15. The 2D code data can be scanned by other terminals in order to be bound with terminal A. Such binding can enable the other terminals to use one or more certain functions of an application program that terminal A uses, such as 'sending webpage' service as shown in FIG. 15. In one example, such binding can enable terminal A to send a webpageto terminal B, andenable terminal B to send a webpageto terminal A, so the user can view the same webpage on both of terminal A and terminal B.

[00149] In Step 6, on a terminal B that supports scanning 2D code, the 2D code dataof the terminal A is scanned to identify the2D code and obtain the URL information contained inthe2D code.

[00150] In Step 7, the terminal B sends a requestcarrying the URL, and device attribute information of the terminal B.

[00151] In Step 8, when the binding server receives the URL from the terminal B, the binding server can obtain the carried device attribute information of the terminal B. The binding server can look up the URLin the stored mapping relationship. That is, the binding server can search the stored mapping relationship for the URL carried in the request.After findingthe URLin the stored mapping relationship, the binding server can add the device attribute information of the terminal B to the mappingrelationship and storethe mappingrelationship. Thus, a binding relationship between the terminal A and the terminal B can be established.

[00152] In Step 9, the binding server sends a binding-success message to the terminal A and the terminal B. FIG. 16 depicts displaying of a binding relationship in accordance with various disclosed embodiments.In this case, when the terminal A and the terminal B have a binding relationship, the terminal A and the terminal B can both use one or more certain functions of an application program, such as 'send webpage' service (e.g., also as shown in FIG. 15).When the user requests to send a webpage, the user interface can show that a terminal 'lisalu_iPhone' is bound with the current terminal displaying the user interface, indicated by a 'bound' button 1601. Text 'bound' can be shown on the 'bound' button 1601. In other examples, the 'bound' button 1601 can include an icon, a text box, or the like, in order to indicate a terminal isbound with the current terminal displaying the user interface. The user can select to send the webpage to the bound terminal 'lisalu_iPhone'.

[00153] As used herein, relational terms such as 'first' and 'second' are merely used for differentiate one element or operation from another element or operation, and do not require or imply that any actual relationship or order as such exist between these elements or operations. In addition, the terms "include", "comprise", "contain", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a series of elements can not only include those elements, but also include other elements not expressly listed, or inherent elements for such a process, method, article, or apparatus. Without further limitation, an element defined by a statement "include one " does not exclude additional identical elements that may be included in the process, method, article, or apparatus that includes the element.

[00154] Part or all of the steps in the methods in accordance with various embodiments can be accomplished using hardware, so using a program/software to instruct related hardware. The program/software can be stored in a (non-transitory) computer-readable storage medium including, e.g., ROM/RAM, magnetic disk, optical disk, etc.

[00155] The embodiments disclosed herein are exemplary only. Other applications, advantages, alternations, modifications, or equivalents to the disclosed embodiments are obvious to those skilled in the art and are intended to be encompassed within the scope of the present disclosure.

INDUSTRIAL APPLICABILITY AND ADVANTAGEOUS EFFECTS

[00156] Without limiting the scope of any claim and/or the specification, examples of industrial applicability and certain advantageous effects of the disclosed embodiments are listed for illustrative purposes. Various alternations, modifications, or equivalents to the technical solutions of the disclosed embodiments can be obvious to those skilled in the art and can be included in this disclosure.

[00157] The disclosedmethods, binding servers, terminals, and systems for binding multiple terminals can be used in a variety of computer applications that need tobind multiple terminals in order to enable the terminals to conveniently use the same application program simultaneously. Suchcomputer applications can include, but be not limited to, browser, online media streaming, media playback, video games, email, voice-over- Internet Protocol (VoIP), instant messaging, operating system, document/data processing, document/data sharing, document/data storage and backup, social network services, and the like. The terminals for binding can include, but be not limited to, a mobile phone, a tablet computer, a personal digital assistant, a personal computer (PC), a car-carried-computer, an internet TV, or any other desired terminal devices.

[00158] Using the methods in accordance with various embodiments, a URL

corresponding to device information of a first terminal can be generated by a binding server. 2D code data containing the URL can be generated and sent to the first terminal. Accordingly, a second terminal can achieve the binding with the first terminal by scanning the 2D code data corresponding to the first terminal, i.e., corresponding to the device information of the first terminal. Thus, a process for binding the second terminal with the first terminal can be accomplished without the need of account information. The operation of binding multiple terminals can be simplified.

Reference Sig

Terminal 101

Terminal 102

Binding server 103

Obtaining module 801

First generating module 802

Second generating module 803

First sending module 804

Receiving module 805

Determining module 806

First establishing module 807

Second sending module 808

Uploading module 901

First receiving module 902

Second receiving module 903

Scanning module 1001

Sending module 1002

Receiving module 1003

First terminal 1101

Binding server 1102

Second terminal 1103

Terminal 1200

RF (radio frequency) circuit 110 Storage device 120

Input unit 130

Display unit 140

Sensor 150

Audio circuit 160

WiFi (Wireless Fidelity) module 170 Processor 180

Power supply 190

Touch-sensitive surface 131 Other input device(s) 132

Display panel 141

Audio output device 161

Audio input device 162

Terminal 1300

Bound button 1601

Claims

WHAT IS CLAIMED IS:

1. A method for binding multiple terminalsimplemented by a binding server, comprising: obtainingdevice information of a first terminal and generating a uniform resource locator

(URL) corresponding to the device information of the first terminal;

generatingtwo-dimensional (2D) code data containing the URL, and sendingthe 2D code data to the first terminal;

receivinga connection request sent by a second terminal, the connection request carrying device information of the second terminal and a URL;

determining whether the URL carried in the connection request matches the generated URL; and

when the URL carried in the connection request matches the generated URL, establishinga binding relationship between the first terminal and the second terminal, and sending a binding-success message to the first terminal and the second terminal, the binding- success message carrying the device information of the first terminal and the second terminal.

2. The method according to claim 1 , wherein, after generating the URL corresponding to the device information of the first terminal, the method further comprises:

establishing and storing a mapping relationship between the generated URL and the device information of the first terminal; and

whereinthe determining of whether the URL carried in the connection request matches the generated URL comprises:

searchingthe stored mapping relationshipfor the URL carried in the connection request; and

when the URL carried in the connection request is found, determining that the URL carried in the connection request matches the generated URL.

3. The method according to claim 2, wherein, after establishing the binding relationship between the first terminal and the second terminal, the method further comprises:

adding the device information of the second terminal to the mapping relationship between the generated URL and the device information of the first terminal.

4. A method for binding multiple terminals, comprising:

uploading device information of a first terminal to a binding server;

after the binding server generates a URL corresponding to the device information of the first terminal and returns 2D code data containing the URL, receiving the 2D code data containing the URL; and

after a second terminal scans the 2D code data and uploads, to the binding server, the URL contained in the 2D code data and device information of the second terminal, receiving a binding-success message returned by the binding server, wherein the binding-success message carries the device information of the second terminal.

5. The method according to claim 4, wherein, after receiving the 2D code data containing the URL, the method further comprises:

displaying the received 2D code data.

6. The method according to claim 4, wherein, after receiving the binding-success message returned by the binding server, the method further comprises: displaying a binding relationship, according to the device information of the second terminal that is carried in the binding-success message.

7. The method according to claim 4, further comprising:

scanning the 2D code data corresponding to the first terminal, to obtain the URL contained in the 2D code data, wherein the 2D code data containing the URL is previously generated by the binding server after the binding server generates the URL corresponding to the device information of the first terminal;

sending a connection request to the binding server, the connection request carrying the URL and device information of the second terminal; and

receiving a binding-success message returned by the binding server, the binding-success message carrying the device information of the first terminal.

8. The method according to claim 7, wherein, after receiving the binding-success message returned by the binding server, the method further comprises:

displaying a binding relationship, according to the device information of the first terminal carried in the binding-success message.

9. A system for binding multiple terminals, comprising:

abinding server comprising:

an obtaining module configured to obtain device information of a first terminal;

a first generating module configured to generate a URL corresponding to the device information of the first terminal; a second generating module configured to generate 2D code data that contain the URL; a first sending module configured to send the 2D code data to the first terminal;

a receiving module configured to receive a connection request sent by a second terminal, the connection request carrying device information of the second terminal and a URL;

a determining module configured to determine whether the URL carried in the connection request matches the generated URL;

a first establishing module configured to, when the URL carried in the connection request matches the generated URL, establish a binding relationship between the first terminal and the second terminal; and

a second sending module configured to send a binding-success message to the first terminal and the second terminal, the binding-success message carrying the device information of the first terminal and the second terminal.

10. The system according to claim 9, further comprising:

a second establishing module configured to establish a mapping relationship between the generated URL and the device information of the first terminal; and

a storing module configured to store the mapping relationship between the generated URL and the device information of the first terminal that is established by the second

establishing module, whereinthe determining module is further configured to:

searchthe mapping relationship stored by the storing module forthe URL carried in the connection request; and

when the URL carried in the connection request is found, determine that the URL carried in the connection request matches the generated URL.

11. The system according to claim 10, further comprising:

an adding module configured to add the device information of the second terminal to the mapping relationship between the generated URL and the device information of the first terminal.

12. The system according to claim 9, further comprising:

a first terminal comprising:

an uploading module configured to upload device information of the first terminal to a binding server;

a first receiving module configured to, after the binding server generates a URL corresponding to the device information of the first terminal, receive 2D code data containing the URL that is returned by the binding server; and

a second receiving module configured to, after a second terminal scans the 2D code data and uploads to the binding server the URL contained in the 2D code data and device information of the second terminal, receive a binding-success message returned by the binding server, the binding-success message carrying the device information of the second terminal.

13. The systemaccording to claim 12, whereinthe first terminal further comprises:

a first displaying module configured to display the received 2D code data.

14. The systemaccording to claim 12, whereinthe first terminal further comprises:

a second displaying module configured to display a binding relationship, according to the device information of the second terminal carried in the binding-success message.

15. The system according to claim 9, further comprising:

a second terminal comprising:

a scanning module configured to scan 2D code data corresponding to a first terminal, to obtain a URL contained in the 2D code data, wherein the 2D code data containing the URL is previously generated by a binding server after the binding server generates the URL

corresponding to device information of the first terminal;

a sending module configured to send a connection request to the binding server, the connection request carrying the URL and the device information of the second terminal; and areceiving module configured to receive a binding-success message returned by the binding server, the binding-success message carrying the device information of the first terminal.

16. The systemaccording to claim 15, whereinthe second terminal further comprises:

a displaying module configured to display a binding relationship, according to the device information of the first terminal carried in the binding-success message.