TWI777070B - Binding, migration method and apparatus, computing device and storage medium - Google Patents

Abstract

This specification provides a binding and migration method and device, a computing device and a storage medium, wherein the binding method includes: sending a pre-binding request to a service server, the pre-binding request carrying the device parameter information of the pre-binding terminal device and pre-bound account information; receive a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is generated based on the device parameter information and the account information; The server sends a binding request, and the binding request carries the binding beacon; and receives the 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 and match the The operation code bound to the account and the terminal device; the key factor of generating the code is sent to the terminal device to generate and display the operation code.

Description

Binding, migration method and apparatus, computing device and storage medium

This specification relates to the field of mobile application technologies, and in particular, to a binding and migration method and device, a computing device and a storage medium.

At present, smart devices are emerging in an endless stream, and payment products are constantly being produced and upgraded. The lack of standardized processes for device binding and product maintenance has brought great inconvenience to daily access work and poor user experience.

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

According to a first aspect of the embodiments of this specification, a binding method is provided, which is applied to a client. The method includes: sending a pre-binding request to a service server, where the pre-binding request carries a device of a pre-bound terminal device Parameter information and pre-bound account information; receive a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is generated based on the device parameter information and the account information; Send a binding request to the service server, where the binding request carries the binding beacon; receive the key factor used to generate the opcode sent by the service server in response to the binding request, wherein the The key factor for generating the operation code is used to generate the operation code bound to the account and the terminal device; the key factor for generating the operation code is sent to the terminal device to generate and display the operation code.

According to a second aspect of the embodiments of this specification, a binding method is provided, which is applied to a service server. The method includes: receiving a pre-binding request sent by a client, where the pre-binding request carries the information of a pre-bound terminal device. Device parameter information and pre-bound account information; generate a binding beacon based on the device parameter information and the account information, and send the binding beacon to the client; receive the binding request sent by the client, The binding request carries the binding beacon; generate a key factor for generating an opcode for generating an opcode bound to the account and the terminal device, and send the key factor for generating an opcode to the client.

According to a third aspect of the embodiments of this specification, a binding method is provided, applied to a network device, the method includes: sending a pre-binding request to a service server, where the pre-binding request carries the device of the network device parameter information; receiving a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is generated based on the device parameter information; A first operation code is generated according to the binding beacon, and the first operation code is displayed so that the client can scan the code and send a binding request to the service server. The binding request carries the binding beacon and the bound account information; send a polling request to the business server for polling the binding result, and receive the binding result information sent by the business server in response to the polling request, wherein, when the binding is successful, The binding result information carries a key factor for generating an opcode, and the key factor for generating an opcode is used to generate a second opcode bound to the account and the network device; sending the binding to the service server The binding request carries the binding beacon; the key factor used to generate the opcode sent by the service server in response to the binding request is received, wherein the key factor used to generate the opcode is to generate a second operation code bound to the account and the network device; generate and display the second operation code according to the key factor for generating the operation code.

According to a fourth aspect of the embodiments of this specification, a binding method is provided, which is applied to a service server. The method includes: receiving a pre-binding request sent by a network device, where the pre-binding request carries the information of the network device. Device parameter information; generate a binding beacon based on the device parameter information, and send the binding beacon to the network device so that the network device generates and displays the first opcode based on the binding beacon; receives the client The binding request sent, the binding request carries the information of the binding beacon and the bound account, wherein the client scans the The first operation code displayed by the network device obtains the binding beacon; obtains the device parameter information based on the binding beacon, and binds the network device corresponding to the device parameter information to the account corresponding to the account information ; Generate a key factor for generating an operation code, the generation key factor is used to generate a second operation code bound to the account and the network device; Receive the first operation code sent by the network device for polling the binding result a polling request, and sending binding result information to the network device in response to the first polling request, wherein, when the binding is successful, the binding result information carries the key factor for generating the opcode to generate the second opcode and display it.

According to a fifth aspect of the embodiments of this specification, a binding method is provided, applied to a client, the method includes: acquiring a binding beacon by scanning a first operation code displayed by a network device, and the binding beacon is used for Identify the identity information of the network device; send a binding request to the service server, the binding request carrying the information of the binding beacon and the bound account; receive the response sent by the service server in response to the binding request The key factor for generating an opcode, wherein the key factor for generating an opcode is used to generate a second opcode binding the network device and the account.

According to a sixth aspect of the embodiments of this specification, a binding migration method is provided, applied to a network device, the method includes: sending a pre-binding request to a first service server, so that the first service server is based on the The device parameter information of the network device carried in the pre-binding request generates a first binding beacon; Receive a second binding beacon sent by the first service server in response to the pre-binding request, wherein the second binding beacon is based on the first service server by a second service server serving as a migration destination server The device parameter information sent by the device and the first binding beacon are generated; the first operation code is generated according to the second binding beacon, and the first operation code is displayed so that the client can scan the code to obtain the second binding beacon to send a binding request to the second business server, the binding request carrying the information of the second binding beacon and the bound account; sending a wheel for polling the binding result to the first business server polling request, and receiving binding result information sent by the first service server in response to the polling request, wherein the binding result information is sent by the second service server based on the round forwarded by the first service server The query request is generated. When the binding is successful, the binding result information carries the key factor used to generate the opcode, and the key factor used to generate the opcode is used to generate a second binding with the account and the network device. an opcode; the second opcode is generated and displayed according to the key factor for generating the opcode.

According to a seventh aspect of the embodiments of the present specification, a binding migration method is provided, which is applied to a first service server. The method includes: receiving a pre-binding request sent by a network device, where the pre-binding request carries the network Device parameter information of the device; determine whether the service destination server of the pre-binding request is the first service server, if the judgment result is otherwise, generate a first binding beacon based on the device parameter information, and the first binding The beacon and the pre-binding request are sent to The second service server as the migration destination server enables the second service server to generate a second binding beacon based on the device parameter information and the first binding beacon; receiving the response sent by the second service server in The second binding beacon of the pre-binding request is sent to the network device; the polling request for polling the binding result sent by the network device is received, and the second binding beacon is sent to the network device. send the polling request to the second service server; receive the binding result information sent by the second service server in response to the polling request, and send the binding result information to the network device, when the binding is successful , the binding result information carries a key factor for generating an opcode, and the key factor for generating an opcode is used to generate a second opcode bound to the account and the network device.

According to an eighth aspect of the embodiments of this specification, a binding migration method is provided, applied to a second service server, the method includes: receiving a pre-binding request sent by the first service server, wherein the pre-binding request carries There is device parameter information of the pre-bound network device and a first binding beacon, the first binding beacon is generated by the first service server based on the device parameter information; based on the device parameter information and the first binding beacon The binding beacon generates a second binding beacon; the second binding beacon is sent to the first service server so that the first service server sends the second binding beacon to the network device so that the network device generates and displays a first opcode according to the second binding beacon; receives a binding request sent by the client, wherein the binding request includes the The information of the second binding beacon and the pre-bound account, the client obtains the second binding beacon by scanning the first operation code displayed by the network device; and determines whether the binding request contains the first binding beacon. 2. Binding beacon, if the judgment result is yes, the account will be bound with the network device, and the key factor used to generate the opcode will be generated according to the binding result and sent to the client; the first service server will be received. The first polling request sent by the server to poll the binding result, wherein the first polling request is sent by the network device to the first service server; query the network device according to the first polling request With the binding result of the account, send the queried binding result information to the first business server, so that the first business server sends the binding result information to the network device, wherein after the binding is successful In the case of , the binding result information carries the key factor for generating the opcode, and the key factor for generating the opcode is used to generate the second opcode bound to the account and the network device.

According to a ninth aspect of the embodiments of this specification, there is provided a binding apparatus, which is applied to a client, the apparatus includes: a first requester, configured to send a pre-binding request to a service server, where the pre-binding request carries There are device parameter information of the pre-bound terminal device and information of the pre-bound account; the first receiver is configured to receive the binding beacon sent by the service server in response to the pre-binding request, wherein the binding The fixed beacon is generated based on the device parameter information and the information of the account; the second requester is configured to send a binding request to the service server, and the binding request carries the binding beacon; a second receiver, configured to receive a key factor for generating an opcode sent by the service server in response to the binding request, wherein the key factor for generating an opcode is used to generate an association between the account and the The operation code bound to the terminal device; the first presenter is configured to send the key factor for generating the operation code to the terminal device to generate and display the operation code.

According to a tenth aspect of the embodiments of this specification, there is provided a binding apparatus, which is applied to a service server, the apparatus includes: a third receiver configured to receive a pre-binding request sent by a client, the pre-binding request Carrying the device parameter information of the pre-bound terminal device and the information of the pre-bound account; the first generator is configured to generate a binding beacon based on the device parameter information and the information of the account, and send it to the client the binding beacon; a fourth receiver configured to receive a binding request sent by the client, the binding request carrying the binding beacon; a second generator configured to generate The account and the key factor for generating the operation code of the operation code bound to the terminal device are sent to the client.

According to an eleventh aspect of the embodiments of this specification, there is provided a binding apparatus, which is applied to a network device. The apparatus includes: a third requester configured to send a pre-binding request to a service server, the pre-binding The request carries the device parameter information of the network device; the fourth receiver is configured to receive a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is based on the device parameter information generation; the second presenter is configured to generate a first operation code according to the binding beacon, display the first operation code so that the client can scan the code and send a binding request to the service server, the binding The request carries the information of the binding beacon and the bound account; the fourth requester is configured to send a polling request for polling the binding result to the business server, and receive the information sent by the business server. Binding result information in response to the polling request, wherein, when the binding is successful, the binding result information carries the key factor used to generate the opcode, and the key factor used to generate the opcode is used to generate a connection with the account a second opcode bound to the network device; a fifth requester, configured to send a binding request to the service server, the binding request carrying the binding beacon; a fifth receiver, configured In order to receive the key factor for generating an opcode sent by the service server in response to the binding request, the key factor for generating an opcode is used to generate the first key factor bound to the account and the network device. A second opcode; a third presenter configured to generate and present the second opcode according to the key factor for generating the opcode.

According to a twelfth aspect of the embodiments of the present specification, a binding apparatus is provided, applied to a service server, the apparatus includes: a sixth receiver configured to receive a pre-binding request sent by a network device, the pre-binding The predetermined request carries the device parameter information of the network device; the third generator is configured to generate a binding based on the device parameter information a beacon, which sends the binding beacon to the network device so that the network device generates and displays a first operation code based on the binding beacon; a seventh receiver is configured to receive the binding sent by the client request, the binding request carries the binding beacon and the information of the bound account, wherein the client obtains the binding beacon by scanning the first operation code displayed by the network device; the first binding a generator, configured to obtain the device parameter information based on the binding beacon, and bind the network device corresponding to the device parameter information to the account corresponding to the account information; a fourth generator, configured to generate A key factor for generating an operation code, the generating key factor is used to generate a second operation code bound to the account and the network device; an eighth receiver is configured to receive a message sent by the network device for polling the binding A first polling request for determining a result, and sending binding result information to the network device in response to the first polling request, wherein, when the binding is successful, the binding result information carries the information for generating the operation key factor of the code to generate the second opcode and display.

According to a thirteenth aspect of the embodiments of this specification, there is provided a binding device, which is applied to a client, the device includes: a scanner configured to acquire a binding beacon by scanning a first operation code displayed by a network device, The binding beacon is used to identify the identity information of the network device; the sixth requester is configured to send a binding request to the service server, and the binding request carries the binding beacon and the bound account information. News; A ninth receiver, configured to receive a key factor for generating an opcode sent by the service server in response to the binding request, wherein the key factor for generating an opcode is used to generate and bind the network device and the second opcode for that account.

According to a fourteenth aspect of the embodiments of the present specification, there is provided a binding migration apparatus, which is applied to a network device. The apparatus includes: a seventh requester, configured to send a pre-binding request to the first service server to Make the first service server generate a first binding beacon based on the device parameter information of the network device carried in the pre-binding request; a tenth receiver is configured to receive a response sent by the first service server in The second binding beacon of the pre-binding request, wherein the second binding beacon is sent by the second service server as the migration destination server based on the device parameter information sent by the first service server and the first binding A fixed beacon is generated; the fifth generator is configured to generate a first operation code according to the second binding beacon, and display the first operation code so that the client can scan the code to obtain the second binding beacon to send to the first The second business server sends a binding request, the binding request carries the information of the second binding beacon and the bound account; the eighth requester is configured to send a polling request to the first business server A polling request for binding results, and receiving binding result information sent by the first service server in response to the polling request, wherein the binding result information is sent by the second service server based on the first service server The polling request forwarded by the server is generated. When the binding is successful, the binding result information carries the key factor used to generate the opcode, and the key factor used to generate the opcode is used to generate a connection between the account and the network device. the bound second opcode; The fourth presenter is configured to generate and present the second opcode according to the key factor for generating the opcode.

According to a fifteenth aspect of the embodiments of this specification, there is provided a binding migration apparatus, which is applied to a first service server, and the apparatus includes: an eleventh receiver configured to receive a pre-binding request sent by a network device , the pre-binding request carries the device parameter information of the network device; the sixth generator is configured to judge whether the service purpose server of the pre-binding request is the first service server, and if the judgment result is otherwise A first binding beacon is generated based on the device parameter information, and the first binding beacon and the pre-binding request are sent to the second service server as the migration destination server, so that the second service server is based on the The device parameter information and the first binding beacon generate a second binding beacon; the twelfth receiver is configured to receive the second binding beacon sent by the second service server in response to the pre-binding request , send the second binding beacon to the network device; the thirteenth receiver is configured to receive the polling request sent by the network device for polling the binding result, and send the polling request to the second service server; the fourteenth receiver is configured to receive the binding result information sent by the second service server in response to the polling request, and send the binding result information to the network device , when the binding is successful, the binding result information carries a key factor for generating an opcode, and the key factor for generating an opcode is used to generate a second opcode bound to the account and the network device.

According to the sixteenth aspect of the embodiments of the present specification, a binding is provided A migration device, applied to a second service server, includes: a fifteenth receiver configured to receive a pre-binding request sent by the first service server, wherein the pre-binding request carries a pre-bound network device parameter information of the road device and a first binding beacon, the first binding beacon is generated by the first service server based on the device parameter information; a seventh generator is configured based on the device parameter information and the The first binding beacon generates a second binding beacon, and sends the second binding beacon to the first service server so that the first service server sends the second binding beacon to the network a road device, so that the network device generates a first opcode according to the second binding beacon and displays it; a sixteenth receiver is configured to receive a binding request sent by a client, wherein the binding request includes the first operation code. Two binding beacons and pre-bound account information, the client obtains the second binding beacon by scanning the first operation code displayed by the network device; the judger is configured to judge the binding request Whether the second binding beacon is included, and if the judgment result is yes, the account is bound to the network device, and the key factor used to generate the opcode is generated according to the binding result and sent to the client; Seventeen receivers, configured to receive a first polling request sent by the first service server for polling the binding result, wherein the first polling request is sent by the network device to the first service server The second binding device is configured to query the binding result between the network device and the account according to the first polling request, and send the binding result information obtained by the query to the first service server, so that the The first service server binds the binding If the information is sent to the network device, in the case of successful binding, the binding result information carries the key factor used to generate the opcode, and the key factor used to generate the opcode is used to generate a connection with the account The second opcode bound to the network device.

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

According to an eighteenth aspect of the embodiments of the present specification, a computer-readable storage medium is provided, which stores computer instructions, and when the instructions are executed by a processor, implements the steps of the binding method or the binding migration method.

In the embodiment of this specification, by binding the device parameter information of the terminal device with the account information of the client, after successful binding, the operation code is generated on the terminal device according to the key factor used to generate the operation code generated by the service server of the account, and the Display, so that the old terminal equipment can also operate the account like the new product, which is convenient and simple, and improves the user experience; it provides a convenient and safe solution for the increasing number of smart device binding and the replacement of old and new business account products. The binding process enables new product applications to be compatible with old devices, facilitates old devices to use new product applications, and ensures service usability and security during the evolution of new and old products.

100: Computing Devices

110: Memory

120: Processor

130: Busbar

140: Access device

150:Database

160: Internet

202~210: Steps

302~308: Steps

1~9.3: Steps

502~514: Steps

602~612: Steps

702~706: Steps

902~910: Steps

1002~1010: Steps

1102~1112: Steps

1300, 1400, 1500, 1600, 1700: Binding devices

1302: First Requester

1304: First Receiver

1306: Second Requester

1308: Second Receiver

1310: First Demonstrator

1402: Third Receiver

1404: First Builder

1406: Fourth Receiver

1408: Second Generator

1502: Third Requester

1504: Fourth Receiver

1506: Second Demonstrator

1508: Fourth Requester

1510: Fifth Requester

1512: Fifth Receiver

1514: Third Demonstrator

1602: Sixth Receiver

1604: Third Generator

1606: Seventh Receiver

1608: First Binder

1610: Fourth Generator

1612: Eighth Receiver

1702: Scanner

1704: Sixth Requester

1706: Ninth Receiver

1800, 1900, 2000: Migration devices

1802: Seventh Requester

1804: Tenth Receiver

1806: The Fifth Builder

1808: Eighth Requester

1810: Fourth Demonstrator

1902: Eleventh Receiver

1904: Sixth Builder

1906: Twelfth Receiver

1908: Thirteenth Receiver

1910: Fourteenth Receiver

2002: The fifteenth receiver

2004: Seventh Builder

2006: Sixteenth Receiver

2008: Judger

2010: The Seventeenth Receiver

2012: Second Binder

In order to more clearly illustrate the technical solutions of the embodiments of the present specification, the drawings required to be used in the description of the embodiments will be briefly introduced below. It is obvious that the drawings in the following description are only some embodiments of this specification, and for those skilled in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1 is a block diagram showing the structure of a computing device 100 according to an embodiment of the present specification; FIG. 2 is a schematic flowchart showing a binding method applied to a client according to an embodiment of the present specification; A schematic flowchart of a binding method applied to a server according to an embodiment of this specification; FIG. 4 is a schematic flowchart showing a binding method of an embodiment of this specification; FIG. 5 is an application of an embodiment of this specification. FIG. 6 is a schematic flowchart showing a binding method applied to a server according to an embodiment of the present specification; FIG. 7 is a schematic flowchart showing an application of an embodiment of the present specification. A schematic flowchart of a binding method for a client; FIG. 8 is a schematic flowchart illustrating a binding method according to another embodiment of the present specification; FIG. 9 is a schematic flowchart illustrating a binding migration applied to a network device according to an embodiment of the present specification. A schematic flowchart of the method; FIG. 10 is a schematic flowchart illustrating a binding migration method applied to a first server according to an embodiment of the present specification; FIG. 11 is a schematic flowchart illustrating an embodiment of the present specification applied to a second server FIG. 12 is a schematic flowchart of a binding migration method according to an embodiment of the present specification; FIG. 13 is a module diagram showing a binding device according to an embodiment of the present specification; FIG. 14 is a module diagram showing a binding device according to another embodiment of this specification; FIG. 15 is a module diagram showing a binding device according to another embodiment of this specification; A module diagram of a binding device according to an embodiment; FIG. 17 is a module diagram showing a binding device according to another embodiment of this specification; FIG. 18 is a diagram showing a binding migration device according to an embodiment of this specification. Module diagram; FIG. 19 is a module diagram illustrating a binding migration device according to another embodiment of the present specification; FIG. 20 is a module diagram illustrating a binding device according to another embodiment of the present specification.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can do so without departing from this specification. Therefore, this specification is not limited by the specific implementation disclosed below.

FIG. 1 is a block diagram illustrating the structure of a computing device 100 according to an embodiment of the present specification. Elements of the computing device 100 include, but are not limited to, the memory 110 and the processor 120 . The processor 120 and the memory 110 are connected through the bus bar 130, and the database 150 is used for storing user data.

Computing device 100 also includes access device 140 that enables computing device 100 to communicate via one or more networks 160 . Examples of such networks include a 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 (eg, Network Interface Card (NIC)), wired or wireless, such as IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, World Interoperability for Microwave Access (Wi-MAX) interface, Ethernet interface, Universal Serial Bus (USB) interface, cellular network interface, Bluetooth interface, Near Field Communication (NFC) interface, etc.

In one embodiment of the present specification, the above-described and other elements of the computing device 100 not shown in FIG. 1 may also be connected to each other, such as by bus bars. It should be understood that the block diagram of the computing device structure shown in FIG. 1 is only for the purpose of example, and not for limiting the scope of this specification. Those skilled in the art can add or replace other elements as needed.

Computing device 100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (eg, tablet computer, personal digital assistant, notebook computer, notebook computer, lightweight laptop, etc.), Mobile phones (eg, smartphones), wearable computing devices (eg, smart watches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs. Computing device 100 may also be a mobile or stationary server.

The processor 120 may execute the steps in the method shown in FIG. 2 . FIG. 2 is a schematic flowchart showing a binding method according to an embodiment of the present specification, which is applied to a client. The client may be a payment application such as Alipay, WeChat, JD Wallet, Baidu Wallet, and the like. The method includes steps 202 to 210 .

Step 202: Send a pre-binding request to the service server, where the pre-binding request carries the device parameter information of the pre-bound terminal device and the information of the pre-bound account.

In one implementation, the account is a payment account, and the operation code is a payment code or a payment code. In addition, the account can also be a barcode for access control or other barcodes for identifying information.

In an implementation manner, the terminal device is a Bluetooth device, such as a Bluetooth-enabled bracelet, a watch, and other terminal devices.

In an implementation manner, before the pre-binding request is sent to the service server, the pre-binding request carrying the device parameter information of the pre-bound terminal device and the information of the pre-bound account further includes: to obtain an acquisition request for device parameter information, and receive the device parameter information sent by the terminal device in response to the acquisition request. In addition, during specific implementation, the device parameters of the pre-bound terminal device may also be manually input at the client.

Step 204: Receive a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is generated based on the device parameter information and the account information.

Step 206: Send a binding request to the service server, where the binding request carries the binding beacon.

Step 208: Receive a key factor for generating an opcode sent by the service server in response to the binding request, wherein the key factor for generating an opcode is used to generate a key factor bound to the account and the terminal device. opcode.

Step 210: Send the key factor for generating the opcode to the terminal device to generate and display the opcode.

In an implementation manner, after the key factor for generating the operation code is sent to the terminal device to generate and display the payment code or the payment code, the method further includes: receiving a successful reception of the operation code used for generating the operation sent by the terminal device. The first feedback information of the key factor of the code; based on the first feedback information, the second feedback information for completing the binding is generated, and the second feedback information is sent to the service server; the response sent by the service server is received in response to the The second feedback information is used to notify the service notification that the binding is available, and forward the service notification to the terminal device.

The processor 120 may execute the steps in the method shown in FIG. 3 . FIG. 3 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, which is applied to a server. The method includes steps 302 to 308 .

Step 302: Receive a pre-binding request sent by the client, the pre-binding request carrying the device parameter information of the pre-binding terminal device and the pre-binding account. account information.

In one implementation, the account is a payment account, and the operation code is a payment code or a payment code. In addition, the account can also be a barcode for access control or other barcodes for identifying information.

In an implementation manner, the terminal device is a Bluetooth device, such as a Bluetooth-enabled bracelet, a watch, and other terminal devices.

Step 304: Generate a binding beacon based on the device parameter information and the account information, and send the binding beacon to the client.

Step 306: Receive a binding request sent by the client, where the binding request carries the binding beacon.

Step 308: Generate a key factor for generating an opcode for generating an opcode bound to the account and the terminal device, and send the key factor for generating an opcode to the client.

In an implementation manner, after generating the key factor for generating the opcode used to generate the opcode bound to the account and the terminal device, and sending the key factor for generating the opcode to the client Including: receiving second feedback information sent by the client to complete the binding, wherein the second feedback information is generated based on the first feedback information sent by the terminal device that successfully receives the key factor used to generate the opcode; The client sends a service notification that the service processing is successful in response to the second feedback information.

In the embodiment of this specification, by binding the device parameter information of the terminal device with the account information of the client, after successful binding, the operation code is generated on the terminal device according to the key factor used to generate the operation code generated by the service server of the account, and the display, so that the old terminal equipment can also look like the new It is convenient and simple to operate accounts in the same way as products, which improves the user experience; it provides a convenient and secure binding process for the increasing number of smart device binding and the replacement of new and old business account products, so that new product applications can be compatible with old devices. It is convenient for old devices to use new products and applications, and ensures the ease of use and security of services during the evolution of new and old products.

FIG. 4 is a schematic flowchart showing a binding method according to an embodiment of this specification; as shown in FIG. 4 , the method includes: 1. A client sends a request to a Bluetooth device to obtain device parameters of a pre-bound Bluetooth device; In response to the client's request, the Bluetooth device sends device parameter information to the client (corresponding to step 1.1 in Figure 4); 2. The client sends a pre-binding request to the service server according to the received device parameter information of the Bluetooth device. The pre-binding request carries the pre-binding param (parameter): the device parameter information of the Bluetooth device and the information of the pre-bound account; the service server generates the binding according to the device parameter information of the Bluetooth device and the information of the pre-bound account. Set the context token (binding beacon) (corresponding to step 2.1 in Figure 4); the business server sends the binding context token to the client (corresponding to step 2.2 in Figure 4); the client sends a binding request to the business server, The binding request carries the binding param, and the binding param includes the binding context token and the bound account information (corresponding to step 2.3 in Figure 4); the service server verifies the received binding request and determines the binding request Whether the binding beacon is carried in the device, if the judgment result is yes, the account will be bound to the Bluetooth device, and the key factor used to generate the opcode will be generated. This step is the key process of product binding (corresponding to Figure 4). Step 2.3.1); the business server returns the key factor used to generate the opcode to the client (corresponding to the step in Figure 4) Step 2.3.2); 3. The client uploads the received key factor for generating the opcode to the Bluetooth device; the Bluetooth device returns to the client the feedback information of successfully receiving the key factor for generating the opcode (corresponding figure Step 3.1 in 4); 4, the client sends the feedback information that the Bluetooth device and the account are bound to the 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 ) ), deliver service parameters to the client, and inform (bind) that the service is processed successfully (corresponding to step 4.2 in Figure 4); 5. The client sends notification information to the Bluetooth device that the binding is successful, and the Bluetooth device sends and receives to the client For successful feedback information, the operation code (corresponding to step 5.1 in Figure 4) is generated and displayed according to the key factors used to generate the operation code, and then operations such as payment and access control can be performed.

The processor 120 may execute the steps in the method shown in FIG. 5 . FIG. 5 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, which is applied to a network device, which may be a terminal device such as a smart watch or a mobile phone with a network communication function. The method includes steps 502 to 514 .

Step 502: Send a pre-binding request to the service server, where the pre-binding request carries the device parameter information of the network device.

In one implementation, the account is a payment account, and the operation code is a payment code or a payment code. In addition, the account can also be a barcode for access control or other barcodes for identifying information.

Step 504: Receive a response sent by the service server in response to the pre-binding The requested binding beacon, wherein the binding beacon is generated based on the device parameter information.

Step 506: Generate a first operation code according to the binding beacon, display the first operation code so that the client can scan the code and send a binding request to the service server, the binding request carries the binding beacon and Information about the linked account.

Step 508: Send a polling request for polling the binding result to the service server, and receive the binding result information sent by the service server in response to the polling request, wherein, when the binding is successful, the The binding result information carries a key factor for generating an opcode, and the key factor for generating an opcode is used to generate a second opcode bound to the account and the network device.

Step 510: Send a binding request to the service server, where the binding request carries the binding beacon.

Step 512: Receive a key factor for generating an opcode sent by the service server in response to the binding request, wherein the key factor for generating an opcode is used to generate a binding with the account and the network device the second opcode.

Step 514: Generate and display the second opcode according to the key factor for generating the opcode.

In an implementation manner, after generating and displaying the second opcode according to the key factor for generating the opcode, the method further includes: sending the first feedback information that the account and the network device are bound to the service server. ; Receive the notification information sent by the service server in response to the first feedback information for notifying that the binding is available.

The processor 120 may execute the steps in the method shown in FIG. 6 . FIG. 6 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, which is applied to a service server. The method includes steps 602 to 612 .

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

Step 604: Generate a binding beacon based on the device parameter information, and send the binding beacon to the network device so that the network device generates and displays a first operation code based on the binding beacon.

Step 606: Receive a binding request sent by the client, where the binding request carries the binding beacon and the information of the bound account, wherein the client scans the first implementation displayed by the network device , the account is a payment account and the opcode is a payment code or a receipt code. In addition, the account can also be a barcode for access control or other barcodes for identifying information.

The opcode gets the binding beacon.

Step 608: Obtain the device parameter information based on the binding beacon, and bind the network device corresponding to the device parameter information to the account corresponding to the account information.

Step 610: Generate a key factor for generating an opcode, where the key factor is used to generate a second opcode bound to the account and the network device.

In an implementation manner, after the generating the key factor for generating the opcode, the method further includes: sending the key factor for generating the opcode to the client.

Step 612: Receive a first polling request sent by the network device for polling the binding result, and send binding result information to the network device in response to the first polling request. When successful, the binding result information carries the key factor for generating the opcode to generate and display the second opcode.

In one implementation, the second operation is generated by receiving a polling request sent by the network device for polling the binding result, and sending binding result information to the network device in response to the polling request. After the code is displayed and displayed, the method further includes: receiving an operation request for the account sent by the network device; and performing an operation corresponding to the operation request for the account according to the binding relationship between the account and the network device.

In one implementation, the second operation is generated by receiving a polling request sent by the network device for polling the binding result, and sending binding result information to the network device in response to the polling request. After the code is displayed, it also includes: receiving first feedback information sent by the network device that the account and the network device have completed binding; generating notification information for notifying that binding is available in response to the first feedback information, and sending the The network device sends the notification information.

In an implementation manner, after sending the key factor used to generate the opcode to the client, the method further includes: receiving a second polling request sent by the client for polling the binding result, and responding to the first polling request. The second polling request sends the binding result information to the client.

The processor 120 may execute the steps in the method shown in FIG. 7 . picture 7 is a schematic flow chart showing a binding method according to an embodiment of the present specification, which is applied to a client, and the client may be a payment application such as Alipay, WeChat, JD Wallet, Baidu Wallet, and the like. The method includes steps 702 to 706 .

Step 702: Obtain a binding beacon by scanning the first operation code displayed by the network device, where the binding beacon is used to identify the identity information of the network device.

Step 704: Send a binding request to the service server, where the binding request carries the binding beacon and the information of the bound account.

In one implementation, the account is a payment account, and the operation code is a payment code or a payment code. In addition, the account can also be a barcode for access control or other barcodes for identifying information.

Step 706: Receive the key factor used to generate the opcode sent by the service server in response to the binding request, wherein the key factor used to generate the opcode is used to generate the first key factor for binding the network device and the account. Two opcodes.

In an implementation manner, after receiving the key factor for generating the operation code sent by the service server in response to the binding request, the method further includes: sending to the service server for polling the network device and the account. Polling request for binding results; receive binding result notification information sent by the service server in response to the polling request.

In the embodiment of this specification, by binding the device parameter information of the terminal device with the account information of the client, after successful binding, the operation code is generated on the terminal device according to the key factor used to generate the operation code generated by the service server of the account, and the display, so that the old terminal equipment can also look like the new It is convenient and simple to operate accounts in the same way as products, which improves the user experience; it provides a convenient and secure binding process for the increasing number of smart device binding and the replacement of new and old business account products, so that new product applications can be compatible with old devices. It is convenient for old devices to use new products and applications, and ensures the ease of use and security of services during the evolution of new and old products.

FIG. 8 is a schematic flowchart showing a binding method according to an embodiment of the present specification; as shown in FIG. 8 , the method includes: 1. The network device sends a pre-binding request to the service server, and uploads the device of the network device Parameter information param; the service server generates a binding context token (beacon) according to the device parameter information of the network device (corresponding to step 1.1 in Figure 8), and returns the binding context token to the network device (corresponding to Figure 8 in Step 1.2); the network device generates a binding two-dimensional barcode according to the received binding context token (corresponding to step 1.3 in Figure 8); 2. The client scans the binding two-dimensional barcode to obtain the binding context token (corresponding to the figure Step 2.1) in 8; 3, the client sends a binding request to the service server, and the binding request includes the information of the binding context token and the pre-bound account; the service server verifies the received binding request , judge whether the binding context token is carried in the binding request, and if the judgment result is yes, bind the account to the network device, and generate the key factor for generating the opcode. This step is the key to product binding Process (corresponding to step 3.1 in Figure 8); the business server returns the key factor used to generate the opcode to the client (corresponding to step 3.2 in Figure 8); 4. After generating the bound two-dimensional barcode, the network device sends the business server Start sending a polling request to check whether the binding is successful, the service server queries the binding result in response to the polling request (corresponding to step 4.1 in Figure 8), and sends the binding result information obtained by the query to the network The device, wherein, when the binding is successful, the binding result information carries the key factor for generating the opcode (corresponding to step 4.2 in Figure 8), and the key factor for generating the opcode is used to generate the account and the The operation code bound by the network device; after receiving the key factor used to generate the operation code, the network device sends the service server the feedback information that the network device and the account have been bound (corresponding to the steps in Fig. 8 ) 4.3); 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 Figure 8), and issues service parameters to the network device to inform (bind) that the service has been processed successfully (corresponding to Figure 8). Step 4..3.2 in 8); the network device generates an opcode and displays it according to the received key factor for generating the opcode (corresponding to step 4.3.3 in Figure 8), and then it can perform services such as payment and access control Operation; 5. The client sends a polling request to the business server to check whether the binding is successful, and the business server queries the binding result in response to the polling request (corresponding to step 5.1 in Figure 8), and obtains the result of the query. The binding result information sent to the client corresponds to step 5.2 in Figure 8).

The processor 120 may execute the steps in the method shown in FIG. 9 . FIG. 9 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, which is applied to a network device. The method includes steps 902 to 910 .

Step 902: Send a pre-binding request to the first service server, so that the first service server generates a first binding beacon based on the device parameter information of the network device carried in the pre-binding request.

Step 904: Receive a second binding beacon sent by the first service server in response to the pre-binding request, wherein the second binding beacon is sent by the second service server serving as the migration destination server based on the first The device parameter information sent by a service server and the first binding beacon are generated.

Step 906: Generate a first operation code according to the second binding beacon, display the first operation code so that the client can scan the code to obtain the second binding beacon to send a binding request to the second service server, the The binding request carries the information of the second binding beacon and the bound account.

In one implementation, the account is a payment account, and the operation code is a payment code or a payment code. In addition, the account can also be a barcode for access control or other barcodes for identifying information.

Step 908: Send a polling request for polling the binding result to the first service server, and receive binding result information sent by the first service server in response to the polling request, wherein the binding The result information is generated by the second service server based on the polling request forwarded by the first service server. When the binding is successful, the binding result information carries the key factor used to generate the operation code, which is used to generate the operation code. The key factor of the code is used to generate a second opcode bound to the account and the network device.

Step 910: Generate and display the second opcode according to the key factor for generating the opcode.

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

In an implementation manner, after the second operation code is generated and displayed according to the key factor for generating the operation code, the method further includes: reporting to the first service The server sends feedback information that the account has been bound with the network device; receives the first notification information sent by the first business server in response to the feedback information to notify that the binding is available, wherein the first notification information Generated by the second service server based on the feedback information forwarded by the first service server.

In an implementation manner, after generating and displaying the second opcode according to the key factor for generating the opcode, the method further includes: sending an unbinding message to the first service server to unbind the account from the network device. request; receiving second notification information sent by the first service server in response to the unbinding request for notifying the unbinding, wherein the second notification information is based on the first service server by the second service server The forwarded unbinding request is generated.

The processor 120 may execute the steps in the method shown in FIG. 10 . FIG. 10 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, which is applied to the first service server. The method includes steps 1002 to 1010 .

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

Step 1004: Determine whether the service destination server of the pre-binding request is the first service server, and if the judgment result is otherwise, generate a first binding beacon based on the device parameter information, and use the first binding beacon and the The pre-binding request is sent to the second service server as the migration destination server, so that the second service server generates a second binding beacon based on the device parameter information and the first binding beacon;

Step 1006: Receive a response sent by the second service server in response to the preset The second binding beacon of the binding request is sent to the network device.

Step 1008: Receive a polling request sent by the network device for polling the binding result, and send the polling request to the second service server.

Step 1010: Receive the binding result information sent by the second service server in response to the polling request, and send the binding result information to the network device. When the binding is successful, the binding result information carries useful information The key factor for generating an opcode is used to generate a second opcode bound to the account and the network device.

In one implementation, the account is a payment account, and the operation code is a payment code or a payment code. In addition, the account can also be a barcode for access control or other barcodes for identifying information.

In an implementation manner, after 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 the information sent by the network device. The feedback information that the account is bound to the network device is completed, and the feedback information is sent to the second service server; the feedback information sent by the second service server in response to the feedback information is used to notify that the binding is available. The first notification information is sent to the network device.

In an implementation manner, after 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 the information sent by the network device. the unbind request to unbind the account from the network device, send the unbind request to the second service server; receive the response sent by the second service server in The second notification information of the unbinding request for notifying the unbinding is sent to the network device.

The processor 120 may execute the steps in the method shown in FIG. 11 . FIG. 11 is a schematic flowchart illustrating a binding migration method according to an embodiment of the present specification, which is applied to a second service server. The method includes steps 1102 to 1110 .

Step 1102: Receive a pre-binding request sent by the first service server, wherein the pre-binding request carries device parameter information of the pre-bound network device and a first binding beacon, the first binding beacon Generated by the first service server based on the device parameter information.

Step 1104: Generate a second binding beacon based on the device parameter information and the first binding beacon, and send the second binding beacon to the first service server so that the first service server The second binding beacon is sent to the network device so that the network device generates and displays the first operation code according to the second binding beacon.

Step 1106: Receive a binding request sent by the client, wherein the binding request includes the second binding beacon and the information of the pre-bound account, and the client scans the first opcode displayed by the network device Obtain the second binding beacon.

Step 1108: Determine whether the binding request contains the second binding beacon, and if the determination result is yes, bind the account with the network device, and generate a key factor for generating an opcode according to the binding result and sent to the client.

Step 1110: Receive the polling binding sent by the first service server A first polling request with a given result, wherein the first polling request is sent by the network device to the first service server.

Step 1112: Query the 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 binds the account. The result information is sent to the network device, wherein in the case of successful binding, the binding result information carries the key factor used to generate the opcode, and the key factor used to generate the opcode is used to generate and match the key factor. The second opcode bound to the account and this network device.

In an implementation manner, when the binding result between the network device and the account is queried according to the first polling request, the binding result obtained by the query is sent to the first business server, so that the first business server will After the binding result information is sent to the network device, the method further includes: receiving feedback information sent by the first service server that the account has been bound with the network device, wherein the feedback information is generated by the network device; The feedback information is generated to notify first notification information that binding is available, and the first notification information is sent to the first service server so that the first service server sends the first notification information to the network device .

In an implementation manner, when querying the binding result between the network device and the account according to the polling request, the first business server is informed of the binding result obtained by the query, so that the first business server will bind the binding result. After sending the determination result information to the network device, the method further includes: receiving an unbinding request sent by the first service server to unbind the account from the network device, wherein the unbinding request is generated and sent by the network device. to the first service server; according to the solution The binding request unbinds the account from the network device, and generates second notification information for notifying the unbinding; sending the second notification information to the first service server so that the first service server will The second notification information is sent to the network device.

In an implementation manner, after receiving the binding request sent by the client, the method further includes: receiving a second polling request sent by the client for polling the binding result; querying the network according to the second polling request The binding result between the device and the account sends the queried binding result information to the client, wherein in the case of successful binding, the binding result information carries the key factor used to generate the opcode.

In the embodiment of this specification, by binding the device parameter information of the terminal device with the account information of the client, after successful binding, the operation code is generated on the terminal device according to the key factor used to generate the operation code generated by the service server of the account, and the Display, so that the old terminal equipment can also operate the account like the new product, which is convenient and simple, and improves the user experience; it provides a convenient and safe solution for the increasing number of smart device binding and the replacement of old and new business account products. The binding process enables new product applications to be compatible with old devices, facilitates old devices to use new product applications, and ensures service usability and security during the evolution of new and old products.

FIG. 12 is a schematic flowchart showing a binding method according to an embodiment of the present specification; as shown in FIG. 12 , the method includes: 1. The network device sends a pre-binding request to the service server A, and uploads the data of the network device. Device parameter information param; the service server generates a binding context token (beacon) according to the device parameter information of the network device, (corresponding to the Step 1.1), and send the binding context token and the device parameter information of the network device to the service server B (corresponding to step 1.2 in Figure 12); the service server B receives the binding context token and device parameter information according to the received Generate the binding context of the specified token (corresponding to step 1.2.1 in Figure 12); business server B returns the binding context token of the specified token to business server A (corresponding to step 1.2.2 in Figure 12); business server A returns the binding context of the specified token to the network device (corresponding to step 1.2.3 in Figure 12); 2. The network device binds a QR code according to the received binding context of the specified token; 3. The client Scan the binding QR code to obtain the binding context token (corresponding to step 3.1 in Figure 12); 4. The client sends a binding request to the service server B, and the binding request includes the binding context token and pre-binding The information of the account; the business server B verifies the received binding request, and judges whether the binding context token is carried in the binding request. If the judgment result is yes, the account is bound to the network device. Generate the key factor used to generate the opcode, this step is the key process of product binding (corresponding to step 4.1 in Figure 12); business server B returns the key factor used to generate the opcode to the client (corresponding to Figure 8 in Figure 8) Step 4.2); 5. After generating the binding two-dimensional barcode, the network device starts to send a polling request to query whether the binding migration is successful to the service server A, and the service server A forwards the polling request to the service server. server B (corresponding to step 5.1 in Figure 12); service server B queries the binding result in response to the polling request (corresponding to step 5.1.1 in Figure 12), and sends the binding result information obtained by the query to Send it to service server A (corresponding to step 5.1.2 in Figure 12); service server A forwards the binding result information to the network device, and marks the forwarding flag as forwarding (corresponding to step 5.1.4 in Figure 12) , wherein, when the binding is successful, the binding result information carries a key factor for generating an opcode, and the key factor for generating an opcode is used to generate an opcode bound to the account and the network device; 6. After receiving the key factor used to generate the opcode, the network device sends feedback information that the network device and the account are bound to the service server A; the service server A forwards the forwarding flag bit. (corresponding to step 6.1 in Fig. 12 ), forward the bound feedback information to business server B (corresponding to step 6.2 in Fig. 12 ); business server B processes the availability of business products according to the feedback information (corresponding to Fig. 12 in Fig. 12 ) Step 6.2.1), deliver service parameters to service server A, and notify (binding migration) that the service processing is successful (corresponding to step 6.2.2 in Figure 12); service server A sends a notification that the service processing is successful to the network. network device (corresponding to step 6.2.3 in Figure 12); 7. The network device generates and displays the opcode according to the received key factor used to generate the opcode, and can perform business operations such as payment and access control; 8. The client sends a polling request to the service server B to check whether the binding is successful. Send the determination result information to the client (corresponding to step 8.2 in Figure 12); 9. The network device sends an unbinding request to the service server A to unbind the account from the network device; the service server A sends the unbinding request to the network device; Bind the request to forward to The service server B (corresponding to step 9.1 in Figure 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 it to the service server Server A (corresponding to Step 9.2 in Figure 12); Service Server A forwards the notification information of the unbinding result to the network device (corresponding to Step 9.3 in Figure 12).

Corresponding to the aforementioned binding method and binding migration method, this specification also provides an embodiment of a binding device and a binding migration device, and the device embodiment can be implemented by software, or by a combination of hardware or software and hardware. accomplish. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the internal memory through the processor of the device where it is located. From a hardware perspective, a hardware structure of the device where the binding device and the binding migration device are located in this specification may include a processor, a network interface, an internal memory, and a non-volatile memory. In the embodiment, the device The device in which it is located usually may include other hardware according to the actual function, which will not be repeated here.

Referring to FIG. 13 , it is a module diagram of the binding device according to an embodiment of the present specification. The binding apparatus 1300 corresponds to the embodiment shown in FIG. 2, and the apparatus 1300 includes: a first requester 1302, which is configured to send a pre-binding request to the service server, where the pre-binding request carries the information of the pre-bound terminal equipment. Device parameter information and pre-bound account information; the first receiver 1304 is configured to receive a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is based on the device Parameter information and information generation for the account; The second requester 1306 is configured to send a binding request to the service server, and the binding request carries the binding beacon; the second receiver 1308 is configured to receive a response sent by the service server in response to the A key factor for generating an opcode of the binding request, wherein the key factor for generating an opcode is used to generate an opcode bound to the account and the terminal device; the first presenter 1310 is configured to The key factor for generating the opcode is sent to the terminal device to generate and display the opcode.

In an optional embodiment, the terminal device is a Bluetooth device.

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

Referring to FIG. 14 , it is a module diagram of a binding device provided in an embodiment of the present specification. 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, the pre-binding request carrying the information of the pre-binding terminal device device parameter information and pre-bound account information; the first generator 1404 is configured to generate a binding beacon based on the device parameter information and the account information, and send the binding beacon to the client; The fourth receiver 1406 is configured to receive the binding request sent by the client, and the binding request carries the binding beacon; the second generator 1408 is configured to generate a connection between the account and the terminal device. the key factor of the bound opcode used to generate the opcode, And send the key factor used to generate the opcode to the client.

In an optional embodiment, the terminal device is a Bluetooth device.

Referring to FIG. 15 , it is a module diagram of the binding device according to an embodiment of the present specification. 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 the service server, where the pre-binding request carries the equipment of the network device parameter information; the fourth receiver 1504 is configured to receive a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is generated based on the device parameter information; the second presenter 1506 , is configured to generate a first operation code according to the binding beacon, display the first operation code to enable the client to scan the code and send a binding request to the service server, the binding request carrying the binding beacon and information of the bound account; the fourth requester 1508 is configured to send a polling request to the service server for polling the binding result, and to receive a response to the polling request sent by the service server Binding result information, wherein, when the binding is successful, the binding result information carries a key factor for generating an opcode, and the key factor for generating an opcode is used to generate a binding with the account and the network device The second opcode of The key factor sent by the server in response to the bind request to generate the opcode, where, The key factor for generating an opcode is used to generate a second opcode bound to the account and the network device; the third presenter 1514 is configured to generate and display according to the key factor for generating an opcode the second opcode.

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

Referring to FIG. 16 , it is a module diagram of a binding device provided in an embodiment of the present specification. 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 the information of the network device. device parameter information; the third generator 1604 is configured to generate a binding beacon based on the device parameter information, and send the binding beacon to the network device so that the network device generates and transmits the binding beacon based on the binding beacon. The first operation code is displayed; the seventh receiver 1606 is configured to receive a binding request sent by the client, and the binding request carries the binding beacon and the information of the bound account, wherein the client scans the The first operation code displayed by the network device obtains the binding beacon; the first binder 1608 is configured to obtain the device parameter information based on the binding beacon, and the network corresponding to the device parameter information The device is bound to the account corresponding to the account information; the fourth generator 1610 is configured to generate a key factor for generating an operation code, and the generation key factor is used to generate a key factor associated with the account and the network device The second opcode for binding; the eighth receiver 1612 is configured to receive a first polling request sent by the network device for polling the binding result, and to bind the binding in response to the first polling request The result information is sent to the network device, wherein when the binding is successful, the binding result information carries the key factor for generating the operation code to generate and display the second operation code.

Referring to FIG. 17 , it is a module diagram of a binding device according to an embodiment of the present specification. The binding device 1700 corresponds to the embodiment shown in FIG. 7 , and the device 1700 includes: a scanner 1702 configured to obtain a binding beacon by scanning a first operation code displayed by a network device, and the binding beacon is used to identify The identity information of the network device; the sixth requester 1704 is configured to send a binding request to the service server, the binding request carrying the binding beacon and the information of the bound account; the ninth receiver 1706 , is configured to receive a key factor for generating an opcode sent by the service server in response to the binding request, wherein the key factor for generating an opcode is used to generate a key factor for binding the network device and the account Second opcode.

Referring to FIG. 18 , it is a module diagram of a binding migration device according to an embodiment of the present specification. 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 the first service server, so that the first service server is based on the The device parameter information of the network device carried in the pre-binding request generates a first binding beacon; The tenth receiver 1804 is configured to receive a second binding beacon sent by the first service server in response to the pre-binding request, wherein the second binding beacon is sent by a second binding beacon serving as a migration destination server The service server is generated based on the device parameter information and the first binding beacon sent by the first service server; the fifth generator 1806 is configured to generate a first operation code according to the second binding beacon, showing the The first operation code enables the client to scan the code to obtain the second binding beacon to send a binding request to the second service server, and the binding request carries the information of the second binding beacon and the bound account The eighth requester 1808 is configured to send a polling request for polling the binding result to the first service server, and receive a binding result sent by the first service server in response to the polling request information, 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 the key used to generate the opcode factor, the key factor for generating an opcode is used to generate a second opcode bound to the account and the network device; the fourth presenter 1810 is configured to generate a second opcode according to the key factor for generating an opcode and display the second opcode.

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

Referring to FIG. 19 , it is a module diagram of a binding migration device according to an embodiment of the present specification. The binding migration apparatus 1900 corresponds to the embodiment shown in FIG. 10 and is applied to the first service server. The apparatus 1900 includes: The eleventh receiver 1902 is configured to receive a pre-binding request sent by a network device, and the pre-binding request carries device parameter information of the network device; the sixth generator 1904 is configured to determine the pre-binding request Determine whether the requested service purpose server is the first service server, and if the judgment result is otherwise, generate a first binding beacon based on the device parameter information, and send the first binding beacon and the pre-binding request to The second service server serving as the migration destination server enables the second service server to generate a second binding beacon based on the device parameter information and the first binding beacon; the twelfth receiver 1906 is configured to receive The second binding beacon sent by the second service server in response to the pre-binding request is sent to the network device; the thirteenth receiver 1908 is configured to receive the second binding beacon. The polling request sent by the network device to poll the binding result, and the polling request is sent to the second service server; the fourteenth receiver 1910 is configured to receive the data sent by the second service server. In response to the binding result information of the polling request, the binding result information is sent to the network device. When the binding is successful, the binding result information carries the key factor used to generate the opcode, which is used to generate The key factor of the opcode is used to generate a second opcode bound to the account and the network device.

Referring to FIG. 20 , it is a module diagram of a binding migration device according to an embodiment of the present specification. The binding migration apparatus 2000 corresponds to the embodiment shown in FIG. 11 and is applied to the second service server. The apparatus 2000 includes: The fifteenth receiver 2002 is configured to receive a pre-binding request sent by the first service server, wherein the pre-binding request carries the device parameter information of the pre-bound network device and the first binding beacon, The first binding beacon is generated by the first service server based on the device parameter information; the seventh generator 2004 is configured to generate a second binding beacon based on the device parameter information and the first binding beacon , sending the second binding beacon to the first service server, so that the first service server sends the second binding beacon to the network device, so that the network device according to the second binding The fixed beacon generates and displays the first operation code; the sixteenth receiver 2006 is configured to receive a binding request sent by the client, wherein the binding request includes the second binding beacon and the pre-bound account information, the client obtains the second binding beacon by scanning the first operation code displayed by the network device; the determiner 2008 is configured to determine whether the binding request contains the second binding beacon, If the judgment result is yes, the account is bound to the network device, and the key factor for generating the operation code is generated according to the binding result and sent to the client; the seventeenth receiver 2010 is configured to receive the The first polling request sent by the first service server for polling the binding result, wherein the first polling request is sent by the network device to the first service server; the second binding device 2012 is is configured to query the 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 binds the account The result information is sent to the network device, in which case the binding is successful Next, the binding result information carries the key factor for generating the opcode, and the key factor for generating the opcode is used to generate the second opcode bound to the account and the network device.

The devices, modules or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. The specific form of the computer can be a personal computer, a notebook computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control device. Tablets, Tablets, Wearables, or a combination of any of these devices.

For details of the implementation process of the functions and functions of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method, which will not be repeated here.

For the apparatus embodiments, since they basically correspond to the method embodiments, reference may be made to the partial descriptions of the method embodiments for related parts. The apparatus embodiments described above are only illustrative, wherein the units described as separate elements may or may not be physically separated, and the elements displayed as units may or may not be physical units, that is, they may be located in a local, or it can be distributed over multiple network elements. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement it without creative effort.

An embodiment of the present specification further provides a computing device, including a memory, a processor, and a computer instruction stored in the memory and running on the processor, and the processor implements the binding method, the binding method when the processor executes the instruction Certainly The steps of the migration method.

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, implements the steps of the binding method and the binding migration method.

The above is a schematic solution of a computer-readable storage medium of this embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the above method belong to the same concept, and the details of the technical solution of the storage medium that are not described in detail can be referred to the description of the technical solution of the above method.

The computer instructions include computer program code, which may be in source code form, object code form, 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 flash drive, portable hard disk, magnetic disk, optical disc, computer memory, Read-Only Memory (ROM, Read-Only) Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in this computer-readable medium may be appropriately increased or decreased in accordance with the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not Including electrical carrier signals and telecommunication signals.

It should be noted that, for the convenience of description, the foregoing method embodiments are all expressed as a series of action combinations, but those skilled in the art should know that this specification is not limited by the described action sequence. Because in accordance with this specification, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that in the description The described embodiments are all preferred embodiments, and the actions and modules involved are not necessarily all necessary in this specification.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are provided only to aid in the elaboration of the present specification. Alternative embodiments are not intended to exhaust all details, nor do they limit the invention to only the described embodiments. Obviously, many modifications and variations are possible in light of the content of this specification. These embodiments are selected and described in this specification to better explain the principles and practical applications of this specification, so that those skilled in the art can well understand and utilize this specification. This specification is limited only by the scope of the patent application and its full scope and equivalents.

Claims (20)

A binding method, applied to a client, includes: sending a pre-binding request to a service server, the pre-binding request carrying device parameter information of a pre-bound terminal device and information of a pre-bound account; receiving A binding beacon sent by the business server in response to the pre-binding request, wherein the binding beacon is generated based on the device parameter information and the account information; a binding request is sent to the business server, the binding The request carries the binding beacon; the key factor for generating an opcode sent by the service server in response to the binding request is received, wherein the key factor for generating an opcode is used to generate a key factor for generating an operation code with the account and The operation code bound to the terminal device; the key factor for generating the operation code is sent to the terminal device to generate and display the operation code, wherein the terminal device is any terminal device. The method of claim 1, wherein the terminal device is a Bluetooth device. The method of claim 1, wherein the account is a payment account and the opcode is a payment code or a collection code. The method according to claim 1, wherein sending to the service server before sending a pre-binding request, the pre-binding request carrying the device parameter information of the pre-bound terminal device and the information of the pre-bound account further includes: sending an acquisition request for acquiring the device parameter information to the terminal device, and receiving Device parameter information sent by the terminal device in response to the acquisition request. The method according to claim 1, wherein after sending the key factor for generating an operation code to the terminal device to generate and display the operation code, the method further comprises: receiving a successful reception of the operation code sent by the terminal device for generating the operation code. The first feedback information of the key factor of the opcode; the second feedback information for completing the binding is generated based on the first feedback information, and the second feedback information is sent to the service server; the response sent by the service server is received in For the second feedback information, an available service notification is bound, and the service notification is forwarded to the terminal device. A binding method, applied to a service server, comprises: receiving a pre-binding request sent by a network device, the pre-binding request carrying device parameter information of the network device; generating a binding based on the device parameter information beacon, send the binding beacon to the network device so that the network device generates and displays the first operation code based on the binding beacon; receives the binding request sent by the client, the binding request carries the the tie The information of the fixed beacon and the bound account, wherein the client obtains the bound beacon by scanning the first operation code displayed by the network device; obtains the device parameter information based on the bound beacon, and uses the The network device corresponding to the device parameter information is bound to the account corresponding to the account information; the key factor used to generate the operation code is generated, and the key factor is used to generate the second key factor bound to the account and the network device. Operation code; receive the first polling request sent by the network device for polling the binding result, and send the binding result information to the network device in response to the first polling request. When successful, the binding result information carries the key factor for generating the operation code to generate and display the second operation code, wherein the network device is any network device. The method according to claim 6, wherein receiving a polling request sent by the network device for polling a binding result, and sending binding result information to the network device in response to the polling request for After the second operation code is generated and displayed, the method further includes: receiving an operation request for the account sent by the network device; and performing an operation corresponding to the operation request for the account according to the binding relationship between the account and the network device. The method of claim 6, wherein the account is a payment account and the second operation code is a payment code or a collection code. The method according to claim 6, wherein receiving a polling request sent by the network device for polling a binding result, and sending binding result information to the network device in response to the polling request for After the second operation code is generated and displayed, the method further includes: receiving first feedback information sent by the network device that the account and the network device have completed binding; Notification information, and send the notification information to the network device. The method according to claim 6, wherein after the generating the key factor for generating the opcode, the method further comprises: sending the key factor for generating the opcode to the client. The method according to claim 10, wherein after sending the key factor for generating the opcode to the client, the method further comprises: receiving a second polling request sent by the client for polling the binding result, and sending binding result information to the client in response to the second polling request. A binding migration method is applied to a first service server. The method includes: receiving a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device; determining the pre-binding request Whether the requested business purpose server is the first business The service server, if the judgment result is otherwise, generates a first binding beacon based on the device parameter information, and sends the first binding beacon and the pre-binding request to the second service server as the migration destination server for causing the second service server to generate a second binding beacon based on the device parameter information and the first binding beacon; receiving a second binding beacon sent by the second service server in response to the pre-binding request , send the second binding beacon to the network device; receive the polling request sent by the network device for polling the binding result, and send the polling request to the second service server; receive The binding result information sent by the second service server in response to the polling request is sent to the network device. When the binding is successful, the binding result information carries an operation code for generating The key factor for generating an operation code is used to generate a second operation code bound to the account and the network device, wherein the network device is any network device. The method of claim 12, wherein the account is a payment account and the second operation code is a payment code or a collection code. The method according to claim 12, wherein after 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 comprises: receiving Feedback information sent by the network device to complete the binding between the account and the network device, and send the feedback information to the second service server; Receive the first notification information sent by the second service server in response to the feedback information for notifying that the binding is available, and send the first notification information to the network device. The method according to claim 12, wherein after 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 comprises: receiving An unbinding request sent by the network device to unbind the account from the network device, send the unbinding request to the second service server; receive a response sent by the second service server in response to the unbinding request The second notification information used to notify the release of the binding is sent to the network device. A binding device, applied to a client, includes: a first requester configured to send a pre-binding request to a service server, the pre-binding request carrying device parameter information and pre-binding of a pre-binding terminal device information of the bound account; the first receiver is configured to receive a binding beacon sent by the service server in response to the pre-binding request, wherein the binding beacon is based on the device parameter information and the account's information information generation; a second requester, configured to send a binding request to the service server, the binding request carrying the binding beacon; a second receiver, configured to receive a response sent by the service server in The key factor used to generate the opcode for this bind request, where the The key factor for generating the opcode is used to generate the opcode bound to the account and the terminal device; the first presenter is configured to send the key factor for generating the opcode to the terminal device to generate and display The operation code, wherein the terminal device is any terminal device. A binding device, applied to a service server, includes: a sixth receiver configured to receive a pre-binding request sent by a network device, the pre-binding request carrying device parameter information of the network device; a third generator, configured to generate a binding beacon based on the device parameter information, and send the binding beacon to the network device so that the network device generates and displays the first opcode based on the binding beacon ; a seventh receiver, configured to receive a binding request sent by the client, the binding request carrying the binding beacon and the information of the bound account, wherein the client scans the network device to display the information The first operation code obtains the binding beacon; the first binder is configured to obtain the device parameter information based on the binding beacon, and the network device corresponding to the device parameter information corresponds to the information of the account the account binding; the fourth generator is configured to generate a key factor for generating an opcode, the generating key factor is used to generate a second opcode bound to the account and the network device; an eighth receiver , configured to receive a first polling request sent by the network device for polling the binding result, and to respond to the first polling request Send the binding result information to the network device, wherein when the binding is successful, the binding result information carries the key factor used to generate the opcode to generate the second opcode and display, wherein the network A network device is any network device. A binding migration apparatus, applied to a first service server, includes: an eleventh receiver configured to receive a pre-binding request sent by a network device, the pre-binding request carrying the information of the network device device parameter information; the sixth generator is configured to determine whether the service purpose server of the pre-binding request is the first service server, and if the determination result is otherwise, a first binding beacon is generated based on the device parameter information, Sending the first binding beacon 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 service based on the device parameter information and the first binding beacon a binding beacon; a twelfth receiver, configured to receive a second binding beacon sent by the second service server in response to the pre-binding request, and send the second binding beacon to the network The thirteenth receiver is configured to receive the polling request sent by the network device for polling the binding result, and send the polling request to the second service server; the fourteenth receiver , is configured to receive the binding result information sent by the second service server in response to the polling request, and send the binding result information to the network device. When the binding is successful, the binding result information carries There is a key factor for generating an opcode, and the key factor for generating an opcode is used to generate a second opcode bound to the account and the network device, wherein the network device is any one of the network devices . A computing device includes a memory, a processor, and computer instructions stored in the memory and executable on the processor, and the processor implements the steps of the method described in any one of claim 1-15 when the processor executes the instructions. A computer-readable storage medium storing computer instructions, when executed by a processor, implements the steps of the method described in any one of claims 1-15.

Images