Registration method, verification method, client device, sending card and display screen

Abstract

The present application relates to a registration method, a verification method, a client device, a sending card, and a display screen. The registration method includes: the client device obtains a registration code and a dynamic number, where the registration code is generated by a registration code generation device through first encryption processing of a device identifier, a super permission identifier, and the dynamic number, and the super permission identifier is the unique identifier of the registration code generation device; the client device sends the registration code to the sending card, and the registration code is used to instruct the sending card to perform registration; the client device receives the sending card identifier fed back by the sending card in the case of successful registration, and saves the sending card identifier and the dynamic number. A third-party application software registration code generation device is used to generate the registration code, and the registration code generation device adds a dynamic code, a super permission identifier, and a device identifier to jointly perform encryption, so as to avoid the encryption algorithm being obtained by reverse developers by cracking the system software of the client device, and improve the confidentiality of the registration process.

Description

Technical Field

[0001] This application relates to the technical field of LED display control systems, and particularly to a registration method, a verification method, a client device, a transmitting card, and a display screen. Background Art

[0002] Display screen products communicate with their corresponding control systems and upper computers. However, there are illegal personnel who control the transmitting card through illegal means to display illegal content, causing losses to customers. To improve the security between the display control system and the upper computer, encryption methods are usually adopted. The existing encryption method is to obtain a verification code through encryption algorithm operations using a unique feature code composed of the unique physical ID of the client device and the unique ID of the transmitting card of the control system for encryption. This encryption method is directly implemented on the client device, and the confidentiality is not high enough. Since the verification code is obtained by performing a fixed encryption algorithm on two unique feature codes, the verification code is also a fixed value when the device is fixed. Crackers can analyze the verification code by capturing data packets without having to crack the encryption algorithm, and this method is easily cracked by reverse developers to obtain the encryption algorithm. Summary of the Invention

[0003] Based on this, in view of the above technical problems, it is necessary to provide a registration method, a verification method, a client device, a transmitting card, and a display screen with higher confidentiality.

[0004] In a first aspect, an embodiment of the present application provides a registration method for registering a client device by a transmitting card of a display screen. The registration method includes:

[0005] The client device obtains a registration code and a dynamic number. The registration code is generated by a registration code generation device after performing a first encryption process on a device identifier, a super permission identifier, and the dynamic number. The dynamic number is generated by the registration code generation device. The device identifier is the unique identifier of the client device obtained by the registration code generation device from the client device, and the super permission identifier is the unique identifier of the registration code generation device;

[0006] The client device sends the registration code to the transmitting card of the display screen. The registration code is used to instruct the transmitting card to perform registration, and the transmitting card is used to control the display screen;

[0007] The client device receives the transmitting card identifier feedback by the transmitting card when the registration is successful, and saves the transmitting card identifier and the dynamic number, where the transmitting card identifier is the unique identifier of the transmitting card.

[0008] In the above registration method, the client device does not directly generate the registration code using its own system software. Instead, it uses the registration code generated by the registration code generation device of a third-party application software. Moreover, the registration code generation device adds a dynamic code and a super permission identifier to be encrypted together with the device identifier. The super permission identifier is the unique identifier of the preset registration code generation device, which is stored in the registration code generation device and is not easily obtained by others. Thus, it can prevent the encryption algorithm from being obtained by reverse developers by cracking the system software of the client device, improving the confidentiality of the registration process.

[0009] In a second aspect, an embodiment of the present application provides a registration code generation method, which is applied to a remote service device. The registration code generation method includes:

[0010] The remote service device obtains the device identifier of the client device;

[0011] The remote service device generates a dynamic number;

[0012] The remote service device performs a first encryption process on the device identifier, the dynamic number, and the super permission identifier to obtain a registration code. Among them, the registration code is used for the registration of the client device, and the super permission identifier is the unique identifier of the remote service device.

[0013] In a third aspect, an embodiment of the present application provides a registration method for a sending card of a display screen to register a client device. The sending card is used to control the display screen. The registration method includes:

[0014] The sending card receives the registration code sent by the client device, and the registration code is generated by the registration code generation device;

[0015] The sending card performs a first decryption process on the registration code to obtain the device identifier, the super permission identifier, and the dynamic number. Among them, the device identifier is the unique identifier of the client device, and the super permission identifier is the unique identifier of the registration code generation device;

[0016] If the super permission identifier is consistent with the preset permission identifier, the sending card determines that the registration is successful and saves the device identifier and the dynamic number;

[0017] The sending card sends the sending card identifier to the client device; wherein, the sending card identifier is the unique identifier of the sending card.

[0018] In a fourth aspect, an embodiment of the present application provides a verification method for a sending card of a display screen to verify a client device. The sending card is used to control the display screen. The verification method includes:

[0019] The client device obtains the pre - saved sending card identifier, the pre - saved dynamic number, and the device identifier, where the sending card identifier is the unique identifier of the sending card, and the device identifier is the unique identifier of the client device;

[0020] The client device updates the pre - saved dynamic number using a first update rule;

[0021] The client device performs a second encryption process on the pre - saved sending card identifier, device identifier, and the updated dynamic number to obtain a verification code;

[0022] The client device sends the verification code to the sending card, and the verification code is used to instruct the sending card to verify the client device.

[0023] In the above verification method, before the client device performs a second encryption process on the data each time it needs to initiate a verification with the sending card, it updates the pre - saved dynamic number to a verification dynamic number using the first update rule for the obtained pre - stored dynamic numbers, and then encrypts the sending card identifier, device identifier, and verification dynamic number simultaneously. Since the dynamic number involved in the encryption process is the updated one rather than the pre - stored dynamic number before encryption, it can prevent illegal crackers from cracking the verification code through packet capture analysis, enhancing the confidentiality of the verification method.

[0024] In a fifth aspect, an embodiment of the present application provides a verification method for a sending card of a display screen to verify a client device. The sending card is used to control the display screen, and the verification method includes:

[0025] The sending card receives the verification code sent by the client device;

[0026] The sending card performs a second decryption process on the verification code to obtain the device identifier, the sending card identifier, and the verification dynamic number;

[0027] The sending card obtains the pre - saved dynamic number and updates the pre - saved dynamic number using the first update rule;

[0028] If the verification dynamic number is consistent with the updated dynamic number, the device identifier is consistent with the pre - stored device identifier, and the sending card identifier is consistent with the pre - stored sending card identifier, it is determined that the client device passes the verification.

[0029] In a sixth aspect, an embodiment of the present application provides a registration device for a sending card of a display screen to register a client device. The registration device includes:

[0030] The first acquisition module is used to acquire a registration code and a dynamic number. The registration code is generated by a registration code generation device through first encryption processing on a device identifier, a super permission identifier, and the dynamic number. The dynamic number is generated by the registration code generation device. The device identifier is the unique identifier of the client device obtained by the registration code generation device from the client device, and the super permission identifier is the unique identifier of the registration code generation device.

[0031] The first sending module is used to send the registration code to the sending card of the display screen. The registration code is used to instruct the sending card to perform registration, and the sending card is used to control the display screen.

[0032] The first receiving module is used to receive the sending card identifier feedback by the sending card when the registration is successful, and save the sending card identifier and the dynamic number. The sending card identifier is the unique identifier of the sending card.

[0033] In a seventh aspect, an embodiment of the present application provides a registration code generation device applied to a remote service device. The registration code generation device includes:

[0034] The second acquisition module is used to acquire the device identifier of the client device.

[0035] The dynamic number generation module is used to generate a dynamic number.

[0036] The first encryption module is used to perform first encryption processing on the device identifier, the dynamic number, and the super permission identifier to obtain a registration code. The registration code is used for the registration of the client device, and the super permission identifier is the unique identifier of the remote service device.

[0037] In an eighth aspect, an embodiment of the present application provides a registration device for registering a client device by a sending card of a display screen. The sending card is used to control the display screen. The registration device includes:

[0038] The second receiving module is used to receive the registration code sent by the client device. The registration code is generated by a registration code generation device.

[0039] The first decryption module is used to perform first decryption processing on the registration code to obtain a device identifier, a super permission identifier, and a dynamic number. The device identifier is the unique identifier of the client device, and the super permission identifier is the unique identifier of the registration code generation device.

[0040] The first determination module is used to determine that the registration is successful if the super permission identifier is consistent with a preset permission identifier, and save the device identifier and the dynamic number.

[0041] A second sending module, configured to send a sending card identifier to the client device; wherein, the sending card identifier is the unique identifier of the sending card.

[0042] In a ninth aspect, an embodiment of the present application provides a verification device for a sending card of a display screen to verify a client device, where the sending card is used to control the display screen, and the verification device includes:

[0043] A third obtaining module, configured to obtain a pre-stored sending card identifier, a pre-stored dynamic number, and a device identifier, where the sending card identifier is the unique identifier of the sending card, and the device identifier is the unique identifier of the client device;

[0044] A first updating module, configured to update the pre-stored dynamic number according to a first updating rule;

[0045] A second encryption module, configured to perform a second encryption process on the pre-stored sending card identifier, device identifier, and the updated dynamic number to obtain a verification code;

[0046] A third sending module, configured to send the verification code to the sending card, and the verification code is used to instruct the sending card to verify the client device.

[0047] In a tenth aspect, an embodiment of the present application provides a verification device for a sending card of a display screen to verify a client device, where the sending card is used to control the display screen, and the verification device includes:

[0048] A third receiving module, configured to receive the verification code sent by the client device;

[0049] A second decryption module, configured to perform a second decryption process on the verification code to obtain a device identifier, a sending card identifier, and a verification dynamic number;

[0050] A second updating module, configured to obtain the pre-stored dynamic number and update the pre-stored dynamic number according to a first updating rule;

[0051] A determination module, configured to determine that the client device passes the verification if the verification dynamic number is consistent with the updated dynamic number, the device identifier is consistent with the pre-stored device identifier, and the sending card identifier is consistent with the pre-stored sending card identifier.

[0052] In an eleventh aspect, an embodiment of the present application provides a client device, including a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, the steps of the above first aspect and fourth aspect and any possible method thereof are implemented.

[0053] In a twelfth aspect, an embodiment of the present application provides a sending card, including a controller, the controller includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the steps of the above-mentioned third aspect and fifth aspect and any possible method thereof are implemented.

[0054] In a thirteenth aspect, an embodiment of the present application provides a display screen, including the sending card of the above-mentioned twelfth aspect.

[0055] In a fourteenth aspect, an embodiment of the present application provides a computer storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned first aspect to fifth aspect and any possible method thereof are implemented. Description of the Drawings

[0056] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0057] Figure 1 It is a diagram of the application scenario of the registration method and verification method in an embodiment;

[0058] Figure 2 It is a schematic flowchart of a registration method in an embodiment;

[0059] Figure 3 It is a schematic flowchart of a registration code generation method in an embodiment;

[0060] Figure 4 It is a schematic flowchart of a registration method in an embodiment;

[0061] Figure 5 It is a schematic flowchart of a verification method in an embodiment;

[0062] Figure 6 It is a schematic flowchart of a verification method in an embodiment;

[0063] Figure 7 It is a schematic structural diagram of a sending card, the upper computer software of a client device, and a registration code generation device in an embodiment;

[0064] Figure 8 It is a schematic structural diagram of the encryption module of the registration code generation device in an embodiment;

[0065] Figure 9 It is a schematic diagram of the splicing method of the first original code in an embodiment;

[0066] Figure 10 It is a schematic structural diagram of a registration processing module in an embodiment;

[0067] Figure 11 It is a schematic structural diagram of a verification processing module in an embodiment;

[0068] Figure 12 It is a schematic diagram of the splicing method of the second original code in an embodiment;

[0069] Figure 13 It is a schematic structural diagram of a sending card transceiver module in an embodiment;

[0070] Figure 14 It is a schematic structural diagram of a decryption module of a sending card in an embodiment;

[0071] Figure 15 It is a schematic structural diagram of a verification module of a sending card in an embodiment;

[0072] Figure 16 It is a schematic structural diagram of a locking / unlocking module of a sending card in an embodiment;

[0073] Figure 17 It is an overall flowchart of a registration method in an embodiment;

[0074] Figure 18 It is an overall flowchart of a verification method in an embodiment. Detailed implementation manners

[0075] To facilitate the understanding of the present application, the present application will be described more comprehensively below with reference to the relevant drawings. Embodiments of the present application are given in the drawings. However, the present application can be implemented in many different forms and is not limited to the embodiments described herein. On the contrary, these embodiments are provided to make the disclosure of the present application more thorough and comprehensive.

[0076] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field to which the present application belongs. The terms used in the specification of the present application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application.

[0077] It can be understood that the terms "first" and "second" used in this application are only for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include at least one such feature. The terms "first", "second", etc. may be used in this application to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish a first element from another element. In addition, in the description of this application, "a plurality of" means at least two, such as two, three, etc., unless otherwise specifically defined. In the description of this application, "several" means at least one, such as one, two, etc., unless otherwise specifically defined.

[0078] As described in the background art, the communication confidentiality between the client device and the transmitting card of the display screen control system in the prior art is poor, and the transmitting card is easily manipulated by unauthenticated or illegal software and devices. During the communication process between the client device and the transmitting card, the verification code is easily intercepted and illegally verified to pass, so that the transmitting card can be controlled to display, causing losses to customers.

[0079] Based on the above problems, the present invention proposes a registration and verification method for a client device, effectively improving the communication security between the client device and the transmitting card.

[0080] The registration method and verification method provided by the present invention can be applied in the Figure 1 application scenario as shown. The transmitting card 700 is a control card of the display screen, and its function is to convert and transmit the audio-visual signals of the client device 500 to the display screen. The transmitting card 700 has been encrypted. The client device 500 needs to be verified by the transmitting card 700 to control the transmitting card 700. In the case of failed verification, most modules of the transmitting card 700 cannot work properly, that is, the transmitting card 700 cannot be controlled. To make the transmitting card 700 work properly, communication verification must be carried out first, and the client device 500 must be registered before communication verification, otherwise the transmitting card 700 cannot recognize the client device 500, resulting in verification failure. The registration code generation device 600 is a third-party device outside the client device 500 and the transmitting card 700, and its function is to generate the registration code required for the registration of the client device 500. In Figure 1In the application scenario, the registration code generation device 600 is a remote server, and the registration method is remote registration. The registration code is generated by the remote server, and it is very difficult for crackers to crack the encryption method of the registration code by cracking the system software. During the remote registration process, user participation is required. First, the user finds the device identifier of the client device 500 through the system software of the client device 500, then opens the identifier input interface of the registration code generation device 600, and transfers the device identifier to the registration code generation device 600 through the interface input method. The interface of the registration code generation device 600 will display the generated registration code and a dynamic number. The user then transfers the registration code and the dynamic number to the system software interface of the client device 500 through the interface input method. After receiving the registration code and the dynamic number, the client device 500 sends the registration code to the sending card 700 for registration, and saves the dynamic code at the same time. The dynamic code is used for the verification of the client device 500. After receiving the registration code, the sending card 700 decrypts the registration code to obtain the device identifier, the super permission identifier, and the dynamic number. If the super permission identifier is consistent with the preset permission identifier, the registration is successful. At the same time, the sending card 700 saves the device identifier and the dynamic number, and sends the sending card identifier to the client device 500. The client device 500 saves the sending card identifier and saves the dynamic number obtained from the registration code generation device 600 at the same time, for initiating communication verification to the sending card 700. In another application scenario, the registration code generation device 600 is an application software installed on the client device 500. The registration method is local registration. During the local registration process, the registration code generation device 600 directly obtains the device identifier from the system software of the client device 500 and generates the registration code. The client device 500 then sends the registration code to the sending card 700 through the registration code generation device 600.

[0081] After the client device 500 is registered through the sending card 700, when the client device 500 and the sending card 700 need to communicate, the client device 500 initiates a verification request to the sending card 700. The client device 500 obtains the device identifier, the pre-saved sending card identifier, and the pre-saved dynamic number, updates the pre-saved dynamic number into a verification dynamic number using the first update rule, then performs a second encryption process on the device identifier, the verification dynamic number, and the sending card identifier to obtain a verification code, and sends the verification code to the sending card 700. After decrypting the verification code, the sending card 700 obtains the device identifier, the sending card identifier, and the verification dynamic number, and then updates the dynamic number pre-stored in the sending card 700 using the first update rule. If the updated dynamic number is consistent with the verification dynamic number, the device identifier is consistent with the pre-stored device identifier, and the sending card identifier is consistent with the sending card unique identifier, it is determined that the client device 500 has passed the verification. After the verification is successful, the sending card 700 unlocks the corresponding module so that the client device 500 can control it. If the verification fails, the sending card 700 locks some modules and they cannot work.

[0082] In one embodiment, as Figure 2 shown, a registration method is provided, which is used for a sending card of a display screen to register a client device. The registration method includes the following steps:

[0083] S110. The client device obtains a registration code and a dynamic number.

[0084] Specifically, the registration code is generated after the registration code generation device performs a first encryption process on the device identifier, the super privilege identifier, and the dynamic number. The dynamic number is generated by the registration code generation device. The client device needs to obtain the registration code through the registration code generation device. To generate the registration code, the registration code generation device needs to obtain the device identifier of the device to be registered, that is, the registration code generation device obtains the unique identifier of the client device from the client device. The unique identifier refers to the unique ID sequence set at the factory of the hardware, such as the CPU, network card, chip, etc. The device identifier can be the unique device identifier of a single device or the operation result of the unique device identifiers of multiple devices, as long as it can represent the unique identifier of the client device. The super privilege identifier is an identifier stored in the registration code generation device, that is, it can be understood as the unique identifier of the registration code generation device. The super privilege identifier is the basis for judging whether the client device is successfully registered, and other identifiers cannot be registered. The super privilege identifier can only be obtained through the registration software and will not be directly transmitted for external use. The super privilege identifier will be used inside the registration software to generate the registration code to improve data confidentiality. The dynamic number is a dynamic number randomly generated by the registration code generation device. The registration code generation device encrypts the device identifier, the super privilege identifier, and the dynamic number to generate the registration code. The client device obtains the registration code. Among them, the registration code generation device can be installed on the client device or on other devices. If the registration code generation device is installed on the client device, the registration method is local registration. The registration code generation device can directly obtain the device identifier of the client device, and after generating the registration code, the client device directly obtains the registration code. If the registration code generation device is not installed on the client device, the registration method is remote registration. The registration code generation device obtains the device identifier by means of user interface input, and after generating the registration code, the client device obtains the registration code and the dynamic number by means of user interface input.

[0085] S120. The client device sends the registration code to the sending card, and the registration code is used to instruct the sending card to perform registration.

[0086] Specifically, the sending card is used to control the display of the display screen. If the client device wants to control the display content, it needs to control the sending card. To control the sending card, it needs to pass the verification of the sending card. Before verification, it needs to register with the sending card. Only after successful registration can a verification be initiated to the sending card. The client device sends the registration code to the sending card, and the sending card decrypts the registration code to obtain the verification information for registration, and determines whether the client device can be successfully registered through this verification information.

[0087] S130. The client device receives the sending card identifier feedback by the sending card in the case of successful registration, and saves the sending card identifier and the dynamic number.

[0088] Specifically, the sending card identifier is the unique identifier of the sending card. After the sending card determines successful registration, the client device receives the sending card identifier transmitted by the sending card. The dynamic number can be obtained directly from the registration code generation device by the client device (the registration method is local registration), or can be obtained by means of interface input (the registration method is remote registration). The client device saves the sending card identifier and the dynamic number, and the sending card identifier and the dynamic number are used to initiate a communication verification request to the sending card.

[0089] In the above embodiment, the registration code generation device is used to perform a first encryption process on the device identifier, super permission identifier, and dynamic number of the client device to obtain the registration code. The client device obtains the registration code and the dynamic number through the registration code generation device, and sends the registration code to the sending card. The sending card determines whether the client device is successfully registered according to the registration code. If the registration is successful, the sending card sends the sending card identifier to the client device, and the client device saves the sending card identifier and the dynamic number. The saved sending card identifier and dynamic number are used to send a communication verification request to the sending card. By using the super permission identifier to encrypt with the device identifier and the dynamic number at the same time through the registration code generation device, the super permission identifier is the identifier of the pre-set registration code generation device, and the third-party registration method is adopted to avoid the encryption algorithm being cracked, improving the communication confidentiality between the client device and the sending card.

[0090] In one embodiment, the client device is installed with a registration code generation device. Step S110 specifically includes:

[0091] S111. In response to the registration instruction, the registration code generation device reads the device identifier of the client device and generates a dynamic number.

[0092] S112. The registration code generation device performs a first encryption process on the device identifier, super permission identifier, and dynamic number based on a first preset key to obtain the registration code.

[0093] Specifically, the registration code generation device is installed on the client device. At this time, the registration method is local registration. The registration code is generated by the registration code generation device installed on the client device. After the client device is connected to the sending card, it can be registered with one key through the registration code generation device. The client device generates a dynamic number through the registration code generation device, and then the registration code generation device performs a first encryption process on the device identifier, the super permission identifier, and the dynamic number to directly obtain the registration code. After the registration is completed, the registration code generation device is deleted from the client device to prevent others from obtaining the super permission identifier by cracking the client device software.

[0094] In one embodiment, step S112 specifically includes: the registration code generation device splices the device identifier, the dynamic number, and the super permission identifier to obtain a first original code; the registration code generation device performs a bit transformation process on the first original code to obtain a first transformation code; the registration code generation device adds the first transformation code and a first preset key using single-byte addition operation to obtain the registration code.

[0095] Specifically, in the case where the registration method is local registration, the process of the first encryption process is implemented by the client device through the registration code generation device. The client device splices the device identifier, the dynamic number, and the super permission identifier through the registration code generation device. The splicing order is not limited. It can be spliced in the order of device identifier, dynamic number, and super permission identifier, or it can be spliced in the order of super permission identifier, dynamic number, and device identifier. However, it is necessary to agree with the sending card on the splicing order adopted so that the correct device identifier, dynamic number, and super permission identifier can be obtained after the sending card decrypts. After splicing the device identifier, the dynamic number, and the super permission identifier, the first original code is obtained. The registration code generation device then encrypts the first original code to obtain the registration code. The first original code is a binary number, and its length is not limited. For example, it can be a binary number of 128bit or 256bit. The length of the first original code can be unlimited. If the length of the binary number obtained after splicing does not reach the preset number of bits, data 0 is supplemented at the end to obtain the first original code with the preset length. Then, bit transformation processing is performed on the first original code. Bit transformation processing refers to transforming the positions of the values in the first original code according to a preset transformation method. The preset transformation method is not limited as long as it can transform the character positions in the first original code. After obtaining the first transformation code, the first transformation code is added to the first preset key using single-byte addition operation. The length of the first preset key is the same as the length of the first transformation code. The values in the first transformation code are divided into bytes in the order from the lowest bit to the highest bit. At the same time, the first preset key is also divided into bytes in the order from the lowest bit to the highest bit. Then, the number of bytes of the first transformation code is the same as the number of bytes of the first preset key. The first transformation code and the first preset key are subjected to unsigned addition operation in units of one byte. The encryption operation of each unit is independent, that is, the first byte of the first transformation code is subjected to unsigned addition operation with the first byte of the first preset key, the second byte of the first transformation code is subjected to unsigned addition operation with the second byte of the first preset key, and so on. Finally, the registration code is obtained.

[0096] In one embodiment, the value at the j-th bit of the first original code is the same as the value at the i-th bit of the first transformation code, where j is the i-th array element of the first preset bit transformation array, the length of the first preset bit transformation array, the length of the first original code, and the length of the first transformation code are the same, and both i and j are natural numbers.

[0097] Specifically, the bit transformation formula adopted in this embodiment is: Temp[i] = Scode[BitChange[i]], where Scode[j] is the first original code, Temp[i] is the first transformed code, j = BitChange[i] is the first preset bit transformation array, the values in BitChange[i] are non-repeating integers from 0 to n, the relationship between i and BitChange[i] is the bit transformation relationship, and n is the length of the first original code. In this way, the lengths of the first transformed code, the first original code, and the first preset bit transformation array can be made the same. For a more specific illustration, taking 4-bit transformation as an example, the length of the first original code Sc is 4, Scode[j] represents the value of the j-th bit in 4 bits, the value of j is from 0 to 3, the values in the first preset bit transformation array BitChange are non-repeating values within 0 to 3, that is, the length of BitChange is also 4, and BitChange[i] represents the value of the i-th bit in 4 bits, the value of i is from 0 to 3. Assuming the bit transformation array is BC[4] = {3, 1, 2, 0} and the first original code Sc = 1010, then T[0] = Sc[BC[0]] = Sc[3] = 0, T[1] = Sc[BC[1]] = Sc[1] = 0, T[2] = Sc[BC[2]] = Sc[2] = 1, T[3] = Sc[BC[3]] = Sc[0] = 1, so the first transformed code T = 0011 obtained after bit transformation.

[0098] In one of the embodiments, the length of the first original code Scode is 128, Scode[j] represents the value of the j-th bit in 128 bits, the value of j is from 0 to 127, the values in the first preset bit transformation array BitChange are non-repeating values within 0 to 127, that is, the length of BitChange is also 128, and BitChange[i] represents the value of the i-th bit in 128 bits. After the bit transformation process, the first transformed code Temp is obtained. A single-byte addition operation is performed on the first transformed code Temp and the first preset key SKey. The length of the first transformed code Temp is 128 bits, and starting from the 0th bit (i.e., the lowest bit), every 8 bits are sequentially divided into a byte, so Temp is divided into an intermediate variable Temp1 of 16 bytes. The length of the first preset key SKey is the same as the length of the first transformed code and is also divided into 16 bytes in this way. The single-byte addition operation is performed by adding one byte as a unit. The single-byte addition operation formula is: Rcode[j] = Temp1[j] + SKey[j], where Temp1[j] represents the j-th byte of Temp1, SKey[j] is the j-th byte of SKey, Rcode is the registration code, Rcode[j] is the j-th byte of Rcode, and j is from 0 to 15.

[0099] In one embodiment, step S123 specifically includes: forming a registration code into a registration frame and sending the registration frame to a sending card to initiate a registration request to the sending card. After receiving the registration code, the sending card first performs frame parsing processing on the registration code, and obtains the frame type through the parsing processing. Since the keys used in the registration encryption process and the keys and / or bit transformation arrays used in the subsequent verification encryption process may be different, the frame type can enable the sending card to determine whether the received ciphertext is a registration code or a verification code, so as to select the correct key and bit transformation array to correctly decrypt the registration code. In one of the embodiments, the frame format of the registration frame is shown in Table 1:

[0100] Table 1 Frame format of the registration frame

[0101]

[0102] In one embodiment, as Figure 3 shown, a registration code generation method is provided, which is applied to a remote service device. The registration code generation method includes:

[0103] S510. The remote service device obtains the device identifier of the client device;

[0104] S520. The remote service device generates a dynamic number;

[0105] S530. The remote service device performs a first encryption process on the device identifier, the dynamic number, and the super permission identifier to obtain a registration code, where the registration code is used for the registration of the client device, and the super permission identifier is the unique identifier of the remote service device.

[0106] Specifically, when the registration code generation device is not installed on the client device, it is a remote server. At this time, the registration method adopted by the client device during registration is remote registration, and the remote registration method requires the user to participate in the acquisition and transmission of data. First, the user finds the device identifier of the client device through the system software of the client device to be registered and records the device identifier. Then, the user opens the identifier input interface of the remote server, inputs the device identifier through the interface, and clicks register; after that, the remote service device generates a dynamic number and retrieves the super permission identifier, and then performs a first encryption process on the device identifier, the super permission identifier, and the dynamic number. After generating the registration code, the interface of the remote server will display the generated registration code and the generated dynamic number; after the user records the registration code and the dynamic number, the user then inputs the registration code and the dynamic number into the client device through the system software interface of the client device. After clicking OK, the client device sends the registration code to the registration code for registration, and at the same time, the client device saves the dynamic code, and the dynamic code is used for the verification of the client device. Since the encryption process of the registration code is not performed on the client device, the difficulty of cracking the encryption algorithm is further improved, and the confidentiality of the registration process is enhanced.

[0107] In one embodiment, as Figure 4 shown, a registration method is provided for a sending card of a display screen to register a client device. The sending card is used to control the display screen. The registration method includes the following steps:

[0108] S210. The sending card receives a registration code sent by the client device;

[0109] S220. The sending card performs a first decryption process on the registration code to obtain a device identifier, a super permission identifier, and a dynamic number;

[0110] S230. If the super permission identifier is consistent with a preset permission identifier, the sending card determines that the registration is successful and saves the device identifier and the dynamic number;

[0111] S240. The sending card sends a sending card identifier to the client device.

[0112] Specifically, the client device is a device to be registered. The registration code is generated by a registration code generation device, and its specific generation method has been described above and will not be elaborated here. The sending card identifier is the unique identifier of the sending card. The preset permission identifier is a fixed value preset by the sending card and the registration code generation device. The device identifier is the unique identifier of the client device. After receiving the registration code, the sending card performs a first decryption process on the registration code to obtain the device identifier, the super permission identifier, and the dynamic number. During the process of judging the decrypted information, the sending card only judges whether the decrypted super permission identifier is consistent with the preset permission identifier. If so, the registration is successful, and the sending card saves the decrypted device identifier and the dynamic number. The saved device identifier and dynamic number are the basis for judging whether the verification is passed during the communication verification process. At the same time, the sending card sends the sending card identifier to the client device, and the sending card identifier is used for the client device to initiate verification to the sending card. The method of the first decryption process corresponds to the method of the first encryption process. In one embodiment, the sending card decrypts the verification code based on a first preset key, that is, the key used for encryption and decryption during the registration process is the first preset key

[0113] In a specific embodiment, first, perform an unsigned single-byte subtraction operation on the received registration code Rcode: RTemp[j] = Rcode[j] - SKey[j], where RTemp is the temporary result of the decryption processing subtraction operation, SKey is the first preset key, and the calculation units of RTemp, Rcode, and SKey are all bytes, that is, j is the number of bits of a byte. And the operation of the above formula does not handle carry, so the above calculation is called an unsigned single-byte subtraction operation. After completing the key subtraction, perform the inverse bit transformation of the bit transformation during encryption. This operation is to restore the first original code obtained by the bit transformation during encryption. The principle of the inverse bit transformation is the same as that of the bit transformation, and it is also implemented through a preset inverse bit transformation array UnBitChange. The UnBitChange array swaps the array positions and array values of the preset bit transformation array BitChange. The mathematical expression of UnBitChange is:

[0114] UnBitChange[BitChange[i]] = i,

[0115] The inverse bit transformation calculation formula for the decryption original code Scode is:

[0116] Scode[i] = RTemp[UnBitChange[i]].

[0117] Taking the 4-bit bit transformation in the above description of the encryption method as an example, assume that the bit transformation array is BC[4] = {3, 1, 2, 0}, the first original code Sc = 1010, then the first transformation code T is 0011, and the inverse bit transformation UBC[BC[i]] = i. Let i = 0, 1, 2, 3, and get the array UBC[4] = {3, 1, 2, 0}. The decryption result DS[i] = T[UBC[i]]. Substituting i from 0 to 3 into the calculation, we get DS = 1010, which is the same as the original code Sc.

[0118] In the above embodiment, after the sending card decrypts the registration code, since the preset identifier is a preset fixed value agreed upon by the sending card and the registration code generation device, it is very difficult for others to know this preset super permission identifier. By verifying whether the super permission identifier is consistent with the preset identifier, the sending card can determine whether the client device for registration is the correct control device, avoiding illegal registration and verification of other devices.

[0119] In one embodiment, if the obtained super privilege identifier after decryption is inconsistent with the preset privilege identifier, the registration fails, and the sending card does not save the obtained device identifier and dynamic number after decryption. In this way, the device identifier and dynamic number can be used as verification bases during the communication verification process. In the case of registration failure, the sending card can send the sending card identifier to the client device, or it can not send it, because as long as the sending card does not save the device identifier, the client device cannot pass the verification of the sending card during the subsequent verification process.

[0120] In one implementation manner, step S240 specifically includes: forming a registration feedback frame with the registration result and the sending card identifier, and sending the registration feedback frame to the client device. In one embodiment, the frame format of the registration feedback frame is shown in Table 2.

[0121] Table 2 Frame format of the registration feedback frame

[0122]

[0123] In one embodiment, as Figure 5 shown, a verification method is provided for the sending card of the display screen to verify the client device. The sending card is used to control the display screen. The verification method includes:

[0124] S310. The client device obtains the pre-saved sending card identifier, the pre-saved dynamic number, and the device identifier;

[0125] Specifically, the sending card identifier is the unique identifier of the sending card, and the device identifier is the unique identifier of the client device. After the client device is registered through the sending card, the sending card sends its sending card identifier to the client device, and the dynamic number generated by the registration code generation device during the registration of the client device. The client device saves the sending card identifier and the dynamic number used to initiate verification to the sending card. The client device needs to initiate a verification request to the sending card according to the pre-saved sending card identifier, the pre-saved dynamic number, and the device identifier. It should be noted that after the client device is registered, the pre-saved dynamic number for the first time to send a verification request to the sending card is the dynamic number obtained by the client device from the registration code generation device. Since the pre-saved dynamic number is updated for each verification request, starting from the second verification, the pre-saved dynamic number refers to the updated dynamic number during the previous verification.

[0126] S320. The client device updates the pre-saved dynamic number according to the first update rule.

[0127] The dynamic number used by the client device for encrypted verification code generation is the dynamic number obtained after updating the pre-stored dynamic number, rather than directly using the pre-stored dynamic number for encryption. This can prevent illegal crackers from cracking the verification code through packet capture analysis and enhance the confidentiality of the verification method. The update rule of the dynamic number can be determined according to the required confidentiality level. It can add a preset value to the current dynamic number during each verification, or add a preset value to the initial dynamic number each time, or multiply by a preset value. At the same time, the sending card also pre-stores the program of this update rule, enabling the sending card to update the pre-saved dynamic number according to this update for verifying the verification dynamic number obtained after the sending card decrypts the verification code.

[0128] S330. The client device performs a second encryption process on the pre-saved sending card identifier, the updated dynamic number, and the device identifier to obtain a verification code.

[0129] After the client device updates the dynamic number, it performs a second encryption process on the pre-stored sending card identifier, dynamic number, and device identifier. The method of the second encryption process may be the same as or different from that of the first encryption process, as long as the sending card can decrypt the verification code to obtain the corresponding information.

[0130] S340. The client device sends the verification code to the sending card.

[0131] The verification code is used to indicate the sending card to verify the client device. After the client device generates the verification code, it sends the verification code to the sending card, and the sending card determines whether the client device passes the verification according to the verification code.

[0132] In the above embodiments, before the client device performs a second encryption process on the data each time it needs to initiate a verification to the sending card, it updates the pre-saved dynamic number to the verification dynamic number using the first update rule for all the obtained pre-stored dynamic numbers, and then encrypts the sending card identifier, device identifier, and verification dynamic number at the same time. Since the dynamic number participating in the encryption process is the updated one rather than the pre-stored dynamic number before encryption, it can prevent illegal crackers from cracking the verification code through packet capture analysis and enhance the confidentiality of the verification method.

[0133] In one embodiment, the client device encrypts the pre-stored sending card identifier, the updated dynamic number, and the device identifier using a second preset key to obtain a verification code. The second preset key may be the same as or different from the first preset key. Preferably, the second preset key is different from the first preset key, which can improve the confidentiality of the encryption method.

[0134] In one embodiment, step S322 specifically includes: the client device splices the device identifier, the updated dynamic number, and the pre-saved sending card identifier to obtain a second original code; the client device performs a bit transformation process on the second original code to obtain a second transformation code; the client device uses single-byte addition operation to add the second transformation code and a second preset key to obtain a verification code.

[0135] In this embodiment, the method of the second encryption process is the same as that of the first encryption process. The client device splices the device identifier, the updated dynamic number, and the pre-saved sending card identifier to obtain a second original code. The splicing order is not limited, but it is necessary to agree with the sending card on the adopted splicing order so that the sending card can obtain the correct information after decrypting the verification code. The method of performing a bit transformation process on the second original code and the method of using single-byte addition operation to add the second transformation code and the second original code are the same as the encryption process adopted during the above registration, and the specific process will not be elaborated here. The second preset bit transformation array used for performing the bit transformation process on the second original code may be the same as or different from the first preset bit transformation array. In one embodiment, the second preset bit transformation array used for performing the bit transformation process on the second original code is different from the first preset bit transformation array, which increases the difficulty for others to crack the encryption method of this embodiment.

[0136] In one embodiment, step S330 specifically includes: forming the verification code into a verification frame and sending the verification frame to the sending card to initiate a verification request to the sending card. After receiving the verification code, the sending card first performs a frame parsing process on the verification code, obtains the frame type through the parsing process, and determines the key used to decrypt the verification code based on the frame type, so as to correctly decrypt the verification code.

[0137] In one embodiment, the frame format of the verification frame is shown in Table 3:

[0138] Table 3 Frame format of the verification frame

[0139]

[0140] In one embodiment, as Figure 6 shown, a verification method is provided for the sending card of the display screen to verify the client device. The sending card is used to control the display screen. The verification method includes:

[0141] 410. The sending card receives the verification code sent by the client device;

[0142] 420. The sending card performs a second decryption process on the verification code to obtain the device identifier, the sending card identifier, and the verification dynamic number;

[0143] 430. The sending card obtains the pre - saved dynamic number and updates the pre - saved dynamic number using the first update rule;

[0144] 440. If the verification dynamic number is consistent with the updated dynamic number, the device identifier is consistent with the pre - stored device identifier, and the sending - card identifier is consistent with the pre - stored sending - card identifier, then the sending card determines that the client device passes the verification.

[0145] The verification code is used for the client device to initiate a verification request to the sending card. After receiving the verification code, the sending card performs a second decryption process on the verification code to obtain the device identifier, the sending - card identifier, and the verification dynamic number. The process of the second decryption process is similar to that of the first decryption process and will not be elaborated here. In the registration stage of the client device and when it is determined that the client device registration is successful, the sending card has stored the device identifier and the dynamic number. Whether the client device can pass the verification requires checking whether the device identifier, the sending - card identifier, and the verification dynamic number obtained after decrypting the verification code are respectively consistent with the pre - stored device identifier, the unique identifier of the sending card, and the pre - stored dynamic number in sequence. If they are consistent, the verification passes. It should be noted that the pre - saved dynamic number used by the sending card for the first verification is the device identifier saved after the sending card determines the registration is successful. Starting from the second verification, the pre - saved dynamic numbers used are the updated dynamic numbers from the previous communication verification, that is, each time the sending card goes through a verification process, it replaces the previously saved dynamic number with the updated dynamic number. During verification, if the decrypted device identifier is consistent with the device identifier saved by the sending card after successful registration, the decrypted sending - card identifier is consistent with the unique identifier of the sending card, and the decrypted verification dynamic number is consistent with the updated dynamic number, then the verification is successful.

[0146] In the above - mentioned embodiment, after the sending card decrypts the verification code, since the sending card has pre - stored the device identifier and the dynamic number of the client device that has successfully registered, and devices that have not registered successfully will not save the dynamic number and the device identifier. Based on the pre - stored device identifier, the pre - stored dynamic number, and the unique identifier of the sending card, on the one hand, it can be known whether its encryption method corresponds to the decryption method of the sending card, and at the same time, it can be judged whether the device identifier has been registered to determine whether this verification is an illegal verification, improving the confidentiality of the communication verification process.

[0147] In one embodiment, after step 430, it further includes: forming a verification feedback frame with the verification result and sending the verification feedback frame to the client device. In one of the embodiments, the frame format of the verification feedback frame is shown in Table 4.

[0148] Table 4 Frame format of the verification feedback frame

[0149]

[0150] In one embodiment, the sending card decrypts the verification code based on a second preset key to obtain a device identifier, a sending card identifier, and a verification dynamic number. The second encryption process corresponds to the second decryption process, and the key used for encryption and decryption during the verification process is the second preset key.

[0151] In some embodiments, the first preset key is different from the second preset key. To improve confidentiality, the key used during registration is different from the key used during verification, but the keys used for the encryption and decryption processes during registration are the same, and the keys used for the encryption and decryption processes during verification are the same.

[0152] The following specific embodiments illustrate the specific implementation manners of the present invention:

[0153] Please refer to Figure 7 , the registration generation device includes a device identifier management module, a super permission identifier module, a registration end processing module, a registration end transceiver module, and a storage module. The upper computer software in the client device (i.e., the system software of the client device) includes a registration information module, a device identifier module, a registration processing module, a verification processing module, and a client transceiver module; the sending card includes a sending card transceiver module, a frame parsing module, a feedback frame construction module, a sending card identifier module, a verification module, a decryption module, and a lock / unlock module.

[0154] The function of the device identifier management module is to obtain the client device identifier and provide an acquisition interface for other modules. The super permission identifier module mainly provides a super permission identifier for other modules.

[0155] The registration end processing module is used to generate a registration code. The structure of the registration end processing module is as Figure 8 shown, including: a counter, a splicing module, a bit transformation module, an addition operation module, and a registration frame construction module. The first counter is used to generate a dynamic number. The first splicing module is used to splice the device identifier, the super permission identifier, and the dynamic number to generate a first original code (the splicing method is as Figure 9 shown). The bit transformation is used to encrypt the first original code to obtain a first transformation code of the registration code. The addition operation module is used to add the first transformation code and the first preset key to obtain the registration code. The registration frame construction module is used to form the registration code into a registration frame.

[0156] The registration end transceiver module is the data frame transceiver module of the registration code generation device, and mainly completes the sending of the registration frame and the reception of the registration feedback frame.

[0157] The storage module is used to store the sending card identifier and the dynamic number. During local registration, the client device directly reads the information from the storage module.

[0158] The registration information module is a module for the host computer software of the client device to obtain registration information. During local registration, the sending card identification and dynamic number required for verification are saved in the storage module, and during verification, the registration information module directly reads the registration information required for verification from the storage module. During remote registration, the sending card identification and dynamic number required for verification are saved in the registration processing module, and the verification processing module obtains the sending card identification and dynamic number from the registration processing module.

[0159] The device identification module is a module for obtaining device identification. During local registration, the registration code generation module obtains the device identification from the device identification module through the system interface. During remote registration, the registration processing module obtains the device identification from the device identification module and displays the device identification on the client device interface.

[0160] The registration processing module is the registration management module of the host computer software. As Figure 10 shown, this module includes an information acquisition module, a display module, a registration code input module, and a registration frame creation module. After local registration, the information acquisition module obtains the sending card identification and device identification through the registration information module and transfers them to the registration processing module, then sets the device identification into the device identification module and sets the sending card identification into the verification processing module. During remote registration, the registration processing module notifies the device identification module to obtain the device identification through the system interface and display it in the display module, transfers the device identification to the registration code generation device by means of interface input, the registration code generation device generates a registration code using the device identification and displays the registration code, then inputs the registration code to the registration code input module through the host computer software interface, after the registration processing module obtains the registration code, it forms a registration frame with the registration code in the registration frame creation module and transfers it to the client transceiver module, issues a registration request to the sending card through the client transceiver module, there will be a sending card identification in the feedback frame received after successful registration, and the registration processing module saves the sending card identification to the verification processing module.

[0161] The verification processing module is the core module for the host computer software to initiate communication verification. As Figure 11 shown, the verification processing module includes a second splicing module, a second counter, an encryption module, and a verification frame construction module. After obtaining the pre-saved dynamic number, device identification, and pre-saved sending card identification from other modules, the second counter module adds 1 to the pre-saved dynamic number to obtain an updated dynamic number. The value of the updated dynamic number is, except for the first time which is the dynamic number generated by the registration code generation device +1, in other cases, it is added 1 on the basis of the updated dynamic number when the previous verification was initiated. After reaching the maximum value, the dynamic number is reset to 0 and continues to accumulate; after obtaining the three parameters, they are spliced in the second splicing module to obtain a second original code. The splicing method of the second original code is similar to that of the first original code (as Figure 12As shown, after splicing to obtain the second original code, it is encrypted in the encryption module using the second preset key. The encryption method of the encryption module is the same as that of the registration terminal processing module. After encryption, a verification code is obtained. Finally, the verification frame construction module constructs a communication verification frame and passes it to the client transceiver module for sending.

[0162] The client transceiver module is the receiving and sending module of the host computer software, mainly completing the sending functions of the registration frame and the verification frame, and the receiving and distribution functions of the registration feedback frame and the verification feedback frame. As Figure 13 shown, when sending, neither the registration frame nor the verification frame needs to be processed and is directly sent. When receiving, the frame type parameter of the frame header information needs to be read and passed to the frame judgment module. The frame judgment module judges whether it is a registration feedback frame or a communication verification frame, and then dispatches it to the receiving module of the frame data.

[0163] The sending card transceiver module is the receiving and sending module of the sending card, mainly completing the receiving and dispatching functions of the registration frame and the communication verification frame, and the sending functions of the registration feedback frame and the communication verification feedback frame. The module does not perform any processing on the frame data and only completes the sending and receiving functions.

[0164] The sending card identification module is a module that stores the sending card identification, providing setting and obtaining interfaces for external settings and acquisitions.

[0165] The frame parsing module is the receiving data processing module of the sending card, completing the frame parsing function. Parsing means obtaining the corresponding position data according to the registration frame and the communication verification frame format from the received data, parsing the received registration frame or communication verification frame to obtain the frame type and ciphertext. If the received is a registration frame, the ciphertext is the registration code. If the received is a communication verification frame, the ciphertext is the communication verification code. The parsed frame type is passed to the feedback frame construction module, and at the same time, the frame type and ciphertext are passed to the decryption module.

[0166] The decryption module of the sending card is opposite to the encryption module of the registration code generation device and the host computer software. During the registration process, the keys used for encryption and decryption are the same. During the verification process, the keys used for encryption and decryption are the same. However, the keys for the registration process and the verification process are different, that is, the first preset key and the second preset key are different. And the preset bit transformation arrays used in the registration process and the verification process are also different. The corresponding key and bit transformation array are selected for decryption by receiving the frame type. Although different keys are used, the encryption method is the same. Taking the parsing of the registration code as an example, the structure of the decryption module is as Figure 14As shown in the figure, when the array and key judgment module receives the frame type and the frame type of the registration code is the registration frame, it selects to decrypt using the first key and the first preset bit transformation array. The registration code obtains the first transformation code through the subtraction operation module, the first transformation code obtains the first original code through the inverse bit transformation module, and the first original code obtains the dynamic number, device identifier, and super permission identifier through the clipping module, completing the decryption.

[0167] The verification module is used to verify the information obtained after decrypting the registration code or verification code by the sending card, and perform differentiated verification according to the frame type. The frame type is obtained from the frame parsing module. The structure of the verification module is as Figure 15 shown. To decrypt the registration code, only the super permission identifier needs to be judged, while for the three parameters obtained by decrypting the verification code, all need to be judged. The previously saved dynamic number is incremented by 1 to obtain the updated dynamic number. Verifying that the dynamic number is equal to the updated dynamic number indicates successful verification, that is, the dynamic number after this decryption being equal to the result of adding 1 to the dynamic number judged last time indicates successful verification. The judgment of the device identifier is performed in the first identifier verification module, and it is necessary to read the registered device identifier list and read and judge each identifier for equality. If there is no equality, it indicates that the device initiating the verification is not registered, and "verification unsuccessful" is returned. If equality is judged, it indicates successful verification; the judgment of the super permission identifier and the sending card identifier is performed in the second identifier verification module. For the verification of the super permission identifier obtained by decryption, it is necessary to judge the registration frame. If it is a registration frame, it is not necessary to verify the dynamic number and device identifier obtained by decryption. It is only necessary to verify whether the super permission identifier obtained by decryption is consistent with the preset super permission identifier. If the super permission identifier verification passes, the dynamic number and device identifier are saved; otherwise, the dynamic number and device identifier are not saved. Finally, the verification module sends the registration result to the feedback frame construction module and the lock / unlock module; if it is a communication verification frame, it is necessary to obtain the sending card identifier from the sending card identifier module and make an equality judgment with the received sending card identifier. If they are equal, it indicates that the sending card identifier verification passes. Only when both the dynamic number and device identifier verifications pass does it indicate that the communication verification passes. After the communication verification passes, the saved dynamic number is replaced with the dynamically updated number this time as the judgment basis for the next verification.

[0168] The main function of the feedback frame construction module is to construct the registration feedback frame and the communication verification feedback frame. The specific type of the feedback frame is determined by the frame type parameter passed by the frame parsing module. When it receives the verification result passed by the verification module, it starts to construct the feedback frame. The registration feedback frame needs to obtain the sending card identifier from the sending card identifier module. After completing the construction of the feedback frame according to the feedback frame structure, it is directly passed to the sending card transceiver module for sending.

[0169] The lock / unlock module is as Figure 13As shown, this module is used to configure the modules that require verification for the sending card to work properly, and to lock or unlock the modules that require verification to work properly according to the verification results. At the same time, the communication port is checked by the port check module to detect whether the communication port has changed. The locking configuration method is to add an unlocking judgment before each module starts. Otherwise, when this function is executed, it will directly jump out, which is equivalent to not doing any processing for this module, resulting in the module not working properly. The verification result is directly converted into unlocking and locking state parameters for setting. By detecting the change of the communication port, a communication verification notice is sent to the host computer software and the sending card is locked, mainly detecting the plugging and unplugging of the communication port and the change of the port number.

[0170] The overall process in the registration stage is as Figure 17 As shown, when the registration code generation device is installed on the client device, the device identification management module obtains the device identification of the client device through the system interface and passes it to the registration end processing module; the registration end processing module reads the preset super permission identifier from the super permission identifier module, the counter module in the registration end processing module generates a dynamic number, and the registration end processing module performs encryption processing based on the super permission identifier, device identification and dynamic number to obtain the registration code. The registration code is formed into a registration frame and sent to the sending card transceiver module through the registration end transceiver module. The sending card transceiver module passes the registration frame to the frame parsing module to parse out the frame type and registration code. The frame type is passed to the feedback frame construction module, and the registration code is passed to the decryption module for decryption. After decryption, the super permission identifier, device identification and dynamic number are obtained. The super permission identifier is passed to the verification module for verification. If the registration verification passes, the device identification and dynamic number are saved, otherwise they are not saved. At the same time, the feedback frame construction module is notified to obtain the sending card identification from the sending card identification module. The registration result and the sending card identification are formed into a registration feedback frame and the registration feedback frame is sent to the registration end transceiver module. After receiving the registration feedback frame, the registration end transceiver module parses the feedback frame to obtain the registration result and the sending card identification and passes them to the storage module. After receiving the registration result and the sending card identification, if the registration fails, the storage module prompts the registration failure. If the registration is successful, the sending card identification, device identification and dynamic number are saved to the registration file together and the registration success is prompted.

[0171] If the registration device is not installed on the client device, the device identification module obtains the device identification of the client device through the system interface; it is passed to the device identification management module through the interface input method. The device identification management module transmits the device identification to the registration end processing module. The registration end processing module reads the preset super authority identification from the super authority identification module and generates a dynamic number through the counter module. The registration end processing module encrypts the super authority identification, device identification and dynamic number to obtain a registration code, and displays the registration code and dynamic number on the interface. The registration code and dynamic number are passed to the registration processing module of the client device's host computer software through the interface input method. The registration processing module composes a registration frame and sends it to the sending card transceiver module through the client transceiver module, sending a registration request to the sending card.

[0172] The overall process in the verification phase is as follows Figure 18 As shown, after successful registration, the host computer software initiates a communication verification frame. First, the verification processing module of the host computer software obtains the device identification from the device identification module, obtains the pre-saved dynamic number and the sending card identification from the registration processing module, and updates the pre-saved dynamic number through the counter. Among them, the pre-saved dynamic number of each verification request will be accumulated by 1 based on the new dynamic number generated last time. After reaching the maximum value, it will continue to accumulate 1 from 0. The device ID, the sending card ID, and the second dynamic number are concatenated and then encrypted to generate a verification code. A verification frame is constructed based on the verification code. The verification frame is sent to the sending card transceiver module via the client transceiver module. After receiving the verification frame, the sending card transceiver module passes it to the frame parsing module to parse the frame type and verification code. The frame type is passed to the feedback frame construction module. The verification code is passed to the decryption module for decryption to obtain the device ID, the sending card ID, and the verification dynamic number. The device ID, the sending card ID, and the verification dynamic number are passed to the verification module for verification information. If the verification passes, the locking / unlocking module removes the restrictions on some modules of the sending card, allowing them to operate normally. The feedback frame construction module receives the verification result of the verification module, obtains the sending card ID, constructs a feedback frame, and sends it to the sending card transceiver module to the client transceiver module. If the verification fails, the locking / unlocking module removes the restrictions on some modules of the sending card. At the same time, the verification module composes a feedback frame indicating that the verification failed and sends it to the sending card transceiver module to the client transceiver module. After receiving the communication verification frame, the client transceiver module feeds it back to the verification processing module for parsing to obtain the verification result and display it on the interface.

[0173] It should be understood that although Figures 1 - 6 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figures 1 - 6At least some of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential but can be executed alternately or in rotation with at least some of the steps or stages in other steps or other steps.

[0174] In one embodiment, a registration device is provided for a sending card of a display screen to register a client device. The registration device includes:

[0175] A first acquisition module, configured to acquire a registration code and a dynamic number. The registration code is generated by a registration code generation device after performing a first encryption process on a device identifier, a super permission identifier, and the dynamic number. The dynamic number is generated by the registration code generation device. The device identifier is the unique identifier of the client device acquired by the registration code generation device from the client device, and the super permission identifier is the unique identifier of the registration code generation device.

[0176] A first sending module, configured to send the registration code to the sending card of the display screen. The registration code is used to instruct the sending card to perform registration, and the sending card is used to control the display screen.

[0177] A first receiving module, configured to receive the sending card identifier fed back by the sending card when the registration is successful, and save the sending card identifier and the dynamic number. The sending card identifier is the unique identifier of the sending card.

[0178] In one embodiment, a registration code generation device is provided, which is applied to a remote service device. The registration code generation device includes:

[0179] A second acquisition module, configured to acquire the device identifier of the client device.

[0180] A dynamic number generation module, configured to generate a dynamic number.

[0181] A first encryption module, configured to perform a first encryption process on the device identifier, the dynamic number, and the super permission identifier to obtain a registration code. The registration code is used for the registration of the client device, and the super permission identifier is the unique identifier of the remote service device.

[0182] In one embodiment, a registration device is provided for a sending card of a display screen to register a client device. The sending card is used to control the display screen. The registration device includes:

[0183] A second receiving module, configured to receive the registration code sent by the client device. The registration code is generated by the registration code generation device.

[0184] The first decryption module is used to perform the first decryption process on the registration code to obtain the device identifier, the super permission identifier, and the dynamic number, where the device identifier is the unique identifier of the client device, and the super permission identifier is the unique identifier of the registration code generation device;

[0185] The first determination module is used to determine that the registration is successful if the super permission identifier is consistent with the preset permission identifier, and save the device identifier and the dynamic number;

[0186] The second sending module is used to send the sending card identifier to the client device; where the sending card identifier is the unique identifier of the sending card.

[0187] In one embodiment, a verification device is provided for the sending card of the display screen to verify the client device. The sending card is used to control the display screen. The verification device includes:

[0188] The third acquisition module acquires the pre-saved sending card identifier, the pre-saved dynamic number, and the device identifier, where the sending card identifier is the unique identifier of the sending card, and the device identifier is the unique identifier of the client device;

[0189] The first update module is used to update the pre-saved dynamic number according to the first update rule;

[0190] The second encryption module is used to perform the second encryption process on the sending card identifier, the updated dynamic number, and the device identifier to obtain the verification code;

[0191] The third sending module sends the verification code to the sending card, and the verification code is used to instruct the sending card to verify the client device.

[0192] In one embodiment, a verification device is provided for the sending card of the display screen to verify the client device. The sending card is used to control the display screen. The verification device includes:

[0193] The third receiving module is used to receive the verification code sent by the client device;

[0194] The second decryption module is used to perform the second decryption process on the verification code to obtain the device identifier, the sending card identifier, and the verification dynamic number;

[0195] The second update module is used to obtain the pre-saved dynamic number and update the pre-saved dynamic number according to the first update rule;

[0196] The determination module is used to determine that the client device passes the verification if the verification dynamic number is consistent with the updated dynamic number, the device identifier is consistent with the pre-stored device identifier, and the sending card identifier is consistent with the pre-stored sending card identifier.

[0197] In one embodiment, a client device is provided, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the steps of the method executed by the above client device are implemented.

[0198] In one embodiment, a sending card is provided, including a controller. The controller includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the steps of the method executed by the above sending card are implemented.

[0199] In one embodiment, a display screen is provided, including the sending card mentioned in any one of the above embodiments.

[0200] In one embodiment, a computer storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method in any one of the above embodiments are implemented.

[0201] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0202] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0203] The above embodiments only represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the appended claims.

Claims

1. A registration method, characterized in that, A registration client device for a sending card of a display screen, and the registration method includes: The client device obtains a registration code and a dynamic number. Among them, the registration code is generated by a registration code generation device after performing a first encryption process on the device identifier, the super permission identifier, and the dynamic number. The dynamic number is generated by the registration code generation device. The device identifier is the unique identifier of the client device obtained by the registration code generation device from the client device, and the super permission identifier is the unique identifier of the registration code generation device; The client device sends the registration code to the sending card of the display screen. The registration code is used to instruct the sending card to perform registration, and the sending card is used to control the display screen; The client device receives the sending card identifier fed back by the sending card in the case of successful registration, and saves the sending card identifier and the dynamic number. Among them, the sending card identifier is the unique identifier of the sending card.

2. The registration method according to claim 1, characterized in that, The client device is installed with the registration code generation device; The client device obtaining the registration code and the dynamic number includes: In response to a registration instruction, the registration code generation device reads the device identifier of the client device and generates a dynamic number; The registration code generation device performs a first encryption process on the device identifier, the super permission identifier, and the dynamic number based on a first preset key to obtain a registration code.

3. The registration method according to claim 2, wherein The registration code generation device performing a first encryption process on the device identifier, the super permission identifier, and the dynamic number based on a first preset key to obtain a registration code includes: The registration code generation device splices the device identifier, the dynamic number, and the super permission identifier to obtain a first original code; The registration code generation device performs a bit transformation process on the first original code to obtain a first transformation code; The registration code generation device adds the first transformation code and the first preset key using single-byte addition operation to obtain a registration code.

4. According to the registration method described in claim 3, wherein The value of the j-th bit of the first original code is the same as the value of the i-th bit of the first transformation code, where j is the i-th array element of a first preset bit transformation array. The lengths of the first preset bit transformation array, the first original code, and the first transformation code are the same, and both i and j are natural numbers.

5. A registration code generation method, characterized in that, Applied to a remote service device, the registration code generation method includes: The remote service device obtains the device identifier of the client device; The remote service device generates a dynamic number; The remote service device performs a first encryption process on the device identifier, the dynamic number, and the super permission identifier to obtain a registration code. Among them, the registration code is used for the registration of the client device, and the super permission identifier is the unique identifier of the remote service device.

6. A registration method, characterized in that, A registration client device for a sending card of a display screen, the sending card is used to control the display screen, and the registration method includes: The sending card receives the registration code sent by the client device, and the registration code is generated by a registration code generation device; The sending card performs a first decryption process on the registration code to obtain a device identifier, a super privilege identifier, and a dynamic number, where the device identifier is the unique identifier of the client device, and the super privilege identifier is the unique identifier of the registration code generation device; If the super privilege identifier is consistent with a preset privilege identifier, the sending card determines that the registration is successful and saves the device identifier and the dynamic number; The sending card sends a sending card identifier to the client device; where the sending card identifier is the unique identifier of the sending card.

7. A verification method, characterized in that, A sending card for a display screen verifies a client device, and the sending card is used to control the display screen. The verification method includes: The client device obtains a pre-saved sending card identifier, a pre-saved dynamic number, and a device identifier, where the sending card identifier is the unique identifier of the sending card, and the device identifier is the unique identifier of the client device; the sending card identifier is obtained by the client device according to the registration method described in any one of claims 1 to 4; The client device updates the pre-saved dynamic number using a first update rule; The client device performs a second encryption process on the pre-saved sending card identifier, device identifier, and updated dynamic number to obtain a verification code; The client device sends the verification code to the sending card, and the verification code is used to instruct the sending card to verify the client device.

8. The verification method according to claim 7, wherein The client device performing a second encryption process on the pre-saved sending card identifier, device identifier, and updated dynamic number to obtain a verification code includes: The client device splices the device identifier, the updated dynamic number, and the pre-saved sending card identifier to obtain a second original code; The client device performs a bit transformation process on the second original code to obtain a second transformation code; The client device adds the second transformation code and a second preset key using a single-byte addition operation to obtain a verification code.

9. A verification method, characterized in that, A sending card for a display screen verifies a client device, and the sending card is used to control the display screen. The verification method includes: The sending card receives the verification code sent by the client device; The sending card performs a second decryption process on the verification code to obtain a device identifier, a sending card identifier, and a verification dynamic number; the sending card identifier is obtained by the client device according to the registration method described in any one of claims 1 to 4; The sending card obtains a pre-saved dynamic number and updates the pre-saved dynamic number using a first update rule; If the verification dynamic number is consistent with the updated dynamic number, the device identifier is consistent with a pre-stored device identifier, and the sending card identifier is consistent with a pre-stored sending card identifier, the sending card determines that the client device passes the verification.

10. A registration device, characterized in that, A sending card for a display screen registers a client device, and the registration device includes: A first acquisition module, configured to acquire a registration code and a dynamic number, where the registration code is generated by a registration code generation device through first encryption processing on a device identifier, a super permission identifier, and the dynamic number, the dynamic number is generated by the registration code generation device, the device identifier is the unique identifier of the client device acquired by the registration code generation device from the client device, and the super permission identifier is the unique identifier of the registration code generation device; A first sending module, configured to send the registration code to a sending card of a display screen, where the registration code is used to instruct the sending card to perform registration, and the sending card is used to control the display screen; A first receiving module, configured to receive a sending card identifier fed back by the sending card when the registration is successful, and save the sending card identifier and the dynamic number, where the sending card identifier is the unique identifier of the sending card.

11. A registration code generation device, characterized in that, Applied to a remote service device, the registration code generation device includes: A second acquisition module, configured to acquire the device identifier of the client device; A dynamic number generation module, configured to generate a dynamic number; A first encryption module, configured to perform first encryption processing on the device identifier, the dynamic number, and the super permission identifier to obtain a registration code, where the registration code is used for registration of the client device, and the super permission identifier is the unique identifier of the remote service device.

12. A registration device, characterized in that, For a sending card of a display screen to register a client device, the sending card is used to control the display screen, and the registration device includes: A second receiving module, configured to receive a registration code sent by the client device, where the registration code is generated by a registration code generation device; A first decryption module, configured to perform first decryption processing on the registration code to obtain a device identifier, a super permission identifier, and a dynamic number, where the device identifier is the unique identifier of the client device, and the super permission identifier is the unique identifier of the registration code generation device; A first determination module, configured to determine that the registration is successful if the super permission identifier is consistent with a preset permission identifier, and save the device identifier and the dynamic number; A second sending module, configured to send a sending card identifier to the client device; where the sending card identifier is the unique identifier of the sending card.

13. A verification device, characterized in that, For a sending card of a display screen to verify a client device, the sending card is used to control the display screen, and the verification device includes: A third acquisition module, which acquires a pre-saved sending card identifier, a pre-saved dynamic number, and a device identifier, where the sending card identifier is the unique identifier of the sending card, and the device identifier is the unique identifier of the client device; the sending card identifier is acquired by the client device according to the registration method according to any one of claims 1 to 4; A first update module, configured to update the pre-saved dynamic number according to a first update rule; A second encryption module, configured to perform second encryption processing on the pre-saved sending card identifier, the device identifier, and the updated dynamic number to obtain a verification code; A third sending module, which sends the verification code to the sending card, and the verification code is used to instruct the sending card to verify the client device.

14. A verification device, characterized in that, A verification client device for a sending card of a display screen, the sending card being used to control the display screen, the verification device comprising: A third receiving module, configured to receive a verification code sent by the client device; A second decryption module, configured to perform a second decryption process on the verification code to obtain a device identifier, a sending card identifier, and a verification dynamic number; the sending card identifier is obtained by the client device according to the registration method described in any one of claims 1 to 4; A second update module, configured to obtain a pre-stored dynamic number and update the pre-stored dynamic number using a first update rule; A second determination module, configured to determine that the client device passes the verification if the verification dynamic number is consistent with the updated dynamic number, the device identifier is consistent with a pre-stored device identifier, and the sending card identifier is consistent with a pre-stored sending card identifier.

15. A client device, characterized in that, Comprising a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the steps of the method described in any one of claims 1-4 or 7 or 8 are implemented.

16. A sending card, characterized in that, Comprising a controller, the controller comprises a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the steps of the method described in claim 6 or 9 are implemented.

17. A display screen, characterized in that, Comprising a sending card as described in claim 16.

18. A computer storage medium, on which a computer program is stored, characterized in that, When the computer program is executed by the processor, the steps of the method described in any one of claims 1-9 are implemented.

Images