Real object ID management method and system based on full life cycle, and medium

Abstract

The invention relates to a real object ID management method and system based on a whole life cycle and a medium, and belongs to the field of equipment information statistics, and the method comprises the steps: S1, extracting coded data of each link of the whole life cycle, associating the corresponding coded data with a real object ID, and storing the coded data and the real object ID in a storage library; s2, monitoring the coded data in the database corresponding to all links, and skipping to S3 when the state of the coded data changes; s3, extracting the coded data updated in the step S2; s4, according to the coded data in the S3, searching the associated physical ID in the storage library, and updating the coded data of the data change link corresponding to the physical ID in the storage library; and S5, sending the modified coded data to other links to complete data updating. By monitoring the state and quantity change of the coded data of all links in real time, the real object ID associated data is ensured to be consistent with the actual state of the real object assets at any time.

Description

Technical Field

[0001] The present invention belongs to the field of equipment information statistics, and particularly relates to a physical ID management method, system and medium based on the whole life cycle. Background Art

[0002] The physical ID runs through all stages of the whole life cycle of power grid physical assets, including planning and design, demand planning, tendering and procurement, production manufacturing, product delivery, performance execution, engineering construction, operation and maintenance, and retirement and recycling, and is used to realize the associated sharing of project coding, WBS coding, material coding, asset coding, equipment coding, dispatching coding and waste material coding information in the whole life cycle of assets. The aim is to use the physical ID as a link to realize the interconnection and interoperability of information such as the status, cost, and defects of power grid physical assets in the whole life cycle.

[0003] The construction of physical ID has started nationwide. However, the business matching the physical ID spans multiple business departments such as projects, materials, equipment, and assets, and the relevant data involves multiple information systems such as PMS2.0, ERP, and micro-applications. The functions of the physical ID in different information systems are different.

[0004] In the prior art, ETL (Extract-Transform-Load) is often used to associate different codes of the same equipment with the physical ID in different links. When using ETL technology, data extraction is required. In the prior art, due to the limitations of ETL, data or new data is often scanned and extracted at regular intervals or by external instructions. However, there are problems with data timeliness in the data processing process using the above methods. Regular updates mean that during the interval between two updates, the physical ID-related data may be in an outdated state. For example, if the status of a physical asset changes at a certain moment (such as equipment failure, location change, etc.), but since the regular update time point has not been reached, the ETL process cannot obtain and update this change in a timely manner, resulting in a deviation between the physical ID data in the data warehouse or target storage and the actual situation, and it cannot meet the requirements of businesses with high requirements for real-time data, such as real-time equipment monitoring scenarios. Summary of the Invention

[0005] In view of the problems in the prior art, the present invention provides a physical ID management method, system and medium based on the whole life cycle, which solves the problem that the physical ID-related data may be in an outdated state due to regular updates when using ETL to associate different codes with the physical ID in the prior art, and thus cannot meet the requirements of businesses with high requirements for real-time data, such as real-time equipment monitoring scenarios.

[0006] The technical solution adopted by the present invention is as follows: In a first aspect, the present application provides a physical ID management method based on the entire life cycle. The method includes the following steps: Step S1: Extract the coding data of each link in the entire life cycle, associate the corresponding coding data with the physical ID, and store the coding data and the physical ID in a repository; Step S2: Monitor the coding data in the corresponding databases of all links. When there is a change in the status of the coding data, jump to Step S3; Step S3: Extract the updated coding data generated in Step S2; Step S4: Search for the associated physical ID in the repository according to the coding data in Step S3, and update the coding data of the data change link corresponding to the physical ID in the repository; Step S5: Send the modified coding data to the remaining links to complete the data update.

[0007] Preferably, in Step S1, it includes the following steps: Step S1-1: Extract all fields of the coding data of all links in real time; Step S1-2: Clean the coding data extracted in Step S1-1; Step S1-3: Reconstruct the cleaned coding data according to a single data model; Step S1-4: Associate the coding data reconstructed in Step S1-3 with the physical ID using the physical ID as the key; Step S1-5: Store the reconstructed coding data and the physical ID in a repository.

[0008] Preferably, Step S5 includes the following steps: Step S5-1: Use a data monitoring module to monitor the coding data in the repository; Step S5-2: When a log of newly associated coding data appears in the repository, the data monitoring module starts and parses the newly added log to obtain the data rows that have changed and the type of change in the coding data; Step S5-3: Extract the coding data that has changed in the log; Step S5-4: Search for the associated physical ID in the repository according to the coding data before the change in Step S5-3, and update the coding data of other links corresponding to the physical ID in the repository.

[0009] Preferably, Step S5-2 includes the following steps: Step S5-2-1: When a log of newly associated coding data appears in the repository, the data monitoring module starts and reads from the starting position of the newly added log; Step S5-2-2: After the data monitoring module obtains the data rows that have changed in the log and the types of encoded data changes, it records them and maintains a pointer to the data rows that have changed. When the encoded data status is updated, the data monitoring module generates an update flag. Step S5-2-3: The data monitoring module uses a message queue to transfer the update flag and the corresponding encoded data to the staging repository. Step S5-2-4: Continue to read the data rows that have changed in Step S5-2-2. When there are data changes after the pointer position, jump to Step S5-2-2; otherwise, complete the parsing of the data monitoring module.

[0010] Preferably, in Step S5-3, an extraction method is used to extract all fields of the encoded data in the staging repository.

[0011] Preferably, in Step S4, a hash table search algorithm is used to search in the storage repository for the physical object ID associated with the encoded data extracted in Step S3.

[0012] Preferably, in Step S4, when updating the encoded data corresponding to the physical object ID in the storage repository, historical information of the data update is recorded; the historical information includes the update time, the data before the update, and the data after the update.

[0013] Preferably, in Step S5-4, the encoded data in the storage repository is sent to the corresponding link using a message queue mechanism, and the data is sent to the receiving queue of the corresponding link in the form of a message. After the data update is completed, the corresponding link sends feedback information to the storage repository to confirm the successful reception and update of the data. If no feedback is received within a certain time, a retransmission mechanism is triggered.

[0014] In a second aspect, the present application provides a physical object ID management system based on the whole life cycle, including: A data monitoring module, configured to monitor changes in the encoded data in the database / storage repository and generate change flags. An extraction module, configured to extract the encoded data and perform reconstruction of the encoded data. A storage repository, connected to the extraction module, for storing the encoded data and the physical object ID. A staging repository, connected to the data monitoring module, for temporarily storing the encoded data extracted by the data monitoring module and the generated change flags.

[0015] In a third aspect, the present application provides a medium storing program instructions, and when the program instructions are running, they execute the physical object ID management method based on the whole life cycle as described in the first aspect.

[0016] As can be seen from the above technical solutions, the present invention has the following advantages: By monitoring the status and quantity changes of the encoded data in real time, it is ensured that the physical ID associated data is always consistent with the actual status of the physical assets, enabling precise implementation of operations with high real-time requirements and avoiding decision-making errors caused by data lag. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 It is a flowchart of the method in the embodiment of the specific implementation manner of the present invention.

[0019] Figure 2 It is a flowchart of step S1 in the method in the embodiment of the specific implementation manner of the present invention.

[0020] Figure 3 It is a flowchart of step S5 in the method in the embodiment of the specific implementation manner of the present invention.

[0021] Figure 4 It is a flowchart of step S5-2 in the method in the embodiment of the specific implementation manner of the present invention.

[0022] Figure 5 It is a structural block diagram of the system in the embodiment of the specific implementation manner of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0023] In the following detailed description, various embodiments of the present disclosure will be described more fully. The present disclosure may have various embodiments and adjustments and changes may be made therein. However, it should be understood that there is no intention to limit the various embodiments of the present disclosure to the specific embodiments disclosed herein, but rather the present disclosure should be understood to cover all adjustments, equivalents, and / or alternative solutions falling within the spirit and scope of the various embodiments of the present disclosure.

[0024] In view of the problems in the prior art, the present invention provides a physical ID management method, system, and medium based on the full life cycle, which solves the problem that when using ETL to associate different codes with physical IDs in the prior art, the physical ID-related data may be in an outdated state due to scheduled updates, and thus cannot meet the requirements of operations with high real-time data requirements, such as real-time device monitoring and other scenarios.

[0025] As Figures 1-4 shown, this embodiment provides a physical ID management method based on the full life cycle. The method includes the following steps: Step S1: Extract the coding data in several links, associate the corresponding coding data with the physical ID, and store the coding data and the physical ID in the repository; In this application, a total of nine stages are involved, including planning and design, requirements planning, bidding and procurement, production and manufacturing, product delivery, performance execution, engineering construction, operation and maintenance, and decommissioning and recycling, including project coding, WBS coding, material coding, asset coding, equipment coding, scheduling coding, and waste material coding for realizing the full life cycle of assets.

[0026] Among them, step S1 includes the following steps: Step S1-1: Extract all fields of the coding data in all links in real time; Determine the data source locations corresponding to several links, such as databases in different business links such as the production system database and the logistics link record database involved in these links; According to the pre-set coding data format specification, use database query statements combined with corresponding field extraction functions to extract all fields of the coding data. The coding data is stored in a table in a relational database, and each field corresponds to a column in the table. Specify the column name to extract the corresponding field content, and organize the extracted coding data into a format for subsequent processing, and store each complete coding data record in a list form; Step S1-2: Clean the coding data extracted in step S1-1; Establish a data cleaning rule set, and the rules cover removing duplicate records in the coding data, correcting error characters that do not conform to the coding specification, removing spaces and other irrelevant special symbols, etc.; Use Talend to judge and process the extracted coding data one by one according to the rule set. Adopt a loop traversal method to perform rule matching on each field in each coding data. If it does not conform to the rule, perform corresponding correction or deletion operations, and finally obtain a set of cleaned coding data; Through the set of coding data obtained by cleaning, it is possible to avoid inaccurate analysis results caused by duplicate records and avoid data redundancy; follow specific coding specifications to avoid that error characters may cause decoding failures or incorrect decoding results, ensure data accuracy and improve data consistency; Step S1-3: Reconstruct the cleaned coding data according to a single data model; Design a single data model, clarify the definitions, data types, and logical relationships between each field in the model, and ensure that it can cover all the key information of the coding data that needs to be reconstructed and has a unified structure; Use data restructuring tools or write code logic to perform field mapping and reorganization on the cleaned coded data according to the requirements of a single data model. Fill the similar information stored in different links of the original coded data into the corresponding new field positions according to the new model specifications to complete the data restructuring process; Step S1-4: Use the physical object ID as the key to associate the restructured coded data in Step S1-3 with the physical object ID; Use the physical object ID as the primary key to establish the structure of the association relationship table or reserve fields for associating the physical object ID in the structure storing the coded data. Through programming means, associate and bind each restructured coded data in Step S1-3 with the corresponding physical object ID to form a data set with a clear association relationship; Step S1-5: Store the restructured coded data and the physical object ID in a repository; Configure the connection parameters of the repository, use the corresponding repository operation interface, store the associated restructured coded data and the physical object ID batch by batch or at one time in the corresponding storage location in the repository, and verify the storage results; Step S2: Monitor the coded data in the databases corresponding to all links. When there is a change in the status of the coded data, jump to Step S3; Among them, Step S2 includes the following steps: Step S2-1: Use a data monitoring module to monitor the coded data in the database of each link; In the database system corresponding to each link involving physical object ID management, install and configure a data monitoring module, set parameters such as the range of database tables to be monitored, the monitoring time interval, and the condition threshold for triggering monitoring, and start the data monitoring module to make it run continuously in the background according to the set rules, and monitor the coded data in the corresponding database in real time; Step S2-2: When the log changes in the database of the corresponding link, the data monitoring module starts and parses the changed log to obtain the data rows that have changed and the type of change of the coded data; Step S3: Extract the updated coded data generated in Step S2; Among them, in Step S3, an extraction method is used to extract all fields of the coded data in the staging repository; Use the extraction method mentioned in Step S1-1; According to the format of the coded data stored in the staging repository and the requirements of all predefined fields, use appropriate query statements or reading functions to completely extract all fields of the added or updated coded data in the staging repository, and organize the extracted data into a data set format convenient for subsequent processing; Step S4: Search for the associated physical ID in the repository based on the encoded data in Step S3, and update the encoded data of the data change link corresponding to the physical ID in the repository; In Step S4, the hash table search algorithm is used to search in the repository for the physical ID associated with the encoded data extracted in Step S3; A hash table structure is constructed in the repository, and the stored encoded data and the corresponding physical IDs are organized and stored according to the requirements of the hash algorithm. For the encoded data extracted in Step S3, based on its corresponding key feature field values for hash calculation, the hash table search algorithm is used to quickly locate the position of the physical ID associated with it in the repository, and obtain the corresponding physical ID information; When updating the encoded data of several links corresponding to the physical ID in the repository, record the historical information of the data update; the historical information includes the update time, the data before update, and the data after update; According to the found physical ID, locate the storage position of the encoded data of several links associated with the corresponding physical ID in the repository, and use the corresponding repository update operation to overwrite the original old encoded data with the updated encoded data extracted in Step S3 to complete the data update process. At the same time of the update, obtain the current system time as the update time, record the content of the old data before update and the new data after update, and store this information in the area of the repository specifically used to record the historical information of data update in the specified format; Step S5: Send the encoded data of several links in the repository to the corresponding links to complete the data update; Among them, Step S5 includes the following steps: Step S5-1: Use the data monitoring module to monitor the encoded data in the repository; Step S5-2: When a new log of associated encoded data appears in the repository, the data monitoring module starts and parses the new log to obtain the data rows that have changed and the type of change of the encoded data; Step S5-3: Extract the encoded data that has changed in the log; Adopt the extraction method mentioned in Step S1-1, connect to the corresponding storage position of the staging repository, and configure the corresponding access permissions and connection parameters; Step S5-4: Search for the associated physical ID in the repository based on the encoded data before the change in Step S5-3, and update the encoded data of other links corresponding to the physical ID in the repository.

[0027] Among them, Step S5-2 includes the following steps: Step S5-2-1: When a new log of associated encoded data appears in the repository, the data monitoring module starts and reads from the starting position of the new log; After the data monitoring module is started, according to the log format and storage rules of the monitored database, it locates the starting position of the log, and reads the log content line by line in a predefined order through file reading operations or database query operations, preparing to parse the information related to the changes in the encoded data; Step S5-2-2: After the data monitoring module obtains the data rows that have changed in the log and the types of changes in the encoded data, it records them, and at the same time maintains a pointer to the data row that has changed; When the status of the encoded data is updated, the data monitoring module generates an update flag; During the process of reading the log, using a preset log parsing algorithm, it identifies the data rows that have changed, and at the same time determines the type of change in the encoded data according to the operation type recorded in the log. It records the key information such as the obtained data rows that have changed and the type of change in the encoded data into a dedicated data structure, and maintains a pointer to point to the position of the currently changed data row; When the status of the encoded data is updated, the data monitoring module generates an update flag; when the quantity of the encoded data decreases, the data monitoring module generates a deletion flag; when the quantity of the encoded data increases, the data monitoring module generates a new addition flag; When extracting the encoded data with quantity changes or status changes, the extracted encoded data is cleaned; Step S5-2-3: The data monitoring module uses a message queue to transfer the update flag and the corresponding encoded data to the staging repository; According to the different flags generated by the changes in the encoded data, the corresponding flags and the corresponding encoded data are organized into a message format that meets the requirements of the message queue. The connection information of the message queue is configured, and the organized message is sent to the corresponding message queue of the staging repository, and at the same time, the reliability mechanism for completing the message sending is set; Step S5-2-4: Continue to read the data rows that have changed in Step S5-2-2. When there are data changes after the pointer position, jump to Step S5-2-2; otherwise, complete the parsing of the data monitoring module; If it is found that there are further data changes after the pointer position, jump back to Step S5-2-2 again to obtain, record and maintain the pointer for the new change information; If there are no new data changes subsequently, complete the parsing process of this batch of logs by the data monitoring module; Among them, in Step S5-4, the encoded data in several links in the storage repository is sent to the corresponding link by using a message queue mechanism, and the data is sent to the receiving queue of the corresponding link in the form of a message; Configure a message queue mechanism to determine parameters such as the queue name, queue type, and message format specification for message passing between the repository and the corresponding link. Pack the encoded data of several links in the repository according to the message format requirements, and send these messages to the receiving queue of the corresponding link through the sending interface of the message queue. On the side of the corresponding link, set up a message receiving and processing logic. When receiving a message from the repository, perform message parsing and verification, extract the encoded data, and apply it to the relevant business systems of this link to complete the data update operation; After the corresponding link successfully completes data reception and update, according to the pre-agreed feedback mechanism, send a feedback message to the repository. On the repository side, set up a feedback message receiving and processing module to parse and judge the feedback information. If the feedback message is not received within the specified time, trigger the retransmission mechanism.

[0028] As Figure 5 shown, in this embodiment, a physical ID management system based on the whole life cycle is also provided, including: A data monitoring module for monitoring the changes in the encoded data in the database / repository and generating change marks; Build the operating environment of the data monitoring module, including establishing stable connection channels with the databases of each link, configuring its own operating parameters, and initializing the internal data structure for recording the changes in the monitoring data. Implement the specific monitoring logic, and monitor the changes in the encoded data in real time by regularly querying the database logs and comparing the data status. According to relevant requirements, perform operations such as generating change marks for the changed data, recording information, and transmitting relevant data to the staging repository through the message queue, and provide a monitoring status query interface externally; An extraction module for extracting the encoded data and reconstructing the encoded data; Build the program architecture of the extraction module, which internally includes different functional units such as a data source connection management sub-module, a data extraction sub-module, a data cleaning sub-module, and a data reconstruction sub-module. These units work together through reasonable interfaces and data transfer methods, and provide a unified extraction interface externally. Other system components can call this interface, pass in the corresponding parameters to trigger a series of operations such as extraction, cleaning, and reconstruction of the encoded data by the extraction module, and return the associated result of the processed encoded data and the physical ID; A repository, connected to the extraction module, for storing the encoded data and the physical ID; According to business requirements and data volume estimates, select appropriate storage technologies and architectures as the underlying implementation of the repository, design the data table structure or the logical structure for storing data in the repository, define the storage fields, table relationships or storage paths, formats, etc. for related data such as encoded data, physical IDs, and data update history information, and develop corresponding repository operation interfaces for other modules to call to implement read, write, and management operations on the data in the repository; A staging repository, connected to the data monitoring module, is used to stage the encoded data extracted by the data monitoring module and the generated change markers; Determine the storage method of the staging repository. For the data transmitted through the message queue, design the corresponding parsing and storage logic, store different types of data in different areas of the staging repository, and at the same time provide management interfaces such as querying and cleaning the staged data to facilitate the processing of the data in the staging repository in subsequent steps.

[0029] In this embodiment, a medium is also provided, storing program instructions that, when running, execute the physical ID management method based on the entire life cycle as described above.

[0030] It can be understood that the systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver device, a game console, a tablet computer, a wearable device, or a combination of any several of these devices.

[0031] In a typical configuration, a computer includes one or more processors (CPUs), an input / output interface, a network interface, and a memory.

[0032] The memory may include non-permanent memory in the computer-readable medium, random access memory (RAM), and / or non-volatile memory in the form of, for example, read-only memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.

[0033] A computer-readable medium includes permanent and non-permanent, removable and non-removable media that can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassette tapes, disk storage, quantum memory, graphene-based storage media, or other magnetic storage devices, or any other non-transitory media that can be used to store information accessible by a computing device. As defined herein, computer-readable media do not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0034] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been authorized by the user or fully authorized by all parties. Moreover, the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or reject.

[0035] It should also be noted that the term "comprising", "including", or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a series of elements includes not only those elements but also other elements not expressly listed, or elements that are inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0036] The specific embodiments of this specification have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0037] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a", "the", and "said" used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0038] It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining".

[0039] The above description is only the preferred embodiment of one or more embodiments of this specification and is not intended to limit one or more embodiments of this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of one or more embodiments of this specification shall be included within the scope of protection of one or more embodiments of this specification.

Claims

1. A physical ID management method based on the whole life cycle, characterized in that, The method includes the following steps: Step S1: Extract the coding data of each link in the whole life cycle, associate the corresponding coding data with the physical ID, and then store the coding data and the physical ID in the repository; Step S2: Monitor the coding data in the corresponding database of all links. When there is a change in the status of the coding data, jump to Step S3; Step S3: Extract the updated coding data generated in Step S2; Step S4: Search for the associated physical ID in the repository according to the coding data in Step S3, and update the coding data of the data change link corresponding to the physical ID in the repository; Step S5: Send the modified coding data to the remaining links to complete the data update.

2. The physical ID management method based on the whole life cycle according to claim 1, wherein In Step S1, it includes the following steps: Step S1-1: Extract all fields of the coding data of all links in real time; Step S1-2: Clean the coding data extracted in Step S1-1; Step S1-3: Reconstruct the cleaned coding data according to a single data model; Step S1-4: Use the physical ID as the key to associate the reconstructed coding data in Step S1-3 with the physical ID; Step S1-5: Store the reconstructed coding data and the physical ID in the repository.

3. The method for managing physical ID based on the whole life cycle according to claim 1, characterized in that In Step S5, it includes the following steps: Step S5-1: Use the data monitoring module to monitor the coding data in the repository; Step S5-2: When a new log of associated coding data is added to the repository, the data monitoring module starts and parses the new log to obtain the changed data rows and the type of coding data change; Step S5-3: Extract the coding data that has changed in the log; Step S5-4: Search for the associated physical ID in the repository according to the coding data before the change in Step S5-3, and update the coding data of other links corresponding to the physical ID in the repository.

4. The method for managing physical ID based on the whole life cycle according to claim 3, wherein, In Step S5-2, it includes the following steps: Step S5-2-1: When a new log of associated coding data is added to the repository, the data monitoring module starts and reads from the starting position of the new log; Step S5-2-2: After the data monitoring module obtains the changed data rows and the type of coding data change in the log, it records them and maintains the pointer to the changed data row at the same time; When the status of the coding data is updated, the data monitoring module generates an update flag; Step S5-2-3: The data monitoring module uses a message queue to transfer the update flag and the corresponding coding data to the staging repository; Step S5-2-4: Continue to read the data rows that have changed in Step S5-2-2. When there is data change after the pointer position, jump to Step S5-2-2, otherwise complete the parsing of the data monitoring module.

5. The physical ID management method based on the whole life cycle according to claim 4, characterized in that In Step S5-3, an extraction method is used to extract all fields of the coding data in the staging repository.

6. The physical ID management method based on the whole life cycle according to claim 1, characterized in that In Step S4, a hash table search algorithm is used to search in the repository for the physical ID associated with the coding data extracted in Step S3.

7. The method for managing physical ID based on the whole life cycle according to claim 1, wherein In Step S4, when updating the coding data of the link corresponding to the physical ID in the repository, record the historical information of the data update; the historical information includes the update time, the data before the update, and the data after the update.

8. The physical ID management method based on the whole life cycle according to claim 1, characterized in that In step S5-4, the encoded data in the repository is sent to the corresponding link by using a message queue mechanism, and the data is sent to the receiving queue of the corresponding link in the form of a message; After the data update is completed, the corresponding link sends feedback information to the repository to confirm the successful reception and update of the data. If no feedback is received within a certain period of time, a retransmission mechanism is triggered.

9. An in-kind ID management system based on the whole life cycle, characterized in that, including: A data monitoring module for monitoring the change of encoded data in the database / repository and generating a change flag; An extraction module for extracting encoded data and reconstructing the encoded data; A repository, connected to the extraction module, for storing encoded data and physical IDs; A staging repository, connected to the data monitoring module, for staging the encoded data extracted by the data monitoring module and the generated change flags.

10. A medium, characterized in that, Stored with program instructions, the program instructions, when running, execute the physical ID management method based on the entire life cycle according to any one of claims 1 to 8.

Images