Feature #5123
ACSI service for link supervision on application level
Added by Andreas Ostermeier about 3 years ago.
Updated over 1 year ago.
Category:
Standard extension required
Due date:
02/11/2022 (over 2 years late)
Discuss in Upcoming Meeting:
No
Needs More Information:
No
Description
Link supervision is currently not defined as an ACSI service, but mentioned in the mapping documents
8-1 defines TCP-Keepalive shall be used for link supervision
8-2 defines XMPP Ping for link supervision
9-2 defines Goose TTL for link supervision
TCP-Keepalive as defined in 8-2 alone might not be sufficient in some scenarios.
It will just proof that the Ethernet Stack of the IED is still alive, but doesn't give any clue on the status of the higher protocol levels or the application itself.
Therefore
Proposal descriptions
TF Communication Supervision (90-28) is defining LTPA logical node to supervise two-party associations covering this issue.
- Discuss in Upcoming Meeting changed from No to Yes
- Status changed from New to Feedback
- Standard(s) set to IEC 61850-7-2, 8-1, 8-2
Indicate why having such ACSI service supervision should solve the problem. A Client today already can send periodically supported service to monitor application to application communication. Verify which comm. architecture involving WAN could interfere with the TCP KEEPALIVE usage in the server to discover that the client has gone.
Andreas Ostermeier wrote:
Link supervision is currently not defined as an ACSI service, but mentioned in the mapping documents
8-1 defines TCP-Keepalive shall be used for link supervision
8-2 defines XMPP Ping for link supervision
8-1 defines Goose TTL for link supervision
TCP-Keepalive as defined in 8-1 alone might not be sufficient in some scenarios.
It will just proof that the Ethernet Stack of the IED is still alive, but doesn't give any clue on the status of the higher protocol levels or the application itself.
Therefore
Note that 8-2 XMPP Ping or 8-1 TCP-KEEPALIVE it not for Link supervision but for the supervision of the trasport layer.
- ID set to 2
- TF Unique ID changed from 2 to 2 # 80-6
- Status changed from Feedback to Resolved
- Discuss in Upcoming Meeting changed from Yes to No
- Proposal descriptions updated (diff)
- Short Proposal set to 90-28 to cover the issue
- Standard(s) changed from IEC 61850-7-2, 8-1, 8-2 to IEC 61850-90-28
TF Communication Supervision is defining LTPA logical node to supervise two-party associations covering this issue.
- Needs More Information set to No
- Discuss in Upcoming Meeting changed from No to Yes
- Discuss in Upcoming Meeting changed from Yes to No
Also available in: Atom
PDF