Interface control file management method and system
The ICD management system with remote and local nodes ensures comprehensive tracking of ICD information versions and modifications, addressing the limitations of centralized management by recording and tracing all changes across the project.
Patent Information
- Application Number
- CN202111517692.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-13
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2041-12-13
AI Technical Summary
Centralized ICD management methods fail to trace all versions and modification information during the product development process.
An ICD management system with an ICD remote node and at least two ICD local nodes, where each local node generates a version identifier for local changes and sends them to the remote node, enabling the remote node to store and trace all ICD information versions across the project.
Enables comprehensive tracking of all ICD information modifications and versions, improving the management and coordination of interface control documents throughout the R&D lifecycle.
Smart Images

Figure CN114185586B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of information management, and in particular relates to an interface control file management method and system. Background Art
[0002] An Interface Control Document (ICD) is a formal description of the methods and structures involved in providing input and receiving output for a specific system. The system described by the interface control document can be a software library or hardware.
[0003] In some application scenarios, the use of ICD information may run through the entire R&D life cycle of the product, going through multiple stages including system requirement analysis, system design, subsystem implementation, semi-physical simulation testing, full system testing, and field testing. The product's ICD information will also be gradually improved and finalized as the product is used.
[0004] In the related art, one ICD management method is a centralized management method, in which the main R&D unit of the product designs the ICD, and then exports the file to the R&D subsystem unit or test unit of the product. If the R&D subsystem unit or test unit finds a problem, it will feedback to the main R&D unit through a coordination sheet or file. The main R&D unit then imports the file into the centralized ICD database to manage the ICD information. This centralized management method cannot trace all versions of ICD information and modification information during the product development process. Summary of the invention
[0005] In view of this, the purpose of the present invention is to provide an interface control file management method and system to solve the problem that the centralized ICD management method in the related art cannot trace all the modification information of the ICD. The technical solution provided by the present invention is as follows:
[0006] In a first aspect, the present invention provides an interface control file management method, which is applied to an interface control file ICD management system, wherein the ICD management system includes an ICD remote node and at least two ICD local nodes, wherein the ICD remote node maintains ICD information corresponding to all devices in the project, and the ICD local node maintains ICD information corresponding to some devices in the project, wherein the method includes:
[0007] The ICD local node acquires ICD information of a device matching the ICD local node;
[0008] The ICD local node generates a different first version identifier for each local ICD information change;
[0009] Each of the ICD local nodes sends each version of local ICD information to the ICD remote node;
[0010] The ICD remote node stores each version of ICD information corresponding to each device in the project.
[0011] In a possible implementation manner of the first aspect, the ICD local node generates a different first version identifier for each locally changed ICD information, including:
[0012] The ICD local node records at least one ICD information corresponding to each change, and generates a first version identifier for the at least one ICD information based on the information of the ICD remote node and the ICD local node, and the ICD current version information of the local ICD local node;
[0013] The current version information of the ICD is updated to the version information corresponding to the first version identifier.
[0014] In another possible implementation manner of the first aspect, the method further includes:
[0015] The ICD remote node generates ICD information corresponding to all devices in the project and generates a globally unique identifier for each ICD information;
[0016] The ICD remote node generates a different second version identifier for each changed ICD information.
[0017] In another possible implementation manner of the first aspect, the ICD remote node generates a different second version identifier for each changed ICD information, including:
[0018] The ICD remote node generates a second version identifier for at least one ICD information of this change based on the information of the ICD remote node and the local ICD current version information of the ICD remote node.
[0019] In another possible implementation manner of the first aspect, the ICD local node acquires ICD information of a device matching the ICD local node, including:
[0020] The ICD local node obtains the latest remote ICD information of the ICD local node maintenance device from the ICD remote node, or the latest remote ICD information and remote historical ICD information;
[0021] Among them, the latest remote ICD information is the latest version of ICD information in the ICD remote node corresponding to the ICD local node maintenance device, and the remote historical ICD information includes all versions of ICD information before the latest version corresponding to the ICD local node maintenance device.
[0022] In another possible implementation manner of the first aspect, the ICD local node obtains the latest remote ICD information and remote historical ICD information of the ICD local node maintenance device from the ICD remote node; the method further includes:
[0023] The ICD local node generates a third version identifier corresponding to each remote historical ICD information based on the second version identifier corresponding to each remote historical ICD information and the time information of receiving the remote historical ICD information, and records each remote historical ICD information and the corresponding third version identifier.
[0024] In another possible implementation manner of the first aspect, the method further includes: merging the local ICD information in the ICD local node with the latest remote ICD information corresponding to the ICD local node stored in the ICD remote node.
[0025] In another possible implementation manner of the first aspect, the merging the local ICD information in the ICD local node with the latest remote ICD information corresponding to the ICD local node stored in the ICD remote node includes:
[0026] The ICD local node obtains the latest remote ICD information corresponding to the ICD local node from the ICD remote node;
[0027] For any of the latest remote ICD information, the ICD local node queries the ICD local node for the latest local ICD information having the same global unique identifier as any of the latest remote ICD information;
[0028] The ICD local node modifies the latest local ICD information based on the latest remote ICD information to obtain merged ICD information;
[0029] The ICD local node sends the merged ICD information and all local historical ICD information in the ICD local node to the ICD remote node.
[0030] In another possible implementation manner of the first aspect, the merging the local ICD information in the ICD local node with the latest remote ICD information corresponding to the ICD local node stored in the ICD remote node includes:
[0031] The ICD remote node receives the latest local ICD information and local historical ICD information sent by the ICD local node;
[0032] For any piece of latest local ICD information, the ICD remote node queries the ICD remote node for the latest remote ICD information having the same global unique identifier as the any piece of latest local ICD information;
[0033] The ICD remote node modifies the latest local ICD information based on the latest remote ICD information to obtain merged ICD information;
[0034] The ICD remote node stores the local historical ICD information.
[0035] In a second aspect, the present invention further provides an interface control file management system, comprising: an interface control file ICD remote node and at least two ICD local nodes, wherein the ICD remote node maintains ICD information corresponding to all devices of the project, and the ICD local node maintains ICD information corresponding to some devices of the project;
[0036] The ICD remote node and at least two ICD local nodes are used to execute the interface control file management method described in any one of the first aspects above.
[0037] An interface control file management method provided by the present invention is applied to an ICD management system, which includes an ICD remote node and at least two ICD local nodes, wherein the ICD remote node is used to maintain the ICD information corresponding to all devices in the project, and the ICD local node maintains the ICD information corresponding to some devices in the project. The ICD local node generates a different first version identifier for each local change in the ICD information, and sends each version of the ICD information to the ICD remote node. Thereby, the ICD remote node stores each version of the ICD information of each device in the project. It can be seen from the above process that the ICD local node will generate a corresponding first version identification record for each ICD information change and send it to the ICD remote node. It can be seen that the ICD remote node records all modification information of the ICD information of all devices, that is, it realizes the tracing of all modification information of all versions of ICD of all devices in the project. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0039] Figure 1 is a structural block diagram of an ICD management system provided by an embodiment of the present invention;
[0040] Figure 2 is a flow chart of an ICD management method provided by an embodiment of the present invention;
[0041] Figure 3 is a flow chart of another ICD management method provided by an embodiment of the present invention;
[0042] Figure 4 is a flow chart of an ICD merging process provided by an embodiment of the present invention;
[0043] Figure 5 It is a flow chart of an ICD merging process provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0044] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0045] See also Figure 1 , shows a structural block diagram of an ICD management system provided by an embodiment of the present invention, the system includes at least one ICD remote node 1 and at least two ICD local nodes 2.
[0046] Each ICD local node 2 can be directly connected to the ICD remote node 1 for information exchange.
[0047] ICD remote node 1 is responsible for maintaining the ICD information corresponding to all devices in the project, and ICD local node 2 is responsible for maintaining the ICD information corresponding to some devices.
[0048] For example, the same project includes 10 subsystems, each of which may include at least one device. Each subsystem is provided with an ICD local node 2, that is, each ICD local node 2 maintains all ICD information of at least one device.
[0049] The ICD remote node performs ICD entry and obtains the ICD information corresponding to all devices in the entire project. Each device corresponds to a set of ICD information. The ICD remote node distributes the ICD information corresponding to each subsystem to the ICD local node corresponding to each subsystem.
[0050] The entered ICD information includes the design requirements of the ICD and other constraint information. For example, the ICD information includes the system name, subsystem name, device name, bus name under the device, configuration information of each bus, domain definition information of the data on the bus, etc.
[0051] Each ICD local node designs the ICD information distributed by the remote node to obtain the final designed ICD information of the corresponding device. During the ICD design process, the ICD local node records each ICD information change and sends all ICD information in the local node to the ICD remote node. Thus, the ICD remote node can record and trace all changes of all ICD information in the entire system.
[0052] The following will be combined Figure 2 to Figure 5 Introduction Run on Figure 1 The specific process of the ICD management method of the ICD management system shown.
[0053] See also Figure 2 , shows a flowchart of an ICD management method provided by an embodiment of the present invention, the method is applied to Figure 1 In the ICD management system shown in Figure 1 As shown, the method may include the following steps:
[0054] S110: The ICD local node obtains ICD information of a device matching the node.
[0055] In one embodiment of the present invention, the ICD local node obtains the ICD information of all devices (or subsystems) maintained by the ICD remote node from the ICD local node.
[0056] In a possible implementation, the ICD local node may be directly connected to the ICD remote node, and the ICD information of a certain device or all devices of a subsystem maintained by the ICD local node may be synchronously imported to the ICD local node.
[0057] S120, the ICD local node generates a different first version identifier for each local change of ICD information.
[0058] The ICD local node is responsible for designing the ICD information of the maintained equipment. During the ICD design process, multiple modifications (i.e., ICD changes) can be made in sequence based on the ICD information obtained from the ICD remote node. For each modification, the ICD local node will record each modified ICD information and generate a version identifier for the modified ICD information, i.e., the first version identifier.
[0059] In one embodiment of the present invention, the user of the ICD local node can complete the corresponding ICD design through the client corresponding to the local node, such as designing the relevant information of all messages or signals involved in the device or subsystem, for example, the relevant information of the input / output signal of the sensor.
[0060] One ICD change can modify multiple ICD information. For example, in one scenario, if the output port of a sensor in a subsystem is modified, the input port of another component connected to the output port of the sensor also needs to be modified. Of course, ICD information that has no association relationship can also be modified. The present invention does not limit this.
[0061] When the ICD local node stores the change information of the ICD information in the local database, it generates a corresponding first version identifier for the change information this time, and the first version identifier is used to identify different ICD versions of the ICD local node.
[0062] In one embodiment of the present invention, a first version identifier is generated for each change in the ICD information corresponding to the ICD remote node and the ICD local node information, as well as the ICD current version information of the local ICD local node. For example, based on the ICD remote node name, the ICD local node name and the local ICD current version information, a first version identifier of the ICD information after the change is generated. It is understandable that in order to facilitate the use of the latest current version information the next time the ICD information is changed, after each change in the ICD information, the ICD current version information is updated to the version information corresponding to the first version identifier obtained this time.
[0063] The version information of the ICD may be used to distinguish the order of different ICD versions. For example, the ICD version may be represented by numbers, such as 1.0, 1.1, and so on.
[0064] The ICD local node generates a different first version identifier for each ICD change, so all modification information of the ICD can be recorded.
[0065] S130, each ICD local node sends each version of local ICD information to the ICD remote node.
[0066] The ICD local node will synchronize the local versions of ICD information to the ICD remote node according to the preset conditions. For example, the ICD remote node can agree on the timing of synchronizing ICD information for each ICD local node, such as uploading the local ICD information to the ICD remote node after the ICD local node completes a certain stage of ICD design.
[0067] S140, the ICD remote node stores the ICD information of each version corresponding to each device in the project.
[0068] The ICD remote node stores the received ICD information sent by each ICD local node in the local database of the ICD remote node. In this way, the ICD remote node stores all ICD information and modification information of all devices in the project, so as to trace all changes of any ICD information in the project.
[0069] The ICD management method provided in this embodiment is applied to an ICD management system, which includes an ICD remote node and at least two ICD local nodes, wherein the ICD remote node is used to maintain the ICD information corresponding to all devices in the project, while the ICD local node maintains the ICD information corresponding to some devices in the project. The ICD local node generates a different first version identifier for each local change in the ICD information, and sends each version of the ICD information to the ICD remote node. Thereby, the ICD remote node stores each version of the ICD information of each device in the project. It can be seen from the above process that the ICD local node will generate a corresponding first version identification record for each change in the ICD information, and send it to the ICD remote node. It can be seen that the ICD remote node records all modification information of the ICD information of all devices, that is, it realizes the tracing of all modification information of all versions of all devices in the project.
[0070] See also Figure 3 , showing a flow chart of another ICD management method provided by an embodiment of the present invention. The method is applied to an ICD management system. The ICD remote node in this embodiment can also design ICD information corresponding to certain subsystems and generate different version identifiers for each modification.
[0071] like Figure 3 As shown, the method may include the following steps:
[0072] S210, the ICD remote node generates ICD information of all devices in the project, and generates a globally unique identifier for each piece of ICD information.
[0073] The ICD remote node performs ICD entry to obtain the ICD information of all devices in the entire project. One device corresponds to a set of ICD information.
[0074] The ICD remote node generates a globally unique identifier for each ICD message based on the project, system, subsystem, device, and ICD name. The globally unique identifier is used to uniquely identify an ICD message, that is, the globally unique ICD message is guaranteed by the globally unique identifier. In practical applications, the string concatenation of each part can be used as the globally unique identifier, such as project-sys-subsys-dev-icd.
[0075] S220, the ICD remote node provides each ICD information to the matching ICD local node.
[0076] After recording the ICD information of all devices in the project, the ICD remote node provides each ICD information to the matching ICD local node according to the pre-configured subsystems or devices maintained by each ICD local node.
[0077] For example, ICD local node A is responsible for designing and maintaining ICD information of all devices in subsystem b, and ICD remote node sends all ICD information related to subsystem b to ICD local node A.
[0078] In one embodiment of the present invention, the ICD remote node may be directly connected to the ICD local node, and send the ICD information of the device maintained by the ICD local node to the ICD local node.
[0079] In another embodiment of the present invention, the ICD remote node exports the ICD information maintained by a certain ICD local node in a file of a preset format, and sends the exported file to the ICD local node, such as by sending the file via network communication.
[0080] In an embodiment of the present invention, if the ICD remote node contains the latest remote ICD information and remote historical ICD information corresponding to the ICD local node, the ICD local node can choose whether the imported or synchronized ICD information contains the remote historical ICD information.
[0081] Among them, the latest remote ICD information refers to the latest version of ICD information corresponding to the ICD local node in the ICD remote node. Historical ICD information refers to the intermediate version of ICD information. In other words, the latest remote ICD information is the latest version of ICD information corresponding to the ICD local node maintenance device in the ICD remote node, and the remote historical ICD information includes all versions of ICD information corresponding to the ICD local node maintenance device before the latest version.
[0082] The ICD local node imports the remote historical ICD information from the ICD remote node, which is beneficial for the ICD local node to view the historical design information of the ICD. In a possible implementation, the remote historical ICD information and the latest remote ICD information are stored in different databases, for example, the remote historical ICD information is stored in the R&D library, and the latest remote ICD information is stored in the final version library.
[0083] S230, the ICD local node generates a different first version identifier for each local ICD information change.
[0084] During the design process of the ICD information of the equipment maintained by the ICD local node, it may be necessary to modify it multiple times in sequence. When the changed ICD information is saved to the local database, a new version identifier is generated for the changed ICD information to avoid confusion with the previous ICD version. In this way, the ICD local node will record the changed ICD information for each ICD change and generate a new version identifier.
[0085] In one embodiment of the present invention, when modifying ICD information, the change information of each piece of ICD information is identified by the globally unique identifier of the ICD.
[0086] In one possible implementation, a user may select the ICD information to be modified through the UI (User Interface) interface of the ICD client of the ICD local node, and further generate a corresponding ICD change instruction based on the operation, which carries the globally unique identifier of the ICD.
[0087] S240, the ICD remote node generates a different second version identifier for each local change of the ICD information.
[0088] In one scenario, the ICD remote node can also modify the ICD information in the project, for example, modify the constraint information of a certain device, thereby generating different versions of ICD information. The ICD remote node needs to record each changed ICD information and generate a different version identifier for the changed ICD information, namely, the second version identifier.
[0089] In another scenario, the ICD remote node can also design the ICD information of certain subsystems or equipment in the project, such as the ICD remote node is responsible for the design of the ICD information of the core subsystem in the project. During the ICD information design process, the ICD remote node can make multiple modifications in sequence based on the initially entered ICD information, and the ICD remote node generates a version identifier for each changed information, i.e., the second version identifier.
[0090] In one embodiment of the present invention, the ICD remote node generates a second version identifier of the ICD information based on the information of the ICD remote node (such as the remote node name) and the local ICD current version information. The second version identifier is used to identify different ICD versions of the ICD remote node. Moreover, each time a new second version identifier is generated, the local ICD current version information of the ICD remote node is updated to the latest second version identifier so as to generate the next second version identifier.
[0091] The process of modifying ICD information by the ICD remote node is the same as that of the ICD local node, and will not be repeated here.
[0092] S250, merging the local ICD information in the ICD local node and the latest remote ICD information in the ICD remote node corresponding to the ICD local node.
[0093] In one embodiment of the present invention, if the current situation satisfies the timing for merging ICD information agreed upon by the ICD remote node and the ICD local node (such as the agreement that the ICD local node completes a certain stage of ICD design), the ICD information in the ICD local node (i.e., local ICD information) and the latest ICD information in the remote ICD node corresponding to the ICD local node (i.e., the latest remote ICD information) are merged.
[0094] In a scenario, the ICD remote node modifies less ICD information corresponding to a subsystem or device, while the ICD local node corresponding to the subsystem or device modifies more ICD information. In this scenario, the ICD local node can merge the ICD information, such as Figure 4 As shown, the ICD information merging process may include the following steps:
[0095] S2511, the ICD local node obtains the latest remote ICD information corresponding to the ICD local node from the ICD remote node.
[0096] In a possible implementation, the ICD local node may be directly connected to the ICD remote node and request synchronization of ICD information maintained by the ICD local node from the ICD remote node, which is referred to as remote ICD information.
[0097] If the ICD remote node contains the latest remote ICD information and remote historical ICD information corresponding to the ICD local node, it can be selected whether the ICD information synchronized by the ICD local node contains the remote historical ICD information. That is, the remote ICD information can include the latest remote ICD information, or include the latest remote ICD and remote historical ICD information.
[0098] When the ICD information synchronized by the ICD local node includes remote historical ICD information, all remote historical ICD information corresponding to the ICD local node in the ICD remote node can be synchronized to the ICD local node, so that the ICD local node can easily view the historical design information of the ICD remote node for ICD.
[0099] In the case where the ICD local node chooses to synchronize historical ICD information, in order to avoid conflicts between the version identifiers of the remote historical ICD information imported by the ICD local node from the ICD remote node and the local ICD information, the ICD local node generates a new version identifier (i.e., a third version identifier) for the remote historical ICD information according to the version identifier of the imported remote historical ICD information and the time when the remote historical ICD information was imported. Wherein, the local ICD information refers to the ICD information stored in the ICD local node.
[0100] For example, the version identifier of the remote historical ICD information is xxxdate, where xxx is the version identifier generated by the ICD remote node, and date indicates the time when the version identifier is generated; the ICD local node changes the version identifier of each remote historical ICD information to xxxdate.ldate in turn, that is, adds "ldate" to the version identifier of the original remote historical ICD information, where ldate indicates the time when the ICD local node imports the remote historical ICD information.
[0101] The ICD local node modifies the version identifier of the imported remote historical ICD information so that the ICD local node can identify and record the ICD historical data of the remote ICD node.
[0102] It should be noted that in some embodiments of the present invention, merging processing may not be performed, and the ICD local node generates a third version identifier corresponding to each remote historical ICD information based on the second version identifier corresponding to each remote historical ICD information and the time information of receiving the remote historical ICD information, and records each remote historical ICD information and the corresponding third version identifier.
[0103] S2512: For any latest remote ICD information, the ICD local node queries locally for the latest local ICD information having the same global unique identifier as the latest remote ICD information.
[0104] In the embodiment of the present invention, the ICD local node only performs a merging process on the latest remote ICD information and the latest local ICD information. The merging process is performed based on the global unique identifier of the ICD information to search for the latest remote ICD information and the latest local ICD information containing the same global unique identifier.
[0105] S2513, the ICD local node modifies the latest local ICD information based on the latest remote ICD information to obtain merged ICD information.
[0106] For example, if a latest remote ICD information has the same global unique identifier as a latest local ICD information, the latest remote ICD information is merged with the latest local ICD information to obtain a merged ICD information, while retaining the local historical ICD information containing the global unique identifier in the local ICD node, that is, the local ICD node retains all historical ICD information corresponding to the global unique identifier.
[0107] In the embodiment of the present invention, the merging process here is to modify the latest local ICD information of the ICD local node according to the latest remote ICD information.
[0108] For example, the latest remote ICD information modifies the constraint of a certain parameter based on the initial version of ICD information, and the ICD local node performs ICD design based on the initial version of ICD information to obtain the latest local ICD information. In this scenario, when the latest remote ICD information and the latest local ICD information are merged, the ICD local node needs to modify the parameter design information in the latest local ICD information according to the latest remote ICD information.
[0109] Furthermore, the ICD local node generates a new version identifier for the merged ICD information. For example, if the current version of the ICD local node is 1.3, the new version is 1.4. A new version identifier, such as AB1.4, is generated based on the new version information, the remote ICD node (such as A) and the name of the ICD local node (such as B).
[0110] S2514, the ICD local node submits the merged ICD information and all local historical ICD information in the ICD local node to the ICD remote node.
[0111] After the ICD local node completes merging the latest remote ICD information associated with the local node in the ICD remote node with the latest local ICD information locally, it submits the merged ICD information and all historical ICD information of the ICD local node (i.e., local historical ICD information) to the ICD remote node, so that the ICD remote node can record all historical ICD information in the ICD local node and trace all historical ICD information.
[0112] In another scenario, the ICD remote node makes more modifications to the ICD information corresponding to a certain subsystem or device, while the ICD local node corresponding to the subsystem or device makes fewer modifications to the ICD information. For example, the ICD local node has synchronized all historical ICD information before this modification to the ICD remote node, and the amount of ICD information modified this time is relatively small. In this scenario, the ICD remote node can merge the ICD information of the ICD local node.
[0113] See also Figure 5 , shows a flowchart of another ICD merging process provided by an embodiment of the present invention, such as Figure 5 As shown, the process may include the following steps:
[0114] S2521, the ICD remote node receives local ICD information sent by the ICD local node.
[0115] The local ICD information submitted directly by the ICD local node to the ICD remote node includes the latest local ICD information and the local historical ICD information.
[0116] S2522: For any latest local ICD information, the ICD remote node queries the ICD remote node for the latest remote ICD information having the same global unique identifier as the latest local ICD information.
[0117] The ICD remote node can use the project name, system name, subsystem name and device name to find the latest ICD information corresponding to the ICD local node from the latest ICD information stored in the ICD remote node, which is called the latest remote ICD information.
[0118] S2523, the ICD remote node modifies the latest local ICD information based on the latest remote ICD information to obtain merged ICD information.
[0119] This process is the same as the merging process of the ICD local node and will not be repeated here.
[0120] S2524, the ICD remote node stores the local historical ICD information uploaded by the ICD local node.
[0121] The ICD remote node saves all local historical ICD information uploaded by the ICD local node so as to trace the historical ICD information.
[0122] S260, displaying the ICD information of the project in a tree format.
[0123] On the one hand, the entire ICD version change record is displayed in a tree format, where the root node displays the current latest version of ICD, the first-level child nodes display the ICD information of all finalized versions, and the second-level child nodes display the historical change records of all finalized versions.
[0124] On the other hand, the modification submission information of each version is displayed in the form of a tree node. When the user clicks a tree node, the library source of the version is displayed, such as an ICD remote node or any ICD local node. For example, when the user clicks a tree node, the change history and submitter information of this version can be displayed in a table.
[0125] The ICD management method provided by the embodiment of the present invention is applied to an ICD management system, which includes an ICD local node and an ICD remote node. Moreover, the ICD local node and the ICD remote node can modify the ICD information respectively, and generate different version identifiers for the modified ICD information, so that all modification records of all ICD information can be recorded and traced. Moreover, the scheme can perform ICD merging at the ICD remote node or the ICD local node, thereby improving the flexibility of the merging processing operation.
[0126] The present invention also provides an ICD remote node, which includes a memory and a processor. The memory stores program instructions, and the processor executes the program instructions to execute the method executed by the ICD remote node in the above-mentioned ICD management method.
[0127] The present invention also provides an ICD local node, which includes a memory and a processor. The memory stores program instructions, and the processor executes the program instructions to execute the method executed by the ICD local node in the above-mentioned ICD management method.
[0128] On the other hand, the present invention also provides a storage medium executable by a computing device, wherein a program is stored in the storage medium, and when the program is executed by the computing device, the method executed by the ICD remote node in the above-mentioned ICD management method is implemented. Alternatively, when the program is executed by the computing device, the method executed by the ICD local node in the above-mentioned ICD management method is implemented.
[0129] For the above-mentioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the order of the actions described, because according to the present invention, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.
[0130] It should be noted that the technical features recorded in the various embodiments in this specification can be replaced or combined with each other, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0131] The steps in the methods of the embodiments of the present invention may be adjusted in order, combined, or deleted according to actual needs.
[0132] The modules and sub-modules in the apparatus and terminal in each embodiment of the present invention may be combined, divided or deleted according to actual needs.
[0133] In the several embodiments provided by the present invention, it should be understood that the disclosed terminals, devices and methods can be implemented in other ways. For example, the terminal embodiments described above are only schematic, for example, the division of modules or submodules is only a logical function division, and there may be other division methods in actual implementation, such as multiple submodules or modules can be combined or integrated into another module, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.
[0134] The modules or submodules described as separate components may or may not be physically separated, and the components of the modules or submodules may or may not be physical modules or submodules, that is, they may be located in one place, or they may be distributed on multiple network modules or submodules. Some or all of the modules or submodules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0135] In addition, each functional module or submodule in each embodiment of the present invention may be integrated into one processing module, or each module or submodule may exist physically separately, or two or more modules or submodules may be integrated into one module. The above-mentioned integrated modules or submodules may be implemented in the form of hardware or in the form of software functional modules or submodules.
[0136] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0137] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.
[0138] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.
Claims
1. An interface control file management method, characterized in that: Applied to an interface control file ICD management system, the ICD management system includes an ICD remote node and at least two ICD local nodes, the ICD remote node maintains ICD information corresponding to all devices in the project, and the ICD local node maintains ICD information corresponding to some devices in the project, the method includes: The ICD local node acquires ICD information of a device matching the ICD local node; The ICD local node generates a different first version identifier for each local ICD information change; wherein, when the ICD local node stores the change information of the ICD information in the local database, it generates a corresponding first version identifier for the change information of this time; Each of the ICD local nodes sends each version of local ICD information to the ICD remote node according to preset conditions, wherein the preset conditions include the timing of synchronizing the ICD information; The ICD remote node stores ICD information of various versions corresponding to each device in the project; The method further comprises: The local ICD information in the ICD local node is merged with the latest remote ICD information corresponding to the ICD local node stored in the ICD remote node, wherein the node with the larger amount of modification to the ICD information among the ICD local node and the ICD remote node is merged.
2. The method according to claim 1, characterized in that The ICD local node generates a different first version identifier for each locally changed ICD information, including: The ICD local node records at least one ICD information corresponding to each change, and generates a first version identifier for the at least one ICD information based on the information of the ICD remote node and the ICD local node, and the ICD current version information of the local ICD local node; The current version information of the ICD is updated to the version information corresponding to the first version identifier.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: The ICD remote node generates ICD information corresponding to all devices in the project and generates a globally unique identifier for each ICD information; The ICD remote node generates a different second version identifier for each changed ICD information.
4. The method according to claim 3, characterized in that The ICD remote node generates a different second version identifier for each changed ICD information, including: The ICD remote node generates a second version identifier for at least one ICD information of this change based on the information of the ICD remote node and the local ICD current version information of the ICD remote node.
5. The method according to claim 4, characterized in that The ICD local node acquires ICD information of a device matching the ICD local node, including: The ICD local node obtains the latest remote ICD information of the ICD local node maintenance device from the ICD remote node, or the latest remote ICD information and remote historical ICD information; Among them, the latest remote ICD information is the latest version of ICD information in the ICD remote node corresponding to the ICD local node maintenance device, and the remote historical ICD information includes all versions of ICD information before the latest version corresponding to the ICD local node maintenance device.
6. The method according to claim 5, characterized in that The ICD local node obtains the latest remote ICD information and remote historical ICD information of the ICD local node maintenance device from the ICD remote node; the method further includes: The ICD local node generates a third version identifier corresponding to each remote historical ICD information based on the second version identifier corresponding to each remote historical ICD information and the time information of receiving the remote historical ICD information, and records each remote historical ICD information and the corresponding third version identifier.
7. The method according to claim 1, characterized in that The merging of the local ICD information in the ICD local node with the latest remote ICD information corresponding to the ICD local node stored in the ICD remote node includes: The ICD local node obtains the latest remote ICD information corresponding to the ICD local node from the ICD remote node; For any of the latest remote ICD information, the ICD local node queries the ICD local node for the latest local ICD information having the same global unique identifier as any of the latest remote ICD information; The ICD local node modifies the latest local ICD information based on the latest remote ICD information to obtain merged ICD information; The ICD local node sends the merged ICD information and all local historical ICD information in the ICD local node to the ICD remote node.
8. The method according to claim 1, characterized in that The merging of the local ICD information in the ICD local node with the latest remote ICD information corresponding to the ICD local node stored in the ICD remote node includes: The ICD remote node receives the latest local ICD information and local historical ICD information sent by the ICD local node; For any piece of latest local ICD information, the ICD remote node queries the ICD remote node for the latest remote ICD information having the same global unique identifier as the any piece of latest local ICD information; The ICD remote node modifies the latest local ICD information based on the latest remote ICD information to obtain merged ICD information; The ICD remote node stores the local historical ICD information.
9. An interface control file management system, characterized in that: include: An interface control file ICD remote node and at least two ICD local nodes, wherein the ICD remote node maintains ICD information corresponding to all devices of the project, and the ICD local node maintains ICD information corresponding to some devices of the project; The ICD remote node and at least two ICD local nodes are used to execute the interface control file management method described in any one of claims 1-8.
