CN109145527B - IP soft core property protection and infringement identification method based on USB3.1 protocol TS2 training sequence - Google Patents

Abstract

The invention provides an IP soft core property rights protection and infringement identification method based on the USB3.1 protocol TS2 training sequence, wherein the IP soft core property rights protection method based on the USB3.1 protocol TS2 training sequence is applied to a USB3.1 device, including: detecting whether Meet the trigger condition of the preset protection identification mode; if so, switch the current working state to the protection identification mode; wherein, in the working state of the protection identification mode, and in the Polling.Configuration state and/or Recovery. The reserved bytes of the TS2 training sequence sent from the Configuration state to the USB host carry protection identification information. The present invention effectively realizes the intellectual property protection and identification of the USB3.1 soft core by deeply binding with the USB3.1 protocol.

Description

IP Soft Core Property Rights Protection and Infringement Identification Based on USB3.1 Protocol TS2 Training Sequence method

technical field

The present invention relates to the technical field of silicon intellectual property rights of USB devices, in particular to a method and device for protecting property rights of an IP soft core based on a TS2 training sequence of the USB3.1 protocol, and an IP soft core based on the TS2 training sequence of the USB3.1 protocol. Infringement identification method and device, and corresponding storage medium and electronic equipment.

Background technique

USB is the abbreviation of Universal Serial Bus (Universal Serial Bus) in English. It is an external bus standard used to regulate the connection and communication between computers and external devices. The USB interface supports plug-and-play and hot-plugging of the device. The USB standard was jointly proposed by Intel, Compaq, IBM, Microsoft and other companies at the end of 1994, and has been widely used in various electronic devices such as computers, mobile phones, and digital cameras. The USB standard is formulated and maintained by USB-IF, an official USB organization. Since the beginning, five versions of USB1.1, USB2.0, USB3.0, USB3.1 and USB3.2 have been released in sequence. The new version is forward compatible with the old version. . The maximum transfer rate supported by each version is distributed as follows: USB1.1: 12Mbps; USB2.0: 480Mbps; USB3.0: 5Gbps; USB3.1: 10Gbps; USB3.2: 20Gbps.

Silicon Intellectual Property (SIP, Silicon Intellectual Property) refers to a pre-defined, verified reusable module in the chip (IC) industry that can perform specific functions. As the complexity and integration of chips increase, processors, memories, I/O ports, and analog circuits are all integrated on one silicon chip to form a complete system on chip (SOC, System On Chip). Each module of the SOC product must be designed from scratch and then integrated and verified, which will inevitably lead to a prolonged development cycle, and the quality of the design will be difficult to control. Therefore, reusing pre-designed and validated integrated circuit modules (IP) is the most efficient solution in the industry today.

From the design process, IP can be divided into three types: soft core, solid core, and hard core:

1. Soft IP (Soft IP)

In the process of logic IC design, the IC designer will use the hardware description language to write the functions required by the system out of the register transfer level (RTL, Register Transfer Level) program after the system specification is completed. This RTL file is called It is an IP soft core.

Since the IP soft core is provided in the form of source code, it has high flexibility and can be modified by the user to realize the required circuit system design, and has nothing to do with the specific implementation process, but the disadvantage is that independent intellectual property rights are not easy to obtain. Protection, especially for standard protocol IP (such as USB3.1), even if the code is encrypted, customers can still use the encrypted code of the same IP repeatedly in different SOC projects.

2. IP solid core (Firm IP)

After the RTL program is verified by simulation and meets the design requirements, the designer selects the corresponding logic gate from the Cell Library with the help of Electronic Design Automation Tool (EDA), and converts the RTL file into a network presented in the form of logic gate units. Table (Netlist) file, this netlist file is the so-called IP solid core.

The IP solid core is a compromise between the IP soft core and the IP hard core. It is more reliable than the IP soft core and more flexible than the IP hard core, but it cannot be logically modified according to customer needs like the IP soft core.

3. Hard IP

After the netlist file is verified, enter the step of physical design, first perform the location configuration design (Floor Planning) of the functional block, and then perform the layout and routing design (Place&Routing), and the GDSII file generated after the physical layout and routing is completed. , which is the IP hard core.

The design and process of the IP hard core have been completed and cannot be modified. The IP hard core obtained by the user is only a product function rather than a product design. Therefore, the design and manufacturer of the IP hard core exercise full control over it. Compared with the IP soft core and the IP solid core, the intellectual property protection of the IP hard core is relatively simple.

USB3.1 IP is a widely used standard IP, and it is necessary to take effective measures to protect its intellectual property. However, there are few research solutions for IP soft core protection of USB3.1 devices in the field.

SUMMARY OF THE INVENTION

In view of the above-mentioned shortcomings of the prior art, the purpose of the present invention is to provide an IP soft-core property rights protection and infringement identification method based on the USB3.1 protocol TS2 training sequence, which is used to solve the problem of IP soft-core IP protection of USB3.1 devices in the prior art. The technical issues of intellectual property protection for soft cores.

In order to achieve the above purpose and other related purposes, the present invention provides a IP soft core property rights protection method based on the USB3.1 protocol TS2 training sequence, applied to a USB3.1 device, the method includes: detecting whether a preset protection identification is satisfied The trigger condition of the mode; if so, switch the current working state to the protection identification mode; wherein, in the working state of the protection identification mode, and in the Polling.Configuration state and/or Recovery.Configuration state to the USB host The reserved bytes of the sent TS2 training sequence carry protection identification information.

In an embodiment of the present invention, the triggering condition of the preset protection identification mode includes: triggering condition 1) receiving a reserved byte sent by a USB host in the Polling.Configuration state and/or Recovery.Configuration state to carry TS2 training sequence with specific information; and/or trigger condition 2) receiving a user test link management data packet carrying specific information sent by the USB host in the U0 state; wherein, when the trigger condition 1) is satisfied , the USB3.1 device correspondingly enters the Polling.Configuration state and/or the Recovery.Configuration state, and sends the TS2 training sequence carrying the protection identification information in the reserved bytes to the USB host; when the trigger condition 2 is satisfied ), the USB3.1 device enters the Recovery.Configuration state, and sends a TS2 training sequence carrying protection identification information in the reserved bytes to the USB host.

In an embodiment of the present invention, the step of sending the TS2 training sequence to the USB host in the Polling.Configuration state and/or the Recovery.Configuration state further includes: periodically sending the TS2 training sequence that carries the protection information in the reserved bytes. Sequence; wherein, the protection identification information in the period is arranged in chronological order to form authorized customer name, product batch information, and/or authorized time information.

In an embodiment of the present invention, the reserved byte is the fifth byte of the TS2 training sequence.

In an embodiment of the present invention, the protection identification information is generated in advance using ASCII code encoding.

In an embodiment of the present invention, the method further includes: exiting the protection identification mode after re-powering on or receiving a reset request sent by the USB host.

In order to achieve the above purpose and other related purposes, the present invention provides an IP soft core infringement identification method based on the USB3.1 protocol TS2 training sequence, which is applied to a USB protocol analysis device. The method includes: capturing the USB3.1 device for protection identification TS2 training sequence sent to the USB host in the working state of the mode and in the Polling.Configuration state and/or Recovery.Configuration state; extract the protection identification information in the reserved bytes of the TS2 training sequence; determine the protection identification Whether the information matches the preset protection identification information; if not, it is determined that the USB3.1 device is infringing.

In an embodiment of the present invention, the method further includes: if the protection identification information does not exist in the reserved bytes of the TS2 training sequence, determining that the USB3.1 device is not a target device.

In an embodiment of the present invention, the method further includes: continuously capturing the TS2 training sequences for a certain period of time or a certain number; extracting the protection identification information of each of the captured TS2 training sequences, and converting the protection identification information Arrange in chronological order to restore the authorized customer name, product batch information, and/or authorization time information; determine whether the authorized customer name, product batch information, and/or authorization time information is the same as that of the USB3.1 device. The corresponding information of the manufacturer matches; if not, it is determined that the USB3.1 device is infringing.

In an embodiment of the present invention, the step of extracting the captured protection identification information of each of the TS2 training sequences and arranging them in chronological order further includes: using ASCII code to decode each protection identification information; The protection identification information after the code is arranged in chronological order.

In order to achieve the above object and other related objects, the present invention provides an IP soft core infringement identification method based on the USB3.1 protocol TS2 training sequence, which is applied to a USB host, and the method includes: in Polling.Configuration state and/or Recovery. In the Configuration state, send a TS2 training sequence with specific information in the reserved bytes to the USB3.1 device, and check whether the USB3.1 device enters the protection identification mode; if not, it is determined that the USB3.1 device is not the target device; and/or in the U0 state, send a user test link management data packet carrying specific information to the USB3.1 device, and check whether the USB3.1 device enters the protection identification mode; if not, it is determined that the USB3.1 devices are not target devices.

In order to achieve the above purpose and other related purposes, the present invention provides an IP soft core property rights protection device based on the USB3.1 protocol TS2 training sequence, which is applied to USB3.1 equipment. The device includes: a mode conversion module for detecting whether Meet the triggering condition of the preset protection identification mode; if so, switch the current working state to the protection identification mode; the sequence sending module is used to be in the working state of the protection identification mode, and in the Polling.Configuration state and / or the Recovery.Configuration state sends the TS2 training sequence with the protection identification information in the reserved bytes to the USB host.

In order to achieve the above object and other related purposes, the present invention provides an IP soft core infringement identification device based on the USB3.1 protocol TS2 training sequence, which is applied to a USB protocol analysis device. The device includes: a sequence capture module for capturing USB3 .1 The TS2 training sequence sent by the device to the USB host in the state of Polling.Configuration and/or Recovery.Configuration under the working state of the protection identification mode; an information extraction module for extracting the reserved words of the TS2 training sequence The protection identification information in the section; the infringement identification module is used to judge whether the protection identification information matches the preset protection identification information; if not, it is determined that the USB3.1 device is infringing.

In order to achieve the above purpose and other related purposes, the present invention provides an IP soft core infringement identification device based on the USB3.1 protocol TS2 training sequence, which is applied to a USB host. The TS2 training sequence with specific information in the reserved bytes is sent to the USB3.1 device in the state and/or Recovery.Configuration state; and/or used to send the user test carrying the specific information to the USB3.1 device in the U0 state Link management data packet; infringement identification module, used to check whether the USB3.1 device enters the protection identification mode; if not, it is determined that the USB3.1 device is not a target device.

In order to achieve the above object and other related objects, the present invention provides a storage medium, in which a computer program is stored, and when the computer program is loaded and executed by a processor, any one of the above methods is implemented.

In order to achieve the above object and other related objects, the present invention provides an electronic device, comprising: a communicator, a processor, and a memory; wherein, the communicator is used to establish a communication connection between the electronic device and an external device; the memory used to store a computer program; the processor is used to load and execute the computer program, so that the electronic device executes any of the above methods.

As mentioned above, the IP soft core property rights protection and infringement identification method based on the USB3.1 protocol TS2 training sequence of the present invention is based on the USB3.1 protocol, and an embedded protection identification code is added to the TS2 training sequence, so that the USB3.1 The IP soft core of the device performs effective intellectual property protection. At the same time, an infringement identification technology for this intellectual property protection scheme is provided. When the IP soft core is used or made into a product without authorization, the infringement identification and proof can be carried out by triggering the protection identification code.

Description of drawings

FIG. 1 is a schematic flowchart of an IP soft core protection method based on a TS2 training sequence of the USB3.1 protocol according to an embodiment of the present invention.

FIG. 2A is a schematic structural diagram of a user test link management data packet according to an embodiment of the present invention.

FIG. 2B is a schematic diagram showing the transition between the Polling sub-states of USB 3.1 according to an embodiment of the present invention.

FIG. 3 is a schematic flowchart of an IP soft core infringement identification method based on the TS2 training sequence of the USB3.1 protocol according to an embodiment of the present invention.

FIG. 4 is a schematic flowchart of an IP soft core infringement identification method based on the TS2 training sequence of the USB3.1 protocol according to another embodiment of the present invention.

FIG. 5 is a schematic block diagram of an IP soft core protection device based on the TS2 training sequence of the USB3.1 protocol according to an embodiment of the present invention.

FIG. 6 is a schematic block diagram of an IP soft core infringement identification device based on the TS2 training sequence of the USB3.1 protocol according to an embodiment of the present invention.

FIG. 7 is a schematic block diagram of an IP soft core infringement identification device based on the TS2 training sequence of the USB3.1 protocol according to another embodiment of the present invention.

FIG. 8 is a schematic structural diagram of an electronic device in another embodiment of the present invention.

Detailed ways

The embodiments of the present invention are described below through specific specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments may be combined with each other under the condition of no conflict.

It should be noted that the drawings provided in the following embodiments are only used to illustrate the basic concept of the present invention in a schematic way, so the drawings only show the components related to the present invention rather than the number, shape and number of components in actual implementation. For dimension drawing, the type, quantity and proportion of each component can be changed at will in actual implementation, and the component layout may also be more complicated.

Referring to FIG. 1 , this embodiment provides a property rights protection method for an IP soft core based on the TS2 training sequence of the USB3.1 protocol, which is used to effectively protect the intellectual property rights of the IP soft core of a USB3.1 device (Device). Here, a USB3.1 device refers to all devices connected to a USB host (Host) through a USB3.1 interface, such as a common U disk, a card reader, a mobile hard disk, an external recorder, and the like. The method is executed by the USB3.1 device, and specifically includes the following steps:

S11: Detect whether the trigger condition of the preset protection identification mode is met. If the detection result is yes, execute step S12; otherwise, keep the current working state unchanged.

S12: Switch the current working state to the protection identification mode.

S13: In the working state of the protection identification mode, and in the Polling.Configuration state and/or the Recovery.Configuration state, the reserved bytes of the TS2 training sequence sent to the USB host carry protection identification information.

Steps S11 to S13 will be explained in detail below.

In the normal working mode, the USB3.1 device will not send the protection identification information. Only when the specific trigger conditions are met, the USB3.1 device will enter the protection identification mode, and insert the protection identification information into the TS2 training sequence sent later. , or send the TS2 training sequence that carries the protection identification information in advance. That is to say, in the present invention, the USB3.1 device sends the TS2 training sequence carrying the protection identification information to the outside. As for when the protection identification information is embedded in the TS2 training sequence, there is no specific limitation. It can also be embedded before leaving the factory.

The two trigger conditions for entering the protection identification mode are listed below:

Trigger condition 1. 1) Receive one or a certain number of TS2 training sequences with specific information in the reserved bytes sent by the USB host in the Polling.Configuration state, and/or, 2) Receive the Recovery.Configuration state The reserved bytes sent by the USB host carry one or a certain number of TS2 training sequences with specific information.

Trigger condition 2: Receive one or a certain number of user test link management data packets that carry specific information and are sent by the USB host in the U0 state.

When the above trigger condition 1) is satisfied, the USB3.1 device enters the Polling.Configuration state accordingly, and sends a TS2 training sequence carrying protection identification information in the reserved bytes to the USB host; when the above trigger condition 2 is satisfied ), the USB3.1 device correspondingly enters the Recovery.Configuration state, and sends the TS2 training sequence carrying the protection identification information in the reserved bytes to the USB host.

When the second trigger condition is satisfied, the USB3.1 device enters the Recovery.Configuration state, and sends a TS2 training sequence carrying protection identification information in the reserved bytes to the USB host. Figure 2A shows the format of a Vendor Device Test Link Management Packet, the specific information is located in DWORD1 and/or DWORD2, when the USB3.1 device receives the Vendor Device Test Link Management Packet containing this specific information After managing the packets, enter the protection identification mode and enter the Recovery state.

In trigger condition 1 and trigger condition 2, the specific information may be preset uppercase and lowercase letters, numbers or punctuation marks, or may be a character string formed by combining several of them.

As we all know, from the power-on of the link to the normal operation (similar to inserting the USB3.1 U disk into the USB3.1 interface of the notebook until the data can be read normally), it needs to go through three stages: Rx.Detect, Polling, U0, in which, the Polling (polling) process will perform relevant initialization settings on the terminal devices on the link (that is, it means that the Host and Device are initializing the sender and receiver and synchronizing to prepare for sending data packets); The process from Rx.Detect to U0 needs to go through several sub-processes, including the sending of the TS2 training sequence in the Polling.Configuration sub-state: the two devices send the TS2 training sequence to each other to set relevant parameters, and send and receive to the designated After the number of TS2 training sequences, the handshake is completed, and the next sub-state Poll.Idle is entered; after the initialization of the entire link is completed, it will enter the U0 stage (normal working state, with data packets sent and received on the link). In addition, the USB3.1 communication protocol stipulates that the initiator or receiver will enter the Recovery (recovery) state after the link has a recoverable error or exit the low-power state, and before entering the working state, and will repeat the transmission in this state. TS2 training sequence, the initiator or receiver can know that it has entered the Recovery (recovery) state or has exited the low power consumption state when receiving the TS2 training sequence sent by the other party.

Following the above, according to the USB3.1 protocol, the TS2 training sequence will be sent in the Polling.Configuration and Recovery.Configuration sub-states, and the handshake will be completed. Figure 2B shows the USB3.1 jump between the Polling sub-states, in which Polling.Configuration It is a sub-state that USB3.1 must go through to enter the working state, so inserting the reserved identification code in the TS2 training sequence can effectively protect and identify IP.

Table 1 shows the format of the TS2 training sequence of the USB3.1 protocol, and its length is 16 bytes. In this embodiment, the fifth symbol bit of the TS2 training sequence (that is, the symbol number 4 in Table 1) is preferably used as the reserved byte to carry protective identification information. The reason is: according to the USB3.1 protocol, the reserved byte is set to zero by default when the sender sends it, and the receiver does not check it after receiving it. Therefore, using the reserved byte No. 4 to carry the protection identification information will not affect the USB3.1 device. normal work.

Table 1

According to the definition of the TS2 training sequence, there is one byte of space in a TS2 training sequence that can carry reserved identification information. Therefore, in one embodiment, the encoding method of American Standard Code for Information Interchange (ASCII, American Standard Code for Information Interchange) is adopted. , each byte is represented as a capital letter, number or punctuation mark. After the USB3.1 device enters the protection identification mode, the identification information is inserted into the reserved bytes of the continuous TS2 training sequence to complete the marking of the device . The so-called marking the device means that after our USB3.1 device enters the protection identification mode, it has protection identification information in the reserved bytes of the TS2 training sequence, while other USB3.1 devices do not have this function, so that we can Effectively differentiate our equipment from other equipment. At this time, if a USB3.1 device does not enter the protection identification mode after meeting the trigger conditions, it means that the USB3.1 device does not use our IP soft core, and there is no infringement problem.

Since a TS2 training sequence can only carry one byte of identification information, in an implementation example, the identification information is inserted letter by letter and sent periodically. Protected identification information can include information such as IP authorized client name, authorized batch and time. For example, if the authorized customer is A, the authorized batch is B, and the authorization time is C, the protection identification information is ABC. Three TS2 training sequences are sent in one cycle, the protection identification information carried in the reserved bytes of the first TS2 training sequence sent is A, and the protection identification information carried in the reserved bytes of the second TS2 training sequence sent It is B, and the protection identification information carried by the reserved bytes of the third TS2 training sequence sent is C, where A to C are respectively located in the 5th byte of each TS2 training sequence, and exist in the form of ASCII codes , namely: 01000001, 01000010, and 01000011, respectively.

In another embodiment, after step S13, the method further includes: exiting the protection identification mode after re-powering on or receiving a reset request sent by the USB host.

Referring to FIG. 3 , this embodiment provides an IP soft core infringement identification method based on the USB3.1 protocol TS2 training sequence, which is used to effectively identify the IP soft core of the USB3.1 device in the foregoing method embodiment. The method is executed by a USB protocol analysis device, and the USB protocol analysis device refers to an electronic device with a USB protocol analysis function, such as a USB protocol analyzer and the like. The method specifically includes the following steps:

S31: Capture the TS2 training sequence sent to the USB host in the Polling.Configuration state and/or Recovery.Configuration state in the working state of the USB3.1 device under test in the protection identification mode.

The USB3.1 device under test is connected to the USB host for communication, the USB protocol analysis device records the behavior on the USB3.1 interface, and captures the USB3.1 device under test in the protection identification mode, in Polling.Configuration state and/or Recovery.Configuration state TS2 training sequence sent to the USB host.

S32: Extract the protection identification information in the reserved bytes of the TS2 training sequence.

Obviously, if there is no protection identification information in the reserved bytes of the captured TS2 training sequence, it can be determined that the USB3.1 device under test is not our device, and there is no infringement problem.

S33: Determine whether the protection identification information matches the preset protection identification information; if not, execute step S34; otherwise, execute step S35.

The preset protection identification information may be preset uppercase and lowercase letters, numbers, or punctuation marks, and may also be a character string formed by combining several of them. When the extracted protection identification information matches the preset protection identification information, it means that the USB3.1 device is our product.

S34: Determining that the USB3.1 device infringes.

S35: Determine that the USB3.1 device is not infringing.

In one embodiment, step S31 continuously captures a certain time or a certain number of TS2 training sequences, and step S32 extracts the protection identification information in each of the TS2 training sequences and decodes it using ASCII code, and decodes the decoded data. Each of the protection identification information is arranged in sequence, so as to restore the authorized customer name, product batch information, and/or authorization time information, and step S33 judges whether the authorized customer name, product batch information, and/or authorization time information is It matches the corresponding information of the manufacturer of the USB 3.1 device (namely, the product batch, and/or the authorization time). If it does not match, it is determined that the USB 3.1 device under test is infringing.

Referring to FIG. 4 , this embodiment provides another IP soft core infringement identification method based on the USB3.1 protocol TS2 training sequence, which is used to effectively identify the IP soft core of the USB3.1 device in the foregoing method embodiment. The method is executed by a USB host, and the USB host refers to an electronic device such as a desktop computer, a notebook computer, etc., which has a USB3.1 interface and can be connected and communicated with a USB3.1 device. The method specifically includes the following steps:

S41: In the Polling.Configuration state and/or Recovery.Configuration state, send a TS2 training sequence with specific information in the reserved bytes to the USB3.1 device, and/or, in the U0 state, send to the USB3.1 device User test link management packets carrying specific information.

S42: Check whether the USB3.1 device enters the protection identification mode; if not, execute step S43; otherwise, execute the method described in the embodiment of FIG. 3, and then judge the infringement situation.

S43: It is determined that the USB3.1 device is not the target device, that is, the tested USB3.1 device is not our product, and there is no infringement problem.

Referring to FIG. 5 , similar to the principle of the method embodiment shown in FIG. 1 , this embodiment provides an IP soft core property rights protection device 500 based on the USB3.1 protocol TS2 training sequence. The device is installed as a software product on a USB3.1 device. , so as to implement all or part of the steps in the method embodiment shown in FIG. 1 at runtime. Specifically, the apparatus 500 includes the following modules:

The mode conversion module 501 is used to detect whether the trigger condition of the preset protection recognition mode is met; if so, switch the current working state to the protection recognition mode; further, the mode conversion module 501 is also used to detect the USB3.1 After the device is powered on again or receives a reset request sent by the USB host, it exits the protection identification mode.

The sequence sending module 502 is configured to send the TS2 training sequence carrying the protection identification information in the reserved bytes to the USB host in the working state of the protection identification mode and in the Polling.Configuration state and/or the Recovery.Configuration state; further , the sequence sending module 502 is also used to: periodically send the TS2 training sequence carrying the protection information in the reserved bytes; wherein, the protection identification information in the period is arranged in chronological order to form the authorized customer name, product batch information, and/or authorization time information.

Since the specific implementation of the apparatus 500 is similar in principle to the specific implementation of the method in FIG. 1 , detailed descriptions are omitted here.

Referring to FIG. 6 , similar to the principle of the method embodiment shown in FIG. 3 , this embodiment provides an IP soft core infringement identification device 600 based on the TS2 training sequence of the USB3.1 protocol. The device, as a software product, is mounted on the USB3.1 protocol Analyzing the device to implement all or part of the steps in the method embodiment shown in FIG. 3 at runtime. Specifically, the apparatus 600 includes the following modules:

The sequence capture module 601 is used to capture the TS2 training sequence sent to the USB host in the Polling.Configuration state and/or Recovery.Configuration state under the working state of the USB3.1 device under test in the protection identification mode; further, the sequence capture The module 601 is further configured to continuously capture a certain time or a certain number of the TS2 training sequences.

The information extraction module 602 is configured to extract the protection identification information in the reserved bytes of the TS2 training sequence; further, the information extraction module 602 is further configured to: extract the captured protection identification information of each of the TS2 training sequences, and extract the protection identification information of each of the TS2 training sequences. The protection identification information is arranged in chronological order to restore the authorized customer name, product batch information, and/or authorization time information; further, the information extraction module 602 is also used for: using ASCII code to perform the operation of each protection identification information. Decoding: Arranging the decoded protection identification information in chronological order.

The infringement identification module 603 is used for judging whether the protection identification information matches the preset protection identification information; if not, it is determined that the USB3.1 device infringes; further, the infringement identification module 603 is further used for: if the TS2 If the protection identification information does not exist in the reserved bytes of the training sequence, it is determined that the USB3.1 device is not a target device; or, further, the infringement identification module 603 is further configured to: determine the authorized customer name, product batch Whether the information and/or authorization time information matches the corresponding information of the manufacturer of the USB3.1 device, if not, it is determined that the USB3.1 device is infringing.

Since the specific implementation of the apparatus 600 is similar in principle to the specific implementation of the method in FIG. 3 , detailed descriptions are omitted here.

Referring to FIG. 7 , similar to the principle of the method embodiment shown in FIG. 4 , this embodiment provides another IP soft core infringement identification device 700 based on the USB3.1 protocol TS2 training sequence. The device is mounted on a USB host as a software product. All or part of the steps in the method embodiment shown in FIG. 4 are implemented at runtime. Specifically, the apparatus 700 includes the following modules:

The sequence sending module 701 is used for sending the TS2 training sequence carrying specific information in the reserved bytes to the USB3.1 device in the Polling.Configuration state and/or the Recovery.Configuration state; and/or for sending the TS2 training sequence to the USB3.1 device in the U0 state. 1 The device sends a user test link management data packet carrying specific information.

The infringement identification module 702 is used to check whether the USB3.1 device enters the protection identification mode; if not, it is determined that the USB3.1 device is not the target device; further, if so, connect and jump to the sequence capture of the device 600 Module 601.

Since the specific implementation of the apparatus 700 is similar in principle to the specific implementation of the method in FIG. 4 , it will not be repeated here.

Those skilled in the art should understand that the division of each module in the embodiments of FIG. 5 to FIG. 7 is only a division of logical functions, and may be fully or partially integrated into one or more physical entities in actual implementation. And these modules can all be implemented in the form of software calling through processing elements, or all of them can be implemented in hardware, and some modules can be implemented in the form of calling software through processing elements, and some modules can be implemented in hardware. For example, the mode conversion module 501 can be a separately established processing element, or can be integrated in a certain chip, and can also be stored in the memory in the form of program code, and the mode conversion module 501 can be called and executed by a certain processing element. function. The implementation of other modules is similar. The processing element described here may be an integrated circuit with signal processing capability. In the implementation process, each step of the above-mentioned method or each of the above-mentioned modules can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by hardware related to computer programs. Based on this understanding, the present invention also provides a computer program product comprising one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server or data center by wired (eg coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg: infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be stored by a computer, or a data storage device such as a server, data center, etc., which includes one or more available media integrated. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)), and the like.

Referring to FIG. 8 , this embodiment provides an electronic device, such as a USB3.1 device, a USB host, a USB protocol analyzer, etc., which includes a communicator 82 , a processor 83 , and a memory 84 connected through a bus 81 , wherein , the communicator 82 is used to realize the information transmission between the electronic device and the external device, the memory 83 is used to store the computer program, and the processor 84 is used to execute the computer program stored in the memory 83, so that the electronic device executes any of the foregoing method embodiments. A step of.

The system bus mentioned above may be a Peripheral Pomponent Interconnect (PCI for short) bus or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA for short) bus or the like. The system bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The communication interface is used to realize the communication between the database access device and other devices (eg client, read-write library and read-only library). The memory may include random access memory (Random Access Memory, RAM for short), and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The above-mentioned processor can be a general-purpose processor, including a central processing unit (CentralProcessingUnit, referred to as CPU), a network processor (NetworkProcessor, referred to as NP), etc.; can also be a digital signal processor (DigitalSignalProcessing, referred to as DSP), application-specific integrated circuit ( ApplicationSpecificIntegratedCircuit, referred to as ASIC), field programmable gate array (Field-ProgrammableGateArray, referred to as FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

To sum up, the IP soft core property rights protection and infringement identification method based on the TS2 training sequence of the USB3.1 protocol of the present invention adopts the method of deep binding with the USB3.1 protocol, and effectively realizes the protection of the USB3.1 soft core. The protection and identification of intellectual property rights effectively overcome various shortcomings in the existing technology and have high industrial utilization value.

The above-mentioned embodiments merely illustrate the principles and effects of the present invention, but are not intended to limit the present invention. Anyone skilled in the art can modify or change the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or changes made by those with ordinary knowledge in the technical field without departing from the spirit and technical idea disclosed in the present invention should still be covered by the claims of the present invention.

Claims (16)

1. An IP soft core property protection method based on a training sequence of a USB3.1 protocol TS2 is applied to a USB3.1 device, and comprises the following steps:

detecting whether a preset trigger condition of a protection identification mode is met; the preset trigger condition for protecting the identification mode comprises the following steps: triggering condition 1) receiving a TS2 training sequence carrying specific information in reserved bytes sent by a USB host in a polling. And/or triggering condition 2) receiving a user test link management data packet carrying specific information sent by the USB host in the U0 state;

if so, switching the current working state to the protection identification mode; wherein,

in the working state of the protection identification mode, the reserved bytes of the TS2 training sequence sent to the USB host in the polling.

2. The method of claim 1, wherein,

when the trigger condition 1) is met, the USB3.1 device correspondingly enters a polling.configuration state and/or a recovery.configuration state, and sends a TS2 training sequence carrying protection identification information in reserved bytes to the USB host;

when the trigger condition 2) is met, the USB3.1 device enters a recovery.configuration state, and sends a TS2 training sequence carrying protection identification information in a reserved byte to the USB host.

3. The method of claim 1, wherein the step of sending TS2 training sequence to the USB host in the polling.

Periodically sending TS2 training sequences carrying protection information in reserved bytes; wherein,

and arranging the protection identification information in the period according to the time sequence to form an authorized client name, product batch information and/or authorized time information.

4. The method of claim 1 or 2, wherein the reserved byte is the fifth byte of the TS2 training sequence.

5. The method of claim 1, wherein the protected identification information is previously generated using ASCII code encoding.

6. The method of claim 1, further comprising: exiting the protected identification mode upon re-powering on or receiving a reset request sent by the USB host.

7. An IP soft core infringement identification method based on a training sequence TS2 of a USB3.1 protocol is applied to a USB protocol analysis device, and the method comprises the following steps:

capturing a TS2 training sequence sent by the USB3.1 device to the USB host in a polling.configuration state and/or a recovery.configuration state under the working state of the protected identification mode;

extracting protection identification information in reserved bytes of the TS2 training sequence;

judging whether the protection identification information is matched with preset protection identification information or not;

if not, the USB3.1 equipment infringement is determined.

8. The method of claim 7, further comprising: and if the protection identification information does not exist in the reserved bytes of the TS2 training sequence, the USB3.1 device is determined not to be the target device.

9. The method of claim 7, further comprising:

continuously capturing a certain time or a certain number of the TS2 training sequences;

extracting the captured protection identification information of each TS2 training sequence, and arranging the protection identification information in time sequence to restore authorized client names, product batch information and/or authorized time information;

judging whether the name of the authorized client, the product batch information and/or the authorized time information are matched with the corresponding information of the manufacturer of the USB3.1 equipment;

if not, the USB3.1 equipment infringement is determined.

10. The method of claim 9, wherein the step of extracting and chronologically arranging the protection identification information of each captured TS2 training sequence further comprises:

decoding each protection identification information by using an ASCII code;

and arranging each piece of the decoded protection identification information according to a time sequence.

11. An IP soft core infringement identification method based on a training sequence TS2 of a USB3.1 protocol is applied to a USB host, and the method comprises the following steps:

sending a TS2 training sequence carrying specific information in reserved bytes to a USB3.1 device in a polling.configuration state and/or a recovery.configuration state, and checking whether the USB3.1 device enters a protected identification mode; if not, determining that the USB3.1 equipment is not the target equipment; and/or

In the U0 state, sending a user test link management data packet carrying specific information to the USB3.1 equipment, and checking whether the USB3.1 equipment enters a protection identification mode; if not, the USB3.1 equipment is determined not to be the target equipment.

12. An IP soft core property right protection device based on a training sequence of a USB3.1 protocol TS2, which is applied to a USB3.1 device, and comprises:

the mode conversion module is used for detecting whether a preset trigger condition for protecting the identification mode is met or not; if so, switching the current working state to the protection identification mode; the preset trigger condition for protecting the identification mode comprises the following steps: triggering condition 1) receiving a TS2 training sequence carrying specific information in reserved bytes sent by a USB host in a polling. And/or triggering condition 2) receiving a user test link management data packet carrying specific information sent by the USB host in the U0 state;

and the sequence sending module is used for sending the TS2 training sequence carrying the protection identification information in the reserved byte to the USB host in the working state of the protection identification mode and in the polling.

13. An IP soft core infringement authentication device based on a training sequence of a USB3.1 protocol TS2, which is applied to a USB protocol analysis device, and comprises:

a sequence capture module, configured to capture a TS2 training sequence sent by the USB3.1 device to the USB host in a polling.configuration state and/or a recovery.configuration state in a working state of the protected identification mode;

the information extraction module is used for extracting protection identification information in reserved bytes of the TS2 training sequence;

the infringement identification module is used for judging whether the protection identification information is matched with preset protection identification information or not; if not, the USB3.1 equipment infringement is determined.

14. An IP soft core infringement authentication device based on a training sequence of a USB3.1 protocol TS2, which is applied to a USB host and comprises:

a sequence sending module, configured to send, to the USB3.1 device, a TS2 training sequence in which specific information is carried in reserved bytes in a polling.configuration state and/or a recovery.configuration state; and/or the device is used for sending a user test link management data packet carrying specific information to the USB3.1 device in the U0 state;

the infringement authentication module is used for checking whether the USB3.1 equipment enters a protection identification mode or not; if not, the USB3.1 equipment is determined not to be the target equipment.

15. A storage medium in which a computer program is stored, which, when loaded and executed by a processor, carries out the method according to any one of claims 1 to 11.

16. An electronic device, comprising: a communicator, a processor, and a memory; wherein,

the communicator is used for establishing communication connection between the electronic equipment and external equipment;

the memory is used for storing a computer program;

the processor is configured to load and execute the computer program to cause the electronic device to perform the method according to any one of claims 1 to 11.

Images