Automatic equipment configuration system and method and electronic equipment

Abstract

The invention belongs to the technical field of Internet of Things equipment management, and particularly relates to an automatic equipment configuration system and method and electronic equipment, and a to-be-configured device firstly and autonomously selects a target edge gateway from an accessible gateway list, and actively sends a connection request containing own information to the target edge gateway; after receiving the request, the edge gateway verifies the equipment, and if the verification is passed, equipment information and own gateway information are packaged together and sent to the cloud platform; the cloud platform matches corresponding configuration parameters according to the received information, generates verification information and sends the verification information to the user terminal for authorization confirmation; and after the user completes verification, the cloud platform issues the final configuration parameters to the equipment, and the equipment completes automatic configuration. According to the system, remote one-key deployment of large-scale and cross-region equipment without field manual intervention is realized. The problems that a traditional mode is low in configuration efficiency and high in labor cost are effectively solved. Meanwhile, the user authorization link enhances the security of the configuration process.

Description

Automatic configuration systems, methods and electronic equipment Technical Field

[0001] This application belongs to the field of Internet of Things (IoT) device management technology, specifically relating to an automatic device configuration system, method, and electronic device. Background Technology

[0002] With the rapid development of IoT technology, the scale of connected devices in fields such as smart homes, industrial IoT, smart cities, and remote monitoring is growing exponentially. In industrial workshops, thousands of sensors, actuators, and monitoring devices need to be rapidly deployed and configured to achieve real-time data collection and remote control. In smart city scenarios, tens of thousands of streetlights, environmental monitoring terminals, traffic cameras, and other devices need to work collaboratively across regions and protocols, and their configuration efficiency directly affects the speed at which the city's level of intelligence is improved.

[0003] In existing technologies, device network configuration still relies on manual operation or automatic discovery within a local area network, which cannot meet the needs of large-scale, cross-regional remote automated deployment. For example, environmental monitoring equipment deployed in remote areas (such as soil moisture sensors and hydrological monitoring terminals) needs to be connected via low-power wide area networks, resulting in low equipment configuration efficiency and high labor costs. In addition, if equipment malfunctions after deployment, maintenance personnel need to conduct on-site troubleshooting, further increasing maintenance costs.

[0004] Therefore, there is an urgent need for an efficient device configuration solution to meet the practical needs of large-scale, low-cost, and efficient deployment of IoT devices. Summary of the Invention

[0005] To address the aforementioned issues, this application provides an automatic device configuration system, method, and electronic device.

[0006] In a first aspect, this application provides an automatic device configuration system, the system comprising: at least one device to be configured, an edge gateway, and a cloud platform.

[0007] The device to be configured is used to determine the target edge gateway based on the list of accessible edge gateways, and send a connection request to the edge gateway; the connection request includes the device to be configured information;

[0008] The edge gateway is used to verify the device to be configured based on the connection request. If the verification is successful, it sends configuration information to the cloud platform. The configuration information includes the device to be configured information and the edge gateway information.

[0009] The cloud platform is used to determine the corresponding configuration parameters based on the configuration information; generate verification information and send the verification information to the user terminal; after the user terminal completes the verification based on the verification information, the configuration parameters are sent to the device to be configured.

[0010] The device to be configured is also used to perform network configuration based on the configuration parameters.

[0011] In one possible implementation, the device to be configured includes multiple communication modules, each supporting a different communication protocol, and the device to be configured is specifically used for:

[0012] Activate multiple communication modules in a preset order and obtain a list of accessible edge gateways obtained by scanning the multiple communication modules;

[0013] For each candidate edge gateway in the list of accessible edge gateways, key parameters of the candidate edge gateway are collected, including at least one of signal strength, packet loss rate, and response latency.

[0014] Based on the key parameters of the candidate edge gateways, the target access edge gateway is determined;

[0015] Send a connection request to the edge gateway.

[0016] In one possible implementation, the device to be configured is specifically used for:

[0017] The adaptation score of the candidate edge gateway is determined based on the key parameters and corresponding weights of the candidate edge gateway; wherein the signal strength is positively correlated with the adaptation score, and the packet loss rate and the response latency are negatively correlated with the adaptation score, respectively.

[0018] The candidate edge gateway with the highest adaptation score is determined as the target access edge gateway.

[0019] In one possible implementation, the device to be configured is further used for:

[0020] If there are multiple candidate edge gateways with the same adaptation score, the priority of the communication module corresponding to the candidate edge gateway is determined.

[0021] The candidate edge gateway corresponding to the communication module with the highest priority is determined as the edge gateway for the target access; wherein, the lower the power consumption of the communication module, the higher its priority.

[0022] In one possible implementation, the device information to be configured includes the device model and device identifier, and the edge gateway is specifically used for:

[0023] Based on the device information to be configured and the preset device list, it is determined whether the device to be configured meets the verification conditions; wherein, the verification conditions include: matching the device model from the device list, and / or matching the key field of the device identifier from the device list;

[0024] If the conditions are met, the verification is successful, and the edge gateway information is obtained based on the gateway identifier and key parameters corresponding to the target access edge gateway.

[0025] Based on the device information to be configured and the edge gateway information, the configuration information is obtained and sent to the cloud platform.

[0026] In one possible implementation, the device information to be configured includes the device location, and the edge gateway is further used for:

[0027] If the device to be configured does not meet the verification conditions, then determine whether the device to be configured can be matched from the dynamic device list;

[0028] If so, the verification passes, and the configuration information is sent to the cloud platform;

[0029] If not, then based on the device location, determine whether to add the device to be configured to the dynamic device list.

[0030] In one possible implementation, the edge gateway is specifically used for:

[0031] Determine whether the device location is within a trusted geofence;

[0032] If the device is within a trusted geofence, a continuous request indication message is sent to the device to be configured, so that the device to be configured continuously sends a preset number of supplementary connection requests.

[0033] Based on the preset number of supplementary connection requests returned by the device to be configured, determine whether the device locations indicated by the preset number of supplementary connection requests are the same;

[0034] If they are the same, a dynamic device list addition request and the configuration information are sent to the cloud platform; the dynamic device list addition request is used to instruct the request to add the device to be configured to the dynamic device list.

[0035] In one possible implementation, the device information to be configured further includes inherent device attributes, device signal quality, and current time; the cloud platform is also used for:

[0036] The system receives the dynamic device list addition request and determines the trust score corresponding to the device to be configured based on the device information. The inherent attributes of the device are determined based on a preset mapping relationship to determine the corresponding trust score contribution. The device signal quality is positively correlated with the trust score. If the current position and the current time are in a preset active period, the contribution to the trust score will be greater.

[0037] The validity period of the device to be configured is determined based on the trust score; the trust score and the validity period are positively correlated.

[0038] The device to be configured and its corresponding validity period are updated to the dynamic device list to obtain the updated dynamic device list.

[0039] The updated list of dynamic devices is sent to each edge gateway.

[0040] Secondly, this application provides a device automatic configuration method, applied to a device automatic configuration system, the system including at least one device to be configured, an edge gateway, and a cloud platform, the method including:

[0041] The device to be configured determines the target edge gateway based on the list of accessible edge gateways and sends a connection request to the edge gateway; the connection request includes information about the device to be configured.

[0042] The edge gateway verifies the device to be configured based on the connection request. If the verification is successful, it sends configuration information to the cloud platform. The configuration information includes the device to be configured information and the edge gateway information.

[0043] The cloud platform determines the corresponding configuration parameters based on the configuration information; generates verification information and sends the verification information to the user terminal; after the user terminal completes the verification based on the verification information, the configuration parameters are sent to the device to be configured.

[0044] The device to be configured performs network configuration based on the configuration parameters.

[0045] Thirdly, this application provides an electronic device, comprising: at least one processor and a memory; wherein,

[0046] The memory stores computer-executed instructions;

[0047] The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the device automatic configuration method as described in the second aspect.

[0048] The automatic device configuration system, method, and electronic device provided in this application involve the device to be configured first autonomously selecting a target edge gateway from a list of accessible gateways and proactively sending a connection request containing its own information. Upon receiving the request, the edge gateway verifies the device; if verification is successful, it packages the device information along with its own gateway information and sends it to the cloud platform. The cloud platform matches the corresponding configuration parameters based on the received information and generates verification information, which is sent to the user terminal for authorization confirmation. After the user completes verification, the cloud platform then sends the final configuration parameters to the device, allowing the device to complete the automatic configuration. This system, through a collaborative mechanism of device autonomous gateway discovery, gateway security verification, centralized cloud management, and user authorization confirmation, achieves large-scale, cross-regional remote one-click deployment of devices without on-site manual intervention. It effectively solves the problems of low configuration efficiency and high labor costs associated with traditional methods, and is particularly suitable for the rapid deployment of low-power devices in remote areas. Simultaneously, the user authorization process enhances the security of the configuration process, preventing unauthorized device binding and laying an automated foundation for subsequent remote operation and maintenance. Attached Figure Description

[0049] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0050] Figure 1 is a structural diagram of the automatic device configuration system provided in an embodiment of this application;

[0051] Figure 2 is a flowchart of the edge gateway processing in the device automatic configuration system provided in the embodiment of this application;

[0052] Figure 3 is a flowchart of the automatic device configuration method provided in an embodiment of this application;

[0053] Figure 4 is a hardware schematic diagram of the electronic device provided in an embodiment of the present invention.

[0054] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0056] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented, for example, in orders other than those illustrated or described herein.

[0057] In this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0058] The existing technology still has the following problems:

[0059] The current equipment configuration requires on-site operation by technicians or manual pre-entry of information, which cannot achieve automated deployment across regions without human intervention, resulting in high labor costs and low efficiency when deploying large-scale equipment.

[0060] Different brands and models of devices are compatible with different communication protocols. Existing gateways lack a unified protocol conversion capability, requiring dedicated gateways to be configured for different devices, which increases deployment costs and limits flexible deployment.

[0061] Manually inputting parameters can easily lead to information leakage, and traditional solutions lack device authentication and configuration command encryption mechanisms, posing risks of unauthorized device access to the network and configuration information being tampered with.

[0062] Existing automatic configuration solutions only support discovery within a local area network and require devices to be pre-associated with a server. They cannot achieve cross-regional automatic identification and binding of devices without pre-association, making it difficult to meet temporary or dynamic deployment needs.

[0063] The configuration process is not logged, and if a fault occurs after the device is deployed, it needs to be checked on-site. This is especially problematic for devices that are difficult to operate on-site, resulting in high maintenance costs and slow response times.

[0064] To address the problems in existing technologies, this application provides an automatic device configuration system. The device to be configured first autonomously selects a target edge gateway from the list of accessible gateways and actively sends a connection request containing its own information to it. After receiving the request, the edge gateway verifies the device. If the verification is successful, it packages the device information and its own gateway information together and sends them to the cloud platform. The cloud platform matches the corresponding configuration parameters based on the received information and generates verification information, which is sent to the user terminal for authorization confirmation. After the user completes the verification, the cloud platform then sends the final configuration parameters to the device, which completes the automatic configuration.

[0065] This system achieves large-scale, cross-regional remote one-click deployment of devices without on-site manual intervention through a collaborative mechanism involving device autonomous gateway discovery, gateway security verification, centralized cloud management, and user authorization confirmation. It effectively solves the problems of low configuration efficiency and high labor costs associated with traditional methods, making it particularly suitable for the rapid deployment of low-power devices in remote areas. Simultaneously, the user authorization process enhances security, preventing unauthorized device binding and laying an automated foundation for subsequent remote operation and maintenance.

[0066] According to one aspect of the embodiments of this application, an automatic device configuration system is provided. This automatic device configuration system can be widely applied to whole-house intelligent digital control application scenarios such as smart homes, smart home ecosystems, and intelligence house ecosystems.

[0067] The technical solutions of this application and how they solve the aforementioned technical problems are described in detail below with specific embodiments. These specific embodiments may exist independently or in combination with each other. Identical or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0068] This embodiment provides an automatic device configuration system. Figure 1 is a structural diagram of the automatic device configuration system provided in this embodiment. As shown in Figure 1, the system 10 includes at least one device to be configured 101, an edge gateway 102, and a cloud platform 103.

[0069] The device to be configured 101 is used to determine the target edge gateway based on the list of accessible edge gateways and send a connection request to the edge gateway 102; the connection request includes the device to be configured information.

[0070] It should be noted that the list of accessible edge gateways refers to the collection of nearby gateways that the device to be configured has detected through wireless scanning, have a signal reachable, and support the relevant protocols. The list may include basic identifiers and preliminary signal parameters for each gateway. A connection request is a network layer communication message initiated by the device to be configured, aiming to establish a preliminary physical / logical connection with the selected gateway. This request includes information about the device to be configured, including but not limited to its unique identifier, model number, hardware version number, and other core metadata used for identification and configuration matching.

[0071] For example, a priority list for gateway selection can be pre-configured within the device to be configured (e.g., prioritizing connections to specific network identifiers). The device to be configured will attempt to establish connections with gateways in the list in this fixed order until successful. If none of the gateways in the list are available, it may enter a low-power sleep state and retry periodically.

[0072] For example, the device to be configured 101 includes multiple communication modules, each supporting a different communication protocol. The device to be configured 101 is specifically used for:

[0073] Activate multiple communication modules in a preset order and obtain a list of accessible edge gateways obtained from the scanning of multiple communication modules;

[0074] For each candidate edge gateway in the list of accessible edge gateways, key parameters of the candidate edge gateway are collected. The key parameters include at least one of signal strength, packet loss rate, and response latency.

[0075] Based on the key parameters of the candidate edge gateways, determine the target edge gateway for access;

[0076] Send a connection request to the edge gateway.

[0077] In this example, the preset order refers to the pre-defined sequence within the device to be configured, which is the order in which its different communication modules (such as NB-IoT, LoRa, and Wi-Fi) are activated. This order can be determined based on service strategies, such as logic based on coverage from wide to narrow, power consumption from low to high, or priority given to the primary network.

[0078] For example, a priority strategy (e.g., NB-IoT > LoRa > Wi-Fi) can be pre-configured in the firmware of the device to be configured, and the communication modules will be activated in this order after power-on. After each module is activated, it performs a scan and adds the detected gateways to a unified candidate pool. Subsequently, the device to be configured initiates a brief probe interaction with each gateway (candidate edge gateway) in the pool to collect its current key performance parameters, such as signal strength, test packet loss rate, and response latency. Finally, the decision algorithm built into the device to be configured (e.g., based on a weighted scoring model) performs a comprehensive analysis of all candidate gateways, selects the one with the highest comprehensive score, identifies it as the target gateway, and sends a connection request.

[0079] This example ensures that the device can intelligently select the access point with the best overall communication quality in a multi-network environment, thereby significantly improving the initial access success rate and laying the foundation for stable data transmission in the future.

[0080] For example, the device to be configured 101 is specifically used for:

[0081] The adaptation score of the candidate edge gateway is determined based on the key parameters and corresponding weights of the candidate edge gateway; among them, signal strength is positively correlated with the adaptation score, while packet loss rate and response latency are negatively correlated with the adaptation score, respectively.

[0082] The candidate edge gateway with the highest adaptation score is selected as the target access edge gateway.

[0083] For example, after collecting the raw parameters of each candidate gateway, normalization processing is first performed to map parameters with different dimensions and ranges to a numerical range of 0-1 (e.g., linearly mapping signal strength to [0, 1], packet loss rate to 1 - packet loss rate, and latency to 1 / latency). Then, the device to be configured performs a weighted sum of the normalized parameters according to preset weights (e.g., signal strength weight 0.6, stability weight 0.3, latency weight 0.1) to calculate the single adaptation score for each gateway. Finally, the device to be configured directly compares the scores of all candidate gateways and selects the one with the highest score as the target access gateway.

[0084] This example not only avoids the high packet loss or high latency issues that may be encountered when selecting based on a single strong signal, but also significantly improves the success rate of initial connections and the reliability of long-term communication.

[0085] For example, the device to be configured 101 is also used for:

[0086] If there are multiple candidate edge gateways with the same adaptation score, then determine the priority of the communication module corresponding to the candidate edge gateway being scanned;

[0087] The candidate edge gateway corresponding to the highest priority communication module is determined as the target access edge gateway; among them, the lower the power consumption of the communication module, the higher its priority.

[0088] In this example, when multiple gateways perform similarly in terms of signal quality, stability, and latency, the device to be configured will actively select the gateway served by the lower power communication protocol. This directly extends the battery life of the battery-powered device and effectively meets the core demand for low power consumption of IoT devices.

[0089] Edge gateway 102 is used to verify the device to be configured based on the connection request. If the verification is successful, it sends configuration information to cloud platform 103. The configuration information includes the device to be configured and edge gateway information.

[0090] For example, the edge gateway locally stores a list of authorized devices or verification rules (such as allowing only specific device models to access). When a connection request is received, the gateway directly queries and compares the device information locally. If the verification is successful, the information is immediately forwarded to the cloud platform; otherwise, it is rejected directly.

[0091] For example, the edge gateway can also perform only preliminary information extraction and format verification, and then forward the device information to be configured to the cloud platform in real time or in batches for centralized verification and decision-making. The cloud platform can make judgments based on dynamic rules such as device model, access geographical location, and time policy, and return the results to the edge gateway.

[0092] The cloud platform 103 is used to determine the corresponding configuration parameters based on the configuration information; generate verification information and send the verification information to the user terminal 104. After the user terminal 104 completes the verification based on the verification information, it sends the configuration parameters to the device to be configured 101.

[0093] It should be noted that configuration parameters refer to a complete set of software setting instructions that enable the device to function properly. This includes not only network parameters but also business parameters, such as the destination address for data reporting, sensor sampling frequency, alarm thresholds, and firmware upgrade channel addresses. Verification information refers to credentials generated by the cloud platform and sent to the user terminal (such as the administrator's mobile application or web backend) for secondary confirmation. This can be a one-time password, a digital token, or a push notification with a confirmation link, etc., the purpose of which is to ensure that the configuration operation is authorized by the device owner or administrator.

[0094] For example, the cloud platform can pre-create various configuration templates based on the device model and deployment scenario (which can be inferred from the location in the gateway information). When configuration information is received, the platform directly calls the corresponding default template as the configuration parameter by matching the device model. The verification information is simply bound to the administrator account preset during the device registration.

[0095] For example, the cloud platform dynamically generates configurations based on richer contextual information. For instance, by combining device information, gateway location, current network conditions, and even data from other systems (such as a ticketing system), a policy engine calculates the optimal configuration parameters. The destination of verification information can also be dynamically routed to the appropriate responsible person for approval based on the organizational structure to which the device belongs.

[0096] The device to be configured 101 is also used to perform network configuration based on configuration parameters.

[0097] It should be noted that network configuration refers to the process by which the device to be configured sets the various parameters required for its network communication based on the configuration parameters received. These parameters include, but are not limited to: access point name and password, IP address allocation method, server address, communication port, reporting cycle, etc.

[0098] The automatic device configuration system provided in this embodiment first allows the device to autonomously select a target edge gateway from the list of accessible gateways and proactively send a connection request containing its own information. Upon receiving the request, the edge gateway verifies the device; if verification is successful, it packages the device information along with its own gateway information and sends it to the cloud platform. The cloud platform matches the corresponding configuration parameters based on the received information and generates verification information, which is sent to the user terminal for authorization confirmation. After the user completes verification, the cloud platform then sends the final configuration parameters to the device, allowing the device to complete the automatic configuration. This system, through a collaborative mechanism of device autonomous gateway discovery, gateway security verification, centralized cloud management, and user authorization confirmation, achieves large-scale, cross-regional remote one-click deployment of devices without on-site manual intervention. It effectively solves the problems of low efficiency and high labor costs associated with traditional configuration methods, and is particularly suitable for the rapid deployment of low-power devices in remote areas. Simultaneously, the user authorization process enhances the security of the configuration process, preventing unauthorized device binding and laying an automated foundation for subsequent remote operation and maintenance.

[0099] This embodiment provides an automatic device configuration system. Figure 2 is a flowchart of the edge gateway processing in the automatic device configuration system provided in this embodiment. As shown in Figure 2, this embodiment, based on the embodiment in Figure 1, provides a detailed description of the edge gateway processing procedure. The edge gateway is specifically used for:

[0100] S201. Receive a connection request sent by the device to be configured. The connection request includes information about the device to be configured.

[0101] S202. Based on the device information to be configured and the preset device list, determine whether the device to be configured meets the verification conditions.

[0102] The verification conditions include: matching the device model from the device list, and / or matching the key field of the device identifier from the device list.

[0103] S203. If yes, the verification is successful. Based on the gateway identifier and key parameters corresponding to the edge gateway accessed by the target, the edge gateway information is obtained.

[0104] S204. Based on the device information to be configured and the edge gateway information, obtain the configuration information and send the configuration information to the cloud platform.

[0105] It's important to note that using a pre-defined static device list for verification ensures that only pre-authorized devices with known models or identification patterns can access the network, preventing unauthorized device intrusion at the source and meeting basic security requirements. The verification criteria incorporate matching of key fields such as device model and / or device identification, providing flexible policy configuration options to adapt to scenarios with different security levels. Upon successful verification, not only is the device's own information reported, but gateway identification and key parameters (such as signal strength) are also proactively added, providing the cloud platform with the complete context needed for decision-making, facilitating subsequent configuration matching, network quality analysis, and device location.

[0106] For example, after parsing a connection request, the edge gateway extracts the device model and device identifier. It then queries a pre-stored list of devices (which could be a hash table or a small database with device model as the key and allowed identifier rules (such as a list of device identifier prefixes) as values). Verification is completed by checking if the device identifier matches the corresponding model's rules. Once verification is successful, the edge gateway packages the device information, its own gateway identifier, and the collected key parameters, and sends them to the cloud platform via an encrypted link.

[0107] S205. If not, determine whether the device to be configured is matched from the dynamic device list.

[0108] S206. If yes, the verification is successful, and the configuration information is sent to the cloud platform.

[0109] S207. If not, determine whether to add the device to be configured to the dynamic device list based on the device location.

[0110] It should be noted that by introducing a dynamic device list (a temporary cache with an expiration date), devices that are not on the preset list but have been recently verified or are located in a trusted area are allowed to quickly access the system, avoiding the mistaken rejection of legitimate devices due to delayed list updates. In particular, when the device to be configured is not on any list, a location-based judgment logic is introduced, enabling new devices that are physically within a controlled environment to be automatically and temporarily authorized, significantly reducing manual intervention.

[0111] For example, an edge gateway can query a local list of dynamic devices. If the record for the device to be configured is found, it is considered verified and reported. If not found, the edge gateway may request the device to provide or calculate its location information itself and compare it with a predefined range. If the location is reliable, the edge gateway can add the device information to the dynamic list (with a short validity period, such as 2 hours) and verify it; otherwise, it will refuse access and log the information.

[0112] For example, the edge gateway is specifically used for:

[0113] Determine whether the device location is within a trusted geofence;

[0114] If the device is within a trusted geofence, a continuous request indication message is sent to the device to be configured, so that the device to be configured will continuously send a preset number of supplementary connection requests.

[0115] Based on the number of supplementary connection requests returned by the device to be configured, determine whether the device locations indicated by the number of supplementary connection requests are the same.

[0116] If they are the same, a dynamic device list addition request, along with configuration information, is sent to the cloud platform; the dynamic device list addition request is used to instruct the request to add the device to be configured to the dynamic device list.

[0117] In this example, a trusted geofence sets a predefined virtual geographic boundary, which can define specific physical areas such as industrial parks and buildings based on latitude and longitude coordinates. The preset number of times requires the device to continuously send location requests a fixed number of times (e.g., 3 times) to double-check the stability and authenticity of the device's location.

[0118] This example effectively identifies and filters out unauthorized or temporary devices that forge location information using a single instance or only briefly pass through a trusted area, ensuring that only devices that are continuously and stably present in a trusted physical space can obtain temporary access permissions. This approach reduces the risk of misauthorization due to accidental device movement (such as being carried along), improving deployment flexibility while maintaining effective security.

[0119] For example, the device information to be configured also includes inherent device attributes, device signal quality, and the current time; the cloud platform is also used for:

[0120] Receive a request to add a dynamic device to the list, and determine the trust score corresponding to the device to be configured based on the device information. Among them, the inherent attributes of the device are determined based on a preset mapping relationship to determine the corresponding trust score contribution. The device signal quality is positively correlated with the trust score. If the current location and the current time period are in a preset active period, the contribution to the trust score will be greater.

[0121] The validity period of the device to be configured is determined based on the trust score; the trust score and the validity period are positively correlated.

[0122] Update the devices to be configured and their corresponding validity periods to the dynamic device list to obtain the updated dynamic device list;

[0123] The updated list of dynamic devices is sent to each edge gateway.

[0124] In this example, by introducing inherent device attributes to confirm basic trustworthiness, signal quality to reflect the current link status, current location to confirm spatial compliance, and current time to match behavioral patterns, the access risk of the device to be configured can be quantified more accurately. Based on differentiated validity periods for trust scores, dynamic scaling of security policies is achieved: long-term authorization is granted to high-trust devices to reduce control overhead, while short-term authorization is implemented for low-trust devices for continuous monitoring.

[0125] For example, the cloud platform can query a preset baseline score mapping table based on the device's inherent attributes (such as model and security level); convert signal quality into a quality score using a linear or piecewise function (the stronger the signal, the higher the score); determine if the current location is within a trusted fence, and if so, add a geographical trust score; finally, check if the current time is within the device's historical active period or a preset legal period (such as office hours), and if so, add a time period compliance score. The cloud platform weights and sums the above items to generate a total trust score from 0 to 100. Subsequently, according to a preset mapping strategy (e.g., 30 days for scores above 90, 7 days for scores between 60 and 89, and 1 day for scores below 60), the dynamic validity period is determined, and this entry (device identifier, trust score, validity period to timestamp) is updated to the global dynamic list in the central database. Finally, the incremental update is synchronized to all relevant edge gateways through a message push mechanism.

[0126] The automatic device configuration system provided in this embodiment reduces access latency and dependence on cloud networks, and enhances the autonomy and robustness of the edge side. At the same time, it enhances the system's ability to accept new or temporary devices, reduces operation and maintenance complexity and manpower costs, and ensures the security of dynamic authorization through geographical location constraints, thus achieving an effective balance between security and convenience.

[0127] This embodiment provides a device automatic configuration method. Figure 3 is a flowchart of the device automatic configuration method provided in this embodiment. As shown in Figure 3, the method is applied to a device automatic configuration system, which includes at least one device to be configured, an edge gateway, and a cloud platform. The method includes:

[0128] S301. The device to be configured determines the target edge gateway based on the list of accessible edge gateways and sends a connection request to the edge gateway; the connection request includes information about the device to be configured.

[0129] In this step, the device to be configured acts as an access device. After powering on, its built-in multi-protocol communication module chip (supporting NB-IoT, LoRa, and Wi-Fi protocols) can be initialized. The device scans its surrounding environment according to a preset strategy, generating a list of all detectable gateways. Based on parameters such as signal strength and packet loss rate, it intelligently selects the optimal target edge gateway. Subsequently, the device actively initiates a connection request to this gateway. This request includes its unique identifier, model number, and other information about the device to be configured, providing a basis for identity verification and configuration.

[0130] S302. The edge gateway verifies the device to be configured based on the connection request. If the verification is successful, it sends configuration information to the cloud platform. The configuration information includes the device to be configured and the edge gateway information.

[0131] In this step, the edge gateway acts as the core processing node on the edge side. Upon receiving a connection request, the edge gateway parses the request using its integrated multi-protocol conversion module. Next, it runs a gateway verification algorithm to perform a rapid security check on the device to be configured based on a local device list or dynamic rules. If the verification passes, the edge gateway not only verifies the device's compliance but also packages the device information to be configured along with its own edge gateway information (such as gateway identifier and device signal quality) to form configuration information, which is then reported to the cloud platform via an encrypted link.

[0132] S303: The cloud platform determines the corresponding configuration parameters based on the configuration information; generates verification information and sends the verification information to the user terminal; after the user terminal completes the verification based on the verification information, the configuration parameters are sent to the device to be configured.

[0133] In this step, the cloud management platform acts as the central control hub. Upon receiving the configuration information, the cloud platform leverages the computing power of its server cluster to quickly match the device model and scenario, determining the corresponding configuration parameters from a pre-defined configuration template library. Simultaneously, the cloud platform generates one-time verification information (such as a verification code) and pushes it to the user's terminal application through a secure channel protected by its security nodes. Only after the user completes verification and authorization on their smartphone or terminal does the cloud platform officially distribute the encrypted configuration parameters.

[0134] S304. The device to be configured performs network configuration based on the configuration parameters.

[0135] In this step, we return to the device to be configured. The device receives configuration parameters from the cloud platform, forwarded via the edge gateway, through its multi-protocol communication module. The local configuration program on the device decrypts and parses the parameters, then automatically configures network and service parameters, such as setting the server address and data reporting cycle. After configuration, the device can also send a success message to the platform.

[0136] The automatic device configuration method provided in this embodiment achieves large-scale, cross-regional remote one-click deployment of devices without on-site manual intervention through a collaborative mechanism involving the device to be configured autonomously discovering the gateway, gateway security verification, centralized cloud management, and user authorization confirmation. This effectively solves the problems of low efficiency and high labor costs associated with traditional configuration methods, making it particularly suitable for the rapid deployment of low-power devices in remote areas. Simultaneously, the user authorization process enhances security, preventing unauthorized device binding and laying an automated foundation for subsequent remote operation and maintenance.

[0137] Figure 4 is a hardware schematic diagram of an electronic device provided in an embodiment of the present invention. As shown in Figure 4, the electronic device 40 provided in this embodiment includes at least one processor 401 and a memory 402. The device 40 also includes a communication component 403. The processor 401, the memory 402, and the communication component 403 are connected via a bus 404.

[0138] In the specific implementation process, at least one processor 401 executes computer execution instructions stored in memory 402, causing at least one processor 401 to perform the above method.

[0139] The specific implementation process of processor 401 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0140] In the embodiment shown in Figure 4 above, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0141] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0142] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0143] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the method described above.

[0144] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0145] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0146] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0147] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0148] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0149] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0150] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0151] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. An automatic equipment configuration system, characterized in that, The system includes: at least one device to be configured, an edge gateway, and a cloud platform. The device to be configured is used to determine a target edge gateway based on a list of accessible edge gateways and send a connection request to the edge gateway; the connection request includes information about the device to be configured. The edge gateway is used to verify the device to be configured based on the connection request. If the verification is successful, it sends configuration information to the cloud platform; the configuration information includes the information about the device to be configured and the edge gateway information. The cloud platform is used to determine corresponding configuration parameters based on the configuration information; generate verification information and send the verification information to a user terminal. After the user terminal completes verification based on the verification information, it sends the configuration parameters to the device to be configured. The device to be configured is also used to perform network configuration based on the configuration parameters.

2. The system according to claim 1, characterized in that, The device to be configured includes multiple communication modules, each supporting a different communication protocol. Specifically, the device to be configured is used to: activate the multiple communication modules in a preset order and obtain a list of accessible edge gateways scanned by the multiple communication modules; for each candidate edge gateway in the list of accessible edge gateways, collect key parameters of the candidate edge gateway, including at least one of signal strength, packet loss rate, and response latency; determine the target edge gateway based on the key parameters of the candidate edge gateway; and send a connection request to the edge gateway.

3. The system according to claim 2, characterized in that, The device to be configured is specifically used to: determine the adaptation score of the candidate edge gateway based on the key parameters and corresponding weights of the candidate edge gateway; wherein the signal strength is positively correlated with the adaptation score, and the packet loss rate and response latency are negatively correlated with the adaptation score; and determine the candidate edge gateway with the highest adaptation score as the target access edge gateway.

4. The system according to claim 3, characterized in that, The device to be configured is further configured to: if there are multiple candidate edge gateways with the same adaptation score, determine the priority of the communication module corresponding to the candidate edge gateway being scanned; and determine the candidate edge gateway corresponding to the communication module with the highest priority as the target access edge gateway; wherein, the lower the power consumption of the communication module, the higher its corresponding priority.

5. The system according to claim 1, characterized in that, The device information to be configured includes a device model and a device identifier. The edge gateway is specifically used to: determine whether the device to be configured meets the verification conditions based on the device information to be configured and a preset device list; wherein, the verification conditions include: matching the device model from the device list, and / or matching the key field of the device identifier from the device list; if satisfied, the verification is successful; obtain the edge gateway information based on the gateway identifier and key parameters corresponding to the target access edge gateway; obtain the configuration information based on the device information to be configured and the edge gateway information, and send the configuration information to the cloud platform.

6. The system according to claim 5, characterized in that, The device information to be configured includes the device location. The edge gateway is further configured to: if the device to be configured does not meet the verification conditions, determine whether the device to be configured is matched from the dynamic device list; if yes, the verification is passed and configuration information is sent to the cloud platform; if no, determine whether to add the device to be configured to the dynamic device list based on the device location.

7. The system according to claim 6, characterized in that, The edge gateway is specifically used to: determine whether the device location is within a trusted geofence; if it is within a trusted geofence, send continuous request indication information to the device to be configured, so that the device to be configured continuously sends a preset number of supplementary connection requests; based on the preset number of supplementary connection requests returned by the device to be configured, determine whether the device locations indicated by the preset number of supplementary connection requests are the same; if they are the same, send a dynamic device list addition request and the configuration information to the cloud platform; The dynamic device list addition request is used to instruct the request to add the device to be configured to the dynamic device list.

8. The system according to claim 7, characterized in that, The device information to be configured also includes the device's inherent attributes, device signal quality, and current time. The cloud platform is further configured to: receive the dynamic device list addition request; determine the trust score corresponding to the device to be configured based on the device information; wherein, the device's inherent attributes are determined based on a preset mapping relationship to determine the corresponding trust score contribution; the device signal quality is positively correlated with the trust score; and the current location and current time are more likely to contribute to the trust score if the time period is within a preset active time period; determine the validity period corresponding to the device to be configured based on the trust score; the trust score and the validity period are positively correlated; update the device to be configured and its corresponding validity period in the dynamic device list to obtain an updated dynamic device list; and send the updated dynamic device list to each edge gateway.

9. An automatic equipment configuration method, characterized in that, An automatic device configuration system is applied, the system including at least one device to be configured, an edge gateway, and a cloud platform; the method includes: the device to be configured determining a target edge gateway based on a list of accessible edge gateways and sending a connection request to the edge gateway; the connection request includes information about the device to be configured; the edge gateway verifying the device to be configured based on the connection request, and if the verification is successful, sending configuration information to the cloud platform; the configuration information including information about the device to be configured and information about the edge gateway; the cloud platform determining corresponding configuration parameters based on the configuration information; generating verification information and sending the verification information to a user terminal; after the user terminal completes verification based on the verification information, sending the configuration parameters to the device to be configured; and the device to be configured performing network configuration based on the configuration parameters.

10. An electronic device, characterized in that, include: At least one processor and a memory; wherein the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, causing the at least one processor to perform the device automatic configuration method as described in claim 9.

Images