CN109274726B

CN109274726B - Binding method, migration method, binding device, migration device, computing equipment and storage medium

Info

Publication number: CN109274726B
Application number: CN201811014039.3A
Authority: CN
Inventors: 刘统丽
Original assignee: Alibaba Group Holding Ltd
Current assignee: Advanced New Technologies Co Ltd; Advantageous New Technologies Co Ltd
Priority date: 2018-08-31
Filing date: 2018-08-31
Publication date: 2020-07-07
Anticipated expiration: 2038-08-31
Also published as: CN111835824B; TWI777070B; CN111835824A; TW202011722A; CN109274726A; WO2020042823A1

Abstract

The specification provides a binding method, a migration method, a binding device, a migration device, a computing device and a storage medium, wherein the binding method comprises the following steps: sending a pre-binding request to a service server, wherein the pre-binding request carries equipment parameter information of pre-binding terminal equipment and information of a pre-binding account; receiving a binding token sent by the business server and responding to the pre-binding request, wherein the binding token is generated based on the equipment parameter information and the information of the account; sending a binding request to the service server, wherein the binding request carries the binding token; receiving a code generation key factor which is sent by the service server and responds to the binding request, wherein the code generation key factor is used for generating an operation code bound with the account and the terminal equipment; and sending the code generation key factor to the terminal equipment to generate and display the operation code.

Description

Binding method, migration method, binding device, migration device, computing equipment and storage medium

Technical Field

The present disclosure relates to the field of mobile application technologies, and in particular, to a binding method, a migration method, a binding apparatus, a migration apparatus, a computing device, and a storage medium.

Background

At present, the intelligent equipment is in a variety of layers, payment products are continuously generated and upgraded, and equipment binding and product maintenance lack a standardized flow, so that great inconvenience is brought to daily access work, and user experience is poor.

Disclosure of Invention

In view of this, embodiments of the present specification provide a binding method, a migration method, a binding apparatus, a migration apparatus, a computing device, and a storage medium, so as to solve technical defects in the prior art.

According to a first aspect of embodiments of the present specification, there is provided a binding method applied to a client, the method including:

sending a pre-binding request to a service server, wherein the pre-binding request carries equipment parameter information of pre-binding terminal equipment and information of a pre-binding account;

receiving a binding token sent by the business server and responding to the pre-binding request, wherein the binding token is generated based on the equipment parameter information and the information of the account;

sending a binding request to the service server, wherein the binding request carries the binding token;

receiving a code generation key factor which is sent by the service server and responds to the binding request, wherein the code generation key factor is used for generating an operation code bound with the account and the terminal equipment;

and sending the code generation key factor to the terminal equipment to generate and display the operation code.

According to a second aspect of the embodiments of the present specification, there is provided a binding method applied to a service server, the method including:

receiving a pre-binding request sent by a client, wherein the pre-binding request carries equipment parameter information of pre-binding terminal equipment and information of a pre-binding account;

generating a binding token based on the device parameter information and the account information, and sending the binding token to the client;

receiving a binding request sent by the client, wherein the binding request carries the binding token;

and generating a code generation key factor used for generating an operation code bound with the account and the terminal equipment, and sending the code generation key factor to the client.

According to a third aspect of embodiments herein, there is provided a binding method applied to a network device, the method including:

sending a pre-binding request to a service server, wherein the pre-binding request carries equipment parameter information of the network equipment;

receiving a binding token sent by the service server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information;

generating a first operation code according to the binding token, displaying the first operation code so that a client scans the code and sends a binding request to the service server, wherein the binding request carries the binding token and information of the bound account;

sending a polling request for polling a binding result to the service server, and receiving binding result information sent by the service server and responding to the polling request, wherein when the binding is successful, the binding result information carries a code generation key factor, and the code generation key factor is used for generating a second operation code bound with the account and the network equipment;

receiving a code generation key factor which is sent by the business server and responds to the binding request, wherein the code generation key factor is used for generating a second operation code which is bound with the account and the network equipment;

and generating and displaying the second operation code according to the code generation key factor.

According to a fourth aspect of the embodiments of the present specification, there is provided a binding method applied to a service server, the method including:

receiving a pre-binding request sent by network equipment, wherein the pre-binding request carries equipment parameter information of the network equipment;

generating a binding token based on the device parameter information, and sending the binding token to the network device so that the network device generates and displays a first operation code based on the binding token;

receiving a binding request sent by a client, wherein the binding request carries the binding token and information of a bound account, and the client acquires the binding token by scanning the first operation code displayed by the network equipment;

obtaining the device parameter information based on the binding token, and binding the network device corresponding to the device parameter information and the account corresponding to the account information;

generating a code generation key factor, wherein the code generation key factor is used for generating a second operation code bound with the account and the network equipment;

receiving a first polling request sent by the network equipment and used for polling a binding result, and sending binding result information to the network equipment in response to the first polling request, wherein when the binding is successful, the binding result information carries the code generation key factor to generate and display the second operation code.

According to a fifth aspect of embodiments of the present specification, there is provided a binding method applied to a client, the method including:

acquiring a binding token by scanning a first operation code displayed by network equipment, wherein the binding token is used for identifying identity information of the network equipment;

sending a binding request to a service server, wherein the binding request carries the information of the binding token and the bound account;

and receiving a code generation key factor which is sent by the business server and responds to the binding request, wherein the code generation key factor is used for generating a second operation code for binding the network equipment and the account.

According to a sixth aspect of the embodiments of the present specification, there is provided a binding migration method applied to a network device, the method including:

sending a pre-binding request to a first service server so that the first service server generates a first binding token based on the device parameter information of the network device carried by the pre-binding request;

receiving a second binding token which is sent by the first business server and responds to the pre-binding request, wherein the second binding token is generated by a second business server which is a migration destination server based on the equipment parameter information and the first binding token sent by the first business server;

generating a first operation code according to the second binding token, and displaying the first operation code to enable a client to scan the code to obtain the second binding token so as to send a binding request to a second service server, wherein the binding request carries information of the second binding token and a bound account;

sending a polling request for polling a binding result to the first service server, and receiving binding result information sent by the first service server and responding to the polling request, wherein the binding result information is generated by the second service server based on the polling request forwarded by the first service server, and when the binding is successful, the binding result information carries a code generation key factor which is used for generating a second operation code bound with the account and the network equipment;

According to a seventh aspect of the embodiments of the present specification, there is provided a binding migration method applied to a first service server, the method including:

judging whether a service destination server of the pre-binding request is the first service server, if not, generating a first binding token based on the equipment parameter information, and sending the first binding token and the pre-binding request to a second service server serving as a migration destination server so that the second service server generates a second binding token based on the equipment parameter information and the first binding token;

receiving a second binding token which is sent by the second business server and responds to the pre-binding request, and sending the second binding token to the network equipment;

receiving a polling request which is sent by the network equipment and used for polling a binding result, and sending the polling request to the second service server;

and receiving binding result information which is sent by the second service server and responds to the polling request, and sending the binding result information to the network equipment, wherein when the binding is successful, the binding result information carries a code generation key factor which is used for generating a second operation code bound with the account and the network equipment.

According to an eighth aspect of the embodiments of the present specification, there is provided a binding migration method applied to a second service server, the method including:

receiving a pre-binding request sent by a first service server, wherein the pre-binding request carries equipment parameter information of pre-bound network equipment and a first binding token, and the first binding token is generated by the first service server based on the equipment parameter information;

generating a second binding token based on the device parameter information and the first binding token;

sending the second binding token to the first service server so that the first service server sends the second binding token to the network equipment so that the network equipment generates and displays a first operation code according to the second binding token;

receiving a binding request sent by a client, wherein the binding request comprises the second binding token and information of a pre-bound account, and the client acquires the second binding token by scanning the first operation code displayed by the network equipment;

judging whether the binding request contains the second binding token, if so, binding the account with the network equipment, generating a code generation key factor according to the binding result and sending the code generation key factor to the client;

receiving a first polling request which is sent by the first service server and used for polling a binding result, wherein the first polling request is sent to the first service server by the network equipment;

and inquiring a binding result of the network equipment and the account according to the first polling request, and sending the inquired binding result information to the first service server so that the first service server sends the binding result information to the network equipment, wherein under the condition of successful binding, the binding result information carries the code generation key factor which is used for generating a second operation code bound with the account and the network equipment.

According to a ninth aspect of embodiments herein, there is provided a binding apparatus applied to a client, the apparatus including:

the system comprises a first requester, a first server and a second requester, wherein the first requester is configured to send a pre-binding request to a service server, and the pre-binding request carries equipment parameter information of pre-binding terminal equipment and information of a pre-binding account;

a first receiver configured to receive a binding token sent by the traffic server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information and the information of the account;

a second requester configured to send a binding request to the service server, wherein the binding request carries the binding token;

a second receiver configured to receive a code generation key factor sent by the service server in response to the binding request, wherein the code generation key factor is used for generating an operation code bound with the account and the terminal device;

the first displayer is configured to send the code generation key factor to the terminal equipment so as to generate and display the operation code.

According to a tenth aspect of the embodiments of the present specification, there is provided a binding apparatus applied to a service server, the apparatus including:

the third receiver is configured to receive a pre-binding request sent by a client, wherein the pre-binding request carries device parameter information of pre-binding terminal equipment and information of a pre-binding account;

a first generator configured to generate a binding token based on the device parameter information and the information of the account and to send the binding token to the client;

a fourth receiver, configured to receive a binding request sent by the client, where the binding request carries the binding token;

a second generator configured to generate a code generation key factor used to generate an operation code bound with the account and the terminal device, and to send the code generation key factor to the client.

According to an eleventh aspect of embodiments herein, there is provided a binding apparatus, applied to a network device, the apparatus including:

a third requester configured to send a pre-binding request to a service server, where the pre-binding request carries device parameter information of the network device;

a fourth receiver configured to receive a binding token sent by the traffic server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information;

the second displayer is configured to generate a first operation code according to the binding token, display the first operation code so that a client scans the code and sends a binding request to the service server, wherein the binding request carries the binding token and information of the bound account;

a fourth requester configured to send a polling request for polling a binding result to the service server, and receive binding result information sent by the service server in response to the polling request, where the binding result information carries a code generation key factor used to generate a second operation code bound to the account and the network device when the binding is successful;

a fifth requester configured to send a binding request to the service server, where the binding request carries the binding token;

a fifth receiver configured to receive a code generation key factor sent by the service server in response to the binding request, wherein the code generation key factor is used to generate a second operation code bound with the account and the network device;

a third presenter configured to generate and present the second operation code according to the code generation key factor.

According to a twelfth aspect of the embodiments of the present specification, there is provided a binding apparatus applied to a service server, the apparatus including:

a sixth receiver, configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;

a third generator configured to generate a binding token based on the device parameter information, send the binding token to the network device, and cause the network device to generate and display a first operation code based on the binding token;

a seventh receiver, configured to receive a binding request sent by a client, where the binding request carries the binding token and information of a bound account, and the client obtains the binding token by scanning the first operation code displayed by the network device;

the first binder is configured to obtain the device parameter information based on the binding token, and bind the network device corresponding to the device parameter information and the account corresponding to the account information;

a fourth generator configured to generate a code generation key factor to generate a second opcode that binds to the account and the network device;

an eighth receiver, configured to receive a first polling request sent by the network device for polling a binding result, and send binding result information to the network device in response to the first polling request, where when the binding is successful, the binding result information carries the code generation key factor to generate and display the second operation code.

According to a thirteenth aspect of embodiments herein, there is provided a binding apparatus applied to a client, the apparatus including:

the network equipment comprises a scanner and a server, wherein the scanner is configured to obtain a binding token by scanning a first operation code displayed by network equipment, and the binding token is used for identifying identity information of the network equipment;

a sixth requester configured to send a binding request to a service server, where the binding request carries the binding token and information of the bound account;

a ninth receiver configured to receive a code generation key factor sent by the service server in response to the binding request, wherein the code generation key factor is used to generate a second operation code for binding the network device and the account.

According to a fourteenth aspect of the embodiments of the present specification, there is provided a binding migration apparatus, applied to a network device, the apparatus including:

a seventh requester configured to send a pre-binding request to a first service server, so that the first service server generates a first binding token based on the device parameter information of the network device carried by the pre-binding request;

a tenth receiver configured to receive a second binding token sent by the first traffic server in response to the pre-binding request, wherein the second binding token is generated by a second traffic server serving as a migration destination server based on the device parameter information and the first binding token sent by the first traffic server;

a fifth generator, configured to generate a first operation code according to the second binding token, and display the first operation code so that a client scans a code to obtain the second binding token to send a binding request to a second service server, where the binding request carries information of the second binding token and a bound account;

an eighth requester, configured to send a polling request for polling a binding result to the first service server, and receive binding result information sent by the first service server and responding to the polling request, where the binding result information is generated by the second service server based on the polling request forwarded by the first service server, and when the binding is successful, the binding result information carries a code generation key factor, where the code generation key factor is used to generate a second operation code bound to the account and the network device;

a fourth exposer configured to generate and expose the second operation code according to the code generation key factor.

According to a fifteenth aspect of the embodiments of the present specification, there is provided a binding migration apparatus applied to a first service server, the apparatus including:

an eleventh receiver, configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;

a sixth generator configured to determine whether a service destination server of the pre-binding request is the first service server, if the determination result is no, generate a first binding token based on the device parameter information, and send the first binding token and the pre-binding request to a second service server serving as a migration destination server so that the second service server generates a second binding token based on the device parameter information and the first binding token;

a twelfth receiver configured to receive a second binding token sent by the second traffic server in response to the pre-binding request, and send the second binding token to the network device;

a thirteenth receiver, configured to receive a polling request sent by the network device to poll a binding result, and send the polling request to the second service server;

a fourteenth receiver, configured to receive binding result information sent by the second service server and responding to the polling request, and send the binding result information to the network device, where when the binding is successful, the binding result information carries a key code generating factor, and the key code generating factor is used to generate a second operation code bound to the account and the network device.

According to a sixteenth aspect of the embodiments of the present specification, there is provided a binding migration apparatus applied to a second service server, the apparatus including:

a fifteenth receiver, configured to receive a pre-binding request sent by a first service server, where the pre-binding request carries device parameter information of a pre-bound network device and a first binding token, and the first binding token is generated by the first service server based on the device parameter information;

a seventh generator, configured to generate a second binding token based on the device parameter information and the first binding token, and send the second binding token to the first service server, so that the first service server sends the second binding token to the network device, so that the network device generates and displays a first operation code according to the second binding token;

a sixteenth receiver, configured to receive a binding request sent by a client, where the binding request includes the second binding token and information of a pre-bound account, and the client obtains the second binding token by scanning the first operation code displayed by the network device;

the judger is configured to judge whether the binding request contains the second binding token, if so, the account is bound with the network equipment, and a code generation key factor is generated according to the binding result and is sent to the client;

a seventeenth receiver configured to receive a first polling request sent by the first traffic server to poll a binding result, wherein the first polling request is sent to the first traffic server by the network device;

and the second binder is configured to query a binding result between the network device and the account according to the first polling request, and send the queried binding result information to the first service server so that the first service server sends the binding result information to the network device, wherein the binding result information carries the code generation key factor under the condition of successful binding, and the code generation key factor is used for generating a second operation code bound with the account and the network device.

According to a seventeenth aspect of embodiments of the present specification, there is provided a computing device comprising a memory, a processor and computer instructions stored on the memory and executable on the processor, the processor implementing the steps of the binding method or the binding migration method when executing the instructions.

According to an eighteenth aspect of embodiments herein, there is provided a computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the binding method or the binding migration method.

According to the embodiment of the specification, the device parameter information of the terminal device is bound with the account information of the client, and after the binding is successful, the operation code is generated and displayed on the terminal device according to the code generation key factor generated by the service server of the account, so that the old terminal device can operate the account as a new product, convenience and simplicity are realized, and the user experience is improved; the method provides a convenient and safe binding flow for the increasing binding of intelligent equipment and the new and old replacement of service account products, so that new product application can be compatible with old equipment, the old equipment can use the new product application conveniently, and the service usability and safety in the evolution process of the new and old products are ensured.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

FIG. 1 is a block diagram illustrating a configuration of a computing device 100 according to an embodiment of the present description;

FIG. 2 is a flow diagram illustrating a binding method applied to a client in one embodiment of the present specification;

FIG. 3 is a flow diagram illustrating a binding method applied to a server according to an embodiment of the present specification;

FIG. 4 is a flow diagram illustrating a binding method of an embodiment of the present description;

fig. 5 is a flowchart illustrating a binding method applied to a network device according to an embodiment of the present specification;

FIG. 6 is a flow diagram illustrating a binding method applied to a server in one embodiment of the present specification;

FIG. 7 is a flow diagram illustrating a binding method applied to a client in one embodiment of the present specification;

FIG. 8 is a flow diagram illustrating a binding method according to another embodiment of the present description;

fig. 9 is a flowchart illustrating a binding migration method applied to a network device according to an embodiment of the present specification;

FIG. 10 is a flowchart illustrating a binding migration method applied to a first server according to an embodiment of the present specification;

FIG. 11 is a flowchart illustrating a binding migration method applied to a second server according to an embodiment of the present specification;

FIG. 12 is a flow diagram illustrating a bind migration method of an embodiment of the present specification;

FIG. 13 is a block diagram illustrating a binding apparatus according to one embodiment of the present specification;

FIG. 14 is a block diagram showing a binding apparatus according to another embodiment of the present specification;

FIG. 15 is a block diagram showing a binding apparatus according to still another embodiment of the present specification;

FIG. 16 is a block diagram showing a binding apparatus according to still another embodiment of the present specification;

FIG. 17 is a block diagram showing a binding apparatus according to another embodiment of the present specification;

FIG. 18 is a block diagram illustrating a bind migration apparatus according to one embodiment of the present specification;

FIG. 19 is a block diagram illustrating a bind migration apparatus according to another embodiment of the present specification;

fig. 20 is a block diagram showing a binding apparatus according to still another embodiment of the present specification.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.

Fig. 1 is a block diagram illustrating a configuration of a computing device 100 according to an embodiment of the present specification. The components of the computing device 100 include, but are not limited to, memory 110 and processor 120. The processor 120 is coupled to the memory 110 via a bus 130 and the database 150 is used to store user data.

Computing device 100 also includes access device 140, access device 140 enabling computing device 100 to communicate via one or more networks 160. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. Access device 140 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the other components of the computing device 100 described above and not shown in FIG. 1 may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 1 is for purposes of example only and is not limiting as to the scope of the description. Those skilled in the art may add or replace other components as desired.

Computing device 100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), a mobile phone (e.g., smartphone), a wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 100 may also be a mobile or stationary server.

Wherein the processor 120 may perform the steps of the method shown in fig. 2. Fig. 2 is a schematic flow chart diagram illustrating a binding method according to an embodiment of the present specification, applied to a client, which may be a payment-type application App such as a payroll, wechat, a kyoto wallet, a hundredth wallet, or the like. The method includes steps 202 through 210.

Step 202: and sending a pre-binding request to a service server, wherein the pre-binding request carries the equipment parameter information of the pre-binding terminal equipment and the information of the pre-binding account.

In one implementation, the account is a payment account and the operation code is a payment code or a collection code. The account may also be a bar code for access control or other bar codes for identifying identity information.

In one implementation, the terminal device is a bluetooth device, such as a bluetooth bracelet or a bluetooth watch.

In one implementation manner, before sending a pre-binding request to a service server, where the pre-binding request carries device parameter information of a pre-binding terminal device and information of a pre-binding account, the method further includes: sending an acquisition request for acquiring device parameter information to a terminal device, and receiving the device parameter information sent by the terminal device and responding to the acquisition request. In addition, in specific implementation, the device parameters of the pre-bound terminal device can be manually input at the client.

Step 204: receiving a binding token sent by the business server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information and the information of the account.

Step 206: and sending a binding request to the service server, wherein the binding request carries the binding token.

Step 208: and receiving a code generation key factor which is sent by the service server and responds to the binding request, wherein the code generation key factor is used for generating an operation code bound with the account and the terminal equipment.

Step 210: and sending the code generation key factor to the terminal equipment to generate and display the operation code.

In one implementation, after the sending the code generation key factor to the terminal device to generate and display the payment code or the collection code, the method further includes: receiving first feedback information which is sent by the terminal equipment and used for successfully receiving the code generation key factor; generating second feedback information which completes binding based on the first feedback information, and sending the second feedback information to the service server; and receiving a service notification which is sent by the service server and responds to the second feedback information and is used for notifying that binding is available, and forwarding the service notification to the terminal equipment.

Wherein the processor 120 may perform the steps of the method shown in fig. 3. Fig. 3 is a schematic flow chart diagram illustrating a binding method according to an embodiment of the present specification, applied to a server. The method includes steps 302 through 308.

Step 302: receiving a pre-binding request sent by a client, wherein the pre-binding request carries equipment parameter information of pre-binding terminal equipment and information of a pre-binding account.

Step 304: and generating a binding token based on the equipment parameter information and the account information, and sending the binding token to the client.

Step 306: and receiving a binding request sent by the client, wherein the binding request carries the binding token.

Step 308: and generating a code generation key factor used for generating an operation code bound with the account and the terminal equipment, and sending the code generation key factor to the client.

In one implementation, after generating a code generation key factor for generating an operation code bound with the account and the terminal device, and sending the code generation key factor to the client, the method further includes: receiving second feedback information which is sent by the client and completes binding, wherein the second feedback information is generated based on first feedback information which is sent by the terminal equipment and successfully receives the code generation key factor; and sending a service notification responding to the second feedback information that the service processing is successful to the client.

FIG. 4 is a flow diagram illustrating a binding method of an embodiment of the present description; as shown in fig. 4, the method includes:

1. the client sends a request to the Bluetooth equipment to acquire the equipment parameters of the pre-bound Bluetooth equipment; the bluetooth equipment responds to the request of the client and sends equipment parameter information to the client (corresponding to step 1.1 in fig. 4);

2. the client sends a pre-binding request to a service server according to the received equipment parameter information of the Bluetooth equipment, wherein the pre-binding request carries pre-binding param (parameters): device parameter information of the Bluetooth device and information of the pre-bound account; the service server generates a binding context token (corresponding to step 2.1 in fig. 4) according to the device parameter information of the bluetooth device and the information of the pre-bound account; the service server issues a binding context token to the client (corresponding to step 2.2 in fig. 4); the client sends a binding request to the service server, wherein the binding request carries binding param, and the binding param comprises a binding context token and binding account information (corresponding to step 2.3 in fig. 4); the service server verifies the received binding request, judges whether the binding request carries the binding token, if so, binds the account with the Bluetooth equipment to generate a code generation key factor, which is a key process of product binding (corresponding to step 2.3.1 in fig. 4); the service server returns the code generation key factor to the client (corresponding to step 2.3.2 in fig. 4);

3. the client uploads the received code generation key factor to the Bluetooth equipment; the bluetooth device returns feedback information of successfully receiving the key factor of the code to the client (corresponding to step 3.1 in fig. 4);

4. the client sends feedback information of binding completion of the Bluetooth equipment and the account to a service server; the service server performs service product availability processing according to the feedback information sent by the client (corresponding to step 4.1 in fig. 4), and issues service parameters to the client to inform (bind) that the service processing is successful (corresponding to step 4.2 in fig. 4);

5. the client sends notification information informing that the binding is successful to the Bluetooth device, the Bluetooth device sends feedback information of successful receiving to the client, and an operation code is generated and displayed according to the code generation key factor (corresponding to step 5.1 in fig. 4), so that operations such as payment and access control swiping can be performed.

Wherein the processor 120 may perform the steps of the method shown in fig. 5. Fig. 5 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, and is applied to a network device, which may be a terminal device such as a smart watch, a mobile phone, etc. having a network communication function. The method includes steps 502 through 514.

Step 502: and sending a pre-binding request to a service server, wherein the pre-binding request carries the equipment parameter information of the network equipment.

Step 504: receiving a binding token sent by the traffic server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information.

Step 506: and generating a first operation code according to the binding token, displaying the first operation code so as to enable a client to scan the code and sending a binding request to the service server, wherein the binding request carries the binding token and the information of the bound account.

Step 508: sending a polling request for polling a binding result to the service server, and receiving binding result information sent by the service server and responding to the polling request, wherein when the binding is successful, the binding result information carries a code generation key factor, and the code generation key factor is used for generating a second operation code bound with the account and the network equipment.

Step 510: and sending a binding request to the service server, wherein the binding request carries the binding token.

Step 512: and receiving a code generation key factor which is sent by the business server and responds to the binding request, wherein the code generation key factor is used for generating a second operation code which is bound with the account and the network equipment.

Step 514: and generating and displaying the second operation code according to the code generation key factor.

In one implementation, after the generating and presenting the second operation code according to the code generation critical factor, the method further includes: sending first feedback information of the account bound with the network equipment to the service server; and receiving notification information which is sent by the service server and responds to the first feedback information to notify that binding is available.

Wherein the processor 120 may perform the steps of the method shown in fig. 6. Fig. 6 is a schematic flow chart diagram illustrating a binding method according to an embodiment of the present specification, applied to a service server. The method includes steps 602 through 612.

Step 602: receiving a pre-binding request sent by a network device, wherein the pre-binding request carries device parameter information of the network device.

Step 604: generating a binding token based on the device parameter information, and sending the binding token to the network device to enable the network device to generate and display a first operation code based on the binding token.

Step 606: receiving a binding request sent by a client, wherein the binding request carries information of the binding token and a bound account, and in the first implementation mode displayed by the client through scanning the network device, the account is a payment account, and the operation code is a payment code or a collection code. The account may also be a bar code for access control or other bar codes for identifying identity information.

And the operation code acquires the binding token.

Step 608: and obtaining the equipment parameter information based on the binding token, and binding the network equipment corresponding to the equipment parameter information and the account corresponding to the account information.

Step 610: generating a code generation key factor, the generation key factor being used to generate a second opcode that is bound to the account and the network device.

In one implementation, after the generating the code generation key factor, the method further includes: and sending the code generation key factor to the client.

Step 612: receiving a first polling request sent by the network equipment and used for polling a binding result, and sending binding result information to the network equipment in response to the first polling request, wherein when the binding is successful, the binding result information carries the code generation key factor to generate and display the second operation code.

In one implementation, after the receiving a polling request sent by the network device to poll a binding result, and sending binding result information to the network device in response to the polling request to generate and expose the second opcode, the method further includes: receiving an operation request for the account sent by the network equipment; and executing the operation corresponding to the operation request on the account according to the binding relationship between the account and the network equipment.

In one implementation, after the receiving a polling request sent by the network device to poll a binding result, and sending binding result information to the network device in response to the polling request to generate and expose the second opcode, the method further includes: receiving first feedback information which is sent by the network equipment and used for binding the account and the network equipment; generating notification information for notifying that binding is available in response to the first feedback information, and sending the notification information to the network device.

In one implementation, after sending the transcoding key factor to the client, the method further includes:

receiving a second polling request sent by the client for polling the binding result, and sending the binding result information to the client in response to the second polling request.

Wherein the processor 120 may perform the steps of the method shown in fig. 7. Fig. 7 is a schematic flow chart diagram illustrating a binding method according to an embodiment of the present specification, applied to a client, which may be a payment-type application App such as a payroll, wechat, a kyoto wallet, a hundredth wallet, or the like. The method includes steps 702 through 706.

Step 702: the method comprises the steps of scanning a first operation code displayed by network equipment to obtain a binding token, wherein the binding token is used for identifying identity information of the network equipment.

Step 704: and sending a binding request to a service server, wherein the binding request carries the information of the binding token and the bound account.

Step 706: and receiving a code generation key factor which is sent by the business server and responds to the binding request, wherein the code generation key factor is used for generating a second operation code for binding the network equipment and the account.

In one implementation, after the receiving the key factor for generating code, sent by the service server, in response to the binding request, the method further includes: sending a polling request for polling the binding result of the network equipment and the account to the service server; and receiving binding result notification information which is sent by the service server and responds to the polling request.

FIG. 8 is a flow diagram illustrating a binding method of one embodiment of the present specification; as shown in fig. 8, the method includes:

1. the network equipment sends a pre-binding request to the service server and uploads equipment parameter information param of the network equipment; the service server generates a binding context token (corresponding to step 1.1 in fig. 8) according to the device parameter information of the network device, and returns the binding context token to the network device (corresponding to step 1.2 in fig. 8); the network device generates a binding two-dimensional code according to the received binding context token (corresponding to step 1.3 in fig. 8);

2. the client scans the binding two-dimensional code to obtain a binding context token (corresponding to step 2.1 in fig. 8);

3. a client sends a binding request to a service server, wherein the binding request comprises the binding context token and information of a pre-bound account; the service server verifies the received binding request, judges whether the binding request carries the binding context token, if so, binds the account with the network equipment to generate a code generation key factor, which is a key process of product binding (corresponding to step 3.1 in fig. 8); the service server returns the code generation key factor to the client (corresponding to step 3.2 in fig. 8);

4. after generating the binding two-dimensional code, the network device starts to send a polling request for inquiring whether the binding is successful to the service server, the service server inquires a binding result in response to the polling request (corresponding to step 4.1 in fig. 8), and sends the inquired binding result information to the network device, wherein when the binding is successful, the binding result information carries a code generation key factor (corresponding to step 4.2 in fig. 8), and the code generation key factor is used for generating an operation code bound with the account and the network device; after receiving the key code generation factor, the network device sends feedback information that the binding between the network device and the account is completed to a service server (corresponding to step 4.3 in fig. 8); the service server performs service product availability processing according to the feedback information sent by the network device (corresponding to step 4.3.1 in fig. 8), issues a service parameter to the network device, and informs (binds) that the service processing is successful (corresponding to step 4..3.2 in fig. 8); the network device generates an operation code according to the received code generation key factor and displays the operation code (corresponding to step 4.3.3 in fig. 8), so that business operations such as payment, access control swiping and the like can be performed;

5. the client sends a polling request for inquiring whether the binding is successful to the service server, the service server inquires the binding result in response to the polling request (corresponding to step 5.1 in fig. 8), and sends the inquired binding result information to the client corresponding to step 5.2 in fig. 8).

Wherein the processor 120 may perform the steps of the method shown in fig. 9. Fig. 9 is a schematic flow chart diagram illustrating a binding method according to an embodiment of the present specification, applied to a network device. The method includes steps 902 through 910.

Step 902: sending a pre-binding request to a first service server so that the first service server generates a first binding token based on the device parameter information of the network device carried by the pre-binding request.

Step 904: and receiving a second binding token which is sent by the first business server and responds to the pre-binding request, wherein the second binding token is generated by a second business server which is a migration destination server based on the equipment parameter information and the first binding token sent by the first business server.

Step 906: and generating a first operation code according to the second binding token, and displaying the first operation code to enable a client to scan the code to obtain the second binding token so as to send a binding request to a second service server, wherein the binding request carries the second binding token and the information of the bound account.

Step 908: sending a polling request for polling a binding result to the first service server, and receiving binding result information sent by the first service server and responding to the polling request, wherein the binding result information is generated by the second service server based on the polling request forwarded by the first service server, and when the binding is successful, the binding result information carries a code generation key factor, and the code generation key factor is used for generating a second operation code bound with the account and the network equipment.

Step 910: and generating and displaying the second operation code according to the code generation key factor.

In one implementation, the account is a payment account and the second operation code is a payment code or a collection code.

In one implementation, after the generating and presenting the second operation code according to the code generation critical factor, the method further includes: sending feedback information of the account bound with the network equipment to the first service server; and receiving first notification information which is sent by the first service server and responds to the feedback information to notify that binding is available, wherein the first notification information is generated by the second service server based on the feedback information forwarded by the first service server.

In one implementation, after the generating and presenting the second operation code according to the code generation critical factor, the method further includes: sending a unbinding request to the first business server to unbind the account from the network device; and receiving second notification information which is sent by the first service server and responds to the unbinding request and used for notifying the unbinding, wherein the second notification information is generated by the second service server based on the unbinding request forwarded by the first service server.

Wherein the processor 120 may perform the steps of the method shown in fig. 10. Fig. 10 is a schematic flow chart diagram illustrating a binding method according to an embodiment of the present specification, applied to a first service server. The method includes steps 1002-1010.

Step 1002: receiving a pre-binding request sent by a network device, wherein the pre-binding request carries device parameter information of the network device.

Step 1004: judging whether a service destination server of the pre-binding request is the first service server, if not, generating a first binding token based on the equipment parameter information, and sending the first binding token and the pre-binding request to a second service server serving as a migration destination server so that the second service server generates a second binding token based on the equipment parameter information and the first binding token; .

Step 1006: and receiving a second binding token which is sent by the second service server and responds to the pre-binding request, and sending the second binding token to the network equipment.

Step 1008: and receiving a polling request which is sent by the network equipment and used for polling the binding result, and sending the polling request to the second service server.

Step 1010: and receiving binding result information which is sent by the second service server and responds to the polling request, and sending the binding result information to the network equipment, wherein when the binding is successful, the binding result information carries a code generation key factor which is used for generating a second operation code bound with the account and the network equipment.

In one implementation manner, after the receiving the binding result information sent by the second service server in response to the polling request, and sending the binding result information to the network device, the method further includes: receiving feedback information sent by the network equipment, wherein the account and the network equipment are bound, and sending the feedback information to the second service server; and receiving first notification information which is sent by the second service server and responds to the feedback information and is used for notifying that binding is available, and sending the first notification information to the network equipment.

In one implementation manner, after the receiving the binding result information sent by the second service server in response to the polling request, and sending the binding result information to the network device, the method further includes: receiving a unbinding request which is sent by the network equipment and used for unbinding the account from the network equipment, and sending the unbinding request to the second service server; and receiving second notification information which is sent by the second service server and responds to the unbinding request and is used for notifying the unbinding, and sending the second notification information to the network equipment.

Wherein the processor 120 may perform the steps of the method shown in fig. 11. Fig. 11 is a schematic flow chart diagram illustrating a binding migration method according to an embodiment of the present specification, applied to a second service server. The method includes steps 1102 through 1110.

Step 1102: receiving a pre-binding request sent by a first service server, wherein the pre-binding request carries device parameter information of pre-bound network devices and a first binding token, and the first binding token is generated by the first service server based on the device parameter information.

Step 1104: and generating a second binding token based on the device parameter information and the first binding token, and sending the second binding token to the first business server so that the first business server sends the second binding token to the network device to enable the network device to generate and display a first operation code according to the second binding token.

Step 1106: receiving a binding request sent by a client, wherein the binding request comprises the second binding token and information of a pre-bound account, and the client acquires the second binding token by scanning the first operation code displayed by the network equipment.

Step 1108: and judging whether the binding request contains the second binding token, if so, binding the account and the network equipment, generating a code generation key factor according to the binding result and sending the code generation key factor to the client.

Step 1110: and receiving a first polling request which is sent by the first service server and used for polling a binding result, wherein the first polling request is sent to the first service server by the network equipment.

Step 1112: and inquiring a binding result of the network equipment and the account according to the first polling request, and sending the inquired binding result information to the first service server so that the first service server sends the binding result information to the network equipment, wherein under the condition of successful binding, the binding result information carries the code generation key factor which is used for generating a second operation code bound with the account and the network equipment.

In one implementation manner, after the querying a binding result between the network device and the account according to the first polling request, and the querying the first service server for the binding result information so that the first service server sends the binding result information to the network device, the method further includes: receiving feedback information sent by the first service server, wherein the feedback information is generated by the network equipment, and the account is bound with the network equipment; and generating first notification information for notifying that binding is available according to the feedback information, and sending the first notification information to the first service server so that the first service server sends the first notification information to the network equipment.

In one implementation manner, after the querying a binding result between the network device and the account according to the polling request, and the first service server sending the queried binding result information to the network device, the method further includes: receiving a unbinding request sent by the first service server to unbind the account from the network device, wherein the unbinding request is generated by the network device and sent to the first service server; the account and the network equipment are unbound according to the unbinding request, and second notification information used for notifying the unbinding is generated; and sending the second notification information to the first service server so that the first service server sends the second notification information to the network device.

In one implementation manner, after receiving the binding request sent by the client, the method further includes: receiving a second polling request which is sent by the client and used for polling the binding result; and inquiring a binding result of the network equipment and the account according to the second polling request, and sending inquired binding result information to the client, wherein the binding result information carries the code generation key factor under the condition of successful binding.

FIG. 12 is a flow diagram illustrating a binding method of an embodiment of the present description; as shown in fig. 12, the method includes:

1. the network equipment sends a pre-binding request to the service server A and uploads equipment parameter information param of the network equipment; the service server generates a binding context token (corresponding to step 1.1 in fig. 8) according to the device parameter information of the network device, and sends the binding context token and the device parameter information of the network device to the service server B (corresponding to step 1.2 in fig. 12); the service server B generates a binding context of the specified token according to the received binding context token and the device parameter information (corresponding to step 1.2.1 in fig. 12); the service server B returns the binding context token of the specified token to the service server a (corresponding to step 1.2.2 in fig. 12); the service server a returns the binding context of the specified token to the network device (corresponding to step 1.2.3 in fig. 12);

2. the network equipment forms a binding two-dimensional code according to the received binding context of the specified token;

3. the client scans the binding two-dimensional code to obtain a binding context token (corresponding to step 3.1 in fig. 12);

4. a client sends a binding request to a service server B, wherein the binding request comprises the binding context token and information of a pre-bound account; the service server B verifies the received binding request, judges whether the binding request carries the binding context token, if so, binds the account with the network equipment to generate a key code generating factor, which is a key process of product binding (corresponding to step 4.1 in FIG. 12); the service server B returns the code generation key factor to the client (corresponding to step 4.2 in fig. 8);

5. after the binding two-dimensional code is generated, the network device starts to send a polling request for inquiring whether binding migration is successful or not to the service server a, and the service server a forwards the polling request to the service server B (corresponding to step 5.1 in fig. 12); the service server B queries the binding result in response to the polling request (corresponding to step 5.1.1 in fig. 12), and sends the binding result information obtained by the query to the service server a (corresponding to step 5.1.2 in fig. 12); the service server a forwards the binding result information to the network device, and marks the forwarding flag bit as forwarding (corresponding to step 5.1.4 in fig. 12), wherein, when the binding is successful, the binding result information carries a key code generation factor, and the key code generation factor is used to generate an operation code bound with the account and the network device;

6. after receiving the code generation key factor, the network equipment sends feedback information of binding completion between the network equipment and the account to a service server A; the service server a forwards the flag bit (corresponding to step 6.1 in fig. 12), and forwards the feedback information after binding to the service server B (corresponding to step 6.2 in fig. 12); the service server B performs service product availability processing according to the feedback information (corresponding to step 6.2.1 in fig. 12), issues a service parameter to the service server a, and informs (binds to migrate) that the service processing is successful (corresponding to step 6.2.2 in fig. 12); the service server a issues a notification of successful service processing to the network device (corresponding to step 6.2.3 in fig. 12);

7. the network equipment generates and displays an operation code according to the received code generation key factor, and then business operations such as payment, access control and the like can be carried out;

8. the client sends a polling request for inquiring whether the binding is successful to the service server B, the service server B inquires the binding result in response to the polling request (corresponding to the step 8.1 in the figure 12), and sends the information of the binding result obtained by inquiry to the client (corresponding to the step 8.2 in the figure 12);

9. the network equipment sends a unbinding request for unbinding the account and the network equipment to a service server A; service server a forwards the unbind request to service server B (corresponding to step 9.1 in fig. 12); the service server B unbinds the account from the network device according to the unbinding request, generates notification information for notifying the unbinding, and sends the notification information to the service server a (corresponding to step 9.2 in fig. 12); the service server a forwards the notification information of the unbinding result to the network device (corresponding to step 9.3 in fig. 12).

Corresponding to the foregoing binding method and binding migration method, this specification further provides a binding apparatus and an embodiment of the binding migration apparatus, where the embodiment of the apparatus may be implemented by software, or may be implemented by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. In terms of hardware, a hardware structure of the device in which the binding apparatus and the binding migration apparatus of this specification are located may include a processor, a network interface, a memory, and a nonvolatile memory, and the device in which the apparatus is located in the embodiment may also include other hardware according to an actual function, which is not described herein again.

Referring to fig. 13, a block diagram of a binding apparatus according to an embodiment of the present disclosure is provided. The binding apparatus 1300 corresponds to the embodiment shown in fig. 2, and the apparatus 1300 includes:

a first requester 1302, configured to send a pre-binding request to a service server, where the pre-binding request carries device parameter information of a pre-binding terminal device and information of a pre-binding account;

a first receiver 1304 configured to receive a binding token sent by the traffic server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information and the information of the account;

a second requester 1306, configured to send a binding request to the service server, where the binding request carries the binding token;

a second receiver 1308, configured to receive a code generation key factor sent by the service server in response to the binding request, where the code generation key factor is used to generate an operation code bound with the account and the terminal device;

a first presenter 1310 configured to send the code generation key factor to the terminal device to generate and present the operation code.

In an alternative embodiment, the terminal device is a bluetooth device.

In an alternative embodiment, the account is a payment account and the operation code is a payment code or a collection code.

Referring to fig. 14, a block diagram of a binding apparatus according to an embodiment of the present disclosure is provided. The binding apparatus 1400 corresponds to the embodiment shown in fig. 3, and the apparatus 1400 includes:

a third receiver 1402, configured to receive a pre-binding request sent by a client, where the pre-binding request carries device parameter information of a pre-binding terminal device and information of a pre-binding account;

a first generator 1404 configured to generate a binding token based on the device parameter information and the information of the account, and to send the binding token to the client;

a fourth receiver 1406 configured to receive a binding request sent by the client, where the binding request carries the binding token;

a second generator 1408 configured to generate a code generation key for generating an operation code bound with the account and the terminal device, and transmit the code generation key to the client.

In an alternative embodiment, the terminal device is a bluetooth device.

Referring to fig. 15, a block diagram of a binding apparatus according to an embodiment of the present disclosure is provided. The binding apparatus 1500 corresponds to the embodiment shown in fig. 5, and the apparatus 1500 includes:

a third requester 1502 configured to send a pre-binding request to a service server, where the pre-binding request carries device parameter information of the network device;

a fourth receiver 1504 configured to receive a binding token sent by the traffic server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information;

a second exposer 1506, configured to generate a first operation code according to the binding token, expose the first operation code to enable a client to scan the code and send a binding request to the service server, where the binding request carries information of the binding token and a bound account;

a fourth requester 1508, configured to send a polling request for polling a binding result to the service server, and receive binding result information sent by the service server in response to the polling request, where the binding result information carries a code generation key factor, and the code generation key factor is used to generate a second operation code bound with the account and the network device when the binding is successful;

a fifth requester 1510 configured to send a binding request to the service server, where the binding request carries the binding token;

a fifth receiver 1512 configured to receive a code generation key factor sent by the service server in response to the binding request, wherein the code generation key factor is used to generate a second operation code bound to the account and the network device;

a third presenter 1514 configured to generate and present the second operation code in accordance with the code generation key factor.

In an alternative embodiment, the account is a payment account and the second operation code is a payment code or a collection code.

Referring to fig. 16, a block diagram of a binding apparatus according to an embodiment of the present disclosure is provided. The binding apparatus 1600 corresponds to the embodiment shown in fig. 6, and the apparatus 1600 includes:

a sixth receiver 1602, configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;

a third generator 1604 configured to generate a binding token based on the device parameter information, send the binding token to the network device, and cause the network device to generate and display a first operation code based on the binding token;

a seventh receiver 1606, configured to receive a binding request sent by a client, where the binding request carries the binding token and information of a bound account, and the client obtains the binding token by scanning the first operation code displayed by the network device;

a first binder 1608 configured to obtain the device parameter information based on the binding token, and bind the network device corresponding to the device parameter information and the account corresponding to the information of the account;

a fourth generator 1610 configured to generate a generation key factor for generating a second opcode bound to the account and the network device;

an eighth receiver 1612, configured to receive a first polling request sent by the network device for polling a binding result, and send binding result information to the network device in response to the first polling request, where when the binding is successful, the binding result information carries the code generation key factor to generate and display the second operation code.

Referring to fig. 17, a block diagram of a binding apparatus according to an embodiment of the present disclosure is provided. The binding apparatus 1700 corresponds to the embodiment shown in fig. 7, and the apparatus 1700 includes:

a scanner 1702 configured to obtain a binding token by scanning a first operation code displayed by a network device, where the binding token is used to identify identity information of the network device;

a sixth requester 1704, configured to send a binding request to a service server, where the binding request carries the binding token and information of the bound account;

a ninth receiver 1706, configured to receive a code generation key factor sent by the service server in response to the binding request, wherein the code generation key factor is used to generate a second operation code for binding the network device and the account.

Referring to fig. 18, a block diagram of a binding migration apparatus according to an embodiment of the present disclosure is provided. The binding migration apparatus 1800 corresponds to the embodiment shown in fig. 9, and the apparatus 1800 includes:

a seventh requester 1802, configured to send a pre-binding request to a first service server, so that the first service server generates a first binding token based on device parameter information of the network device carried in the pre-binding request;

a tenth receiver 1804 configured to receive a second binding token sent by the first traffic server in response to the pre-binding request, wherein the second binding token is generated by a second traffic server acting as a migration destination server based on the device parameter information and the first binding token sent by the first traffic server;

a fifth generator 1806, configured to generate a first operation code according to the second binding token, and display the first operation code so that a client scans a code to obtain the second binding token to send a binding request to a second service server, where the binding request carries information of the second binding token and a bound account;

an eighth requester 1808, configured to send a polling request for polling a binding result to the first service server, and receive binding result information sent by the first service server and responding to the polling request, where the binding result information is generated by the second service server based on the polling request forwarded by the first service server, and when the binding is successful, the binding result information carries a code generation key factor, where the code generation key factor is used to generate a second operation code bound to the account and the network device;

a fourth exposer 1810 configured to generate and expose the second operation code according to the code generation key factor.

Referring to fig. 19, a block diagram of a binding migration apparatus according to an embodiment of the present disclosure is provided. The binding migration apparatus 1900 corresponds to the embodiment shown in fig. 10, and is applied to a first service server, where the apparatus 1900 includes:

an eleventh receiver 1902, configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;

a sixth generator 1904 configured to determine whether a service destination server of the pre-bind request is the first service server, if the determination result is otherwise, generate a first bind token based on the device parameter information, and send the first bind token and the pre-bind request to a second service server serving as a migration destination server to enable the second service server to generate a second bind token based on the device parameter information and the first bind token;

a twelfth receiver 1906 configured to receive a second binding token sent by the second traffic server in response to the pre-binding request, and send the second binding token to the network device;

a thirteenth receiver 1908, configured to receive a polling request sent by the network device to poll a binding result, and send the polling request to the second service server;

a fourteenth receiver 1910 configured to receive binding result information sent by the second service server and responding to the polling request, and send the binding result information to the network device, where when the binding is successful, the binding result information carries a key code generation factor, and the key code generation factor is used to generate a second operation code bound to the account and the network device.

Referring to fig. 20, a block diagram of a binding migration apparatus according to an embodiment of the present disclosure is provided. The binding migration apparatus 2000 corresponds to the embodiment shown in fig. 11, and is applied to the second service server, where the apparatus 2000 includes:

a fifteenth receiver 2002 configured to receive a pre-binding request sent by a first service server, where the pre-binding request carries device parameter information of a pre-bound network device and a first binding token, and the first binding token is generated by the first service server based on the device parameter information;

a seventh generator 2004 configured to generate a second binding token based on the device parameter information and the first binding token, send the second binding token to the first traffic server to cause the first traffic server to send the second binding token to the network device to cause the network device to generate and display a first operation code according to the second binding token;

a sixteenth receiver 2006 configured to receive a binding request sent by a client, where the binding request includes the second binding token and information of a pre-bound account, and the client obtains the second binding token by scanning the first operation code displayed by the network device;

a determiner 2008 configured to determine whether the binding request includes the second binding token, if so, bind the account with the network device, generate a code generation key factor according to the binding result, and send the code generation key factor to the client;

a seventeenth receiver 2010 configured to receive a first polling request sent by the first traffic server to poll a binding result, wherein the first polling request is sent by the network device to the first traffic server;

a second binder 2012 configured to query a binding result between the network device and the account according to the first polling request, and send the queried binding result information to the first service server so that the first service server sends the binding result information to the network device, where, in case of successful binding, the binding result information carries the code generation key factor, and the code generation key factor is used to generate a second operation code bound with the account and the network device.

The apparatuses, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.

An embodiment of the present specification further provides a computing device, which includes a memory, a processor, and computer instructions stored in the memory and executable on the processor, wherein the processor implements the steps of the binding method and the binding migration method when executing the instructions.

An embodiment of the present specification further provides a computer readable storage medium, which stores computer instructions, and when the instructions are executed by a processor, the computer instructions implement the binding method and the steps of the binding migration method.

The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the above-mentioned method, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the above-mentioned method.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present disclosure is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present disclosure. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for this description.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the specification and its practical application, to thereby enable others skilled in the art to best understand the specification and its practical application. The specification is limited only by the claims and their full scope and equivalents.

Claims

1. A binding method is applied to a client, and comprises the following steps:

sending an acquisition request for acquiring equipment parameter information to a terminal device, and receiving the equipment parameter information which is sent by the terminal device and responds to the acquisition request;

sending the code generation key factor to the terminal equipment to generate and display the operation code;

receiving first feedback information which is sent by the terminal equipment and used for successfully receiving the code generation key factor;

generating second feedback information which completes binding based on the first feedback information, and sending the second feedback information to the service server;

and receiving the service notification which is sent by the service server and responds to the second feedback information, binding the available service notification, and forwarding the service notification to the terminal equipment.

2. The method of claim 1, wherein the terminal device is a bluetooth device.

3. The method of claim 1, wherein the account is a payment account and the operation code is a payment code or a collection code.

4. A binding method is applied to a service server, and the method comprises the following steps:

5. The method of claim 4, wherein further comprising, after said receiving a polling request sent by the network device to poll for binding results and sending binding result information to the network device in response to the polling request to generate the second opcode and expose:

receiving an operation request for the account sent by the network equipment;

and executing the operation corresponding to the operation request on the account according to the binding relationship between the account and the network equipment.

6. The method of claim 4, wherein the account is a payment account and the second operation code is a payment code or a collection code.

7. The method of claim 4, wherein further comprising, after said receiving a polling request sent by the network device to poll for binding results and sending binding result information to the network device in response to the polling request to generate the second opcode and expose:

receiving first feedback information which is sent by the network equipment and used for binding the account and the network equipment;

generating notification information for notifying that binding is available in response to the first feedback information, and sending the notification information to the network device.

8. The method of claim 4, wherein after the generating a code generation key further comprises:

and sending the code generation key factor to the client.

9. The method of claim 8, wherein after sending the transcoding critical factor to the client, further comprising:

10. A binding migration method is applied to a first service server, and comprises the following steps:

and receiving binding result information which is sent by the second service server and responds to the polling request, and sending the binding result information to the network equipment, wherein when the binding is successful, the binding result information carries a code generation key factor which is used for generating a second operation code, and the second operation code is bound with an account and the network equipment.

11. The method of claim 10, wherein the account is a payment account and the second operation code is a payment code or a collection code.

12. The method according to claim 10, wherein after said receiving the binding result information sent by the second service server in response to the polling request, sending the binding result information to the network device further comprises:

receiving feedback information sent by the network equipment, wherein the account and the network equipment are bound, and sending the feedback information to the second service server;

and receiving first notification information which is sent by the second service server and responds to the feedback information and is used for notifying that binding is available, and sending the first notification information to the network equipment.

13. The method according to claim 10, wherein after said receiving the binding result information sent by the second service server in response to the polling request, sending the binding result information to the network device further comprises:

receiving a unbinding request which is sent by the network equipment and used for unbinding the account from the network equipment, and sending the unbinding request to the second service server;

and receiving second notification information which is sent by the second service server and responds to the unbinding request and is used for notifying the unbinding, and sending the second notification information to the network equipment.

14. A binding device applied to a service server comprises:

15. A binding migration apparatus applied to a first service server, the apparatus comprising:

a fourteenth receiver, configured to receive binding result information sent by the second service server and responding to the polling request, and send the binding result information to the network device, where when the binding is successful, the binding result information carries a key code generating factor, and the key code generating factor is used to generate a second operation code, and the second operation code is bound with an account and the network device.

16. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, the processor implementing the steps of the method of any of claims 1-3 or 4-13 when executing the instructions.

17. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the method of any one of claims 1-3 or 4-13.