TWI810454B - Method for transferring service-bound device and system thereof - Google Patents

Abstract

A method for transferring service-bound device and a system thereof are provided. The method is used to transfer a service-bound first device to a second device. In one aspect, a binding code is generated by the second device, and the first device read the binding code from the second device; or alternatively, the binding code can be generated by the first device, and the second device read the binding code from the first device. The method is operated in a serving system. The serving system receives the binding code from the first device after authenticating its user, and also receiving the binding code from the second device. After verifying the binding codes from the both parties, it confirms that the service-bound device can be transferred to another. After the serving system receives binding data from the second device, the service-bound device is transferred to the second device successful.

Description

Method and system for transfer service binding device

The description discloses a method for binding a device, in particular a method and system for transferring a device bound to a certain service to another device.

Under the requirements of information security, many services with higher security requirements require users to designate a device to access a service, such as mobile devices, computer devices, etc. Users cannot only use traditional account numbers and passwords to access services , but you need to use the device bound when registering the service to access related services.

In conventional technologies, such as financial-related services with high security requirements, when registering to use the service, the user will be required to bind a certain device, such as a mobile device, and bind it to the server during the registration process During the program, the mobile device will send the unique machine serial number (such as International Mobile Equipment Identity, IMEI) or the serial number of a specific hardware component to the server, and the server will set the user to use only this mobile device under a specific service access services.

Since the bound device is restricted to access a certain service or link to a certain website, illegal intruders cannot enter the door, and the security is relatively improved. However, when there is a need to switch the bound device, such as mobile device damage or loss Or changing the phone, relatively complex procedures are required to transfer the bound device. Generally speaking, the server needs to re-authenticate the user and execute the process of binding the device again.

In view of the fact that due to security considerations in the conventional technology, there must be a cumbersome process for transferring the device originally bound to the service, the manual discloses a method and system for transferring the service bound device, providing a transfer binding with both security and convenience For the device solution, in the above embodiment, the first device is originally bound to a specific service, and the second device is a new bound device that the user wants to replace the original first device.

According to an embodiment, a method for transferring a service binding device is operated in a server system for transferring a bound first device to bind a second device, in the method, receiving a binding code from the second device, and After the user's identity is authenticated by the first device, the binding code is received from the first device, and after the binding code is verified, the convertible binding is confirmed with the second device. When the server system receives the binding data uploaded by the second device After that, the binding of the second device is completed.

Further, when the server system agrees to bind the second device, the second device uploads the binding request, binding data and binding code, and executes a binding procedure after being confirmed by the server system.

In one embodiment, a binding program is executed in the second device to generate a one-time binding code and send it to the server system; at the same time, it can be read by the first device in the form of a one-dimensional barcode, two-dimensional barcode or wireless identification code , to obtain the binding code, the wireless identification code can be delivered in various ways, such as NFC (Near Field Communication), sound waves and infrared rays. After the user logs into the server system through the first device, a session is established. During the session, the server system receives the binding code from the first device, and after verifying the binding code before and after, agrees to bind the second device.

In another embodiment, the binding program can be executed in the first device to generate the binding code and send it to the server system, and it can also be a one-dimensional barcode, two-dimensional barcode or wireless identification code, and then read by the second device A binding code generated by the first device. Afterwards, when the user logs into the server system through the first device, a session is established. During this session, the server system can receive the binding code from the first device, and after verifying the binding code before and after, agree to bind the second device.

Further, when the second device executes the binding procedure, it requests the binding from the server system, and repeatedly and periodically asks the server system whether the binding can be changed until receiving confirmation that the binding can be changed or until a time limit is reached.

According to an embodiment of the system for transferring a service binding device, the system includes a server system, which includes an authentication module and a binding module realized by software and matching hardware to run the method for transferring a service binding device. In another embodiment, the authentication module and the binding module can be independent servers.

The system provides a service program for the first device to execute a service program for logging into the server system, provides a binding program for the second device to execute the binding program, and transmits data to the server system, and the server system executes all The method for binding the device with the transfer service described above.

Further, when the second device is successfully bound, the server system may cancel the original binding relationship of the first device. In another solution, even if the process of transferring and binding to the second device has been completed, the binding relationship originally bound to the first device can still be retained according to requirements.

In order to further understand the features and technical content of the present invention, please refer to the following detailed description and drawings related to the present invention. However, the provided drawings are only for reference and description, and are not intended to limit the present invention.

The implementation of the present invention is described below through specific specific examples, and those skilled in the art can understand the advantages and effects of the present invention from the content disclosed in this specification. The present invention can be implemented or applied through other different specific embodiments, and various modifications and changes can be made to the details in this specification based on different viewpoints and applications without departing from the concept of the present invention. In addition, the drawings of the present invention are only for simple illustration, and are not drawn according to the actual size, which is stated in advance. The following embodiments will further describe the relevant technical content of the present invention in detail, but the disclosed content is not intended to limit the protection scope of the present invention.

It should be understood that although terms such as "first", "second", and "third" may be used herein to describe various elements or signals, these elements or signals should not be limited by these terms. These terms are mainly used to distinguish one element from another element, or one signal from another signal. In addition, the term "or" used herein may include any one or a combination of more of the associated listed items depending on the actual situation.

The manual discloses a method and system for transferring service-bound devices, providing a convenient and secure device transfer solution, that is, allowing users to use devices that have been bound to specific services (such as financial services, etc.) (embodiment Called the first device), the transfer is bound to another device (the second device).

For example, when a user wants to access a network service, such as financial services: transfer, inquiry, purchase of financial products, digital payment, etc., the server system may require the user to bind this service to the user's first device , when binding, the user will be required to upload personal data, device information (such as the hardware serial number), and set a password. After completion, the device binding will be completed, and the user can only use this first device to access the bound services. Later, when the user wants to transfer the bound device, such as buying a new machine (second device), to transfer the device bound by the service to the second device, a request for re-binding is required, and the transfer proposed by the disclosure The method of the service binding device provides a solution to transfer and bind a first device originally bound to a specific service to a second device.

For the system architecture implementing the method for the transfer service binding device, reference may be made to the schematic diagram of a system embodiment of the transfer service binding device shown in FIG. 1 .

The figure shows that a user 100 operates a first device 101 and a second device 102. The first device 101 is schematically represented as a device originally bound to a server system service, and the second device 102 is used to replace the first device originally bound to the service. 101. The first device 101 and the second device 102 are connected to the server system through the network 10. At the server system end, it may include a server host 12 for processing network packets, as well as software and matching hardware (such as network, server, The service module 121 , the binding module 123 and the authentication module 125 realized by database, etc.).

The service module 121 is a software module that provides services for the system side, and can also be a server that operates independently, such as financial services. The specified second device 102 accesses the service. The authentication module 125 is a software module used by the server system to authenticate the identity of the user 100 and the device, and can process the binding request sent by the user end, and can also be an independent server. The binding module 123 is a software module in the server system that processes the programs for binding devices, and can also be a server running independently at the system end.

The server system executes the transfer service binding device method through the authentication module 125 and the binding module 123. At the terminal, the server system provides a service program executed on the first device 101, such as an application program (APP) in a mobile device, or It is a program provided through a web page, allowing the user 100 to log in to the server system with this service program, and the server system provides services after authenticating the user 100 (including the authentication device). The server system provides a binding program that executes binding on the second device 102, or also provides the binding program to the first device 101, which is used to execute a binding program, and can transmit data to server system.

For the method for transferring a service binding device through the server system described in the above embodiments, reference may be made to the flowchart embodiment diagram shown in FIG. 2 .

The figure shows a server system 20 , and a first device 101 and a second device 102 connected through a network, wherein the first device 101 is a device originally bound to the service provided by the server system 20 . When the second device 102 is to be used as the binding device instead of the first device 101, in this example, the binding program is executed in the second device 102, and a program such as random number generation is executed to generate a one-time binding code, The binding code can be coded to generate the binding code 202 as shown in the figure, and other encoding patterns or wireless identification codes are not excluded to represent the binding code. The wireless identification code can be transmitted in various ways, such as NFC (Near Field Communication), sound waves and infrared rays.

According to the flow shown in the figure, after the second device 102 generates the binding code through the executed program, upload the binding code to the server system 20 (step S201), the binding code can be a string, after encoding, according to this example, form the binding code 202 displayed on the second device 102, and start the scanner reading by the first device 101, as shown in the figure, the binding code 201 displayed on the first device 101 (step S203), the first device 101 Upload the binding code obtained by scanning the two-dimensional barcode to the servo system 20 (step S205 ).

It is worth mentioning that the coding pattern displayed on the second device 102 can be a one-dimensional barcode, or the one-time binding code can be directly displayed on the screen in the form of a character string, and then filled into another device, that is, The first device 101. According to yet another embodiment, when the second device 102 encodes the binding code as a wireless identification code, such as broadcasting by Near Field Communication (NFC), the first device 101 starts the corresponding communication module (such as an NFC module) and the software reader Take this wireless identification code and decode it to get the binding code.

When the server system 20 receives the binding code uploaded by the first device 101 and the second device 102 within a certain period of time, such as a session (session), after verifying that the binding code is correct, for example, compare the two binding codes If they are consistent, a message may be sent to the second device 102 that issued the binding request, indicating that the binding is agreed (step S207 ). At this time, the second device 102 executes the binding program and performs a binding process, including uploading the binding request, binding data and the current binding code (step S209), and after being confirmed by the server system 20, the rebinding is completed. At this time, the second device 102 may send a message indicating that the binding is completed (step S211 ). On the other hand, the server system 20 may send another message to the original binding first device 101, notifying the completion of transfer binding (step S213).

As far as the server system is concerned, FIG. 3 shows a flowchart of an embodiment of a method for transferring a service binding device executed in the server system.

In the server system, according to the binding code transmitted by the first device (which may include device binding data and user login data) and the second device (which may include a binding request) in the above embodiment, and the database records Confirm whether the user agrees to transfer the binding information, that is, complete the transfer binding procedure within a certain time limit.

The user intends to use the second device to replace the first device originally bound to the server system service. In the first embodiment, the user operates the second device to generate a binding code, and then uses the first device to read the binding code; The second embodiment is to operate the first device to generate the binding code, and then use the second device to read the binding code. In this way, after the first device or the second device generates the binding code, it can be coded into a one-dimensional barcode, two-dimensional barcode or wireless identification code, or a character string, and then read (or input) by another device, and After decoding, the binding code is obtained. In the beginning, no matter which way, the first device and the second device have the same binding code.

In this process, the user uses the first device of the original binding device to log in to the server system, the server system can authenticate the first device and its user identity according to the information sent by the first device (step S301), and receive the binding code from the second device (step S303), and also receive a binding code from the first device (step S305). The order of the above steps S301, S303 and S305 is not used to limit the method flow, and the order can be changed.

Next, in the server system, it is verified whether the binding codes received within a period of time are the same by comparing the binding codes (step S307 ), and if the verification fails, the user will be notified of the transfer binding failure. When the verification is successful, the server system confirms the convertible binding with the second device (step S309), and receives from the second device the necessary information for re-binding the second device, such as hardware information about the device (step S311), through After the registration is completed, the binding of the second device is completed (step S313 ).

What is mentioned here is that, in one embodiment, when the second device is successfully bound, the server system can cancel the binding relationship of the first device that was originally bound, wherein the server system can delete the binding relationship of the related first device. set data, or unbound with the mark; but in another embodiment, the binding of the second device can be added, that is, even if the process of transferring and binding to the second device has been completed, it can still be According to the requirements, the original binding relationship of the first device is retained. The embodiment can also be extended to bind multiple devices at the same time, and the server system will keep the binding information of multiple binding devices at the same time.

Fig. 4 then shows an embodiment diagram of the process of running on the transfer service binding device system. The system is provided with an authentication module 43 and a binding module 44. The authentication module 43 and the binding module 44 can be realized by combining software with hardware, or as a standalone server. The authentication module 43 is used to identify the identity of the user, and receives the code of device binding uploaded by the authenticated user, and provides the binding module 44 to query the binding code, and the binding module 44 is used to process the data uploaded by the terminal device to perform Bound program. The system provides software programs for the first device 41 and the second device 42 to execute device binding. In this embodiment, the first device 41 is a device originally served by the bound system, and the second device 42 is to replace the first device 41 devices.

In the process of this embodiment, the second device 42 first generates a binding code through the binding program provided by the system (step S401), then sends a binding request to the authentication module 43, and uploads the newly generated binding code (step S401). S403). Once the information requesting binding is sent to the server system and the binding code is uploaded, the second device 42 can repeatedly and regularly ask the server system (authentication module 43) whether the binding can be converted until receiving confirmation that the binding can be converted, or until a time limit is reached. It should be mentioned here that the action of the second device 42 inquiring the server system may start from when it first decides to execute the transfer binding device, or from generating the binding code. If the authentication module 43 fails to obtain sufficient information of the transfer binding provided by the first device 41 within the time limit, the process is terminated.

On the other hand, the user first operates the first device 41, including authenticating the identity in the machine, which can refer to verifying the identification ID, password, and biometric feature, and can also obtain the information of the authentication device at this time. The user operates the first device 41 to log in to the system, and the authentication module 43 processes the procedures for authenticating the user and the device (step S405). Once the login is confirmed, the identity authentication is completed (step S407). At this time, the server system can The binding request sets a session (session), which means that the entire program can set a time limit, and is used to confirm that the incoming and outgoing information is within the session.

The embodiment shows that at this time the first device 41 obtains the binding code from the second device 42 (step S409), and also uploads the obtained binding code to the authentication module 43 (step S411). The sequence of steps S403, S409, and S411 in this embodiment is not used to limit the process of transferring the bound device. Moreover, the first device 41 can also generate the binding code first, and then obtain it from the second device 42. After that, the authentication module The group 43 verifies the binding code uploaded by the first device 41 and the second device 42. During the process, the second device 42 continuously inquires the authentication module 43 to confirm whether the binding can be performed, and the binding transfer is completed after confirmation.

Afterwards, the server system receives the binding code from the first device 41 and the second device 42 during the current session through the authentication module 43, stores it, and verifies the binding code before and after (step S413). After the verification confirms the correctness, That is, agree to bind the second device, and send the consent binding information to the second device 42 (step S415 ). At this time, the second device 42 generates a binding request and relevant binding materials through a software program, that is, transmits the binding request, the binding code and the binding data to the binding module 44 of the server system (step S417), wherein, The binding module 44 will inquire whether the authentication module 43 has completed the verification and can re-bind the device (step S419). After confirmation, the binding is agreed (step S421), and the second device 42 can also be notified of the successful binding information (step S423).

According to the description of the above embodiments, at the beginning of the process of the transfer service binding device method proposed in the disclosure, the binding code can be generated by the first device 41 or the second device 42, and then the system verifies the binding code uploaded by the two devices , and confirm the completion of the transfer procedure of the bound device accordingly. According to yet another embodiment, cross-device verification can also be achieved through the process of the above embodiment, wherein, if the binding code is first generated by the second device 42, the binding code is then sent to the first device 41 that has logged into the system. When the system verifies the binding codes uploaded by the two devices, it also verifies the second device 42 synchronously while completing the transfer service binding device, so that the second device 42 can automatically log in to the system, but the second device 42 that has been unbound A device 41 may be logged out by the system.

According to the embodiment, if the binding code is generated by the first device 41 that can log into the system, it will also be sent to the second device 42 in the same way, so that the system can verify the binding code and complete the transfer service binding device at the same time, Similarly, the second device 42 is also authenticated, so that the second device 42 can log in to the system synchronously. Similarly, when the second device 42 is bound and logs in to the system, the system can also actively log out of the first device 41 that was originally logged in.

FIGS. 5A-5E are schematic diagrams showing an embodiment of the flow of the user operating the first device 51 and the second device 52 to complete the transfer service binding device.

FIG. 5A shows a second device 52. When requesting binding, the second device 52 can display on its screen the required data fields for logging in to the system, including user name 501, password 502, and login 503. However, this embodiment shows that the user selects the device replacement 504 in this screen. At this time, as shown in FIG. 5B , the second device 52 executes the code generating program, and forms a two-dimensional barcode 505 through encoding. At the same time, this binding code can be uploaded to the servo system.

In FIG. 5C, the first device 51 starts to scan the scanning window 506 of the two-dimensional barcode 505. As shown in FIG. 5D, the first device 51 captures and obtains the two-dimensional barcode 507, obtains the binding code after decoding, and uses the function of sending 508 to upload server system.

Then the second device 52 is required to upload the data for binding, and it is shown in FIG. 5E that the second device 52 has completed the binding and can continue to obtain various services.

To sum up, the method and system for transferring service-bound devices proposed in the above-mentioned embodiments is used to handle the transfer of bound devices. It is different from the conventional method that when the user proposes to transfer the binding, the system needs to go through a large number of The incoming and outgoing information confirms the identity of the user and the newly bound device. The method of transferring the service and binding the device is completed through the code used for security trust between devices. The conventional system requires many steps to ensure that the transfer and binding is a safe and sound process.

The content disclosed above is only a preferred feasible embodiment of the present invention, and does not therefore limit the scope of the patent application of the present invention. Therefore, all equivalent technical changes made by using the description and drawings of the present invention are included in the application of the present invention. within the scope of the patent.

10: Internet 101: First device 102: Second device 100: user 12:Servo host 121: Service Module 125: Authentication module 123: Binding module 20:Servo system 201, 202: binding code 41: First device 42: Second device 43:Authentication module 44: Binding Module 51: First device 52: Second device 501: Username 502: Password 503: login 504: Device replacement 505, 507: 2D barcode 506: Scan window 508: send Steps S201-S213: method flow for transferring service-bound devices Steps S301-S313: method flow for transferring service-bound devices Steps S401-S423: method flow for transferring service-bound devices

FIG. 1 shows a schematic diagram of a system embodiment of a transfer service binding device;

Fig. 2 shows a flow chart of an embodiment of a method for transferring a service binding device;

FIG. 3 shows a flowchart of an embodiment of a method for transferring a service binding device;

Fig. 4 shows a diagram of an embodiment of the process running on the transfer service binding device system; and

FIG. 5A-FIG. 5E show flowcharts of an embodiment of a method for transferring a service binding device.

20:Servo system

101: First device

201,202: binding code

102: Second device

Claims (15)

A method for transferring a service binding device, operating in a server system, for transferring a bound first device to a second device, comprising: the server receiving a one-time form from the second device Binding code, wherein the second device executes a binding program to generate the one-time binding code, or the second device reads from the first device the one-time form generated by the first device executing the binding program binding code; after the server system authenticates a user identity through the first device, it receives the one-time binding code from the first device, wherein the first device executes the binding program to generate the one-time binding code, Or the first device reads the one-time binding code generated by the second device executing the binding program from the second device; the server system compares the one-time binding code uploaded from the first device and the second device respectively The one-time binding code, after successfully verifying the one-time binding code uploaded from the first device and the second device respectively, confirms convertible binding with the second device; and the server system receives the second After the device uploads the binding data, the binding of the second device is completed. The method for transferring a service binding device as described in Claim 1, wherein, after the server system agrees to bind the second device, the second device uploads a binding request, the binding data, and the one-time binding set the code. The method for transferring a service binding device as described in claim 2, wherein after the user logs in the server system through the first device, a session is established, and the server system receives the session from the first device during the session The one-time binding code, after verifying the one-time binding code before and after, agrees to bind the second device. The method for transferring a service binding device as described in claim 3, wherein the second device executes the binding program, requests binding from the server system, and repeatedly inquires The server is asked whether it can switch bindings until a confirmation switchable binding message is received, or a time limit is reached. The method for transferring a service binding device as described in claim 3, wherein the one-time binding code is uploaded via the second device, and the server system is repeatedly and regularly asked whether the binding can be converted, until receiving confirmation that the binding can be converted information, or until a time limit is reached. The method for transferring a service binding device according to any one of claims 1 to 5, wherein, when the binding of the second device is completed, the server system cancels the binding relationship with the first device. The method for transferring a service binding device according to any one of claims 1 to 5, wherein, when the binding of the second device is completed, the server system retains the binding relationship with the first device. The method for transferring a service binding device as described in any one of claims 1 to 5, wherein, after the first device or the second device generates the one-time binding code, the code is a one-dimensional barcode, a The two-dimensional barcode or a wireless identification code is read by another device and decoded to obtain the one-time binding code. The method for transferring a service binding device according to any one of claims 1 to 5, wherein, after the first device or the second device generates the one-time binding code, it is displayed on a screen in the form of a character string on another device. A system for transferring service binding equipment, comprising: a server system, including an authentication module and a binding module, to run a method for transferring service binding equipment; a service program executed on a first device, used When logging into the server system; a binding program executed on the first device or a second device for executing a binding program and sending data to the server system; wherein the transfer running in the server system Methods for service binding devices include: In the authentication module, a one-time binding code is received from the second device, wherein the second device executes the binding program to generate the one-time binding code, or the second device receives the one-time binding code from the first device Read the one-time binding code generated by the first device executing the binding program; after authenticating a user identity through the first device, receive the one-time binding code from the first device, wherein the first The device executes the binding program to generate the one-time binding code, or the first device reads from the second device the one-time binding code generated by the second device executing the binding program; in the authentication mode In the group, comparing the one-time binding code uploaded from the first device and the second device respectively, after successfully verifying the one-time binding code uploaded from the first device and the second device respectively, and The second device confirms that the binding can be converted; and in the binding module, after receiving the binding data uploaded by the second device, the binding of the second device is completed. The system for transferring service binding equipment as described in claim 10, wherein after the user logs in the server system through the first device, a session is established, and the server system receives from the first device during the session The one-time binding code, after verifying the one-time binding code before and after, agrees to bind the second device. The system for transferring service binding equipment as described in claim item 11, wherein the second device executes the binding program, requests binding from the server system, and repeatedly and regularly asks the server system whether the binding can be switched until receiving The convertible binding information is confirmed, or until a time limit is reached. The system for transferring service binding equipment as described in claim 11, wherein the one-time binding code is uploaded via the second device, and the server system is repeatedly and periodically asked whether the binding can be converted until receiving confirmation that the binding can be converted information, or until a time limit is reached. In the system for transferring a service binding device according to any one of claims 10 to 13, when the binding of the second device is completed, the server system cancels the binding relationship with the first device. The system for transferring a service binding device according to any one of claims 10 to 13, wherein, when the binding of the second device is completed, the server system retains the binding relationship with the first device.

Images