Cross-region-based heterogeneous data model consistency maintenance method, device and system

Abstract

The application discloses a heterogeneous data model consistency maintenance method, device and system based on cross-regions, which comprises the following steps: generating a calling file according to requirements and sending the calling file to a third region; receiving a model data file sent by the third region; the generation of the model data file comprises the following steps: the third region analyzes the received calling file, obtains corresponding model data in a specified data maintenance range based on instruction types in the calling file, table names of model objects and a preset model mapping relationship, converts the obtained model data according to the preset model mapping relationship, generates a model data file, analyzes the received model data file, compares the obtained model data with model data in a specified data maintenance range of the region, and performs consistency maintenance on model data of the region according to a comparison result. The application can realize heterogeneous power grid model consistency processing under a cross-region system.

Description

Technical Field

[0001] This invention belongs to the field of smart grid models, specifically relating to a method, device, and system for maintaining consistency of heterogeneous data models across regions. Background Technology

[0002] The new generation of dispatch automation system adopts the concept of "physical distribution and logical unification" in the modeling of the power grid. The dispatch cloud realizes unified modeling and management of the power grid model in the production management area (zone three), while the monitoring system realizes the use of the power grid model in the production control area (zone one). The production control area (zone one) and the production management area (zone three) are physically isolated from each other through forward and reverse isolation devices. Since the power grid model structures of zone three and zone one are heterogeneous, there is a need for cross-zone synchronization and consistency processing of heterogeneous models when synchronizing the models of zone three to zone one. Summary of the Invention

[0003] To address the aforementioned issues, this invention proposes a method, apparatus, and system for maintaining consistency of heterogeneous data models across regions, which can achieve consistency processing of heterogeneous power grid models in cross-regional systems.

[0004] To achieve the above-mentioned technical objectives and effects, the present invention is implemented through the following technical solution:

[0005] In a first aspect, the present invention provides a method for maintaining consistency of heterogeneous data models across regions, applied to a single region, comprising:

[0006] Generate a summoning file based on requirements and send it across three regions;

[0007] The model data file is received from the three regions. The steps for generating the model data file include: parsing the received call file in the three regions; obtaining the corresponding model data within the specified data maintenance range based on the instruction type and table name of the model object in the call file, as well as the preset model mapping relationship; and converting the obtained model data according to the preset model mapping relationship to generate the model data file.

[0008] The received model data file is parsed, and the parsed model data is compared with the model data in the specified data maintenance range of this area. Based on the comparison results, the consistency of the model data in this area is maintained.

[0009] Optionally, the preset conversion rules include table correspondence rules and domain correspondence rules;

[0010] The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the table correspondence between Zone 1 and Zone 3;

[0011] The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the domain correspondence between Zone 1 and Zone 3.

[0012] Optionally, the method for generating the model data file includes:

[0013] According to the domain correspondence rules in the preset conversion rules, the acquired model data is converted into a heterogeneous first-zone model data structure to form a model data file.

[0014] Optionally, the instruction type is used to specify the data maintenance scope;

[0015] When the instruction type is full model summon, the method for obtaining the corresponding model data includes:

[0016] Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0017] When the instruction type is based on a substation or feeder, the summoning file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0018] Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0019] When the instruction type is region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0020] Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

[0021] Secondly, this invention provides a method for maintaining consistency of heterogeneous data models across regions, applicable to three regions, including:

[0022] Receive a summoning file, which is generated by Zone 1 according to requirements;

[0023] Parse the received call file, and based on the instruction type and model object table name in the call file, as well as the preset model mapping relationship, obtain the corresponding model data within the specified data maintenance range;

[0024] Based on the preset model mapping relationship, the acquired model data is transformed to generate a model data file;

[0025] The model data file is sent to Zone 1, which parses the model data file, compares the parsed model data with the model data within the specified data maintenance range of Zone 1, and maintains the consistency of the model data in Zone 1 based on the comparison results.

[0026] Optionally, the preset conversion rules include table correspondence rules and domain correspondence rules;

[0027] The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the table correspondence between Zone 1 and Zone 3;

[0028] The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the domain correspondence between Zone 1 and Zone 3.

[0029] Optionally, the method for generating the model data file includes:

[0030] According to the domain correspondence rules in the preset conversion rules, the acquired model data is converted into a heterogeneous first-zone model data structure to form a model data file.

[0031] Optionally, the instruction type is used to specify the data maintenance scope;

[0032] When the instruction type is full model summon, the method for obtaining the corresponding model data includes:

[0033] Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0034] When the instruction type is based on a substation or feeder, the summoning file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0035] Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0036] When the instruction type is region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0037] Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

[0038] Thirdly, the present invention provides a cross-regional heterogeneous data model consistency maintenance device, applied to a single region, comprising:

[0039] The sending module is used to generate a summoning file according to requirements and send it across regions to all three regions;

[0040] The receiving module is used to receive model data files sent by the three zones. The steps for generating the model data files include: parsing the received call file by the three zones; obtaining the corresponding model data within a specified data maintenance range based on the instruction type and table name of the model object in the call file, as well as the preset model mapping relationship; and converting the obtained model data according to the preset model mapping relationship to generate a model data file.

[0041] The maintenance module is used to parse the received model data file, compare the parsed model data with the model data in the specified data maintenance range of this area, and maintain the consistency of the model data in this area based on the comparison results.

[0042] Fourthly, the present invention provides a cross-regional heterogeneous data model consistency maintenance device, applied to three regions, comprising:

[0043] The receiving module is used to receive the summoning file, which is generated by Zone 1 according to requirements;

[0044] The parsing module is used to parse the received summon file, and based on the instruction type and table name of the model object in the summon file, as well as the preset model mapping relationship, obtain the corresponding model data within the specified data maintenance range.

[0045] The generation module is used to transform the acquired model data according to the preset model mapping relationship and generate model data files;

[0046] The maintenance module is used to send the model data file to Zone 1, so that Zone 1 parses the model data file, compares the parsed model data with the model data in the specified data maintenance range of Zone 1, and performs consistency maintenance on the model data in Zone 1 based on the comparison results.

[0047] Fifthly, the present invention provides a cross-regional heterogeneous data model consistency maintenance system, including a storage medium and a processor;

[0048] The storage medium is used to store instructions;

[0049] The processor is configured to operate according to the instructions to perform the steps of the method according to any one of the first aspects.

[0050] Sixthly, the present invention provides a cross-regional heterogeneous data model consistency maintenance system, including a storage medium and a processor;

[0051] The storage medium is used to store instructions;

[0052] The processor is configured to operate according to the instructions to perform the steps of the method according to any one of the second aspects.

[0053] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0054] This invention uses three regions (such as a control cloud platform) as the data source and one region (such as a monitoring system) as the destination. The destination specifies the data maintenance area and model objects through a specified call file, which is then sent to the data source. The data source extracts, transforms, and synchronizes the data, ultimately achieving consistency of heterogeneous power grid models across different regions. Attached Figure Description

[0055] To make the content of this invention easier to understand, the invention will be further described in detail below with reference to specific embodiments and accompanying drawings, wherein:

[0056] Figure 1 This is one of the flowcharts for a cross-regional heterogeneous data model consistency maintenance method according to an embodiment of the present invention.

[0057] Figure 2 This is the second flowchart of a cross-regional heterogeneous data model consistency maintenance method according to an embodiment of the present invention. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the scope of protection of the invention.

[0059] The application principle of the present invention will be described in detail below with reference to the accompanying drawings.

[0060] Example 1

[0061] This invention provides a method for maintaining consistency of heterogeneous data models across regions, applied to a single region, where the single region is the destination, such as a monitoring system, and includes the following steps:

[0062] (1) Generate a summoning file according to the requirements and send it to the three regions across regions;

[0063] (2) Receive the model data file sent by the three zones. The model data file generation steps include: the three zones parse the received call file, and based on the instruction type and table name of the model object in the call file, as well as the preset model mapping relationship, obtain the corresponding model data within the specified data maintenance range; and convert the obtained model data according to the preset model mapping relationship to generate the model data file.

[0064] (3) Parse the received model data file, compare the parsed model data with the model data in the specified data maintenance range of this area, and maintain the consistency of the model data in this area according to the comparison results, such as marking inconsistent data to achieve model data maintenance in one area.

[0065] In practical applications, the data source (generally referring to the third security management zone) and the data destination (generally referring to the first security management zone) have different model organizational structures and corresponding element architectures. Without structural conversion, data consistency maintenance cannot be directly achieved. Therefore, in one specific embodiment of this invention, the preset conversion rules include table correspondence rules and domain correspondence rules, used to achieve table-domain correspondence conversion of model data.

[0066] The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, completing the table correspondence between Zone 1 and Zone 3, so as to complete the parsing of the data range;

[0067] The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, completing the domain correspondence between Zone 1 and Zone 3, so as to complete the reconstruction of the data model.

[0068] In one specific embodiment of the present invention, the instruction type is used to specify the data maintenance scope; when the instruction type is full model summoning, the corresponding method for obtaining the model data includes:

[0069] Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0070] In another specific embodiment of the present invention, when the instruction type is based on a substation or feeder call, the call file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0071] Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0072] In a third specific embodiment of the present invention, when the instruction type is a region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0073] Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

[0074] In one specific embodiment of Example 1 of the present invention, the method for generating the model data file includes:

[0075] Based on the domain correspondence rules in the preset conversion rules, the three zones convert the acquired model data into a heterogeneous model data structure in the first zone, forming a model data file.

[0076] The method in the embodiments of the present invention will be described in detail below with reference to a specific implementation method.

[0077] like Figure 1-2 As shown, this embodiment of the invention provides a method for maintaining consistency of heterogeneous data models across regions, including the following steps:

[0078] Step 1) Compile model mapping relationships (i.e., construct heterogeneous model matching rules and corresponding relationships), which specifically includes the following sub-steps;

[0079] Step 1.1) Construct the correspondence between the model object tables of the heterogeneous models across Zone 1 and Zone 3. The configuration rules for the Zone 1 model object table are shown in Table 1, and the corresponding configuration of the Zone 3 model object table is shown in Table 2.

[0080] Table 1

[0081] English name Chinese name Data types Is this field required? meaning ENG_NAME Table English Name String yes - CHN_NAME Chinese name String yes - TABLE_CODE Table No. Number yes - KEY_FIELD Primary key field String yes - GROUP_FIELD Domain String no The factory station belonging to the first area model STATE_FIELD State domain String no Model running status in Zone 1

[0082] Table 2

[0083]

[0084] Table 2. Three-zone model table rule configuration

[0085] Step 1.2) Construct the domain transformation relationship of the correspondence table of heterogeneous models across Zone 1 and Zone 3. The domain configuration rules of the heterogeneous models across Zone 1 and Zone 3 are shown in Table 3.

[0086] English name Chinese name Data types Is this field required? meaning SG_TABLE Three-zone table (English name) String yes - NAME Domain Chinese name String yes - FIELD_RT English name of a region String yes - FIELD_SG English names of three regions String yes - FIELD_TYPE_RT A region data type String yes - FIELD_TYPE_SG Three-region data type String yes -

[0087] Table 3. Rule Configurations Corresponding to the Heterogeneous Model Domains in Zones 1 and 3

[0088] Step 2) Generate and send the model data request file (i.e., initiate a model maintenance request), which includes the following steps:

[0089] The Zone 1 service can specify the required data model range by setting the instruction type and its specific parameters (such as the table name of the model object, plant, feeder, and region) in the model data retrieval file, thereby generating a retrieval file, which is then sent to Zone 3 via the cross-zone service. The specific instruction types that can be included in the retrieval file are shown in Table 4.

[0090]

[0091] Table 4 Synchronization Instruction Logic

[0092] Step 3) Model data acquisition, transformation, and model data file generation and return, specifically including the following steps:

[0093] After receiving the summoning file, Zone 3 obtains model data within a specified range according to the heterogeneous data model consistency maintenance instructions, the instruction type and table name of the model object (i.e., the specified logic) in the summoning file, and performs model data conversion and splicing according to the model mapping relationship configured in step 1) to generate a model data file (i.e., data record) that conforms to the model structure of Zone 1. In other words, it performs data verification and model conversion and reconstruction on the obtained model data of Zone 3, and then sends it to Zone 1.

[0094] Step 4) Model data comparison and maintenance, the specific operation process includes:

[0095] After receiving the model data file within the specified range from the reconstructed model data file in Zone 3, Zone 1 parses the file and compares the parsed model data with the model data within the same range in Zone 1. After comparison, the data is displayed in Zone 3 according to the addition, deletion, and modification methods relative to the model data in Zone 1. If a device in Zone 1's model is not present in Zone 3's model, it is displayed as newly added; if a device in Zone 3's model is not present in Zone 1's model, it is displayed as deleted; if both Zone 1 and Zone 3 have the device, but their data is inconsistent, it is displayed as modified. Specifying the corresponding Zone 1 model record for inclusion in the database maintains the consistency of that data across Zone 1 and Zone 3 models.

[0096] Step 5) Process management, the specific operation process includes:

[0097] Step 5.1) Process management after receiving the summoning file: After the third-zone service receives the model summoning file requested by the first-zone service, it returns a message receipt to the first-zone service indicating that the summoning file has been received and is ready to obtain the model data.

[0098] Step 5.2) After the data acquisition is completed, the three-zone service will return a message receipt to the first zone after the data acquisition is completed according to the instructions, informing the first zone that the data acquisition has been completed according to the specified data range and waiting for the model reconstruction and splicing to be completed before returning to the first zone.

[0099] Example 2

[0100] This invention provides a method for maintaining consistency of heterogeneous data models across regions, applicable to three regions, comprising the following steps:

[0101] Receive a summoning file, which is generated by Zone 1 according to requirements;

[0102] Parse the received call file, and based on the instruction type and model object table name in the call file, as well as the preset model mapping relationship, obtain the corresponding model data within the specified data maintenance range;

[0103] Based on the preset model mapping relationship, the acquired model data is transformed to generate a model data file;

[0104] The model data file is sent to Zone 1, which parses the model data file, compares the parsed model with the model data file in Zone 1, and maintains the consistency of the model data file in Zone 1 based on the comparison result.

[0105] In practical applications, the data source (generally referring to the third security management zone) and the data destination (generally referring to the first security management zone) have different model organizational structures and corresponding element architectures. Without structural conversion, data consistency maintenance cannot be directly achieved. Therefore, in one specific embodiment of this invention, the preset conversion rules include table correspondence rules and domain correspondence rules, used to achieve table-domain correspondence conversion of model data.

[0106] The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, completing the table correspondence between Zone 1 and Zone 3, so as to complete the parsing of the data range;

[0107] The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, completing the domain correspondence between Zone 1 and Zone 3, so as to complete the reconstruction of the data model.

[0108] In one specific embodiment of the present invention, the instruction type is used to specify the data maintenance range;

[0109] When the instruction type is full model summon, the method for obtaining the corresponding model data includes:

[0110] Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0111] In another specific embodiment of the present invention, when the instruction type is based on a substation or feeder call, the call file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0112] Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship;

[0113] In a third specific embodiment of the present invention, when the instruction type is a region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes:

[0114] Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

[0115] In one specific embodiment of the present invention, the method for generating the model data file includes:

[0116] According to the domain correspondence rules in the preset conversion rules, the acquired model data is converted into a heterogeneous first-zone model data structure to form a model data file.

[0117] The method in the embodiments of the present invention will be described in detail below with reference to a specific implementation method.

[0118] like Figure 1-2 As shown, this embodiment of the invention provides a method for maintaining consistency of heterogeneous data models across regions, including the following steps:

[0119] Step 1) Compile model mapping relationships (i.e., construct heterogeneous model matching rules and corresponding relationships), which specifically includes the following sub-steps;

[0120] Step 1.1) Construct the correspondence between the model object tables of the heterogeneous models across Zone 1 and Zone 3. The configuration rules for the Zone 1 model object table are shown in Table 1, and the corresponding configuration of the Zone 3 model object table is shown in Table 2.

[0121] Table 1

[0122] English name Chinese name Data types Is this field required? meaning ENG_NAME Table English Name String yes - CHN_NAME Chinese name String yes - TABLE_CODE Table No. Number yes - KEY_FIELD Primary key field String yes - GROUP_FIELD Domain String no The factory station belonging to the first area model STATE_FIELD State domain String no Model running status in Zone 1

[0123] Table 2

[0124]

[0125] Table 2. Three-zone model table rule configuration

[0126] Step 1.2) Construct the domain transformation relationship of the correspondence table of heterogeneous models across Zone 1 and Zone 3. The domain configuration rules of the heterogeneous models across Zone 1 and Zone 3 are shown in Table 3.

[0127] English name Chinese name Data types Is this field required? meaning SG_TABLE Three-zone table (English name) String yes - NAME Domain Chinese name String yes - FIELD_RT English name of a region String yes - FIELD_SG English names of three regions String yes - FIELD_TYPE_RT A region data type String yes - FIELD_TYPE_SG Three-region data type String yes -

[0128] Table 3. Rule Configurations Corresponding to the Heterogeneous Model Domains in Zones 1 and 3

[0129] Step 2) Generate and send the model data request file (i.e., initiate a model maintenance request), which includes the following steps:

[0130] The Zone 1 service can specify the required data model range by setting the instruction type and its specific parameters (such as the table name of the model object, plant, feeder, and region) in the model data retrieval file, thereby generating a retrieval file, which is then sent to Zone 3 via the cross-zone service. The specific instruction types that can be included in the retrieval file are shown in Table 4.

[0131]

[0132] Table 4 Synchronization Instruction Logic

[0133] Step 3) Model data acquisition, transformation, and model data file generation and return, specifically including the following steps:

[0134] After receiving the summoning file, Zone 3 obtains model data within a specified range according to the heterogeneous data model consistency maintenance instructions, the instruction type and table name of the model object (i.e., the specified logic) in the summoning file, and performs model data conversion and splicing according to the model mapping relationship configured in step 1) to generate a model data file (i.e., data record) that conforms to the model structure of Zone 1. In other words, it performs data verification and model conversion and reconstruction on the obtained model data of Zone 3, and then sends it to Zone 1.

[0135] Step 4) Model data comparison and maintenance, the specific operation process includes:

[0136] After receiving the model data file within the specified range from the reconstructed model data file in Zone 3, Zone 1 parses the file and compares the parsed model data with the model data within the same range in Zone 1. After comparison, the data is displayed in Zone 3 according to the addition, deletion, and modification methods relative to the model data in Zone 1. If a device in Zone 1's model is not present in Zone 3's model, it is displayed as newly added; if a device in Zone 3's model is not present in Zone 1's model, it is displayed as deleted; if both Zone 1 and Zone 3 have the device, but their data is inconsistent, it is displayed as modified. Specifying the corresponding Zone 1 model record for inclusion in the database maintains the consistency of that data across Zone 1 and Zone 3 models.

[0137] Step 5) Process management, the specific operation process includes:

[0138] Step 5.1) Process management after receiving the summoning file: After the third-zone service receives the model summoning file requested by the first-zone service, it returns a message receipt to the first-zone service indicating that the summoning file has been received and is ready to obtain the model data.

[0139] Step 5.2) After the data acquisition is completed, the three-zone service will return a message receipt to the first zone after the data acquisition is completed according to the instructions, informing the first zone that the data acquisition has been completed according to the specified data range and waiting for the model reconstruction and splicing to be completed before returning to the first zone.

[0140] Example 3

[0141] Based on the same inventive concept as in Embodiment 1, this embodiment of the invention provides a cross-regional heterogeneous data model consistency maintenance device, applied to one region, comprising:

[0142] The sending module is used to generate a summoning file according to requirements and send it across regions to all three regions;

[0143] The receiving module is used to receive model data files sent by the three zones. The steps for generating the model data files include: parsing the received call file by the three zones; obtaining the corresponding model data within a specified data maintenance range based on the instruction type and table name of the model object in the call file, as well as the preset model mapping relationship; and converting the obtained model data according to the preset model mapping relationship to generate a model data file.

[0144] The maintenance module is used to parse the received model data file, compare the parsed model data with the model data in the specified data maintenance range of this area, and maintain the consistency of the model data in this area based on the comparison results.

[0145] The rest are the same as in Example 1.

[0146] Example 4

[0147] Based on the same inventive concept as Embodiment 2, this embodiment of the invention provides a cross-regional heterogeneous data model consistency maintenance device, applied to three regions, including:

[0148] The receiving module is used to receive the summoning file, which is generated by Zone 1 according to requirements;

[0149] The parsing module is used to parse the received summon file, and based on the instruction type and table name of the model object in the summon file, as well as the preset model mapping relationship, obtain the corresponding model data within the specified data maintenance range.

[0150] The generation module is used to transform the acquired model data according to the preset model mapping relationship and generate model data files;

[0151] The maintenance module is used to send the model data file to Zone 1, so that Zone 1 parses the model data file, compares the parsed model data with the model data in Zone 1, and maintains the consistency of the model data in Zone 1 based on the comparison results.

[0152] The rest are the same as in Example 2.

[0153] Example 5

[0154] Based on the same inventive concept as in Embodiment 1, this embodiment of the invention provides a cross-regional heterogeneous data model consistency maintenance system, including a storage medium and a processor;

[0155] The storage medium is used to store instructions;

[0156] The processor is configured to operate according to the instructions to perform the steps of the method according to any one of Embodiment 1.

[0157] Example 6

[0158] Based on the same inventive concept as in Embodiment 2, this embodiment of the invention provides a cross-regional heterogeneous data model consistency maintenance system, including a storage medium and a processor;

[0159] The storage medium is used to store instructions;

[0160] The processor is configured to operate according to the instructions to perform the steps of the method according to any one of Embodiment 2.

[0161] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0162] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0163] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1The function specified in one or more boxes.

[0164] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0165] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

[0166] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A method for maintaining consistency of heterogeneous data models across regions, characterized in that, Applied to Zone 1, including: Generate a summoning file based on requirements and send it across three regions; The model data file is received from the three regions. The steps for generating the model data file include: parsing the received call file in the three regions; obtaining the corresponding model data within the specified data maintenance range based on the instruction type and table name of the model object in the call file, as well as the preset model mapping relationship; and converting the obtained model data according to the preset model mapping relationship to generate the model data file. The received model data file is parsed, and the parsed model data is compared with the model data in the specified data maintenance range of this area. Based on the comparison results, the consistency of the model data in this area is maintained. The preset conversion rules include table mapping rules and domain mapping rules; The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the table correspondence between Zone 1 and Zone 3; The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the domain correspondence between Zone 1 and Zone 3; The instruction type is used to specify the scope of data maintenance; When the instruction type is full model summon, the method for obtaining the corresponding model data includes: Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is based on a substation or feeder, the summoning file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

2. The method for maintaining consistency of heterogeneous data models across regions according to claim 1, characterized in that: The method for generating the model data file includes: According to the domain correspondence rules in the preset conversion rules, the acquired model data is converted into a heterogeneous first-zone model data structure to form a model data file.

3. A method for maintaining consistency of heterogeneous data models across regions, characterized in that, Applied to three zones, including: Receive a summoning file, which is generated by Zone 1 according to requirements; Parse the received call file, and based on the instruction type and model object table name in the call file, as well as the preset model mapping relationship, obtain the corresponding model data within the specified data maintenance range; Based on the preset model mapping relationship, the acquired model data is transformed to generate a model data file; The model data file is sent to Zone 1, which parses the model data file, compares the parsed model data with the model data within the specified data maintenance range of Zone 1, and maintains the consistency of the model data in Zone 1 based on the comparison results. The preset conversion rules include table mapping rules and domain mapping rules; The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the table correspondence between Zone 1 and Zone 3; The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the domain correspondence between Zone 1 and Zone 3; The instruction type is used to specify the scope of data maintenance; When the instruction type is full model summon, the method for obtaining the corresponding model data includes: Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is based on a substation or feeder, the summoning file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

4. The method for maintaining consistency of heterogeneous data models across regions according to claim 3, characterized in that: The method for generating the model data file includes: According to the domain correspondence rules in the preset conversion rules, the acquired model data is converted into a heterogeneous first-zone model data structure to form a model data file.

5. A consistency maintenance device for heterogeneous data models across regions, characterized in that, Applied to Zone 1, including: The sending module is used to generate a summoning file according to requirements and send it across regions to all three regions; The receiving module is used to receive model data files sent by the three zones. The steps for generating the model data files include: parsing the received call file by the three zones; obtaining the corresponding model data within a specified data maintenance range based on the instruction type and table name of the model object in the call file, as well as the preset model mapping relationship; and converting the obtained model data according to the preset model mapping relationship to generate a model data file. The maintenance module is used to parse the received model data file, compare the parsed model data with the model data in the specified data maintenance range of this area, and maintain the consistency of the model data in this area based on the comparison results. The preset conversion rules include table mapping rules and domain mapping rules; The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the table correspondence between Zone 1 and Zone 3; The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the domain correspondence between Zone 1 and Zone 3; The instruction type is used to specify the scope of data maintenance; When the instruction type is full model summon, the method for obtaining the corresponding model data includes: Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is based on a substation or feeder, the summoning file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

6. A consistency maintenance device for heterogeneous data models across regions, characterized in that, Applied to three zones, including: The receiving module is used to receive the summoning file, which is generated by Zone 1 according to requirements; The parsing module is used to parse the received summon file, and based on the instruction type and table name of the model object in the summon file, as well as the preset model mapping relationship, obtain the corresponding model data within the specified data maintenance range. The generation module is used to transform the acquired model data according to the preset model mapping relationship and generate model data files; The maintenance module is used to send the model data file to Zone 1, so that Zone 1 parses the model data file, compares the parsed model data with the model data in the specified data maintenance range of Zone 1, and performs consistency maintenance on the model data in Zone 1 based on the comparison results. The preset conversion rules include table mapping rules and domain mapping rules; The method for generating the table correspondence rules includes: specifying the correspondence between table names in the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the table correspondence between Zone 1 and Zone 3; The method for generating the domain correspondence rules includes: specifying the correspondence between domains in the correspondence tables of the heterogeneous data models of Zone 1 and Zone 3 respectively, and completing the domain correspondence between Zone 1 and Zone 3; The instruction type is used to specify the scope of data maintenance; When the instruction type is full model summon, the method for obtaining the corresponding model data includes: Based on the device table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is based on a substation or feeder, the summoning file also includes the substation or feeder to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the equipment table of the model object, find all model records of the model object in the three zones according to the preset model mapping relationship; When the instruction type is region-based summoning, the summoning file also includes the region to which the model object belongs, and the method for obtaining the corresponding model data includes: Based on the device table of the model object, and according to the preset model mapping relationship, find all model records of the model object in the three zones.

7. A system for maintaining consistency of heterogeneous data models across regions, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the steps of the method according to any one of claims 1-2.

8. A system for maintaining consistency of heterogeneous data models across regions, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the steps of the method according to any one of claims 3-4.

Images