Label management method for information system modeling
Through the label management method, the attributes and steps of the product and process are abstracted into independent label modules, which solves the problem that traditional information system development methods are difficult to adapt to rapidly changing needs, realizes flexible and efficient modeling and adjustment of the information system, and improves production efficiency.
Patent Information
- Application Number
- CN202411540499.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-31
- Publication Date
- 2025-02-28
AI Technical Summary
Traditional information system development methods are difficult to adapt to the rapidly changing product parameters and process requirements in wheel manufacturing, resulting in complex development and maintenance, lack of dynamic adjustment capabilities, and affecting production flexibility and efficiency.
The label management method is adopted to abstract the attributes and steps of the product and process into independent label modules. Developers define these labels during the development period and dynamically combine them on demand during the run period to achieve flexible and efficient system modeling and adjustment.
Through label management technology, information systems can quickly respond to changes, reduce development and maintenance costs, improve production efficiency, and are suitable for complex and dynamically changing scenarios.
Smart Images
Figure CN119537488A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of software development, and more specifically, the present invention relates to a tag management method for information system modeling. Background Art
[0002] Wheel manufacturing covers many complex links from raw material selection, heat treatment, quenching, slow cooling, rough machining, fine machining, painting, shot peening to packaging. The process combination of each order may be different, and the parameter types of each category of wheel products are not the same. The parameter types in the processes corresponding to the products are not exactly the same. It is difficult for developers to describe all products and processes in a unified way, and the development and maintenance of information systems is extremely complex.
[0003] In the traditional development mode, developers need to independently model each wheel product and its process route, and statically set each attribute and the logical relationship between attributes. Once new product parameters or process changes appear, a large number of code modifications and reconfigurations need to be made within the information system, which is time-consuming and error-prone, and difficult to adapt to rapidly changing needs. In addition, the static development model cannot flexibly respond to resource scheduling and process combinations, and the information system lacks dynamic adjustment capabilities during operation. Some parameters and functions that have been implemented on one part of the product cannot be directly transplanted to another part of the product, which greatly affects the flexibility and efficiency of production.
[0004] In terms of data management, the traditional method designs storage structures for different processes and product models separately, which leads to inconsistent data operations and complex development and maintenance. In particular, the system responds slowly during high-frequency changes, making it difficult to support flexible production needs. Summary of the invention
[0005] The present invention provides a tag management method for information system modeling, aiming to improve the above-mentioned problem.
[0006] The present invention is implemented as follows: a tag management method for information system modeling, the method is specifically as follows:
[0007] Tag storage: Store products and their tags in the namespace corresponding to the tag source;
[0008] Reading of labels: Input the target label ID, and traverse each namespace in descending order of priority. After finding the target label ID, read the corresponding label data and stop traversal.
[0009] A product has at least one tag, the signature identifier is used to identify the corresponding signature, and the tag data is used to describe the behavior of the product.
[0010] Furthermore, there are basic tags and compound tags in the tag set of each namespace. The compound tag is a sequential combination of multiple basic tags in the tag set. One basic tag corresponds to one behavior, and one compound tag is a processing technology composed of a sequential combination of multiple behaviors.
[0011] Furthermore, each namespace corresponds to a read cache space, and the read cache space of each namespace is connected to the persistent storage space; wherein, the read cache space uses a hash algorithm to obtain the tag key-value pair of the tag data written into the persistent storage space, parses the tag key-value pair read from the persistent storage space, and obtains the tag data. The persistent storage space is used to store the tag key-value pair of the tag.
[0012] Furthermore, the target label identifier is searched in sequence according to the cache space and the namespace.
[0013] Furthermore, the priority of the corresponding namespace is defined in the attributes of each namespace. The tag reading process in the namespace is as follows:
[0014] Sort all namespaces in order of priority from high to low;
[0015] Start traversing from the namespace with the highest priority to check whether the target tag key exists in the current namespace. If not, use the next namespace as the current namespace. If so, output the target tag value of the target tag key in the current namespace, put the target tag value into the cache space of the current namespace, and stop the search process.
[0016] Furthermore, the tag writing process is as follows:
[0017] The operating user issues a tag writing request, which carries the requested product ID and tag ID, and uses the tag ID as the tag key;
[0018] Obtain the operation user ID to determine the corresponding namespace ID;
[0019] Check whether the operation permission of the user requesting the operation exists write permission. If so, put the requested product ID, namespace ID, tag key and corresponding tag value into the data cache space, and store the requested product ID, tag key and corresponding tag value into the namespace corresponding to the namespace ID.
[0020] Furthermore, the current state of the data cache space is periodically checked to determine whether the conditions for the batch write operation are currently met. If so, the current batch write operation is triggered, and the time when the current batch write operation is triggered is recorded;
[0021] If the number of tags in the data cache space reaches a set threshold, or the time interval detection from the last batch write operation to the current one exceeds the set time interval, it is determined that the conditions for the batch write operation are currently met.
[0022] Furthermore, when performing batch write operations, the tag key-value pairs of each tag are written to the persistent storage space in turn, the product identifier, namespace identifier and tag key of the tag to be written are obtained, and a check is made in the persistent storage space whether there is a tag value in the persistent storage space that is the same as the product identifier, namespace identifier and tag key value of the tag to be written. If so, the corresponding tag value in the persistent storage space is deleted, and the tag value of the tag to be written is written to realize the tag update in the persistent storage space.
[0023] Furthermore, when performing batch write operations, the tag key-value pairs of each tag are written into the corresponding namespace in turn, the product identifier, namespace identifier and tag key of the current tag to be written are obtained, and a search is conducted in the corresponding namespace to determine whether there is a tag value that is the same as the product identifier and tag key value of the tag to be written. If so, the corresponding tag value in the namespace is deleted, and the tag value of the current tag to be written is written to implement the tag update within the namespace.
[0024] Furthermore, the tag deletion operation is as follows:
[0025] The operating user sends a tag deletion request, which carries the requested product ID and tag ID. It checks whether the requesting operating user has the deletion permission in his operating permissions. If so, the namespace ID corresponding to the operating user is determined, and the tag data corresponding to the requested product ID and tag ID are deleted in the corresponding namespace. At the same time, the deletion request and its corresponding namespace ID are sent to the request cache space to determine in real time whether the conditions for the batch deletion operation are currently met. If so, the current batch deletion operation is triggered, and the time when the batch deletion operation is triggered is recorded. The corresponding tags in the persistent storage space are deleted in turn based on the product ID, tag ID and namespace ID of each deletion request.
[0026] The tag management method for information system modeling provided by the present invention has the following beneficial effects:
[0027] The present invention greatly improves the complexity problem in information system modeling by adopting tag management technology. Tag management abstracts the attributes and steps of products and processes into independent tag modules. Developers define these tags during the development period and dynamically combine them as needed during the operation period to achieve flexible and efficient system modeling and adjustment. For the diversified needs in wheel manufacturing, the information system can dynamically configure the process flow and parameters by combining the corresponding tag modules, so as to quickly respond to changes, reduce development and maintenance costs, and improve production efficiency.
[0028] In addition, tag management technology is applicable to all types of information system modeling, not limited to wheel manufacturing or PDM system modeling; it is a general modeling method that can be applied to various complex and dynamically changing scenarios through flexible combination of tag modules, thus achieving efficient development, operation and maintenance of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Figure 1 A flowchart of a product label management method for information system modeling provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0030] The specific implementation modes of the present invention are further explained in detail below by describing the embodiments with reference to the accompanying drawings, so as to help those skilled in the art to have a more complete, accurate and in-depth understanding of the inventive concept and technical solution of the present invention.
[0031] Flags describe the management system for managing complex products, dynamically storing and managing product tags at runtime, and adjusting product behaviors or actions based on tag changes. Figure 1 A flowchart of a product label management method for information system modeling provided by an embodiment of the present invention, the method is specifically as follows:
[0032] Tag storage: Store products and their tags in the namespace corresponding to the tag source;
[0033] Reading of labels: Enter the target label identifier, and traverse each namespace in order of priority from high to low. After finding the target label identifier, read the corresponding label data and stop traversal.
[0034] A product has at least one tag, where the tag data is used to describe the behavior of the product.
[0035] (1) Storage of tags;
[0036] In an embodiment of the present invention, the namespace mapping table is implemented by a hash table (Hash Map), using the name of the namespace as the key and the tag set as the value. Each namespace contains a tag set, which stores tags from a specified source. The tag sources include: system default tags and user-defined tags, wherein tags of different user roles or different users belong to tags from different sources.
[0037] The tag namespace mapping table is implemented through a hash map. The key is the tag identifier, called the tag key, and the value is the tag data and tag status, called the tag value. The tag key and tag value form a tag key-value pair. To improve performance, the tag value is accompanied by the tag status, including: the generation timestamp of the tag data, etc.
[0038] To enhance the flexibility of the structure, a mechanism for managing metadata is added to the namespace attributes, including the namespace priority and validity period. The introduction of priority ensures that the system makes efficient decisions when dealing with conflicts, and the validity period enables the system to automatically clean up and recycle obsolete or invalid namespaces, thereby maintaining optimal utilization of system resources.
[0039] In an embodiment of the present invention, there are basic tags in the tag set of each namespace, and there may be composite tags. The composite tag is a combination of multiple basic tags in the tag set. One basic tag corresponds to one behavior, and a composite tag is a process composed of multiple behaviors combined in sequence. Taking the processing technology of the wheel as an example, the rough processing of the wheel is a basic tag, and the fine processing of the wheel is a basic tag. The rough processing and fine processing of the wheel are combined to form a composite tag of the wheel processing technology.
[0040] To address the performance issues of high-frequency read and write scenarios, a read cache space is set up for each namespace. The read cache space of each namespace is connected to the persistent storage space. The read cache space uses a hash algorithm to obtain the key-value pair of the tag data written to the persistent storage space, and then puts it into the persistent storage space to parse the key-value pair of the tag read from the persistent storage space to obtain the tag data. The persistent storage space is a database or file system, etc., which is used to store tag key-value pairs. The cache space is used to cache the most recently read tags. Based on the access frequency of the tags, the cache space is divided into a short-term cache area and a medium-term cache area. Tags with low access frequency are cached in the short-term cache area, and tags with high access frequency are cached in the medium-term cache area. It should be noted that the system pre-defined default space has no persistent storage area. Combined with the batch write mechanism, this hierarchical storage strategy effectively reduces the impact of high-frequency operations on system performance, especially in large event-driven systems, ensuring that the system can still maintain good response speed and stability under high load.
[0041] (2) Tag reading;
[0042] In the embodiment of the present invention, the tag reading process in the namespace is specifically as follows:
[0043] (21) Sort all namespaces in order of priority from high to low;
[0044] (22) Start traversing from the namespace with the highest priority to check whether the target tag key exists in the current namespace. If not, use the next namespace as the current namespace. If so, output the target tag value of the target tag key in the current namespace, put the target tag value into the cache space of the current namespace, and stop the search process.
[0045] In the tag reading operation, namespace priority sorting is the core step to ensure correct handling of tag conflicts and fast search. The priority sorting algorithm is used to ensure that the namespace is searched in the optimal order when reading tags, thereby ensuring that high-priority tags can be accessed quickly.
[0046] At the beginning of each tag reading operation, all relevant namespaces are first obtained and sorted according to their priorities. Priority sorting ensures that tag keys found in high-priority namespaces are used first, without wasting resources on additional searches in low-priority namespaces. Conflict handling is a key issue in priority management. When the same tag key exists in multiple namespaces, the tag value in which namespace is adopted will be determined based on the priority order. Specifically, when a conflict occurs, the tag value in the namespace with the highest priority will be used first, and the same tag in the lower-priority namespace will be ignored. This mechanism not only ensures the consistency of the system, but also provides flexibility. Developers or administrators can control the actual order in which tags take effect by adjusting the priority of the namespace.
[0047] Through this priority sorting mechanism and conflict handling rules, the system can efficiently manage the tag search process in multiple namespaces, ensuring that it can always provide fast response and accurate data processing capabilities in complex dynamic event environments.
[0048] In an embodiment of the present invention, when searching for the target tag key in the namespace, the search is performed in the order of the cache space and the namespace, starting from the cache space to search for the target tag key to ensure that the delay can be minimized to the greatest extent in frequent access scenarios. If the cache space hits, that is, the target tag key already exists in the cache space, the corresponding value in the cache space is directly returned, eliminating the further search process. If the cache space does not hit, the namespace is entered to query and read the target tag key. The specific query method is as described above.
[0049] When the operating user issues a tag read or write request, it is first detected whether there is read permission in the operating permissions of the requesting operating user. If so, the above reading process is executed. The operating permissions include: read permission, write permission and delete permission.
[0050] (3) Writing of labels;
[0051] The operating user issues a tag write request, which carries the requested product ID and tag ID, and uses the tag ID as the tag key; obtains the operating user ID to determine the corresponding namespace ID; detects whether the operating permissions of the requesting operating user have write permissions, and if so, puts the requested product ID, namespace ID, tag key and corresponding tag value into the data cache space, and records the current timestamp, which is the generation timestamp in the status information; at the same time, stores the requested product ID, tag key and corresponding tag value into the namespace corresponding to the namespace ID.
[0052] The tag data is first temporarily stored in the data cache space, and time information is also provided for the trigger mechanism of batch processing, so that the batch write operation can be determined according to the time interval, and the tag key-value pairs in the data cache space are written to the persistent storage space and its corresponding namespace.
[0053] Periodically check the status of the data cache space to determine whether the conditions for batch write operations are currently met. If the number of tags in the data cache space reaches the set threshold, or the time interval from the last batch write operation to the current detection exceeds the set time interval, the current batch write operation is triggered and the time when the current batch write operation is triggered is recorded.
[0054] Once a batch write operation is triggered, all tag key-value pairs in the data cache space are written to the corresponding persistent storage space. The batch write method can greatly reduce the overhead caused by frequent small-scale writes. After the write is completed, the tag data in the persistent storage space will be cleared.
[0055] When performing batch write operations, write the tag key-value pairs of each tag into the persistent storage space in turn, obtain the product identifier, namespace identifier and tag key of the current tag to be written, check whether there is a tag value in the persistent storage space that is the same as the product identifier, namespace identifier and tag key value of the tag to be written. If so, delete the corresponding tag value in the persistent storage space, write the tag value of the current tag to be written, implement the tag update in the persistent storage space, and record the current timestamp. If not, directly write the product identifier, namespace identifier, tag key and tag value of the current tag to be written into the persistent storage space.
[0056] When performing batch write operations, write the tag key-value pairs of each tag into the corresponding namespace in turn, obtain the product ID, namespace ID and tag key of the current tag to be written, and search in the corresponding namespace to see whether there is a tag value with the same product ID and tag key value as the tag to be written. If so, delete the corresponding tag value in the namespace, write the tag value of the current tag to be written, implement the tag update in the namespace, and record the current timestamp. If not, write the product ID, tag key and tag value of the tag to be written into the namespace corresponding to the namespace ID.
[0057] In an embodiment of the present invention, after a batch write operation is triggered, log information of the batch write operation is recorded, including: the identity of the operator, the operation timestamp, the corresponding namespace, the tag key-value pair, etc. The preservation of the log not only helps in future system audits, but also provides a basis for rollback operations in the event of a failure, thereby ensuring the stability and maintainability of the system.
[0058] (5) Deletion of labels;
[0059] The operating user sends a tag deletion request, which carries the requested product ID and tag ID. It is detected whether the requesting operating user has the deletion permission in his / her operation permissions. If so, the namespace ID corresponding to the operating user is determined, and the tag data corresponding to the requested product ID and tag ID are deleted in the corresponding namespace.
[0060] At the same time, the deletion request and its corresponding namespace identifier are sent to the request cache space to determine in real time whether the conditions for the batch deletion operation are met. If the number of deletion requests in the request cache space reaches the set threshold, or the time interval detection from the last batch deletion operation to the current one exceeds the set time interval, the current batch deletion operation is triggered, and the time when the batch deletion operation is triggered is recorded. The corresponding tags in the persistent storage space are deleted in turn based on the product identifier, tag identifier and namespace identifier of each deletion request.
[0061] In the embodiment of the present invention, after restarting, the namespace reads the tag from the persistent storage space, and during operation, the user reads the tag from the namespace in real time.
[0062] The tag management method for information system modeling provided by the present invention has the following beneficial effects:
[0063] 1) Improved information system performance: By introducing a cache mechanism and batch processing of mark write operations, the system resource consumption during high-frequency reading and writing is reduced, thereby improving the system response speed and processing efficiency, which is particularly suitable for systems with high performance requirements.
[0064] 2) Enhanced information system scalability: Through priority management and namespace mechanisms, the present invention allows dynamic management and adjustment of tags for different objects in different scenarios, making system functions more flexible and supporting complex and changing business needs.
[0065] 3) Improve the maintainability of information systems: Through tag dependency management and conflict detection functions, the dependency and conflict problems between tags are effectively solved, improving the overall maintainability of the system.
[0066] 4) Improved information system security and stability: Through a strict permission control mechanism, only authorized users can modify tags, all modification operations will be logged, and the system also provides a rollback mechanism to ensure that it can quickly recover to a safe state when an error occurs, thereby ensuring the stable operation of the system.
[0067] The present invention has been described exemplarily. Obviously, the specific implementation of the present invention is not limited to the above-mentioned method. As long as various non-substantial improvements are made using the method concept and technical solution of the present invention, or the concept and technical solution of the present invention are directly applied to other occasions without improvement, they are all within the protection scope of the present invention.
Claims
1. A tag management method for information system modeling, characterized in that: The method is specifically as follows: Tag storage: Store products and their tags in the namespace corresponding to the tag source; Reading of labels: Input the target label ID, and traverse each namespace in descending order of priority. After finding the target label ID, read the corresponding label data and stop traversal. A product has at least one tag, the signature identifier is used to identify the corresponding signature, and the tag data is used to describe the behavior of the product.
2. The tag management method for information system modeling according to claim 1, characterized in that: There are basic tags and compound tags in the tag set of each namespace. A compound tag is a combination of multiple basic tags in the tag set. One basic tag corresponds to one behavior, and a compound tag is a processing technology composed of a combination of multiple behaviors.
3. The tag management method for information system modeling according to claim 1, characterized in that: Each namespace corresponds to a read cache space, and the read cache space of each namespace is connected to the persistent storage space; the read cache space uses a hash algorithm to obtain the tag key-value pair of the tag data written into the persistent storage space, and parses the tag key-value pair read from the persistent storage space to obtain the tag data. The persistent storage space is used to store the tag key-value pair of the tag.
4. The tag management method for information system modeling according to claim 1, characterized in that: Search for the target label identifier in the order of cache space and namespace.
5. The tag management method for information system modeling according to claim 4, characterized in that: The tag reading process in the namespace is as follows: Sort all namespaces in order of priority from high to low; Start traversing from the namespace with the highest priority to check whether the target tag key exists in the current namespace. If not, use the next namespace as the current namespace. If so, output the target tag value of the target tag key in the current namespace, put the target tag value into the cache space of the current namespace, and stop the search process.
6. The tag management method for information system modeling according to claim 1, characterized in that: The tag writing process is as follows: The operating user issues a tag writing request, which carries the requested product ID and tag ID, and uses the tag ID as the tag key; Obtain the operation user ID to determine the corresponding namespace ID; Check whether the operation permission of the user requesting the operation exists write permission. If so, put the requested product ID, namespace ID, tag key and corresponding tag value into the data cache space, and store the requested product ID, tag key and corresponding tag value into the namespace corresponding to the namespace ID.
7. The tag management method for information system modeling according to claim 6, characterized in that: Periodically check the current state of the data cache space to determine whether the conditions for the batch write operation are met. If so, trigger the current batch write operation and record the time when the batch write operation is triggered. If the number of tags in the data cache space reaches a set threshold, or the time interval detection from the last batch write operation to the current one exceeds the set time interval, it is determined that the conditions for the batch write operation are currently met.
8. The tag management method for information system modeling according to claim 6 or 7, characterized in that: When performing batch write operations, write the tag key-value pairs of each tag to the persistent storage space in turn, obtain the product identifier, namespace identifier and tag key of the tag to be written, and check whether there is a tag value in the persistent storage space that is the same as the product identifier, namespace identifier and tag key value of the tag to be written. If so, delete the corresponding tag value in the persistent storage space, write the tag value of the tag to be written, and implement the tag update in the persistent storage space.
9. The tag management method for information system modeling according to claim 6 or 7, characterized in that: When performing batch write operations, write the tag key-value pairs of each tag into the corresponding namespace in turn, obtain the product ID, namespace ID and tag key of the tag to be written, and search in the corresponding namespace to see whether there is a tag value with the same product ID and tag key value as the tag to be written. If so, delete the corresponding tag value in the namespace and write the tag value of the tag to be written to implement the tag update in the namespace.
10. The tag management method for information system modeling according to claim 1, characterized in that: The specific operations for deleting a tag are as follows: The operating user sends a tag deletion request, which carries the requested product ID and tag ID. It checks whether the requesting operating user has the deletion permission in his operating permissions. If so, the namespace ID corresponding to the operating user is determined, and the tag data corresponding to the requested product ID and tag ID are deleted in the corresponding namespace. At the same time, the deletion request and its corresponding namespace ID are sent to the request cache space to determine in real time whether the conditions for the batch deletion operation are currently met. If so, the current batch deletion operation is triggered, and the time when the batch deletion operation is triggered is recorded. The corresponding tags in the persistent storage space are deleted in turn based on the product ID, tag ID and namespace ID of each deletion request.