CN109145527B

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

Info

Publication number: CN109145527B
Application number: CN201810651407.9A
Authority: CN
Inventors: 范凯; 卢笙; 姜欣; 肖骁; 董晓军
Original assignee: Xinqiyuan Shanghai Semiconductor Technology Co ltd
Current assignee: Xinqiyuan Shanghai Semiconductor Technology Co ltd
Priority date: 2018-06-22
Filing date: 2018-06-22
Publication date: 2020-10-09
Anticipated expiration: 2038-06-22
Also published as: CN109145527A

Abstract

The invention provides an IP soft core property protection and infringement identification method based on a USB3.1 protocol TS2 training sequence, wherein the IP soft core property protection method based on the USB3.1 protocol TS2 training sequence is applied to USB3.1 equipment and comprises the following steps: detecting whether a preset trigger condition of a protection identification mode is met; if so, switching the current working state to the protection identification mode; 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. The invention adopts a mode of deeply binding with the USB3.1 protocol, and effectively realizes the intellectual property protection and identification of the USB3.1 soft core.

Description

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

Technical Field

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

Background

USB is an abbreviation for Universal Serial Bus (USB), a standard for external Bus, and is used to standardize the connection and communication between computers and external devices. The USB interface supports plug and play and hot plug functions of the device. The USB standard was proposed by a combination of companies such as intel, compaq, IBM, Microsoft and the like in the end of 1994, and has been widely used in various electronic devices such as computers, mobile phones, digital cameras and the like. The USB standard is established and maintained by USB official organization USB-IF, five versions of USB1.1, USB2.0, USB3.0, USB3.1 and USB3.2 are released from the beginning to the present in sequence, and the new version is forward compatible with the old version. The maximum transmission rate distribution supported by each version is: USB 1.1: 12 Mbps; USB 2.0: 480 Mbps; USB 3.0: 5 Gbps; USB 3.1: 10 Gbps; USB 3.2: 20 Gbps.

Silicon Intellectual Property (SIP) refers to a module that is defined in advance, can be repeatedly used after being verified, and can perform a specific function in the chip (IC) industry. With the increase of the complexity and integration of the Chip, the processor, the memory, the I/O port and the analog circuit are integrated On a silicon Chip to form a complete System On Chip (SOC), if each module of a new SOC product is designed from the beginning and then System integration and verification are performed, the development cycle will be prolonged, and the design quality will be difficult to control. Therefore, reusing pre-designed and verified integrated circuit modules (IPs) is the most effective solution in the industry today.

The IP can be divided into three types of soft core, fixed core and hard core by distinguishing from the design flow:

1. IP Soft core (Soft IP)

In the process of designing a logic IC, an IC designer writes functions required by the system out of a Register Transfer Level (RTL) program using a hardware description language after the system specification is formulated, and the RTL file is called an IP soft core.

The IP soft core is provided in the form of source code, so that the method has high flexibility, can be modified by a user to realize the required circuit system design, is independent of a specific implementation process, and has the defect that the proprietary intellectual property rights are not easy to protect, particularly for a standard protocol IP (such as USB3.1), even if the code is encrypted, a client can repeatedly use the encrypted code of the same IP in different SOC projects.

2. IP core (Firm IP)

After the RTL program is verified by simulation and meets the design requirements, a designer selects a corresponding logic gate from a Cell Library (Cell Library) by using an electronic design automation tool (EDA), and converts the RTL file into a Netlist (Netlist) file presented in the form of a logic gate unit, namely, a so-called IP-based check.

The IP fixed core is a compromise between the IP soft core and the IP hard core, has higher reliability than the IP soft core and stronger flexibility than the IP hard core, but cannot be logically modified according to the requirements of clients like the IP soft core.

3. IP hardcore (Hard IP)

After the netlist file is verified, the step of entity design is entered, the position configuration design (Floor Planning) of the functional module is firstly carried out, then the Place and wiring design (Place & Routing) is carried out, and the GDSII file generated after the layout and wiring of the entity are finished is the IP hardmac.

The design and process of the IP hardmac is finished and cannot be modified, and the IP hardmac obtained by a user is only a product function and not a product design, so that the design and manufacture of the IP hardmac exercise full control over the IP hardmac. Compared with the IP soft core and the IP fixed core, the IP hard core is simpler in intellectual property protection.

USB3.1 IP is a widely used standard IP, and it is necessary to take effective measures to protect intellectual property rights. However, there is little research in the art for intellectual property protection of the IP soft core of USB3.1 devices.

Disclosure of Invention

In view of the above drawbacks of the prior art, the present invention provides a method for IP soft core property protection and infringement authentication based on a training sequence of a USB3.1 protocol TS2, which is used to solve the technical problem in the prior art that it is difficult to perform intellectual property protection on an IP soft core of a USB3.1 device.

In order to achieve the above objects and other related objects, the present invention provides a method for protecting IP soft core property based on a training sequence of a USB3.1 protocol TS2, applied to a USB3.1 device, the method including: detecting whether a preset trigger condition of a protection identification mode is met; if so, switching the current working state to the protection identification mode; 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.

In an embodiment of the present invention, the preset trigger condition for protecting the identification mode includes: 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; 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.

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 TS2 training sequences carrying protection information in reserved bytes; 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.

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 by encoding ASCII code in advance.

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

In order to achieve the above objects and other related objects, the present invention provides an IP soft core infringement identification method based on a training sequence of a USB3.1 protocol TS2, applied to a USB protocol analysis device, the method including: 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.

In an embodiment of the present invention, the method further includes: 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.

In an embodiment of the present invention, the method further includes: 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.

In an embodiment of the present invention, the step of extracting and arranging the captured protection identification information of each TS2 training sequence in chronological order further includes: 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.

In order to achieve the above objects and other related objects, the present invention provides a method for identifying IP soft core piracy based on a training sequence of a USB3.1 protocol TS2, applied to a USB host, the method including: 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.

In order to achieve the above objects and other related objects, the present invention provides an IP soft core property protection apparatus based on a training sequence of a USB3.1 protocol TS2, applied to a USB3.1 device, the apparatus comprising: 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; 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.

In order to achieve the above objects and other related objects, the present invention provides an IP soft core infringement identification apparatus based on a training sequence of a USB3.1 protocol TS2, applied to a USB protocol analysis device, the apparatus including: 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.

In order to achieve the above objects and other related objects, the present invention provides an IP soft core piracy identification apparatus based on a training sequence of a USB3.1 protocol TS2, applied to a USB host, the apparatus including: 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.

To achieve the above and other related objects, the present invention provides a storage medium having stored therein a computer program which, when loaded and executed by a processor, implements a method as described in any one of the above.

To achieve the above and other related objects, the present invention provides an electronic device, comprising: a communicator, a processor, and a memory; 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 as described in any of the above.

As described above, the IP soft core property protection and infringement authentication method based on the training sequence TS2 of the USB3.1 protocol adds the embedded protection identification code in the training sequence TS2 based on the USB3.1 protocol, thereby effectively protecting the IP soft core of the USB3.1 device. Meanwhile, an infringement authentication technology aiming at the intellectual property protection scheme is provided, and when the IP soft core is used or made into a product under the unauthorized condition, infringement authentication and proof can be carried out by triggering the protection identification code.

Drawings

Fig. 1 is a flowchart illustrating 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 illustrating a user test link management packet according to an embodiment of the present invention.

Fig. 2B is a schematic diagram illustrating a jump between Polling substates of the USB3.1 according to an embodiment of the present invention.

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

Fig. 4 is a flowchart illustrating 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 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 block diagram of an IP soft-core infringement authentication apparatus based on the TS2 training sequence of the USB3.1 protocol according to an embodiment of the invention.

Fig. 7 is a block diagram of an IP soft-core infringement authentication apparatus 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 invention.

Detailed Description

The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict.

It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present invention, and the components related to the present invention are only shown in the drawings rather than drawn according to the number, shape and size of the components in actual implementation, and the type, quantity and proportion of the components in actual implementation may be changed freely, and the layout of the components may be more complicated.

Referring to fig. 1, the embodiment provides a method for protecting IP soft core property based on the training sequence of the USB3.1 protocol TS2, which is used to effectively protect the IP soft core of the USB3.1 Device (Device). Herein, the USB3.1 device refers to all devices connected to a USB Host (Host) through a USB3.1 interface, such as a common USB disk, a card reader, a mobile hard disk, an external recorder, and so on. The method is executed by the USB3.1 device, and specifically comprises the following steps:

s11: and detecting whether a preset trigger condition of the protection identification mode is met. If yes, go to step S12; otherwise, the current working state is kept unchanged.

S12: and switching the current working state to the protection identification mode.

S13: 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.

The steps S11-S13 will be explained in detail below.

In a normal working mode, the USB3.1 device does not send protection identification information, and only when a specific trigger condition is satisfied, the USB3.1 device enters the protection identification mode, inserts the protection identification information into a TS2 training sequence sent later, or sends a TS2 training sequence carrying the protection identification information in advance later. That is, in the present invention, the USB3.1 device sends the TS2 training sequence carrying the protection identification information to the outside, and when the protection identification information is embedded in the TS2 training sequence, the protection identification information is not specifically limited, and may be embedded during sending or embedded before shipping.

Two triggering conditions for entering the protected identification mode are listed below:

triggering condition one, 1) receiving one or a certain number of TS2 training sequences carrying specific information in reserved bytes sent by a USB host in a polling configuration state, and/or 2) receiving one or a certain number of TS2 training sequences carrying specific information in reserved bytes sent by a USB host in a recovery configuration state.

And a second triggering condition, receiving one or a certain number of user test link management data packets carrying specific information sent by the USB host in the U0 state.

When the triggering condition 1) is met, the USB3.1 device correspondingly enters a polling.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 correspondingly enters a recovery.configuration state, and sends a TS2 training sequence carrying protection identification information in a reserved byte to the USB host.

When the triggering condition two 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. Fig. 2A shows a format of a user Test Link Management Packet (vector Device Test Link Management Packet), where specific information is located in DWORD1 and/or DWORD2, and when the USB3.1 Device receives the user Test Link Management Packet containing the specific information, the Device enters a protection recognition mode and enters a Recovery state.

In the first trigger condition and the second trigger condition, the specific information may be preset large and small letters, numbers or punctuation marks, or may be a character string formed by combining several of the large and small letters, numbers or punctuation marks.

As is well known, from the start of link power-up to normal operation (similar to plugging a USB3.1 USB disk onto a notebook USB3.1 interface to be able to start reading data normally) it needs to go through three phases: detect, Polling, and U0, where the Polling procedure performs related initialization setting on the terminal Device on the link (that is, it means that Host and Device are at the initialization transmitting end and receiving end and are synchronized to prepare for transmitting data packets); the process from rx.detect to U0 needs to go through several sub-processes including the transmission of TS2 training sequence in the polling.configuration sub-state: the devices of the two parties set relevant parameters by sending TS2 training sequences to the opposite party, complete handshaking after receiving and sending TS2 training sequences with specified number, and enter the next substate, poll.Idle; the initialization of the whole link is completed and the U0 stage is entered (normal operation, with the transmission and reception of data packets on the link). In addition, the USB3.1 communication protocol provides that the initiator or the receiver enters a Recovery state after a link has a recoverable error or exits from a low power consumption state and before entering a working state, and repeatedly sends a TS2 training sequence in the Recovery state, and the initiator or the receiver can know that the initiator or the receiver has entered the Recovery state or has exited from the low power consumption state when receiving a TS2 training sequence sent by the other party.

In connection with the above, according to the USB3.1 protocol, the TS2 training sequence is sent in the Polling _ configuration and recovery _ configuration sub-states, and the handshake is completed, and fig. 2B shows the jump of the USB3.1 between the Polling _ configuration sub-states, where the Polling _ configuration is the sub-state that the USB3.1 must pass through to enter the working state, so that the IP can be effectively protected and identified by inserting the reserved id code in the TS2 training sequence.

Table 1 shows the format of the training sequence TS2 in the USB3.1 protocol, which is 16 bytes long, and the present embodiment preferably uses the 5 th sign bit (i.e. symbol number 4 in table 1) of the training sequence TS2 as the reserved byte to carry the protected identification information. The reason is that: according to the USB3.1 protocol, the reserved byte sender is set to zero by default when sending, and the receiver does not check after receiving, so that the normal work of the USB3.1 equipment cannot be influenced by using the reserved byte No. 4 to carry the protection identification information.

TABLE 1

According to the definition of the TS2 training sequence, a TS2 training sequence has a byte space for carrying reserved identification Information, so in an embodiment, each byte is represented as a capital letter, a numeric letter or a punctuation mark by using an encoding method of American Standard Code for Information Interchange (ASCII), and after the USB3.1 device enters the protected identification mode, the device is marked by inserting the identification Information into the reserved byte of the continuous TS2 training sequence. The device marking means that after entering the protected identification mode, the USB3.1 device has the protected identification information in the reserved byte of the TS2 training sequence, and the other USB3.1 devices do not have this function, so that the USB3.1 device can be effectively distinguished from the other devices. At this time, if a certain USB3.1 device does not enter the protection recognition mode after meeting the trigger condition, it is described that the USB3.1 device uses an IP soft core that is not our, and thus there is no infringement problem.

Since a TS2 training sequence can only carry one byte of identification information, in one embodiment, the identification information is inserted letter-by-letter and sent periodically. The protected identification information may include information such as the name of the client authorized by the IP, the authorized lot and time. For example, if the authorized client is a, the authorized batch is B, and the authorized time is C, the protection identification information is ABC. Sending three TS2 training sequences in one period, wherein protection identification information carried by reserved bytes of a first TS2 training sequence is A, protection identification information carried by reserved bytes of a second TS2 training sequence is B, and protection identification information carried by reserved bytes of a third TS2 training sequence is C, wherein A-C are respectively located in the 5 th byte of each TS2 training sequence and exist in the form of ASCII codes, namely respectively: 01000001, 01000010, and 01000011.

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

Referring to fig. 3, the present embodiment provides an IP soft core infringement identification method based on a training sequence of a USB3.1 protocol TS2, which is used to perform effective infringement identification on an IP soft core of a 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. The method specifically comprises the following steps:

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

The tested USB3.1 device is in communication connection with the USB host, the USB protocol analysis device records the behavior on the USB3.1 interface, and captures a TS2 training sequence sent by the tested USB3.1 device to the USB host in a Polling.configuration state and/or a recovery.configuration state in a protection recognition mode.

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

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

S33: judging whether the protection identification information is matched with preset protection identification information or not; if not, go to step S34; otherwise, step S35 is executed.

The preset protection identification information can be preset large and small letters, numbers or punctuation marks, and can also be a character string formed by combining several kinds of the preset protection identification information. When the extracted protection identification information is matched with the preset protection identification information, the USB3.1 device is a product.

S34: and identifying the USB3.1 equipment infringement.

S35: the USB3.1 device is deemed not infringing.

In an embodiment, step S31 continuously captures a certain time or a certain number of TS2 training sequences, step S32 extracts the protection identification information in each TS2 training sequence, decodes the protection identification information with ASCII code, and arranges the decoded protection identification information in sequence, so as to restore authorized client name, product batch information, and/or authorized time information, step S33 determines whether the authorized client name, product batch information, and/or authorized time information match with the corresponding information (i.e., name, product batch, and/or authorized time) of the manufacturer of the USB3.1 device, and if not, determines that the USB3.1 device under test is infringed.

Referring to fig. 4, the present embodiment provides another IP soft core infringement identification method based on the training sequence of the USB3.1 protocol TS2, for performing effective infringement identification on the IP soft core of the USB3.1 device in the foregoing method embodiment. The method is executed by a USB host, wherein the USB host refers to electronic equipment such as a desktop computer, a notebook computer and the like which has a USB3.1 interface and can be connected with and communicate with USB3.1 equipment. The method specifically comprises the following steps:

s41: sending a TS2 training sequence carrying specific information in reserved bytes to the USB3.1 equipment in a polling.configuration state and/or a recovery.configuration state, and/or sending a user test link management data packet carrying specific information to the USB3.1 equipment in a U0 state.

S42: checking whether the USB3.1 equipment enters a protection identification mode; if not, go to step S43; otherwise, the method described in the embodiment of fig. 3 may be performed to determine the infringement condition.

S43: and the USB3.1 device is not determined to be a target device, namely the tested USB3.1 device is not our product, and the infringement problem does not exist.

Referring to fig. 5, similar to the principle of the embodiment of the method shown in fig. 1, the embodiment provides an IP soft core property right protection apparatus 500 based on the training sequence of the USB3.1 protocol TS2, which is mounted on the USB3.1 device as a software product to implement all or part of the steps in the embodiment of the method shown in fig. 1 when running. Specifically, the apparatus 500 includes the following modules:

the mode conversion module 501 is configured to detect whether a trigger condition of a preset protection recognition mode is met; if so, switching the current working state to the protection identification mode; further, the mode conversion module 501 is further configured to exit the protection identification mode after detecting that the USB3.1 device is powered on again or receiving a reset request sent by the USB host.

The sequence sending module 502 is configured to send, in the working state of the protection identification mode, a TS2 training sequence carrying protection identification information in reserved bytes to the USB host in a polling. Further, the sequence sending module 502 is further configured to: periodically sending TS2 training sequences carrying protection information in reserved bytes; 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.

Since the embodiment of the apparatus 500 is similar in principle to the embodiment of the method of fig. 1, further description is omitted here.

Referring to fig. 6, similar to the principle of the embodiment of the method shown in fig. 3, the embodiment provides an IP soft-core piracy identification apparatus 600 based on the training sequence of the USB3.1 protocol TS2, which is mounted on the USB3.1 protocol analysis device as a software product to implement all or part of the steps in the embodiment of the method shown in fig. 3 when running. Specifically, the apparatus 600 includes the following modules:

the sequence capturing module 601 is configured to capture a TS2 training sequence sent by the USB3.1 device under test in the working state of the protection recognition mode and in the polling.configuration state and/or the recovery.configuration state to the USB host; further, the sequence capturing module 601 is further configured to: continuously capturing a certain time or a certain number of the TS2 training sequences.

The information extraction module 602 is configured to extract protection identification information in reserved bytes of the TS2 training sequence; further, the information extraction module 602 is further configured to: 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; further, the information extraction module 602 is further configured to: 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.

The infringement authentication module 603 is configured to determine whether the protection identification information matches preset protection identification information; if not, determining that the USB3.1 equipment infringes; further, the infringement authentication module 603 is further configured to: 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 a target device; or, further, the infringement authentication module 603 is further configured to: and 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, and if not, determining that the USB3.1 equipment infringes.

Since the embodiment of the apparatus 600 is similar in principle to the embodiment of the method of fig. 3, further description is omitted here.

Referring to fig. 7, similar to the principle of the embodiment of the method shown in fig. 4, the present embodiment provides another IP soft piracy authentication apparatus 700 based on the training sequence of the USB3.1 protocol TS2, which is installed as a software product on a USB host to implement all or part of the steps in the embodiment of the method shown in fig. 4 when running. Specifically, the apparatus 700 includes the following modules:

the sequence sending module 701 is 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 for sending user test link management packets carrying specific information to the USB3.1 device in the U0 state.

The infringement authentication module 702 is configured to check whether the USB3.1 device enters a protected identification mode; if not, determining that the USB3.1 equipment is not the target equipment; further, if yes, connect and jump to the sequence capturing module 601 of the apparatus 600.

Since the embodiment of the apparatus 700 is similar in principle to the embodiment of the method of fig. 4, further description is omitted here.

Those skilled in the art should understand that the division of the modules in the embodiments of fig. 5 to 7 is only a logical division, and the actual implementation can be wholly or partially integrated into one or more physical entities. And the modules can be realized in a form that all software is called by the processing element, or in a form that all the modules are realized in a form that all the modules are called by the processing element, or in a form that part of the modules are called by the hardware. For example, the mode conversion module 501 may be a separate processing element, or may be implemented by being integrated in a chip, or may be stored in a memory in the form of program code, and the function of the mode conversion module 501 is called and executed by a certain processing element. Other modules are implemented similarly. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.

It will be understood by those skilled in the art that all or part of the steps for implementing the above-described method embodiments may be performed by hardware associated with a computer program. Based upon such an understanding, the present invention also provides a computer program product comprising one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Referring to fig. 8, the present embodiment provides an electronic device, for example: USB3.1 device, USB host, USB protocol analyzer, etc., comprising, connected by a bus 81: the communication device 82 is used for realizing information transmission between the electronic device and an external device, the memory 83 is used for storing computer programs, and the processor 84 is used for executing the computer programs stored in the memory 83 to make the electronic device execute the steps in any of the method embodiments.

The above-mentioned system bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The system bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus. The communication interface is used for realizing communication between the database access device and other equipment (such as a client, a read-write library and a read-only library). The memory may include a Random Access Memory (RAM), and may further include a non-volatile memory (non-volatile memory), such as at least one disk memory.

The processor may be a general-purpose processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the integrated circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.

In summary, the IP soft core property protection and infringement identification method based on the USB3.1 protocol TS2 training sequence of the present invention adopts a deep binding manner with the USB3.1 protocol, so as to effectively realize the intellectual property protection and identification of the USB3.1 soft core, and effectively overcome various disadvantages in the prior art, thereby having high industrial utilization value.

The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or change the above-mentioned embodiments without departing from the spirit and scope of the present invention. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical spirit of the present invention be covered by the claims of the present invention.

Claims

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.