Project

General

Profile

Feature #5123

ACSI service for link supervision on application level

Added by Andreas Ostermeier 9 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Category:
Standard extension required
Start date:
11/22/2021
Due date:
02/11/2022 (about 6 months late)
% Done:

0%

Estimated time:
ID:
2
Source:
TF 61850-80-6
TF Unique ID:
2 # 80-6
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
No
Short Proposal:

90-28 to cover the issue

Standard(s):

IEC 61850-90-28


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.

#1

Updated by Andreas Ostermeier 9 months ago

  • TF Unique ID set to 2
#2

Updated by Vladan Cvejic 8 months ago

  • Discuss in Upcoming Meeting changed from No to Yes
#3

Updated by Vladan Cvejic 8 months ago

  • 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.

#4

Updated by Thierry Dufaure 8 months ago

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

#5

Updated by Thierry Dufaure 8 months ago

Note that 8-2 XMPP Ping or 8-1 TCP-KEEPALIVE it not for Link supervision but for the supervision of the trasport layer.

#6

Updated by Carlos Rodriguez del Castillo 8 months ago

  • ID set to 2
  • TF Unique ID changed from 2 to 2 # 80-6
#7

Updated by Carlos Rodriguez del Castillo about 2 months ago

  • 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.

Also available in: Atom PDF