Multi-dimensional configurable tree data coding and construction system

Abstract

The invention provides a multi-dimensional configurable tree data coding and construction system, and relates to the technical field of data coding and management. The system comprises a code configuration management module, a code distribution module, a code search module and a data storage module, and the code configuration management module is responsible for creating and managing code configuration and providing a code rule for the code distribution module; the coding distribution module is responsible for distributing the configured coding rule to a specific management object; the code search module is responsible for calling the data storage module to perform data query according to a query condition input by a user; and the data storage module is responsible for storing and managing coded data and providing a data access interface for the upper layer module. The invention provides a data coding and construction system which is more flexible, efficient and extensible, so that the urgent requirements of complex industrial control systems such as power plants and other fields on data coding management are better met.

Description

Technical Field

[0001] The present invention relates to the technical field of data encoding and management, and particularly relates to a multi-dimensional configurable tree data encoding and construction system. Background Art

[0002] In today's information age, data management and information system design play crucial roles in all walks of life. Among them, the tree structure, as a basic and effective data structure, is widely used in various data management and information systems because it can clearly and intuitively represent data sets with hierarchical and branching characteristics. The application scenarios of the tree structure are extremely extensive, and its advantage lies in being able to intuitively display the classification and hierarchical relationships between data. In the field of industrial equipment management, the application of the tree structure is particularly important. Industrial equipment usually has complex hierarchical relationships. From the entire factory to production lines and then to individual equipment, each level has its unique functions and dependencies. Through the tree structure, this hierarchical relationship can be clearly represented, thus realizing the efficient management and maintenance of equipment. For example, in large industrial facilities such as power plants, the number of equipment and components is huge, the types are numerous, and the relationships are complex. Conducting efficient and accurate coding management for them is of crucial significance for the maintenance, management, and operation of the system.

[0003] The KKS coding (Kraftwerk-Kennzeichen-System, power plant identification system) is a hierarchical coding system widely used in industrial control systems such as power plants. The KKS coding uniquely identifies the equipment and components in the power plant through predefined coding rules, facilitating equipment identification, location, information management, and maintenance. However, with the continuous expansion of the scale of power plant systems and increasingly complex management requirements, some deficiencies of traditional KKS coding have gradually emerged in terms of flexibility, scalability, and management efficiency. First of all, although the KKS coding has relatively high generality in the power plant industry, its coding rules are relatively fixed and it is difficult to flexibly adjust according to the specific requirements of different power plants. For example, for some special equipment or components, the KKS coding may not provide sufficient coding space or a suitable coding structure. Secondly, with the development of technology, the relationships between equipment and components in power plant systems have become increasingly complex, and a single KKS coding is difficult to meet multi-dimensional and multi-level management requirements. For example, in addition to coding according to equipment type and location, it is also necessary to identify and manage according to multiple dimensions such as control loops, affiliated systems, and safety levels. In addition, during the upgrade and transformation process of power plant systems, how to be compatible with the original KKS coding and achieve a smooth transition between the old and new systems is also an urgent problem to be solved.

[0004] Although there are some existing coding methods and related research, they are still insufficient in dealing with the above challenges. Most of the existing coding methods are targeted at specific fields or specific types of management objects, lacking generality and flexibility, and it is difficult to adapt to complex industrial control systems. Especially when dealing with multi-level tree-shaped data, traditional methods often face problems such as complex coding design, low data query efficiency, and difficult system maintenance. Summary of the Invention

[0005] The object of the present invention is to provide a multi-dimensional configurable tree-shaped data coding and construction system for solving the data coding management problem in view of the deficiencies of the above-mentioned existing technologies.

[0006] To achieve the above object, the technical solution adopted by the present invention is as follows:

[0007] The present invention provides a multi-dimensional configurable tree-shaped data coding and construction system, which includes: a coding configuration management module, a coding allocation module, a coding search module, and a data storage module.

[0008] The coding configuration management module is responsible for creating and managing coding configurations, and providing coding rules to the coding allocation module. The coding configuration includes coding length, segmentation method, segment length, segment meaning, and base selection.

[0009] The coding allocation module is responsible for allocating the configured coding rules to specific management objects, and the management objects are various business entities.

[0010] The coding search module is responsible for calling the data storage module to perform data queries according to the query conditions input by the user. The coding search module provides a unified coding search interface, supports single search and range search, and can automatically select search strategies according to different coding rules and data storage methods.

[0011] The data storage module is responsible for storing and managing coding data, and providing a data access interface to the upper-layer module.

[0012] Optionally, in the coding configuration management module,

[0013] Configuring the coding length supports fixed-length and variable-length coding;

[0014] Configuring the segmentation method supports multi-level segmentation, and can segment by numerical bits or by character bits;

[0015] The base selection supports binary, octal, decimal, hexadecimal, vigesimal, duodecimal, hexavigesimal, and sexagesimal, and also supports user-configured arbitrary bases.

[0016] Optionally, the coding allocation module is specifically used for:

[0017] Support the selection of management objects for different management systems; apply the encoding configuration to the selected management objects; maintain a mapping relationship between the encoding rules and the management objects; provide an interface for each management module to call to obtain its corresponding encoding rules; ensure that the allocated encoding is unique under the same encoding rule.

[0018] Optionally, the encoding lookup module is specifically used for:

[0019] In the case of single lookup, perform an exact lookup based on the complete encoding;

[0020] In the case of range lookup, support range lookups greater than and / or less than a certain encoding. Range lookups include mask lookups and numerical range lookups. In the case of mask lookups, provide a mask of the same length as the encoding, with the positions corresponding to the segments to be looked up being 1 and the other positions being 0. Perform a "bitwise AND" operation between the mask and the encoding to extract the values of the corresponding segments, and compare the extracted values with the target values to determine if there is a match. In the case of numerical range lookups, provide the start value and end value of the target numerical range. According to the rule of segmenting by numerical bits, convert the start value and end value into the numerical ranges of the corresponding segments, and directly compare whether the numerical values of the corresponding segments in the encoding are within the target range to determine if there is a match.

[0021] Optionally, the data storage module is specifically used for:

[0022] Hide the underlying data storage details from the upper-layer applications and provide a unified data access interface;

[0023] Support relational databases, binary files, and files in various structured representations;

[0024] Provide interfaces for data reading, writing, updating, and deleting operations;

[0025] Handle the differences between different storage methods and provide a consistent access experience for the upper-layer applications;

[0026] Use each segment of the encoding as a field in the database table and establish an index to enable lookup using the index.

[0027] The beneficial effects of the present invention include:

[0028] The multi-dimensional configurable tree data encoding and construction system provided by the present invention includes: an encoding configuration management module, an encoding allocation module, an encoding search module, and a data storage module. The encoding configuration management module is responsible for creating and managing encoding configurations, and providing encoding rules to the encoding allocation module. The encoding configuration includes encoding length, segmentation method, segmentation length, segment meaning, and base selection. The encoding allocation module is responsible for allocating the configured encoding rules to specific management objects, where the management objects are various business entities. The encoding search module is responsible for calling the data storage module to perform data queries according to the query conditions input by the user. The encoding search module provides a unified encoding search interface, supports single search and range search, and can automatically select search strategies according to different encoding rules and data storage methods. The data storage module is responsible for storing and managing encoding data, and providing a data access interface to the upper-level module. The present invention provides a more flexible, efficient, and scalable data encoding and construction system, thereby better meeting the urgent needs of complex industrial control systems such as power plants and other fields for data encoding management. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0030] Figure 1 FIG. shows the structural schematic diagram of the multi-dimensional configurable tree data encoding and construction system provided by the embodiment of the present invention;

[0031] Figure 2 FIG. shows the schematic diagram of numerical bit segmentation provided by the embodiment of the present invention;

[0032] Figure 3 FIG. shows the schematic diagram of character bit segmentation provided by the embodiment of the present invention;

[0033] Figure 4 FIG. shows the schematic diagram of the user interface of the encoding configuration management module provided by the embodiment of the present invention;

[0034] Figure 5 FIG. shows the schematic diagram of the working process of the encoding allocation module provided by the embodiment of the present invention;

[0035] Figure 6 FIG. shows the schematic diagram of mask search provided by the embodiment of the present invention;

[0036] Figure 7 FIG. shows the schematic diagram of numerical range search provided by the embodiment of the present invention;

[0037] Figure 8 Shows the schematic diagram of the working process of the encoding lookup module provided by the embodiment of the present invention;

[0038] Figure 9 Shows the schematic diagram of the relational database provided by the embodiment of the present invention;

[0039] Figure 10 Shows the schematic diagram of the data storage module provided by the embodiment of the present invention;

[0040] Figure 11 Shows the example diagram of the power plant equipment encoding configuration provided by the embodiment of the present invention;

[0041] Figure 12 Shows the example diagram of the ID card encoding configuration provided by the embodiment of the present invention;

[0042] Figure 13 Shows the example diagram of the VIN encoding configuration provided by the embodiment of the present invention;

[0043] Figure 14 Shows the example diagram of the unified social credit code configuration provided by the embodiment of the present invention;

[0044] Figure 15 Shows the example diagram of the multi-level encoding configuration provided by the embodiment of the present invention;

[0045] Figure 16 Shows the example diagram of the multi-level encoding application provided by the embodiment of the present invention. Detailed implementation manners

[0046] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0047] Based on an in-depth analysis of existing technologies and applications, it can be concluded that the current data coding management has the following shortcomings: The coding structure is rigid and inflexible: The existing coding methods, especially the coding systems such as KKS coding that are applied to specific industries, have relatively fixed coding structures and rules, which are difficult to flexibly adjust according to the needs of actual application scenarios. This rigid coding structure limits the system's adaptability to management objects of different types and sizes, and it is difficult to meet diverse coding needs. For example, when some special equipment or components need to be encoded, the existing coding methods may not provide enough coding space or suitable coding structures. Limited configuration options and poor scalability: The existing coding systems lack sufficient configuration options in terms of coding length, segmentation mode, and base selection, and users cannot customize coding parameters according to actual needs. This limited configurability leads to poor scalability of the coding system, which is difficult to adapt to the needs of future business development and technological progress. For example, most of the existing coding methods only support specific bases (such as decimal or hexadecimal) and cannot be flexibly connected to coding systems of other bases. Poor compatibility with multiple coding standards: Existing coding methods are usually designed for specific fields or specific types of management objects, and lack compatibility with multiple coding standards. In practical applications, especially in large and complex systems (such as power plants), it is often necessary to use multiple coding standards at the same time to identify different objects or meet different management requirements (such as equipment identification, control loop identification, etc.). It is difficult for existing technologies to achieve unified management and application of multiple coding standards, which makes system integration difficult, data sharing difficult, and increases management complexity and cost. Inefficient coding search: Traditional coding search methods have slow retrieval speed and low efficiency when processing large-scale data, especially when performing range search or fuzzy matching. For example, traversing a tree structure in a relational database usually requires the use of recursive queries or join queries. These operations consume a lot of computing resources and time when the amount of data is large, and it is difficult to meet application scenarios with high real-time requirements. The data storage method is single and lacks flexibility: The existing technology mainly relies on relational databases for the storage and management of coded data, and lacks support for other data storage methods. This single data storage method may have storage and query performance bottlenecks when facing massive data or specific application scenarios, and it is also difficult to meet the personalized needs of different users for data security, data backup, etc. Insufficient support for multi-dimensional management and complex handling of special cases: Most existing coding methods only support single-dimensional coding, which is difficult to meet the needs of multi-dimensional management. For example, in a power plant system, in addition to coding according to equipment type and location, it is also necessary to identify and manage according to multiple dimensions such as control loop, system, and safety level. In addition, the existing technology is often complicated to handle some special cases (such as the same object needs to be assigned multiple codes of different standards), lacking effective solutions, which increases the management difficulty and maintenance cost of the system.The information system needs to manage multiple objects with multiple encodings and lacks a unified management solution: In an actual information system, it is often necessary to manage multiple different types of objects and assign different encoding rules to these objects. Existing technologies usually lack the ability to integrate multiple encoding rules of multiple objects into a unified system for unified management. For example, an information system may need to manage multiple objects such as organizational structures, personnel, equipment, and documents at the same time and assign different encodings to them. In this case, if traditional encoding methods are used, a separate encoding system needs to be established for each type of object, resulting in problems such as system redundancy, data inconsistency, and complex management.

[0048] To this end, the present invention provides a multi-dimensional configurable tree data encoding and construction system to solve the problem of data encoding management.

[0049] Figure 1 The structure diagram of the multi-dimensional configurable tree data encoding and construction system provided by the embodiment of the present invention is shown, as Figure 1 shown, the multi-dimensional configurable tree data encoding and construction system provided by the present invention includes: an encoding configuration management module, an encoding assignment module, an encoding search module, and a data storage module.

[0050] The user interacts with the system through the user interface. In Figure 1 the figure, the arrows represent the call relationships or data flows between the modules, where the solid arrows represent the main call relationships and the dashed arrows represent the optional call relationships.

[0051] The encoding configuration management module is responsible for creating and managing encoding configurations and providing encoding rules to the encoding assignment module. The encoding configuration includes encoding length, segmentation method (by numerical bit or character bit), segmentation length, segment meaning, and base selection. The user can customize the encoding parameters according to specific requirements.

[0052] In the encoding configuration management module, the configured encoding length supports fixed-length and variable-length encodings.

[0053] The configured segmentation method specifically includes: supporting multi-level segmentation, capable of segmenting by numerical bit or by character bit; the base selection supports binary, octal, decimal, hexadecimal, vigesimal, duodecimal, hexavigesimal, and base-36, and supports the user to configure any base. Specifically, the configured segmentation method supports multi-level segmentation, can segment by numerical bit (similar to the snowflake algorithm) or by character, and the segmentation method can be abstracted as segmenting according to specified rules, and the rules can be defined according to different application scenarios. Segmenting by numerical bit is to divide the numerical bits of the encoding into multiple segments, and each segment represents a specific meaning. For example, each bit or several bits of a long integer can be used as a segment. As Figure 2As shown, a 64-bit long integer can be divided into multiple segments, and each segment has a specific meaning. For example, the first segment can represent the system, the second segment can represent the device type, and so on. Segmenting by character bits means taking each character bit of the encoded string as a segment. For example, each character of a string can be taken as a segment. As Figure 3 shown, a string encoding can be divided into multiple character bits, and each character bit can be taken as a segment.

[0054] Configuring the segment length and the meaning of segments specifically includes: the length of each segment, which can be the number of numerical bits or the number of character bits, and the specific meaning represented by each segment. For example, in the KKS coding of power plants, a certain segment may represent the system, and a certain segment may represent the device type; in the drug traceability code, a certain segment may represent the enterprise code, and a certain segment may represent the drug identification.

[0055] Selecting the coding base specifically includes: supporting multiple base selections such as binary, octal, decimal, hexadecimal, vigesimal, duodecimal, hexavigesimal, and base-36, and supporting users to configure any base. Selecting different bases can achieve compatibility with specific coding standards. For example: when selecting decimal, it can be compatible with ID card coding and drug traceability codes. When selecting hexadecimal, it can be compatible with the KKS coding of power plants. When selecting base-36, it can be compatible with the unified social credit code.

[0056] The storage of the configuration specifically includes: configuration files (such as JSON, YAML, XML, etc.) or databases can be used to store configuration information. The storage method of the configuration can be abstracted as storing the configuration information in any readable and writable medium. According to the different configuration methods and storage methods, different reading and parsing logics are adopted. The configuration of the user is verified to ensure the legality and consistency of the configuration. For example, it is necessary to verify the legality of the base (for example, it cannot be base-1 or a negative base), whether the sum of the segment lengths exceeds the maximum length, etc.

[0057] The configuration interface specifically includes: a graphical configuration interface can be provided, and users can select the base, set the segmentation method, length, and meaning, etc. through controls such as drop-down boxes and text boxes. The configuration interface can be abstracted as any interface form that can perform human-computer interaction. As Figure 4 shown, users can configure the encoding through this graphical interface.

[0058] The encoding configuration information can be stored in multiple ways. For example: the configuration file can adopt the JSON format, which has a clear structure, is easy to read and edit, and is suitable for storing configuration information with a hierarchical structure. For example:

[0059] {

[0060] "codeName":"KKS",

[0061] "base": 16,

[0062] "maxLength": 15,

[0063] "segments":

[0064] {"name": "System", "length": 4, "type": "numeric"},

[0065] {"name": "Device Type", "length": 3, "type": "numeric"},

[0066] {"name": "Device Number", "length": 8, "type": "numeric"}

[0068] }

[0069] The configuration file can also be in YAML format. This format has a more concise syntax, stronger readability, and is also suitable for storing hierarchical configuration information. For example:

[0070] codeName: KKS

[0071] base: 16

[0072] maxLength: 15

[0073] segments:

[0074] - name: System

[0075] length: 4

[0076] type: numeric

[0077] - name: Device Type

[0078] length: 3

[0079] type: numeric

[0080] - name: Device Number

[0081] length: 8

[0082] type: numeric

[0083] The configuration file can also be in XML format. This format has good scalability and self - descriptiveness and is suitable for storing complex configuration information. For example:

[0084] ​<codeconfig>

[0085] <codename>KKS< / codename>

[0086] <base> 16

[0087] <maxlength> 15< / maxlength>

[0088] <segments>

[0089] <segment>

[0090] <name>system< / name>

[0091] <length> 4< / length>

[0092] <type>numeric< / type>

[0093] < / segment>

[0094] <segment>

[0095] <name>equipment type< / name>

[0096] <length> 3< / length>

[0097] <type>numeric< / type>

[0098] < / segment>

[0099] <segment>

[0100] <name>equipment number< / name>

[0101] <length> 8< / length>

[0102] <type>numeric< / type>

[0103] < / segment>

[0104] < / segments>

[0105] < / codeconfig>

[0106] The Properties file can be used to store configuration information. This file stores configuration information in the form of key-value pairs, which is simple and easy to use and suitable for storing simple configuration items. For example:

[0107] codeName=KKS

[0108] base=16

[0109] maxLength=15

[0110] segments.system.name=System

[0111] segments.system.length=4

[0112] segments.system.type=numeric

[0113] segments.deviceType.name=Device Type

[0114] segments.deviceType.length=3

[0115] segments.deviceType.type=numeric

[0116] segments.deviceID.name=Device ID

[0117] segments.deviceID.length=8

[0118] segments.deviceID.type=numeric

[0119] A relational database or a non-relational database can be used to store configuration information. For example, a configuration table can be created, which contains fields such as coding name, base, maximum length, and segmentation information. A distributed configuration center (such as ZooKeeper, Etcd, Apollo, Nacos, etc.) can be used to store and manage configuration information to achieve dynamic update and centralized management of configurations. Other storage methods can also be selected according to specific requirements, such as storing configuration information in specific hardware devices or transmitting and storing it through specific protocols.

[0120] The configured storage method can be abstracted as storing configuration information in any readable and writable medium. The system can adopt different reading and parsing logics according to different storage methods, and verify the configuration information to ensure the legality and consistency of the configuration. At the same time, the configuration storage method is extensible to support more storage methods in the future. When the user submits a configuration, the system will perform verifications, such as whether the base is within the supported range, whether the sum of the segment lengths exceeds the maximum length, and whether the names of each segment are repeated, etc. The verification rules can be extended according to specific requirements.

[0121] The encoding assignment module is responsible for assigning the configured encoding rules to specific management objects, where the management objects are various business entities, such as organizational structures, personnel, devices, documents, etc.

[0122] Optionally, the encoding assignment module is specifically used for: supporting the selection of management objects in different management systems, where the management objects can be abstracted as any entity that requires encoding management; applying the encoding configuration to the selected management objects; maintaining a mapping relationship between the encoding rules and the management objects, and the mapping relationship is shown in Table 1 below; providing an interface for each management module to call to obtain its corresponding encoding rules, and this interface can be abstracted as any interface form that can perform data exchange; ensuring that the assigned encoding is unique under the same encoding rule.

[0123] In actual operation, the corresponding encoding rules can be automatically assigned according to the type of management object. For example, if the selected management object is "power plant equipment", then the "KKS compatible encoding rule" is automatically assigned. The assignment strategy can be abstracted as any method of automatically or manually assigning encoding rules according to the type of management object or other attributes. When assigning an encoding, the system will check whether the newly generated encoding is unique according to the encoding rule and the already assigned encodings. If it is not unique, the encoding will be regenerated until a unique encoding is generated. The uniqueness check can be abstracted as any algorithm or method that ensures the uniqueness of the encoding under the same encoding rule. As Figure 5 shown, the encoding assignment module generates an encoding based on the management object and encoding rule selected by the user, performs a uniqueness check, and finally stores the assignment result.

[0124] The encoding lookup module is responsible for calling the data storage module to perform data queries according to the query conditions input by the user. The encoding lookup module provides a unified encoding lookup interface that supports single lookup (exact match) and range lookup (based on mask and numerical range), improves the encoding retrieval efficiency, and can automatically select the lookup strategy according to different encoding rules and data storage methods.

[0125] Optionally, the encoding lookup module is specifically configured to: in the case of single lookup, perform an exact lookup based on the complete encoding; in the case of range lookup, support range lookup greater than and / or less than a certain encoding, where range lookup includes mask lookup and numerical range lookup. In the case of mask lookup, provide a mask with the same length as the encoding, with the positions corresponding to the segments to be looked up set to 1 and the other positions set to 0; perform an "AND" operation on the mask and the encoding to extract the values of the corresponding segments; compare the extracted values with the target values to determine whether there is a match. For example, to find all devices with the "system" field in the KKS encoding being "01KP", the mask "FFFF00000000000" can be used (assuming the "system" field is the first 4 bits and in hexadecimal). Performing an "AND" operation on this mask and the KKS encodings of all devices can quickly filter out the devices that meet the conditions. As Figure 6 shown, the specified field values in the encoding are extracted through mask and bit operations and compared with the target values. In the case of numerical range lookup, provide the start value and end value of the target numerical range; convert the start value and end value into the numerical ranges of the corresponding segments according to the rule of segmenting by numerical bits; directly compare whether the numerical values of the corresponding segments in the encoding are within the target range to determine whether there is a match. For example, to find all devices with the device number between 1000 and 2000, the numerical values of the "device number" field in the encoding can be directly compared to see if they are within this range. As Figure 7 shown, the numerical range is converted into the target range, and then the corresponding field values in the encoding are compared to see if they are within the target range. Appropriate lookup strategies (such as mask lookup, range lookup, etc.) can be automatically selected according to different encoding rules. The selection of the lookup strategy can be abstracted as automatically selecting the optimal lookup method based on encoding rules, query conditions, or other factors. It can handle different data storage methods (databases, files in various formats), interact with the data storage module to obtain data.

[0126] In actual operation, a hash table or other data structures can be used for single lookup to achieve fast and accurate matching. Mask lookup can be implemented through bitwise operations. More abstractly, mask lookup can be regarded as using a template encoding that is the same length as the encoding or truncated as needed. Each bit in the template encoding can be specified as a specific value or a wildcard. For example, if you want to find an encoding starting with a specific string, wildcards can be used to represent the remaining part. For range lookup, for numeric fields, the sizes can be directly compared; for character fields, comparison can be performed in lexicographic order. More abstractly, range lookup can be regarded as converting the target range into one or more template encodings and then using these template encodings for lookup. The lookup strategy can be automatically selected according to the segmentation method and segment type in the encoding rule. For example, if a segment is segmented by numeric bits and the lookup condition is a numeric range, range lookup can be selected; if a segment is segmented by character bits and the lookup condition is an exact match, single lookup can be selected. As Figure 8 shown, the encoding lookup module selects an appropriate lookup strategy according to different lookup requirements and encoding rules, and obtains data through the data storage module interface.

[0127] The data storage module is responsible for storing and managing encoding data and providing a data access interface to the upper-level module.

[0128] Specifically, the data storage module is used to: be responsible for saving the encoding data to a relational database or files in different formats, hiding the underlying data storage details from the upper-level application, and providing a unified data access interface; support relational databases, binary files, and various structured representation files (such as JSON, XML, YAML, etc.), and the storage method can be abstracted as any medium or method that can persist data; provide interfaces for data reading, writing, updating, and deleting. For example, getData(code, codeType): obtain data according to the encoding and encoding type; writeData(data, codeType): write data, where data contains the management object and its corresponding encoding information; updateData(data, codeType): update data; deleteData(code, codeType): delete data. Handle the differences between different storage methods and provide a consistent access experience for the upper-level application; use each segment of the encoding as a field in the database table and establish an index, so that lookup can be achieved using the index. Through bitwise operations and numeric range comparison, the target node or node set can be directly located without recursive query or join query. The data storage module can also selectively store the configuration information of the encoding configuration management module.

[0129] In actual operation, a table can be created for each coding rule, and the fields of the table correspond one by one to the segments in the coding rule. For example, for KKS-compatible coding, a table named "KKS_DEVICE" can be created, which contains fields such as "system", "device type", "device number", etc. As Figure 9 shown, the fields in the KKS_DEVICE table correspond to the segments in the KKS-compatible coding rule. Indexes can be established on each field to improve query efficiency. SQL statements can be used to implement data reading, writing, updating, and deleting operations. For example, "SELECT * FROM KKS_DEVICE WHERE (coding & system mask) = coding value of system A" can be used to implement mask lookup. The format of the binary file can be customized. For example, each coding can be stored as a byte array with a fixed length, and each part of the array corresponds to a segment in the coding rule. File streams can be used to implement data reading and writing operations. For example, for the JSON format, each management object and its coding information can be stored as a JSON object, and multiple JSON objects form a JSON array and are stored in a file. The reading and writing operations can be performed using the corresponding JSON library. As Figure 10 shown, the data storage module provides a unified data access interface and supports multiple different storage methods.

[0130] The multi-dimensional configurable tree data coding and construction system provided by the present invention is an organic whole, and each component cooperates with each other to jointly complete functions such as coding configuration, allocation, search, and data storage. Their connection relationships are mainly reflected in the following aspects:

[0131] Coding configuration management module and coding allocation module: The coding configuration management module is the data source of the coding allocation module. The coding configuration management module is responsible for creating and maintaining various coding configurations (such as coding base, length, segmentation method, meaning of each segment, etc.), and providing these configuration information to the coding allocation module. When performing coding allocation, the coding allocation module needs to call the interface provided by the coding configuration management module to obtain the coding configuration information corresponding to a specific management object (such as power plant equipment, organization structure, etc.). When the configuration information in the coding configuration management module changes (for example, an administrator modifies a certain coding rule), the coding allocation module needs to be notified so that it can update the relevant mapping relationships and the allocated coding data (optional).

[0132] Coding Allocation Module and Coding Search Module: The coding allocation module is responsible for applying coding configuration rules to specific management objects and generating corresponding codes. These generated codes and coding rules are the basis for the coding search module to perform search operations. When the coding search module performs a search operation, it needs to parse the query conditions input by the user according to the coding rules (such as segmentation methods, meanings of each segment, etc.) provided by the coding allocation module and generate corresponding search strategies (such as masks, template codes, etc.). The search results of the coding search module depend on the coding data generated by the coding allocation module.

[0133] Coding Allocation Module and Data Storage Module: After generating codes for management objects, the coding allocation module needs to transfer the information of the management objects and the corresponding coding data to the data storage module for storage. When the coding allocation module updates the coding information of a certain management object (such as due to configuration changes or information modification), it needs to notify the data storage module to update the corresponding data records. When generating codes, the coding allocation module can use the interfaces provided by the data storage module to perform coding uniqueness verification to ensure that the generated codes are unique in the system.

[0134] Coding Search Module and Data Storage Module: The coding search module is the main user of the data storage module. According to the query conditions and coding rules input by the user, the coding search module generates corresponding query statements or instructions and calls the interfaces provided by the data storage module to perform data query operations. The data storage module is responsible for reading the corresponding data from the underlying storage medium (such as databases, files, etc.) according to the requests of the coding search module and returning it to the coding search module. The data storage module hides the details of the underlying data storage from the coding search module, enabling the coding search module to focus on the implementation of the search logic without having to worry about how the data is specifically stored.

[0135] User Interface and Each Module: Users interact with the coding configuration management module through the user interface to create, modify, delete, and view coding configuration information. Users can select management objects through the user interface and trigger the coding allocation module to perform coding allocation operations. Users input query conditions through the user interface and trigger the coding search module to perform coding search operations. The user interface is responsible for displaying the query results returned by the coding search module.

[0136] Configuration Information Storage: The coding configuration management module can store configuration information in multiple media (such as files, databases, distributed configuration centers, etc.). This part of the configuration information can be read and used by the coding configuration management module itself or other modules. The data storage module can also selectively store the configuration information of the coding configuration management module as needed, such as storing the configuration information as part of a data table for more efficient query and management.

[0137] The following will use multiple specific application scenario examples to elaborate in detail on the operation process of the system provided by the present invention, and will focus on demonstrating the fixed-length coding designed according to the latest rules and its advantages.

[0138] Scenario 1: Power plant equipment coding management (reflecting multiple attributes through coding)

[0139] The power plant administrator creates a new coding configuration through the coding configuration management module for the unified coding management of power plant equipment. Select the hexadecimal system, set the maximum coding length to 16 bits, and configure the segmentation method as segmentation by numerical bits. Configure the segment information: Bits 1-2: Plant area / unit, with a length of 2 bits. For example, A1 represents Unit 1 in Plant Area A; Bits 3-6: System, with a length of 4 bits. For example, KPQA represents the relevant systems of the turbine specialty; Bits 7-8: Control loop, with a length of 2 bits. For example, 01 represents Control Loop 1; Bits 9-12: Installation location, with a length of 4 bits. For example, LOC1 represents a specific installation location; Bits 13-16: Equipment number, with a length of 4 bits. For example, 0001 represents a specific equipment number. The system verifies the legality and consistency of the configuration. The system stores the configuration information in the database. Figure 11 It shows a possible coding configuration method for power plant equipment, dividing the coding into multiple segments such as plant area / unit, system, control loop, installation location, and equipment number. Through this coding configuration, each coding directly reflects the multiple attributes of the equipment.

[0140] The power plant administrator selects the management object of "power plant equipment" through the coding assignment module. The system automatically assigns "power plant equipment coding configuration" to "power plant equipment". The power plant administrator enters equipment information, for example: equipment name: Equipment A, plant / unit: A1, system: KPQA, control loop: 01, installation location: LOC1, equipment number: 0001. The coding assignment module generates a code for this equipment according to the "power plant equipment coding configuration": A1KPQA01LOC10001. This code directly reflects the plant / unit, system, control loop, installation location and equipment number to which the equipment belongs. The system saves the equipment information and the corresponding code to the database through the data storage module. During a single search, the power plant administrator needs to search for the equipment information with the code "A1KPQA01LOC10001". The coding search module receives the query request. The coding search module determines it is a single search according to the "power plant equipment coding configuration". The coding search module calls the interface of the data storage module to query the equipment information according to the code. The data storage module returns the equipment information. During a range search, the power plant administrator can perform a range search according to different attribute combinations. For example: to search for all equipment with "plant / unit" being "A1", the mask "FFFF000000000000" or the template code "A1???" can be used. To search for all equipment with "system" being "KPQA", the mask "0000FFFF00000000" or the template code "??KPQA???" can be used. To search for all equipment with "control loop" being "01", the mask "00000000FFFF0000" or the template code "???01???" can be used. To search for all equipment with "installation location" being "LOC1", the mask "000000000000FFFF" or the template code "???LOC1???" can be used. To search for all equipment with "plant / unit" being "A1", "system" being "KPQA", and "control loop" being "01", the mask "FFFFFFFF00000000" or the template code "A1KPQA01???" can be used. The coding search module receives the query request. The coding search module determines it is a range search according to the "power plant equipment coding configuration" and generates the corresponding mask or template code according to the query conditions. The coding search module calls the interface of the data storage module to perform a query operation with the mask or template code. The data storage module returns all equipment information that meets the conditions.

[0141] When the device information changes, such as the device being moved to a new installation location, the administrator can update the device information through the user interface, and the coding assignment module is responsible for updating the corresponding coding of the device. For example, if the installation location changes from "LOC1" to "LOC2", the coding will correspondingly change from "A1KPQA01LOC10001" to "A1KPQA01LOC20001". The data storage module is responsible for saving the updated device information and coding to the database. When the device is scrapped, the administrator can delete the device information through the user interface, and the data storage module is responsible for deleting the information of the device and the corresponding coding from the database.

[0142] The administrator can update the existing coding configuration through the coding configuration management module, such as modifying the length of a certain segment of the "Power Plant Equipment Coding Configuration". The system will update the coding data stored in the data storage module according to the new configuration information. If there are major changes to the coding rules, it may be necessary to provide corresponding coding conversion tools or services.

[0143] Scenario 2: ID Card Coding Management

[0144] The system administrator creates the "ID Card Coding Configuration" through the coding configuration management module, selects the decimal system, sets the maximum coding length to 18 digits, and configures the segmentation method to segment by character position. Configuration of segment information: The 1st - 6th digits: Address code, with a length of 6 digits; The 7th - 14th digits: Date of birth code, with a length of 8 digits; The 15th - 17th digits: Sequence code, with a length of 3 digits; The 18th digit: Check code, with a length of 1 digit. The system verifies the legality and consistency of the configuration. The system stores the configuration information in the database. Figure 12 Shows the configuration method of the ID card coding, which divides the coding into four segments: address code, date of birth code, sequence code, and check code. The system administrator selects the management object of "personnel" through the coding assignment module. The system automatically assigns the "ID Card Coding Configuration" to "personnel".

[0145] The system administrator enters personnel information, including name, ID number, etc. The coding allocation module validates the legality of the entered ID number according to the "ID coding configuration", including whether the length is 18 digits, whether each field conforms to the rules, whether the check code is correct, etc. The system saves the personnel information and the corresponding ID number to the database through the data storage module. In a single search, the system administrator needs to search for the personnel information of the person with the ID number "110101199001011234". The coding search module receives the query request. The coding search module determines it is a single search according to the "ID coding configuration". The coding search module calls the interface of the data storage module to query the personnel information according to the ID number. The data storage module returns the personnel information. In a range search, the system administrator needs to search for the personnel information of those born between January 1, 1990 and December 31, 1990. The coding search module receives the query request. The coding search module determines it is a range search according to the "ID coding configuration" and identifies the position and length of the birth date code. The coding search module generates the template code "???1990???", where "?" represents a wildcard. The coding search module calls the interface of the data storage module to perform a template code matching query operation. The data storage module returns all the personnel information whose birth date code fields match "1990".

[0146] Scenario 3: Vehicle Identification Number (VIN) Management

[0147] The system administrator creates a "VIN coding configuration" through the coding configuration management module, selects the base-34 number system (excluding I, O, Q), sets the maximum coding length to 17 digits. The configuration segmentation method is segmented by character position. Configuration segment information: The 1st - 3rd digits: World Manufacturer Identifier (WMI), with a length of 3 digits; The 4th - 9th digits: Vehicle Descriptor Section (VDS), with a length of 6 digits; The 10th digit: Model Year, with a length of 1 digit; The 11th digit: Assembly Plant, with a length of 1 digit; The 12th - 17th digits: Production Serial Number, with a length of 6 digits. The system validates the legality and consistency of the configuration. The system stores the configuration information in the database. Figure 13 Shows the configuration method of the VIN coding, dividing the coding into five segments: WMI, VDS, Model Year, Assembly Plant, and Production Serial Number. The system administrator selects the "Vehicle" management object through the coding allocation module. The system automatically assigns the "VIN coding configuration" to "Vehicle".

[0148] The system administrator enters vehicle information, including the manufacturer, model, VIN, etc. The coding allocation module validates the legality of the entered VIN according to the "VIN Coding Configuration", including whether the length is 17 digits, whether it contains illegal characters (I, O, Q), and whether each field conforms to the rules, etc. The system saves the vehicle information and the corresponding VIN to the database through the data storage module. During a single search, the system administrator needs to search for vehicle information with a VIN of "L???". The coding search module receives the query request and specifies the VIN as "L???". The coding search module determines it is a single search according to the "VIN Coding Configuration". The coding search module calls the interface of the data storage module to query the vehicle information according to the VIN. The data storage module returns the vehicle information. During a range search, the system administrator needs to search for all vehicle information produced in China (assuming the first digit of the WMI is "L" indicating China). The coding search module receives the query request, and the search condition is that the WMI starts with "L". The coding search module determines it is a range search according to the "VIN Coding Configuration" and identifies the position and length of the WMI field. The coding search module generates a template code "L???", where "?" represents a wildcard. The coding search module calls the interface of the data storage module to perform a template code matching query operation. The data storage module returns all vehicle information with the WMI field starting with "L".

[0149] Scenario 4: Unified Social Credit Code Management

[0150] The system administrator creates a "Unified Social Credit Code Configuration" through the coding configuration management module, selects the base-36 system (numbers and capital letters), sets the maximum coding length to 18 digits, and configures the segmentation method as character-position segmentation. Configuration segment information: The 1st digit: Registration management department code, length 1 digit; The 2nd digit: Organization category code, length 1 digit; The 3rd - 8th digits: Administrative division code of the registration management authority, length 6 digits; The 9th - 17th digits: Entity identification code (organization code), length 9 digits; The 18th digit: Check code, length 1 digit. The system validates the legality and consistency of the configuration. The system stores the configuration information in the database. Figure 14 It shows the configuration method of the unified social credit code, dividing the code into five segments: registration management department code, organization category code, administrative division code, entity identification code, and check code. The system administrator selects the management object of "enterprise" through the coding allocation module. The system automatically assigns the "Unified Social Credit Code Configuration" to the "enterprise".

[0151] The system administrator enters enterprise information, including the enterprise name, unified social credit code, etc. The coding allocation module verifies the legality of the entered unified social credit code according to the "Unified Social Credit Code Configuration", including whether the length is 18 digits, whether each field complies with the rules, whether the check code is correct, etc. The system saves the enterprise information and the corresponding unified social credit code into the database through the data storage module. During a single search, the system administrator needs to search for the enterprise information with the unified social credit code of "91110108MA01K7287Q". The coding search module receives the query request. The coding search module determines it is a single search according to the "Unified Social Credit Code Configuration". The coding search module calls the interface of the data storage module and queries the enterprise information according to the unified social credit code. The data storage module returns the enterprise information. During a range search, the system administrator needs to search for all enterprise information with the administrative division code of the registration authority as "110108" (Haidian District, Beijing). The coding search module receives the query request. The coding search module determines it is a range search according to the "Unified Social Credit Code Configuration" and identifies the position and length of the administrative division code. The coding search module generates the template code "??110108????", where "?" represents a wildcard. The coding search module calls the interface of the data storage module and performs a template code matching query operation. The data storage module returns all enterprise information with the administrative division code field as "110108".

[0152] Scenario Five: Multi-level Coding Management (Reflecting Hierarchical Relationships through Fixed-length Coding)

[0153] The system administrator creates the "Organization Coding Configuration" through the coding configuration management module, selects the base-36 system (numbers and capital letters), sets the maximum coding length to 18 digits (configured according to actual needs), and configures the segmentation method as segmentation by numerical digits. Configuration of segment information: The 1st - 4th digits: First-level department code, with a length of 4 digits; The 5th - 6th digits: Second-level department code, with a length of 2 digits; The 7th - 8th digits: Third-level department code, with a length of 2 digits; The 9th - 10th digits: Fourth-level department code, with a length of 2 digits; The 11th - 18th digits: Self-code of the fourth-level department, with a length of 8 digits. Figure 15 It shows the improved multi-level coding configuration method, which is divided into five coding segments according to the hierarchical relationship. The last coding segment is the self-coding segment of the management object (fourth-level department), and the length can be configured as needed. In this example, it is 8 digits. The system administrator selects the management object of "Organization" through the coding allocation module. The system automatically assigns the "Organization Coding Configuration" to "Organization".

[0154] The system administrator enters the organizational structure information and assigns codes in sequence according to the hierarchical relationship. For example: The code for the Group Headquarters (first-level department) is: 000100000000000001; the code for the Group Headquarters - Finance Department (second-level department) is: 000101000000000001; the code for the Group Headquarters - Finance Department - Accounting Group (third-level department) is: 000101010000000001; the code for the Group Headquarters - Finance Department - Accounting Group - Cashier Position (fourth-level department) is: 000101010100000001. The system automatically generates and assigns fixed-length codes according to the configured coding rules. Among them, the first four code segments are used to represent the hierarchical relationship and can be 0; the last code segment is the own code of this fourth-level department and is at least 1. The system saves the organizational structure information and the corresponding codes into the database through the data storage module. In a single search, search for the organizational structure information (i.e., the cashier position) with the code "000101010100000001". In a range search, search for all subordinate department information belonging to "Group Headquarters - Finance Department" (the code prefix is "000101"). The code search module receives the query request. The code search module determines it is a range search according to the "Organizational Structure Code Configuration". The code search module generates a mask "FFFFFFFF0000000000" or a template code "000101???" and calls the data storage module interface to perform a range search. The data storage module returns all organizational structure information with the upper-level department code of "000101". Figure 16 Shows the application of the improved multi-level code in the hierarchical relationship of the organizational structure, clearly reflecting the hierarchical relationship through the fixed-length code, and the last level is the own code of this fourth-level department.

[0155] It should be specifically noted that the present invention is not intended to completely replace the KKS code, but to provide a more flexible and configurable coding method. In scenarios where it is necessary to be compatible with the KKS code, such as when upgrading and transforming an existing power plant system, the present invention can keep the original KKS code unchanged to achieve a smooth transition; or when building a new power plant system, the KKS code can be selected to maintain consistency with industry practices. The core advantage of the present invention is to provide a more flexible and configurable coding system that can perform customized coding configuration and management according to the specific requirements of complex industrial control systems such as power plants, and can also be compatible with the KKS code or other coding standards as needed.

[0156] The present invention proposes a multi-dimensional configurable tree data encoding and construction system, which has the following significant beneficial effects compared to the prior art: Flexible encoding configuration: The present invention supports multiple bases (including but not limited to binary, decimal, hexadecimal, hexadecimal, etc.) and custom bases, supports segmentation by numerical and character bits, and allows users to customize the length and meaning of each segment, providing great flexibility in encoding configuration. This flexibility enables the present invention to adapt to the encoding requirements of various application scenarios, support multiple classification standards, such as compatible with existing ID card codes, power plant KKS codes, unified social credit codes, VIN codes, etc., and can also be used to build a new encoding system. Diversification of encoding configuration is achieved, and diversified configuration options including encoding length, segmentation mode, segment meaning, base selection, etc. are provided, so that users can customize encoding parameters according to actual needs to meet the specific needs of different fields and different systems. A multi-coding standard compatible encoding allocation mechanism is provided, which supports assigning different encoding rules to different management objects, realizes unified management and cross-system application, especially supports the allocation of multiple encoding standards for the same object, and simplifies the complexity of multi-coding management. Efficient code search: Design an efficient code search algorithm, especially for range search and fuzzy matching, improve the retrieval speed, meet the requirements of real-time and efficiency, the present invention supports single search and range search, and can automatically select the optimal search strategy according to the coding rules. Through mask search and value range search technology, the target code or code set can be quickly located, which significantly improves the efficiency of code retrieval. In particular, when the code is stored in a database, by using each segment of the code as a field of the database table and establishing an index, the index mechanism of the database can be fully utilized to achieve efficient data query, avoid full table scanning or complex association query, and solve the problem of extremely low efficiency of tree structure traversal in relational databases. Abstract data storage: The present invention hides the details of the underlying data storage from the upper-level application through the data storage module, provides a variety of data storage options, supports relational databases, multiple file formats (JSON, XML, YAML, binary, etc.) and other storage methods. This abstraction allows the present invention to flexibly adapt to different data storage environments, facilitate data migration and system expansion. Good scalability: The present invention adopts a modular design, and the modules interact through clearly defined interfaces, so that the system has good scalability. For example, new coding systems, new segmentation methods, new search strategies, and new data storage methods can be easily added without modifying the core code of the system. Wide range of application scenarios: The present invention can be widely used in various fields that require coding management, such as: Asset management: Generate unique codes for assets such as equipment and materials, and quickly find and locate assets according to coding rules. Organizational management: Construct a hierarchical organizational coding system to facilitate the query and statistics of organizational information.Personnel Management: Assign a unique code to each person and quickly search for personnel information based on the code, for example, being compatible with the existing ID card coding rules. Document Management: Generate a unique code for each document and quickly search for and file documents according to the coding rules. Product Traceability: Generate a unique code for each product and trace the production, circulation, and sales processes of the product based on the code. Advantages of Fixed-Length Coding (for specific scenarios, such as Scenario Five): In Scenario Five (multi-level coding management), the present invention adopts a fixed-length coding scheme. Through predefined coding segments, the hierarchical relationship of data is clearly expressed. The coding for each level occupies a fixed number of digits, making the coding structure more regular and facilitating computer processing and parsing. The fixed-length coding scheme simplifies data query operations, especially range searches. Through simple string prefix matching or masking operations, all data at the target level or sub-level can be quickly located without complex recursive queries or multi-table join operations, significantly improving query efficiency. The fixed-length coding scheme facilitates hardware acceleration. The regularity and determinacy of fixed-length coding leave room for hardware implementation. Through the parallel processing ability of hardware circuits, the efficiency of coding generation and query can be further improved. It provides flexible multi-dimensional coding management and special case handling strategies, supports coding and managing objects according to different dimensions, and provides effective solutions to handle special cases, simplifies management complexity, and improves the management efficiency and accuracy of the system. It provides a unified coding management system that can integrate multiple coding rules for multiple objects into a unified system for management, realizing unified coding and management of all managed objects, without deploying multiple sets of coding systems separately for different objects or different coding standards, thereby reducing system redundancy, improving data consistency, and simplifying management processes.

[0157] In summary, the present invention provides a multi-dimensional configurable tree data coding and construction system with high flexibility, strong scalability, support for multi-coding standard compatibility, and efficient search, which is of great significance for improving the management efficiency and level of complex industrial control systems such as power plants, as well as data management and information system design in a wider range of fields.

[0158] The above embodiments are only used to illustrate the technical concept and features of the present invention, and their purpose is to enable those of ordinary skill in the art to understand the content of the present invention and implement it. However, the protection scope of the present invention cannot be limited thereby. Any equivalent changes or modifications made according to the spirit and essence of the present invention should be covered within the protection scope of the present invention.

Claims

1. A multi-dimensional configurable tree data encoding and construction system, characterized in that: The system includes: a code configuration management module, a code allocation module, a code search module, and a data storage module. The coding configuration management module is responsible for creating and managing coding configurations and providing coding rules to the coding allocation module. The coding configuration includes coding length, segmentation mode, segment length, segment meaning, and base selection. The coding allocation module is responsible for allocating the configured coding rules to specific management objects, which are various business entities; The code search module is responsible for calling the data storage module to query data according to the query conditions entered by the user. The code search module provides a unified code search interface, supports single search and range search, and can automatically select the search strategy according to different coding rules and data storage methods; The data storage module is responsible for storing and managing the encoded data and providing a data access interface to the upper-level modules.

2. The multi-dimensional configurable tree data encoding and construction system according to claim 1, characterized in that: In the encoding configuration management module, Configure the encoding length to support fixed length and variable length encoding; The configuration segmentation mode supports multi-level segmentation, which can be segmented by numerical bit or character bit; The base selection supports binary, octal, decimal, hexadecimal, 20-base, 24-base, 26-base, and 36-base, and supports users to configure any base.

3. The multi-dimensional configurable tree data encoding and construction system according to claim 1, characterized in that: The coding allocation module is specifically used for: Support the selection of management objects for different management systems; apply the coding configuration to the selected management objects; maintain a mapping relationship between a coding rule and a management object; provide an interface for each management module to call to obtain its corresponding coding rule; ensure that the assigned code is unique under the same coding rule.

4. The multi-dimensional configurable tree data encoding and construction system according to claim 2, characterized in that: The encoding search module is specifically used for: In the case of a single search, an accurate search is performed based on the complete code; In the case of range search, range search greater than and / or less than a certain code is supported. Range search includes mask search and value range search. In the case of mask search, a mask with the same length as the code is provided. The position corresponding to the segment to be searched in the mask is 1, and the other positions are 0. The mask and the code are "AND" operated to extract the value of the corresponding segment, and the extracted value is compared with the target value to determine whether it matches; in the case of value range search, the start value and end value of the target value range are provided. According to the rule of segmentation by numerical bit, the start value and end value are converted into the value range of the corresponding segment, and the value of the corresponding segment in the code is directly compared to determine whether it is within the target range, that is, to determine whether it matches.

5. The multi-dimensional configurable tree data encoding and construction system according to claim 1, characterized in that: The data storage module is specifically used for: Hide the underlying data storage details from upper-layer applications and provide a unified data access interface; Supports relational databases, binary files, and various structured representation files; Provides interfaces for reading, writing, updating and deleting data; Handle the differences between different storage methods and provide a consistent access experience for upper-layer applications; Each segment of the code is used as a field of the database table and an index is created to enable search using the index.

Images