Identity authentication method for equipment operator

Abstract

According to the equipment operator identity authentication method provided by the invention, face recognition, USBKey and equipment digital identity authentication technologies are deeply fused, and the camera at the equipment control computer end is adopted to collect the biological feature information of the face of the operator, so that the credible authentication of the identity of the equipment operator is realized. According to the method, face recognition, USBKey and equipment digital identity authentication are deeply fused through technologies, so that double verification of the identity of an equipment operator and the digital identity of the equipment is realized, and the safety is high. In the USBKey for verifying the authority of the equipment operator, the face image of the equipment operator with a digital signature is stored, the digital identity information of the equipment is also stored, the face image of the equipment operator needs to be compared and the real identity of the equipment needs to be verified in the authority verification process, and the safety of the equipment in the use process is fully guaranteed.

Description

Technical Field

[0001] The invention relates to the technical field of identity authentication, in particular to an identity authentication method for an equipment operator. Background Art

[0002] With the rapid development of information technology, network security issues have become increasingly prominent. In order to achieve secure Internet access for various devices and prevent unauthorized devices from illegally accessing the system, devices are usually given digital identities and authenticated based on the identities. For example, Chinese patent CN202210889790.8 "A method for managing digital identities of terminal devices" discloses a method for flexibly managing the digital identities of multiple devices, thereby achieving unified security management of different types of devices.

[0003] In order to achieve full-process traceability management of the device usage process, in addition to verifying the device's networking permissions, it is also necessary to identify the identity of the device operator to determine the operator's access rights to the device. USBKey is used for personnel identity authentication in many scenarios. Traditional USBKey mainly relies on static passwords for authentication. This single-factor authentication method cannot effectively ensure the consistency between the authorized personnel and the actual operator. There are security risks such as easy cracking, theft or substitution of others to operate the device, which brings huge hidden dangers to system security.

[0004] There are also forms of identity authentication that simply add a layer of identity authentication on top of the USB key using biometrics such as fingerprints. However, most of them are simple superpositions of separate biometric authentication and USBKey technology. Although the security factor has increased, attackers have the opportunity to bypass a single authentication factor, thereby threatening the security and stability of the entire system. Summary of the invention

[0005] In order to solve the problem of security loopholes in the existing personnel identity authentication method in the form of single element superposition, the present invention provides a device operator identity authentication method, which deeply integrates face recognition, USBKey and device digital identity authentication technology to build a highly secure and reliable identity authentication system, thereby improving the security of device operator identity authentication.

[0006] The technical solution of the present invention is as follows: a method for authenticating the identity of an equipment operator, characterized in that it comprises the following steps: S1: The computer that controls the device to be operated is recorded as: control terminal computer; The port of the control terminal computer supports USB key, and a camera for collecting portraits is installed; the device management client software runs on the control terminal computer; The device operator interacts with the device to be operated and the device management service system through the device management client software; A device digital identity security chip is set in the device to be operated, and the digital identity security chip is responsible for the authentication process of the device to be operated; S2: The device operator, as an applicant, submits an application to the device administrator for device operation authority; The device administrator collects the applicant's facial image, which is recorded as the registration facial image; The device administrator submits the registration face image and device operation permission application to the device management service system through the device management client software, and applies for the applicant to obtain the permission to operate the device; The data of the device operation permission application includes the device serial number DevSN and the device operator information OptInfo; S3: After the authorization process is completed, the device management service system embeds the device operator authorization information, the desensitized value of the device serial number and the digital signature into the registered face image to form an operator authorization image; wherein the device operator authorization information records which specific functions of the device to be operated are authorized to the applicant; The device management service system sends the authority authorization data to the device administrator; The device administrator writes the permission information related to the device to be operated into the operator USBKey based on the device management client software, and performs hardware encryption on the USBkey and assigns an initial value using a PIN code; The information written into the operator USBKey includes: device operator information OptInfo, device serial number DevSN and operator authorization image; The device operator information OptInfo and the device serial number DevSN are desensitized and written into the operator USBKey; The desensitized value of the device serial number in the operator's USBKey is consistent with the desensitized value of the device serial number DesenDevID in the device digital ID certificate; The desensitized value DesenUserID of the device operator information OptInfo is used as the user name of the operator to log in and authenticate the USBKey; S4: inserting the operator USBKey into the control terminal computer, and the device operator obtains the access rights of the operator USBKey based on the user name and PIN code authentication; When the device operator uses the PIN code to authenticate the operator USBKey, if the USBKey determines that the PIN code is the initial PIN code, the device operator is prompted to modify the initial PIN code; S5: the device management client software collects the face image of the device operator through the camera, which is recorded as: on-site collection of face image; The device management client software reads the operator authorization image stored in the operator USBKey and verifies the legitimacy of the digital signature embedded in the authorization image; if the digital signature embedded in the authorization image is legitimate, the on-site collected face image is compared with the operator authorization image; If the comparison is consistent, execute step S6; If the comparison is inconsistent, the face image collected on site is uploaded to the device management service system and the current operation is stopped; S6: The device management client software calls the operator USBKey to perform two-way identity authentication with the device to be operated; During the authentication process, the operator's USBKey determines the consistency between the desensitized value of the device serial number and the DesenDevID stored in the digital identity security chip; the digital identity security chip of the device to be operated determines whether the operator's USBKey has the authority to operate the device; S7: After the operator's USBKey and the device to be operated have passed the two-way identity authentication, the device management client software confirms the current networking status. If the control terminal computer is in the networking status at this time, step S8 is executed; Otherwise, the operating rights of the functions that do not require networking in the device operator authorization information are authorized to the applicant, and the functions that require networking are not allowed to be used by the applicant in this operation; the device operator identity authentication process ends; S8: The device management client software calls the operator USBKey to perform two-way identity authentication with the device management service system; The device management service system searches the operator authority list for the device to be operated and finds the device operator information of the applicant, and determines whether the applicant has the authority to operate the device to be operated; If the device operator has the device operation authority, the operator obtains the device operation log and the signature value of the on-site collected face image through USBKey, and embeds the operation log and signature value into the on-site collected face image; sends the on-site collected face image with embedded data to the device management service system for archiving; and completes the two-way authentication; The device management service system finds the operator corresponding to the device to be operated in the operator authority list, but the corresponding status of the operator is revoked, then it records the operator as a revoked person, and notifies the operator USBKey and the digital identity security chip of the revoked person, performs the authority revocation action, and cancels the revoked person's operating authority; End the device operator identity authentication process.

[0007] It is further characterized by: The operator USBKey includes: a user management module and an authentication management module; The user management module verifies all user application data received by the operator USBKey, and performs management work for each new user after verification, and the management work includes: creation, query and deletion; When the user management module creates a new user, a dedicated storage space is allocated to the user, each dedicated storage space is isolated from each other, and a dedicated authentication management module is created for each user; all data related to user authentication is stored in the dedicated storage space corresponding to the user; and the authentication management module corresponding to each user is bound to the dedicated storage space; each authentication management module runs in the designated dedicated cache space after startup; The authentication management module is responsible for handling all authentication related work for its corresponding user and can only read and write data in the corresponding dedicated storage space; In step S3, the permission authorization process specifically includes the following steps: a1: The device administrator collects the device serial number DevSN and device operator information OptInfo and submits them to the device management service system through the device management client software; Wherein, the OptInfo includes: the operator's ID number, name and contact number; a2: The device management service system generates the device serial number desensitized value DesenDevID and the device operator desensitized value DesenUserID according to DevSN and OptInfo; simultaneously generates the application data of the newly created user and sends it to the operator USBKey; Among them, the desensitized value of the device serial number DesenDevID is obtained by querying the digital identity service system; The device operator desensitized value DesenUserID is obtained by desensitizing DevSN||OptInfo using the desensitizing key DesenKey; The new user application data is: DesenDevID||DesenUserID||USERID||TimeSys1||Sign(DesenDevID||DesenUserID||USERID||TimeSys1)||CertSys; Among them, || represents information cascade operation, TimeSys1 is the system time of the device management service system, USERID is the ID number or telephone number of the device operator, Sign() is the signature operation using the private key of the device management service system, and CertSys is the certificate of the device management service system; a3: After receiving the new user application data, the operator USBKey verifies the information of the new user application data based on the user management module. After the verification is passed, a new user is created with DesenUserID as the user name, and DesenDevID, USERID and TimeSys1 are associated with the user name DesenUserID; The user management module creates a DesenUserID user and allocates a dedicated storage space for the user, and starts the authentication management module corresponding to the DesenUserID; The authentication management module generates a pair of public and private keys for the newly created DesenUserID user, and forms the device operation permission application data, and returns it to the user management module; and saves the DesenUserID, public and private keys, DesenDevID, USERID, TimeSys1 and initial PIN code in the dedicated storage space of the user DesenUserID; The user management module sends the device operation authority application data to the device management service system; The device operation permission application data is: DesenUserID||PubKeyUKey||KeySN||TimeSys1||Sign(DesenUserID||PubKeyUKey||KeySN||TimeSys1); Wherein, PubKeyUKey is the public key of the user DesenUserID, KeySN is the serial number of the operator USBKey, and Sign() is the signature operation of the private key of the user DesenUserID on the data of DesenUserID||PubKeyUKey||KeySN||TimeSys1; a4: The device management service system verifies the legitimacy of the device operation permission application data; if the verification is successful, a digital certificate CertKeyUser is issued to the user DesenUserID, and permission authorization data is generated; The legitimacy verification content includes: user name DesenUserID, TimeSys1 and signature value Sign; The certificate CertKeyUser includes: DesenUserID, DesenDevID and device operation authority information; The permission authorization data format is as follows: CertKeyUser||DelUserList||TimeSys2||Sign(CertKeyUser||DelUserList||TimeSys2)||CertSys||FacePicwithsign; Wherein, DelUserList is a list of user names whose operation permissions are to be revoked. If there is no user to be revoked, this data item is empty. TimeSys2 is the current time of the device management service system. Sign() is the signature operation of the service system on the authorization data. FacePicwithsign is the operator authorization image. a5: After receiving the authority authorization data, the user management module of the operator USBKey forwards the authority authorization data to the authentication management module corresponding to the user DesenUserID; The authentication management module verifies the legitimacy of the device management service system's certificate CertSys, signature value Sign and digital certificate CertKeyUser, and verifies whether the public key and DesenUserID information contained in the digital certificate CertKeyUser are consistent with the data stored in the dedicated storage space of the user DesenUserID; If the verification is successful, the digital certificate CertKeyUser is saved in the dedicated storage space of the user DesenUserID, and the operation result is fed back to the user management module, which then adds the user name DesenUserID and USERID to the valid user list ValidUserList; Complete the permission authorization process; Obtaining the access rights of the operator's USBKey based on the user name and PIN code authentication specifically includes the following steps: c1: The device operator enters the user name DesenUserID and PIN code through the device management client software and performs the first identity authentication operation with the operator USBKey; The device management client software sends first authentication request data to USBKey; The first authentication request data includes: DesenUserID, the user management module in the USBKey starts the authentication management module of the corresponding user according to the user name DesenUserID input by the operator, and the authentication management module generates and returns a random number Rnd0 to the device management client software; c2: the device management client software generates first identity authentication data based on Rnd0, and the DesenUserID and PIN code input by the device operator, and sends the first identity authentication data to the operator USBKey; The data format of the first identity authentication data is: Hash(Enc(DesenUserID, Rnd0)||PIN), where Hash is a summary operation, and Enc(DesenUserID, Rnd0) is to encrypt DesenUserID using Rnd0 as the key; c3: The authentication management module of USBKey calculates and generates the first identity authentication reference data according to the Hash(Enc(DesenUserID, Rnd0)||PIN) formula, and compares it with the received first identity authentication data; if the comparison result is consistent, the first identity authentication passes, and the authentication management module generates and returns the random number Rnd1 again and sends it to the device management client software; the PIN code authentication process is completed; In step S6, the operator USBKey performs two-way identity authentication with the device to be operated, which specifically includes the following steps: b1: The device operator obtains the access rights of the operator's USBKey based on the user name and PIN code authentication; b2: The device management client software sends Rnd1 returned by USBKey to the device digital identity security chip for identity authentication; b3: The device digital identity security chip generates identity authentication response data and returns it to the device management client software; The identity authentication response data includes: Rnd1, RndDev, SamCert2, and the signature value of the private key pair Rnd1||RndDev corresponding to the device digital identity security chip certificate SamCert2; wherein RndDev is a random number generated inside the device digital identity security chip, and SamCert2 is the second digital certificate of the device digital identity security chip; b4: The device management client software sends the identity authentication response data to the operator USBKey, and the corresponding authentication management module of the operator USBKey verifies the legitimacy of the data. The verification content includes: Whether the certificate SamCert2, signature value, and Rnd1 are the same as the random number generated in the first identity authentication process, and whether the desensitized value DesenDevID' of the device serial number in the SamCert2 certificate is consistent with the value stored in the authentication management module; wherein the desensitized value DesenDevID' of the device serial number is issued by the device management service system when the device to be operated joins the network and is stored in the device digital identity security chip; If the verification is successful, second authentication request data is generated and sent to the device management client software; The second authentication request data is: Rnd2||Sign(Rnd2||RndDev)||CertKeyUser; wherein Rnd2 is a random number newly generated by the authentication management module of the USBKey, and Sign(Rnd2||RndDev) is a signature value of the Rnd2||RndDev data using the private key corresponding to the user's operation authority certificate CertKeyUser; b5: the device management client software sends the second authentication request data to the device digital identity security chip; The device digital identity security chip verifies the legitimacy of the second authentication request data; The verification of the legitimacy of the second authentication request data includes: Verify that the user authority certificate CertKeyUser of the operator's USBKey, the signature value, the operator information in the certificate CertKeyUser, and the desensitized value of the device serial number in the certificate CertKeyUser are consistent with the values ​​stored in the digital identity security chip of the device; The operator information is stored in the device digital identity security chip, and if the verification is successful, the authentication ends; In step S6, during the two-way identity authentication, if the digital identity security chip does not contain the permission information of the operator's USBKey, the digital identity security chip generates binding request data during the authentication process and sends it to the device management service system, and the device management service system sends the operation permission authorization information to the digital identity security chip; The binding request data includes: the device operator information of the current permission application, and the information of all other device operators with the device operation permission; The operation authority authorization information includes: the device operator authority, and the device operator information of the device operator whose operation authority is to be revoked; The digital identity security chip of the device to be operated stores the device operator information with the device operation authority in the secure storage area of ​​the security chip; In step S6, during the two-way authentication, the operator USBKey and the device to be operated perform two-way authentication, which also includes the following steps: d1: If the device digital identity security chip does not contain the operator information, then generate binding request data, the format of which is: DesenUserID||DesenDevID||UserList||RndDev1||SignBindReq||SamCert2; Wherein, DesenUserID and DesenDevID are obtained by parsing the certificate CertKeyUser, UserList is a list of all user information supported by the device digital identity security chip, RndDev1 is a random number newly generated by the authentication management module, and SignBindReq is the signature value of the private key pair DesenUserID||DesenDevID||UserList||RndDev1 data corresponding to the second digital certificate SamCert2 of the device digital identity security chip; d2: The device management client software sends the binding request data to the device management service system; The device management service system verifies the legitimacy of the binding request data and verifies whether the system has authorized the operation authority of the DesenDevID device for the user DesenUserID. If the verification is successful, the operation authority authorization information is generated and sent to the device digital identity security chip. The format of the operation authority authorization information is: DesenUserID||DeleteList||Time||RndDev1||SignAuth||CertSys; Wherein, DesenUserID is the user name of the user to be authorized, Time is the current time of the device management service system, RndDev1 is the random number returned by the device digital identity security chip, and SignAuth is the signature value of the private key pair DesenUserID||DeleteList||Time||RndDev1 data corresponding to the device management service system certificate CertSys; d3: The device digital identity security chip verifies the legitimacy of the operation authority authorization information. The verification content includes: verifying the device management service system certificate CertSys, the service system's signature value SignAuth for the authorization information, and whether DesenUserID and RndDev1 are consistent with the operator information and random number in the binding request data; if the verification is consistent, the operator information DesenUserID is added to the operator list of the device digital identity security chip; d4: The device management service system updates the list of operators who have the authority to operate the device according to the returned status, and completes the operator authority authorization process; It also includes a multi-user management method, specifically including the following: e1: Each time the device management service system releases the permission authorization data to the operator USBKey, it will simultaneously transmit the corresponding user information to be deleted in the operator USBKey to the operator USBKey; The field DelUserList included in the permission authorization data is a list of user names whose operation permissions are to be revoked, and is used to record relevant information; When the device management service system issues a digital certificate CertKeyUser to the operator USBKey, the device management service system determines whether the operator USBKey with the serial number KeySN has user information to be deleted. If there is a user to be deleted, the user name to be deleted and the certificate CertKeyUser are combined into authority authorization data; and the authority authorization data is sent to the operator USBKey; In the user management module, a valid user list ValidUserList and a to-be-revoked user list DelUserList are set; When a new device operator is added to the device to be operated, the user management module adds the user name DesenUserID and USERID to the valid user list ValidUserList. The valid user list ValidUserList also contains the self-signed data of all user data by the user management module to achieve the tamper-proof feature of the list data; If the permission authorization data received by the user management module includes DelUserList information, the user management module removes all users in the to-be-revoked user list DelUserList from the ValidUserList before adding a new user to the ValidUserList list; e2: When the device management service system generates operation authority authorization information to the device digital identity security chip, it will also send the device operator information to be deleted to the device digital identity security chip; The field DeleteList included in the operation authority authorization information is used to record relevant information; When the device management service generates the operation permission authorization information, the device management service system determines whether there is a device operator whose operation permission is to be deleted on the DesenDevID device. If so, the user information list DeleteList to be deleted in the operation permission authorization information should also include the device operator information whose operation permission is to be deleted. Otherwise, DeleteList is empty. After receiving the operation authority authorization information, the device digital identity security chip determines whether there is a device operator to be deleted in the authorization information, and if so, deletes the device operator to be deleted from the operator list; after processing, the device digital identity security chip regenerates the self-signed data of the operator list and returns the operation result to the device management service system; e3: When the device management service system performs two-way authentication with the operator USBKey, if it is found that the device operator being authenticated is a revoked person, the device digital identity security chip and the operator USBKey will be notified of the revoked person's information. After receiving the information of the revoked person, the user management module removes the information of the revoked person from the ValidUserList list, deletes the authentication management module of the revoked person, and releases the dedicated storage space corresponding to the revoked person; After receiving the information of the revoked person, the device digital identity security chip deletes the revoked person from the operator list; after deletion, the device digital identity security chip regenerates the self-signed data of the operator list and returns the operation result to the device management service system.

[0008] The present invention provides a device operator identity authentication method, which deeply integrates face recognition, USBKey and device digital identity authentication technology, and uses the camera of the device control computer to collect the operator's facial biometric information, thereby realizing the trusted authentication of the device operator's identity. This method deeply integrates face recognition, USBKey and device digital identity authentication technology, and realizes the dual verification of the device operator's identity and the device's digital identity, with high security. The USBKey used for device operator authority verification stores both the face image of the device operator with a digital signature and the digital identity information of the device. During the authority verification process, it is necessary to compare the face image of the device operator and verify the true identity of the device, which fully guarantees the safety of the device use process. In this method, USBKey supports the safe and isolated storage of the authority information of multiple device operators. At the same time, this method also supports the use of the camera of the device control computer to collect face images, and the investment cost is low. Based on this method, during the device operator authority authentication process, the dynamic adjustment of the device operator's operating authority can be realized, and the management cost is low. This method supports hierarchical management of device operator authorization information. It does not require networking functions. After verifying the operator's identity, the operator can be authorized to use it, which effectively meets the needs of the device's offline application function for user authority verification. When the device operator uses USBKey for device networking authentication for the first time, the operator's operating authority will be added to the device's digital identity security chip. At the same time, the device management service system will delete the expired device operator authority from the device's digital identity security chip, ensuring that data can be synchronized in a timely manner between the USBkey and the device management service system, thereby improving system security. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 This is a schematic diagram of the structure of the device operator identity authentication system in this application; Figure 2This is a flow chart of the device operator identity authentication method of this application; Figure 3 Authorization flow chart for backup operators; Figure 4 A flowchart for authenticating a device operator with the device and obtaining device operation authority. DETAILED DESCRIPTION

[0010] The present invention comprises a method for authenticating the identity of an equipment operator, which comprises the following steps.

[0011] S1: The computer that controls the device to be operated is recorded as: control terminal computer; The port of the control-end computer supports USB key, and a camera for capturing portraits is installed; the device management client software runs on the control-end computer; the device operator interacts with the device to be operated and the device management service system through the device management client software; A device digital identity security chip is set in the device to be operated, and the digital identity security chip is responsible for the authentication process of the device to be operated.

[0012] Specific as Figure 1 The structure diagram of the system used for the device operator identity authentication method is shown. The device management service system, the device to be operated and the operator's USB Key are respectively connected to the control end computer for data communication.

[0013] The operator USBKey includes: a user management module and an authentication management module; The user management module verifies all user application data received by the operator USBKey, and manages each new user after verification. The management work includes: creation, query and deletion; When the user management module creates a new user, it allocates a dedicated storage space for the user. Each dedicated storage space is isolated from each other, and a dedicated authentication management module is created for each user; all data related to user authentication is stored in the dedicated storage space corresponding to the user; and the authentication management module corresponding to each user is bound to the dedicated storage space; each authentication management module runs in the designated dedicated cache space after startup; The authentication management module is responsible for handling all authentication-related tasks for its corresponding users and can only read and write data in its corresponding dedicated storage space.

[0014] In order to reduce costs, this method allows multiple operators to use the same USB key. Different operators are distinguished by user names, and each user name corresponds to a PIN code and operator authorization image. Figure 1As shown in , including U1, U2...Un, there are n users in total, and each user has his own dedicated storage space. Any operator user with authorization authority can control the device to be operated based on the operator USBKey. The specific USBKey is implemented based on the chip of the national secret algorithm module. In order to ensure security in this method, an independent authentication management module and a dedicated storage space are set for each operator user, and the storage space accessible to the authentication management module is bound based on the space address. After each user's authentication management module is started, it runs in the designated dedicated cache space and can only access its dedicated storage space. In this way, even if an outsider obtains the pin code and user name of one of the users, he can only access the data of one user and use the permissions of one user. He cannot access the data of other users, nor can he use the permissions of other users, which greatly improves the security of the USBKey.

[0015] S2: The device operator, as an applicant, submits an application to the device administrator for device operation authority; The device administrator collects the applicant's facial image, which is recorded as the registration facial image; The device administrator submits the registration face image and device operation permission application to the device management service system through the device management client software, and applies for the applicant to obtain the permission to operate the device; The data for applying for device operation permission includes the device serial number DevSN and the device operator information OptInfo.

[0016] S3: After the authorization process is completed, the device management service system embeds the device operator authorization information, the desensitized value of the device serial number and the digital signature into the registered face image to form an operator authorization image; the device operator authorization information records which specific functions of the device to be operated are authorized to the applicant; The device management service system sends the permission authorization data to the device administrator; The device administrator writes the permission information related to the device to be operated into the operator USBKey based on the device management client software, and performs hardware encryption on the USBkey and assigns an initial value using a PIN code; The information written into the operator USBKey includes: device operator information OptInfo, device serial number DevSN and operator authorization image; Among them, the device operator information OptInfo and the device serial number DevSN are desensitized and written into the operator USBKey; The desensitized value of the device serial number in the operator's USBKey is consistent with the desensitized value of the device serial number DesenDevID in the device digital ID card; The desensitized value DesenUserID of the device operator information OptInfo is used as the user name of the operator login authentication USBKey.

[0017] In this application, the operator authorization image stored in the operator USBKey and the operator face image collected during the operation of the device are in JPEG format. The device operation authority, operation log and digital signature are embedded in the application reserved marker segment of the JPEG image. The defined quantization table (DQT) of the JPEG image is encrypted data.

[0018] The operator in this application can call the user management module and obtain the user name DesenUserID for logging in to USBKey through USERID query, but it is not allowed to obtain USERID through DesenUserID query.

[0019] In step S3, the permission authorization process specifically includes the following steps: a1: The device administrator collects the device serial number DevSN and device operator information OptInfo and submits them to the device management service system through the device management client software; Among them, OptInfo includes: operator ID number, name and contact number; a2: The device management service system generates the device serial number desensitized value DesenDevID and the device operator desensitized value DesenUserID based on DevSN and OptInfo; it also generates the application data of the new user and sends it to the operator USBKey; Among them, the desensitized value of the device serial number DesenDevID is obtained by querying the digital identity service system; The device operator desensitized value DesenUserID is obtained by desensitizing DevSN||OptInfo using the desensitizing key DesenKey; The application data for a new user is: DesenDevID||DesenUserID||USERID||TimeSys1||Sign(DesenDevID||DesenUserID||USERID||TimeSys1)||CertSys; Among them, || represents information cascade operation, TimeSys1 is the system time of the device management service system, USERID is the ID number or telephone number of the device operator, Sign() is the signature operation using the private key of the device management service system, and CertSys is the certificate of the device management service system; a3: After receiving the application data of the new user, the operator USBKey verifies the information of the application data of the new user based on the user management module. After the verification is passed, a new user is created with DesenUserID as the user name, and DesenDevID, USERID and TimeSys1 are associated with the user name DesenUserID; The user management module creates a DesenUserID user and allocates a dedicated storage space for the user, and starts the authentication management module corresponding to the DesenUserID; The authentication management module generates a pair of public and private keys for the newly created DesenUserID user, and forms the device operation permission application data, and returns it to the user management module; and saves the DesenUserID, public and private keys, DesenDevID, USERID, TimeSys1 and initial PIN code in the dedicated storage space of the user DesenUserID; The user management module sends the device operation permission application data to the device management service system; The data required to apply for device operation permission is: DesenUserID||PubKeyUKey||KeySN||TimeSys1||Sign(DesenUserID||PubKeyUKey||KeySN||TimeSys1); Wherein, PubKeyUKey is the public key of user DesenUserID, KeySN is the serial number of operator USBKey, and Sign() is the signature operation of user DesenUserID's private key on DesenUserID||PubKeyUKey||KeySN||TimeSys1 data; a4: The device management service system verifies the legitimacy of the device operation permission application data; if the verification is successful, a digital certificate CertKeyUser is issued for the user DesenUserID, and permission authorization data is generated; The legitimacy verification content includes: user name DesenUserID, TimeSys1 and signature value Sign; The certificate CertKeyUser includes: DesenUserID, DesenDevID and device operation permission information; The format of permission authorization data is as follows: CertKeyUser||DelUserList||TimeSys2||Sign(CertKeyUser||DelUserList||TimeSys2)||CertSys||FacePicwithsign; Among them, DelUserList is the user name list of the operation permissions to be revoked. If there is no user to be revoked, this data item is empty. TimeSys2 is the current time of the device management service system. Sign() is the signature operation of the service system on the authorization data. FacePicwithsign is the operator authorization image. a5: After receiving the authorization data, the user management module of the operator's USBKey forwards the authorization data to the authentication management module corresponding to the user's DesenUserID; The authentication management module verifies the legitimacy of the device management service system's certificate CertSys, signature value Sign, and digital certificate CertKeyUser, and verifies whether the public key and DesenUserID information contained in the digital certificate CertKeyUser are consistent with the data stored in the dedicated storage space of the user DesenUserID; If the verification is successful, the digital certificate CertKeyUser is saved in the dedicated storage space of the user DesenUserID, and the operation result is fed back to the user management module, which then adds the user name DesenUserID and USERID to the valid user list ValidUserList; Complete the permission authorization process.

[0020] S4: Insert the operator USBKey on the control terminal computer, and the device operator obtains the access rights of the operator USBKey based on the user name and PIN code authentication; When the device operator uses the PIN code to authenticate the operator USBKey, if the USBKey determines that the PIN code is the initial PIN code, the device operator is prompted to modify the initial PIN code.

[0021] The access rights of the operator's USBKey are obtained based on the user name and PIN code authentication, which specifically includes the following steps: c1: The device operator enters the user name DesenUserID and PIN code through the device management client software and performs the first identity authentication operation with the operator USBKey; The device management client software sends the first authentication request data to the USBKey; The first authentication request data includes: DesenUserID, the user management module in the USBKey starts the authentication management module of the corresponding user according to the user name DesenUserID input by the operator, and the authentication management module generates and returns a random number Rnd0 to the device management client software; c2: The device management client software generates the first identity authentication data based on Rnd0 and the DesenUserID and PIN code input by the device operator, and sends the first identity authentication data to the operator USBKey; The data format of the first identity authentication data is: Hash(Enc(DesenUserID, Rnd0)||PIN), where Hash is a summary operation, and Enc(DesenUserID, Rnd0) is to encrypt DesenUserID using Rnd0 as a key; c3: The authentication management module of USBKey calculates and generates the first identity authentication reference data according to the Hash(Enc(DesenUserID, Rnd0)||PIN) formula, and compares it with the received first identity authentication data; if the comparison result is consistent, the first identity authentication passes, and the authentication management module generates and returns the random number Rnd1 again and sends it to the device management client software; completing the PIN code authentication process.

[0022] S5: the device management client software collects the face image of the device operator through the camera, which is recorded as: collecting the face image on site, and compares the face image collected on site with the operator authorization image stored in the operator USBKey; If the comparison is consistent, execute step S6; If the comparison is inconsistent, the facial image collected on site will be uploaded to the equipment management service system and the operation will be stopped.

[0023] In actual operation, before facial image comparison, the device management client software reads the operator authorization image corresponding to the device operator username from the operator USBKey, decrypts the definition quantization table (DQT) of the authorization image into plain text data, and verifies the legitimacy of the digital signature embedded in the facial image; prevents the operator authorization image stored in the USBKey from being tampered with, thereby improving system security.

[0024] S6: The device management client software calls the operator's USBKey to perform two-way identity authentication with the device to be operated; During the authentication process, the operator's USBKey determines the consistency between the desensitized value of the device serial number and the DesenDevID stored in the digital identity security chip; the digital identity security chip of the device to be operated determines whether the operator's USBKey has the authority to operate the device.

[0025] In step S6, the operator's USBKey performs two-way identity authentication with the device to be operated, which specifically includes the following steps: b1: The device operator obtains access rights to the operator USBKey based on user name and PIN code authentication; b2: The device management client software sends Rnd1 returned by USBKey to the device digital identity security chip for identity authentication; b3: The device digital identity security chip generates identity authentication response data and returns it to the device management client software; The identity authentication response data includes: Rnd1, RndDev, SamCert2, and the signature value of the private key pair Rnd1||RndDev corresponding to the device digital identity security chip certificate SamCert2; wherein RndDev is a random number generated inside the device digital identity security chip, and SamCert2 is the second digital certificate of the device digital identity security chip; b4: The device management client software sends the identity authentication response data to the operator's USBKey, and the corresponding authentication management module of the operator's USBKey verifies the legitimacy of the data. The verification content includes: Whether the certificate SamCert2, signature value, and Rnd1 are the same as the random number generated in the first identity authentication process, and whether the desensitized value DesenDevID' of the device serial number in the SamCert2 certificate is consistent with the value stored in the authentication management module; wherein, the desensitized value DesenDevID' of the device serial number is issued by the device management service system when the device to be operated joins the network and is stored in the device digital identity security chip; If the verification is successful, second authentication request data is generated and sent to the device management client software; The second authentication request data is: Rnd2||Sign(Rnd2||RndDev)||CertKeyUser; wherein Rnd2 is a random number newly generated by the authentication management module of USBKey, and Sign(Rnd2||RndDev) is the signature value of the Rnd2||RndDev data using the private key corresponding to the user's operation authority certificate CertKeyUser; b5: The device management client software sends the second authentication request data to the device digital identity security chip; The device's digital identity security chip verifies the legitimacy of the second authentication request data; The verification of the legitimacy of the second authentication request data includes: Verify that the operator's USBKey user authority certificate CertKeyUser, signature value, operator information in the certificate CertKeyUser, and the desensitized value of the device serial number in the certificate CertKeyUser are consistent with the values ​​stored in the device's digital identity security chip; The device’s digital identity security chip contains operator information, and if the verification is successful, the authentication is complete.

[0026] In step S6, during the two-way identity authentication, if the digital identity security chip does not contain the authority information of the operator's USBKey, the digital identity security chip generates binding request data during the authentication process and sends it to the device management service system, and the device management service system sends the operation authority authorization information to the digital identity security chip; The binding request data includes: the device operator information for this permission application, and the information of all other device operators with device operation permissions; The operation authority authorization information includes: equipment operator authority, and the equipment operator information whose operation authority is to be revoked; The digital identity security chip of the device to be operated stores the device operator information with device operation authority in a secure storage area of ​​the security chip.

[0027] Specifically, during the two-way authentication, the operator's USBKey and the device to be operated perform two-way authentication, which also includes the following steps: d1: If there is no operator information in the device digital identity security chip, a binding request data is generated. The format of the binding request data is: DesenUserID||DesenDevID||UserList||RndDev1||SignBindReq||SamCert2; Among them, DesenUserID and DesenDevID are obtained by parsing the certificate CertKeyUser, UserList is a list of all user information supported by the device digital identity security chip, RndDev1 is a random number newly generated by the authentication management module, and SignBindReq is the signature value of the private key pair DesenUserID||DesenDevID||UserList||RndDev1 data corresponding to the second digital certificate SamCert2 of the device digital identity security chip; d2: The device management client software sends the binding request data to the device management service system; The device management service system verifies the legitimacy of the binding request data and verifies whether the system has authorized the operation authority of the DesenDevID device for the user DesenUserID. If the verification is successful, the operation authority authorization information is generated and sent to the device digital identity security chip. The format of the operation authority authorization information is: DesenUserID||DeleteList||Time||RndDev1||SignAuth||CertSys; Where DesenUserID is the user name of the user to be authorized, Time is the current time of the device management service system, RndDev1 is the random number returned by the device digital identity security chip, and SignAuth is the signature value of the private key pair DesenUserID||DeleteList||Time||RndDev1 data corresponding to the device management service system certificate CertSys; d3: The device digital identity security chip verifies the legitimacy of the operation permission authorization information. The verification content includes: verifying the device management service system certificate SysCert, the service system's signature value SignAuth for the authorization information, and whether DesenUserID and RndDev1 are consistent with the operator information and random number in the binding request data. If the verification is consistent, the operator information DesenUserID is added to the operator list of the device digital identity security chip; d4: The device management service system updates the list of operators with device operation rights based on the returned status and completes the operator rights authorization process.

[0028] S7: After the operator's USBKey and the device to be operated have passed the two-way identity authentication, the device management client software confirms the current networking status. If the control terminal computer is in the networking status at this time, step S8 is executed; Otherwise, the operating authority of the functions that do not require networking in the device operator authorization information is authorized to the applicant, and the applicant is not allowed to use the functions that require networking in this operation; the device operator identity authentication process ends.

[0029] In this method, the identity authentication between the operator's USBKey and the device to be operated and the face image comparison of the device operator can be performed in an offline environment. This method has the ability to manage the device operation permissions in a hierarchical manner. For some functions that do not require an Internet connection, after the operator's identity is verified, the operator can be authorized to use them, effectively meeting the device's needs for user authority verification when used offline.

[0030] S8: The device management client software calls the operator's USBKey to perform two-way identity authentication with the device management service system; The equipment management service system searches the operator authority list for the equipment to be operated and finds the equipment operator information of the applicant, and determines whether the applicant has the authority to operate the equipment to be operated; If the equipment operator has the equipment operation authority, the operator USBKey obtains the equipment operation log and the signature value of the face image collected on site, and embeds the operation log and signature value into the face image collected on site; sends the face image collected on site with embedded data to the equipment management service system for archiving; and completes the two-way authentication; The equipment management service system finds the operator corresponding to the equipment to be operated in the operator authority list, but the corresponding status of the operator is revoked, then it will be recorded as: revoked personnel, and the revoked personnel will be notified to the operator USBKey and digital identity security chip, and the authority revocation action will be performed to cancel the revoked personnel's operating authority.

[0031] In order to improve the reliability of data synchronization for multiple users, the method also includes a multi-user management method, which synchronously revokes user information during each two-way authentication and each new operator user is added; specifically, the following contents are included.

[0032] e1: Every time the device management service system releases the authorization data to the operator's USBKey, it will also pass the corresponding user information to be deleted in the operator's USBKey to the operator's USBKey; The field DelUserList included in the permission authorization data is a list of user names whose operation permissions are to be revoked, used to record relevant information; When the device management service system issues a digital certificate CertKeyUser to the operator USBKey, the device management service system determines whether the operator USBKey with the serial number KeySN has user information to be deleted. If there is a user to be deleted, the user name to be deleted and the certificate CertKeyUser are combined into permission authorization data; the permission authorization data is sent to the operator USBKey; In the user management module, set the valid user list ValidUserList and the user list to be revoked DelUserList; When a new device operator is added to the device to be operated, the user management module adds the user name DesenUserID and USERID to the valid user list ValidUserList. The valid user list ValidUserList also contains the self-signed data of all user data by the user management module to achieve the tamper-proof feature of the list data; If the permission authorization data received by the user management module includes DelUserList information, the user management module removes all users in the to-be-revoked user list DelUserList from the ValidUserList before adding a new user to the ValidUserList.

[0033] e2: When the device management service system generates operation permission authorization information to the device digital identity security chip, it will also send the device operator information to be deleted to the device digital identity security chip; The DeleteList field included in the operation permission authorization information is used to record relevant information; When the device management service generates the operation permission authorization information, the device management service system determines whether there is a device operator whose operation permission is to be deleted on the DesenDevID device. If so, the user information list DeleteList in the operation permission authorization information should also contain the device operator information whose operation permission is to be deleted. Otherwise, DeleteList is empty. After the device digital identity security chip receives the operation permission authorization information, it determines whether there is a device operator to be deleted in the authorization information. If so, the device operator to be deleted will be deleted from the operator list, and the device operator information whose operation permission is to be revoked will be deleted from the secure storage area. After processing is completed, the device digital identity security chip regenerates the self-signed data of the operator list and returns the operation result to the device management service system.

[0034] e3: When the device management service system performs two-way authentication with the operator's USBKey, if it finds that the device operator being authenticated is a revoked person, it will actively notify the device digital identity security chip and the operator's USBKey of the revoked person's information; After receiving the information of the revoked person, the user management module removes the information of the revoked person from the ValidUserList list, deletes the authentication management module of the revoked person, and releases the dedicated storage space corresponding to the revoked person; After the device digital identity security chip receives the information of the revoked person, it deletes the revoked person from the operator list and deletes the revoked person's data from the secure storage area; after deletion, the device digital identity security chip regenerates the self-signed data of the operator list and returns the operation result to the device management service system.

[0035] This application focuses on the technical solution of realizing operator identity authentication by integrating face recognition and device digital identity technology based on USB key; while the technical solution related to the management method of the device digital identity of the operating device based on the digital identity security chip is not developed in the technical solution of this application.

[0036] After using the technical solution of the present invention, it realizes the dual verification of the operator's identity and the device's digital identity on the basis of ensuring the safe implementation of the device operator's identity authentication, thereby improving the efficiency of refined management of device use. In this solution, by deeply integrating face recognition, USBKey and device digital identity technology, a highly secure and reliable multi-factor identity authentication system for device operators is constructed. The device operator identity authentication method and system provided by the present invention improve the efficiency of device operator identity management and enhance the security and traceability of the device use process.

Claims

1. A method for authenticating the identity of an equipment operator, characterized in that: It includes the following steps: S1: The computer that controls the device to be operated is recorded as: control terminal computer; The port of the control terminal computer supports USB key, and a camera for collecting portraits is installed; the device management client software runs on the control terminal computer; The device operator interacts with the device to be operated and the device management service system through the device management client software; A device digital identity security chip is set in the device to be operated, and the digital identity security chip is responsible for the authentication process of the device to be operated; S2: The device operator, as an applicant, submits an application to the device administrator for device operation authority; The device administrator collects the applicant's facial image, which is recorded as the registration facial image; The device administrator submits the registration face image and device operation permission application to the device management service system through the device management client software, and applies for the applicant to obtain the permission to operate the device; The data of the device operation permission application includes the device serial number DevSN and the device operator information OptInfo; S3: After the authorization process is completed, the device management service system embeds the device operator authorization information, the desensitized value of the device serial number and the digital signature into the registered face image to form an operator authorization image; wherein the device operator authorization information records which specific functions of the device to be operated are authorized to the applicant; The device management service system sends the authority authorization data to the device administrator; The device administrator writes the permission information related to the device to be operated into the operator USBKey based on the device management client software, and performs hardware encryption on the USBkey and assigns an initial value using a PIN code; The information written into the operator USBKey includes: device operator information OptInfo, device serial number DevSN and operator authorization image; The device operator information OptInfo and the device serial number DevSN are desensitized and written into the operator USBKey; The desensitized value of the device serial number in the operator's USBKey is consistent with the desensitized value of the device serial number DesenDevID in the device digital ID certificate; The desensitized value DesenUserID of the device operator information OptInfo is used as the user name of the operator to log in and authenticate the USBKey; S4: inserting the operator USBKey into the control terminal computer, and the device operator obtains the access rights of the operator USBKey based on the user name and PIN code authentication; When the device operator uses the PIN code to authenticate the operator USBKey, if the USBKey determines that the PIN code is the initial PIN code, the device operator is prompted to modify the initial PIN code; S5: the device management client software collects the face image of the device operator through the camera, which is recorded as: on-site collection of face image; The device management client software reads the operator authorization image stored in the operator USBKey and verifies the legitimacy of the digital signature embedded in the authorization image; if the digital signature embedded in the authorization image is legitimate, the on-site collected face image is compared with the operator authorization image; If the comparison is consistent, execute step S6; If the comparison is inconsistent, the face image collected on site is uploaded to the device management service system and the current operation is stopped; S6: The device management client software calls the operator USBKey to perform two-way identity authentication with the device to be operated; During the authentication process, the operator's USBKey determines the consistency between the desensitized value of the device serial number and the DesenDevID stored in the digital identity security chip; the digital identity security chip of the device to be operated determines whether the operator's USBKey has the authority to operate the device; S7: After the operator's USBKey and the device to be operated have passed the two-way identity authentication, the device management client software confirms the current networking status. If the control terminal computer is in the networking status at this time, step S8 is executed; Otherwise, the operating rights of the functions that do not require networking in the device operator authorization information are authorized to the applicant, and the functions that require networking are not allowed to be used by the applicant in this operation; the device operator identity authentication process ends; S8: The device management client software calls the operator USBKey to perform two-way identity authentication with the device management service system; The device management service system searches the operator authority list for the device to be operated and finds the device operator information of the applicant, and determines whether the applicant has the authority to operate the device to be operated; If the device operator has the device operation authority, the operator obtains the device operation log and the signature value of the on-site collected face image through USBKey, and embeds the operation log and signature value into the on-site collected face image; sends the on-site collected face image with embedded data to the device management service system for archiving; and completes the two-way authentication; The device management service system finds the operator corresponding to the device to be operated in the operator authority list, but the corresponding status of the operator is revoked, then it records the operator as a revoked person, and notifies the operator USBKey and the digital identity security chip of the revoked person, performs the authority revocation action, and cancels the revoked person's operating authority; End the device operator identity authentication process.

2. According to claim 1, a method for authenticating the identity of an equipment operator is characterized in that: The operator USBKey includes: a user management module and an authentication management module; The user management module verifies all user application data received by the operator USBKey, and performs management work for each new user after verification, and the management work includes: creation, query and deletion; When the user management module creates a new user, a dedicated storage space is allocated to the user, each dedicated storage space is isolated from each other, and a dedicated authentication management module is created for each user; all data related to user authentication is stored in the dedicated storage space corresponding to the user; and the authentication management module corresponding to each user is bound to the dedicated storage space; each authentication management module runs in the designated dedicated cache space after startup; The authentication management module is responsible for processing all authentication related work for its corresponding user and can only read and write data in the corresponding dedicated storage space.

3. The device operator identity authentication method according to claim 2, characterized in that: In step S3, the permission authorization process specifically includes the following steps: a1: The device administrator collects the device serial number DevSN and device operator information OptInfo and submits them to the device management service system through the device management client software; Wherein, the OptInfo includes: the operator's ID number, name and contact number; a2: The device management service system generates the device serial number desensitized value DesenDevID and the device operator desensitized value DesenUserID according to DevSN and OptInfo; simultaneously generates the application data of the newly created user and sends it to the operator USBKey; Among them, the desensitized value of the device serial number DesenDevID is obtained by querying the digital identity service system; The device operator desensitized value DesenUserID is obtained by desensitizing DevSN||OptInfo using the desensitizing key DesenKey; The new user application data is: DesenDevID||DesenUserID||USERID||TimeSys1||Sign(DesenDevID||DesenUserID||USERID||TimeSys1)||CertSys; Among them, || represents information cascade operation, TimeSys1 is the system time of the device management service system, USERID is the ID number or telephone number of the device operator, Sign() is the signature operation using the private key of the device management service system, and CertSys is the certificate of the device management service system; a3: After receiving the new user application data, the operator USBKey verifies the information of the new user application data based on the user management module. After the verification is passed, a new user is created with DesenUserID as the user name, and DesenDevID, USERID and TimeSys1 are associated with the user name DesenUserID; The user management module creates a DesenUserID user and allocates a dedicated storage space for the user, and starts the authentication management module corresponding to the DesenUserID; The authentication management module generates a pair of public and private keys for the newly created DesenUserID user, and forms the device operation permission application data, and returns it to the user management module; and saves the DesenUserID, public and private keys, DesenDevID, USERID, TimeSys1 and initial PIN code in the dedicated storage space of the user DesenUserID; The user management module sends the device operation authority application data to the device management service system; The device operation permission application data is: DesenUserID||PubKeyUKey||KeySN||TimeSys1||Sign(DesenUserID||PubKeyUKey||KeySN||TimeSys1); Wherein, PubKeyUKey is the public key of the user DesenUserID, KeySN is the serial number of the operator USBKey, and Sign() is the signature operation of the private key of the user DesenUserID on the data of DesenUserID||PubKeyUKey||KeySN||TimeSys1; a4: The device management service system verifies the legitimacy of the device operation permission application data; if the verification is successful, a digital certificate CertKeyUser is issued to the user DesenUserID, and permission authorization data is generated; The legitimacy verification content includes: user name DesenUserID, TimeSys1 and signature value Sign; The certificate CertKeyUser includes: DesenUserID, DesenDevID and device operation authority information; The permission authorization data format is as follows: CertKeyUser||DelUserList||TimeSys2||Sign(CertKeyUser||DelUserList||TimeSys2)||CertSys||FacePicwithsign; Wherein, DelUserList is a list of user names whose operation permissions are to be revoked. If there is no user to be revoked, this data item is empty. TimeSys2 is the current time of the device management service system. Sign() is the signature operation of the service system on the authorization data. FacePicwithsign is the operator authorization image. a5: After receiving the authority authorization data, the user management module of the operator USBKey forwards the authority authorization data to the authentication management module corresponding to the user DesenUserID; The authentication management module verifies the legitimacy of the device management service system's certificate CertSys, signature value Sign and digital certificate CertKeyUser, and verifies whether the public key and DesenUserID information contained in the digital certificate CertKeyUser are consistent with the data stored in the dedicated storage space of the user DesenUserID; If the verification is successful, the digital certificate CertKeyUser is saved in the dedicated storage space of the user DesenUserID, and the operation result is fed back to the user management module, which then adds the user name DesenUserID and USERID to the valid user list ValidUserList; Complete the permission authorization process.

4. The device operator identity authentication method according to claim 2, characterized in that: Obtaining the access rights of the operator's USBKey based on the user name and PIN code authentication specifically includes the following steps: c1: The device operator enters the user name DesenUserID and PIN code through the device management client software and performs the first identity authentication operation with the operator USBKey; The device management client software sends first authentication request data to USBKey; The first authentication request data includes: DesenUserID, the user management module in the USBKey starts the authentication management module of the corresponding user according to the user name DesenUserID input by the operator, and the authentication management module generates and returns a random number Rnd0 to the device management client software; c2: the device management client software generates first identity authentication data based on Rnd0, and the DesenUserID and PIN code input by the device operator, and sends the first identity authentication data to the operator USBKey; The data format of the first identity authentication data is: Hash(Enc(DesenUserID, Rnd0)||PIN), where Hash is a summary operation, and Enc(DesenUserID, Rnd0) is to encrypt DesenUserID using Rnd0 as the key; c3: The authentication management module of USBKey calculates and generates the first identity authentication reference data according to the Hash(Enc(DesenUserID, Rnd0)||PIN) formula, and compares it with the received first identity authentication data; if the comparison result is consistent, the first identity authentication passes, and the authentication management module generates and returns the random number Rnd1 again and sends it to the device management client software; completing the PIN code authentication process.

5. The device operator identity authentication method according to claim 1, characterized in that: In step S6, the operator USBKey performs two-way identity authentication with the device to be operated, which specifically includes the following steps: b1: The device operator obtains the access rights of the operator's USBKey based on the user name and PIN code authentication; b2: The device management client software sends Rnd1 returned by USBKey to the device digital identity security chip for identity authentication; b3: The device digital identity security chip generates identity authentication response data and returns it to the device management client software; The identity authentication response data includes: Rnd1, RndDev, SamCert2, and the signature value of the private key pair Rnd1||RndDev corresponding to the device digital identity security chip certificate SamCert2; wherein RndDev is a random number generated inside the device digital identity security chip, and SamCert2 is the second digital certificate of the device digital identity security chip; b4: The device management client software sends the identity authentication response data to the operator USBKey, and the corresponding authentication management module of the operator USBKey verifies the legitimacy of the data. The verification content includes: Whether the certificate SamCert2, signature value, and Rnd1 are the same as the random number generated in the first identity authentication process, and whether the desensitized value DesenDevID' of the device serial number in the SamCert2 certificate is consistent with the value stored in the authentication management module; wherein the desensitized value DesenDevID' of the device serial number is issued by the device management service system when the device to be operated joins the network and is stored in the device digital identity security chip; If the verification is successful, second authentication request data is generated and sent to the device management client software; The second authentication request data is: Rnd2||Sign(Rnd2||RndDev)||CertKeyUser; wherein Rnd2 is a random number newly generated by the authentication management module of the USBKey, and Sign(Rnd2||RndDev) is a signature value of the Rnd2||RndDev data using the private key corresponding to the user's operation authority certificate CertKeyUser; b5: the device management client software sends the second authentication request data to the device digital identity security chip; The device digital identity security chip verifies the legitimacy of the second authentication request data; The verification of the legitimacy of the second authentication request data includes: Verify that the user authority certificate CertKeyUser of the operator's USBKey, the signature value, the operator information in the certificate CertKeyUser, and the desensitized value of the device serial number in the certificate CertKeyUser are consistent with the values ​​stored in the digital identity security chip of the device; The operator information is stored in the device digital identity security chip, and if the verification is passed, the authentication is completed.

6. A method for authenticating the identity of an equipment operator according to claim 5, characterized in that: In step S6, during the two-way identity authentication, if the digital identity security chip does not contain the permission information of the operator's USBKey, the digital identity security chip generates binding request data during the authentication process and sends it to the device management service system, and the device management service system sends the operation permission authorization information to the digital identity security chip; The binding request data includes: the device operator information of the current permission application, and the information of all other device operators with the device operation permission; The operation authority authorization information includes: the device operator authority, and the device operator information of the device operator whose operation authority is to be revoked; The digital identity security chip of the device to be operated stores the device operator information having the device operation authority in a secure storage area of ​​the security chip.

7. A method for authenticating the identity of an equipment operator according to claim 6, characterized in that: In step S6, during the two-way authentication, the operator USBKey and the device to be operated perform two-way authentication, which also includes the following steps: d1: If the device digital identity security chip does not contain the operator information, then generate binding request data, the format of which is: DesenUserID||DesenDevID||UserList||RndDev1||SignBindReq||SamCert2; Wherein, DesenUserID and DesenDevID are obtained by parsing the certificate CertKeyUser, UserList is a list of all user information supported by the device digital identity security chip, RndDev1 is a random number newly generated by the authentication management module, and SignBindReq is the signature value of the private key pair DesenUserID||DesenDevID||UserList||RndDev1 data corresponding to the second digital certificate SamCert2 of the device digital identity security chip; d2: The device management client software sends the binding request data to the device management service system; The device management service system verifies the legitimacy of the binding request data and verifies whether the system has authorized the operation authority of the DesenDevID device for the user DesenUserID. If the verification is successful, the operation authority authorization information is generated and sent to the device digital identity security chip. The format of the operation authority authorization information is: DesenUserID||DeleteList||Time||RndDev1||SignAuth||CertSys; Wherein, DesenUserID is the user name of the user to be authorized, Time is the current time of the device management service system, RndDev1 is the random number returned by the device digital identity security chip, and SignAuth is the signature value of the private key pair DesenUserID||DeleteList||Time||RndDev1 data corresponding to the device management service system certificate CertSys; d3: The device digital identity security chip verifies the legitimacy of the operation permission authorization information. The verification content includes: verifying the device management service system certificate CertSys, the service system's signature value SignAuth for the authorization information, and whether DesenUserID and RndDev1 are consistent with the operator information and random number in the binding request data; If the verification is consistent, the operator information DesenUserID is added to the operator list of the device digital identity security chip; d4: The device management service system updates the list of operators who have the authority to operate the device according to the returned status, and completes the operator authority authorization process.

8. The device operator identity authentication method according to claim 2, characterized in that: It also includes a multi-user management method, specifically including the following: e1: Each time the device management service system releases the permission authorization data to the operator USBKey, it will simultaneously transmit the corresponding user information to be deleted in the operator USBKey to the operator USBKey; The field DelUserList included in the permission authorization data is a list of user names whose operation permissions are to be revoked, and is used to record relevant information; When the device management service system issues a digital certificate CertKeyUser to the operator USBKey, the device management service system determines whether the operator USBKey with the serial number KeySN has user information to be deleted. If there is a user to be deleted, the user name to be deleted and the certificate CertKeyUser form the authority authorization data; Sending the authority authorization data to the operator USBKey; In the user management module, a valid user list ValidUserList and a to-be-revoked user list DelUserList are set; When a new device operator is added to the device to be operated, the user management module adds the user name DesenUserID and USERID to the valid user list ValidUserList. The valid user list ValidUserList also contains the self-signed data of all user data by the user management module to achieve the tamper-proof feature of the list data; If the permission authorization data received by the user management module includes DelUserList information, the user management module removes all users in the to-be-revoked user list DelUserList from the ValidUserList before adding a new user to the ValidUserList list; e2: When the device management service system generates operation authority authorization information to the device digital identity security chip, it will also send the device operator information to be deleted to the device digital identity security chip; The field DeleteList included in the operation authority authorization information is used to record relevant information; When the device management service generates the operation permission authorization information, the device management service system determines whether there is a device operator whose operation permission is to be deleted on the DesenDevID device. If so, the user information list DeleteList to be deleted in the operation permission authorization information should also include the device operator information whose operation permission is to be deleted. Otherwise, DeleteList is empty. After receiving the operation authority authorization information, the device digital identity security chip determines whether there is a device operator to be deleted in the authorization information, and if so, deletes the device operator to be deleted from the operator list; After the processing is completed, the device digital identity security chip regenerates the self-signed data of the operator list and returns the operation result to the device management service system; e3: When the device management service system performs two-way authentication with the operator USBKey, if it is found that the device operator being authenticated is a revoked person, the device digital identity security chip and the operator USBKey will be notified of the revoked person's information. After receiving the information of the revoked person, the user management module removes the information of the revoked person from the ValidUserList list, deletes the authentication management module of the revoked person, and releases the dedicated storage space corresponding to the revoked person; After receiving the information of the revoked person, the device digital identity security chip deletes the revoked person from the operator list; after deletion, the device digital identity security chip regenerates the self-signed data of the operator list and returns the operation result to the device management service system.

Images