CN103368693A - Method for reliably transmitting data of power distribution network information exchange bus - Google Patents
Method for reliably transmitting data of power distribution network information exchange bus Download PDFInfo
- Publication number
- CN103368693A CN103368693A CN2013102799758A CN201310279975A CN103368693A CN 103368693 A CN103368693 A CN 103368693A CN 2013102799758 A CN2013102799758 A CN 2013102799758A CN 201310279975 A CN201310279975 A CN 201310279975A CN 103368693 A CN103368693 A CN 103368693A
- Authority
- CN
- China
- Prior art keywords
- bus
- message
- field
- messageid
- information
- 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.)
- Granted
Links
Images
Abstract
The invention relates to a method for reliably transmitting data, wherein reliable transmission is the important technical support and guarantee of a power distribution network information exchange system, the conventional transmission mode lacks the protection to the information, namely the information can not be guaranteed to safely and timely arrive at the destination in the case of unusual condition of equipment such as the interruption of power supply, the outage of network, the short dump and the like. The method provides the invention for transmitting the data reliably, the functions of storage and retransmission of the information can be realized by designing a message data table at a bus side, the loss rate of the information can be furthest reduced, and the reliability of an IEC 61968 information exchange platform can be improved.
Description
Technical field
The invention belongs to the integrated and bridging technology field of power distribution network information, be specifically related to a kind of method of power distribution network information exchange bus reliable data transmission.
Background technology
The information system that power distribution network is relevant is numerous, and is professional complicated, need to run through a plurality of information systems, thus information integrated be the key point of power distribution network informatization.In recent years, development along with intelligent grid, interoperability becomes the integrated up-to-date target of distribution information, IEC 61968 standards become the integrated common recognition of distribution information, and many power supply enterprises progressively become the mode from point-to-point information set and are transitioned into intergration model based on information exchange bus and SOA service architecture.
IEC 61968 standards are by formulating unified distribution common information model, unified message format and unified service interface, for the distribution interoperability lays the first stone, yet, owing to lack information flow transmitting technology, caused following problem:
1. after a certain system is recovered, can't receive the information that other system between age at failure sends from fault, reliability and the information integrity of whole system brought very large negative effect.
2. user's information flow operation conditions of monitoring bus intuitively, and the statistics of information flow lacks data supporting and source, has brought very large difficulty for the analytical work of information exchange.
Summary of the invention
For the deficiencies in the prior art, the present invention proposes a kind of method of power distribution network information exchange bus reliable data transmission, by designing a message data table in bus side, the storage of realization information and retransmitting function, farthest reduce the information dropout rate, improved greatly the reliability of IEC 61968 information exchange platforms.
The method of a kind of power distribution network information exchange bus reliable data transmission provided by the invention, its improvements are, in bus side the message data table are set; The message of the bus of flowing through all is stored into described tables of data; Behind the bus receipt message message is distributed; After the success of transmission information, revise the state of message in the message data table.
Wherein, described message data table comprises a MessageID field; When message was passed through bus for the first time, bus generated MessageID, and the broadcast and the response message that are after this caused by this message all use described MessageID.
Wherein, have in comprising in the described message data table:
MessageID field, Sender field, Receiver field, Noun field, Verb field, Content field, ReturnContent field, CreationTime field, Status field, Trans_Type field and Fault_code field.
Wherein, the flow through message of bus is divided into Event type information or the Request type information that adapter or other buses send.
Wherein, after bus received Event type information content and deposits described message data table in, bus was distributed message, and after the success of transmission information, the step of revising content in the message data table comprises:
1) according to the agreement of IEC61968 agreement, the Header node should comprise noun and verb and the sender who consists of theme.With its taking-up and deposit respectively Noun field, Verb field and Sender field in; Deposit bus number in the Receiver field; If described MessageID node is empty, then bus is MessageID of this message generation, deposits the MessageID field in, and this value is write in the MessageID child node in the Header node; From Payload, obtain the main body of IEC 61968 information, deposit the Content field in; Record the time of described information arrival bus, deposit the CreationTime field in; " SUCCESS " deposited in the Status field; " publish " deposited in the Trans_type field;
2) described bus is sought the recipient from subscribing relationship, generates record in the message data table;
3) described bus is carried out information broadcast according to recipient's address, after the recipient receives message, can return a response message to bus;
4) bus is obtained sender's ID from the Header node of response message, establishes it and is N and MessageID, establishes it and is M; The value of bus Receiver field is that the value of N and MessageID field is that the state of the record of M is set to successfully, and namely the Status field changes " SUCCESS " into by " sent ".
Wherein, step 2) described bus is sought the recipient from subscribing relationship, generates theing contents are as follows of record in the message data table:
ID is the MessageID that generates;
Sender is bus;
Receiver is bus or the adapter of having subscribed to this theme;
Noun is the noun that obtains;
Verb is the verb that obtains;
Content is the source body that obtains;
CreationTime is for sending the time of this message;
Status is " sent ", and expression message is sent from bus;
Trans_type is " broadcast ", represents that this type of message is broadcast distribution.
Wherein, after bus received Request type information content and deposits described message data table in, bus was distributed message, and after the success of transmission information, the step of revising content among the MessageID comprises:
1. according to the agreement of IEC61968 agreement, the Header node should comprise noun and verb and the sender who consists of theme; Take out and deposit in respectively Noun field, Verb field and Sender field; Deposit bus number in the Receiver field; If the MessageID node is empty, then bus is MessageID of this message generation, deposits the MessageID field in, and this value is write in the MessageID child node in the Header node; From Payload, obtain the main body of IEC 61968 information, deposit the Content field in; Record the time of this information arrival bus, deposit the CreationTime field in; " SUCCESS " deposited in the Status field; " Request " deposited in the Trans_type field;
2. described bus is sought the respondent from subscribing relationship, if a plurality of respondents are arranged, then selects first available respondent, generates record in the message data table:
3. bus after the respondent receives message, through processing, can return to bus with response message with asynchronous form according to respondent's address forwarding messages;
4. bus is obtained sender's ID from the Header node of response message, establishes it and is N and MessageID, is made as M; The value of bus Receiver field is that the value of N and MessageID field is that the state of the record of M is set to successfully, and with in the message typing ReturnContent field among the Payload.
Wherein, step 2. described bus is sought the respondent from subscribing relationship, if a plurality of respondents are arranged, then selects first available respondent, generates theing contents are as follows of record in the message data table:
MessageID is the MessageID that generates;
Sender is bus;
Receiver is bus or the adapter that has this theme corresponding authority;
Noun is the noun that obtains;
Verb is the verb that obtains;
Content is the request source body that obtains;
ReturnContent is the reply source body that obtains;
CreationTime is for sending the time of this message;
Status is " sent ", and expression message is sent from bus;
Trans_type is " reply ", represents that this type of message is response.
Wherein, if hindering for some reason, certain unit fails in time to receive the message that bus is sent, so after this trouble unit recovers normal and identifies by legitimacy, bus can be initiated bind request, with Receiver field in the message data table for this unit ID and Status for the message of " sent " resends to this unit, finish the repeating transmission of message.
Compared with the prior art, beneficial effect of the present invention is:
The present invention is a kind of method of reliable data transmission; transmitting is that the important technology of power distribution network Information Interchange System supports and assurance; traditional transmission mode lacks the protection to information; namely occur at equipment can't ensuring information security and arriving timely the destination in the unusual conditions such as outage, suspension, program crashing.The present invention proposes the method for reliable data transmission, by at message data table of bus side design, realizes storage and the retransmitting function of information, farthest reduces the information dropout rate, has improved greatly the reliability of IEC 61968 information exchange platforms.
The present invention carries out exchanges data by at bus configuration message data table, and the reliability of power distribution network information flow, stability are further strengthened.
The present invention is for the flow through information of bus of each bar, and bus all can be kept at it in message data table, and records the information such as its transmit leg, recipient, information type, transmission state.After fault recovery, can again send to the destination according to the information that records undelivered, realize the transmitting of information flow, positive effect has been played in the raising of power distribution network information exchange platform reliability and stability.
Description of drawings
Fig. 1 is message table schematic diagram provided by the invention.
Fig. 2 is Event Message Processing schematic flow sheet provided by the invention.
Fig. 3 is Request/Reply Message Processing schematic flow sheet provided by the invention.
Fig. 4 is retransmission process schematic diagram provided by the invention.
Embodiment
Below in conjunction with accompanying drawing the specific embodiment of the present invention is described in further detail.
The method of a kind of power distribution network information exchange bus reliable data transmission that present embodiment proposes is in bus side the message data table to be set; The message of the bus of flowing through all is stored into described message data table; Bus is distributed message after receiving message, after the success of transmission information, revises the state of message in the message data table.Comprise a MessageID in the message data table; When message was passed through bus for the first time, bus generated MessageID, and the broadcast and the response message that are after this caused by this message all use described MessageID.
Concrete, the message data list structure schematic diagram that present embodiment proposes as shown in Figure 1, its comprise in have:
MessageID field, Sender field, Receiver field, Noun field, Verb field, Content field, ReturnContent field, CreationTime field, Status field, Trans_Type field and Fault_code field.
Be divided into Event type information or the Request type information that adapter or other buses send according to the message of the bus of flowing through, present embodiment is done respectively following explanation:
For bus reception Event type information content and after depositing described message data table in, bus is distributed message, after the success of transmission information, revises the flow chart of content in the message data table as shown in Figure 2, and concrete steps comprise:
1) bus receives the Event type information of adapter or the transmission of other buses, according to the agreement of IEC61968 agreement, obtains the noun and verb and the sender that consist of theme from the Header node, deposits Noun field, Verb field and Sender field in; The recipient of this message is bus, so deposit this bus number in the Receiver field; Be empty such as the MessageID node, represent that then this message is for the first time through bus, this moment, bus was MessageID of this message generation, deposited the MessageID field in, and this value is write in the MessageID child node in the Header node; Be not empty such as the MessageID node, direct use content wherein then; From Payload, obtain the main body of IEC 61968 information, deposit the Content field in; Record the time of this information arrival bus, deposit the CreationTime field in; Because this information successfully arrives bus, so " SUCCESS " deposited in the Status field; The type of message is " issue ", therefore " publish " is deposited in the Trans_type field;
2) meanwhile, bus is sought the recipient from subscribing relationship, generates record in the message data table, thes contents are as follows:
MessageID is the MessageID that previous step generates, and Sender is bus; Receiver is bus or the adapter of having subscribed to this theme; Noun is the noun that previous step is obtained; Verb is the verb that previous step is obtained; Content is the source body that previous step is obtained; CreationTime is for sending the time of this message; Status is " sent ", and expression message is sent from bus; Trans_type is " broadcast ", represents that this type of message is broadcast distribution;
Value that it should be noted that the MessageID field of these several records all is the same, only has the value of Receiver different, that is to say, the associating major key of this table is MessageID and Receiver;
3) bus is carried out information broadcast according to recipient's address, after the recipient receives message, can return a response message to bus.Bus is obtained sender's ID from the Header node of response message, establish it and be N and MessageID, establishes it and is M.Then bus is that the value of N and MessageID field is the Status field of the record of M with the value of Receiver field, changes " SUCCESS " into by " sent ".
For bus reception Request type information content content and after depositing described message data table in, bus is distributed message, after the success of transmission information, revises the flow chart of content among the Message ID as shown in Figure 3, and concrete steps comprise:
1. bus reception adapter or other buses send to get the Request type information.According to the agreement of IEC61968 agreement, the Header node should comprise noun and verb and the sender who consists of theme.With its taking-up and deposit Noun field, Verb field and Sender field in; The recipient of this message is bus, so deposit this bus number in the Receiver field; Be empty such as the MessageID node, represent that then this message is for the first time through bus, this moment, bus was MessageID of this message generation, deposited the MessageID field in, and this value is write in the MessageID child node in the Header node; Be not empty such as the MessageID node, then directly use wherein content; Obtain the main body of IEC 61968 information from Payload, deposit the Content field in, according to the agreement of IEC 61968 agreements, in request message, the Payload node can be sky; Record the time of this information arrival bus, deposit the CreationTime field in; Because this information successfully arrives bus, so " SUCCESS " deposited in the Status field; The type of message is " request ", therefore " Request " is deposited in the Trans_type field;
2. meanwhile, bus is sought the respondent from subscribing relationship, if a plurality of respondents are arranged, then selects first available respondent, generates record in the message data table, thes contents are as follows:
MessageID is the MessageID that previous step generates, and Sender is bus; Receiver is bus or the adapter that has this theme corresponding authority; Noun is the noun that previous step is obtained; Verb is the verb that previous step is obtained; Content is the source body that previous step is obtained; CreationTime is for sending the time of this message; Status is " sent ", and expression message is sent from bus; Trans_type is " reply ", represents that this type of message is response.
3. bus after the respondent receives message, through a series of processing, can return to bus with response message with asynchronous form according to respondent's address forwarding messages.Bus is obtained sender's ID from the Header node of response message, establish it and be N and MessageID, establishes it and is M.Next bus is that the value of N and MessageID field is the Status field of the record of M with the value of Receiver field, changes " SUCCESS " into by " sent ", and with in the message typing returnContent field among the Payload.
For the unsuccessful situation of bus sending information, from the present embodiment foregoing description, can find out, rear recipient does not receive message if bus initiates a message, perhaps the recipient receives after the message because fault does not return to bus with feedback message, the Status field of this record will rest on " sent " so, and the expression bus is sent but do not received feedback information.At this moment, normal if this trouble unit recovers, initiate bind request to bus, bus is after identifying its legitimacy, with Receiver field in the message data table for this unit ID and Status for the message of " sent " resends to this unit, finish the repeating transmission of message, as shown in Figure 4.
Should be noted that at last: above embodiment is only in order to illustrate that technical scheme of the present invention is not intended to limit, although with reference to above-described embodiment the present invention is had been described in detail, those of ordinary skill in the field are to be understood that: still can make amendment or be equal to replacement the specific embodiment of the present invention, and do not break away from any modification of spirit and scope of the invention or be equal to replacement, it all should be encompassed in the middle of the claim scope of the present invention.
Claims (9)
1. the method for a power distribution network information exchange bus reliable data transmission is characterized in that, in bus side the message data table is set; The message of the bus of flowing through all is stored into described message data table; Bus is distributed message after receiving message; After the success of transmission information, revise the state of message in the message data table.
2. the method for claim 1 is characterized in that, described message data table comprises a MessageID field; When message was passed through bus for the first time, bus generated MessageID, and the broadcast and the response message that are after this caused by this message all use described MessageID.
3. method as claimed in claim 2 is characterized in that, has in comprising in the described message data table:
MessageID field, Sender field, Receiver field, Noun field, Verb field, Content field, returnContent field, creationTime field, Status field, Trans_Type field and Fault_code field.
4. method as claimed in claim 2 is characterized in that, the message of the bus of flowing through is divided into Event type information, Request type information and Reply type information.
5. method as claimed in claim 4 is characterized in that, after bus received Event type information content and deposits described message data table in, bus was distributed message, and after the success of transmission information, the step of revising the state of message in the message data table comprises:
1) according to the agreement of IEC61968 agreement, comprises the noun and verb and the sender that consist of theme in the Header node; With its taking-up and deposit respectively Noun field, Verb field and Sender field in; Deposit bus number in the Receiver field; If described MessageID node is empty, then bus is Message ID of this message generation, deposits the MessageID field in, and this value is write in the MessageID child node in the Header node; From Payload, obtain the main body of IEC 61968 information, deposit the Content field in; Record the time of described information arrival bus, deposit Creation Time field in; " SUCCESS " deposited in the Status field; " publish " deposited in the Trans_type field;
2) described bus is sought the recipient from subscribing relationship, generates record in the message data table;
3) described bus is carried out information broadcast according to recipient's address, after the recipient receives message, can return a response message to bus;
4) bus is obtained sender's ID from the Header node of response message, establishes it and is N and MessageID, establishes it and is M; The value of bus Receiver field is that the value of N and MessageID field is that the state of the record of M is set to successfully.
6. method as claimed in claim 5 is characterized in that step 2) described bus seeks the recipient from subscribing relationship, generate theing contents are as follows of record in the message data table:
MessageID is the MessageID that generates;
Sender is bus;
Receiver is bus or the adapter of having subscribed to this theme;
Noun is the noun that obtains;
Verb is the verb that obtains;
Content is the source body that obtains;
CreationTime is for sending the time of this message;
Status is " sent ", and expression message is sent from bus;
Trans_type is " broadcast ", represents that this type of message is broadcast distribution.
7. method as claimed in claim 4 is characterized in that, after bus received Request type information content and deposits described message data table in, bus was distributed message, and after the success of transmission information, the step of revising message status in the message data table comprises:
1. according to the agreement of IEC61968 agreement, comprise the noun and verb and the sender that consist of theme in the Header node; With its taking-up and deposit respectively Noun field, Verb field and Sender field in; Deposit bus number in the Receiver field; If the MessageID node is empty, then bus is MessageID of this message generation, deposits the MessageID field in, and this value is write in the MessageID child node in the Header node; From Payload, obtain the main body of IEC 61968 information, deposit the Content field in; Record the time of this information arrival bus, deposit the CreationTime field in; " SUCCESS " deposited in the status field; " Request " deposited in the trans_type field;
2. described bus is sought the respondent from subscribing relationship, if a plurality of respondents are arranged, then selects first available respondent, generates record in the message data table:
3. bus after the respondent receives message, through processing, can return to bus with response message with asynchronous form according to respondent's address forwarding messages;
4. bus is obtained sender's ID from the Header node of response message, establishes it and is N and MessageID, is made as M; The value of bus Receiver field is that the value of N and MessageID field is that the state of the record of M is set to successfully, and with in the message typing ReturnContent field among the Payload.
8. method as claimed in claim 7 is characterized in that, step 2. described bus is sought the respondent from subscribing relationship, if a plurality of respondents are arranged, then selects first available respondent, generates theing contents are as follows of record in the message data table:
MessageID is the MessageID that generates;
Sender is bus;
Receiver is bus or the adapter that has this theme corresponding authority;
Noun is the noun that obtains;
Verb is the verb that obtains;
Content is the source body that obtains;
CreationTime is for sending the time of this message;
Status is " sent ", and expression message is sent from bus;
Trans_type is " reply ", represents that this type of message is response.
9. the method for claim 1, it is characterized in that, if hindering for some reason, certain unit fails in time to receive the message that bus is sent, so after this trouble unit recovers normal and identifies by legitimacy, bus can be initiated bind request, with Receiver field in the message data table for this unit ID and Status for the message of " sent " resends to this unit, finish the repeating transmission of message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310279975.8A CN103368693B (en) | 2013-07-04 | 2013-07-04 | A kind of method of power distribution network interexchange bus reliable data transmission |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310279975.8A CN103368693B (en) | 2013-07-04 | 2013-07-04 | A kind of method of power distribution network interexchange bus reliable data transmission |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103368693A true CN103368693A (en) | 2013-10-23 |
| CN103368693B CN103368693B (en) | 2016-12-28 |
Family
ID=49369311
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310279975.8A Active CN103368693B (en) | 2013-07-04 | 2013-07-04 | A kind of method of power distribution network interexchange bus reliable data transmission |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103368693B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105721554A (en) * | 2016-01-25 | 2016-06-29 | 国网福建省电力有限公司 | Verb and noun based power distribution network service message flow generating method |
| CN106296439A (en) * | 2015-05-15 | 2017-01-04 | 中国电力科学研究院 | A kind of priority transmission control method mutual based on IEC61968 information |
| CN111556034A (en) * | 2020-04-15 | 2020-08-18 | 成都飞机工业（集团）有限责任公司 | GJB289A bus message dynamic mapping method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102427419A (en) * | 2011-08-09 | 2012-04-25 | 国电南瑞科技股份有限公司 | Method for supporting poly-morphism function of message bus |
| CN102999463A (en) * | 2012-11-14 | 2013-03-27 | 中国电力科学研究院 | Plug and play method of power distribution network information exchange bus |
| CN103019980A (en) * | 2012-11-14 | 2013-04-03 | 中国电力科学研究院 | Control method for information flow of power distribution network based on IEC(International Electrotechnical Commission) 61968 standard |
-
2013
- 2013-07-04 CN CN201310279975.8A patent/CN103368693B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102427419A (en) * | 2011-08-09 | 2012-04-25 | 国电南瑞科技股份有限公司 | Method for supporting poly-morphism function of message bus |
| CN102999463A (en) * | 2012-11-14 | 2013-03-27 | 中国电力科学研究院 | Plug and play method of power distribution network information exchange bus |
| CN103019980A (en) * | 2012-11-14 | 2013-04-03 | 中国电力科学研究院 | Control method for information flow of power distribution network based on IEC(International Electrotechnical Commission) 61968 standard |
Non-Patent Citations (1)
| Title |
|---|
| 吕广宪 等: "基于IEC 61968标准的信息交换总线主动与协同控制技术", 《电力系统自动化》, vol. 37, no. 13, 3 June 2013 (2013-06-03), pages 83 - 87 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106296439A (en) * | 2015-05-15 | 2017-01-04 | 中国电力科学研究院 | A kind of priority transmission control method mutual based on IEC61968 information |
| CN105721554A (en) * | 2016-01-25 | 2016-06-29 | 国网福建省电力有限公司 | Verb and noun based power distribution network service message flow generating method |
| CN111556034A (en) * | 2020-04-15 | 2020-08-18 | 成都飞机工业（集团）有限责任公司 | GJB289A bus message dynamic mapping method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103368693B (en) | 2016-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102197627B (en) | The improvement of flux of multicast convergence | |
| CN201075870Y (en) | Multi spider route device | |
| CN102148677B (en) | Method for updating address resolution protocol table entries and core switch | |
| CN100589433C (en) | Method and system for providing clock synchronization by packet network | |
| CN101378334B (en) | Communication method based on dual-network redundant universal network model | |
| CN103581307A (en) | Publishing/subscribing system based on clusters and method for guaranteeing reliability of publishing/subscribing system based on clusters | |
| WO2012167569A1 (en) | Method, node and system for link switching in ethernet ring | |
| CN101635975A (en) | Method for collecting and routing data in wireless sensor network and device thereof | |
| CN108551356B (en) | Method and system for reporting power failure of centralized meter reading system | |
| CN101257460A (en) | Instantaneous message temporary cluster group conversational system and method for creating and transmitting instantaneous message | |
| CN111787349B (en) | Data caching method, device, equipment and medium | |
| CN102970231A (en) | Multicast flow forwarding implementation method and routing bridge (RB) | |
| WO2013067735A1 (en) | Components managing method adapted for rail transit comprehensive monitoring system | |
| CN105072021A (en) | Cross-segment message forwarding method for dispatching automation systems | |
| CN103516612A (en) | Method for generating routing table items in a distributed router, and distributed router | |
| CN107645451A (en) | It is a kind of that the system and method uninterruptedly routeing is realized by application and protocol stack linkage | |
| CN102984174B (en) | Reliability guarantee method and system in a kind of distribution subscription system | |
| CN103166800A (en) | Message transmission method for dual-network redundant message bus in cross failure | |
| CN103368693A (en) | Method for reliably transmitting data of power distribution network information exchange bus | |
| EP2472793A1 (en) | Method, device and system for transmitting e1 bidirectional looped network data | |
| WO2020114512A1 (en) | Multicast message transmission method, first network device and second network device | |
| CN103716169A (en) | Point-to-multipoint multicast realization method, network nodes and system | |
| CN110519136A (en) | A kind of RS485 multi-machine communication system of adaptive networking | |
| CN102255798A (en) | Method and line card for synchronizing route forwarding table items | |
| CN106789520B (en) | A kind of high speed failure safe multi-node communication networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |