A security authentication method and system for IoT edge devices

Abstract

The present invention provides a method and system for secure authentication of an IoT edge device, wherein the method comprises: Step 1: generating a key file and a security certificate based on application information entered by a user on an IoT platform; Step 2: obtaining the local security certificate and local private key stored by the user on the target edge device; Step 3: initiating security authentication to the IoT platform based on the local security certificate and local private key; and Step 4: returning a verification result. The method and system for secure authentication of an IoT edge device of the present invention implement an automated identity authentication process through a digital certificate downloaded by the edge device, eliminating the need for users to manually perform identity authentication each time, thereby improving device computing efficiency. Furthermore, the digital certificate contains the device's public key information and additional security attributes, and authentication through the digital certificate can provide a higher level of security.

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, a major challenge facing the deployment of edge devices in the IoT (Internet of Things) is ensuring secure device communication and authentication within resource-limited devices. Most existing cryptographic algorithms and solutions for device security are only suitable for desktop or server devices, consuming excessive computing resources for IoT edge devices. Traditional login authentication relies solely on usernames and passwords, making it vulnerable to man-in-the-middle attacks and password cracking, resulting in weak security.

[0003] In view of this, there is an urgent need for a security authentication method and system for IoT edge devices to at least address 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 implements an automated identity authentication process through digital certificates downloaded from edge devices. 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 device's public key information and additional security attributes, and authentication through digital certificates can provide a higher level of security.

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

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

[0007] Step 2: Obtain the user's local security certificate and local private key stored 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 based on 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: user-created device, SDK version, and development language;

[0012] Generate public and private key pairs 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 the user's local security certificate and local private key stored on the target edge device includes:

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

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

[0017] After changing the required topic, configure MQTTX and obtain the local security certificate and local private key.

[0018] Preferably, step 3: initiating security authentication to the IoT platform based on 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 to extract the local public key;

[0020] The application name and local private key are encrypted, and an authentication request is sent 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 failure.

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

[0024] Step 5: If the verification result is successful, the user is shown the linkable edge devices of the target edge device, 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] Based on historical collaboration records, summarize collaboration functions, collaboration operation instructions and historical usage frequency;

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

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

[0031] The historical collaboration records of collaborative edge devices are obtained, including:

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

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

[0034] Determine the setting time interval and frequency of collaborative edge devices based on 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 the event probability of historical risk scenario events;

[0039] Obtain historical risk scenario events and a preset risk event library to determine the risk value 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 as the second pre-selected historical collaborative records;

[0043] The first pre-selected historical collaboration record and the second pre-selected historical collaboration record are collectively regarded 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 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 extracted corresponding to the characteristic feature vector;

[0050] Determine collaborative operation instructions based on the characterization feature vector;

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

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

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

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

[0055] Obtain and view the shortcut command sequence based on the line of sight information;

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

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

[0058] Get the editing rules for the 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 last and first instruction number of 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 repetition feature of the editing intention instruction;

[0063] Repeating features conform to standard repeating features;

[0064] The number of first instructions 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 entered by the user on the IoT platform;

[0069] The local storage subsystem is used to obtain the user's local security certificate and local private key stored 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 is returned to the subsystem, which 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 the digital certificate downloaded by the edge device. The user does not need to manually perform identity authentication every time, which improves 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 the 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 in part will become apparent from the description, or will be understood by practicing the present invention. The purpose and other advantages of the present invention can be achieved and obtained through the structures specifically pointed out in this application document.

[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 according to 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 with reference to 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 IoT edge devices, such as Figure 1 Shown, including:

[0081] Step 1: Generate a key file and security certificate based on the application information entered 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] Step 1: Generate a key file and security certificate based on the application information entered 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: user-created device, SDK version, and development language;

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

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

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

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

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

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

[0093] Step 3: Initiate 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 to extract the local public key;

[0095] Encrypt the application name and local private key, and then send an authentication request to the IoT platform based on the encrypted ciphertext.

[0096] Among them, step 4: returns the verification result, including:

[0097] The IoT platform verifies the application name based on the ciphertext and returns a verification success or 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 an 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 connect 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 (the 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 the digital certificate downloaded by the edge device. The user does not need to manually perform identity authentication every time, which improves 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 the 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 user is presented with the linkable edge devices of the target edge device, the target linkable edge device selected by the user is determined, and a shortcut command is recommended to the user. 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 light. The recommended shortcut command is a collaborative control command between 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 light within 1 second after the unlock 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. Historical collaboration records include records of collaborative work performed by collaborative edge devices, such as turning on the living room light after unlocking the electronic lock or turning on the bedroom air circulation fan after turning on the bedroom air conditioner.

[0106] Based on historical collaboration records, collaborative functions, collaborative operation instructions, and historical usage frequencies are summarized. A collaborative function is a description of the collaborative effects of collaborative edge devices. For example, unlocking the electronic lock to turn on the living room light is called "smart home return," and turning on the bedroom air conditioner to turn on the bedroom air circulation fan is called "collaborative cooling." Collaborative operation instructions are the control instructions for the corresponding collaborative edge devices when implementing the collaborative function. Historical usage frequencies are the historical usage frequencies 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 collaborative function descriptions in descending order of historical usage frequency. Users click on a collaborative function description to set the corresponding collaborative function. When the collaborative function setting conditions are met, the system automatically executes the collaborative operation instruction.

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

[0109] The historical collaboration records of collaborative edge devices are obtained, including:

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

[0111] Based on the associated scenario, obtain the personnel setting records of the scenario personnel. The personnel setting records are the records of the settings of the collaborative edge devices made by the personnel in the associated scenario in the past, such as turning on the living room lights after opening the door and adjusting the air conditioner to 26°C.

[0112] Determine the setup time interval and setup frequency of the collaborative edge devices based on the personnel setup records; the setup time interval is defined as the startup time difference between each pair of collaborative edge devices in the same personnel setup record; and the setup frequency is defined as the number of personnel setup records corresponding to the setup time interval divided by the total number of personnel setup records.

[0113] Calculate the coordination rate of custom settings based on the setting time interval and setting frequency; custom settings are: the personnel setting records corresponding to the setting time interval; coordination rate is: the inverse 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 pre-set;

[0115] Obtain historical risk scenario events based on associated scenarios. Historical risk scenario events are risk events in associated scenarios, such as a child bumping into furniture at home.

[0116] Obtain the event probability of historical risk scenario events; where the event probability is: the likelihood of the historical risk scenario event occurring. 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 times the child moves 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 correspondence between 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, the pre-selected risk value corresponding to the matching pre-selected risk event is used as the risk value;

[0118] Determine the necessary monitoring value for historical risk scenario events based on the event probability and risk value; the necessary monitoring value is the product of 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 pre-set;

[0120] Obtain the manual collaborative monitoring and control records of the collaborative edge device during the target scene event and use them as the second pre-selected historical collaborative record. The collaborative monitoring and control records are records of manual operation of the collaborative edge device to monitor future target scene events after the target scene event occurs. For example, after a child at home bumps into furniture, the family sets monitoring tasks for the preset camera in the living room and the mobile camera every day at 3 pm when the child is active in the living room.

[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, based on historical collaboration records, collaborative functions, collaborative operation instructions and historical usage frequencies are summarized, including:

[0123] Based on the edge device collaboration feature extraction template, edge device collaboration features are extracted according to historical collaboration records. The edge device collaboration feature extraction template is used to extract edge device collaboration features (edge device ID, edge device trigger instructions, and trigger logic (the triggering order of edge device trigger instructions)) based on historical collaboration records.

[0124] Perform feature clustering on the edge device collaboration features to obtain multiple cluster feature sets; wherein the cluster feature set is: a collection 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 values of each feature type in the target cluster feature set. Based on the cluster feature value mean corresponding to each feature type, construct the corresponding representation feature vector of the target cluster feature set. The cluster feature value mean is: the representative value of the cluster feature value corresponding to the feature type. For example, after unlocking the electronic lock when returning home in the summer, the air conditioner is set to the mean of the summer air conditioner setting temperature recorded in the historical collaboration record.

[0127] Based on the collaborative function description template, the collaborative function is determined according to the historical collaborative records extracted based on the representation feature vectors. The collaborative function description template is a semantic analysis template used to understand the historical collaborative records. The semantic understanding is input into the semantic understanding model to obtain the collaborative function to be achieved by the historical collaborative records extracted based on the representation feature vectors.

[0128] Determine a collaborative operation instruction based on the characterization feature vector; wherein the collaborative operation instruction is: a control instruction sequence of the collaborative edge device that realizes the collaborative function;

[0129] Determining a historical usage frequency based on a first total number of historical collaboration records and a second total number of historical collaboration records extracted from the target cluster feature set; 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 from 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 target edge device's linked edge devices, determine the target linkable edge device selected by the user, and recommend collaborative control instructions for the target edge device and the linkable edge device 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 records of the collaborative edge devices are obtained. Specifically, when obtaining the historical collaboration records, the associated scenarios of the collaborative edge devices are determined, and the setting time interval and setting frequency of the collaborative edge devices in the personnel setting records of the associated scenarios are obtained. Generally, the shorter the setting time interval, the more the other collaborative edge devices need to be triggered immediately after one collaborative edge device is triggered, and the higher the collaboration rate. Therefore, the customary setting collaboration rate is calculated based on 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 records with a collaboration rate greater than or equal to the collaboration rate threshold are filtered; the historical risk scenario events of the associated scenarios 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 and control records of the collaborative edge devices in the target scenario events with a monitoring necessity value greater than or equal to the monitoring necessity value threshold are obtained as the second pre-selected historical collaboration records. The first pre-selected historical collaboration record and the second pre-selected historical collaboration record are used together as historical collaboration records for generating 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. The cluster feature value mean is extracted according to the preset representative value extraction method of the cluster feature value of each feature type in the target cluster feature set. 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 cluster feature value mean 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 extracted historical collaborative records to achieve the collaborative function; according to the representation feature vector, the control instruction sequence of the collaborative edge device that realizes the collaborative function is determined; the first total number of historical collaborative records extracted from 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 based on 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; based on the characterization feature vector, the collaboration operation instructions, collaboration function description and historical usage frequency are determined, and then shortcut instructions are recommended, which is more reasonable and humane.

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

[0137] Obtaining the user's gaze information when viewing the shortcut command list; wherein the gaze information is: the user's gaze trajectory when viewing the shortcut command list, obtained based on the gaze extraction technology;

[0138] Obtaining a viewing shortcut command sequence based on the line of sight information; wherein the viewing shortcut command sequence is a sequence obtained by sorting the shortcut commands in 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] Obtaining 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 editing rules for missing instruction parts of similar sub-instructions; wherein, when determining the missing instruction parts, first determine the instruction structure of the overall execution operation part based on the most recently viewed editing intention instruction, the instruction structure comprising: an instruction execution subject and an execution action relationship, determine a local execution subject and an execution action relationship based on similar sub-instructions, determine the remaining instruction structure parts excluding the local execution subject and execution action relationship as editable parts, and obtain editing rules for the corresponding editable parts;

[0142] Generate an editable template for user editing based on the editing rules and similar sub-instructions; wherein generating an editable template for user editing based on the editing rules and similar sub-instructions refers to determining optional editing items based on the editing rules, such as the execution subject of the remaining instruction structure and its corresponding allowed 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 repetition feature of the editing intention instruction; wherein the repetition feature is: a repetition relationship between different editing intention instructions, for example: if the number of different editing intention instructions in the editing intention instruction is 3, then the repetition feature includes: a repetition relationship between two different editing intention instructions, and a repetition relationship between three different editing intention instructions; the second instruction number preset for the repetition feature is: the number of different editing intention instructions in the repetition relationship corresponding to the different editing intention instructions of the repetition feature, for example: if the repetition relationship is three different editing intention instructions, the preset second instruction number is 3;

[0146] The repetition feature conforms to the standard repetition feature; wherein the standard repetition feature is: the standard repetition relationship of different editing intent instructions corresponding to the number of different editing intent instructions in the editing intent instruction. For example, if the number of different editing intent instructions in the editing intent instruction is 3, 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 up IoT linkage call rules, making it more convenient.

[0152] Specifically, we obtain the user's line of sight when viewing the shortcut command list to determine the shortcut command sequence to be viewed. Since users tend to select editing intent commands with lower editing costs when rewriting, they will perform a comparison. In real-time viewing of the shortcut command sequence, the commands concentrated at the end of the sequence are more likely to be the editing intent commands that the user wants to edit. Therefore, we introduce the editing intent command extraction conditions, including:

[0153] Condition 1: The edit intent command is the first command in the last view shortcut command sequence. This constraint places the edit intent command at the end of the view shortcut command sequence, indicating that the edit intent command is extracted in real time based on line of sight information, improving the timeliness of intent extraction.

[0154] Condition 2: 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, thereby improving the extraction accuracy of the editing intention instruction;

[0155] Condition 3: Repeat features meet standard repeat features, improving 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. This condition constrains the existence of a comparison action and the number of comparisons is less than or equal to the second threshold. The presence of a comparison action without excessive comparisons (implying a hesitant intention) 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 Shown, including:

[0161] Application subsystem 1 is used to generate key files and security certificates based on the application information entered by the user on the IoT platform;

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

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

[0164] Verification result return subsystem 4 is used to return the verification result.

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

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 user's local security certificate and local private key stored 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; Step 5: If the verification result is successful, the user is presented with the linkable edge devices of the target edge device, the target linkable edge device selected by the user is determined, and a shortcut command is recommended 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; Based on historical collaboration records, summarize collaboration functions, collaboration operation instructions and historical usage frequency; Generate a shortcut command list based on collaborative functions, collaborative operation instructions and historical usage frequency; Display a list of shortcuts to the user; The historical collaboration records of collaborative edge devices are obtained, including: Determine the setting time interval and setting frequency of the collaborative edge device according to the personnel setting record of the scene personnel in the associated scene of the collaborative edge device; 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; Determine the necessary monitoring values for historical risk scenario events based on the event probability and risk value of the historical risk scenario events in the associated scenarios; 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 as the second pre-selected historical collaborative records; The first pre-selected historical collaboration record and the second pre-selected historical collaboration record are used together as the historical collaboration record; Among them, the shortcut command list is displayed to the user, including: Based on the editing intention instruction extraction condition, the editing intention instruction is obtained according to the viewing shortcut instruction sequence determined from the line of sight information when the user views the shortcut instruction list; Generate an editable template for the user to edit according to the editing rules of the missing instruction part of the similar sub-instruction of the editing intention instruction and the similar sub-instruction; Among them, the editing intention instruction extraction conditions include: The editing intention instruction is to view the last and first instruction number of 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 repetition feature of the editing intention instruction; Repeating features conform to standard repeating features; The number of first instructions 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.

2. The security authentication method for an IoT edge device according to claim 1, wherein: 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: user-created device, SDK version, and development language; Generate public and private key pairs 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. The security authentication method for an IoT edge device according to claim 1, wherein: 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 currently active policy version and change the required topic; After changing the required topic, configure MQTTX and obtain the local security certificate and local private key.

4. A security authentication method for an IoT edge device according to 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 to extract the local public key; The application name and local private key are encrypted, and an authentication request is sent to the IoT platform based on the encrypted ciphertext.

5. The security authentication method for an IoT edge device according to claim 1, wherein: Step 4: Return verification results, including: The IoT platform verifies the application name based on the ciphertext and returns a verification success or failure.

6. A security authentication method for an IoT edge device according to claim 1, 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 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 extracted corresponding to the characteristic feature vector; Determine collaborative operation instructions based on the characterization feature vector; determining a historical usage frequency based on a first total number of historical collaboration records and a second total number of historical collaboration records extracted from the target cluster feature set; When each cluster feature set has been traversed, the induction is completed.

7. 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 entered by the user on the IoT platform; The local storage subsystem is used to obtain the user's local security certificate and local private key stored 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; The IoT edge device security authentication system also performs the following operations: If the verification result is successful, the user is shown the target edge device's linked edge devices, the target linked edge device selected by the user is determined, and a shortcut command is recommended 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; Based on historical collaboration records, summarize collaboration functions, collaboration operation instructions and historical usage frequency; Generate a shortcut command list based on collaborative functions, collaborative operation instructions and historical usage frequency; Display a list of shortcuts to the user; The historical collaboration records of collaborative edge devices are obtained, including: Determine the setting time interval and setting frequency of the collaborative edge device according to the personnel setting record of the scene personnel in the associated scene of the collaborative edge device; 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; Determine the necessary monitoring values for historical risk scenario events based on the event probability and risk value of the historical risk scenario events in the associated scenarios; 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 as the second pre-selected historical collaborative records; taking the first pre-selected historical collaboration record and the second pre-selected historical collaboration record together as the historical collaboration record; Among them, the shortcut command list is displayed to the user, including: Based on the editing intention instruction extraction condition, the editing intention instruction is obtained according to the viewing shortcut instruction sequence determined from the line of sight information when the user views the shortcut instruction list; Generate an editable template for the user to edit according to the editing rules of the missing instruction part of the similar sub-instruction of the editing intention instruction and the similar sub-instruction; Among them, the editing intention instruction extraction conditions include: The editing intention instruction is to view the last and first instruction number of 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 repetition feature of the editing intention instruction; Repeating features conform to standard repeating features; The number of first instructions 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.

Images