Security authentication method and system for IoT (Internet of Things) edge equipment

Abstract

The invention provides a security authentication method and system for an IoT (Internet of Things) edge device, and the method comprises the steps: 1, generating a key file and a security certificate according to the application information filled in an IoT platform by a user; 2, acquiring a local security certificate and a local private key which are stored in a target edge device by a user; 3, initiating security authentication to the IoT platform according to the local security certificate and the local private key; and step 4, returning a verification result. According to the security authentication method and system for the IoT edge device, an automatic identity authentication process is realized through the digital certificate downloaded by the edge device, and a user does not need to manually authenticate the identity every time, so that the computing efficiency of the device is improved; in addition, the digital certificate comprises the public key information and the additional security attribute of the equipment, and higher-level security can be provided through authentication of the digital certificate.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things, and in particular to a security authentication method and system for an IoT edge device. Background Art

[0002] Currently, one of the main challenges faced in deploying edge devices in IoT (Internet of Things) is how to achieve security of device communication and authentication in devices with limited resources. Most of the existing cryptographic algorithms and solutions used to ensure device security are only applicable to desktop devices or server devices, but for IoT edge devices, the computing resources consumed are too large. In terms of security, traditional login verification only relies on usernames and passwords, which are vulnerable to man-in-the-middle attacks or password cracking, and have weak security performance.

[0003] In view of this, there is an urgent need for a security authentication method and system for IoT edge devices to at least solve the above-mentioned deficiencies. Summary of the invention

[0004] One of the purposes of the present invention is to provide a security authentication method and system for IoT edge devices, which realizes an automated identity authentication process through a digital certificate downloaded by the edge device. Users do not need to manually perform identity authentication every time, thereby improving the computing efficiency of the device. In addition, the digital certificate contains the public key information and additional security attributes of the device, and authentication through a digital certificate can provide a higher level of security.

[0005] An embodiment of the present invention provides a security authentication method for an IoT edge device, comprising:

[0006] Step 1: Generate a key file and security certificate based on the application information filled in by the user on the IoT platform;

[0007] Step 2: Obtain the local security certificate and local private key stored by the user on the target edge device;

[0008] Step 3: Initiate security authentication to the IoT platform based on the local security certificate and local private key;

[0009] Step 4: Return the verification result.

[0010] Preferably, step 1: generating a key file and a security certificate according to the application information filled in by the user on the IoT platform, including:

[0011] Obtain the application information filled in by the user when logging into the IoT platform. The application information includes: the device created by the user, the SDK version and the development language;

[0012] Generate a public key and private key pair based on the IoT platform and application information;

[0013] Generate a key file and security certificate based on the public key and private key pair.

[0014] Preferably, step 2: obtaining a local security certificate and a local private key stored by the user on the target edge device includes:

[0015] Obtain the download security certificate and download key file downloaded by the user;

[0016] Access the current active policy version and change the required topic;

[0017] After the required topic is changed, configure mqttx and obtain the local security certificate and local private key.

[0018] Preferably, step 3: initiating security authentication to the IoT platform according to the local security certificate and the local private key, including:

[0019] Obtain the local security certificate and local private key read by the target edge device, parse the local security certificate and extract the local public key;

[0020] Encrypt according to the application name and local private key, and initiate an authentication request to the IoT platform based on the encrypted ciphertext.

[0021] Preferably, step 4: returning the verification result includes:

[0022] The IoT platform verifies the application name based on the ciphertext and returns a verification success or verification failure.

[0023] An IoT edge device security authentication method provided by an embodiment of the present invention also includes:

[0024] Step 5: If the verification result is successful, the linkable edge devices of the target edge device are displayed to the user, the target linkable edge device selected by the user is determined, and a shortcut command is recommended to the user.

[0025] Preferably, determining that the target selected by the user can be linked to the edge device and recommending a shortcut command to the user includes:

[0026] The target linkable edge device and the target edge device selected by the target user are used together as collaborative edge devices;

[0027] Obtain historical collaboration records of collaborative edge devices;

[0028] According to historical collaboration records, summarize collaboration functions, collaboration operation instructions and historical usage frequency;

[0029] Generate a list of shortcut commands based on collaborative functions, collaborative operation commands and historical usage frequency;

[0030] Display a list of shortcuts to the user;

[0031] Among them, obtaining the historical collaboration records of collaborative edge devices includes:

[0032] Obtain the associated scenarios of collaborative edge devices;

[0033] According to the associated scene, obtain the personnel setting records of the scene personnel;

[0034] Determine the setting time interval and setting frequency of the collaborative edge device based on the personnel setting records;

[0035] Calculate the coordination rate of habit settings based on the setting time interval and setting frequency;

[0036] If the collaboration rate is greater than or equal to the preset collaboration rate threshold, the corresponding personnel setting record is used as the first pre-selected historical collaboration record;

[0037] Obtain historical risk scenario events based on associated scenarios;

[0038] Obtain event probabilities of historical risk scenario events;

[0039] Obtain historical risk scenario events and preset risk event libraries to determine the risk values ​​of historical risk scenario events;

[0040] Determine the necessary monitoring values ​​for historical risk scenario events based on event probability and risk value;

[0041] If the monitoring necessary value is greater than or equal to the preset monitoring necessary value threshold, the corresponding historical risk scenario event is used as the target scenario event;

[0042] Obtaining manual collaborative monitoring and control records of collaborative edge devices in target scenario events, and using them as second pre-selected historical collaborative records;

[0043] The first pre-selected historical collaboration record and the second pre-selected historical collaboration record are taken together as the historical collaboration record.

[0044] Preferably, based on historical collaboration records, collaborative functions, collaborative operation instructions and historical usage frequencies are summarized, including:

[0045] Based on the edge device collaborative feature extraction template, the edge device collaborative features are extracted according to the historical collaborative records;

[0046] Perform feature clustering on the collaborative features of edge devices to obtain multiple cluster feature sets;

[0047] Traverse each cluster feature set in turn to obtain the target cluster feature set currently being traversed;

[0048] Calculate the cluster feature value mean of the cluster feature value of each feature type in the target cluster feature set, and construct the characterization feature vector corresponding to the target cluster feature set according to the cluster feature value mean corresponding to each feature type;

[0049] Based on the collaborative function description template, the collaborative function is determined according to the historical collaborative records corresponding to the extracted characteristic vectors;

[0050] Determine the collaborative operation instruction according to the characterizing feature vector;

[0051] determining a historical usage frequency based on a first total number of historical collaboration records extracted from the target cluster feature set and a second total number of historical collaboration records;

[0052] When each cluster feature set has been traversed, the induction is completed.

[0053] Preferably, a shortcut command list is displayed to the user, including:

[0054] Get the user's sight information when viewing the shortcut command list;

[0055] Obtain and view the shortcut command sequence according to the line of sight information;

[0056] Based on the editing intention instruction extraction condition, the editing intention instruction is obtained according to the viewing shortcut instruction sequence;

[0057] Get similar sub-commands of the editing intention command;

[0058] Obtaining editing rules for missing instruction parts of similar sub-instructions;

[0059] Generate editable templates for users to edit based on editing rules and similar sub-instructions;

[0060] Among them, the editing intention instruction extraction conditions include:

[0061] The editing intention instruction is to view the shortcut instruction numbered last in the shortcut instruction sequence;

[0062] The first instruction number of the editing intention instruction is an integer multiple of the second instruction number preset for the repetitive feature of the editing intention instruction;

[0063] Repeating features conform to standard repeating features;

[0064] The first instruction number is greater than or equal to a preset first threshold;

[0065] The integer multiple is greater than or equal to a preset first threshold and less than or equal to a preset second threshold;

[0066] The execution subject in the editing intention instruction is consistent.

[0067] An embodiment of the present invention provides a security authentication system for an IoT edge device, including:

[0068] The application subsystem is used to generate key files and security certificates based on the application information filled in by the user on the IoT platform;

[0069] The local storage subsystem is used to obtain the local security certificate and local private key stored by the user on the edge device;

[0070] The security authentication subsystem is used to initiate security authentication to the IoT platform based on the local security certificate and local private key;

[0071] The verification result return subsystem is used to return the verification result.

[0072] The beneficial effects of the present invention are:

[0073] The present invention realizes an automated identity authentication process through a digital certificate downloaded by an edge device. Users do not need to manually perform identity authentication every time, thereby improving the computing efficiency of the device. In addition, the digital certificate contains the public key information and additional security attributes of the device. Authentication through a digital certificate can provide a higher level of security.

[0074] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures specifically pointed out in the present application documents.

[0075] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0077] Figure 1 A schematic diagram of a security authentication method for an IoT edge device in an embodiment of the present invention;

[0078] Figure 2 Schematic diagram of a security authentication system for an IoT edge device in an embodiment of the present invention. DETAILED DESCRIPTION

[0079] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0080] The embodiment of the present invention provides a security authentication method for an IoT edge device, such as Figure 1 As shown, including:

[0081] Step 1: Generate a key file and security certificate based on the application information filled in by the user on the IoT platform;

[0082] Step 2: Obtain the local security certificate and local private key stored by the user on the target edge device; the target edge device is: the edge device that the user needs to access the IoT platform;

[0083] Step 3: Initiate security authentication to the IoT platform based on the local security certificate and local private key;

[0084] Step 4: Return the verification result;

[0085] Among them, step 1: Generate a key file and security certificate according to the application information filled in by the user on the IoT platform, including:

[0086] Obtain the application information filled in by the user when logging into the IoT platform. The application information includes: the device created by the user, the SDK version and the development language;

[0087] Generate a public key and private key pair based on the IoT platform and application information;

[0088] Generate key files and security certificates based on public key and private key pairs;

[0089] Among them, step 2: obtaining the local security certificate and local private key stored by the user on the target edge device includes:

[0090] Obtain the download security certificate and download key file downloaded by the user;

[0091] Access the current active policy version and change the required topic;

[0092] After the required topic is changed, configure mqttx and obtain the local security certificate and local private key;

[0093] Among them, step 3: initiating security authentication to the IoT platform based on the local security certificate and local private key, including:

[0094] Obtain the local security certificate and local private key read by the target edge device, parse the local security certificate and extract the local public key;

[0095] Encrypt according to the application name and local private key, and initiate an authentication request to the IoT platform based on the encrypted ciphertext;

[0096] Among them, step 4: returning the verification result includes:

[0097] The IoT platform verifies the application name based on the ciphertext and returns a verification success or verification failure.

[0098] The working principle and beneficial effects of the above technical solution are:

[0099] The IoT platform is an Internet of Things cloud platform that provides services such as device connection, data collection, processing and analysis. When the IoT edge device is connected, the user fills in the application information when creating an application on the IoT platform (user-created device (device entity defined by the user on the IoT platform, these devices will be connected to the platform and exchange data), SDK (Software Development Kit, Software Development Kit) version (developers use these toolkits to develop applications that can interact with the IoT platform) and development language (programming language used by developers to write applications) etc.); the IoT platform automatically generates a key file and security certificate based on the application information; then, the user downloads the security certificate and key file to the local device, the target edge device extracts the local public key, encrypts it according to the application name and local private key, and initiates an authentication request to the IoT platform; the IoT platform verifies the application name based on the ciphertext analysis.

[0100] The present invention realizes an automated identity authentication process through a digital certificate downloaded by an edge device. Users do not need to manually perform identity authentication every time, thereby improving the computing efficiency of the device. In addition, the digital certificate contains the public key information and additional security attributes of the device. Authentication through a digital certificate can provide a higher level of security.

[0101] An embodiment of the present invention provides a security authentication method for an IoT edge device, further comprising:

[0102] Step 5: If the verification result is successful, the linkable edge devices of the target edge device are displayed to the user, the target linkable edge device selected by the user is determined, and a shortcut command is recommended to the user; wherein the linkable edge device is an edge device that can be collaboratively controlled with the target edge device based on the IoT platform, for example, the target edge device is an electronic door lock, and the linkable edge device is a living room lamp; the recommended shortcut command is a collaborative control command of the target edge device and the linkable edge device recommended to the user by the IoT platform, for example, a collaborative control command to turn on the living room lamp within 1 second after the unlocking command is triggered;

[0103] Among them, determining the target selected by the user can link the edge device and recommend shortcut commands to the user, including:

[0104] The target linkable edge device and the target edge device selected by the target user are used together as collaborative edge devices;

[0105] Obtain historical collaboration records of collaborative edge devices; where historical collaboration records are: records of collaborative work of collaborative edge devices, such as: turning on the living room light after unlocking the electronic lock, turning on the bedroom air circulation fan after turning on the bedroom air conditioner;

[0106] According to the historical collaborative records, the collaborative functions, collaborative operation instructions and historical usage frequency are summarized; among them, the collaborative function is: the description of the collaborative effect of the collaborative edge device, for example: the collaborative function of the electronic lock unlocking triggering the turning on of the living room light is: smart home, and the collaborative function of turning on the bedroom air conditioner triggering the turning on of the bedroom air circulation fan is: collaborative cooling; the collaborative operation instruction is: the control instruction of the corresponding collaborative edge device when realizing the collaborative function; the historical usage frequency is: the historical usage frequency of the collaborative function;

[0107] Generate a shortcut command list based on collaborative functions, collaborative operation instructions and historical usage frequency; the shortcut command list displays the collaborative function description in descending order of historical usage frequency. Users click on the collaborative function description to set the collaborative function corresponding to the collaborative function description. When the collaborative function setting conditions are met, the subsequent system automatically executes the collaborative operation instruction.

[0108] Display a list of shortcuts to the user;

[0109] Among them, obtaining the historical collaboration records of collaborative edge devices includes:

[0110] Obtaining the associated scenarios of the collaborative edge device; wherein the associated scenarios are: scenarios in which the collaborative edge device has been used in the past, such as: the home of resident A who has configured smart home devices;

[0111] According to the associated scene, obtain the personnel setting record of the scene personnel; the personnel setting record is: the record of the settings of the collaborative edge device by the personnel in the associated scene in the past, such as: turning on the living room lighting after opening the door, and adjusting the air conditioner to 26°C;

[0112] According to the personnel setting record, determine the setting time interval and setting frequency of the collaborative edge device; wherein the setting time interval is: the start-up time difference between the collaborative edge devices in the same personnel setting record; the setting frequency is: the result obtained by dividing the number of records of the personnel setting record corresponding to the setting time interval by the total number of records of the personnel setting record;

[0113] According to the setting time interval and setting frequency, the coordination rate of the custom setting is calculated; wherein the custom setting is: the personnel setting record corresponding to the setting time interval; the coordination rate is: the reciprocal of the setting time interval multiplied by the setting frequency;

[0114] If the collaboration rate is greater than or equal to a preset collaboration rate threshold, the corresponding personnel setting record is used as the first pre-selected historical collaboration record; wherein the preset collaboration rate threshold is manually preset;

[0115] According to the associated scenarios, historical risk scenario events are obtained; among them, historical risk scenario events are risk events in associated scenarios, such as: children at home bumping into furniture;

[0116] Obtain the event probability of historical risk scenario events; where the event probability is: the possibility of the occurrence of historical risk scenario events, for example: the event probability of a child bumping into furniture at home is the number of times the child bumps into furniture in the living room divided by the total number of activities of the child in the living room;

[0117] Obtain historical risk scenario events and a preset risk event library, and determine the risk value of the historical risk scenario event; wherein the preset risk event library includes: one-to-one corresponding pre-selected risk events and pre-selected risk values. When determining the risk value, if the historical risk scenario event and the pre-selected risk event match consistently, the pre-selected risk value corresponding to the pre-selected risk event that matches consistently is used as the risk value;

[0118] According to the event probability and risk value, determine the necessary monitoring value of the historical risk scenario event; wherein the necessary monitoring value is: the result obtained by multiplying the event probability and the risk value;

[0119] If the monitoring necessary value is greater than or equal to the preset monitoring necessary value threshold, the corresponding historical risk scenario event is used as the target scenario event; wherein the preset monitoring necessary value threshold is manually preset;

[0120] Obtain the manual collaborative monitoring control record of the collaborative edge device in the target scene event and use it as the second pre-selected historical collaborative record; wherein the collaborative monitoring control record is: the record of manually operating the collaborative edge device to monitor the target scene event that will occur in the future after the target scene event occurs, for example: after a child at home hits the furniture, when the child is active in the living room at 3 pm every day, the family sets the monitoring task of the preset camera in the living room and the monitoring task of the mobile camera;

[0121] taking the first pre-selected historical collaboration record and the second pre-selected historical collaboration record together as the historical collaboration record;

[0122] Among them, according to the historical collaboration records, the collaborative functions, collaborative operation instructions and historical usage frequencies are summarized, including:

[0123] Based on the edge device collaborative feature extraction template, the edge device collaborative feature is extracted according to the historical collaborative record; wherein the edge device collaborative feature extraction template is: a template for extracting the edge device collaborative feature (edge ​​device ID, edge device trigger instruction and trigger logic (the triggering sequence relationship of the edge device trigger instruction) by comparing the historical collaborative record;

[0124] Perform feature clustering on the edge device collaboration features to obtain multiple cluster feature sets; wherein the cluster feature set is: a set of edge device collaboration features extracted from similar historical collaboration records;

[0125] Traverse each cluster feature set in turn to obtain the target cluster feature set currently being traversed;

[0126] Calculate the cluster feature value mean of the cluster feature value of each feature type in the target cluster feature set, and construct the corresponding characterization feature vector of the target cluster feature set according to the cluster feature value mean corresponding to each feature type; wherein the cluster feature value mean is: the representative value of the cluster feature value corresponding to the feature type, for example: the mean value of the summer air conditioning setting temperature recorded in the historical collaborative record after the electronic lock is unlocked when returning home in summer;

[0127] Based on the collaborative function description template, the collaborative function is determined according to the historical collaborative records corresponding to the representation feature vector; wherein the collaborative function description template is: a semantic analysis template, which is used to understand the historical collaborative records, and input the understanding semantics into the semantic understanding model to obtain the collaborative function that is to be achieved by the historical collaborative records corresponding to the representation feature vector;

[0128] Determine the collaborative operation instruction according to the characterizing feature vector; wherein the collaborative operation instruction is: a control instruction sequence of the collaborative edge device that realizes the collaborative function;

[0129] Determine the historical usage frequency based on a first total number of historical collaboration records extracted from the target cluster feature set and a second total number of historical collaboration records; wherein the historical usage frequency is a result obtained by dividing the first total number by the second total number;

[0130] When each cluster feature set has been traversed, the induction is completed.

[0131] The working principle and beneficial effects of the above technical solution are:

[0132] After the edge device is connected to the IoT platform, in addition to obtaining data and other resources of the IoT platform, it will also collaborate with other edge devices connected to the IoT platform to achieve more functions. Therefore, after successful verification, the user will be shown the linkable edge devices of the target edge device, determine the target linkable edge device selected by the user, and recommend the target edge device and the linkable edge device's collaborative control instructions to the user;

[0133] When determining the target linkable edge device selected by the user and recommending shortcut commands to the user, the historical collaboration record of the collaborative edge device is obtained. Specifically, when obtaining the historical collaboration record, the associated scenario of the collaborative edge device is determined, and the setting time interval and setting frequency of the collaborative edge device in the personnel setting record of the associated scenario are obtained. Generally, the shorter the setting time interval, the more the other collaborative edge device needs to be triggered and set immediately after one collaborative edge device is triggered, and the higher the collaboration rate is. Therefore, the customary setting collaboration rate is calculated according to the setting time interval and setting frequency (the shorter the setting time interval and the higher the setting frequency, the higher the collaboration rate), and the first pre-selected historical collaboration record with a collaboration rate greater than or equal to the collaboration rate threshold is screened; the historical risk scenario events of the associated scenario are obtained, and the event probability and risk value of the historical risk scenario events are calculated. The greater the event probability and the higher the risk value, the more necessary it is to monitor. Therefore, in addition to the user's customary settings, the manual collaborative monitoring control record of the collaborative edge device in the target scenario event with a monitoring necessity value greater than or equal to the monitoring necessity value threshold is obtained as the second pre-selected historical collaboration record, and the first pre-selected historical collaboration record and the second pre-selected historical collaboration record are used together as historical collaboration records for the generation of subsequent shortcut command lists, thereby improving the comprehensiveness of the acquisition of collaborative control requirements of IoT devices.

[0134] An edge device collaborative feature extraction template is introduced, and the edge device ID, edge device trigger instructions and trigger logic (edge ​​device collaborative features) in the historical collaborative records are extracted. The edge device collaborative features are clustered to obtain multiple cluster feature sets. According to the preset representative value extraction method of the cluster feature value of each feature type in the target cluster feature set, the mean of the cluster feature value is extracted. For example, if the feature type is edge device ID, the representative value extraction method is to filter the edge device ID contained in each corresponding extracted historical collaborative record; for example, if the feature type is trigger logic, the representative value extraction method is to extract the average trigger interval duration; according to the mean of the cluster feature value corresponding to each feature type, a representation feature vector corresponding to the target cluster feature set is constructed; a collaborative function description template is introduced to understand the historical collaborative records, and the understanding semantics is input into the semantic understanding model to obtain the representation feature vector corresponding to the collaborative function that the extracted historical collaborative records want to achieve; according to the representation feature vector, a control instruction sequence of the collaborative edge device that realizes the collaborative function is determined; the first total number of historical collaborative records extracted by the target cluster feature set is divided by the second total number of historical collaborative records to obtain the historical usage frequency.

[0135] The present invention obtains the historical collaboration records of the target linkable edge device and the target edge device selected by the target user, introduces an edge device collaboration feature extraction template, extracts the edge device collaboration features according to the historical collaboration records, clusters the edge device collaboration features extracted from similar historical collaboration records, and constructs a characterization feature vector corresponding to each cluster feature set; determines the collaboration operation instructions, collaboration function description and historical usage frequency based on the characterization feature vector, and then recommends shortcut instructions, which is more reasonable and humane.

[0136] In one embodiment, a shortcut command list is displayed to the user, including:

[0137] Obtaining sight information of the user when viewing the shortcut command list; wherein the sight information is: the sight track of the user when viewing the shortcut command list, obtained according to the sight extraction technology;

[0138] According to the sight information, a viewing shortcut command sequence is obtained; wherein the viewing shortcut command sequence is: a sequence obtained by sorting the shortcut commands in the order of viewing time;

[0139] Based on the editing intention instruction extraction condition, the editing intention instruction is obtained according to the viewing shortcut instruction sequence; wherein the editing intention instruction is: the shortcut instruction that the user wants to edit;

[0140] Obtain similar sub-instructions of the editing intention instruction; wherein the similar sub-instructions are: sub-instructions of similar execution operation parts of the editing intention instruction;

[0141] Obtaining the editing rules of the missing instruction part of the similar sub-instructions; wherein, when determining the missing instruction part, first determine the instruction structure of the overall execution operation part according to the most recently viewed editing intention instruction, the instruction structure is: instruction execution subject and execution action relationship, determine the local execution subject and execution action relationship according to the similar sub-instructions, determine the remaining instruction structure part except the local execution subject and execution action relationship as the editable part, and obtain the editing rules of the corresponding editable part;

[0142] Generate an editable template for the user to edit according to the editing rules and similar sub-instructions; wherein generating an editable template for the user to edit according to the editing rules and similar sub-instructions refers to: determining optional editing items according to the editing rules, such as: the execution subject of the remaining instruction structure part and its corresponding allowed execution action options;

[0143] Among them, the editing intention instruction extraction conditions include:

[0144] The editing intention instruction is the viewing shortcut instruction of the first instruction number at the end of the viewing shortcut instruction sequence; wherein the first instruction number is the instruction number of the editing intention instruction;

[0145] The first instruction number of the editing intention instruction is an integer multiple of the second instruction number preset for the repetitive feature of the editing intention instruction; wherein the repetitive feature is: the repetitive relationship between different editing intention instructions, for example: the number of different editing intention instructions in the editing intention instruction is 3, then the repetitive feature includes: the repetitive relationship between two different editing intention instructions, the repetitive relationship between three different editing intention instructions; the second instruction number preset for the repetitive feature is: the number of different editing intention instructions in the repetitive relationship corresponding to the repetitive feature of different editing intention instructions, for example: the repetitive relationship between three different editing intention instructions, the preset second instruction number is 3;

[0146] The repetition feature meets the standard repetition feature; wherein the standard repetition feature is: the standard repetition relationship of different editing intent instructions corresponding to different numbers of editing intent instructions in the editing intent instruction, for example: the number of different editing intent instructions in the editing intent instruction is 3, and the standard repetition feature is: the repetition relationship of three different editing intent instructions;

[0147] The first instruction number is greater than or equal to a preset first threshold; wherein the preset first threshold is an integer greater than or equal to 2;

[0148] The integer multiple is greater than or equal to a preset first threshold and less than or equal to a preset second threshold; wherein the preset second threshold is manually preset, for example: 4;

[0149] The execution subject in the editing intention instruction is consistent.

[0150] The working principle and beneficial effects of the above technical solution are:

[0151] When users view shortcut commands, they may not be able to directly obtain the desired commands, but they can edit and modify the existing commands. This eliminates the need for users to relearn and set the rules for IoT linkage calls, making it more convenient.

[0152] Specifically, the user's sight information when viewing the shortcut command list is obtained to determine the shortcut command sequence to be viewed. Since the user will select the editing intention command with lower editing cost when rewriting, there will be a comparison action. The command concentrated at the end of the sequence in the real-time viewing shortcut command sequence is more likely to be the editing intention command that the user wants to edit. The editing intention command extraction conditions are introduced, including:

[0153] Condition 1: The editing intention instruction is the first instruction in the last viewing shortcut instruction sequence, which constrains the editing intention instruction to be at the end of the viewing shortcut instruction sequence, indicating that the editing intention instruction is extracted in real time based on the line of sight information, thereby improving the timeliness of intention extraction;

[0154] Condition 2: the number of first instructions of the editing intention instruction is an integer multiple of the number of second instructions preset by the repetitive feature of the editing intention instruction, so as to improve the extraction accuracy of the editing intention instruction;

[0155] Condition 3: The repeated features meet the standard repeated features, which improves the comprehensiveness of editing intent instruction screening;

[0156] Condition 4: The number of first instructions is greater than or equal to a preset first threshold, the constraint contains at least two instructions with different editing intentions, and the constraint has a comparison premise;

[0157] Condition 5: The integer multiple is greater than or equal to the preset first threshold and less than or equal to the preset second threshold. The constraint is that there is a comparison action and the number of comparisons is less than or equal to the second threshold. There is a comparison action but not too much comparison (implying a hesitant intention), which improves the suitability of determining the editing intention instruction.

[0158] Condition 6: The execution subject in the editing intention instruction is consistent, and the execution edge device in the constraint instruction is consistent;

[0159] The above six conditions are introduced as editing information extraction conditions to improve the efficiency of editing information extraction. After the editing information extraction conditions are met, similar sub-instructions of the corresponding editing intention instructions are extracted, and then the editing rules of the missing instruction parts of the similar sub-instructions are introduced. According to the editing rules and similar sub-instructions, an editable template is generated for users to edit, thereby improving the standardization of edge device linkage shortcut instruction editing.

[0160] The embodiment of the present invention provides a security authentication system for IoT edge devices, such as Figure 2 As shown, including:

[0161] Application subsystem 1, used to generate key files and security certificates according to the application information filled in by the user on the IoT platform;

[0162] Local storage subsystem 2, used to obtain the local security certificate and local private key stored by the user on the edge device;

[0163] The security authentication subsystem 3 is used to initiate security authentication to the IoT platform based on the local security certificate and the local private key;

[0164] The verification result is returned to the subsystem 4, which is used to return the verification result.

[0165] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A security authentication method for an IoT edge device, characterized in that: include: Step 1: Generate a key file and security certificate based on the application information filled in by the user on the IoT platform; Step 2: Obtain the local security certificate and local private key stored by the user on the target edge device; Step 3: Initiate security authentication to the IoT platform based on the local security certificate and local private key; Step 4: Return the verification result.

2. A security authentication method for an IoT edge device as claimed in claim 1, characterized in that: Step 1: Generate a key file and security certificate based on the application information filled in by the user on the IoT platform, including: Obtain the application information filled in by the user when logging into the IoT platform. The application information includes: the device created by the user, the SDK version and the development language; Generate a public key and private key pair based on the IoT platform and application information; Generate a key file and security certificate based on the public key and private key pair.

3. A security authentication method for an IoT edge device as claimed in claim 1, characterized in that: Step 2: Obtain the local security certificate and local private key stored by the user on the target edge device, including: Obtain the download security certificate and download key file downloaded by the user; Access the current active policy version and change the required topic; After the required topic is changed, configure mqttx and obtain the local security certificate and local private key.

4. A security authentication method for an IoT edge device as claimed in claim 1, characterized in that: Step 3: Initiate security authentication to the IoT platform based on the local security certificate and local private key, including: Obtain the local security certificate and local private key read by the target edge device, parse the local security certificate and extract the local public key; Encrypt according to the application name and local private key, and initiate an authentication request to the IoT platform based on the encrypted ciphertext.

5. A security authentication method for an IoT edge device as claimed in claim 1, characterized in that: Step 4: Return verification results, including: The IoT platform verifies the application name based on the ciphertext and returns a verification success or verification failure.

6. A security authentication method for an IoT edge device as claimed in claim 1, characterized in that: Also includes: Step 5: If the verification result is successful, the linkable edge devices of the target edge device are displayed to the user, the target linkable edge device selected by the user is determined, and a shortcut command is recommended to the user.

7. A security authentication method for an IoT edge device as claimed in claim 6, characterized in that: Determine the target selected by the user to link the edge device and recommend shortcut commands to the user, including: The target linkable edge device and the target edge device selected by the target user are used together as collaborative edge devices; Obtain historical collaboration records of collaborative edge devices; According to historical collaboration records, summarize collaboration functions, collaboration operation instructions and historical usage frequency; Generate a list of shortcut commands based on collaborative functions, collaborative operation commands and historical usage frequency; Display a list of shortcuts to the user; Among them, obtaining the historical collaboration records of collaborative edge devices includes: Obtain the associated scenarios of collaborative edge devices; According to the associated scene, obtain the personnel setting records of the scene personnel; Determine the setting time interval and setting frequency of the collaborative edge device based on the personnel setting records; Calculate the coordination rate of habit settings based on the setting time interval and setting frequency; If the collaboration rate is greater than or equal to the preset collaboration rate threshold, the corresponding personnel setting record is used as the first pre-selected historical collaboration record; Obtain historical risk scenario events based on associated scenarios; Obtain event probabilities of historical risk scenario events; Obtain historical risk scenario events and preset risk event libraries to determine the risk values ​​of historical risk scenario events; Determine the necessary monitoring values ​​for historical risk scenario events based on event probability and risk value; If the monitoring necessary value is greater than or equal to the preset monitoring necessary value threshold, the corresponding historical risk scenario event is used as the target scenario event; Obtaining manual collaborative monitoring and control records of collaborative edge devices in target scenario events, and using them as second pre-selected historical collaborative records; The first pre-selected historical collaboration record and the second pre-selected historical collaboration record are taken together as the historical collaboration record.

8. A security authentication method for an IoT edge device as claimed in claim 7, characterized in that: Based on historical collaboration records, summarize collaboration functions, collaboration operation instructions and historical usage frequency, including: Based on the edge device collaborative feature extraction template, the edge device collaborative features are extracted according to the historical collaborative records; Perform feature clustering on the collaborative features of edge devices to obtain multiple cluster feature sets; Traverse each cluster feature set in turn to obtain the target cluster feature set currently being traversed; Calculate the cluster feature value mean of the cluster feature value of each feature type in the target cluster feature set, and construct the characterization feature vector corresponding to the target cluster feature set according to the cluster feature value mean corresponding to each feature type; Based on the collaborative function description template, the collaborative function is determined according to the historical collaborative records corresponding to the extracted characteristic vectors; Determine the collaborative operation instruction according to the characterizing feature vector; determining a historical usage frequency based on a first total number of historical collaboration records extracted from the target cluster feature set and a second total number of historical collaboration records; When each cluster feature set has been traversed, the induction is completed.

9. A security authentication method for an IoT edge device as claimed in claim 7, characterized in that: Display a list of shortcuts to the user, including: Get the user's sight information when viewing the shortcut command list; Obtain and view the shortcut command sequence according to the line of sight information; Based on the editing intention instruction extraction condition, the editing intention instruction is obtained according to the viewing shortcut instruction sequence; Get similar sub-commands of the editing intention command; Obtaining editing rules for missing instruction parts of similar sub-instructions; Generate editable templates for users to edit based on editing rules and similar sub-instructions; Among them, the editing intention instruction extraction conditions include: The editing intention instruction is to view the shortcut instruction numbered last in the shortcut instruction sequence; The first instruction number of the editing intention instruction is an integer multiple of the second instruction number preset for the repetitive feature of the editing intention instruction; Repeating features conform to standard repeating features; The first instruction number is greater than or equal to a preset first threshold; The integer multiple is greater than or equal to a preset first threshold and less than or equal to a preset second threshold; The execution subject in the editing intention instruction is consistent.

10. A security authentication system for IoT edge devices, characterized in that: include: The application subsystem is used to generate key files and security certificates based on the application information filled in by the user on the IoT platform; The local storage subsystem is used to obtain the local security certificate and local private key stored by the user on the edge device; The security authentication subsystem is used to initiate security authentication to the IoT platform based on the local security certificate and local private key; The verification result return subsystem is used to return the verification result.

Images