CN108876445A - A kind of data interoperation application based on battalion's distribution end-equipment common information model - Google Patents

Abstract

The invention discloses a data interoperability application based on a public information model of terminal equipment of a business and distribution network, which belongs to the technical field of electric power systems. The application includes: designing a unified interface specification system based on IEC-CIS for the data interoperability service application of the terminal equipment of the distribution network; researching the application architecture of the data interoperability service of the terminal equipment of the distribution network; researching and developing the data interoperability service of the terminal equipment of the distribution network application. The present invention aims at the current problem that when modeling low-voltage distribution network and modeling of marketing-side equipment and marketing service outlets, work is carried out in different departments and in stages, resulting in the isolation of data collection and modeling. Under the guidance of the unified interface system, the research on the framework system of the data interoperability service application of the terminal equipment of the operation and distribution network is carried out, so as to break the barriers of information interaction between the existing systems and realize the efficient modeling of the terminal equipment of the operation and distribution network.

Description

A data interoperability application based on the public information model of terminal equipment in the distribution network

technical field

The invention belongs to the technical field of power systems, and in particular relates to a data interoperability application based on a public information model of terminal equipment of a distribution network.

Background technique

Before the implementation of the integration work, the production management of marketing, distribution network and dispatching was relatively independent, and the information systems of each specialty were also independently designed, developed and operated independently, and there was a lack of data interaction mechanism and system interface between the systems. In order to break the "information island" of marketing, distribution network and dispatching, promote data sharing among marketing, distribution network and dispatching, and support the efficient operation of the "three sets and five majors" system, at the beginning of 2014, the State Grid Corporation issued the "About The "Notice on the Overall Implementation Work Plan for the Integration of Operations and Distribution" officially opened the prelude to the integration of operations and distribution. Through public lines, substations, branch boxes, ring network cabinets, low-voltage user towers, cables, access points, low-voltage metering boxes and marketing services The terminal data collection of main body space coordinates and association relations such as outlets, drawing of power grid equipment graphics, attribute entry, generation of electrical wiring diagrams, and application development of integrated functions, gradually realize the integration of operation, allocation, deployment, and integration; in early 2015, the Marketing Department of the State Grid Corporation issued another The "Notice on Accelerating the Integration of Operations, Distribution and Deployment" requires that based on a sound departmental horizontal coordination mechanism, combined with marketing customer service and basic business, to gradually improve customer service quality, meet customers' growing service needs, and further improve power supply service capabilities At the same time, in the mid-year work conference of State Grid Corporation of China in 2016, it was clearly pointed out that the follow-up needs to continue to improve the "three collections and five majors" system, strengthen resource allocation, professional collaboration, and promote the integration of business, deployment, and terminal integration.

In terms of collected data storage and interaction: Due to the individual needs of provincial (city) companies and factors such as multi-systems and multi-vendors, there are many differences and defects in the data source and modeling entry of grid standardization business. The same business data needs to be based on The needs of different business systems require repeated processing and sorting of various data models; and the modeling of low-voltage distribution network and the modeling of marketing-side equipment and service outlets need to be implemented in different departments and stages, and the distribution network and marketing data collection and modeling are isolated from each other , the asset demarcation point set by the operation inspection side is often inconsistent with the understanding of the marketing personnel, resulting in inefficiency in the data collection and modeling work at the end of the distribution network; in terms of safe storage and safe interaction: the data collection and During the modeling process, operators carry a large amount of plaintext paper or electronic version of power grid business data, which poses a great potential hidden danger to the security and confidentiality of power grid business data. Information security in the 21st century is the core issue that everyone pays attention to. , the power grid company is the focus of the public, and the security of information is very important.

Contents of the invention

The purpose of the present invention is to propose a data interoperability application based on the public information model of the terminal equipment of the distribution network, which is characterized in that it includes the following steps:

Step 1: Design a unified interface specification system based on IEC-CIS for the data interoperability application of the terminal equipment of the distribution network;

Step 2: Design the architecture system of the data interoperability application of the terminal equipment of the camp distribution network;

Step 3: On the basis of the previous steps 1 and 2, and constrained by the unified interface specification and the architecture system of the data interoperability application of the terminal equipment of the operation and distribution network, analyze the business requirements of the data interoperability application of the terminal equipment of the operation and distribution network.

The unified interface specification system of the IEC-CIS-based terminal equipment data interoperability application in the step 1 is based on the IEC 61970CIS international standard and a set of interfaces required for interaction between systems established in combination with the characteristics of the terminal equipment of the distribution network. Reference standards and specifications; applicable to the integrated modeling of PMS (production management system), GIS (geographic information system), marketing business application system, etc. Isolated islands enable each system to exchange or access publicly available data with other systems in a standard way; using a unified modeling entry is conducive to simplifying modeling work, reducing human intervention in modeling work, and finally realizing modeling integration; The unified interface specification includes five parts: public service interface specification, general data access interface specification, high-speed data access interface specification, time series data access specification, general event and subscription interface specification.

The architecture system used for data interoperability of the terminal equipment of the camp distribution network in step 2 is to study the current status of the existing operating system architecture of the terminal equipment management of the current camp and distribution network from a global perspective; the existing operating system architecture Including application architecture, data architecture, deployment architecture and security authentication mode; on this basis, carry out further research on the architecture system of data interoperability application of terminal equipment in the operation and distribution network.

The analysis of the business requirements of the terminal equipment data interoperability application in the step 3 mainly includes the analysis components from the public information model to the private data model of each existing business system, and the connection between the private data model of each existing business system and the public information model. Aggregation components and on this basis, distribution network GIS model data interoperability service, equipment asset model data interoperability service, marketing service resource data model interoperability service and marketing GIS model data interoperability service.

The architecture of the data interoperability application of the terminal equipment of the marketing and distribution network that is further studied is based on the IEC-CIM/CIS61970 standard system, and provides public services that comply with IEC-61970/GDA (General Data Access)/HSDA (High Speed Data Access)/TSDA (Time-series data access)/GES (General Event and Subscription) service, the overall architecture adopts the idea of SOA architecture to build a general and referential system architecture; the system architecture is divided into business data service layer, IEC-CIM service layer, IEC -CIS service layer and business application layer; In order to solve the problems faced by data sharing and interoperability, this architecture starts from practical problems and uses SpringMVC framework, Hibernate persistence framework technology and Web Services technology to build a new system architecture. The system architecture should be open, based on the IEC61970 standard and future-oriented; so that the system it builds has high reliability, high scalability and strong adaptability.

The system architecture is divided into business data service layer, IEC-CIM service layer, IEC-CIS service layer, business application layer and business data service layer: the following is a specific description:

The business data service layer is the basis for the business system to provide the terminal equipment data of the distribution network. In order to ensure the real-time realization of the data, the data push API service is provided externally through WebServices. According to the defined interface rules, the marketing, electric power GIS, and PMS2.0 Push data to data interaction middleware for splitting and conversion;

IEC-CIM service layer:

It mainly analyzes, stores and distributes the data obtained from the business data service layer, which includes CIM physical database, data interaction middleware, and transaction database;

Among them, the data interaction middleware receives the data pushed by the business data service layer, and the middleware parses the data and stores it in the CIM physical table. On the contrary, when the data in the CIM physical database changes, the data is passed to the data interaction In the middle, the middleware aggregates the transaction data and distributes it to the transaction database or the business system database table of the business data service layer;

IEC-CIS service layer

Based on the IEC-CIS standard, public services, GDA, HSDA, GES, and TSDA services are realized. WebServices is used to encapsulate the implementation methods and provide general data access, data read and write service APIs.

The beneficial effect of the present invention is that the unified interface specification system for the data interoperability application of the terminal equipment of the distribution network designed by the present invention is based on the IEC 61970CIS international standard, and a set of interfaces required for interaction between systems established in combination with the characteristics of the terminal equipment of the distribution network reference standards and specifications. It is suitable for the integrated modeling of PMS, GIS, marketing business application system and other terminal-related systems of the distribution network, breaking the information islands among management systems of terminal equipment objects of the distribution network, so that each system can exchange or exchange with other systems in a standard way Access publicly available data. Using a unified modeling entry is conducive to simplifying the modeling work, reducing human intervention in the modeling work, and finally realizing the integration of modeling.

Description of drawings

Figure 1 is a schematic diagram of the architecture design of the data interoperability application of the terminal equipment of the distribution network.

Figure 2 is a system diagram of the overall architecture of the interoperable service application.

Figure 3 is a flowchart of data interoperability.

Detailed ways

The present invention proposes a data interoperability application based on the public information model of terminal equipment in the distribution network, which includes the following steps:

Step 1: Design a unified interface specification system based on IEC-CIS for the data interoperability application of the terminal equipment of the distribution network;

Step 2: Design the architecture system of the data interoperability application of the terminal equipment of the camp distribution network;

Step 3: On the basis of the previous steps 1 and 2, and constrained by the unified interface specification and the architecture system of the data interoperability application of the terminal equipment of the operation and distribution network, analyze the business requirements of the data interoperability application of the terminal equipment of the operation and distribution network.

The present invention will be described in detail below in conjunction with the accompanying drawings and embodiments.

Figure 1 is a schematic diagram of the architecture design of the data interoperability application of the terminal equipment of the distribution network. Shown in the figure is

Specifically include:

The design described in step 1 is based on the IEC-CIS unified interface specification system for the data interoperability application of the terminal equipment of the distribution network. reference standards and specifications. It is applicable to the integrated modeling of PMS, GIS, marketing business application system and other terminal-related systems of the distribution network; unified interface specifications include public service interface specifications, general data access interface specifications, high-speed data access interface specifications, time series data access specifications, and general events and the five parts of the subscription interface specification, which are described in detail below:

Public service interface specification:

This part normatively includes the modeling methods included in the resource identifier module RIM (Resource Identifiers Module) of the UMS (Utility Management System) data access facility DAF (Data Access Facility) by reference. This RIM module defines the generic methods that should be used to identify CIM resources. The DAF resource identifier module uses a universal resource identifier URI (Universal ResourceIdentifier, URI) and a resource ID to identify power enterprise resources. A URI is a string used as a name conforming to the Universal Resource Identifier standard. For example the URI is "http//utility.com/Planning/Production/CIM-schemacimu09a#/Transformer" for the Transformer class. Resource IDs, unlike URIs, consist of more compact 128-bit (16-byte) ID numbers. The DAF specification defines resource ID and URI arrays with resource ID sequences and URI sequences, respectively. In practice, it may be that a unique resource ID is associated with multiple URIs; in order to handle this situation, the Extended Resource ID Service (Extended ResourceID Service) adds a view name parameter to the DAF resource ID, which is used to determine the URI. scope. The Extended Resource ID Service can also set a given view name for a URI and assign a resource ID on the server.

Generic Data Access (GDA)

General data access mainly includes three parts: read access, update access, and events. The essence of read access is a query operation on resource modules. Including query, filtering query, and expanding resource query. Each operation in the resource query service interface performs a single query. Each resource description returned by a query contains values for a subset of the properties queried. The returned property values are listed in the same order as the properties passed to the query, although some of these properties may be omitted. If a property value is not available from the data provider for a particular resource, or if the property identifier is not recognized, the property value is ignored. This feature enables multiple query services to be combined into a single query, where each query service answers part of the combined query. The Filtered Query module enhances access to metadata and instance data maintained in the GDA Read Access Server. In particular, the GDA filter query module extends the GDA resource query interface by adding specified resource query attribute values to limit the resource query function. From the perspective of structured query language SQL (structured query language,), adding a filter condition in the GDA reader is equivalent to adding a "where" clause. GDA filters allow customers to more precisely define the information they are interested in. For the methods in the GDA resource query service interface, the GDA filter resource query service interface adds filters based on attribute values. Extended Resource Query Service (ExtendedResourceQueryService) allows users to connect data, rather than just query along a path as provided by GDA resource query module and GDA filter query module. In this way, for example, one query can return not only breaker data for a selected substation, but also data for that substation in the same query. The GDA extended resource query module provides the UML of the GDA extended query interface for implementing query filtering and joining.

The GDA update module extends GDA read access by providing limited write access to metadata and instance data. The GDA update interface provides the following functions:

1) Object update: From the point of view of common service, it is the ability to update the attribute values of existing resources.

2) Multi-object update: Provides the ability to update a group of objects in one operation.

3) Control of object life cycle: Provides the ability to create and destroy objects accessed through GDA. From a public point of view, it is the ability to create and delete resources.

4) Metadata update: defined as creating, deleting and updating data; from the point of view of public services, it refers to creating, deleting and updating resources of type Class and Property.

5) Encapsulate existing systems: It must be able to implement interfaces for various systems.

6) Multi-client, multi-provider and concurrency: must meet the interaction requirements between multiple clients and multiple data providers. When updating is considered, this requirement is interpreted as having to have some form of concurrency control.

The resource update function is provided by a new service ResourceUpdateService, which is defined as an interface in the GDAUpdate module.

GDA events are an extension of DAF events with a stronger mechanism. The GDA event package provides methods to notify clients of specific data changes and ensure consistent data access. The GDA Events module allows embedding the Resource ID of an object instance into an event as a reminder to the client about the nature of the change.

High Speed Data Access (HSDA)

High-speed data access specifies a common interface for efficient data exchange, fully considering the delay caused by cross-LAN data interaction. The HSDA data model describes how the data seen through the HSDA interface is organized within the server. The data mainly includes four parts:

1) Type (type): describes the node (Nodes). So Type is metadata;

2) Property (nature): describes items (Items) so Property is metadata:

3) Node (node): describe the data object that can be accessed by HSDA. In a hierarchy, nodes can contain other nodes. Nodes can also contain items;

4) Item (item): describes the data value that can be accessed with HSDA. Items are always contained by a node.

In the data message sent from the HSDA server to the client, the payload contains some arrays, and each array includes the following contents:

1) an item ID that uniquely identifies the item within the server;

2) a data value;

3) The quality of the data value, that is, whether the value is reliable. If the value is invalid, this quality also indicates the reason why the value is invalid. The default quality code is "Good", which means the value is valid;

4) A time stamp indicating when the value was last updated;

5) An item ID that uniquely identifies the item within the client.

Generic Events and Subscriptions (GES)

GES can be used to build a document exchange system. The high-speed data access (HSDA) interface in the previous article supports the subscription of measurements, parameters, and other simple data, while the GES interface allows components to publish and subscribe to non-measurement documents (such as work orders) instead of measurement point collections. The event communication interface allows components to publish and subscribe to documents such as work orders without subscribing to each work order property. GES Simple Events may include a document-oriented payload that can be sent or received in any Control Center application. In this way, GES Simple Events can be used to access the entire Common Information Model (CIM). The data transmitted through the GES interface is independent of the GES Interface Definition Language (IDL), that is, GES can be used to display and transmit any information exchange model.

The schema for GES simple events is generic. GES simple events have the following characteristics:

1) Source (Source): A reference to the object that generated the event, this can be an item (such as a specific measurement), or a more general CIM class name, or an application class.

2) Source pathname (Source pathname): The pathname of the source fully limited to the IECTC57 physical model.

3) Time stamp (Time stamp): the time when the event occurred.

4) Message (Message): A text string describing the event.

5) Main category: For simple events, this field contains the resource ID of the simple event.

6) Category (Category): the resource ID of the event type. Each category corresponds to a specific event pattern.

7) Category name (Category name): The name of the event type.

8) Severity: The server prompts the severity of the event.

9) Properties: a list of mapped or indexed properties.

GES subscription filtering provides the ability to specify property values that are used to qualify subscriptions. In SQL terms, adding a GES filter is equivalent to adding a "where" clause. For example, a Subscriber that specifies that it wants to receive "New Transformer Installed" events also specifies that it only wants to receive "New Transformer Installed" events related to transformers from a given manufacturer.

A GES Subscription object maintains a filter specification established by the client. Filters are used to specify what notifications are sent to clients. A server may support different filtering functions, and a client can query what filtering functions are supported by the Subscription Home object. Subscription headquarters can also be used to create any number of subscription manager objects. Each subscription manager is associated with a client that implements a callback object so that the server can send alerts and event notifications to the client. GES event communication does not support the "wildcard" function in the topic subscription string. For example, GES event communication allows components to subscribe to events based on event category (such as "transformer installation request") or based on topics (such as all work orders for circuit breakers), but there is no way to select all areas under a given level. This specification extends GES event communication to support wildcard functionality for topic-based filtering. Adding support for wildcards in region paths does not change the GES Events interface. This specification requires a well-known wildcard URI. The URI for wildcards is http://omg.org/schema/GES#WILDCARD.

Time Series Data Access (TSDA)

Time-series data access specifies an efficient transmission interface for time-series data in a distributed environment. In this access mode, the latency of data transfer is directly related to the data volume. This access mode supports playback capabilities for time series data. The following objects are mainly defined in time series data:

1) Type: Describes objects with the same time series characteristics (such as the time interval between calculations of values or values). Therefore, TSDA Type is different from HSDA Type. HSDA Type mainly describes the types defined in CIM, while TSDA Type has no corresponding description in CIM. However, TSDA Type can generally refer to HSDA Type.

2) Property: Describes the item (Item) recorded as a time series. TSDA Property can usually refer to HSDA Property. A Type can have any number of Properties.

3) ItemAttributeDeftnition: Describe ItemAtlributes specific to time series data. ltemAttributeDeflnition is similar to Property in describing time series data, the difference is that its data is specific to a certain time series. A Type usually has several ItemAttributeDefinition.

4) ItemAttribute: Describes how the item is handled in the TSDA server, that is, it is metadata for the Item time series. Therefore, ItemAttribiite cannot be accessed with HSDA. Since ItemAttribute may change at any time, it is a time series itself, that is, ItemAttributeValue.

5) Node: is an object with one or more items, which are recorded in time series. A TSDA Node generally has a corresponding HSDA Node.

6) Item: It is an object with time series, that is, ItemValue. — An Item has multiple ItemAttributes describing the time series.

7) ItemValue: It is the value of time scale and quality code. Item has a time series consisting of ItemValue.

8) ModifiedItemValue: It is the modification made to ItemValue. Since ItemValue is not allowed to be changed, ModifiedltemValue is used to record the modification of ItemValue.

9) Annotation: Annotation text that can be added to ItemValue.

10) AggregateDefinition: Describes the calculation of time series data, such as average value, maximum value, etc.

In order to meet the needs of information interaction with the power grid GIS, it is necessary to expand the GIS communication mechanism not covered by the original specification in the official version of the CIS interface specification. Compared with real-time GIS, meteorological GIS and other systems, power grid GIS does not emphasize concepts such as space-time transformation and geographic object events. The power grid GIS pays more attention to the maintenance of the ledger information of the physical equipment of the power grid and the static display of the geographical information of the equipment. Therefore, on the basis of the original CIS data model, GIS information can be understood as an attribute of physical equipment and added to the original model. The added content is shown in the table below.

name the code state STATE_ID symbol angle FHJD connection information CONNECTION Whether to label SFBZ callout size BYZGR Callout color BYZ Label orientation BYZGR Arrangement PLFS Number of words per line DHZS longitude POS_X latitude POS_Y elevation ORIGIN_POS_Z symbol size FHDX spatial information SHAPE

Figure 2 shows the architecture system of the data interoperability application of the terminal equipment of the battalion and distribution network described in step 2. This architecture system needs to start from a global perspective to study the application architecture and data of the current terminal equipment management of the battalion and distribution network in the operating system. Based on the status quo of existing system architectures such as architecture, deployment architecture, and security authentication mode, the architecture system design of data interoperability applications for terminal equipment in the distribution network is carried out.

The general design principle of the above-mentioned interoperable application construction is: follow the service-oriented architecture (SOA) idea, strictly implement the IEC61970/61968 standard, and apply to the specific business process of the relevant business data of the terminal equipment, so as to provide a more refined and comprehensive service for the terminal equipment of the distribution network. Intelligent operation and management provide technical support.

1) Standardization: Follow the norms and standards of IEC61970/61968/61850 to realize the standardization of modeling, data exchange and application function interface.

2) Openness: It adopts an open architecture, provides an open environment, can support multiple hardware platforms, and has uniform interface standards between all functional modules, supports the development of user application software programs, and ensures that it can be interconnected and integrated with other systems , or it is very convenient to realize the interface with other systems.

3) Scalability: The system can adapt to the growing needs of the power system and the changing business requirements of the dispatch center, enabling online expansion and upgrading and flexible configuration of applications.

4) Reliability: Provides a fault isolation mechanism, removing faults will not affect the normal operation of other nodes, and ensures a fast and stable fault recovery process, providing convenient and reliable backup and recovery means

5) Security: In accordance with the requirements for the security protection of the power secondary system, the physical security, logical security, data transmission security and data use security of the system data are fully considered.

The architecture of the data interoperability application of the terminal equipment of the distribution network shown in Figure 3 is based on the IEC-CIM/CIS61970 standard system, and provides public services/GDA/HSDA/TSDAGES services in compliance with IEC-61970; its architecture adopts the SOA architecture as a whole. Build a common, referential system architecture. In order to solve the problems faced by data sharing and interoperability, this architecture starts from the actual problems. The interoperability implementation adopts SpringMVC framework, Hibernate persistence framework technology, WebServices and other technologies to build a new system architecture. The system architecture should have an open , based on the IEC61970 standard and future-oriented features, so that the system built on this architecture has high reliability, high scalability and strong adaptability. The system architecture is divided into business data service layer, IEC-CIM service layer, IEC-CIS service layer, business application layer and business data service layer: the following is a specific description:

The business data service layer is the basis for the business system to provide the terminal equipment data of the distribution network. In order to ensure the real-time realization of the data, the data push API service is provided externally through WebServices, and the marketing, electric power GIS, and PMS2.0 follow the defined interface rules. Push data to data interaction middleware for splitting and transformation.

IEC-CIM service layer:

It mainly parses, stores and distributes the data obtained from the business data service layer, which includes CIM physical database, data interaction middleware, and transaction database.

Among them, the data interaction middleware receives the data pushed by the business data service layer, and the middleware parses the data and stores it in the CIM physical table. On the contrary, when the data in the CIM physical database changes, the data is passed to the data interaction In the middle, the middleware aggregates the transaction data and distributes it to the transaction database or the business system library table of the business data service layer.

IEC-CIS service layer

Based on the IEC-CIS standard, public services, GDA, HSDA, GES, and TSDA services are realized. WebServices is used to encapsulate the implementation methods and provide general data access, data read and write service APIs.

In order to ensure the real-time and universality of data, the splitting process uses data interaction middleware, which can support two ways of active push and receiving push. To ensure real-time data transmission, interoperable application services take priority The push interface provided by the interactive middleware actively pushes the terminal equipment data stored in the business system to the middleware. After the middleware receives the data, it splits and stores the data into the CIM physical database according to the established relationship table. middle.

When other application systems call the IEC-CIS read-write interface, the data in the CIM physical database is modified through the CIS interface. At this time, the data transmission interface receives the abnormal data, and the interface will transmit the abnormal data to the data interaction in real time. Middleware, the middleware aggregates the data according to the established business table association relationship, and stores the transaction data in the transaction database. In order to apply to more application scenarios, the aggregated data provides two methods during data transmission. The first is that the data aggregated by the middleware is read regularly by the business database, and the second is that the business system provides interface rules and the middleware distributes them in real time. The two methods can be selected according to the actual business needs.

The CIS implementation of IEC 61970 mainly includes three parts: middleware platform, CIM data background, and CIS general service. Among them, the CIS general service is realized on the CIM data background, so the CIM data background is the key to the realization of CIM/CIS. In the past data platform construction, the CIM data was stored in a self-developed/modified 3D real-time database. Since the original real-time database was based on a hierarchical model, it used a static allocation of memory, and it was necessary to manually specify the initial value of each table. The scale and attribute thickness require different configurations for systems of different scales, often resulting in too much memory consumption, making the entire system impractical. However, the CIM database realized by the present invention is realized on a mature relational database, and has strong practicability and operability.

Relational databases have the characteristics of complete functions and good openness. In the process of implementing interoperable service applications, we gradually realized that if we can make full use of the powerful functions of relational databases, we can reduce the difficulty of system development and improve the openness and stability of the entire system. Using relational database to store CIM data, the main task is to establish the mapping between CIM object-oriented model and relational database, and describe the CIM model in relational database. At present, the mainstream commercial databases are all based on the relational database model, and the entire CIM is described in UML language, using an object-oriented expression. Although each specific database product (such as Oralce, Sybase, MS Sql Server) supports object-oriented characteristics in its own way to a certain extent, or supports XML-oriented data schemas, considering portability and consistency, the present invention still CIM data is stored using a typical relational model.

In step 3, on the basis of the previous steps 1 and 2, and constrained by the unified interface specification and the architecture system of the data interoperability application of the terminal equipment of the operation and distribution network, analyze the business requirements of the data interoperability application of the terminal equipment of the operation and distribution network.

The work content of this part mainly includes, on the basis of completing the unified interface specification system of the terminal equipment data interoperability service application based on IEC-CIS and the framework system of the data interoperability service application of the terminal equipment of the operation and distribution network. The application requirements for data interoperability of distribution network terminal equipment, sorting out business requirements to form demand specifications, and based on the demand specifications, carry out the overall design and detailed design of data interoperability service applications for distribution network terminal equipment. Demonstrate and review the design, and complete the code implementation and system testing of the data interoperability service application of the terminal equipment of the distribution network; it mainly includes the analysis components from the public information model to the private data model of each existing business system, and the private data model of each existing business system. Aggregation components from data model to public information model and based on it, distribution network GIS model data interoperability service, equipment asset model data interoperability service, marketing service resource data model interoperability service, marketing GIS model data interoperability service, etc. .

Claims (6)

1. A data interoperability application based on the public information model of the terminal equipment of the distribution network, characterized in that it comprises the following steps: Step 1: Design a unified interface specification system based on IEC-CIS for the data interoperability application of the terminal equipment of the distribution network; Step 2: Design the architecture system of the data interoperability application of the terminal equipment of the camp distribution network; Step 3: On the basis of the previous steps 1 and 2, and constrained by the unified interface specification and the architecture system of the data interoperability application of the terminal equipment of the operation and distribution network, analyze the business requirements of the data interoperability application of the terminal equipment of the operation and distribution network. 2. The data interoperability application based on the public information model of the terminal equipment of the distribution network according to claim 1, characterized in that, in the step 1, the unified interface specification for the data interoperability application of the terminal equipment of the distribution network based on IEC-CIS The system is based on the IEC 61970 CIS international standard and a set of reference standards and specifications for the interfaces required for interaction between systems established in combination with the characteristics of terminal equipment in the distribution network; it is suitable for production management system PMS, geographic information system GIS, marketing business application system, etc. The integrated modeling of related systems at the end of the camping and distribution network breaks the information islands among the various management systems of the terminal equipment objects of the camping and distribution network, enabling each system to exchange or access publicly available data with other systems in a standard way; use a unified modeling entry , which is conducive to simplifying the modeling work, reducing human intervention in the modeling work, and finally realizing the integration of modeling; the unified interface specification includes public service interface specification, general data access interface specification, high-speed data access interface specification, time series data access There are five parts of specification, common event and subscription interface specification. 3. The data interoperability application based on the public information model of the terminal equipment of the camp and distribution network according to claim 1, characterized in that, the framework system for data interoperability of the terminal equipment of the camp and distribution network in the step 2 is from a global perspective , to study the status quo of the existing operating system architecture of the current terminal equipment management of the operation and distribution network; the existing operation system architecture includes application architecture, data architecture, deployment architecture and security authentication mode; on this basis, the operation and distribution network terminal Further research on the architecture system of device data interoperability applications. 4. The data interoperability application based on the public information model of the terminal equipment of the marketing and distribution network according to claim 1, wherein the analysis of the business requirements of the data interoperability application of the terminal equipment of the marketing and distribution network in the step 3 mainly includes public information Analysis components from models to private data models of existing business systems, aggregation components from private data models of existing business systems to public information models, and distribution network GIS model data interoperability services and equipment asset model data interoperability on this basis Service, Marketing Service Resource Data Model Interoperability Service and Marketing GIS Model Data Interoperability Service. 5. According to the data interoperability application based on the public information model of the terminal equipment of the camp distribution network according to claim 3, it is characterized in that the framework of the data interoperability application of the terminal equipment of the camp distribution network for further research is based on IEC-CIM/CIS61970 The standard system provides public service/GDA/HSDA/TSDA/GES services in compliance with IEC-61970. The overall architecture adopts the idea of SOA architecture to build a general and referential system architecture; the system architecture is divided into business data service layer, IEC- CIM service layer, IEC-CIS service layer and business application layer; in order to solve the problems faced by data sharing and interoperability, this architecture starts from practical problems and adopts SpringMVC framework, Hibernate persistence framework technology and Web Services technology to build a new The system architecture should be open, based on the IEC61970 standard and future-oriented; so that the system it builds has high reliability, high scalability and strong adaptability; GDA is general data access, HSDA is High-speed data access, TSDA for time series data access, and GES for general events and subscriptions. 6. According to the data interoperability application based on the public information model of the terminal equipment of the distribution network according to claim 5, it is characterized in that the system architecture is divided into business data service layer, IEC-CIM service layer, IEC-CIS service layer, Business application layer business data service layer: the following will be specifically explained: The business data service layer is the basis for the business system to provide the terminal equipment data of the distribution network. In order to ensure the real-time realization of the data, the data push API service is provided externally through WebServices. According to the defined interface rules, the marketing, electric power GIS, and PMS2.0 Push data to data interaction middleware for splitting and conversion; IEC-CIM service layer: It mainly analyzes, stores and distributes the data obtained from the business data service layer, which includes CIM physical database, data interaction middleware, and transaction database; Among them, the data interaction middleware receives the data pushed by the business data service layer, and the middleware parses the data and stores it in the CIM physical database table. On the contrary, when the data in the CIM physical database changes, the data is passed to the data In the middle of the interaction, the middleware aggregates the transaction data and distributes it to the transaction database or the business system database table of the business data service layer; IEC-CIS service layer Based on the IEC-CIS standard, public services, GDA, HSDA, GES, and TSDA services are realized. WebServices is used to encapsulate the implementation methods and provide general data access, data read and write service APIs.