Equipment self-adaptive model processing method and system, storage medium and electronic equipment

Abstract

The invention discloses an equipment-adaptive model processing method and system, a storage medium and electronic equipment, relates to the technical field of model processing, and provides an automatic and intelligent bit number distribution mechanism and a template mechanism. The bit number distribution mechanism aims at simplifying the complex bit number configuration process. According to the mechanism, through an intelligent algorithm, the system can automatically identify and distribute suitable bit numbers, human intervention is reduced, the configuration process is smoother and more efficient, and the configuration efficiency is remarkably improved. A template mechanism allows a user to quickly realize automatic generation through a template when equipment with the same bit number strategy needs to be generated in batches, and configuration operation does not need to be repeatedly performed. Therefore, time and human resources are saved, and consistency and standardization of configuration are guaranteed. The application of the template mechanism enables the configuration process to be more efficient, and improves the bit number configuration efficiency of PN devices when a large number of PN devices are accessed.

Description

Technical Field

[0001] This application relates to the field of model processing technology, and more specifically, to a device-adaptive model processing method, system, storage medium, and electronic device. Background Technology

[0002] When traditional control system configuration software connects to devices based on the fieldbus standard (PROFINET, PN) protocol, the input / output (IO) data on such devices is complete data for the entire slave device. Therefore, the device needs to be configured with tag numbers in order to obtain specific IO data blocks.

[0003] The above process involves dividing the IO data area of ​​a PN protocol device (i.e., a PN device) into multiple tag numbers according to actual needs, or performing secondary development through function blocks to obtain the specified IO data block of the PN device. Especially when connecting a large number of PN devices, if the tag number allocation strategy of these devices is uniform, the operation needs to be repeated, making the tag number configuration process for PN devices not only cumbersome but also inconvenient. This further increases the complexity and workload of the system, thereby reducing the efficiency of tag number configuration for PN devices.

[0004] Therefore, how to improve the efficiency of tag configuration for PN devices when connecting a large number of PN devices is a problem that this application urgently needs to solve. Summary of the Invention

[0005] In view of this, this application discloses a device adaptive model processing method, system, storage medium and electronic device, which aims to improve the efficiency of tag configuration of PN devices when a large number of PN devices are connected.

[0006] To achieve the above objectives, the disclosed technical solution is as follows:

[0007] The first aspect of this application discloses a device-adaptive model processing method, the method comprising:

[0008] Obtain the device information corresponding to the device to be added; wherein, the device information includes at least the IO data of the device to be added, the IO data of all sub-devices in the device to be added, and the tag number strategy information corresponding to all sub-devices;

[0009] Create a corresponding device template based on the device information;

[0010] Based on the tag number allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag number strategy information corresponding to all sub-devices, tag number configuration information is generated; wherein, the tag number strategy information is determined at least by the data type of the tag number, the length of the tag number, and the status code of the tag number;

[0011] When a batch of device requests identical to the tag number configuration information is received, and the device template meets the instantiation conditions, the batch template of the batch of device requests is instantiated through the template mechanism and the tag number configuration information.

[0012] Preferably, obtaining the device information corresponding to the device to be added includes:

[0013] Load device configuration file information for all different protocol types supported by the current system using the configuration software;

[0014] Determine the protocol type of the device to be added;

[0015] Call the corresponding parsing device service based on the protocol type of the device to be added;

[0016] The device information corresponding to the device to be added is parsed from the device configuration file information of all different protocol types supported by the current system according to the parsing device service.

[0017] Preferably, the step of creating a corresponding device template based on the device information includes:

[0018] The device information is parsed to obtain the device type of the device to be added;

[0019] Create a corresponding device template based on the device type of the device to be added.

[0020] Preferably, the step of generating tag configuration information based on the tag allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag strategy information corresponding to all sub-devices includes:

[0021] Using configuration software, intelligent algorithms, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag number strategy information corresponding to all sub-devices, the tag number configuration information of each sub-device under the device to be added is generated.

[0022] Preferably, when a batch of device requests identical to the tag number configuration information is received, and the device template meets the instantiation conditions, the batch template instantiation of the batch of device requests is performed through the template mechanism and the tag number configuration information, including:

[0023] When a batch device request with the same tag number configuration information is received, the template device type information and template IO data in the device template are obtained through the configuration software.

[0024] If the device type information corresponding to the device model to be added is compatible with the device type information of the template, and the IO data corresponding to the device model to be added is less than or equal to the IO data of the template, then the device template is determined to meet the instantiation conditions.

[0025] Under the condition that the device template meets the instantiation requirements, the batch template instantiation of the batch device request is performed on the slot of the device to be added according to the obtained number of instantiations, the tag number configuration information, and the device template that meets the instantiation requirements.

[0026] Preferred options also include:

[0027] If the device type information corresponding to the device model to be added is incompatible with the template device type information, or if the IO data corresponding to the device model to be added is greater than the template IO data, it is determined that the device template does not meet the instantiation conditions, and template instantiation operation is prohibited.

[0028] Preferred options also include:

[0029] When a request to add or delete sub-devices is received, the tag number strategy information is modified to generate tag number configuration information.

[0030] A second aspect of this application discloses a device-adaptive model processing system, the system comprising:

[0031] The acquisition unit is used to acquire the device information corresponding to the device to be added; wherein, the device information includes at least the IO data of the device to be added, the IO data of all sub-devices in the device to be added, and the tag number strategy information corresponding to all sub-devices;

[0032] A creation unit is used to create a corresponding device template based on the device information;

[0033] The generation unit is used to generate tag configuration information based on the tag allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag strategy information corresponding to all sub-devices; wherein, the tag strategy information is determined at least by the data type of the tag, the length of the tag, and the status code of the tag;

[0034] The instantiation unit is used to instantiate the batch template of the batch device request through the template mechanism and the tag configuration information when a batch device request with the same tag configuration information is received and the device template meets the instantiation conditions.

[0035] A third aspect of this application discloses a storage medium comprising stored instructions, wherein, when the instructions are executed, the device in which the storage medium resides is controlled to perform a device adaptive model processing method as described in any one of the first aspects.

[0036] The fourth aspect of this application discloses an electronic device, including a memory and one or more instructions, wherein one or more instructions are stored in the memory and configured to be executed by one or more processors using the device adaptive model processing method as described in any of the first aspects.

[0037] As can be seen from the above technical solution, this application discloses a device adaptive model processing method, system, storage medium, and electronic device, which obtains device information corresponding to the device to be added; wherein, the device information includes at least the IO data of the device to be added, the IO data of all sub-devices in the device to be added, and the tag number policy information corresponding to all sub-devices; a corresponding device template is created based on the device information; and tag number configuration information is generated based on the tag number allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag number policy information corresponding to all sub-devices; wherein, the tag number policy information is determined at least by the data type of the tag number, the length of the tag number, and the status code of the tag number; when a batch device request with the same tag number configuration information is received, and the device template meets the instantiation conditions, the batch template instantiation of the batch device request is performed through the template mechanism and the tag number configuration information.

[0038] This solution provides automated and intelligent tag assignment and template mechanisms. The tag assignment mechanism aims to simplify the complex tag configuration process. Through intelligent algorithms, the system can automatically identify and assign suitable tag numbers, reducing human intervention and making the configuration process smoother and more efficient, significantly improving configuration efficiency. The template mechanism allows users to quickly and automatically generate devices with the same tag strategy in batches, without repeating configuration operations. This saves time and manpower, and ensures configuration consistency and standardization. The application of the template mechanism makes the configuration process more efficient, improving the efficiency of tag configuration for PN devices when connecting a large number of PN devices. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0040] Figure 1 This is a schematic flowchart of a device adaptive model processing method disclosed in an embodiment of this application;

[0041] Figure 2This is a schematic diagram of the structure of a device adaptive model processing system disclosed in an embodiment of this application;

[0042] Figure 3 This is a schematic diagram of the structure of the electronic device disclosed in the embodiments of this application. Detailed Implementation

[0043] The technical solutions of the embodiments 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, and 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.

[0044] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0045] As the background technology shows, when connecting a large number of PN devices, if the device tag number allocation strategy is uniform, the operation needs to be repeated, making the tag number configuration process for PN devices not only cumbersome but also inconvenient. This further increases the complexity and workload of the system, thereby reducing the efficiency of PN device tag number configuration.

[0046] To address the aforementioned issues, this application discloses a device adaptive model processing method, system, storage medium, and electronic device. This solution provides an automated and intelligent tag allocation mechanism and a template mechanism. The tag allocation mechanism aims to simplify the complex tag configuration process. Through intelligent algorithms, this mechanism enables the system to automatically identify and allocate suitable tag numbers, reducing human intervention and making the configuration process smoother and more efficient, significantly improving configuration efficiency. The template mechanism allows users to quickly and automatically generate devices with the same tag strategy in batches using templates, without repeating configuration operations. This saves time and manpower, and ensures configuration consistency and standardization. The application of the template mechanism makes the configuration process more efficient, improving the efficiency of tag configuration for PN devices when connecting a large number of PN devices. Specific implementation methods are described in detail in the following embodiments.

[0047] It should be noted that the device adaptive model processing method, system, storage medium and electronic device provided in this application can be used in the technical field of model processing, etc. The above is only an example and does not limit the application field of the device adaptive model processing method, system, storage medium and electronic device provided in this application.

[0048] refer to Figure 1 As shown in the figure, this application discloses a device adaptive model processing method, which mainly includes the following steps:

[0049] S101: Obtain the device information corresponding to the device to be added; wherein, the device information includes at least the IO data of the device to be added, the IO data of all sub-devices in the device to be added, and the tag number strategy information corresponding to all sub-devices.

[0050] In S101, a device configuration file parsing service is provided through a device parsing module, which is used to load and parse the configuration file description information of devices with different protocols. A plug-in framework is used to manage devices, supporting the loading and parsing of configuration files of different protocols and formats.

[0051] The tag strategy information includes the tag data type, tag length, tag status code, and other information.

[0052] It should be noted that tag numbers in a control system can be used to identify data corresponding to devices such as sensors, valves, and motors in the system, and can also represent different signal types and transmission paths. Tag numbers can also be virtual, that is, a memory data unit in the program logic.

[0053] The specific process of obtaining the device information corresponding to the device to be added is shown in A1-A4.

[0054] A1: Load device configuration file information for all different protocol types supported by the current system through configuration software.

[0055] The configuration software provides a framework for parsing devices and is used to support the parsing of configuration file information for different protocol devices.

[0056] This solution supports multiple communication protocols and is easily scalable. Protocol types include, but are not limited to, PROFINET and MODBUS protocols. Through this multi-protocol support, the configuration software can adapt to the communication needs of different devices, automatically parse device configuration files, and display device information in an intuitive graphical format. This multi-protocol compatibility ensures the system's broad applicability, enabling flexible application in various industrial environments and meeting diverse device configuration requirements.

[0057] A2: Determine the protocol type of the device to be added.

[0058] A3: Call the corresponding parsing device service based on the protocol type of the device to be added.

[0059] The configuration software will automatically call the corresponding parsing device service based on the protocol type of the device to be added.

[0060] A4: Based on the device parsing service, the device information corresponding to the device to be added is parsed from the device configuration file information of all different protocol types supported by the current system.

[0061] When the configuration software loads and obtains the configuration file information of all devices supported by the current system, it starts the device parsing module service and obtains the device information according to different parsing methods corresponding to different protocols.

[0062] For example, when the configuration software receives a configuration file (GSDML file) for a PROFINET-based device imported by the user, it will call the GSDML file parsing service according to the protocol type, obtain the device information, the device information of each slot / subslot, and the IO data information of each slot, and cache the corresponding device information.

[0063] S102: Create the corresponding device template based on the device information.

[0064] In S102, the template generation module uses the parsed device information and the device type of the device to be added selected by the user. The configuration software automatically creates the corresponding device template based on the matching template type and displays the device information and tag configuration information in a graphical way for easy viewing and management by the user.

[0065] S103: Generate tag configuration information based on the tag allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag strategy information corresponding to all sub-devices; wherein, the tag strategy information is determined at least by the data type of the tag, the length of the tag, and the status code of the tag.

[0066] In S103, the tag configuration information of each sub-device under the device to be added is generated by the configuration software, intelligent algorithm, IO data of the device to be added, IO data of all sub-devices under the device to be added, and tag strategy information of all sub-devices.

[0067] The bit position strategy information includes, but is not limited to, the data type of the bit position, the length of the bit position, and the status code of the bit position.

[0068] This solution provides an automated and intelligent tag assignment mechanism designed to simplify the complex tag configuration process. By reducing human intervention, the tag assignment mechanism makes the configuration process smoother and more efficient. Through intelligent algorithms, the system can automatically identify and assign appropriate tag numbers, significantly improving configuration efficiency. Furthermore, this automated processing method effectively reduces the risk of errors caused by human factors, ensuring the accuracy and reliability of the configuration.

[0069] The automated tag assignment mechanism not only simplifies the configuration process but also ensures the consistency and accuracy of the configuration, significantly improving the overall efficiency and reliability of the system and providing a guarantee for the stable operation of the control system. It is suitable for various complex industrial control environments.

[0070] The configuration software automatically generates tag configuration information based on the IO data size of the device to be added and all its sub-devices, as well as the tag strategy (including the data type, length, status code, etc. of the tag) of the sub-devices.

[0071] Device information and tag configuration information can be displayed in ways including but not limited to graphical representations, facilitating user viewing and management. Furthermore, when a request to add or delete sub-devices is received, users can add or delete sub-devices as needed and modify the tag policy information to regenerate the tag configuration information.

[0072] For example, during the template adaptive generation phase, when the user selects a specific device model, the configuration software creates a device template based on the parsed device model information. It also automatically generates the tag configuration based on the IO data size and tag strategy information of the PN device and all its sub-devices, and displays the device information and tag configuration information in a graphical way for easy viewing and management by the user.

[0073] S104: When a batch device request with the same tag number configuration information is received, and the device template meets the instantiation conditions, the batch template of the batch device request is instantiated through the template mechanism and the tag number configuration information.

[0074] In S104, modular instantiation is achieved by instantiating modules, allowing users to select the type of device to be instantiated, and using a template mechanism to match and generate configurations from adaptive models.

[0075] During the template instantiation phase, when a user requests to add devices with the same tag number strategy in batches (i.e., a batch of devices with the same tag number configuration information), the corresponding template can be selected. The configuration software generates the configuration through template matching adaptive model based on the corresponding template and the number of devices to be instantiated selected by the user, thus achieving modular instantiation. This provides a more efficient solution for large-scale device access.

[0076] The template mechanism, or template-based approach, allows all devices using the same tag number allocation strategy to automatically generate their configurations directly from the template once the tag number is assigned. This eliminates the need for repeated configurations, providing a more efficient solution for large-scale device access.

[0077] The template mechanism automates configuration and template instantiation. This method supports adaptive adjustments based on specific needs, making the configuration process more flexible and adaptable. The template mechanism allows users to quickly and automatically generate devices with the same tag number strategy in batches, eliminating the need for repetitive configuration operations. This not only saves time and manpower but also ensures configuration consistency and standardization. The application of the template mechanism makes the configuration process more efficient, especially in large-scale industrial applications, providing a more efficient solution for large-scale device access, significantly improving production efficiency, and offering users a more convenient and efficient operating experience.

[0078] The specific process of instantiating batch templates for batch device requests using template mechanisms and tag configuration information is shown in B1-B3.

[0079] B1: When a batch device request with the same tag number configuration information is received, the template device type information and template IO data in the device template are obtained through the configuration software.

[0080] B2: If the device type information corresponding to the device model to be added is compatible with the template device type information, and the IO data corresponding to the device model to be added is less than or equal to the template IO data, then the device template is determined to meet the instantiation conditions.

[0081] If the device type information corresponding to the device model to be added is incompatible with the template device type information, or if the IO data corresponding to the device model to be added is greater than the template IO data, it is determined that the device template does not meet the instantiation conditions, and template instantiation operation is prohibited.

[0082] B3: If the device template meets the instantiation conditions, perform batch template instantiation of batch device requests on the slot of the device to be added based on the obtained number of instantiations, tag number configuration information and device templates that meet the instantiation conditions.

[0083] In B3, users select a template for instantiation in the slot of the device to be added. Specifically, the configuration software checks information such as the device type of the template, the type of the device to be added, and the size limits of input / output data. If the template device type and the device type of the device to be added are incompatible or exceed the input / output data size limits (i.e., the IO data corresponding to the device model to be added is greater than the template IO data), template instantiation is not allowed. The configuration software generates configurations through template matching and adaptive model generation based on the template information and the number of instantiations selected by the user, achieving modular instantiation. Specifically, it adaptively batches the devices to be added according to the template's tag number allocation strategy. During the instantiation process, the configuration software automatically manages the instantiated devices, such as automatically assigning them unique device IDs and initializing the device tag number information.

[0084] This solution provides an adaptive model generation method that automates configuration and template instantiation through template matching. This method supports adaptive adjustments based on specific needs, making the configuration process more flexible and adaptable. The adaptive model generation method not only simplifies the tag configuration process but also improves system scalability and maintainability, making it suitable for applications in constantly changing industrial environments. Based on the template-based adaptive model generation method, this solution provides a more efficient solution for large-scale device access, offering users a more convenient and efficient operating experience.

[0085] This solution proposes a template-based device adaptive model generation method for control systems that can access devices with different protocols. Through an automated and intelligent tag allocation mechanism, the process of automatically generating tag numbers for the template is achieved. At the same time, the template instantiation method provides a more efficient solution for large-scale device access and offers users a more convenient and efficient operating experience.

[0086] This solution provides automated and intelligent tag assignment and template mechanisms. The tag assignment mechanism aims to simplify the complex tag configuration process. Through intelligent algorithms, the system can automatically identify and assign suitable tag numbers, reducing human intervention and making the configuration process smoother and more efficient, significantly improving configuration efficiency. The template mechanism allows users to quickly and automatically generate devices with the same tag strategy in batches, without repeating configuration operations. This saves time and manpower, and ensures configuration consistency and standardization. The application of the template mechanism makes the configuration process more efficient, improving the efficiency of tag configuration for PN devices when connecting a large number of PN devices.

[0087] Based on the above embodiments Figure 1 The disclosed device-adaptive model processing method, in addition to the device-adaptive model processing system, is also provided in this application. Figure 2 As shown, the adaptive model processing system of this device includes:

[0088] The acquisition unit 201 is used to acquire the device information corresponding to the device to be added; wherein, the device information includes at least the IO data of the device to be added, the IO data of all sub-devices in the device to be added, and the tag number strategy information corresponding to all sub-devices;

[0089] Create unit 202, which is used to create a corresponding device template based on the device information;

[0090] The generation unit 203 is used to generate tag configuration information based on the tag allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag strategy information corresponding to all sub-devices; wherein, the tag strategy information is determined at least by the data type of the tag, the length of the tag, and the status code of the tag;

[0091] The instantiation unit 204 is used to instantiate the batch template of the batch device request through the template mechanism and the tag number configuration information when it receives a batch device request that is the same as the tag number configuration information and the device template meets the instantiation conditions.

[0092] Furthermore, the acquisition unit 201 includes:

[0093] The loading module is used to load device configuration file information for all different protocol types supported by the current system through the configuration software.

[0094] The first determining module is used to determine the protocol type of the device to be added;

[0095] The calling module is used to invoke the corresponding parsing device service based on the protocol type of the device to be added.

[0096] The first parsing module is used to parse the device information corresponding to the device to be added from the device configuration file information of all different protocol types supported by the current system based on the parsing device service.

[0097] Furthermore, unit 202 is created, including:

[0098] The second parsing module is used to parse device information and obtain the device type of the device to be added.

[0099] A creation module is used to create a corresponding device template based on the device type of the device to be added.

[0100] Furthermore, the generation unit 203 is specifically used to generate the tag configuration information of each sub-device under the device to be added by using configuration software, intelligent algorithms, IO data of the device to be added, IO data of all sub-devices under the device to be added, and tag strategy information corresponding to all sub-devices.

[0101] Furthermore, instantiation unit 204 includes:

[0102] The acquisition module is used to acquire template device type information and template IO data from the device template through the configuration software when a batch device request with the same tag number configuration information is received.

[0103] The first determining module is used to determine that the device template meets the instantiation conditions if the device type information corresponding to the device model to be added is compatible with the template device type information, and the IO data corresponding to the device model to be added is less than or equal to the template IO data.

[0104] The instantiation module is used to perform batch template instantiation of batch device requests in the slots of the devices to be added, based on the obtained number of instantiations, tag number configuration information, and device templates that meet the instantiation conditions, provided that the device templates meet the instantiation conditions.

[0105] Furthermore, the device-adaptive model processing system also includes:

[0106] The determination unit is used to determine that the device template does not meet the instantiation conditions and prohibits template instantiation operations if the device type information corresponding to the device model to be added is incompatible with the template device type information, or if the IO data corresponding to the device model to be added is greater than the template IO data.

[0107] Furthermore, the device-adaptive model processing system also includes:

[0108] The generation unit is modified to generate tag configuration information by modifying the tag number strategy information when a request to add or delete sub-devices is received.

[0109] This solution provides automated and intelligent tag assignment and template mechanisms. The tag assignment mechanism aims to simplify the complex tag configuration process. Through intelligent algorithms, the system can automatically identify and assign suitable tag numbers, reducing human intervention and making the configuration process smoother and more efficient, significantly improving configuration efficiency. The template mechanism allows users to quickly and automatically generate devices with the same tag strategy in batches, without repeating configuration operations. This saves time and manpower, and ensures configuration consistency and standardization. The application of the template mechanism makes the configuration process more efficient, improving the efficiency of tag configuration for PN devices when connecting a large number of PN devices.

[0110] This application embodiment also provides a storage medium, the storage medium including stored instructions, wherein, when the instructions are executed, the device where the storage medium is located is controlled to execute the device adaptive model processing method as described above.

[0111] This application also provides an electronic device, the structural schematic diagram of which is shown below. Figure 3 As shown, it specifically includes a memory 301 and one or more instructions 302, wherein one or more instructions 302 are stored in the memory 301 and are configured to be executed by one or more processors 303 to perform the above-mentioned device adaptive model processing method.

[0112] For the foregoing method embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0113] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For apparatus embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0114] The steps in the methods of the various embodiments of this application can be adjusted, combined, or deleted according to actual needs.

[0115] Finally, it should be noted that in this paper, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0116] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0117] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A device adaptive model processing method, characterized in that, The method includes: Obtain the device information corresponding to the device to be added; wherein, the device information includes at least the IO data of the device to be added, the IO data of all sub-devices in the device to be added, and the tag number strategy information corresponding to all sub-devices; Create a corresponding device template based on the device information; Based on the tag number allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag number strategy information corresponding to all sub-devices, tag number configuration information is generated; wherein, the tag number strategy information is determined at least by the data type of the tag number, the length of the tag number, and the status code of the tag number; When a batch of device requests identical to the tag number configuration information is received, and the device template meets the instantiation conditions, the batch template of the batch of device requests is instantiated through the template mechanism and the tag number configuration information.

2. The method according to claim 1, characterized in that, The step of obtaining the device information corresponding to the device to be added includes: Load device configuration file information for all different protocol types supported by the current system using the configuration software; Determine the protocol type of the device to be added; Call the corresponding parsing device service based on the protocol type of the device to be added; The device information corresponding to the device to be added is parsed from the device configuration file information of all different protocol types supported by the current system according to the parsing device service.

3. The method according to claim 1, characterized in that, The step of creating a corresponding device template based on the device information includes: The device information is parsed to obtain the device type of the device to be added; Create a corresponding device template based on the device type of the device to be added.

4. The method according to claim 1, characterized in that, The step of generating tag configuration information based on the tag allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag strategy information corresponding to all sub-devices includes: Using configuration software, intelligent algorithms, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag number strategy information corresponding to all sub-devices, the tag number configuration information of each sub-device under the device to be added is generated.

5. The method according to claim 1, characterized in that, When a batch of device requests identical to the tag number configuration information is received, and the device template meets the instantiation conditions, the batch template instantiation of the batch of device requests is performed through the template mechanism and the tag number configuration information, including: When a batch device request with the same tag number configuration information is received, the template device type information and template IO data in the device template are obtained through the configuration software. If the device type information corresponding to the device model to be added is compatible with the device type information of the template, and the IO data corresponding to the device model to be added is less than or equal to the IO data of the template, then the device template is determined to meet the instantiation conditions. Under the condition that the device template meets the instantiation requirements, the batch template instantiation of the batch device request is performed on the slot of the device to be added according to the obtained number of instantiations, the tag number configuration information, and the device template that meets the instantiation requirements.

6. The method according to claim 5, characterized in that, Also includes: If the device type information corresponding to the device model to be added is incompatible with the template device type information, or if the IO data corresponding to the device model to be added is greater than the template IO data, it is determined that the device template does not meet the instantiation conditions, and template instantiation operation is prohibited.

7. The method according to claim 1, characterized in that, Also includes: When a request to add or delete sub-devices is received, the tag number strategy information is modified to generate tag number configuration information.

8. A device-adaptive model processing system, characterized in that, The system includes: The acquisition unit is used to acquire the device information corresponding to the device to be added; wherein, the device information includes at least the IO data of the device to be added, the IO data of all sub-devices in the device to be added, and the tag number strategy information corresponding to all sub-devices; A creation unit is used to create a corresponding device template based on the device information; The generation unit is used to generate tag configuration information based on the tag allocation mechanism, the IO data of the device to be added, the IO data of all sub-devices under the device to be added, and the tag strategy information corresponding to all sub-devices; wherein, the tag strategy information is determined at least by the data type of the tag, the length of the tag, and the status code of the tag; The instantiation unit is used to instantiate the batch template of the batch device request through the template mechanism and the tag configuration information when a batch device request with the same tag configuration information is received and the device template meets the instantiation conditions.

9. A storage medium, characterized in that, The storage medium includes stored instructions, wherein, when the instructions are executed, the device in which the storage medium resides is controlled to perform the device adaptive model processing method as described in any one of claims 1 to 7.

10. An electronic device, characterized in that, It includes a memory, and one or more instructions, wherein one or more instructions are stored in the memory and configured to be executed by one or more processors, as described in any one of claims 1 to 7, of the device adaptive model processing method.

Images