CN113760354B - Ontology information version management and control method and device of dispatching automation system - Google Patents
Ontology information version management and control method and device of dispatching automation system Download PDFInfo
- Publication number
- CN113760354B CN113760354B CN202111043744.8A CN202111043744A CN113760354B CN 113760354 B CN113760354 B CN 113760354B CN 202111043744 A CN202111043744 A CN 202111043744A CN 113760354 B CN113760354 B CN 113760354B
- Authority
- CN
- China
- Prior art keywords
- version
- release configuration
- information
- target
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Library & Information Science (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a method and a device for managing and controlling body information versions of a dispatching automation system, wherein the method comprises the following steps: acquiring system files and version information of all dispatching automation systems; creating an ontology base line version in a software version library based on the system file and version information thereof; based on the base line version of the ontology, making a release configuration version and storing the release configuration version and a software version library; pulling the release configuration version to an external verification environment through a platform program interface on the virtualization platform to verify the release configuration version; in response to an update request of the target dispatch automation system, a target release configuration version is selected from a software version library for deployment on the target dispatch automation system. The method solves the problem that errors occur in the manual maintenance procedure updating link due to the function upgrading and software defect elimination, thereby improving the working efficiency of the deployment upgrading of the system and greatly reducing the deployment time.
Description
Technical Field
The application relates to the technical field of power system management and control, in particular to a method and a device for managing and controlling an ontology information version of a dispatching automation system.
Background
With the continuous improvement of the operation profession of the dispatching automation system on the dispatching control requirement and the rapid development of the automation technology, the scale of the dispatching automation system software is more and more huge, the functions are more and more complex, and the versions of different automation dispatching systems are different and are complicated, specifically, the version information of the dispatching automation system comprises compiled binary executable files, library files, system configuration files, basic data files such as graphic models and operation data files and other 4 types of files, different personalized requirements can be provided by the use units of different systems, the software versions of each site are different, the system software needed to be updated is huge in scale and structure when the system program is updated (such as the conditions of function upgrading or software missing), and the system software is different from the source code control in the software development process of the IT industry, so that the same program updating operation can be safely performed on certain sites, but the system faults can be caused on certain sites, and great influence is caused on the power grid dispatching control.
Disclosure of Invention
The application provides a method and a device for managing and controlling a body information version of a dispatching automation system, which are used for avoiding risks caused by errors in a manual maintenance program updating link due to function updating and software deletion when the dispatching automation system program is updated, so that the working efficiency of system deployment and upgrading is improved, and the deployment time is greatly reduced.
In a first aspect, the present application provides a method for managing and controlling an ontology information version of a dispatching automation system, including:
acquiring system files and version information of all dispatching automation systems;
creating an ontology base line version in a software version library based on the system file and version information thereof;
based on the body baseline version, making a release configuration version and storing the release configuration version and the software version library;
pulling the release configuration version to an external verification environment through a platform program interface on a virtualization platform to verify the release configuration version;
and responding to the update request of the target dispatching automation system, selecting a target release configuration version from the software version library to be deployed on the target dispatching automation system.
Optionally, the software version library is configured with a version management and control center, a demand management and control center and a large file storage engine; creating an ontology base line version in a software version library based on the system file and version information thereof, wherein the method comprises the following steps:
recording the system file into a metadata base of the software version base through the version control center;
recording release characteristics of the version information through the demand management and control center; the release characteristics comprise version optimization information and program defect repair information;
preprocessing and storing the version file by the large file storage engine; the pretreatment comprises the following steps: at least one of decomposing, compressing, or stitching the version file.
Optionally, the system file version information includes: program files, configuration files, base data files, and run data files; recording, by the version control center, the system file into a metadata base of the software version base, including:
rejecting the operation data file in the version information of the system file to obtain rejected version information;
obtaining the abstract corresponding to the rejected version information by calculating the abstract, and storing the abstract into the metadata base;
comparing all the abstracts, and if the same abstracts exist, eliminating the same abstracts.
Optionally, in response to an update request of the target scheduling automation system, selecting a target release configuration version from the software version library to be deployed after the target scheduling automation system further comprises:
performing, by the version control center, a difference analysis on a current version of the target dispatch automation system and the target release configuration version; and listing, by the demand management center, release characteristics of the target release configuration version.
In a second aspect, the present application provides a device for managing and controlling an ontology information version of a dispatching automation system, including:
the acquisition module is used for acquiring system files and version information of all the dispatching automation systems;
the creation module is used for creating an ontology base line version in a software version library based on the system file and version information thereof;
the manufacturing module is used for manufacturing a release configuration version based on the body baseline version and storing the release configuration version and the software version library;
the pulling module is used for pulling the release configuration version to an external verification environment through a platform program interface on the virtualized platform so as to verify the release configuration version;
and the response module is used for responding to the update request of the target dispatching automation system, selecting a target release configuration version from the software version library and deploying the target release configuration version to the target dispatching automation system.
Optionally, the software version library is configured with a version management and control center, a demand management and control center and a large file storage engine; the creation module comprises:
the first recording submodule is used for recording the system file into a metadata base of the software version base through the version control center;
the second recording submodule is used for recording the release characteristics of the version information through the demand management and control center; the release characteristics comprise version optimization information and program defect repair information;
the preprocessing sub-module is used for preprocessing and storing the version file through the large file storage engine; the pretreatment comprises the following steps: at least one of decomposing, compressing, or stitching the version file.
Optionally, the system file version information includes: program files, configuration files, base data files, and run data files; the first recording submodule includes:
the rejecting unit is used for rejecting the operation data file in the system file version information to obtain rejected version information;
the abstract calculating unit is used for obtaining the abstract corresponding to the rejected version information in a abstract calculating mode and storing the abstract in the metadata base;
and the comparison unit is used for comparing all the abstracts, and if the same abstracts exist, the same abstracts are removed.
Optionally, the method further comprises:
the difference analysis module is used for carrying out difference analysis on the current version of the target dispatching automation system and the target release configuration version through the version management and control center; and listing, by the demand management center, release characteristics of the target release configuration version.
In a third aspect, the present application provides an electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which program or instruction when executed by the processor implements the steps of the method as described in the first aspect.
In a fourth aspect, the present application provides a readable storage medium having stored thereon a program or instructions which when executed by a processor performs the steps of the method according to the first aspect.
From the above technical scheme, the application has the following advantages:
the application obtains the system files and the version information of all the dispatching automation systems; creating an ontology base line version in a software version library based on the system file and version information thereof; based on the body baseline version, making a release configuration version and storing the release configuration version and the software version library; pulling the release configuration version to an external verification environment through a platform program interface on a virtualization platform to verify the release configuration version; and responding to the update request of the target dispatching automation system, selecting a target release configuration version from the software version library to be deployed on the target dispatching automation system. Therefore, version management flow is standardized, the system global version deployment condition is favorably known, the risk caused by errors in a manual maintenance program update link due to function upgrading and software deletion when the dispatching automation system program is updated is avoided, the work efficiency of system deployment and upgrading is improved, and the deployment time is greatly reduced.
Drawings
For a clearer description of embodiments of the application or of the solutions of the prior art, the drawings that are necessary for the description of the embodiments or of the prior art will be briefly described, it being obvious that the drawings in the description below are only some embodiments of the application, from which, without inventive faculty, other drawings can be obtained for a person skilled in the art;
FIG. 1 is a flow chart illustrating steps of an embodiment of a method for ontological information version management and control of a dispatch automation system in accordance with the present application;
fig. 2 is a block diagram illustrating an embodiment of a body information version management and control apparatus of a scheduling automation system according to the present application.
Detailed Description
The embodiment of the application provides a method and a device for managing and controlling an ontology information version of a dispatching automation system, which are used for avoiding risks caused by errors in a manual maintenance program updating link due to function updating and software deletion when the dispatching automation system program is updated, so that the working efficiency of system deployment and upgrading is improved, and the deployment time is greatly reduced.
In order to make the objects, features and advantages of the present application more comprehensible, the technical solutions in the embodiments of the present application are described in detail below with reference to the accompanying drawings, and it is apparent that the embodiments described below are only some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, a flowchart of a step of an embodiment of an ontology information version control method of a scheduling automation system of the present application is applied to a version control platform, where the overall architecture of the platform may be divided into a front end and a back end, the front end is developed by using a mature Web framework, and a SPA (Single Page Application) architecture style is used to maximally reduce view transmission overhead and provide efficient operation experience. The functional modules divided on the interface mainly comprise demand management and control, version management and control, basic data management, system management and the like. The back-end business layer adopts an N-layer architecture mode of mainstream field modeling mainly in an industry standardized language mixed development mode, a cut MVC mode (without View) is used for the front-end service layer, and the field layer is divided into RCC (Requirement Control Center, demand management and control center), VCC (Version Control Center, version management and control center), basic data, LFSE (Large File Storage Engine ) and the like according to subsystems. While providing security and logging infrastructure modules. The design supports a service-oriented cloud architecture deployment mode, and each module ensures high cohesion and low coupling.
At the persistence layer, an industry mature database is adopted to store Version Metadata (Version Metadata) (directory tree, file fingerprint (MD 5), integrity description list and the like), and efficient blocking, compression and merging algorithms are adopted to access the Version File (Version File).
The method comprises the following steps:
s1, acquiring system files and version information of all dispatching automation systems;
in the embodiment of the application, the dispatching automation system file provided by a manufacturer is required to be acquired, and the acquired file for operation is required to be a full version instead of a file in a separate patch form, so that no matter what transformation occurs in the environment of a target deployment site, the version which is extracted later is required to be a complete and available version.
S2, creating an ontology base line version in a software version library based on the system file and version information thereof; the method specifically comprises the following steps:
recording the system file into a metadata base of the software version base through the version control center;
recording release characteristics of the version information through the demand management and control center; the release characteristics comprise version optimization information and program defect repair information;
preprocessing and storing the version file by the large file storage engine; the pretreatment comprises the following steps: at least one of decomposing, compressing, or stitching the version file.
In an alternative embodiment, the system file version information includes: program files, configuration files, base data files, and run data files; recording, by the version control center, the system file into a metadata base of the software version base, including:
rejecting the operation data file in the version information of the system file to obtain rejected version information;
obtaining the abstract corresponding to the rejected version information by calculating the abstract, and storing the abstract into the metadata base;
comparing all the abstracts, and if the same abstracts exist, eliminating the same abstracts.
In the embodiment of the application, the acquired system file and version information thereof are imported from the system platform corresponding to the control method, and an ontology base line version is created on the basis of the system file and the version information thereof.
It should be noted that the body baseline version is also called an admission version, and is the initial form of warehousing.
In a specific implementation, the version control center records the system file into a metadata base of a software version base, and the specific record control file is shown in the following table:
| classification | File type | Frequency of change | Importance of | Intake management |
| Program file | Binary system | High height | High height | Is that |
| Configuration file | Text of | In (a) | High height | Is that |
| Basic data file | Binary, text | Low and low | High height | Is (script type only) |
| Running data file | Text-based | High height | Low and low | Whether or not |
That is, the version control center firstly eliminates the operation data file in the version information of the system file to obtain the proposed version information, then obtains the abstract corresponding to the eliminated version information by calculating the abstract, stores the abstract in the version Repo metadata base, namely the metadata base of the software version base, and finally uses abstract comparison to ensure that the file with the same content only has one copy in one Repo.
In a specific implementation, the role played by the demand management center in this link is to record the release characteristics of version information, including: including various types of optimization or BUG fixes.
In a specific implementation, the main responsibility of the large file storage engine is to solve the problem that the large file cannot be effectively transmitted to the version repository through Web, the large file storage engine can decompose, compress and splice the file, then sign the file, and ensure the safety and integrity of file storage.
S3, based on the body baseline version, a release configuration version is manufactured and stored in the software version library;
in the embodiment of the application, the base line version of the body is taken as the version initially submitted by a manufacturer and is solidified, so that disputes are avoided, the follow-up problem is conveniently traced, and the release configuration version is introduced to solve the problem that the version which is actually operated on site is uncontrolled due to manual configuration which is usually carried out on site. In addition, based on the base line version of the body, the issuing configuration version can be manufactured, so that a large number of copy files can be avoided, the version can be quickly created and configured, and the working efficiency is greatly improved.
In particular implementations, various required modifications to release configuration versions are allowed at the version management center to accommodate the site. For example, for a version deployed to the A site, release configuration version X1 specific to version A may be created; for versions deployed to site B, release configuration version X2 specific to version B may be created; and X1 and X2 are possibly based on a common base line version X, and X1 and X2 share the base line version file of the base line, which is equivalent to two branches, support independent evolution, and simultaneously prescribe that X1 and X2 cannot merge the branches again, so that a version evolution tree structure is necessarily formed, and a loop is avoided, thereby greatly simplifying the version control complexity of the current power industry problem domain.
In addition, the version control center stores the difference files in the distribution configuration mix compared with the base line version of the body, so that the space is saved and the reading efficiency is improved.
S4, pulling the release configuration version to an external verification environment on the virtualization platform through a platform program interface so as to verify the release configuration version;
in order to support the subsequent verification in the verification environment, in the embodiment of the application, the version control center supports the platform program interface of the virtualization platform to automatically pack and compress the release configuration version, so that the pulling is performed under the condition of improving the downloading efficiency.
Meanwhile, after the external verification environment is verified, the version control configuration center supports to receive instructions, the release configuration version is marked as a verified state, only the release configuration version in the verified state can be extracted and deployed to the site, deployment accidents caused by version confusion are avoided, and therefore planning is conducted on the version provided to the site to achieve good control.
S5, responding to an update request of the target dispatching automation system, selecting a target release configuration version from the software version library, and deploying the target release configuration version to the target dispatching automation system.
In an alternative embodiment, after selecting a target release configuration version from the software version library to deploy to the target scheduling automation system in response to an update request of the target scheduling automation system, further comprising:
performing, by the version control center, a difference analysis on a current version of the target dispatch automation system and the target release configuration version; and listing, by the demand management center, release characteristics of the target release configuration version.
In the embodiment of the application, when the target dispatching automation system sends out an update request, a target release configuration version is selected from release configuration versions which are verified in a software version library and deployed in the target dispatching automation system. Meanwhile, the version management and control center provides a verification mechanism, performs difference analysis on the deployed version and the current target release configuration version, and supports release characteristics of the target release configuration version to be presented through the demand management and control center, so that deployment personnel can know the version difference conveniently, and errors in the deployment process are reduced.
In the embodiment of the application, the system files and the version information of all the dispatching automation systems are acquired; creating an ontology base line version in a software version library based on the system file and version information thereof; based on the body baseline version, making a release configuration version and storing the release configuration version and the software version library; pulling the release configuration version to an external verification environment through a platform program interface on a virtualization platform to verify the release configuration version; and responding to the update request of the target dispatching automation system, selecting a target release configuration version from the software version library to be deployed on the target dispatching automation system. Therefore, version management flow is standardized, the system global version deployment condition is favorably known, the risk caused by errors in a manual maintenance program update link due to function upgrading and software deletion when the dispatching automation system program is updated is avoided, the work efficiency of system deployment and upgrading is improved, and the deployment time is greatly reduced.
Referring to fig. 2, there is shown a block diagram illustrating an embodiment of an apparatus for controlling an entity information version of a scheduling automation system according to the present application, the apparatus includes:
an obtaining module 401, configured to obtain system files and version information of all scheduling automation systems;
a creating module 402, configured to create an ontology baseline version in a software version library based on the system file and version information thereof;
a making module 403, configured to make a release configuration version based on the ontology base line version, and store the release configuration version and the software version library;
a pulling module 404, configured to pull, on the virtualized platform, the release configuration version to an external verification environment through a platform program interface, to verify the release configuration version;
and the response module 405 is configured to select a target release configuration version from the software version library to be deployed in the target scheduling automation system in response to an update request of the target scheduling automation system.
In an alternative embodiment, the software version library is configured with a version control center, a demand control center and a large file storage engine; the creation module 402 includes:
the first recording submodule is used for recording the system file into a metadata base of the software version base through the version control center;
the second recording submodule is used for recording the release characteristics of the version information through the demand management and control center; the release characteristics comprise version optimization information and program defect repair information;
the preprocessing sub-module is used for preprocessing and storing the version file through the large file storage engine; the pretreatment comprises the following steps: at least one of decomposing, compressing, or stitching the version file.
In an alternative embodiment, the system file version information includes: program files, configuration files, base data files, and run data files; the first recording submodule includes:
the rejecting unit is used for rejecting the operation data file in the system file version information to obtain rejected version information;
the abstract calculating unit is used for obtaining the abstract corresponding to the rejected version information in a abstract calculating mode and storing the abstract in the metadata base;
and the comparison unit is used for comparing all the abstracts, and if the same abstracts exist, the same abstracts are removed.
In an alternative embodiment, the method further comprises:
the difference analysis module is used for carrying out difference analysis on the current version of the target dispatching automation system and the target release configuration version through the version management and control center; and listing, by the demand management center, release characteristics of the target release configuration version.
The embodiment of the application also provides an electronic device, which comprises a memory and a processor, wherein the memory stores an analysis machine program, and when the analysis machine program is executed by the processor, the processor executes the steps of the ontology information version management method of the dispatching automation system.
The embodiment of the application also provides an analysis machine readable storage medium, on which an analysis machine program is stored, wherein the analysis machine program realizes the method for managing the ontology information version of the dispatching automation system according to any embodiment when being executed by the processor.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the embodiments provided in the present application, it should be understood that the methods, apparatuses, electronic devices and storage media disclosed in the present application may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in an analyzer readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or partly in the form of a software product or all or part of the technical solution, which is stored in a readable storage medium, and includes several instructions for causing an analyzer device (which may be a personal analyzer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (6)
1. A method for managing and controlling an ontology version of a scheduling automation system, comprising:
acquiring system files and version information of all dispatching automation systems;
creating an ontology base line version in a software version library based on the system file and version information thereof;
based on the ontology base line version, making a release configuration version and storing the release configuration version in the software version library;
pulling the release configuration version to an external verification environment through a platform program interface on a virtualized platform to verify the release configuration version;
responding to an update request of a target dispatching automation system, selecting a target release configuration version from the software version library and deploying the target release configuration version to the target dispatching automation system;
the software version library is configured with a version control center, a demand control center and a large file storage engine; creating an ontology base line version in a software version library based on the system file and version information thereof, wherein the method comprises the following steps:
recording the system file into a metadata base of the software version base through the version control center;
recording release characteristics of the version information through the demand management and control center; the release characteristics comprise version optimization information and program defect repair information;
preprocessing and storing a version file by the large file storage engine; the pretreatment comprises the following steps: at least one of decomposing, compressing or stitching the version file;
the system file version information includes: program files, configuration files, base data files, and run data files; recording, by the version control center, the system file into a metadata base of the software version base, including:
rejecting the operation data file in the version information of the system file to obtain rejected version information;
obtaining the abstract corresponding to the rejected version information by calculating the abstract, and storing the abstract into the metadata base;
comparing all the abstracts, and if the same abstracts exist, eliminating the same abstracts.
2. The method of claim 1, further comprising, after selecting a target release configuration version from the software release library to deploy to the target scheduling automation system in response to an update request of the target scheduling automation system:
performing, by the version control center, a difference analysis on a current version of the target dispatch automation system and the target release configuration version; and listing, by the demand management center, release characteristics of the target release configuration version.
3. An ontology information version management and control device of a dispatching automation system, which is characterized by comprising:
the acquisition module is used for acquiring system files and version information of all the dispatching automation systems;
the creation module is used for creating an ontology base line version in a software version library based on the system file and version information thereof;
the manufacturing module is used for manufacturing a release configuration version based on the body baseline version and storing the release configuration version in the software version library;
the pulling module is used for pulling the release configuration version to an external verification environment through a platform program interface on the virtualized platform so as to verify the release configuration version;
the response module is used for responding to the update request of the target dispatching automation system, selecting a target release configuration version from the software version library and deploying the target release configuration version to the target dispatching automation system;
the software version library is configured with a version control center, a demand control center and a large file storage engine; the creation module comprises:
the first recording submodule is used for recording the system file into a metadata base of the software version base through the version control center;
the second recording submodule is used for recording the release characteristics of the version information through the demand management and control center; the release characteristics comprise version optimization information and program defect repair information;
the preprocessing sub-module is used for preprocessing and storing edition files through the large-scale file storage engine; the pretreatment comprises the following steps: at least one of decomposing, compressing or stitching the version file;
the system file version information includes: program files, configuration files, base data files, and run data files; the first recording submodule includes:
the rejecting unit is used for rejecting the operation data file in the system file version information to obtain rejected version information;
the abstract calculating unit is used for obtaining the abstract corresponding to the rejected version information in a abstract calculating mode and storing the abstract in the metadata base;
and the comparison unit is used for comparing all the abstracts, and if the same abstracts exist, the same abstracts are removed.
4. The ontology version management and control apparatus of a dispatch automation system according to claim 3, further comprising:
the difference analysis module is used for carrying out difference analysis on the current version of the target dispatching automation system and the target release configuration version through the version management and control center; and listing, by the demand management center, release characteristics of the target release configuration version.
5. An electronic device comprising a processor and a memory storing analyzer readable instructions that when executed by the processor perform the method of any of claims 1-2.
6. A storage medium having stored thereon an analysis computer program which, when executed by a processor, performs the method of any of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111043744.8A CN113760354B (en) | 2021-09-07 | 2021-09-07 | Ontology information version management and control method and device of dispatching automation system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111043744.8A CN113760354B (en) | 2021-09-07 | 2021-09-07 | Ontology information version management and control method and device of dispatching automation system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113760354A CN113760354A (en) | 2021-12-07 |
| CN113760354B true CN113760354B (en) | 2023-10-20 |
Family
ID=78793469
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111043744.8A Active CN113760354B (en) | 2021-09-07 | 2021-09-07 | Ontology information version management and control method and device of dispatching automation system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113760354B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398065B (en) * | 2022-03-24 | 2022-07-08 | Tcl通讯科技（成都）有限公司 | Micro front-end system updating method and device, electronic equipment and storage medium |
| CN117270943A (en) * | 2023-09-15 | 2023-12-22 | 上海子虔科技有限公司 | Cloud application file version management system and method based on metadata |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106886410A (en) * | 2017-01-06 | 2017-06-23 | 深圳云天励飞技术有限公司 | A kind of software version management system |
| US10732967B1 (en) * | 2019-02-22 | 2020-08-04 | Amazon Technologies, Inc. | Safe deployment of configurations to server fleets |
| CN112035365A (en) * | 2020-09-01 | 2020-12-04 | 中国银行股份有限公司 | Version deployment method and device supporting multiple test environments |
| CN112306552A (en) * | 2020-11-01 | 2021-02-02 | 国铁吉讯科技有限公司 | System software version management method, device and storage medium |
| WO2021129733A1 (en) * | 2019-12-24 | 2021-07-01 | 中兴通讯股份有限公司 | Cloud operating system management method and apparatus, server, management system, and medium |
-
2021
- 2021-09-07 CN CN202111043744.8A patent/CN113760354B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106886410A (en) * | 2017-01-06 | 2017-06-23 | 深圳云天励飞技术有限公司 | A kind of software version management system |
| US10732967B1 (en) * | 2019-02-22 | 2020-08-04 | Amazon Technologies, Inc. | Safe deployment of configurations to server fleets |
| WO2021129733A1 (en) * | 2019-12-24 | 2021-07-01 | 中兴通讯股份有限公司 | Cloud operating system management method and apparatus, server, management system, and medium |
| CN112035365A (en) * | 2020-09-01 | 2020-12-04 | 中国银行股份有限公司 | Version deployment method and device supporting multiple test environments |
| CN112306552A (en) * | 2020-11-01 | 2021-02-02 | 国铁吉讯科技有限公司 | System software version management method, device and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 一种能源管控系统多专业数据全息存储及全景事故反演方法;解凯等;《冶金自动化》(第04期);7-11 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113760354A (en) | 2021-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10540335B2 (en) | Solution to generate a scriptset for an automated database migration | |
| CN110309071B (en) | Test code generation method and module, and test method and system | |
| CN113760354B (en) | Ontology information version management and control method and device of dispatching automation system | |
| CN111813661B (en) | Global service data drive automatic test method, device, equipment and medium | |
| US11269822B2 (en) | Generation of automated data migration model | |
| CN108509185B (en) | System and method for arbitrary software logic modeling | |
| CN102902558A (en) | Project script file updating system and method as well as script file merging method and device | |
| CN112130891B (en) | Method and equipment for continuously deploying database | |
| CN111737227B (en) | Data modification method and system | |
| CN106802928B (en) | Power grid historical data management method and system | |
| CN113918532A (en) | Portrait label aggregation method, electronic device and storage medium | |
| CN110175917B (en) | Device and method for parameter graphical processing | |
| CN116821098A (en) | Data warehouse management method, service system and storage medium | |
| CN114519071A (en) | Generation method, matching method, system, device and medium of rule matching model | |
| CN113902531A (en) | Automatic generation system, method, electronic device and storage medium for bid document | |
| CN105589746B (en) | Virtual machine (vm) migration record management method and system | |
| US11934800B2 (en) | Generating metadata to facilitate code generation | |
| CN116820488B (en) | Method for linkage of research, development and deployment processes under DevOps system | |
| CN115829549B (en) | Aircraft maintenance process management method | |
| CN112579643B (en) | Information control method and device for relay protection module | |
| CN111078950B (en) | XML data access method based on full-service unified data center | |
| JP2024043844A (en) | Data processing method and data processing system | |
| CN117194265A (en) | Automatic industry template testing method and device based on data warehouse hive | |
| CN115480804A (en) | Incremental release updating method, equipment and medium | |
| CN117785840A (en) | Unmanned vehicle data attribute management method, device and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |