WO2020042823A1 - 绑定、迁移方法和装置、计算设备及存储介质 - Google Patents

绑定、迁移方法和装置、计算设备及存储介质 Download PDF

Info

Publication number
WO2020042823A1
WO2020042823A1 PCT/CN2019/096693 CN2019096693W WO2020042823A1 WO 2020042823 A1 WO2020042823 A1 WO 2020042823A1 CN 2019096693 W CN2019096693 W CN 2019096693W WO 2020042823 A1 WO2020042823 A1 WO 2020042823A1
Authority
WO
WIPO (PCT)
Prior art keywords
binding
network device
request
service server
information
Prior art date
Application number
PCT/CN2019/096693
Other languages
English (en)
French (fr)
Inventor
刘统丽
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2020042823A1 publication Critical patent/WO2020042823A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • This specification relates to the field of mobile application technology, and in particular, to a binding and migration method and device, a computing device, and a storage medium.
  • the embodiments of the present specification provide a binding and migration method and device, a computing device, and a storage medium to solve technical defects in the prior art.
  • a binding method is provided, which is applied to a client.
  • the method includes:
  • a binding method is provided, which is applied to a service server.
  • the method includes:
  • the pre-binding request carrying device parameter information of a pre-bound terminal device and information of a pre-bound account;
  • a binding method is provided, which is applied to a network device.
  • the method includes:
  • the determination result information carries a key for generating a code, which is used to generate a second operation code bound to the account and the network device;
  • the second operation code is generated and displayed according to the key generation factor.
  • a binding method is provided, which is applied to a service server, and the method includes:
  • the binding result information carries the key factor for generating the code to generate the second operation code and display it.
  • a binding method is provided, which is applied to a client.
  • the method includes:
  • a binding migration method is provided, which is applied to a network device.
  • the method includes:
  • Generating a first operation code according to the second binding token displaying the first operation code to enable a client to scan the code to obtain the second binding token to send a binding request to a second service server, and
  • the binding request carries the information of the second binding token and the bound account
  • the binding result information carries a key for generating a code.
  • the second operation code is generated and displayed according to the key generation factor.
  • a binding migration method is provided, which is applied to a first service server.
  • the method includes:
  • the pre-binding request is sent to a second service server as a migration destination server, so that the second service server generates a second binding token based on the device parameter information and a first binding token;
  • the binding result information carries A key generation factor, which is used to generate a second operation code bound to the account and the network device.
  • a binding migration method is provided and applied to a second service server.
  • the method includes:
  • the first service server Receiving a pre-binding request sent by a first service server, where the pre-binding request carries device parameter information of a pre-bound network device and a first binding token, and the first binding token is sent by the The first service server generates based on the device parameter information;
  • the binding result information carries the key factor for generating the code, and the key factor for generating the code is used to generate the key factor related to the account and the The second opcode bound to the network device.
  • a binding device is provided and applied to a client.
  • the device includes:
  • a first requester configured to send a pre-binding request to a service server, where the pre-binding request carries device parameter information of a pre-bound terminal device and information of a pre-bound account;
  • a first receiver configured to receive a binding token sent by the service server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information and the account information;
  • a second requester configured to send a binding request to the service server, where the binding request carries the binding token
  • a second receiver configured to receive a key factor for generating a code in response to the binding request sent by the service server, wherein the key factor for generating a code is used to generate a binding with the account and the terminal device Operation code
  • the first presenter is configured to send the key factor for generating the code to the terminal device to generate and display the operation code.
  • a binding device which is applied to a service server, and the device includes:
  • a third receiver configured to receive a pre-binding request sent by a client, where the pre-binding request carries device parameter information of a pre-bound terminal device and information of a pre-bound account;
  • a first generator configured to generate a binding token based on the device parameter information and the account information, and send the binding token to the client;
  • a fourth receiver configured to receive a binding request sent by the client, where the binding request carries the binding token
  • the second generator is configured to generate a key generation factor for generating an operation code bound to the account and the terminal device, and send the key generation factor to the client.
  • a binding apparatus which is applied to a network device, and the apparatus includes:
  • a third requester configured to send a pre-binding request to a service server, where the pre-binding request carries device parameter information of the network device;
  • a fourth receiver configured to receive a binding token sent by the service server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information;
  • a second presenter configured to generate a first operation code according to the binding token, and display the first operation code to enable a client to scan a code and send a binding request to the service server, where the binding request Carrying the binding token and information of the bound account;
  • a fourth requester is configured to send a polling request to poll the binding result to the service server, and receive binding result information sent by the business server in response to the polling request.
  • the binding result information carries a key for generating a code, which is used to generate a second operation code bound to the account and the network device;
  • a fifth requester configured to send a binding request to the service server, where the binding request carries the binding token
  • a fifth receiver configured to receive a key factor for generating a code in response to the binding request sent by the service server, wherein the key factor for generating a code is used to generate a binding with the account and the network device The second opcode;
  • a third presenter is configured to generate and display the second operation code according to the key generation factor.
  • a binding device which is applied to a service server, and the device includes:
  • a sixth receiver configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;
  • a third generator is configured to generate a binding token based on the device parameter information, and send the binding token to the network device so that the network device generates and displays a first token based on the binding token.
  • a seventh receiver is configured to receive a binding request sent by a client, where the binding request carries information about the binding token and a bound account, wherein the client scans the network device The displayed first operation code obtains the binding token;
  • a first binder configured to obtain the device parameter information based on the binding token, and bind the network device corresponding to the device parameter information to an account corresponding to the account information;
  • a fourth generator configured to generate a key generation factor for generating a second operation code bound to the account and the network device
  • An eighth receiver configured to receive a first polling request sent by the network device to poll a binding result, and send 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 of the raw code to generate the second operation code and display it.
  • a binding device is provided and applied to a client.
  • the device includes:
  • a scanner configured to obtain a binding token by scanning a first operation code displayed by a network device, where the binding token is used to identify identity information of the network device;
  • a sixth requester configured to send a binding request to a service server, where the binding request carries information about the binding token and the bound account;
  • the ninth receiver is configured to receive a code generation key factor sent by the service server in response to the binding request, where the code generation key factor is used to generate a first key that binds the network device and the account. Two opcodes.
  • a binding migration device which is applied to network equipment, and the device includes:
  • a seventh requester is configured to send a pre-binding request to the first service server, so that the first service server generates a first binding order based on the device parameter information of the network device carried in the pre-binding request. brand;
  • the tenth receiver is configured to receive a second binding token sent by the first service server in response to the pre-binding request, wherein the second binding token is served by a second serving as a migration destination server. Generating a service server based on the device parameter information and the first binding token sent by the first service server;
  • a fifth generator is configured to generate a first operation code according to the second binding token, and display the first operation code to enable the client to scan the code to obtain the second binding token to provide a second service.
  • the server sends a binding request, where the binding request carries information about the second binding token and the bound account;
  • An eighth requester is configured to send a polling request to the first service server to poll a binding result, and receive binding result information sent by the first service server in response to the polling request
  • the binding result information is generated by the second service server based on the polling request forwarded by the first service server, and when the binding is successful, the binding result information carries a key for generating a code
  • the key generation factor is used to generate a second operation code bound to the account and the network device;
  • a fourth presenter is configured to generate and display the second operation code according to the key generation factor.
  • a binding migration device is provided and applied to a first service server.
  • the device includes:
  • An eleventh receiver is configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;
  • a sixth generator is configured to determine whether the service destination server of the pre-binding request is the first service server, and if the determination result is otherwise, generate a first binding token based on the device parameter information, Sending the first binding token and the pre-binding request to a second service server as a migration destination server, so that the second service server generates a second binding based on the device parameter information and the first binding token Token
  • a binding migration device is provided and applied to a second service server.
  • the device includes:
  • a fifteenth receiver is configured to receive a pre-binding request sent by a first service server, where the pre-binding request carries device parameter information of a pre-bound network device and a first binding token, and A first binding token is generated by the first service server based on the device parameter information;
  • a seventh generator is configured to generate a second binding token based on the device parameter information and the first binding token, and send the second binding token to the first service server so that Sending, by the first service server, the second binding token to the network device so that the network device generates a first operation code according to the second binding token and displays it;
  • a sixteenth receiver is configured to receive a binding request sent by a client, where the binding request includes information about the second binding token and a pre-bound account, and the client scans the Acquiring the second binding token by the first operation code displayed by a network device;
  • a seventeenth receiver is configured to receive a first polling request sent by the first service server to poll a binding result, wherein the first polling request is sent by the network device to the first polling request.
  • a second binder is configured to query the binding result between the network device and the account according to the first polling request, and send the obtained binding result information to the first service server to enable all
  • the first service server sends the binding result information to the network device, and in the case of successful binding, the binding result information carries the key factor for generating the code, and the key factor for generating the code is used To generate a second operation code bound to the account and the network device.
  • a computer-readable storage medium which stores computer instructions that, when executed by a processor, implement the steps of the binding method or the binding migration method.
  • FIG. 1 is a block diagram showing a structure of a computing device 100 according to an embodiment of the present specification
  • FIG. 2 is a schematic flowchart illustrating a binding method applied to a client according to an embodiment of the present specification
  • FIG. 3 is a schematic flowchart illustrating a binding method applied to a server according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification
  • FIG. 5 is a schematic flowchart illustrating a binding method applied to a network device according to an embodiment of the present specification
  • FIG. 6 is a schematic flowchart illustrating a binding method applied to a server according to an embodiment of the present specification
  • FIG. 7 is a schematic flowchart illustrating a binding method applied to a client according to an embodiment of the present specification
  • 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 method applied to a network device according to an embodiment of the present specification.
  • 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 a binding migration method applied to a second server according to an embodiment of the present specification
  • FIG. 12 is a schematic flowchart illustrating a binding migration method according to an embodiment of the present specification.
  • FIG. 13 is a block diagram illustrating a binding device according to an embodiment of the present specification.
  • FIG. 14 is a block diagram illustrating a binding apparatus according to another embodiment of the present specification.
  • FIG. 15 is a block diagram illustrating a binding device according to still another embodiment of the present specification.
  • FIG. 16 is a block diagram illustrating a binding device according to another embodiment of the present specification.
  • FIG. 17 is a block diagram illustrating a binding apparatus according to another embodiment of the present specification.
  • FIG. 18 is a block diagram illustrating a binding migration device according to an embodiment of the present specification.
  • 19 is a block diagram showing a binding migration device according to another embodiment of the present specification.
  • FIG. 20 is a block diagram illustrating a binding apparatus according to another embodiment of the present specification.
  • FIG. 1 is a block diagram illustrating a structure of a computing device 100 according to an embodiment of the present specification.
  • the components of the computing device 100 include, but are not limited to, a memory 110 and a processor 120.
  • the processor 120 is connected to the memory 110 through a bus 130, and the database 150 is used to store user data.
  • the computing device 100 also includes an access device 140 that enables the computing device 100 to communicate via one or more networks 160.
  • 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.
  • the access device 140 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, global microwave interconnect access (Wi-MAX) interface, Ethernet interface, universal serial bus (USB) interface, cellular network interface, Bluetooth interface, near field communication (NFC) interface, and so on.
  • NIC network interface card
  • FIG. 1 the block diagram of the computing device structure shown in FIG. 1 is for the purpose of example only, and is not a limitation on the scope of this description. Those skilled in the art can add or replace other components as needed.
  • the computing device 100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet computer, personal digital assistant, laptop computer, notebook computer, netbook, etc.), a mobile phone (e.g., smartphone ), A wearable computing device (eg, a smart watch, smart glasses, etc.) or other type of mobile device, or a stationary computing device such as a desktop computer or PC.
  • the computing device 100 may also be a mobile or stationary server.
  • FIG. 2 is a schematic flowchart illustrating 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, Jingdong 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 device parameter information of the pre-bound terminal device and information of the pre-bound account.
  • the account is a payment account
  • the operation code is a payment code or a receipt code
  • the account may also be a barcode used for access control or other barcode used to identify identity information.
  • the terminal device is a Bluetooth device, such as a terminal device with a Bluetooth function, such as a wristband and a watch.
  • the pre-binding request carrying device parameter information of the pre-bound terminal device and information of the pre-bound account further includes: sending to the terminal device Sending an acquisition request to acquire device parameter information, and receiving device parameter information sent by the terminal device in response to the acquisition request.
  • the device parameters of the pre-bound terminal device can also be manually entered on the client.
  • Step 204 Receive a binding token sent by the service server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information and the account information.
  • Step 206 Send a binding request to the service server, where the binding request carries the binding token.
  • Step 208 Receive a code generation key factor sent by the service server in response to the binding request, where the code generation key factor is used to generate an operation code bound to the account and the terminal device.
  • Step 210 Send the key code generating factor to the terminal device to generate and display the operation code.
  • the method further includes: receiving the successful reception of the health code sent by the terminal device.
  • the first feedback information of the key factor of the code generating the second feedback information of the completed binding based on the first feedback information, and sending the second feedback information to the service server; and receiving the response sent by the service server in response to The second feedback information is used to notify a service notification that binding is available, and forward the service notification to the terminal device.
  • 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 a client, where the pre-binding request carries device parameter information of a pre-bound terminal device and information of a pre-bound account.
  • the account is a payment account
  • the operation code is a payment code or a receipt code
  • the account may also be a barcode used for access control or other barcode used to identify identity information.
  • the terminal device is a Bluetooth device, such as a terminal device with a Bluetooth function, such as a wristband and a watch.
  • Step 304 Generate a binding token based on the device parameter information and the account information, and send the binding token to the client.
  • Step 306 Receive a binding request sent by the client, where the binding request carries the binding token.
  • Step 308 Generate a key generating factor for generating an operation code bound to the account and the terminal device, and send the key generating factor to the client.
  • the method further includes: receiving The 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 to successfully receive the key factor for generating the code; to the client Sending a service notification that the service processing was successful in response to the second feedback information.
  • the device parameter information of the terminal device is bound to the account information of the client, and after successful binding, an operation code is generated and displayed on the terminal device according to the key factor of the code generation generated by the account's business server, thereby making the old device
  • This type of terminal device can also operate accounts like new products, which is convenient and simple and improves the user experience; it provides a convenient and secure binding process for the increasing number of smart device bindings and the replacement of old and new business account products, making new Product applications can be compatible with older devices, making it easier for older devices to use new product applications, and ensuring business ease of use and security during the evolution of new and old products.
  • FIG. 4 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification. As shown in FIG. 4, the method includes:
  • the client sends a request to the Bluetooth device to obtain the device parameters of the pre-bound Bluetooth device; the Bluetooth device sends the device parameter information to the client in response to the client's request (corresponding to step 1.1 in Figure 4);
  • 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 a pre-binding param (parameter): device parameter information and pre-binding of the Bluetooth device.
  • the account information; the service server generates a binding context token (corresponding to step 2.1 in Figure 4) according to the device parameter information of the Bluetooth device and the pre-bound account information; the service server issues a binding context token To the client (corresponding to step 2.2 in FIG.
  • the client sends a binding request to the service server, the binding request carries a binding param, and the binding param includes the binding context token and the bound account information (corresponding to the figure Step 2.3 in 4);
  • the service server verifies the received binding request, determines whether the binding request carries the binding token, and if the determination result is yes, binds the account to the Bluetooth device
  • this step is the key process of product binding (corresponding to step 2.3.1 in Figure 4); the business server returns the key factor for generating the code to the client (corresponding to step 2.3.2 in Figure 4) ;
  • the client uploads the received key-generating key factor to the Bluetooth device; the Bluetooth device returns feedback information to the client that successfully received the key-generating key factor (corresponding to step 3.1 in FIG. 4);
  • the client sends feedback information that the Bluetooth device is bound to the account to the service server; the service server performs service product availability processing (corresponding to step 4.1 in FIG. 4) according to the feedback information sent by the client, and sends it to the client Send service parameters to inform (bind) that the service processing was successful (corresponding to step 4.2 in Figure 4);
  • the client sends a notification message to the Bluetooth device that informs the success of the binding.
  • the Bluetooth device sends feedback information about the success of the reception to the client.
  • the operation code is generated and displayed according to the key factor of the raw code (corresponding to step 5.1 in Figure 4). Payment, access control and other operations.
  • FIG. 5 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, and is applied to a network device, which may be a terminal device such as a smart watch or a mobile phone having 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 device parameter information of the network device.
  • the account is a payment account
  • the operation code is a payment code or a receipt code
  • the account may also be a barcode used for access control or other barcode used to identify identity information.
  • Step 504 Receive a binding token sent by the service server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information.
  • Step 506 Generate a first operation code according to the binding token, and display the first operation code to enable the client to scan the code and send a binding request to the service server, where the binding request carries the binding Set token and bound account information.
  • Step 508 Send a polling request to poll the binding result to the business server, and receive binding result information sent by the business server in response to the polling request.
  • the binding result information carries a key for generating a code, which is used to generate a second operation code 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 token.
  • Step 512 Receive a key factor for generating a code in response to the binding request sent by the service server, wherein the key factor for generating a code is used to generate a second operation code bound to the account and the network device. .
  • Step 514 Generate and display the second operation code according to the key factor of the code generation.
  • the method further includes: sending a first feedback to the service server that the account is bound to the network device. Information; receiving notification information sent by the service server in response to the first feedback information to notify that binding is available.
  • 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 token based on the device parameter information, and send the binding token to the network device so that the network device generates and displays a first operation code based on the binding token.
  • Step 606 Receive a binding request sent by the client, where the binding request carries information about the binding token and the bound account, wherein the client scans the first
  • the account is a payment account
  • the operation code is a payment code or a receipt code.
  • the account may also be a barcode used for access control or other barcode used to identify identity information.
  • the operation code obtains the binding token.
  • Step 608 Obtain the device parameter information based on the binding token, and bind the network device corresponding to the device parameter information to an account corresponding to the account information.
  • Step 610 Generate a key generation factor for generating a code, which is used to generate a second operation code bound to the account and the network device.
  • the method further includes: sending the key factor for generating a code to the client.
  • Step 612 Receive a first polling request sent by the network device to poll a binding result, and send binding result information to the network device in response to the first polling request.
  • the binding result information carries the key for generating the code to generate the second operation code and display it.
  • the method further includes: receiving an operation request for the account sent by the network device; and performing the operation request corresponding to the account according to a binding relationship between the account and the network device. Operation.
  • the method further includes: receiving first feedback information from the network device that the account and the network device have completed binding; and generating, in response to the first feedback information, a notification that binding is available Sending the notification information to the network device.
  • the method further includes:
  • FIG. 7 is a schematic flowchart illustrating 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, Jingdong Wallet, Baidu Wallet, and the like.
  • the method includes steps 702 to 706.
  • Step 702 Obtain a binding token by scanning a first operation code displayed on the network device, where the binding token is used to identify identity information of the network device.
  • Step 704 Send a binding request to the service server, where the binding request carries information about the binding token and the bound account.
  • the account is a payment account
  • the operation code is a payment code or a receipt code
  • the account may also be a barcode used for access control or other barcode used to identify identity information.
  • Step 706 Receive a code generation key factor sent by the service server in response to the binding request, where the code generation key factor is used to generate a second operation code for binding the network device and the account.
  • the method further includes: sending to the service server to poll the network device and the account. A polling request for a binding result; receiving binding result notification information sent by the service server in response to the polling request.
  • the device parameter information of the terminal device is bound to the account information of the client, and after successful binding, an operation code is generated and displayed on the terminal device according to the key factor of the code generation generated by the account's business server, thereby making the old device
  • This type of terminal device can also operate accounts like new products, which is convenient and simple and improves the user experience; it provides a convenient and secure binding process for the increasing number of smart device bindings and the replacement of old and new business account products, making new Product applications can be compatible with older devices, making it easier for older devices to use new product applications, and ensuring business ease of use and security during the evolution of new and old products.
  • FIG. 8 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification. As shown in FIG. 8, the method includes:
  • the network device sends a pre-binding request to the service server, uploading the device parameter information param of the network device; the service server generates a binding context token (token) according to the device parameter information of the network device (corresponding to step 1.1 in FIG. 8), And return the binding context token to the network device (corresponding to step 1.2 in FIG. 8); the network device generates a binding two-dimensional code according to the received binding context token (corresponding to step 1.3 in FIG. 8);
  • the client scans the binding QR code to obtain a binding context token (corresponding to step 2.1 in FIG. 8);
  • the client sends a binding request to the service server, where the binding request includes the binding context token and information about the pre-bound account; the service server verifies the received binding request, and determines whether the binding request is in progress. Whether the binding context token is carried, and if the determination result is yes, bind the account to the network device to generate a key factor for generating a code, this step is a key process of product binding (corresponding to step 3.1 in FIG. 8) ); The service server returns the key factor to the client (corresponding to step 3.2 in FIG. 8);
  • the network device After generating the binding QR code, the network device starts to send a polling request to the business server to check whether the binding is successful.
  • the business server queries the binding result in response to the polling request (corresponding to FIG. 8).
  • Step 4.1) sending the binding result information obtained from the query to the network device, wherein when the binding is successful, the binding result information carries a key for generating a code (corresponding to step 4.2 in FIG. 8), the code generating The key factor is used to generate an operation code bound to the account and the network device; after receiving the key generating factor, the network device sends a feedback to the service server that the network device is bound to the account.
  • Information (corresponding to step 4.3 in FIG. 8); the service server performs service product availability processing (corresponding to step 4.3.1 in FIG.
  • the network device According to the feedback information sent by the network device, and issues business parameters to the network device to inform (bind) the business processing Success (corresponding to step 4..3.2 in FIG. 8); the network device generates an operation code based on the key factors of the generated raw code and displays it (corresponding to step 4.3.3 in FIG. 8), and can perform payments, access control and other industries Service operation
  • the client sends a polling request to the business server to query whether the binding is successful.
  • the business server queries the binding result in response to the polling request (corresponding to step 5.1 in FIG. 8), and binds the obtained binding to the query.
  • the result information is sent to the client corresponding to step 5.2) in Figure 8.
  • 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 token based on the device parameter information of the network device carried in the pre-binding request.
  • Step 904 Receive a second binding token sent by the first service server in response to the pre-binding request, wherein the second binding token is based on the second service server serving as a migration destination server based on the The device parameter information and the first binding token sent by the first service server are generated.
  • Step 906 Generate a first operation code according to the second binding token, and display the first operation code to enable the client to scan the code to obtain the second binding token to send a binding request to the second service server.
  • the binding request carries information about the second binding token and the bound account.
  • the account is a payment account
  • the operation code is a payment code or a receipt code
  • the account may also be a barcode used for access control or other barcode used to identify identity information.
  • Step 908 Send a polling request to poll the binding result to the first service server, and receive binding result information in response to the polling request sent by the first service server, wherein the The binding result information is generated by the second service server based on the polling request forwarded by the first service server.
  • the binding result information carries a key for generating a code, and the code is generated.
  • the key factor is used to generate a second operation code bound to the account and the network device.
  • Step 910 Generate and display the second operation code according to the key factor of the code generation.
  • the account is a payment account
  • the second operation code is a payment code or a payment code
  • the method further includes: sending feedback to the first service server that the account is bound to the network device. Information; receiving first notification information sent by the first service server in response to the feedback information to notify that binding is available, wherein the first notification information is based on the first service by the second service server The feedback information forwarded by the server is generated.
  • the method further includes: sending a solution for unbinding the account from the network device to the first service server.
  • a binding request ; receiving second notification information sent by the first service server in response to the unbinding request to notify the release of binding, wherein the second notification information is based on the first service server by the second service server
  • the unbinding request forwarded by a service server is generated.
  • FIG. 10 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification, which is applied to a 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 determination result is otherwise, generate a first binding token based on the device parameter information, and change the first binding order Sending the card and the pre-binding request to a second service server as a migration destination server, so that the second service server generates a second binding token based on the device parameter information and a first binding token;
  • Step 1006 Receive a second binding token sent by the second service server in response to the pre-binding request, and send the second binding token to the network device.
  • Step 1008 Receive a polling request sent by the network device to poll a 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.
  • the binding result information carries a key for generating a code, which is used to generate a second operation code bound to the account and the network device.
  • the account is a payment account
  • the operation code is a payment code or a receipt code
  • the account may also be a barcode used for access control or other barcode used to identify identity information.
  • the method further includes: receiving the binding result information.
  • the feedback information that the account and the network device have completed binding sent by the network device sends the feedback information to the second service server; and receives the response information sent by the second service server in response to the feedback information. It is used to notify the first notification information that the binding is available, and send the first notification information to the network device.
  • the method further includes: receiving the binding result information.
  • the second notification information used for the binding request to notify the release of the binding is sent to the network device.
  • 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 a first service server, where the pre-binding request carries device parameter information of a pre-bound network device and a first binding token, and the first binding token Generated by the first service server based on the device parameter information.
  • Step 1104 Generate a second binding token based on the device parameter information and the first binding token, and send the second binding token to the first service server to enable the first service
  • the server sends the second binding token to the network device, so that the network device generates a first operation code according to the second binding token and displays it.
  • Step 1106 Receive a binding request sent by a client, where the binding request includes information about the second binding token and a pre-bound account, and the client scans the network device to display the A first operation code obtains the second binding token.
  • Step 1108 Determine whether the binding request includes the second binding token, and if the determination result is yes, bind the account to the network device, generate a key factor for generating a code according to the binding result, and To the client.
  • Step 1110 Receive a first polling request sent by the first service server to poll a binding result, wherein the first polling request is sent by the network device to the first service server.
  • the queried binding result information is sent to the first service server to enable the first
  • the method further includes: receiving feedback information about binding the account and the network device sent by the first service server, where the feedback information is provided by Generating by the network device; generating first notification information for notifying binding availability according to the feedback information, and sending the first notification information to the first service server to cause the first service server to send the first service server The first notification information is sent to the network device.
  • the queried binding result information is sent to the first service server to enable the first service.
  • the method further includes: receiving a unbinding request sent by the first service server to unbind the account from the network device, where the unbinding request is provided by Generating and sending the network device to the first service server; unbinding the account from the network device according to the unbinding request, generating second notification information for notifying the unbinding; Sending second notification information to the first service server, so that the first service server sends the second notification information to the network device.
  • the method further includes: receiving a second polling request sent by the client to poll a binding result; and according to the second polling request Querying the binding result between the network device and the account, and sending the found binding result information to the client, wherein in the case of successful binding, the binding result information carries the birth code Key factors.
  • the device parameter information of the terminal device is bound to the account information of the client, and after successful binding, an operation code is generated and displayed on the terminal device according to the key factor of the code generation generated by the account's business server, thereby making the old device
  • This type of terminal device can also operate accounts like new products, which is convenient and simple and improves the user experience; it provides a convenient and secure binding process for the increasing number of smart device bindings and the replacement of old and new business account products, making new Product applications can be compatible with older devices, making it easier for older devices to use new product applications, and ensuring business ease of use and security during the evolution of new and old products.
  • FIG. 12 is a schematic flowchart illustrating a binding method according to an embodiment of the present specification. As shown in FIG. 12, the method includes:
  • the network device sends a pre-binding request to the service server A, uploading the device parameter information param of the network device; the service server generates a binding context token (token) according to the device parameter information of the network device (corresponding to step 1.1 in FIG. 8) And sends the binding context token and the device parameter information of the network device to the service server B (corresponding to step 1.2 in FIG. 12); the service server B generates a binding of the specified token according to the received binding context token and device parameter information Context (corresponding to step 1.2.1 in FIG. 12); business server B returns the binding context token of the specified token to business server A (corresponding to step 1.2.2 in FIG. 12); business server A returns the binding context of the specified token To network equipment (corresponding to step 1.2.3 in Figure 12);
  • the network device generates a binding QR code according to the received binding context of the specified token
  • the client scans the binding QR code to obtain a binding context token (corresponding to step 3.1 in FIG. 12);
  • the client sends a binding request to the service server B, where the binding request includes the binding context token and information of the pre-bound account; the service server B verifies the received binding request and determines the binding Whether the request carries the binding context token, and if the determination result is yes, bind the account with the network device to generate a key factor for generating a code.
  • This step is a key process of product binding (corresponding to FIG. 12).
  • Step 4.1) the service server B returns the key factor of the code generation to the client (corresponding to step 4.2 in FIG. 8);
  • the network device starts sending a polling request to the business server A to query whether the binding migration is successful.
  • the business server A forwards the polling request to the business server B (corresponding to the step in FIG. 12).
  • service server B queries the binding result in response to the polling request (corresponding to step 5.1.1 in FIG. 12), and sends the binding result information obtained by the query to service server A (corresponding to step 5.1 in FIG. 12) .2)
  • service server A forwards the binding result information to the network device, and marks the forwarding flag bit as forwarding (corresponding to step 5.1.4 in FIG. 12), wherein when the binding is successful, the binding result information Carrying a key for generating a code, which is used to generate an operation code bound to the account and the network device;
  • the network device After receiving the key generation factor, the network device sends feedback information to the service server A that the network device is bound to the account; service server A forwards the forwarding flag bit (corresponding to FIG. 12).
  • Step 6.1 forward the completed binding feedback information to service server B (corresponding to step 6.2 in FIG. 12); service server B performs service product availability processing according to the feedback information (corresponding to step 6.2.1 in FIG. 12)
  • service server A sends a notification of successful service processing to the network device (corresponding to step in FIG. 12) 6.2.3);
  • the network device generates and displays the operation code according to the key factors of the received code, and can perform payment, door access control and other business operations;
  • the client sends a polling request to the business server B to query whether the binding is successful, and the business server B queries the binding result in response to the polling request (corresponding to step 8.1 in FIG. 12),
  • the binding result information is sent to the client (corresponding to step 8.2 in FIG. 12);
  • the service server B unbinds the account from the network device according to the unbinding request, generates notification information for notifying the unbinding and sends the notification information to the service server A (corresponding to step 9.2 in FIG. 12); the service server A forwards the notification information of the unbinding result to the network device (corresponding to step 9.3 in FIG. 12).
  • this specification also provides embodiments of the binding device and the binding migration device.
  • the device embodiments can be implemented by software, or by hardware or a combination of software and hardware. .
  • software implementation as an example, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the device in which it is located.
  • a hardware structure of the binding device and the binding migration device in this specification may include a processor, a network interface, a memory, and a non-volatile memory. According to the actual function, other hardware may also be included, which will not be repeated here.
  • the binding device 1300 corresponds to the embodiment shown in FIG. 2.
  • the device 1300 includes:
  • the first requester 1302 is configured to send a pre-binding request to a service server, where the pre-binding request carries device parameter information of a pre-bound terminal device and information of a pre-bound account;
  • the first receiver 1304 is configured to receive a binding token sent by the service server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information and the account information ;
  • a second requester 1306, configured to send a binding request to the service server, where the binding request carries the binding token
  • the second receiver 1308 is configured to receive a key factor for generating a code in response to the binding request sent by the service server, wherein the key factor for generating a code is used to generate a key for binding with the account and the terminal device.
  • a first presenter 1310 is configured to send the key factor for generating a code to the terminal device to generate and display the operation code.
  • the terminal device is a Bluetooth device.
  • the account is a payment account
  • the operation code is a payment code or a payment code
  • the binding device 1400 corresponds to the embodiment shown in FIG. 3, and the device 1400 includes:
  • the third receiver 1402 is configured to receive a pre-binding request sent by a client, where the pre-binding request carries device parameter information of a pre-bound terminal device and information of a pre-bound account;
  • a first generator 1404 configured to generate a binding token based on the device parameter information and the account information, and send the binding token to the client;
  • a fourth receiver 1406 is configured to receive a binding request sent by the client, where the binding request carries the binding token
  • the second generator 1408 is configured to generate a key generation factor for generating an operation code bound to the account and the terminal device, and send the key generation factor to the client.
  • the terminal device is a Bluetooth device.
  • the binding device 1500 is a block diagram of a binding apparatus according to an embodiment of the present specification.
  • the binding device 1500 corresponds to the embodiment shown in FIG. 5.
  • the device 1500 includes:
  • the third requester 1502 is configured to send a pre-binding request to a service server, where the pre-binding request carries device parameter information of the network device;
  • the fourth receiver 1504 is configured to receive a binding token sent by the service server in response to the pre-binding request, wherein the binding token is generated based on the device parameter information;
  • the second presenter 1506 is configured to generate a first operation code according to the binding token, and display the first operation code to enable a client to scan a code and send a binding request to the service server.
  • the binding The request carries information about the binding token and the bound account;
  • the fourth requester 1508 is configured to send a polling request to the service server to poll the binding result, and receive binding result information sent by the service server in response to the polling request, where: When the binding is successful, the binding result information carries a key for generating a code, which is used to generate a second operation code bound to the account and the network device;
  • a fifth requester 1510 is configured to send a binding request to the service server, where the binding request carries the binding token;
  • a fifth receiver 1512 is configured to receive a key factor for generating a code in response to the binding request sent by the service server, where the key factor for generating a code is used to generate a binding factor with the account and the network device.
  • the third presenter 1514 is configured to generate and display the second operation code according to the key generation factor.
  • the account is a payment account
  • the second operation code is a payment code or a receipt code
  • the binding device 1600 corresponds to the embodiment shown in FIG. 6.
  • the device 1600 includes:
  • a sixth receiver 1602 is configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;
  • a third generator 1604 is configured to generate a binding token based on the device parameter information, and send the binding token to the network device so that the network device generates and displays the binding token based on the binding token.
  • a seventh receiver 1606 is configured to receive a binding request sent by a client, where the binding request carries information of the binding token and a bound account, wherein the client scans the network by Acquiring the binding token by the first operation code displayed by the device;
  • the first binder 1608 is configured to obtain the device parameter information based on the binding token, and bind the network device corresponding to the device parameter information and an account corresponding to the account information;
  • a fourth generator 1610 is configured to generate a key generating factor for generating a second operation code bound to the account and the network device;
  • An eighth receiver 1612 is configured to receive a first polling request sent by the network device to poll a binding result, and send binding result information to the network in response to the first polling request.
  • a device wherein when the binding is successful, the binding result information carries the key for generating a code to generate the second operation code and display it.
  • the binding device 1700 corresponds to the embodiment shown in FIG. 7.
  • the device 1700 includes:
  • the scanner 1702 is configured to obtain a binding token by scanning a first operation code displayed on a network device, where the binding token is used to identify identity information of the network device;
  • a sixth requester 1704 is configured to send a binding request to a service server, where the binding request carries information about the binding token and the bound account;
  • the ninth receiver 1706 is configured to receive a key factor for generating a code in response to the binding request sent by the service server, where the key factor for generating a code is used to generate a key for binding the network device and the account.
  • the second opcode is configured to generate a key factor for generating a code in response to the binding request sent by the service server, where the key factor for generating a code is used to generate a key for binding the network device and the account.
  • the binding migration device 1800 corresponds to the embodiment shown in FIG. 9.
  • the device 1800 includes:
  • a seventh requester 1802 is configured to send a pre-binding request to the first service server, so that the first service server generates a first binding based on the device parameter information of the network device carried in the pre-binding request.
  • a tenth receiver 1804 is configured to receive a second binding token sent by the first service server in response to the pre-binding request, wherein the second binding token is sent by the first server serving as a migration destination server. Generating two service servers based on the device parameter information and the first binding token sent by the first service server;
  • a fifth generator 1806 is configured to generate a first operation code according to the second binding token, and display the first operation code to enable a client to scan the code to obtain the second binding token to the second
  • the service server sends a binding request, where the binding request carries information about the second binding token and the bound account;
  • An eighth requester 1808 is configured to send a polling request to the first service server to poll a binding result, 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 a key for generating a code A factor, the key for generating a code is used to generate a second operation code bound to the account and the network device;
  • a fourth presenter 1810 is configured to generate and display the second operation code according to the key generation factor.
  • the account is a payment account
  • the second operation code is a payment code or a receipt code
  • the binding migration device 1900 corresponds to the embodiment shown in FIG. 10 and is applied to a first service server.
  • the device 1900 includes:
  • An eleventh receiver 1902 is configured to receive a pre-binding request sent by a network device, where the pre-binding request carries device parameter information of the network device;
  • a sixth generator 1904 is configured to determine whether the service destination server of the pre-binding request is the first service server, and if the determination result is otherwise, generate a first binding token based on the device parameter information, The first binding token and the pre-binding request are sent to a second service server as a migration destination server, so that the second service server generates a second binding based on the device parameter information and the first binding token.
  • a twelfth receiver 1906 is configured to receive a second binding token sent by the second service server in response to the pre-binding request, and send the second binding token to the network device. ;
  • a thirteenth receiver 1908 is configured to receive a polling request sent by the network device to poll a binding result, and send the polling request to the second service server;
  • a fourteenth receiver 1910 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.
  • the binding result information carries a key for generating a code
  • the key for generating a code is used to generate a second operation code bound to the account and the network device.
  • the binding migration device 2000 corresponds to the embodiment shown in FIG. 11 and is applied to a second service server.
  • the device 2000 includes:
  • a fifteenth receiver 2002 is configured to receive a pre-binding request sent by a first service server, where the pre-binding request carries device parameter information of a pre-bound network device and a first binding token, so The first binding token is generated by the first service server based on the device parameter information;
  • a seventh generator 2004 is configured to generate a second binding token based on the device parameter information and the first binding token, and send the second binding token to the first service server to Causing the first service server to send the second binding token to the network device so that the network device generates a first operation code according to the second binding token and displays it;
  • the sixteenth receiver 2006 is configured to receive a binding request sent by a client, where the binding request includes information about the second binding token and a pre-bound account, and the client scans all addresses Acquiring the second binding token by the first operation code displayed by the network device;
  • the determiner 2008 is configured to determine whether the binding request includes the second binding token, and if the determination result is yes, bind the account to the network device, and generate a health account based on the binding result. Code a key factor and send it to the client;
  • a seventeenth receiver 2010 is configured to receive a first polling request sent by the first service server to poll a binding result, wherein the first polling request is sent by the network device to the First service server;
  • the second binder 2012 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 Sending, by the first service server, the binding result information to the network device, and in the case of successful binding, the binding result information carries the code generation key factor, and the code generation key factor To generate a second operation code bound to the account and the network device.
  • the device, module, or unit described in the foregoing embodiments may be specifically implemented by a computer chip or entity, or may be implemented by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop 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 Desk, tablet computer, wearable device, or a combination of any of these devices.
  • the relevant part may refer to the description of the method embodiment.
  • the device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, may be located One place, or it can be distributed across 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 without creative efforts.
  • An embodiment of the present specification also provides a computing device including a memory, a processor, and computer instructions stored on the memory and executable on the processor, and the processor implements the binding method when the instruction is executed, Bind the steps of the migration method.
  • An embodiment of the present specification also provides a computer-readable storage medium that stores computer instructions that implement the steps of the binding method and the binding migration method when the instructions are executed by a processor.
  • the computer instructions include computer program code, and the computer program code may be in a source code form, an object code form, an executable file, or some intermediate form.
  • the computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electric carrier signals, telecommunication signals, and software distribution media. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdictions. For example, in some jurisdictions, the computer-readable medium Excludes electric carrier signals and telecommunication signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Packaging For Recording Disks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本说明书提供一种绑定、迁移方法和装置、计算设备及存储介质，其中绑定方法包括：向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息和所述账户的信息生成；向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述终端设备绑定的操作码；将所述生码关键因子发送至所述终端设备以生成并展示所述操作码。

Description

绑定、迁移方法和装置、计算设备及存储介质 技术领域
本说明书涉及移动应用技术领域，特别涉及一种绑定、迁移方法和装置、计算设备及存储介质。
背景技术
当前智能设备层出不穷，支付产品不断产生和升级，而设备绑定、产品维护缺少规范化的流程，给日常接入工作带了很大的不便，用户体验不佳。
发明内容
有鉴于此，本说明书实施例提供了一种绑定、迁移方法和装置、计算设备及存储介质，以解决现有技术中存在的技术缺陷。
根据本说明书实施例的第一方面，提供了一种绑定方法，应用于客户端，所述方法包括：
向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息和所述账户的信息生成；
向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述终端设备绑定的操作码；
将所述生码关键因子发送至所述终端设备以生成并展示所述操作码。
根据本说明书实施例的第二方面，提供了一种绑定方法，应用于业务服务器，所述方法包括：
接收客户端发送的预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
基于所述设备参数信息和所述账户的信息生成绑定令牌，并向所述客户端发送所述 绑定令牌；
接收所述客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌；
生成用以生成与所述账户和所述终端设备绑定的操作码的生码关键因子，并将所述生码关键因子发送给所述客户端。
根据本说明书实施例的第三方面，提供了一种绑定方法，应用于网络设备，所述方法包括：
向业务服务器发送预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息生成；
根据所述绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码并向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息；
向所述业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
根据所述生码关键因子生成并展示所述第二操作码。
根据本说明书实施例的第四方面，提供了一种绑定方法，应用于业务服务器，所述方法包括：
接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
基于所述设备参数信息生成绑定令牌，将所述绑定令牌发送给所述网络设备以使所述网络设备基于所述绑定令牌生成并显示第一操作码；
接收客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信 息，其中，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述绑定令牌；
基于所述绑定令牌得到所述设备参数信息，将所述设备参数信息对应的所述网络设备和所述账户的信息对应的账户绑定；
生成生码关键因子，所述生成关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
接收所述网络设备发送的用以轮询绑定结果的第一轮询请求，以及响应于所述第一轮询请求将绑定结果信息发送给所述网络设备，其中，当绑定成功时，所述绑定结果信息携带有所述生码关键因子以生成所述第二操作码并展示。
根据本说明书实施例的第五方面，提供了一种绑定方法，应用于客户端，所述方法包括：
通过扫描网络设备显示的第一操作码获取绑定令牌，所述绑定令牌用以标识所述网络设备的身份信息；
向业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息；
接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中所述生码关键因子用以生成绑定所述网络设备和所述账户的第二操作码。
根据本说明书实施例的第六方面，提供了一种绑定迁移方法，应用于网络设备，所述方法包括：
向第一业务服务器发送预绑定请求，以使所述第一业务服务器基于所述预绑定请求携带的所述网络设备的设备参数信息生成第一绑定令牌；
接收所述第一业务服务器发送的响应于所述预绑定请求的第二绑定令牌，其中所述第二绑定令牌由作为迁移目的服务器的第二业务服务器基于所述第一业务服务器发送的所述设备参数信息和第一绑定令牌生成；
根据所述第二绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码获取所述第二绑定令牌以向第二业务服务器发送绑定请求，所述绑定请求携带有所述第二绑定令牌和绑定的账户的信息；
向所述第一业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述第一业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，所述绑定结果信息由所述第 二业务服务器基于所述第一业务服务器转发的所述轮询请求生成，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
根据所述生码关键因子生成并展示所述第二操作码。
根据本说明书实施例的第七方面，提供了一种绑定迁移方法，应用于第一业务服务器，所述方法包括：
接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
判断所述预绑定请求的业务目的服务器是否是所述第一业务服务器，如果判断结果为否则基于所述设备参数信息生成第一绑定令牌，将所述第一绑定令牌和所述预绑定请求发送给作为迁移目的服务器的第二业务服务器以使所述第二业务服务器基于所述设备参数信息和第一绑定令牌生成第二绑定令牌；
接收所述第二业务服务器发送的响应于所述预绑定请求的第二绑定令牌，将所述第二绑定令牌发送给所述网络设备；
接收所述网络设备发送的用以轮询绑定结果的轮询请求，将所述轮询请求发送给所述第二业务服务器；
接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
根据本说明书实施例的第八方面，提供了一种绑定迁移方法，应用于第二业务服务器，所述方法包括：
接收第一业务服务器发送的预绑定请求，其中所述预绑定请求携带有预绑定的网络设备的设备参数信息和第一绑定令牌，所述第一绑定令牌由所述第一业务服务器基于所述设备参数信息生成；
基于所述设备参数信息和所述第一绑定令牌生成第二绑定令牌；
将所述第二绑定令牌发送给所述第一业务服务器以使所述第一业务服务器将所述第二绑定令牌发送给所述网络设备以使所述网络设备根据所述第二绑定令牌生成第一操作码并展示；
接收客户端发送的绑定请求，其中所述绑定请求包括所述第二绑定令牌和预绑定的账户的信息，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述第二绑定令牌；
判断所述绑定请求是否包含有所述第二绑定令牌，若判断结果为是则将所述账户与所述网络设备进行绑定，根据绑定结果生成生码关键因子并发送给所述客户端；
接收所述第一业务服务器发送的用以轮询绑定结果的第一轮询请求，其中所述第一轮询请求由所述网络设备发送给所述第一业务服务器；
根据所述第一轮询请求查询所述网络设备与所述账户的绑定结果，将查询到的绑定结果信息发送给所述第一业务服务器以使所述第一业务服务器将所述绑定结果信息发送给所述网络设备，其中在绑定成功的情况下，所述绑定结果信息携带有所述生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
根据本说明书实施例的第九方面，提供了一种绑定装置，应用于客户端，所述装置包括：
第一请求器，被配置为向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
第一接收器，被配置为接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息和所述账户的信息生成；
第二请求器，被配置为向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
第二接收器，被配置为接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述终端设备绑定的操作码；
第一展示器，被配置为将所述生码关键因子发送至所述终端设备以生成并展示所述操作码。
根据本说明书实施例的第十方面，提供了一种绑定装置，应用于业务服务器，所述装置包括：
第三接收器，被配置为接收客户端发送的预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
第一生成器，被配置为基于所述设备参数信息和所述账户的信息生成绑定令牌，并 向所述客户端发送所述绑定令牌；
第四接收器，被配置为接收所述客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌；
第二生成器，被配置为生成用以生成与所述账户和所述终端设备绑定的操作码的生码关键因子，并将所述生码关键因子发送给所述客户端。
根据本说明书实施例的第十一方面，提供了一种绑定装置，应用于网络设备，所述装置包括：
第三请求器，被配置为向业务服务器发送预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
第四接收器，被配置为接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息生成；
第二展示器，被配置为根据所述绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码并向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息；
第四请求器，被配置为向所述业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第五请求器，被配置为向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
第五接收器，被配置为接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第三展示器，被配置为根据所述生码关键因子生成并展示所述第二操作码。
根据本说明书实施例的第十二方面，提供了一种绑定装置，应用于业务服务器，所述装置包括：
第六接收器，被配置为接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
第三生成器，被配置为基于所述设备参数信息生成绑定令牌，将所述绑定令牌发送 给所述网络设备以使所述网络设备基于所述绑定令牌生成并显示第一操作码；
第七接收器，被配置为接收客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息，其中，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述绑定令牌；
第一绑定器，被配置为基于所述绑定令牌得到所述设备参数信息，将所述设备参数信息对应的所述网络设备和所述账户的信息对应的账户绑定；
第四生成器，被配置为生成生码关键因子，所述生成关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第八接收器，被配置为接收所述网络设备发送的用以轮询绑定结果的第一轮询请求，以及响应于所述第一轮询请求将绑定结果信息发送给所述网络设备，其中，当绑定成功时，所述绑定结果信息携带有所述生码关键因子以生成所述第二操作码并展示。
根据本说明书实施例的第十三方面，提供了一种绑定装置，应用于客户端，所述装置包括：
扫描器，被配置为通过扫描网络设备显示的第一操作码获取绑定令牌，所述绑定令牌用以标识所述网络设备的身份信息；
第六请求器，被配置为向业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息；
第九接收器，被配置为接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中所述生码关键因子用以生成绑定所述网络设备和所述账户的第二操作码。
根据本说明书实施例的第十四方面，提供了一种绑定迁移装置，应用于网络设备，所述装置包括：
第七请求器，被配置为向第一业务服务器发送预绑定请求，以使所述第一业务服务器基于所述预绑定请求携带的所述网络设备的设备参数信息生成第一绑定令牌；
第十接收器，被配置为接收所述第一业务服务器发送的响应于所述预绑定请求的第二绑定令牌，其中所述第二绑定令牌由作为迁移目的服务器的第二业务服务器基于所述第一业务服务器发送的所述设备参数信息和第一绑定令牌生成；
第五生成器，被配置为根据所述第二绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码获取所述第二绑定令牌以向第二业务服务器发送绑定请求，所述绑定 请求携带有所述第二绑定令牌和绑定的账户的信息；
第八请求器，被配置为向所述第一业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述第一业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，所述绑定结果信息由所述第二业务服务器基于所述第一业务服务器转发的所述轮询请求生成，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第四展示器，被配置为根据所述生码关键因子生成并展示所述第二操作码。
根据本说明书实施例的第十五方面，提供了一种绑定迁移装置，应用于第一业务服务器，所述装置包括：
第十一接收器，被配置为接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
第六生成器，被配置为判断所述预绑定请求的业务目的服务器是否是所述第一业务服务器，如果判断结果为否则基于所述设备参数信息生成第一绑定令牌，将所述第一绑定令牌和所述预绑定请求发送给作为迁移目的服务器的第二业务服务器以使所述第二业务服务器基于所述设备参数信息和第一绑定令牌生成第二绑定令牌；
第十二接收器，被配置为接收所述第二业务服务器发送的响应于所述预绑定请求的第二绑定令牌，将所述第二绑定令牌发送给所述网络设备；
第十三接收器，被配置为接收所述网络设备发送的用以轮询绑定结果的轮询请求，将所述轮询请求发送给所述第二业务服务器；
第十四接收器，被配置为接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
根据本说明书实施例的第十六方面，提供了一种绑定迁移装置，应用于第二业务服务器，所述装置包括：
第十五接收器，被配置为接收第一业务服务器发送的预绑定请求，其中所述预绑定请求携带有预绑定的网络设备的设备参数信息和第一绑定令牌，所述第一绑定令牌由所述第一业务服务器基于所述设备参数信息生成；
第七生成器，被配置为基于所述设备参数信息和所述第一绑定令牌生成第二绑定令牌，将所述第二绑定令牌发送给所述第一业务服务器以使所述第一业务服务器将所述第二绑定令牌发送给所述网络设备以使所述网络设备根据所述第二绑定令牌生成第一操作码并展示；
第十六接收器，被配置为接收客户端发送的绑定请求，其中所述绑定请求包括所述第二绑定令牌和预绑定的账户的信息，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述第二绑定令牌；
判断器，被配置为判断所述绑定请求是否包含有所述第二绑定令牌，若判断结果为是则将所述账户与所述网络设备进行绑定，根据绑定结果生成生码关键因子并发送给所述客户端；
第十七接收器，被配置为接收所述第一业务服务器发送的用以轮询绑定结果的第一轮询请求，其中所述第一轮询请求由所述网络设备发送给所述第一业务服务器；
第二绑定器，被配置为根据所述第一轮询请求查询所述网络设备与所述账户的绑定结果，将查询到的绑定结果信息发送给所述第一业务服务器以使所述第一业务服务器将所述绑定结果信息发送给所述网络设备，其中在绑定成功的情况下，所述绑定结果信息携带有所述生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
根据本说明书实施例的第十七方面，提供了一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，所述处理器执行所述指令时实现所述的绑定方法或绑定迁移方法的步骤。
根据本说明书实施例的第十八方面，提供了一种计算机可读存储介质，其存储有计算机指令，该指令被处理器执行时实现所述的绑定方法或绑定迁移方法的步骤。
本说明书实施例通过将终端设备的设备参数信息与客户端的账户信息进行绑定，在成功绑定后根据账户的业务服务器生成的生码关键因子在终端设备上生成操作码并展示，从而使得旧款的终端设备也可以像新款产品一样对账户进行操作，方便简单，提升了用户体验；为日益增多的智能设备绑定及业务账户产品的新老更替提供便捷、安全的绑定流程，使得新产品应用可以兼容老设备，方便老设备使用新产品应用，保证新老产品演进过程中的业务易用性和安全性。
附图说明
为了更清楚地说明本说明书实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是示出了根据本说明书一实施例的计算设备100的结构框图；
图2是示出了本说明书一实施例的应用于客户端的绑定方法的流程示意图；
图3是示出了本说明书一实施例的应用于服务器的绑定方法的流程示意图；
图4是示出了本说明书一实施例的绑定方法的流程示意图；
图5是示出了本说明书一实施例的应用于网络设备的绑定方法的流程示意图；
图6是示出了本说明书一实施例的应用于服务器的绑定方法的流程示意图；
图7是示出了本说明书一实施例的应用于客户端的绑定方法的流程示意图；
图8是示出了本说明书另一实施例的绑定方法的流程示意图；
图9是示出了本说明书一实施例的应用于网络设备的绑定迁移方法的流程示意图；
图10是示出了本说明书一实施例的应用于第一服务器的绑定迁移方法的流程示意图；
图11是示出了本说明书一实施例的应用于第二服务器的绑定迁移方法的流程示意图；
图12是示出了本说明书一实施例的绑定迁移方法的流程示意图；
图13是示出了本说明书一实施例的绑定装置的模块图；
图14是示出了本说明书另一实施例的绑定装置的模块图；
图15是示出了本说明书再一实施例的绑定装置的模块图；
图16是示出了本说明书又一实施例的绑定装置的模块图；
图17是示出了本说明书另一实施例的绑定装置的模块图；
图18是示出了本说明书一实施例的绑定迁移装置的模块图；
图19是示出了本说明书另一实施例的绑定迁移装置的模块图；
图20是示出了本说明书又一实施例的绑定装置的模块图。
具体实施方式
在下面的描述中阐述了很多具体细节以便于充分理解本说明书。但是本说明书能够以很多不同于在此描述的其它方式来实施，本领域技术人员可以在不违背本说明书内涵的情况下做类似推广，因此本说明书不受下面公开的具体实施的限制。
图1是示出了根据本说明书一实施例的计算设备100的结构框图。该计算设备100的部件包括但不限于存储器110和处理器120。处理器120与存储器110通过总线130相连接，数据库150用于保存用户数据。
计算设备100还包括接入设备140，接入设备140使得计算设备100能够经由一个或多个网络160通信。这些网络的示例包括公用交换电话网(PSTN)、局域网(LAN)、广域网(WAN)、个域网(PAN)或诸如因特网的通信网络的组合。接入设备140可以包括有线或无线的任何类型的网络接口(例如，网络接口卡(NIC))中的一个或多个，诸如IEEE802.11无线局域网(WLAN)无线接口、全球微波互联接入(Wi-MAX)接口、以太网接口、通用串行总线(USB)接口、蜂窝网络接口、蓝牙接口、近场通信(NFC)接口，等等。
在本说明书的一个实施例中，计算设备100的上述以及图1中未示出的其他部件也可以彼此相连接，例如通过总线。应当理解，图1所示的计算设备结构框图仅仅是出于示例的目的，而不是对本说明书范围的限制。本领域技术人员可以根据需要，增添或替换其他部件。
计算设备100可以是任何类型的静止或移动计算设备，包括移动计算机或移动计算设备(例如，平板计算机、个人数字助理、膝上型计算机、笔记本计算机、上网本等)、移动电话(例如，智能手机)、可佩戴的计算设备(例如，智能手表、智能眼镜等)或其他类型的移动设备，或者诸如台式计算机或PC的静止计算设备。计算设备100还可以是移动式或静止式的服务器。
其中，处理器120可以执行图2所示方法中的步骤。图2是示出了根据本说明书一实施例的绑定方法的示意性流程图，应用于客户端，所述客户端可以是支付类应用程序App如支付宝、微信、京东钱包、百度钱包等。该方法包括步骤202至步骤210。
步骤202：向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息。
一种实现方式中，所述账户是支付账户，所述操作码是付款码或收款码。此外所述账户还可以是用于门禁的条形码或其它用于识别身份信息的条形码。
一种实现方式中，所述终端设备是蓝牙设备，如具有蓝牙功能的手环、手表等终端设备。
一种实现方式中，在所述向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息之前还包括：向终端设备发送用以获取设备参数信息的获取请求，并接收所述终端设备发送的响应于所述获取请求的设备参数信息。此外，在具体实现时，还可以通过在客户端手动输入预绑定的终端设备的设备参数。
步骤204：接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息和所述账户的信息生成。
步骤206：向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌。
步骤208：接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述终端设备绑定的操作码。
步骤210：将所述生码关键因子发送至所述终端设备以生成并展示所述操作码。
一种实现方式中，在所述将所述生码关键因子发送至所述终端设备以生成并展示所述付款码或收款码之后还包括：接收所述终端设备发送的成功接收所述生码关键因子的第一反馈信息；基于所述第一反馈信息生成完成绑定的第二反馈信息，并将所述第二反馈信息发送至所述业务服务器；接收所述业务服务器发送的响应于所述第二反馈信息的用以通知绑定可用的业务通知，并将所述业务通知转发至所述终端设备。
其中，处理器120可以执行图3所示方法中的步骤。图3是示出了根据本说明书一实施例的绑定方法的示意性流程图，应用于服务器。该方法包括步骤302至步骤308。
步骤302：接收客户端发送的预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息。
一种实现方式中，所述账户是支付账户，所述操作码是付款码或收款码。此外所述账户还可以是用于门禁的条形码或其它用于识别身份信息的条形码。
一种实现方式中，所述终端设备是蓝牙设备，如具有蓝牙功能的手环、手表等终端设备。
步骤304：基于所述设备参数信息和所述账户的信息生成绑定令牌，并向所述客户端发送所述绑定令牌。
步骤306：接收所述客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌。
步骤308：生成用以生成与所述账户和所述终端设备绑定的操作码的生码关键因子，并将所述生码关键因子发送给所述客户端。
一种实现方式中，在生成用以生成与所述账户和所述终端设备绑定的操作码的生码关键因子，并将所述生码关键因子发送给所述客户端之后还包括：接收所述客户端发送的完成绑定的第二反馈信息，其中，所述第二反馈信息基于所述终端设备发送的成功接收所述生码关键因子的第一反馈信息生成；向所述客户端发送响应于所述第二反馈信息的业务处理成功的业务通知。
本说明书实施例通过将终端设备的设备参数信息与客户端的账户信息进行绑定，在成功绑定后根据账户的业务服务器生成的生码关键因子在终端设备上生成操作码并展示，从而使得旧款的终端设备也可以像新款产品一样对账户进行操作，方便简单，提升了用户体验；为日益增多的智能设备绑定及业务账户产品的新老更替提供便捷、安全的绑定流程，使得新产品应用可以兼容老设备，方便老设备使用新产品应用，保证新老产品演进过程中的业务易用性和安全性。
图4是示出了本说明书一实施例的绑定方法的流程示意图；如图4所示，该方法包括：
1、客户端向蓝牙设备发送请求，获取预绑定的蓝牙设备的设备参数；蓝牙设备响应于客户端的请求，向客户端下发设备参数信息(对应图4中步骤1.1)；
2、客户端根据所接收的蓝牙设备的设备参数信息向业务服务器发送预绑定请求，所述预绑定请求的携带有预绑定param(参数)：蓝牙设备的设备参数信息和预绑定的账户的信息；业务服务器根据蓝牙设备的设备参数信息和预绑定的账户的信息生成绑定上下文token(绑定令牌)(对应图4中步骤2.1)；业务服务器下发绑定上下文token给客户端(对应图4中步骤2.2)；客户端向业务服务器发送绑定请求，所述绑定请求携带有绑定param，绑定param包括绑定上下文token和绑定的账户信息(对应图4中步骤2.3)；业务服务器对接收到的绑定请求进行验证，判断绑定请求中是否携带有所 述绑定令牌，如果判断结果为是则将所述账户与所述蓝牙设备绑定，生成生码关键因子，此步骤是产品绑定的关键流程(对应图4中步骤2.3.1)；业务服务器将生码关键因子返回给客户端(对应图4中步骤2.3.2)；
3、客户端将所接收的所述生码关键因子上传至蓝牙设备；蓝牙设备向客户端返回成功接收生码关键因子的反馈信息(对应图4中步骤3.1)；
4、客户端向业务服务器发送所述蓝牙设备与所述账户完成绑定的反馈信息；业务服务器根据客户端发送的反馈信息进行业务产品可用性处理(对应图4中步骤4.1)，向客户端下发业务参数，告知(绑定)业务处理成功(对应图4中步骤4.2)；
5、客户端向蓝牙设备发送告知绑定成功的通知信息，蓝牙设备向客户端发送接收成功的反馈信息，根据生码关键因子生成并展示操作码(对应图4中步骤5.1)，即可进行支付、刷门禁等操作。
其中，处理器120可以执行图5所示方法中的步骤。图5是示出了根据本说明书一实施例的绑定方法的示意性流程图，应用于网络设备，该网络设备可以是具有网络通信功能的智能手表、手机等终端设备。该方法包括步骤502至步骤514。
步骤502：向业务服务器发送预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息。
一种实现方式中，所述账户是支付账户，所述操作码是付款码或收款码。此外所述账户还可以是用于门禁的条形码或其它用于识别身份信息的条形码。
步骤504：接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息生成。
步骤506：根据所述绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码并向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息。
步骤508：向所述业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
步骤510：向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌。
步骤512：接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
步骤514：根据所述生码关键因子生成并展示所述第二操作码。
一种实现方式中，在所述根据所述生码关键因子生成并展示所述第二操作码之后还包括：向所述业务服务器发送所述账户与所述网络设备完成绑定的第一反馈信息；接收所述业务服务器发送的响应于所述第一反馈信息的用以通知绑定可用的通知信息。
其中，处理器120可以执行图6所示方法中的步骤。图6是示出了根据本说明书一实施例的绑定方法的示意性流程图，应用于业务服务器。该方法包括步骤602至步骤612。
步骤602：接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息。
步骤604：基于所述设备参数信息生成绑定令牌，将所述绑定令牌发送给所述网络设备以使所述网络设备基于所述绑定令牌生成并显示第一操作码。
步骤606：接收客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息，其中，所述客户端通过扫描所述网络设备展示的所述第一种实现方式中，所述账户是支付账户，所述操作码是付款码或收款码。此外所述账户还可以是用于门禁的条形码或其它用于识别身份信息的条形码。
操作码获取所述绑定令牌。
步骤608：基于所述绑定令牌得到所述设备参数信息，将所述设备参数信息对应的所述网络设备和所述账户的信息对应的账户绑定。
步骤610：生成生码关键因子，所述生成关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
一种实现方式中，在所述生成生码关键因子之后还包括：将所述生码关键因子发送给所述客户端。
步骤612：接收所述网络设备发送的用以轮询绑定结果的第一轮询请求，以及响应于所述第一轮询请求将绑定结果信息发送给所述网络设备，其中，当绑定成功时，所述绑定结果信息携带有所述生码关键因子以生成所述第二操作码并展示。
一种实现方式中，在所述接收所述网络设备发送的用以轮询绑定结果的轮询请 求，以及响应于所述轮询请求将绑定结果信息发送给所述网络设备以生成所述第二操作码并展示之后还包括：接收所述网络设备发送的对所述账户的操作请求；根据所述账户与所述网络设备的绑定关系，对所述账户执行所述操作请求对应的操作。
一种实现方式中，在所述接收所述网络设备发送的用以轮询绑定结果的轮询请求，以及响应于所述轮询请求将绑定结果信息发送给所述网络设备以生成所述第二操作码并展示之后还包括：接收所述网络设备发送的所述账户与所述网络设备完成绑定的第一反馈信息；响应于所述第一反馈信息生成用以通知绑定可用的通知信息，向所述网络设备发送所述通知信息。
一种实现方式中，在将所述生码关键因子发送给所述客户端之后还包括：
接收所述客户端发送的用以轮询绑定结果的第二轮询请求，以及响应于所述第二轮询请求将绑定结果信息发送给所述客户端。
其中，处理器120可以执行图7所示方法中的步骤。图7是示出了根据本说明书一实施例的绑定方法的示意性流程图，应用于客户端，所述客户端可以是支付类应用程序App如支付宝、微信、京东钱包、百度钱包等。该方法包括步骤702至步骤706。
步骤702：通过扫描网络设备显示的第一操作码获取绑定令牌，所述绑定令牌用以标识所述网络设备的身份信息。
步骤704：向业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息。
一种实现方式中，所述账户是支付账户，所述操作码是付款码或收款码。此外所述账户还可以是用于门禁的条形码或其它用于识别身份信息的条形码。
步骤706：接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中所述生码关键因子用以生成绑定所述网络设备和所述账户的第二操作码。
一种实现方式中，在所述接收所述业务服务器发送的响应于所述绑定请求的生码关键因子之后还包括：向所述业务服务器发送用以轮询所述网络设备与所述账户绑定结果的轮询请求；接收所述业务服务器发送的响应于所述轮询请求的绑定结果通知信息。
本说明书实施例通过将终端设备的设备参数信息与客户端的账户信息进行绑定，在成功绑定后根据账户的业务服务器生成的生码关键因子在终端设备上生成操作码并展示，从而使得旧款的终端设备也可以像新款产品一样对账户进行操作，方便简单，提 升了用户体验；为日益增多的智能设备绑定及业务账户产品的新老更替提供便捷、安全的绑定流程，使得新产品应用可以兼容老设备，方便老设备使用新产品应用，保证新老产品演进过程中的业务易用性和安全性。
图8是示出了本说明书一实施例的绑定方法的流程示意图；如图8所示，该方法包括：
1、网络设备向业务服务器发送预绑定请求，上传网络设备的设备参数信息param；业务服务器根据网络设备的设备参数信息生成绑定上下文token(令牌)，(对应图8中步骤1.1)，并将绑定上下文token返回给网络设备(对应图8中步骤1.2)；网络设备根据接收到的绑定上下文token生成绑定二维码(对应图8中步骤1.3)；
2、客户端扫描所述绑定二维码，获取绑定上下文token(对应图8中步骤2.1)；
3、客户端向业务服务器发送绑定请求，所述绑定请求包括所述绑定上下文token和预绑定的账户的信息；业务服务器对接收到的绑定请求进行验证，判断绑定请求中是否携带有所述绑定上下文token，如果判断结果为是则将所述账户与所述网络设备绑定，生成生码关键因子，此步骤是产品绑定的关键流程(对应图8中步骤3.1)；业务服务器将生码关键因子返回给客户端(对应图8中步骤3.2)；
4、从生成绑定二维码后，网络设备向业务服务器开始发送用以查询绑定是否成功的轮询请求，业务服务器响应于所述轮询请求对绑定结果进行查询(对应图8中步骤4.1)，将查询得到的绑定结果信息发送给网络设备，其中，当绑定成功时，所述绑定结果信息携带有生码关键因子(对应图8中步骤4.2)，所述生码关键因子用以生成与所述账户和所述网络设备绑定的操作码；当接收到所述生码关键因子后，网络设备向业务服务器发送所述网络设备与所述账户完成绑定的反馈信息(对应图8中步骤4.3)；业务服务器根据网络设备发送的反馈信息进行业务产品可用性处理(对应图8中步骤4.3.1)，向网络设备下发业务参数，告知(绑定)业务处理成功(对应图8中步骤4..3.2)；网络设备根据所接收到的生码关键因子生成操作码并展示(对应图8中步骤4.3.3)，即可进行支付、刷门禁等业务操作；
5、客户端向业务服务器发送用以查询绑定是否成功的轮询请求，业务服务器响应于所述轮询请求对绑定结果进行查询(对应图8中步骤5.1)，将查询得到的绑定结果信息发送给客户端对应图8中步骤5.2)。
其中，处理器120可以执行图9所示方法中的步骤。图9是示出了根据本说明 书一实施例的绑定方法的示意性流程图，应用于网络设备。该方法包括步骤902至步骤910。
步骤902：向第一业务服务器发送预绑定请求，以使所述第一业务服务器基于所述预绑定请求携带的所述网络设备的设备参数信息生成第一绑定令牌。
步骤904：接收所述第一业务服务器发送的响应于所述预绑定请求的第二绑定令牌，其中所述第二绑定令牌由作为迁移目的服务器的第二业务服务器基于所述第一业务服务器发送的所述设备参数信息和第一绑定令牌生成。
步骤906：根据所述第二绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码获取所述第二绑定令牌以向第二业务服务器发送绑定请求，所述绑定请求携带有所述第二绑定令牌和绑定的账户的信息。
一种实现方式中，所述账户是支付账户，所述操作码是付款码或收款码。此外所述账户还可以是用于门禁的条形码或其它用于识别身份信息的条形码。
步骤908：向所述第一业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述第一业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，所述绑定结果信息由所述第二业务服务器基于所述第一业务服务器转发的所述轮询请求生成，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
步骤910：根据所述生码关键因子生成并展示所述第二操作码。
一种实现方式中，所述账户是支付账户，所述第二操作码是付款码或收款码。
一种实现方式中，在所述根据所述生码关键因子生成并展示所述第二操作码之后还包括：向所述第一业务服务器发送所述账户与所述网络设备完成绑定的反馈信息；接收所述第一业务服务器发送的响应于所述反馈信息的用以通知绑定可用的第一通知信息，其中所述第一通知信息由所述第二业务服务器基于所述第一业务服务器转发的所述反馈信息生成。
一种实现方式中，在所述根据所述生码关键因子生成并展示所述第二操作码之后还包括：向所述第一业务服务器发送将所述账户与所述网络设备解绑的解绑请求；接收所述第一业务服务器发送的响应于所述解绑请求的用以通知绑定解除的第二通知信息，其中所述第二通知信息由所述第二业务服务器基于所述第一业务服务器转发的所述解绑请求生成。
其中，处理器120可以执行图10所示方法中的步骤。图10是示出了根据本说明书一实施例的绑定方法的示意性流程图，应用于第一业务服务器。该方法包括步骤1002至步骤1010。
步骤1002：接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息。
步骤1004：判断所述预绑定请求的业务目的服务器是否是所述第一业务服务器，如果判断结果为否则基于所述设备参数信息生成第一绑定令牌，将所述第一绑定令牌和所述预绑定请求发送给作为迁移目的服务器的第二业务服务器以使所述第二业务服务器基于所述设备参数信息和第一绑定令牌生成第二绑定令牌；。
步骤1006：接收所述第二业务服务器发送的响应于所述预绑定请求的第二绑定令牌，将所述第二绑定令牌发送给所述网络设备。
步骤1008：接收所述网络设备发送的用以轮询绑定结果的轮询请求，将所述轮询请求发送给所述第二业务服务器。
步骤1010：接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
一种实现方式中，所述账户是支付账户，所述操作码是付款码或收款码。此外所述账户还可以是用于门禁的条形码或其它用于识别身份信息的条形码。
一种实现方式中，在所述接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备之后还包括：接收所述网络设备发送的所述账户与所述网络设备完成绑定的反馈信息，将所述反馈信息发送给所述第二业务服务器；接收所述第二业务服务器发送的响应于所述反馈信息的用以通知绑定可用的第一通知信息，将所述第一通知信息发送给所述网络设备。
一种实现方式中，在所述接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备之后还包括：接收所述网络设备发送的将所述账户与所述网络设备解绑的解绑请求，将所述解绑请求发送给所述第二业务服务器；接收所述第二业务服务器发送的响应于所述解绑请求的用以通知绑定解除的第二通知信息，将所述第二通知信息发送给所述网络设备。
其中，处理器120可以执行图11所示方法中的步骤。图11是示出了根据本说明书一实施例的绑定迁移方法的示意性流程图，应用于第二业务服务器。该方法包括步骤1102至步骤1110。
步骤1102：接收第一业务服务器发送的预绑定请求，其中所述预绑定请求携带有预绑定的网络设备的设备参数信息和第一绑定令牌，所述第一绑定令牌由所述第一业务服务器基于所述设备参数信息生成。
步骤1104：基于所述设备参数信息和所述第一绑定令牌生成第二绑定令牌，将所述第二绑定令牌发送给所述第一业务服务器以使所述第一业务服务器将所述第二绑定令牌发送给所述网络设备以使所述网络设备根据所述第二绑定令牌生成第一操作码并展示。
步骤1106：接收客户端发送的绑定请求，其中所述绑定请求包括所述第二绑定令牌和预绑定的账户的信息，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述第二绑定令牌。
步骤1108：判断所述绑定请求是否包含有所述第二绑定令牌，若判断结果为是则将所述账户与所述网络设备进行绑定，根据绑定结果生成生码关键因子并发送给所述客户端。
步骤1110：接收所述第一业务服务器发送的用以轮询绑定结果的第一轮询请求，其中所述第一轮询请求由所述网络设备发送给所述第一业务服务器。
步骤1112：根据所述第一轮询请求查询所述网络设备与所述账户的绑定结果，将查询到的绑定结果信息发送给所述第一业务服务器以使所述第一业务服务器将所述绑定结果信息发送给所述网络设备，其中在绑定成功的情况下，所述绑定结果信息携带有所述生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
一种实现方式中，在所述根据所述第一轮询请求查询所述网络设备与所述账户的绑定结果，将查询到的绑定结果信息所述第一业务服务器以使所述第一业务服务器将所述绑定结果信息发送给所述网络设备之后还包括：接收所述第一业务服务器发送的所述账户与所述网络设备完成绑定的反馈信息，其中所述反馈信息由所述网络设备生成；根据所述反馈信息生成用以通知绑定可用的第一通知信息，将所述第一通知信息发送给所述第一业务服务器以使所述第一业务服务器将所述第一通知信息发送给所述网络设 备。
一种实现方式中，在所述根据所述轮询请求查询所述网络设备与所述账户的绑定结果，将查询到的绑定结果信息所述第一业务服务器以使所述第一业务服务器将所述绑定结果信息发送给所述网络设备之后还包括：接收所述第一业务服务器发送的将所述账户与所述网络设备解绑的解绑请求，其中所述解绑请求由所述网络设备生成并发送给所述第一业务服务器；根据所述解绑请求将所述账户与所述网络设备进行解绑，生成用以通知绑定解除的第二通知信息；将所述第二通知信息发送给所述第一业务服务器以使所述第一业务服务器将所述第二通知信息发送给所述网络设备。
一种实现方式中，在所述接收客户端发送的绑定请求之后还包括：接收所述客户端发送的用以轮询绑定结果的第二轮询请求；根据所述第二轮询请求查询所述网络设备与所述账户的绑定结果，将查询到的绑定结果信息发送给所述客户端，其中在绑定成功的情况下，所述绑定结果信息携带有所述生码关键因子。
本说明书实施例通过将终端设备的设备参数信息与客户端的账户信息进行绑定，在成功绑定后根据账户的业务服务器生成的生码关键因子在终端设备上生成操作码并展示，从而使得旧款的终端设备也可以像新款产品一样对账户进行操作，方便简单，提升了用户体验；为日益增多的智能设备绑定及业务账户产品的新老更替提供便捷、安全的绑定流程，使得新产品应用可以兼容老设备，方便老设备使用新产品应用，保证新老产品演进过程中的业务易用性和安全性。
图12是示出了本说明书一实施例的绑定方法的流程示意图；如图12所示，该方法包括：
1、网络设备向业务服务器A发送预绑定请求，上传网络设备的设备参数信息param；业务服务器根据网络设备的设备参数信息生成绑定上下文token(令牌)，(对应图8中步骤1.1)，并将绑定上下文token和网络设备的设备参数信息发送给业务服务器B(对应图12中步骤1.2)；业务服务器B根据所接收到的绑定上下文token和设备参数信息生成指定token的绑定上下文(对应图12中步骤1.2.1)；业务服务器B将指定token的绑定上下文token返回给业务服务器A(对应图12中步骤1.2.2)；业务服务器A将指定token的绑定上下文返回给网络设备(对应图12中步骤1.2.3)；
2、网络设备根据接收到的指定token的绑定上下文成绑定二维码；
3、客户端扫描所述绑定二维码，获取绑定上下文token(对应图12中步骤3.1)；
4、客户端向业务服务器B发送绑定请求，所述绑定请求包括所述绑定上下文token和预绑定的账户的信息；业务服务器B对接收到的绑定请求进行验证，判断绑定请求中是否携带有所述绑定上下文token，如果判断结果为是则将所述账户与所述网络设备绑定，生成生码关键因子，此步骤是产品绑定的关键流程(对应图12中步骤4.1)；业务服务器B将生码关键因子返回给客户端(对应图8中步骤4.2)；
5、从生成绑定二维码后，网络设备向业务服务器A开始发送用以查询绑定迁移是否成功的轮询请求，业务服务器A将轮询请求转发给业务服务器B(对应图12中步骤5.1)；业务服务器B响应于所述轮询请求对绑定结果进行查询(对应图12中步骤5.1.1)，将查询得到的绑定结果信息发送给业务服务器A(对应图12中步骤5.1.2)；业务服务器A将绑定结果信息转发给网络设备，同时将转发标志位标记为转发(对应图12中步骤5.1.4)，其中，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的操作码；
6、当接收到所述生码关键因子后，网络设备向业务服务器A发送所述网络设备与所述账户完成绑定的反馈信息；业务服务器A将转发标志位标记位转发(对应图12中步骤6.1)，将完成绑定的所述反馈信息转发给业务服务器B(对应图12中步骤6.2)；业务服务器B根据所述反馈信息进行业务产品可用性处理(对应图12中步骤6.2.1)，向业务服务器A下发业务参数，告知(绑定迁移)业务处理成功(对应图12中步骤6.2.2)；业务服务器A将业务处理成功的通知下发给网络设备(对应图12中步骤6.2.3)；
7、网络设备根据所接收到的生码关键因子生成操作码并展示，即可进行支付、刷门禁等业务操作；
8、客户端向业务服务器B发送用以查询绑定是否成功的轮询请求，业务服务器B响应于所述轮询请求对绑定结果进行查询(对应图12中步骤8.1)，将查询得到的绑定结果信息发送给客户端(对应图12中步骤8.2)；
9、网络设备向业务服务器A发送的将所述账户与所述网络设备解绑的解绑请求；业务服务器A将所述解绑请求转发给所述业务服务器B(对应图12中步骤9.1)；业务服务器B根据所述解绑请求将所述账户与所述网络设备进行解绑，生成用以通知绑定解除的通知信息并发送给业务服务器A(对应图12中步骤9.2)；业务服务器A将解绑结果的通知信息转发给所述网络设备(对应图12中步骤9.3)。
与前述绑定方法、绑定迁移方法相对应，本说明书还提供了绑定装置、绑定迁 移装置实施例，所述装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在设备的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，本说明书的绑定装置、绑定迁移装置所在设备的一种硬件结构可以包括处理器、网络接口、内存以及非易失性存储器之外，实施例中装置所在的设备通常根据实际功能，还可以包括其他硬件，对此不再赘述。
参见图13，为本说明书一实施例提供的绑定装置的模块图。绑定装置1300对应了图2所示实施例，所述装置1300包括:
第一请求器1302，被配置为向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
第一接收器1304，被配置为接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息和所述账户的信息生成；
第二请求器1306，被配置为向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
第二接收器1308，被配置为接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述终端设备绑定的操作码；
第一展示器1310，被配置为将所述生码关键因子发送至所述终端设备以生成并展示所述操作码。
一个可选的实施例中，所述终端设备是蓝牙设备。
一个可选的实施例中，所述账户是支付账户，所述操作码是付款码或收款码。
参见图14，为本说明书一实施例提供的绑定装置的模块图。绑定装置1400对应了图3所示实施例，所述装置1400包括:
第三接收器1402，被配置为接收客户端发送的预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
第一生成器1404，被配置为基于所述设备参数信息和所述账户的信息生成绑定令牌，并向所述客户端发送所述绑定令牌；
第四接收器1406，被配置为接收所述客户端发送的绑定请求，所述绑定请求携 带有所述绑定令牌；
第二生成器1408，被配置为生成用以生成与所述账户和所述终端设备绑定的操作码的生码关键因子，并将所述生码关键因子发送给所述客户端。
一个可选的实施例中，所述终端设备是蓝牙设备。
参见图15，为本说明书一实施例提供的绑定装置的模块图。绑定装置1500对应了图5所示实施例，所述装置1500包括:
第三请求器1502，被配置为向业务服务器发送预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
第四接收器1504，被配置为接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息生成；
第二展示器1506，被配置为根据所述绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码并向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息；
第四请求器1508，被配置为向所述业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第五请求器1510，被配置为向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
第五接收器1512，被配置为接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第三展示器1514，被配置为根据所述生码关键因子生成并展示所述第二操作码。
一个可选的实施例中，所述账户是支付账户，所述第二操作码是付款码或收款码。
参见图16，为本说明书一实施例提供的绑定装置的模块图。绑定装置1600对应了图6所示实施例，所述装置1600包括:
第六接收器1602，被配置为接收网络设备发送的预绑定请求，所述预绑定请求 携带有所述网络设备的设备参数信息；
第三生成器1604，被配置为基于所述设备参数信息生成绑定令牌，将所述绑定令牌发送给所述网络设备以使所述网络设备基于所述绑定令牌生成并显示第一操作码；
第七接收器1606，被配置为接收客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息，其中，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述绑定令牌；
第一绑定器1608，被配置为基于所述绑定令牌得到所述设备参数信息，将所述设备参数信息对应的所述网络设备和所述账户的信息对应的账户绑定；
第四生成器1610，被配置为生成生码关键因子，所述生成关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第八接收器1612，被配置为接收所述网络设备发送的用以轮询绑定结果的第一轮询请求，以及响应于所述第一轮询请求将绑定结果信息发送给所述网络设备，其中，当绑定成功时，所述绑定结果信息携带有所述生码关键因子以生成所述第二操作码并展示。
参见图17，为本说明书一实施例提供的绑定装置的模块图。绑定装置1700对应了图7所示实施例，所述装置1700包括:
扫描器1702，被配置为通过扫描网络设备显示的第一操作码获取绑定令牌，所述绑定令牌用以标识所述网络设备的身份信息；
第六请求器1704，被配置为向业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息；
第九接收器1706，被配置为接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中所述生码关键因子用以生成绑定所述网络设备和所述账户的第二操作码。
参见图18，为本说明书一实施例提供的绑定迁移装置的模块图。绑定迁移装置1800对应了图9所示实施例，所述装置1800包括:
第七请求器1802，被配置为向第一业务服务器发送预绑定请求，以使所述第一业务服务器基于所述预绑定请求携带的所述网络设备的设备参数信息生成第一绑定令牌；
第十接收器1804，被配置为接收所述第一业务服务器发送的响应于所述预绑定请求的第二绑定令牌，其中所述第二绑定令牌由作为迁移目的服务器的第二业务服务器基于所述第一业务服务器发送的所述设备参数信息和第一绑定令牌生成；
第五生成器1806，被配置为根据所述第二绑定令牌生成第一操作码，展示所述第一操作码以使客户端扫码获取所述第二绑定令牌以向第二业务服务器发送绑定请求，所述绑定请求携带有所述第二绑定令牌和绑定的账户的信息；
第八请求器1808，被配置为向所述第一业务服务器发送用以轮询绑定结果的轮询请求，以及接收所述第一业务服务器发送的响应于所述轮询请求的绑定结果信息，其中，所述绑定结果信息由所述第二业务服务器基于所述第一业务服务器转发的所述轮询请求生成，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
第四展示器1810，被配置为根据所述生码关键因子生成并展示所述第二操作码。
一个可选的实施例中，所述账户是支付账户，所述第二操作码是付款码或收款码。
参见图19，为本说明书一实施例提供的绑定迁移装置的模块图。绑定迁移装置1900对应了图10所示实施例，应用于第一业务服务器，所述装置1900包括:
第十一接收器1902，被配置为接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
第六生成器1904，被配置为判断所述预绑定请求的业务目的服务器是否是所述第一业务服务器，如果判断结果为否则基于所述设备参数信息生成第一绑定令牌，将所述第一绑定令牌和所述预绑定请求发送给作为迁移目的服务器的第二业务服务器以使所述第二业务服务器基于所述设备参数信息和第一绑定令牌生成第二绑定令牌；
第十二接收器1906，被配置为接收所述第二业务服务器发送的响应于所述预绑定请求的第二绑定令牌，将所述第二绑定令牌发送给所述网络设备；
第十三接收器1908，被配置为接收所述网络设备发送的用以轮询绑定结果的轮询请求，将所述轮询请求发送给所述第二业务服务器；
第十四接收器1910，被配置为接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备，当绑定成功时，所述 绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
参见图20，为本说明书一实施例提供的绑定迁移装置的模块图。绑定迁移装置2000对应了图11所示实施例，应用于第二业务服务器，所述装置2000包括:
第十五接收器2002，被配置为接收第一业务服务器发送的预绑定请求，其中所述预绑定请求携带有预绑定的网络设备的设备参数信息和第一绑定令牌，所述第一绑定令牌由所述第一业务服务器基于所述设备参数信息生成；
第七生成器2004，被配置为基于所述设备参数信息和所述第一绑定令牌生成第二绑定令牌，将所述第二绑定令牌发送给所述第一业务服务器以使所述第一业务服务器将所述第二绑定令牌发送给所述网络设备以使所述网络设备根据所述第二绑定令牌生成第一操作码并展示；
第十六接收器2006，被配置为接收客户端发送的绑定请求，其中所述绑定请求包括所述第二绑定令牌和预绑定的账户的信息，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述第二绑定令牌；
判断器2008，被配置为判断所述绑定请求是否包含有所述第二绑定令牌，若判断结果为是则将所述账户与所述网络设备进行绑定，根据绑定结果生成生码关键因子并发送给所述客户端；
第十七接收器2010，被配置为接收所述第一业务服务器发送的用以轮询绑定结果的第一轮询请求，其中所述第一轮询请求由所述网络设备发送给所述第一业务服务器；
第二绑定器2012，被配置为根据所述第一轮询请求查询所述网络设备与所述账户的绑定结果，将查询到的绑定结果信息发送给所述第一业务服务器以使所述第一业务服务器将所述绑定结果信息发送给所述网络设备，其中在绑定成功的情况下，所述绑定结果信息携带有所述生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
上述实施例阐明的装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本说明书方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本说明书一实施例还提供一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，所述处理器执行所述指令时实现所述的绑定方法、绑定迁移方法的步骤。
本说明书一实施例还提供一种计算机可读存储介质，其存储有计算机指令，该指令被处理器执行时实现所述的绑定方法、绑定迁移方法的步骤。
上述为本实施例的一种计算机可读存储介质的示意性方案。需要说明的是，该存储介质的技术方案与上述的方法的技术方案属于同一构思，存储介质的技术方案未详细描述的细节内容，均可以参见上述方法的技术方案的描述。
所述计算机指令包括计算机程序代码，所述计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括：能够携带所述计算机程序代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读介质不包括电载波信号和电信信号。
需要说明的是，对于前述的各方法实施例，为了简便描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本说明书并不受所描述的动作顺序的限制，因为依据本说明书，某些步骤可以采用其它顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定都是本说明书所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其它实施例的相关描述。
以上公开的本说明书优选实施例只是用于帮助阐述本说明书。可选实施例并没有详尽叙述所有的细节，也不限制该发明仅为所述的具体实施方式。显然，根据本说明书的内容，可作很多的修改和变化。本说明书选取并具体描述这些实施例，是为了更好地解释本说明书的原理和实际应用，从而使所属技术领域技术人员能很好地理解和利用本说明书。本说明书仅受权利要求书及其全部范围和等效物的限制。

Claims (20)

  1. 一种绑定方法，应用于客户端，所述方法包括：
    向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
    接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息和所述账户的信息生成；
    向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
    接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述终端设备绑定的操作码；
    将所述生码关键因子发送至所述终端设备以生成并展示所述操作码。
  2. 根据权利要求1所述的方法，其中所述终端设备是蓝牙设备。
  3. 根据权利要求1所述的方法，其中所述账户是支付账户，所述操作码是付款码或收款码。
  4. 根据权利要求1所述的方法，其中在所述向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息之前还包括：
    向终端设备发送用以获取设备参数信息的获取请求，并接收所述终端设备发送的响应于所述获取请求的设备参数信息。
  5. 根据权利要求1所述的方法，其中在所述将所述生码关键因子发送至所述终端设备以生成并展示所述操作码之后还包括：
    接收所述终端设备发送的成功接收所述生码关键因子的第一反馈信息；
    基于所述第一反馈信息生成完成绑定的第二反馈信息，并将所述第二反馈信息发送至所述业务服务器；
    接收所述业务服务器发送的响应于所述第二反馈信息的，绑定可用的业务通知，并将所述业务通知转发至所述终端设备。
  6. 一种绑定方法，应用于业务服务器，所述方法包括：
    接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
    基于所述设备参数信息生成绑定令牌，将所述绑定令牌发送给所述网络设备以使所述网络设备基于所述绑定令牌生成并显示第一操作码；
    接收客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息，其中，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述绑定令牌；
    基于所述绑定令牌得到所述设备参数信息，将所述设备参数信息对应的所述网络设备和所述账户的信息对应的账户绑定；
    生成生码关键因子，所述生成关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
    接收所述网络设备发送的用以轮询绑定结果的第一轮询请求，以及响应于所述第一轮询请求将绑定结果信息发送给所述网络设备，其中，当绑定成功时，所述绑定结果信息携带有所述生码关键因子以生成所述第二操作码并展示。
  7. 根据权利要求6所述的方法，其中在所述接收所述网络设备发送的用以轮询绑定结果的轮询请求，以及响应于所述轮询请求将绑定结果信息发送给所述网络设备以生成所述第二操作码并展示之后还包括：
    接收所述网络设备发送的对所述账户的操作请求；
    根据所述账户与所述网络设备的绑定关系，对所述账户执行所述操作请求对应的操作。
  8. 根据权利要求6所述的方法，其中所述账户是支付账户，所述第二操作码是付款码或收款码。
  9. 根据权利要求6所述的方法，其中在所述接收所述网络设备发送的用以轮询绑定结果的轮询请求，以及响应于所述轮询请求将绑定结果信息发送给所述网络设备以生成所述第二操作码并展示之后还包括：
    接收所述网络设备发送的所述账户与所述网络设备完成绑定的第一反馈信息；
    响应于所述第一反馈信息生成用以通知绑定可用的通知信息，向所述网络设备发送所述通知信息。
  10. 根据权利要求6所述的方法，其中在所述生成生码关键因子之后还包括：
    将所述生码关键因子发送给所述客户端。
  11. 根据权利要求10所述的方法，其中在将所述生码关键因子发送给所述客户端之后还包括：
    接收所述客户端发送的用以轮询绑定结果的第二轮询请求，以及响应于所述第二轮询请求将绑定结果信息发送给所述客户端。
  12. 一种绑定迁移方法，应用于第一业务服务器，所述方法包括：
    接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
    判断所述预绑定请求的业务目的服务器是否是所述第一业务服务器，如果判断结果 为否则基于所述设备参数信息生成第一绑定令牌，将所述第一绑定令牌和所述预绑定请求发送给作为迁移目的服务器的第二业务服务器以使所述第二业务服务器基于所述设备参数信息和第一绑定令牌生成第二绑定令牌；
    接收所述第二业务服务器发送的响应于所述预绑定请求的第二绑定令牌，将所述第二绑定令牌发送给所述网络设备；
    接收所述网络设备发送的用以轮询绑定结果的轮询请求，将所述轮询请求发送给所述第二业务服务器；
    接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
  13. 根据权利要求12所述的方法，其中所述账户是支付账户，所述第二操作码是付款码或收款码。
  14. 根据权利要求12所述的方法，其中在所述接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备之后还包括：
    接收所述网络设备发送的所述账户与所述网络设备完成绑定的反馈信息，将所述反馈信息发送给所述第二业务服务器；
    接收所述第二业务服务器发送的响应于所述反馈信息的用以通知绑定可用的第一通知信息，将所述第一通知信息发送给所述网络设备。
  15. 根据权利要求12所述的方法，其中在所述接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备之后还包括：
    接收所述网络设备发送的将所述账户与所述网络设备解绑的解绑请求，将所述解绑请求发送给所述第二业务服务器；
    接收所述第二业务服务器发送的响应于所述解绑请求的用以通知绑定解除的第二通知信息，将所述第二通知信息发送给所述网络设备。
  16. 一种绑定装置，应用于客户端，所述装置包括：
    第一请求器，被配置为向业务服务器发送预绑定请求，所述预绑定请求携带有预绑定终端设备的设备参数信息和预绑定的账户的信息；
    第一接收器，被配置为接收所述业务服务器发送的响应于所述预绑定请求的绑定令牌，其中所述绑定令牌基于所述设备参数信息和所述账户的信息生成；
    第二请求器，被配置为向所述业务服务器发送绑定请求，所述绑定请求携带有所述绑定令牌；
    第二接收器，被配置为接收所述业务服务器发送的响应于所述绑定请求的生码关键因子，其中，所述生码关键因子用以生成与所述账户和所述终端设备绑定的操作码；
    第一展示器，被配置为将所述生码关键因子发送至所述终端设备以生成并展示所述操作码。
  17. 一种绑定装置，应用于业务服务器，所述装置包括：
    第六接收器，被配置为接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
    第三生成器，被配置为基于所述设备参数信息生成绑定令牌，将所述绑定令牌发送给所述网络设备以使所述网络设备基于所述绑定令牌生成并显示第一操作码；
    第七接收器，被配置为接收客户端发送的绑定请求，所述绑定请求携带有所述绑定令牌和绑定的账户的信息，其中，所述客户端通过扫描所述网络设备展示的所述第一操作码获取所述绑定令牌；
    第一绑定器，被配置为基于所述绑定令牌得到所述设备参数信息，将所述设备参数信息对应的所述网络设备和所述账户的信息对应的账户绑定；
    第四生成器，被配置为生成生码关键因子，所述生成关键因子用以生成与所述账户和所述网络设备绑定的第二操作码；
    第八接收器，被配置为接收所述网络设备发送的用以轮询绑定结果的第一轮询请求，以及响应于所述第一轮询请求将绑定结果信息发送给所述网络设备，其中，当绑定成功时，所述绑定结果信息携带有所述生码关键因子以生成所述第二操作码并展示。
  18. 一种绑定迁移装置，应用于第一业务服务器，所述装置包括：
    第十一接收器，被配置为接收网络设备发送的预绑定请求，所述预绑定请求携带有所述网络设备的设备参数信息；
    第六生成器，被配置为判断所述预绑定请求的业务目的服务器是否是所述第一业务服务器，如果判断结果为否则基于所述设备参数信息生成第一绑定令牌，将所述第一绑定令牌和所述预绑定请求发送给作为迁移目的服务器的第二业务服务器以使所述第二业务服务器基于所述设备参数信息和第一绑定令牌生成第二绑定令牌；
    第十二接收器，被配置为接收所述第二业务服务器发送的响应于所述预绑定请求的第二绑定令牌，将所述第二绑定令牌发送给所述网络设备；
    第十三接收器，被配置为接收所述网络设备发送的用以轮询绑定结果的轮询请求， 将所述轮询请求发送给所述第二业务服务器；
    第十四接收器，被配置为接收所述第二业务服务器发送的响应于所述轮询请求的绑定结果信息，将所述绑定结果信息发送给所述网络设备，当绑定成功时，所述绑定结果信息携带有生码关键因子，所述生码关键因子用以生成与所述账户和所述网络设备绑定的第二操作码。
  19. 一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，所述处理器执行所述指令时实现权利要求1-15任一项所述的方法的步骤。
  20. 一种计算机可读存储介质，其存储有计算机指令，该指令被处理器执行时实现权利要求1-15任一项所述的方法的步骤。
PCT/CN2019/096693 2018-08-31 2019-07-19 绑定、迁移方法和装置、计算设备及存储介质 WO2020042823A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811014039.3 2018-08-31
CN201811014039.3A CN109274726B (zh) 2018-08-31 2018-08-31 绑定、迁移方法和装置、计算设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020042823A1 true WO2020042823A1 (zh) 2020-03-05

Family

ID=65154999

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/096693 WO2020042823A1 (zh) 2018-08-31 2019-07-19 绑定、迁移方法和装置、计算设备及存储介质

Country Status (3)

Country Link
CN (2) CN109274726B (zh)
TW (1) TWI777070B (zh)
WO (1) WO2020042823A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113641983A (zh) * 2020-04-15 2021-11-12 支付宝(杭州)信息技术有限公司 一种应用程序的账户绑定方法、装置及系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109274726B (zh) * 2018-08-31 2020-07-07 阿里巴巴集团控股有限公司 绑定、迁移方法和装置、计算设备及存储介质
CN113723126A (zh) * 2021-08-31 2021-11-30 北京市商汤科技开发有限公司 数据获取方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103634297A (zh) * 2013-11-11 2014-03-12 广东天际电器股份有限公司 云电器的账号绑定方法及系统
WO2015179726A1 (en) * 2014-05-23 2015-11-26 Looppay, Inc. Systems and methods for linking devices to user accounts
CN107317807A (zh) * 2017-06-22 2017-11-03 北京洋浦伟业科技发展有限公司 一种设备绑定方法、装置及系统
CN108200192A (zh) * 2018-01-30 2018-06-22 北京小米移动软件有限公司 控制终端设备绑定的方法及装置
CN108390873A (zh) * 2018-02-11 2018-08-10 广东美的厨房电器制造有限公司 智能设备的鉴权绑定方法、装置以及系统
CN109274726A (zh) * 2018-08-31 2019-01-25 阿里巴巴集团控股有限公司 绑定、迁移方法和装置、计算设备及存储介质

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2540057A2 (en) * 2010-02-26 2013-01-02 General instrument Corporation Dynamic cryptographic subscriber-device identity binding for subscriber mobility
US9143492B2 (en) * 2013-03-15 2015-09-22 Fortinet, Inc. Soft token system
CN104601327B (zh) * 2013-12-30 2019-01-29 腾讯科技（深圳）有限公司 一种安全验证方法、相关设备和系统
CN103916830A (zh) * 2014-03-31 2014-07-09 福建星网锐捷通讯股份有限公司 一种基于微信的实现用户手机与普通话机进行绑定的系统
CN104217333A (zh) * 2014-05-12 2014-12-17 陈俊 一种借助移动终端、互联网和计算机的认证支付方法
CN104125067B (zh) * 2014-06-26 2017-05-24 小米科技有限责任公司 绑定账号与令牌密钥的方法、装置
CN106161354A (zh) * 2015-03-31 2016-11-23 阿里巴巴集团控股有限公司 业务鉴权方法、装置、设备及业务服务器
CN111833043B (zh) * 2015-05-25 2024-04-19 创新先进技术有限公司 信息交互方法、设备及服务端
CN105897668A (zh) * 2015-10-22 2016-08-24 乐视致新电子科技（天津）有限公司 一种第三方账号授权方法、设备、服务器及其系统
CN108234113B (zh) * 2016-12-15 2020-11-27 腾讯科技（深圳）有限公司 身份验证方法、装置与系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103634297A (zh) * 2013-11-11 2014-03-12 广东天际电器股份有限公司 云电器的账号绑定方法及系统
WO2015179726A1 (en) * 2014-05-23 2015-11-26 Looppay, Inc. Systems and methods for linking devices to user accounts
CN107317807A (zh) * 2017-06-22 2017-11-03 北京洋浦伟业科技发展有限公司 一种设备绑定方法、装置及系统
CN108200192A (zh) * 2018-01-30 2018-06-22 北京小米移动软件有限公司 控制终端设备绑定的方法及装置
CN108390873A (zh) * 2018-02-11 2018-08-10 广东美的厨房电器制造有限公司 智能设备的鉴权绑定方法、装置以及系统
CN109274726A (zh) * 2018-08-31 2019-01-25 阿里巴巴集团控股有限公司 绑定、迁移方法和装置、计算设备及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113641983A (zh) * 2020-04-15 2021-11-12 支付宝(杭州)信息技术有限公司 一种应用程序的账户绑定方法、装置及系统
CN113641983B (zh) * 2020-04-15 2024-06-07 支付宝(杭州)信息技术有限公司 一种应用程序的账户绑定方法、装置及系统

Also Published As

Publication number Publication date
CN109274726B (zh) 2020-07-07
TW202011722A (zh) 2020-03-16
TWI777070B (zh) 2022-09-11
CN111835824A (zh) 2020-10-27
CN111835824B (zh) 2023-02-03
CN109274726A (zh) 2019-01-25

Similar Documents

Publication Publication Date Title
WO2020042823A1 (zh) 绑定、迁移方法和装置、计算设备及存储介质
US20220318233A1 (en) System for tracking data associated with a digital token
KR101986758B1 (ko) 사용자를 소셜 데이터에 매칭하기 위한 시스템 및 방법
TWI767134B (zh) 資料傳輸方法、裝置、計算設備及儲存媒介
US20180070208A1 (en) Interaction tracking and organizing system
JP5628571B2 (ja) 情報処理装置、プログラム、及び情報処理装置の制御方法
JP2024033200A (ja) 情報処理装置、情報処理方法、およびプログラム
JP6005113B2 (ja) 決済管理装置、決済管理方法および決済管理プログラム
JP6203700B2 (ja) 会員管理装置、会員管理方法、およびプログラム
US10555148B2 (en) Mobile ghosting
US20160078469A1 (en) Application Purchasing Method, And Terminal
US11847526B2 (en) Recording multimodal user interaction with items in real and digital environments
WO2018116401A1 (ja) 資産管理システム、資産管理方法、およびプログラム
JP6590879B2 (ja) 会員管理装置、会員管理方法、およびプログラム
WO2018230185A1 (ja) 情報処理装置及び情報処理システム
LU101780B1 (en) Recording multimodal user interaction with items in real and digital environments network using a unified digital code
JP2015219888A (ja) 電子バリュー管理システム及びプログラム
JP7176680B2 (ja) 販売促進支援システム、販売促進支援方法、及びサーバ装置
JP7237217B1 (ja) 情報処理システム、プログラム及び情報処理方法
CN108831012B (zh) 一种贩售机的售货方法和装置
EP3855377A1 (en) A system and method for exchanging contact information
JP2024035016A (ja) 情報処理装置、情報処理方法、およびプログラム
CN113763078A (zh) 一种信息处理方法、装置和系统
JP2021033635A (ja) プログラム、情報処理方法、及び情報処理装置
JP2024035015A (ja) 情報処理装置、情報処理方法、およびプログラム

Legal Events

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

Ref document number: 19853486

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19853486

Country of ref document: EP

Kind code of ref document: A1