SIST EN 300 417-5-2 V1.1.1:2003

• Abstract:

  ICS proforma for ETS 300 417-5-1.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.040.20 - Transmission systems
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI EN 300 417-5-2 V1.1.1 (1999-08) - Transmission and Multiplexing (TM); Generic requirements of transport functionality of equipment; Part 5-2: Plesiochronous Digital Hierarchy (PDH) path layer functions; Implementation Conformance Statement (ICS) proforma specification

SIST EN 300 417-5-2 V1.1.1:2003 is the Slovenian standard identical to EN 300 417-5-2 Version 1.1.1, published by SIST. It is an Implementation Conformance Statement (ICS) proforma for the Transmission and Multiplexing (TM) family, focused on Plesiochronous Digital Hierarchy (PDH) path layer functions. In practice, it tells suppliers and test teams how to document which PDH path-layer functions an implementation supports and how to state conformance for the relevant equipment under test.

What does SIST EN 300 417-5-2 V1.1.1:2003 specify?

SIST EN 300 417-5-2 V1.1.1:2003 specifies the ICS proforma to be used for ETS 300 417-5-1. It is not a product design standard in itself - it is a structured conformance statement template for PDH path-layer functionality.

The document is organized as a short front matter and four main clauses, followed by annexes that carry the actual implementation statements. The annexes are arranged by path layer so a user can complete the sections relevant to the equipment being assessed.

Annex	What it covers
A	Guidance for completing the ICS proforma, including conventions and instructions
B	P4e path layer functions
C	P31e path layer functions
D	P22e path layer functions
E	P12s path layer functions
F	P31s path layer functions
G	P4s path layer functions

Clause 1 gives the scope, Clause 2 lists references, Clause 3 provides definitions and abbreviations, and Clause 4 states the conformance basis for the ICS proforma.

What are the key requirements of SIST EN 300 417-5-2 V1.1.1:2003?

The main practical requirement of SIST EN 300 417-5-2 V1.1.1:2003 is to complete the ICS forms in a consistent way so that an implementation can be compared against the ETS. The annexes do the real technical work: they break each path layer into identifiable functions, options, and reported status items.

Completing the ICS proforma

Clause 4 sets the conformance framework for the ICS proforma. That matters because the document is meant to be filled in as a declaration of support, not read as a list of mandatory design requirements.

Annex A gives the completion guidance and conventions. For a reader preparing a statement, this is the part that tells you how to answer the checklist cleanly and how to interpret the entries.

Identification and traceability

Each path-layer annex starts with identification items for the implementation and the ETS, including the Implementation Under Test (IUT) and System Under Test (SUT). That matters because the resulting statement must be traceable to a specific product or configuration, not just a general product family.

The annexes also include a global statement of conformance for the relevant path layer. In practice, this is where the supplier declares the overall support status before answering the detailed function tables.

Function families covered in every path layer annex

The annexes for P4e, P31e, P22e, P12s, P31s and P4s all use the same basic structure: path layer description, characteristic information, trail termination functions, adaptation functions, monitoring functions, and clock adaptation. For P31s and P4s, the annexes also include tandem connection sub-layer functions.

That structure matters because it lets a buyer, tester, or quality manager see whether the equipment supports the complete path-layer behavior, not just payload transport.

Characteristic information and adapted information

Each annex defines the Characteristic Information (CI) and the Adapted Information (AI) for that layer. The CI entries describe the frame structure and overhead fields used at that layer, while the AI entries describe the transported signal and how it is mapped.

For a reader, this is the part that identifies what signal format the equipment is expected to handle and what overhead or framing conventions apply.

Trail termination behavior

The trail termination sections cover framing, defect indication, and status reporting. Across the annexes, these items include signals such as Frame Alignment Signal (FAS), Remote Defect Indication (RDI), and related reported conditions such as SSF, DEG, UNEQ, TIM, LTC, ODI and OEI where applicable.

These entries matter in practice because they show how the equipment detects loss of alignment, defect conditions, and trace problems, and what it reports to supervision or management functions.

Adaptation, justification, and buffering

The adaptation source and sink functions describe how the path-layer signals are multiplexed, mapped, recovered, and justified. Many of the annex tables deal with elastic stores, justification control, pointer handling, and the timing behavior needed to accommodate plesiochronous signals.

For users, this is the key part that affects interoperability. It tells you what the equipment does when clock rates differ and how it preserves signal integrity while moving between layers.

Monitoring and protection-related behavior

The non-intrusive monitoring functions record reported conditions and performance-related counters without disturbing the main signal path. In the higher-layer annexes, monitoring also covers trace identifiers, defect detection, and status conversion.

That matters because network operators and test labs need to verify observed behavior without changing the traffic path they are measuring.

What terms does SIST EN 300 417-5-2 V1.1.1:2003 define?

• Implementation Conformance Statement (ICS) - the completed statement used to declare which functions and options an implementation supports.
• Implementation Under Test (IUT) - the implementation being assessed against the ETS.
• System Under Test (SUT) - the system setup used for the conformance evaluation.
• Plesiochronous Digital Hierarchy (PDH) - the transport hierarchy covered by the path-layer functions in this document.
• Frame Alignment Signal (FAS) - the framing pattern used to recognize and align received frames.
• Remote Defect Indication (RDI) - the indication used to signal a defect condition to the far end.
• Trail Trace Identifier (TTI) - the identifier used to check that the correct trail is being received.
• Characteristic Information (CI) - the frame or signal format associated with a given path layer.
• Adapted Information (AI) - the payload or mapped signal carried within that path layer.

Who uses SIST EN 300 417-5-2 V1.1.1:2003?

SIST EN 300 417-5-2 V1.1.1:2003 is used by equipment suppliers, conformance test laboratories, network operators, and quality or procurement teams that need a clear statement of PDH path-layer support. It is especially useful when a product must be checked against ETS 300 417-5-1 and the supplier must document which functions are implemented.

Test teams use it to structure interoperability and conformance checking. Buyers and quality managers use it to compare declared support across products and to confirm that the implementation covers the path-layer functions they need.

Which standards are used with SIST EN 300 417-5-2 V1.1.1:2003?

Standard	Role in this document
ETS 300 417-5-1	The companion document named in the scope; this ICS proforma is for it
EN 300 417-1-1	Used for trail termination point mode in several annexes
ETS 300 337	Referenced for signal structure and related mapping details
ETS 300 167	Referenced for 2 048 kbit/s signal structure in the P12s annex
G.751	Referenced for PDH frame and justification behavior in several layers
G.742	Referenced for 8 448 kbit/s signal structure and justification behavior
G.704	Referenced for CRC-4 and multiframe-related P12s behavior
G.823	Referenced for jitter and buffer behavior in adaptation functions

These references support the annex tables by defining the frame structures, pointer formats, and timing or jitter behavior that the proforma asks the implementer to declare.

What does the SIST EN 300 417-5-2 V1.1.1:2003 document contain?

The document is mainly a set of completion forms and structured function tables. It contains annex-by-annex checklists for P4e, P31e, P22e, P12s, P31s and P4s path layers, plus guidance on how to fill them in.

The annex tables cover identification data, global conformance statements, and detailed questions on characteristic information, adaptation, trail termination, monitoring, clock adaptation, and tandem connection sub-layer behavior. Many of the entries point to figures and tables that define frame layouts, overhead bytes, pointer handling, justification processes, and defect handling.

For design teams, the document acts as a conformance recording template. For test teams, it is a checklist for verifying which functions are present and how they behave.

SLOVENSKI STANDARD
01-december-2003
3UHQRVLQPXOWLSOHNVLUDQMH70±*HQHULþQH]DKWHYH]DSUHQRVQRIXQNFLRQDOQRVW
RSUHPH±GHO)XQNFLMHSODVWLSRWLSULSOH]LRKURQLGLJLWDOQLKLHUDUKLML3'+±
3URIRUPDVSHFLILNDFLMDL]MDYHRVNODGQRVWLL]YHGEH,&6
Transmission and Multiplexing (TM); Generic requirements of transport functionality of
equipment; Part 5-2: Plesiochronous Digital Hierarchy (PDH) path layer functions;
Implementation Conformance Statement (ICS) proforma specification
Ta slovenski standard je istoveten z: EN 300 417-5-2 Version 1.1.1
ICS:
33.040.20 Prenosni sistem Transmission systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Transmission and Multiplexing (TM);
Generic requirements of transport functionality of equipment;
Part 5-2: Plesiochronous Digital Hierarchy (PDH)
path layer functions;
Implementation Conformance Statement (ICS)
proforma specification
2 ETSI EN 300 417-5-2 V1.1.1 (1999-08)
Reference
DEN/TM-01015-5-2 (3v19iico.PDF)
Keywords
ICS, SDH, PDH , testing, transmission
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: [phone]  Fax: [phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
[e-mail]
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: [e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1999.
All rights reserved.
ETSI
3 ETSI EN 300 417-5-2 V1.1.1 (1999-08)
Contents
Intellectual Property Rights.13
Foreword .13
Introduction .14
1 Scope.15
2 References.15
3 Definitions and abbreviations .16
3.1 Definitions . 16
3.2 Abbreviations. 16
4 Conformance to this ICS proforma specification .19
Annex A (normative): ICS proforma for EN 300 417-5-1.20
A.1 Guidance for completing the ICS proforma.20
A.1.1 Purposes and structure . 20
A.1.2 Abbreviations and conventions. 20
A.1.3 Instructions for completing the ICS proforma . 22
Annex B (normative): ICS proforma for P4e Path Layer .23
B.1 Identification of the implementation.23
B.1.1 Date of the statement . 23
B.1.2 Implementation Under Test (IUT) identification . 23
B.1.3 System Under Test (SUT) identification. 24
B.1.4 Product supplier. 24
B.1.5 Client . 25
B.1.6 ICS contact person. 25
B.2 Identification of the ETS.26
B.3 Global statement of conformance of P4e Path Layer .26
B.4 P4e Path Layer Functions .26
B.4.0 P4e Path Layer Description . 26
B.4.0.1 Characteristic Information. 28
B.4.0.2 Adapted information . 29
B.4.1 P4e Connection function. 29
B.4.2 P4e Trail Termination functions . 29
B.4.2.1 P4e Trail Termination Source P4e_TT_So . 29
B.4.2.1.1 Processes (P4e_TT_So). 29
B.4.2.2 P4e Trail Termination Sink P4e_TT_Sk. 30
B.4.2.2.1 Management information (P4e_TT_Sk). 30
B.4.2.2.2 Processes (P4e_TT_Sk). 30
B.4.2.2.3 Defects (P4e_TT_Sk) . 31
B.4.2.2.4 Consequent actions (P4e_TT_Sk) . 31
B.4.2.2.5 Defect Correlations (P4e_TT_Sk). 31
B.4.2.2.6 Performance monitoring (P4e_TT_Sk) . 32
B.4.3 P4e Adaptation functions. 32
B.4.3.1 P4e to P31x Adaptation Source P4e/P31x_A_So/i . 32
B.4.3.1.1 Management information (P4e/P31x_A_So). 32
B.4.3.1.2 Processes (P4e/P31x_A_So) . 33
B.4.3.2 P4e to P31x Adaptation Sink P4e/P31x_A_Sk/i. 34
B.4.3.2.1 Management information (P4e/P31x_A_Sk). 34
B.4.3.2.2 Processes (P4e/P31x_A_Sk). 34
B.4.3.2.3 Consequent actions (P4e/P31x_A_Sk) . 36
ETSI
4 ETSI EN 300 417-5-2 V1.1.1 (1999-08)
B.4.3.3 P4e to P31e Adaptation Source P4e/P31e_A_So/i. 36
B.4.3.3.1 Management information (P4e/P31e_A_So). 36
B.4.3.3.2 Processes (P4e/P31e_A_So). 37
B.4.3.4 P4e to P31e Adaptation Sink P4e/P31e_A_Sk/i . 38
B.4.3.4.1 Management information(P4e/P31e_A_Sk) . 38
B.4.3.4.2 Processes (P4e/P31e_A_Sk). 39
B.4.3.4.3 Defects (P4e/P31e_A_Sk) . 41
B.4.3.4.4 Consequent actions (P4e/P31e_A_Sk) . 41
B.4.3.4.5 Defect Correlations (P4e/P31e_A_Sk) . 41
B.4.3.5 P4e to P31s Adaptation Source P4e/P31s_A_So/i. 42
B.4.3.5.1 Management information (P4e/P31s_A_So/i) . 42
B.4.3.5.2 Processes (P4e/P31s_A_So/i). 42
B.4.3.6 P4e to P31s Adaptation Sink P4e/P31s_A_Sk/i. 43
B.4.3.6.1 Management information (P4e/P31s_A_Sk) . 44
B.4.3.6.2 Processes (P4e/P31s_A_Sk). 44
B.4.3.6.3 Defects (P4e/P31s_A_Sk) . 46
B.4.3.6.4 Consequent actions (P4e/P31s_A_Sk). 47
B.4.3.6.5 Defect correlation (P4e/P31s_A_Sk). 47
B.4.4 P4e Layer Monitoring Functions . 47
B.4.4.1 P4e Layer Non-intrusive Monitoring Function P4em_TT_Sk .47
B.4.4.1.1 Management information (P4em_TT_Sk). 47
B.4.4.1.2 Processes . 48
B.4.4.1.3 Defects (P4em_TT_Sk) . 48
B.4.4.1.4 Consequent actions (P4em_TT_Sk) . 49
B.4.4.1.5 Defect Correlations (P4em_TT_Sk). 49
B.4.4.1.6 Performance Monitoring (P4em_TT_Sk). 49
B.4.5 P4e PDH Equipment Clock Adaptation Source P4e_PEC. 49
B.4.5.1 Processes (P4e_PEC) . 50
Annex C (normative): ICS proforma for P31e Path Layer .51
C.1 Identification of the implementation.51
C.1.1 Date of the statement . 51
C.1.2 Implementation Under Test (IUT) identification . 51
C.1.3 System Under Test (SUT) identification. 51
C.1.4 Product supplier. 52
C.1.5 Client . 52
C.1.6 ICS contact person. 53
C.2 Identification of the ETS.53
C.3 Global statement of conformance of P31e Path Layer .54
C.4 P31e Path Layer Functions .54
C.4.0 P31e Path Layer Description . 54
C.4.0.1 Characteristic Information. 56
C.4.0.2 Adapted information . 56
C.4.1 P31e Connection function. 56
C.4.2 P31e Trail Termination functions . 56
C.4.2.1 P31e Trail Termination Source P31e_TT_So . 57
C.4.2.1.1 Processes (P31e_TT_So). 57
C.4.2.2 P31e Trail Termination Sink P31e_TT_Sk. 57
C.4.2.2.1 Management information (P31e_TT_Sk). 57
C.4.2.2.2 Processes (P31e_TT_Sk). 58
C.4.2.2.3 Defects (P31e_TT_Sk) . 59
C.4.2.2.4 Consequent actions (P31e_TT_Sk) . 59
C.4.2.2.5 Defect Correlations (P31e_TT_Sk). 59
C.4.2.2.6 Performance monitoring (P31e_TT_Sk) . 59
C.4.3 P31e Adaptation functions. 60
C.4.3.1 P31e to P22x Adaptation Source P31e/P22x_A_So/i . 60
C.4.3.1.1 Management information (P31e/P22x_A_So). 60
C.4.3.1.2 Processes (P31e/P22x_A_So) . 60
ETSI
5 ETSI EN 300 417-5-2 V1.1.1 (1999-08)
C.4.3.2 P31e to P22x Adaptation Sink P31e/P22x_A_Sk/i. 61
C.4.3.2.1 Management information (P31e/P22x_A_Sk). 62
C.4.3.2.2 Processes (P31e/P22x_A_Sk). 62
C.4.3.2.3 Consequent actions (P31e/P22x_A_Sk) . 64
C.4.3.3 P31e to P22e Adaptation Source P31e/P22e_A_So/i. 64
C.4.3.3.1 Management information (P31e/P22e_A_So/i). 64
C.4.3.3.2 Processes (P31e/P22e_A_So/i) . 65
C.4.3.4 P31e to P22e Adaptation Sink P31e/P22e_A_Sk/i . 66
C.4.3.4.1 Management information(P31e/P22e_A_Sk/i). 66
C.4.3.4.2 Processes (P31e/P22e_A_Sk). 66
C.4.3.4.3 Defects (P31e/P22e_A_Sk) . 69
C.4.3.4.4 Consequent actions (P31e/P22e_A_Sk) . 69
C.4.3.4.5 Defect Correlations (P31e/P22e_A_Sk) . 69
C.4.4 P31e Layer Monitoring Functions . 70
C.4.4.1 P31e Layer Non-intrusive Monitoring Function P31em_TT_Sk . 70
C.4.4.1.1 Management information (P31em_TT_Sk). 70
C.4.4.1.2 Processes . 70
C.4.4.1.3 Defects (P31em_TT_Sk) . 71
C.4.4.1.4 Consequent actions (P31em_TT_Sk) . 71
C.4.4.1.5 Defect Correlations (P31em_TT_Sk). 71
C.4.4.1.6 Performance Monitoring (P31em_TT_Sk). 72
C.4.5 P31e PDH Equipment Clock Adaptation Source P31e_PEC. 72
C.4.5.1 Processes (P31em_TT_Sk) . 72
Annex D (normative): ICS proforma for P22e Path Layer .73
D.1 Identification of the implementation.73
D.1.1 Date of the statement . 73
D.1.2 Implementation Under Test (IUT) identification . 73
D.1.3 System Under Test (SUT) identification. 74
D.1.4 Product supplier. 74
D.1.5 Client . 75
D.1.6 ICS contact person. 75
D.2 Identification of the ETS.75
D.3 Global statement of conformance of P22e Path Layer .76
D.4 P22e Path Layer Functions .76
D.4.0 P22e Path Layer Description . 76
D.4.0.1 Characteristic Information. 77
D.4.0.2 Adapted information . 78
D.4.1 P22e Connection function. 78
D.4.2 P22e Trail Termination functions . 78
D.4.2.1 P22e Trail Termination Source P22e_TT_So . 78
D.4.2.1.1 Processes (P22e_TT_So). 78
D.4.2.2 P22e Trail Termination Sink P22e_TT_Sk. 79
D.4.2.2.1 Management information (P22e_TT_Sk). 79
D.4.2.2.2 Processes (P22e_TT_Sk). 79
D.4.2.2.3 Defects (P22e_TT_Sk) . 80
D.4.2.2.4 Consequent actions (P22e_TT_Sk) . 80
D.4.2.2.5 Defect Correlations (P22e_TT_Sk). 80
D.4.2.2.6 Performance monitoring (P22e_TT_Sk) . 81
D.4.3 P22e Adaptation functions. 81
D.4.3.1 P22e to P12x Adaptation Source P22e/P12x_A_So/i . 81
D.4.3.1.1 Management information (P22e/P12x_A_So). 81
D.4.3.1.2 Processes (P22e/P12x_A_So) . 81
D.4.3.2 P22 . 82
D.4.3.2.1 Management information (P22e/P12x_A_Sk). 83
D.4.3.2.2 Processes (P22e/P12x_A_Sk). 83
D.4.3.2.3 Consequent actions (P22e/P12x_A_Sk) . 85
D.4.3.3 P22e to P12s Adaptation Source P22e/P12s_A_So/i. 85
ETSI
6 ETSI EN 300 417-5-2 V1.1.1 (1999-08)
D.4.3.3.1 Management information (P22e/P12s_A_So/i) . 85
D.4.3.3.2 Processes (P22e/P12s_A_So/i). 85
D.4.3.4 P22e to P12s Adaptation Sink P22e/P12s_A_Sk/i. 86
D.4.3.4.1 Management information (P22e/P12s_A_Sk) . 87
D.4.3.4.2 Processes (P22e/P12s_A_Sk). 87
D.4.3.4.3 Defects (P22e/P12s_A_Sk) . 89
D.4.3.4.4 Consequent actions (P22e/P12s_A_Sk). 90
D.4.3.4.5 Defect correlation (P22e/P12s_A_Sk). 90
D.4.4 P22e Layer Monitoring Functions . 90
D.4.4.1 P22e Layer Non-intrusive Monitoring Function P22em_TT_Sk . 90
D.4.4.1.1 Management information (P22em_TT_Sk). 90
D.4.4.1.2 Processes . 91
D.4.4.1.3 Defects (P22em_TT_Sk) . 92
D.4.4.1.4 Consequent actions (P22em_TT_Sk) . 92
D.4.4.1.5 Defect Correlations (P22em_TT_Sk). 92
D.4.4.1.6 Performance Monitoring (P22em_TT_Sk). 92
D.4.5 P22e PDH Equipment Clock Adaptation Source P22e_PEC. 93
D.4.5.1 Processes (P22em_TT_Sk) . 93
Annex E (normative): ICS proforma for P12s Path Layer.94
E.1 Identification of the implementation.94
E.1.1 Date of the statement . 94
E.1.2 Implementation Under Test (IUT) identification . 94
E.1.3 System Under Test (SUT) identification. 95
E.1.4 Product supplier. 95
E.1.5 Client . 96
E.1.6 ICS contact person. 96
E.2 Identification of the ETS.96
E.3 Global statement of conformance of P12s Path Layer.97
E.4 P12s Path Layer Functions.97
E.4.0 P12s Path Layer Description. 97
E.4.0.1 Characteristic Information. 98
E.4.0.2 Adapted information . 99
E.4.1 P12s Connection function . 99
E.4.2 P12s Trail Termination functions . 99
E.4.2.1 P12s Trail Termination Source P12s_TT_So. 99
E.4.2.1.1 Management information (P12s_TT_So) . 99
E.4.2.1.2 Processes (P12s_TT_So). 100
E.4.2.1.3 Consequent actions (P12s_TT_So) . 101
E.4.2.2 P12s Trail Termination Sink P12s_TT_Sk . 101
E.4.2.2.1 Management information (P12s_TT_Sk) . 102
E.4.2.2.2 Processes (P12s_TT_Sk). 103
E.4.2.2.3 Defects (P12s_TT_Sk) . 104
E.4.2.2.4 Consequent actions (P12s_TT_Sk). 105
E.4.2.2.5 Defect Correlations (P12s_TT_Sk) . 105
E.4.2.2.6 Performance monitoring (P12s_TT_Sk). 106
E.4.3 P12s Adaptation functions . 106
E.4.3.1 P12s to P0-31c Adaptation Source P12s/P0-31c_A_So. 106
E.4.3.1.1 Management information (P12s/P0-31c_A_So). 106
E.4.3.1.2 Processes (P12s/P0-31c_A_So). 107
E.4.3.2 P12s to P0-31c Adaptation Sink P12s/P0-31c_A_Sk . 107
E.4.3.2.1 Management information (P12s/P0-31c_A_Sk). 107
E.4.3.2.2 Processes (P12s/P0-31c_A_Sk). 108
E.4.3.2.3 Consequent actions (P12s/P0-31c_A_Sk) . 108
E.4.3.3 P12s to SD adaptation source P12s/SD_A_So. 108
E.4.3.4 P12s to SD adaptation sink P12s/SD_A_Sk. 108
E.4.3.5 P12s to ATM VP compound adaptation source P12s/Avp_A_So. 108
E.4.3.6 P12s to ATM VP compound adaptation sink P12s/Avp_A_Sk . 109
ETSI
7 ETSI EN 300 417-5-2 V1.1.1 (1999-08)
E.4.3.7 P12s Layer Clock adaptation source P12s-LC_A_So . 109
E.4.4 P12s Layer Monitoring Functions. 109
E.4.4.1 P12s Layer Non-intrusive Monitoring Function P12sm_TT_Sk. 109
E.4.4.1.1 Management information (P12sm_TT_Sk) . 109
E.4.4.1.2 Processes . 110
E.4.4.1.3 Defects (P12sm_TT_Sk) . 112
E.4.4.1.4 Consequent actions (P12sm_TT_Sk). 113
E.4.4.1.5 Defect Correlations (P12sm_TT_Sk) . 113
E.4.4.1.6 Performance Monitoring (P12sm_TT_Sk) . 114
Annex F (normative): ICS proforma for P31s Path Layer.115
F.1 Identification of the implementation.115
F.1.1 Date of the statement . 115
F.1.2 Implementation Under Test (IUT) identification . 115
F.1.3 System Under Test (SUT) identification. 116
F.1.4 Product supplier. 116
F.1.5 Client . 117
F.1.6 ICS contact person. 117
F.2 Identification of the ETS.117
F.3 Global statement of conformance of P31s Path Layer.118
F.4 P31s Path Layer Functions.118
F.4.0 P31s Path Layer Description. 118
F.4.0.1 Characteristic Information. 120
F.4.0.2 Adapted information . 121
F.4.1 P31s Connection function . 121
F.4.2 P31s Trail Termination functions . 121
F.4.2.1 P31s Trail Termination Source P31s_TT_So. 121
F.4.2.1.1 Management information (P31s_TT_So) . 121
F.4.2.1.2 Processes (P31s_TT_So). 122
F.4.2.2 P31s Trail Termination Sink P31s_TT_Sk . 122
F.4.2.2.1 Management information (P31s_TT_Sk) . 123
F.4.2.2.2 Processes (P31s_TT_Sk). 124
F.4.2.2.3 Defects (P31s_TT_Sk) . 125
F.4.2.2.4 Consequent actions (P31s_TT_Sk). 126
F.4.2.2.5 Defect Correlations (P31s_TT_Sk) . 126
F.4.2.2.6 Performance monitoring (P31s_TT_Sk). 127
F.4.3 P31s Adaptation functions . 127
F.4.3.1 P31s to VC-12, VC-11 Compound Adaptation Source P31s/SX_A_So . 127
F.4.3.1.1 P31s to TUG Adaptation Source P31s/TUG_A_So . 128
F.4.3.1.1.1 Management information (P31s/TUG_A_So) . 128
F.4.3.1.1.2 Processes (P31s/TUG_A_So) . 128
F.4.3.1.2 TUG Termination Source TUG_T_So . 129
F.4.3.1.3 TUG to S12 Adaptation Source TUG/S12_A_So . 129
F.4.3.1.3.1 Management information (TUG/S12_A_So). 129
F.4.3.1.3.2 Processes (TUG/S12_A_So). 130
F.4.3.1.3.3 Consequent actions (TUG/S12_A_So) . 131
F.4.3.1.4 TUG to S11 Adaptation Source TUG/S11*_A_So . 131
F.4.3.1.4.1 Management information (TUG/S11*_A_So) . 131
F.4.3.1.4.2 Processes (TUG/S11*_A_So). 132
F.4.3.1.4.3 Consequent actions (TUG/S11*_A_So) . 133
F.4.3.2 P31s to VC-12, VC-11 Compound Adaptation Sink P31s/SX_A_Sk. 133
F.4.3.2.1 P31s to TUG Adaptation Sink P31s/TUG_A_Sk . 134
F.4.3.2.1.1 Management information (P31s/TUG_A_Sk) . 134
F.4.3.2.1.2 Processes (P31s/TUG_A_Sk) . 134
F.4.3.2.1.3 Defects (P31s/TUG_A_Sk). 135
F.4.3.2.1.4 Consequent actions (P31s/TUG_A_Sk). 136
F.4.3.2.1.5 Defect Correlations (P31s/TUG_A_Sk) . 136
F.4.3.2.2 TUG Termination Sink TUG_T_Sk . 136
ETSI
8 ETSI EN 300 417-5-2 V1.1.1 (1999-08)
F.4.3.2.2.1 Consequent actions (TUG_T_Sk). 136
F.4.3.2.3 TUG to S12 Adaptation Sink TUG/S12_A_Sk . 136
F.4.3.2.3.1 Management information (TUG/S12_A_Sk) . 137
F.4.3.2.3.2 Processes (TUG/S12_A_Sk). 137
F.4.3.2.3.3 Defects (TUG/S12_A_Sk) . 138
F.4.3.2.3.4 Consequent actions (TUG/S12_A_Sk) . 138
F.4.3.2.3.5 Defect Correlations (TUG/S12_A_Sk) .
...