1927   Multiplicity of PDUs within Payload for Routable Session in unclear

Created: 21 May 2024

Status: Solution Accepted

Part: Part 8-1 (2020; Edition 2.1)

Links:

Page: 208

Clause: J.3.2.7.3.1 and Fig J.2

Paragraph: Fig J.2

Issue

The paragraph states:
The payload section ... allows multiple user data PDUs to be aggregated within one SPDU.
It is unclear how multipleuser data PDUs can be configured, especially within the scope of a secure MCAA.
How can a sucriber pick out its subscribed infomation within the receive telgramm when multiple user defined PDUs are agreegated.

Proposal

Remove the multiplity so that there is only 1 user defined PDU per SPDU to increase the interoperability of subscribers.

Discussion Created Status
Move to solution accepted. 17 Jun 25 Solution Accepted
Move to ballot period.

Changes are:
1) Figure J.2: replace the multiplicity 1..n PDUs - to 1..1 PDU
2) Replace the clause J.3.2.7.3.1 General with the sentence:
"The payload section, as shown in Figure J.2, allows a single user data PDU to be sent in one SPDU." 		01 Apr 25 Ballot Period
R-GOOSE is not yet tested. This will be included with those tests are added. 01 Apr 25 Conformance Test Verification
No compatiiblity issues were found as
1) it is not in used
2) it was not configurable using SCL means.

Changes are:
1) Figure J.2: replace the multiplicity 1..n PDUs - to 1..1 PDU
2) Replace the clause J.3.2.7.3.1 General with the sentence:
"The payload section, as shown in Figure J.2, allows a single user data PDU to be sent in one SPDU." 		11 Feb 25 Conformance Test Preparation
1) Figure J.2: replace the multiplicity 1..n PDUs - to 1..1 PDU
2) Replace the clause J.3.2.7.3.1 General with the sentence:
"The payload section, as shown in Figure J.2, allows a single user data PDU to be sent in one SPDU." 		21 Jan 25 Analysis Of Compatibility
Proposed changes:
1) Figure J.2: replace the multiplicity 1..n PDUs - to 1..1 PDU
2) Replace the clause J.3.2.7.3.1 General with the sentence:
"The payload section, as shown in Figure J.2, allows a single user data PDU to be sent in one SPDU." 		17 Dec 24 Verify Draft Implementation
Proposed changes:
1) Figure J.2: replace the multiplicity 1..n PDUs - to 1..1 PDU
2) Replace the clause J.3.2.7.3.1 General with the sentence:
"The payload section, as shown in Figure J.2, allows a single user data PDU to be sent in one SPDU."
15 Oct 24 Drafting Implementation
Append the clause J.3.2.7.3.1 General with the sentence:

Within the context of IEC 61850, the number of user data PDUs shall be constrained to one (1). 		27 Aug 24 Drafting Implementation
Propose to append the clause J.3.2.7.3.1 General with the sentence:

Within the context of IEC 61850, the number of user data PDUs shall be constrained to one (1). 		16 Jul 24 Discussion (red)
Open for discussion. 21 May 24 Discussion (red)
Agree, there is no valid use case for multiple user PDU in an SPDU of Routable G/SV.

Additionally, there is no way to configure for this and security is related to one CB, which would restrict the payload. 		21 May 24 Accepted

 

Privacy | Contact | Disclaimer

Tissue DB v. 25.7.7.1