CN107948294B - CIS service maintaining method based on IEC61970 standard and CIS server - Google Patents
CIS service maintaining method based on IEC61970 standard and CIS server Download PDFInfo
- Publication number
- CN107948294B CN107948294B CN201711228419.2A CN201711228419A CN107948294B CN 107948294 B CN107948294 B CN 107948294B CN 201711228419 A CN201711228419 A CN 201711228419A CN 107948294 B CN107948294 B CN 107948294B
- Authority
- CN
- China
- Prior art keywords
- cis
- service
- server
- client
- data
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention discloses a CIS service maintaining method and a CIS server. In the invention, after the connection between the CIS server and the CIS client is established, the data and the callback object required by the transient service creation are stored and stored in the local file of the server in a serialized manner, after the CIS server is restarted, the data and the callback object required by the transient service creation are directly deserialized, the same transient service is reconstructed without establishing the connection with the CIS server again according to the step of establishing the connection with the CIS server by the CIS client and detecting by the CIS client, therefore, the CIS client is not required to be changed, the development complexity of the CIS client is reduced, the burden of calling a CIS server on the CIS server is reduced, the problem that the burden of the CIS server and the complexity of the CIS client are increased when the existing CIS service is disconnected and reconnected is solved, and the CIS server can not actively restore the connection, and the CIS client is required to reestablish the connection with the CIS server according to the step of establishing the connection with the CIS server.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a CIS service maintaining method and a CIS server.
Background
The IEC61970 series of standards have been implemented for many years as a standard way for data exchange between information systems, and as the IEC61970 series of standards mature, more and more systems adopt CIS interfaces for data access.
In actual use, the CIS client is connected with the CIS server, and after data initialization is performed, data needing to be concerned is subscribed, and data change monitoring is performed.
When the CIS server is restarted due to function repair or program abnormality, the CIS server is disconnected from the CIS client, session information (a session name, a set value, and session callback service information provided by the client) and subscription information and subscription callback service information depending on the session are lost, and changed subscription data cannot be continuously pushed.
The existing CIS interface is implemented based on the CORBA technology, and services such as session services created by a server for a CIS client are generally defined as transient services, that is, service addresses corresponding to session objects created by two identical requests (with identical session names and identical settings) are also different, and after the CIS server is restarted, even if the client can detect disconnection and then recover, the client must re-establish connection with the server according to the step of establishing connection with the server, subscribe to relevant data changes, and the implementation is complex.
Because the CIS server is restarted due to function repair or program abnormality and the like, in order to ensure that the CIS client can continuously acquire subscription information, the CIS client must judge whether to disconnect with the CIS server by regularly calling a method of the CIS server, and the CIS regularly calling the CIS server inevitably increases the burden of the CIS server and also increases the complexity of the CIS client; on the other hand, the CIS server cannot restore the connection actively, and needs to wait for the reconnection of the CIS client, and due to the characteristics of the transient service, the transient service created by the CIS client by establishing the session originally is unavailable, and the session needs to be reestablished, so that a new transient service is created.
Therefore, the technical problems that the load of the CIS server and the complexity of the CIS client are increased when the CIS service is disconnected and reconnected currently, the CIS server cannot actively restore the connection, and the CIS client needs to reestablish the connection with the CIS server according to the step of establishing the connection with the CIS server are caused.
Disclosure of Invention
The invention provides a CIS service keeping method and a CIS server, and solves the technical problems that the burden of the CIS server and the complexity of a CIS client are increased when the existing CIS service is disconnected and reconnected, the CIS server cannot actively restore the connection, and the CIS client needs to reestablish the connection with the CIS server according to the step of reestablishing the connection with the CIS server.
The invention provides a CIS service maintaining method, which comprises the following steps:
s1: receiving a connection request of a CIS client, creating a transient service according to the connection request, and recording data and callback objects required by creating the transient service;
s2: serializing and storing data and callback objects required by creating transient service to a local file of a server;
s3: when restarting occurs, detecting a serialized file in a local file of the server after restarting, establishing the same transient service as before restarting through the serialized file corresponding to the data required by the transient service created by deserialization, and registering a callback object through the serialized file corresponding to the deserialization callback object;
s4: and establishing connection with the corresponding CIS client according to the callback object, and sending the data subscribed by the CIS client to the CIS client according to a subscription object in the data required by the transient service creation.
Preferably, step S1 specifically includes:
s101: making a Hash code for each transient service;
s102: receiving a connection request of a CIS client, creating a transient service according to the connection request, detecting whether the Hash changes, and if so, executing a step S103;
s103: data and callback objects needed to create the transient service are recorded.
Preferably, step S4 specifically includes:
s401: establishing connection with a corresponding CIS client according to the callback object;
s402: and detecting whether the data subscribed by the CIS client changes according to a subscription object in the data required for creating the transient service, and if so, sending the data subscribed by the CIS client to the CIS client.
Preferably, step S2 specifically includes:
and serializing and storing data and callback objects required by creating the transient service to a local file of the server through a CDR coding method.
Preferably, the data required for creating the transient service specifically includes: session name, session settings, subscription object, and service address.
The present invention provides a CIS server, including:
the transient recording module is used for receiving a connection request of the CIS client, creating a transient service according to the connection request, and recording data and callback objects required by the creation of the transient service;
the serialization module is used for serializing and storing data and callback objects required by creating the transient service into a local file of the server;
the deserializing module is used for detecting a serialized file in a local file of the server after restarting when restarting occurs, constructing the same transient service as before restarting through the serialized file corresponding to the data required by the deserializing creating the transient service, and registering a callback object through the serialized file corresponding to the deserializing callback object;
and the subscription pushing module is used for establishing connection with the corresponding CIS client according to the callback object and sending the data subscribed by the CIS client to the CIS client according to the subscription object in the data required by the transient service creation.
Preferably, the transient recording module specifically includes:
the encoding submodule is used for formulating a Hash code for each transient service;
the detection submodule is used for receiving a connection request of the CIS client, creating a transient service according to the connection request, detecting whether the Hash changes or not, and if so, executing the step S103;
and the recording submodule is used for recording data and callback objects required by the transient service creation.
Preferably, the subscription pushing module specifically includes:
the callback submodule is used for establishing connection with the corresponding CIS client according to the callback object;
and the pushing sub-module is used for detecting whether the data subscribed by the CIS client changes according to a subscription object in the data required for creating the transient service, and if so, sending the data subscribed by the CIS client to the CIS client.
Preferably, the serialization module is specifically configured to store the data and the callback object required for creating the transient service in the server local file in a serialized manner by using a CDR encoding method.
Preferably, the data required for creating the transient service specifically includes: session name, session settings, subscription object, and service address.
According to the technical scheme, the invention has the following advantages:
the invention provides a CIS service maintaining method, which comprises the following steps: s1: receiving a connection request of a CIS client, creating a transient service according to the connection request, and recording data and callback objects required by creating the transient service; s2: data and callback objects required by creating transient service are stored in a server local file through CDR coding serialization; s3: when restarting occurs, detecting a serialized file in a local file of the server after restarting, establishing the same transient service as before restarting through the serialized file corresponding to the data required by the transient service created by deserialization, and registering a callback object through the serialized file corresponding to the deserialization callback object; s4: and establishing connection with the corresponding CIS client according to the callback object, and sending the data subscribed by the CIS client to the CIS client according to a subscription object in the data required by the transient service creation.
After the connection between the CIS server and the CIS client is established, the CIS server actively stores data and callback objects required by transient service creation and serializes the data and the callback objects to be stored in a server local file, when the CIS server is restarted due to function repair or program abnormality and the like, the data and the callback objects required by transient service creation can be directly deserialized, the same transient service as that before the CIS server is restarted is reconstructed, the CIS client is not required to establish the connection with the CIS server again according to the step of establishing the connection with the CIS server, and the detection is not required by the CIS client, so the CIS client is not required to be modified, the development complexity of the CIS client is reduced, the burden of the CIS server on the CIS server due to the calling of the CIS client for the detection is reduced, and the increase of the burden of the CIS server and the complexity, and the CIS server can not actively restore the connection, and the CIS client is required to reestablish the connection with the CIS server according to the step of establishing the connection with the CIS server.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
FIG. 1 is a schematic flow chart diagram illustrating one embodiment of a CIS service retention method provided in the present invention;
FIG. 2 is a schematic flow chart illustrating another embodiment of a CIS service maintenance method according to the present invention;
fig. 3 is a schematic structural diagram of an embodiment of a CIS service holding device provided by the present invention.
Detailed Description
The embodiment of the invention provides a CIS service maintaining method and a CIS server, and solves the technical problems that when the existing CIS service is disconnected and reconnected, the burden of the CIS server and the complexity of a CIS client are increased, the CIS server cannot actively restore the connection, and the CIS client needs to reestablish the connection with the CIS server again according to the step of establishing the connection with the CIS server.
In order to make the objects, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the embodiments described below are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, an embodiment of the present invention provides an embodiment of a CIS service maintaining method, including:
step 101: receiving a connection request of a CIS client, creating a transient service according to the connection request, and recording data and callback objects required by creating the transient service;
it should be noted that CIS (Component Interface Specification) is a Component Interface Specification for transmitting power system data specified by IEC61970, 401,403,404,405,407 standards;
according to the connection request of the CIS client, the corresponding on-site service is created in the CIS server, and data and callback objects required by creating the transient service are recorded.
Step 102: serializing and storing data and callback objects required by creating transient service to a local file of a server;
it should be noted that, after receiving a connection request of the CIS client, creating a transient service according to the connection request, and recording data and a callback object required for creating the transient service, the CIS server may create a corresponding on-site service in the CIS server according to the connection request of the CIS client, and record data and a callback object required for creating the transient service.
Step 103: when restarting occurs, detecting a serialized file in a local file of the server after restarting, establishing the same transient service as before restarting through the serialized file corresponding to the data required by the transient service created by deserialization, and registering a callback object through the serialized file corresponding to the deserialization callback object;
it should be noted that, after the CIS server is restarted, a serialized file in a local file is detected, if the serialized file exists, the serialized file is deserialized to obtain data and a callback object required by creating a transient service, the same transient service as that before the CIS server is restarted is constructed according to the data required by creating the transient service, and a corresponding CIS client is connected through the callback object;
and because the constructed transient service is consistent with the transient service before the CIS server is restarted, the CIS client can be directly connected with the CIS server through the same service address without a complicated reconnection step.
Step 104: and establishing connection with the corresponding CIS client according to the callback object, and sending the data subscribed by the CIS client to the CIS client according to a subscription object in the data required by the transient service creation.
After the CIS server and the CIS client recover contact, the CIS server sends data subscribed by the CIS client to the CIS client according to a subscription object in the data required for creating the transient service.
In the embodiment, after the connection between the CIS server and the CIS client is established, data and callback objects required by transient service creation are actively stored and stored in a server local file in a serialized mode, when the CIS server is restarted due to function repair or program abnormity, the data and the callback objects required by the transient service creation can be directly deserialized, the same transient service as that before the CIS server is restarted is rebuilt, and the CIS client does not need to establish the connection with the CIS server again according to the step of establishing the connection with the CIS server;
the detection is not needed through the CIS client, so the CIS client is not required to be changed, the development complexity of the CIS client is reduced, and the burden of the CIS server caused by calling the CIS server for detection by the CIS client is reduced;
the method solves the technical problems that the load of the CIS server and the complexity of the CIS client are increased by the existing CIS service maintaining method, the CIS server cannot actively recover the connection, and the CIS client is required to reestablish the connection with the CIS server according to the step of establishing the connection with the CIS server.
The above is an embodiment of the CIS service maintaining method provided by the embodiment of the present invention, and the following is another embodiment of the CIS service maintaining method provided by the embodiment of the present invention.
Referring to fig. 2, another embodiment of the present invention provides a CIS service maintaining method, including:
step 201: making a Hash code for each transient service;
the Hash code is an algorithm, and objects in the same class have different Hash codes as much as possible according to different characteristics of the objects.
Step 202: receiving a connection request of a CIS client, creating a transient service according to the connection request, detecting whether the Hash changes, and if so, executing a step 203;
it should be noted that a Hash code is assigned to each transient service, and when the transient service changes, the Hash code changes, so that the change of the transient service can be detected, and only when the transient service changes, the serialized storage is performed, thereby saving unnecessary storage space.
Step 203: recording data and callback objects required by creating the transient service;
step 204: data and callback objects required by creating transient service are stored in a server local file through CDR coding serialization;
it should be noted that CDR (Common Data Representation) encoding is a low-level binary Representation form that an Object Management Group (OMG) maps an OMG Interface Definition Language (IDL) Data type to network transmission;
serialization (Serialization) is the process of converting the state information of an object into a form that can be stored or transmitted;
during serialization, an object writes its current state to a temporary or persistent store, after which the object may be recreated by reading or deserializing the state of the object from the store.
Step 205: when restarting occurs, detecting a serialized file in a local file of the server after restarting, establishing the same transient service as before restarting through the serialized file corresponding to the data required by the transient service created by deserialization, and registering a callback object through the serialized file corresponding to the deserialization callback object;
it should be noted that, after the CIS server is restarted, the transient state service can be replied and the object can be called back to the restarted CIS server according to the deserialization file in the local file of the server.
Step 206: establishing connection with a corresponding CIS client according to the callback object;
it should be noted that the CIS client can continue to access the CIS server without any modification.
Step 207: detecting whether data subscribed by the CIS client changes according to a subscription object in the data required for creating the transient service, if so, executing a step 208;
after the CIS server and the CIS client recover the connection, the CIS server detects data subscribed by the CIS client according to a subscription object in the data required for creating the transient service, determines whether the data subscribed by the CIS client changes, and if so, executes the next step.
Step 208: and sending the data subscribed by the CIS client to the CIS client.
If the data subscribed by the CIS client changes, the CIS server sends the data subscribed by the CIS client to the CIS server.
After the CIS server and the CIS client are connected, data and callback objects required by transient service creation are actively stored and stored in a server local file through CDR coding serialization;
the CIS interface is serialized through the CDR codes of the CIS interface, so that the development difficulty is reduced;
the storage space of the CIS server is saved by formulating a Hash code for each transient service;
when the CIS server is restarted due to function repair or program abnormality and the like, data and callback objects required by the establishment of the transient service can be directly deserialized, the transient service which is the same as that before the CIS server is restarted is reestablished and established, the CIS client does not need to establish connection with the CIS server again according to the step of establishing connection with the CIS server, the unique identification of the service is kept unchanged, and the CIS client can directly access the CIS server through the original service address;
the method is transparent to the CIS client, and the detection is not required to be carried out through the CIS client, so that the CIS client is not required to be changed, the development complexity of the CIS client is reduced, and the burden of the CIS server caused by calling the CIS server for detection by the CIS client is also reduced;
the method solves the technical problems that the burden of the CIS server and the complexity of the CIS client are increased when the existing CIS service is disconnected and reconnected, the CIS server cannot actively restore the connection, and the CIS client needs to reestablish the connection with the CIS server according to the step of establishing the connection with the CIS server.
Further, the data required for creating the transient service specifically includes: session name, session settings, subscription object, and service address.
The above is another embodiment of the CIS service maintaining method provided by the embodiment of the present invention, and the following is an embodiment of a CIS service maintaining device provided by the embodiment of the present invention.
Referring to fig. 3, an embodiment of the present invention provides an embodiment of a CIS service holding device, including:
the transient recording module 301 is configured to receive a connection request of the CIS client, create a transient service according to the connection request, and record data and a callback object required for creating the transient service;
a serialization module 302, configured to store data and callback objects required for creating a transient service in a server local file in a serialized manner;
the deserializing module 303 is configured to detect a serialized file in the local file of the server after restart, construct a transient service that is the same as that before restart by deserializing a serialized file corresponding to data required for creating the transient service, and register a callback object by the serialized file corresponding to the deserialized callback object when restart occurs;
and the subscription pushing module 304 is configured to establish a connection with a corresponding CIS client according to the callback object, and send data subscribed by the CIS client to the CIS client according to a subscription object in the data required for creating the transient service.
Further, the transient recording module 301 specifically includes:
an encoding sub-module 3011, configured to formulate a Hash code for each transient service;
the detection submodule 3012 is configured to receive a connection request of the CIS client, create a transient service according to the connection request, and detect whether the Hash changes, if yes, execute step S103;
a recording sub-module 3013 for recording data and callback objects required for creating a transient service.
Further, the subscription pushing module 304 specifically includes:
the callback submodule 3041 is configured to establish a connection with a corresponding CIS client according to the callback object;
the pushing sub-module 3042 is configured to detect whether data subscribed by the CIS client changes according to a subscription object in the data required for creating the transient service, and if so, send the data subscribed by the CIS client to the CIS client.
Further, the serialization module 302 is specifically configured to store the data and the callback objects required for creating the transient service in the server local file in a serialized manner by using the CDR encoding method.
Further, the data required for creating the transient service specifically includes: session name, session settings, subscription object, and service address.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and in actual implementation, there may be other divisions, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A CIS service keeping method based on IEC61970 standard is characterized by comprising the following steps:
s1: receiving a connection request of a CIS client, creating a transient service according to the connection request, and recording data and callback objects required by creating the transient service;
s2: serializing and storing data and callback objects required by creating transient service to a local file of a server;
s3: when restarting occurs, detecting a serialized file in a local file of the server after restarting, establishing the same transient service as before restarting through the serialized file corresponding to the data required by the transient service created by deserialization, and registering a callback object through the serialized file corresponding to the deserialization callback object;
s4: and establishing connection with the corresponding CIS client according to the callback object, and sending the data subscribed by the CIS client to the CIS client according to a subscription object in the data required by the transient service creation.
2. The method for CIS service maintenance based on IEC61970 standard according to claim 1, wherein the step S1 specifically includes:
s101: making a Hash code for each transient service;
s102: receiving a connection request of a CIS client, creating a transient service according to the connection request, detecting whether the Hash changes, and if so, executing a step S103;
s103: data and callback objects needed to create the transient service are recorded.
3. The method for CIS service maintenance based on IEC61970 standard according to claim 1, wherein the step S4 specifically includes:
s401: establishing connection with a corresponding CIS client according to the callback object;
s402: and detecting whether the data subscribed by the CIS client changes according to a subscription object in the data required for creating the transient service, and if so, sending the data subscribed by the CIS client to the CIS client.
4. The method for CIS service maintenance based on IEC61970 standard according to claim 1, wherein the step S2 specifically includes:
and serializing and storing data and callback objects required by creating the transient service to a local file of the server through a CDR coding method.
5. The method for CIS service retention according to claim 1 based on IEC61970 standard, wherein the data required for creating the transient service specifically includes: session name, session settings, subscription object, and service address.
6. A CIS server based on IEC61970 standard, comprising:
the transient recording module is used for receiving a connection request of the CIS client, creating a transient service according to the connection request, and recording data and callback objects required by the creation of the transient service;
the serialization module is used for serializing and storing data and callback objects required by creating the transient service into a local file of the server;
the deserializing module is used for detecting a serialized file in a local file of the server after restarting when restarting occurs, constructing the same transient service as before restarting through the serialized file corresponding to the data required by the deserializing creating the transient service, and registering a callback object through the serialized file corresponding to the deserializing callback object;
and the subscription pushing module is used for establishing connection with the corresponding CIS client according to the callback object and sending the data subscribed by the CIS client to the CIS client according to the subscription object in the data required by the transient service creation.
7. The CIS server according to claim 6, wherein the transient recording module specifically comprises:
the encoding submodule is used for formulating a Hash code for each transient service;
the detection submodule is used for receiving a connection request of the CIS client, creating a transient service according to the connection request, detecting whether the Hash changes or not, and if so, executing the step S103;
and the recording submodule is used for recording data and callback objects required by the transient service creation.
8. The IEC61970 standard-based CIS server of claim 6, wherein the subscription push module specifically comprises:
the callback submodule is used for establishing connection with the corresponding CIS client according to the callback object;
and the pushing sub-module is used for detecting whether the data subscribed by the CIS client changes according to a subscription object in the data required for creating the transient service, and if so, sending the data subscribed by the CIS client to the CIS client.
9. The IEC61970 standard-based CIS server as claimed in claim 6, wherein the serialization module is specifically configured to store the data and callback objects required for creating the transient service in a server local file by means of CDR encoding.
10. The CIS server according to claim 6, wherein the data required for creating the transient service specifically comprises: session name, session settings, subscription object, and service address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711228419.2A CN107948294B (en) | 2017-11-29 | 2017-11-29 | CIS service maintaining method based on IEC61970 standard and CIS server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711228419.2A CN107948294B (en) | 2017-11-29 | 2017-11-29 | CIS service maintaining method based on IEC61970 standard and CIS server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107948294A CN107948294A (en) | 2018-04-20 |
| CN107948294B true CN107948294B (en) | 2020-09-01 |
Family
ID=61947754
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711228419.2A Active CN107948294B (en) | 2017-11-29 | 2017-11-29 | CIS service maintaining method based on IEC61970 standard and CIS server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107948294B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102710435A (en) * | 2012-05-14 | 2012-10-03 | 中国电力科学研究院 | System integration interface adapter based on common information model (CIM) |
| CN102904739A (en) * | 2011-07-27 | 2013-01-30 | 华为技术有限公司 | Method for realizing event transmission and common information model (CIM) server |
| CN103546541A (en) * | 2013-09-26 | 2014-01-29 | 中国南方电网有限责任公司 | Intelligent telecontrol communication machine based remote data subscribing and releasing method |
| CN107079509A (en) * | 2014-11-07 | 2017-08-18 | 瑞典爱立信有限公司 | Method, RAN node and mobile management node for suspending and recovering RAN CN connections |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104769582B (en) * | 2012-11-02 | 2018-11-02 | 埃森哲环球服务有限公司 | For the real time data releasing of power grid |
-
2017
- 2017-11-29 CN CN201711228419.2A patent/CN107948294B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102904739A (en) * | 2011-07-27 | 2013-01-30 | 华为技术有限公司 | Method for realizing event transmission and common information model (CIM) server |
| CN102710435A (en) * | 2012-05-14 | 2012-10-03 | 中国电力科学研究院 | System integration interface adapter based on common information model (CIM) |
| CN103546541A (en) * | 2013-09-26 | 2014-01-29 | 中国南方电网有限责任公司 | Intelligent telecontrol communication machine based remote data subscribing and releasing method |
| CN107079509A (en) * | 2014-11-07 | 2017-08-18 | 瑞典爱立信有限公司 | Method, RAN node and mobile management node for suspending and recovering RAN CN connections |
Non-Patent Citations (1)
| Title |
|---|
| 基于公共信息模型和组件接口规范的电力设备监测诊断中心研究与应用;翟瑞聪 等;《广东电力》;20121125(第11期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107948294A (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10387255B2 (en) | Data reconstruction method in distributed storage system, apparatus, and system | |
| CN111124755B (en) | Fault recovery method and device for cluster nodes, electronic equipment and storage medium | |
| CN102868754A (en) | High-availability method, node device and system for achieving cluster storage | |
| CN111064626B (en) | Configuration updating method, device, server and readable storage medium | |
| US10067719B1 (en) | Methods and systems for storing and accessing data in a distributed data storage system | |
| CN110196759B (en) | Distributed transaction processing method and device, storage medium and electronic device | |
| CN111917897A (en) | Identification generation method, device, equipment and storage medium | |
| CN112612769A (en) | File processing method, device and storage medium | |
| CN111541762B (en) | Data processing method, management server, device and storage medium | |
| CN111694845A (en) | Redis-based identifier generation method and device | |
| CN111510480A (en) | Request sending method and device and first server | |
| CN107948294B (en) | CIS service maintaining method based on IEC61970 standard and CIS server | |
| CN113946487A (en) | Method and system for realizing autonomous service degradation recovery in fault scene | |
| US20210096962A1 (en) | Data backup method, device and system | |
| CN113900855B (en) | Active hot start method, system and device for abnormal state of switch | |
| CN113434604B (en) | Time sequence database synchronization method, system, equipment and storage medium | |
| CN114020503A (en) | Optimization method, system and device for transparent fault switching of distributed file system | |
| CN114090687A (en) | Data synchronization method and device | |
| US20150379548A1 (en) | Method and System for Data Processing | |
| CN111273933A (en) | BIOS FW refreshing method and device | |
| CN110890989A (en) | Channel connection method and device | |
| CN116347467B (en) | Method and system for managing user data by UDR in 5G network | |
| CN106375354B (en) | Data processing method and device | |
| CN115086173B (en) | Reliability guarantee method and device in network upgrading process | |
| CN111435919B (en) | Method, device and system for managing configuration parameters |
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 |