SIST EN 300 324-2 V1.2.3:2005

• Abstract:

  Revised PICS.

• Status: Published
• Publication Date: 31-Mar-2005
• ICS: 33.040.30 - Switching and signalling systems
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2005
• Due Date: 01-Apr-2005
• Completion Date: 01-Apr-2005
• Ref Project: ETSI EN 300 324-2 V1.2.2 (1999-06) - V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification

SIST EN 300 324-2 V1.2.3:2005 is the Slovenian adoption of ETSI EN 300 324-2 V1.2.3. It is a Protocol Implementation Conformance Statement (PICS) proforma for the V5.1 interface at a digital Local Exchange (LE) and for the support of an Access Network (AN), used by suppliers and network operators to record or assess which capabilities are implemented.

What does SIST EN 300 324-2 V1.2.3:2005 specify?

SIST EN 300 324-2 V1.2.3:2005 specifies the PICS proforma for the implementation flexibility allowed by the V5.1 interface defined in EN 300 324-1. In practice, it gives a structured way to state which mandatory and optional functions an LE or AN implementation supports, so that a network operator can check conformance or define implementation requirements.

The document is organized as a short conformance and reference framework followed by the PICS proforma itself. It contains Clauses 1 to 6 and one informative annex.

Annex	What it covers
Annex A (informative)	Instructions for completing the PICS proforma

Clause 1 states the scope, Clause 2 lists references, Clause 3 defines terms, Clause 4 lists abbreviations, Clause 5 states conformance, and Clause 6 contains the PICS tables. Annex A explains how to fill in the form.

What are the key requirements of SIST EN 300 324-2 V1.2.3:2005?

SIST EN 300 324-2 V1.2.3:2005 is mainly a declaration and assessment document, not a protocol specification. Its key requirement is that the supplier of an implementation claiming conformance to EN 300 324-1 completes the PICS and identifies the supplier and the implementation. That matters because the document is meant to support a static conformance review against the implemented functions.

Conformance statement and identification

Clause 5 requires the supplier to complete the PICS proforma and provide the information needed to identify the supplier and the implementation. Clause 6.1 then structures that identification for the Implementation Under Test (IUT), the System Under Test (SUT), the product supplier, the client, and the PICS contact person. In practice, this creates a traceable record for testing, procurement, and acceptance.

Clause 6.2 asks for the relationship between the PICS and the System Conformance Statement (SCS). That matters when a whole system, rather than a single device, is being assessed.

Global conformance

Clause 6.4 asks whether the implementation meets all mandatory requirements of the referenced standard. If the answer is No, the non-supported mandatory capabilities must be identified and explained. This lets reviewers quickly see whether the implementation is fully conformant or only partially conformant.

Main features for LE and AN

Clauses 6.5 and 6.6 split the questionnaire into two mirrored parts, one for the Local Exchange and one for the Access Network. Both parts cover main features such as ISDN ports, PSTN ports, semipermanent leased lines, communication channel time slot allocation, and the envelop function. In practice, this tells an operator which service types and channel arrangements the implementation is built to handle.

The tables also use conditional predicates such as O.1, MX.1, MX.2, MX.3 and MX.4. These indicate that some items apply only when specific conditions are met, such as when required by the network operator, by the national PSTN protocol, or by the exception rules named in EN 300 324-1. That helps avoid overclaiming support for features that are only relevant in certain deployments.

Layer 1 and Layer 2

The PICS asks whether the implementation supports the Layer 1 interface in balanced or coaxial form and the interface control procedures. It also asks about detection of loss of signals, including the 1 ms below 20 dB condition and the 10 consecutive ZEROs condition. For buyers and testers, this is the practical check for physical link behavior and fault detection.

At Layer 2, the proforma covers the frame structure for peer-to-peer communication, the format of the data link envelop, envelop address values, and the LAPV5 data link sublayer for control and PSTN protocol. It also includes frame relay function in the AN. These items show how the implementation carries signalling and control data across the link.

Layer 3 protocol capabilities

For the PSTN side, the proforma covers functions such as DTMF senders/receivers, tone generators, announcement, PSTN protocol entity, and PSTN call control entity. For the control side, it includes the Control protocol entity, ISDN user port status indication and control, PSTN user port status indication and control, performance monitoring, and common control items such as variant and interface ID control and re-provisioning support. In practice, this tells an operator what service control and maintenance behavior is available.

The AN-specific part also includes control of time critical sequences and meter pulse scheduling in the AN. These items matter where the AN performs functions that affect signalling timing or metering behavior.

Protocol data units

Clauses 6.5.3 and 6.6.3 list the Protocol Data Units (PDUs) that may be supported. For the PSTN protocol, the PICS covers messages such as ESTABLISH, SIGNAL, STATUS, DISCONNECT, and PROTOCOL PARAMETER, plus information elements such as protocol discriminator, layer 3 address, cause, pulse type, steady signal, and metering-related items. This is the practical checklist for message compatibility.

For the control protocol, the proforma covers common control and port control messages and information elements, including FE101 to FE208 items for access activation, blocking, D-channel block and unblock, and re-provisioning signaling. That lets testers confirm which control exchanges the implementation can send and receive.

What terms does SIST EN 300 324-2 V1.2.3:2005 define?

• Protocol Implementation Conformance Statement (PICS) - A supplier's statement of which capabilities are implemented for a given OSI protocol.
• PICS proforma - A questionnaire-style document that becomes the PICS when completed for a specific implementation.
• Static conformance review - A review that compares the completed PICS with the standard's static conformance requirements.
• Implementation Under Test (IUT) - The implementation being checked for conformance.
• System Under Test (SUT) - The system in which the IUT resides during the conformance assessment.
• System Conformance Statement (SCS) - A document that summarizes which standards a system claims to implement.
• Access Network (AN) - The network side of the V5.1 interface that supports access functions.
• Local Exchange (LE) - The digital local exchange side of the V5.1 interface.

Who uses SIST EN 300 324-2 V1.2.3:2005?

SIST EN 300 324-2 V1.2.3:2005 is used in telecommunications switching and signalling, especially where a V5.1 interface connects a Local Exchange and an Access Network. Network operators use it to state required capabilities and to check whether an implementation matches those requirements.

Product suppliers use it to describe the functions their LE or AN implementation supports. Conformance test teams and quality staff use it to select test cases, document options, and record whether mandatory capabilities are present.

Which standards are used with SIST EN 300 324-2 V1.2.3:2005?

Reference	What it contributes
EN 300 324-1 (V1.2)	The V5.1 interface specification that this PICS applies to
ISO/IEC 9646-1	General concepts for OSI conformance testing
ISO/IEC 9646-7	Rules and guidance for implementation conformance statements
Part 1 of EN 300 324	The base V5.1 interface specification named in the foreword
Parts 3 to 9 of EN 300 324	Test suite structure, abstract test suites, PIXIT proformas, and physical layer test specification for the V5.1 interface

What does the SIST EN 300 324-2 V1.2.3:2005 document contain?

SIST EN 300 324-2 V1.2.3:2005 contains ready-to-complete tables for implementation identification, supplier details, client details, and contact information. It also contains yes/no checklists for the global conformance statement, LE and AN main features, protocol layers, and protocol data units.

The document is structured so that each supported item can be declared against the relevant referenced clause in EN 300 324-1. That makes it useful for design reviews, procurement questionnaires, conformance testing, and acceptance records.

Annex A gives instructions for completing the proforma. It explains how to fill in the IUT and SUT details, how to relate the PICS to an SCS, and how to treat mandatory, optional, and conditional items.

SLOVENSKI STANDARD
01-april-2005
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo
dostopovnemu omrežju (AN) – 2. del: Izjava o skladnosti izvedbe protokola (PICS)
– Proforma specifikacija
V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS) proforma
specification
Ta slovenski standard je istoveten z: EN 300 324-2 Version 1.2.3
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 300 324-2 V1.2.3 (1999-06)
European Standard (Telecommunications series)
V interfaces at the digital Local Exchange (LE);
V5.1 interface for the support of Access Network (AN);
Part 2: Protocol Implementation Conformance
Statement (PICS) proforma specification

2 ETSI EN 300 324-2 V1.2.3 (1999-06)
Reference
REN/SPS-09050-2 (300i0iq0.PDF)
Keywords
V interface, V5 interface, LE, AN, PICS
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 324-2 V1.2.3 (1999-06)
Contents
Intellectual Property Rights . 5
Foreword. 5
1 Scope. 6
2 References . 6
3 Definitions . 6
4 Abbreviations. 7
5 Conformance. 7
6 PICS proforma . 8
6.1 Identification of the implementation. 8
6.1.1 Implementation Under Test (IUT) identification . 8
6.1.2 System Under Test (SUT) identification. 8
6.1.3 Product supplier . 8
6.1.4 Client. 9
6.1.5 PICS contact person . 9
6.2 PICS/System Conformance Statement (SCS) . 10
6.3 Identification of the protocol . 10
6.4 Global statement of conformance . 10
6.5 Local exchange . 11
6.5.1 Main features. 11
6.5.2 Protocol. 12
6.5.2.1 Layer 1. 12
6.5.2.2 Layer 2. 12
6.5.2.3 Layer 3. 12
6.5.2.3.1 PSTN functions. 12
6.5.2.3.2 PSTN protocol . 13
6.5.2.3.3 Control protocol. 13
6.5.2.3.4 Port control protocol. 13
6.5.2.3.5 Common control . 13
6.5.3 Protocol data units. 14
6.5.3.1 PSTN protocol. 14
6.5.3.1.1 Messages. 14
6.5.3.1.2 Information elements, general. 15
6.5.3.1.3 Information elements, pulse type . 16
6.5.3.1.4 Information elements, steady signals . 17
6.5.3.1.5 Information elements, cause types . 19
6.5.3.1.6 Information elements, information element fields. 19
6.5.3.2 Control protocol . 20
6.5.3.2.1 Messages. 20
6.5.3.2.2 Information elements, general. 20
6.5.3.2.3 Information elements, port control. 20
6.5.3.2.4 Information elements, common control . 21
6.6 Access network . 21
6.6.1 Main features. 21
6.6.2 Protocol. 23
6.6.2.1 Layer 1. 23
6.6.2.2 Layer 2. 23
6.6.2.3 Layer 3. 23
6.6.2.3.1 PSTN protocol . 23
6.6.2.3.2 Control protocol. 24
6.6.2.3.3 Port control protocol. 24
6.6.2.3.4 Common control . 24
6.6.3 Protocol data units. 25
ETSI
4 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.6.3.1 PSTN protocol. 25
6.6.3.1.1 Messages. 25
6.6.3.1.2 Information elements, general. 26
6.6.3.1.3 Information elements, pulse type . 27
6.6.3.1.4 Information elements, steady signals . 28
6.6.3.1.5 Information elements, cause types . 30
6.6.3.1.6 Information elements, information element fields. 30
6.6.3.2 Control protocol . 31
6.6.3.2.1 Messages. 31
6.6.3.2.2 Information elements, general. 31
6.6.3.2.3 Information elements, port control. 31
6.6.3.2.4 Information elements, common control . 32
Annex A (informative): Instructions for completing the PICS proforma. 33
A.1 Identification of the implementation . 33
A.2 Global statement of conformance. 33
A.3 Main features . 33
A.4 Protocol. 33
A.5 Protocol data units . 33
History. 34
ETSI
5 ETSI EN 300 324-2 V1.2.3 (1999-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocols and Switching (SPS).
The present document is part 2 of a multi-part standard covering the V5.1 interface specification as described below:
Part 1: "V5.1 interface specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (AN side)";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network layer (AN side)";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LE side)";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network layer (LE side)";
Part 7: "Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer";
Part 8: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the data link layer";
Part 9: "Test specification for the physical layer".
To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and
options have been implemented for a given Open Systems Interconnection (OSI) protocol. Such a statement is called a
Protocol Implementation Conformance Statement (PICS).
NOTE: It is however possible to use the present document to indicate the basic requirements for an Access
Network (AN) or a Local Exchange (LE) required by a network operator. Specific requirements need to
be added, e.g. the Public Switched Telephone Network (PSTN) port characteristics and conditions.
National transposition dates
Date of adoption of this EN: 21 May 1999
Date of latest announcement of this EN (doa): 31 August 1999
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 29 February 2000
Date of withdrawal of any conflicting National Standard (dow): 29 February 2000
ETSI
6 ETSI EN 300 324-2 V1.2.3 (1999-06)
1 Scope
This second part of EN 300 324 defines the Protocol Implementation Conformance Statement (PICS) proforma for the
implementation flexibility allowed for a V5.1 interface defined in EN 300 324-1 [1]. It allows either the Network
Operator to formulate the requirements for V5.1 interface implemented in an Access Network (AN) or Local Exchange
(LE), or to decide whether an implementation meets these requirements. It details in tabular form the implementation
options, i.e. the optional functions additional to those which are mandatory to implement.
The present document is in compliance with the relevant requirements and in accordance with the relevant guidance
given in ISO/IEC 9646-7 [3].
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] EN 300 324-1 (V1.2): "Signalling Protocols and Switching (SPS); V interfaces at the digital Local
Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 1: V5.1 interface
specification".
[2] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[3] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
3 Definitions
For the purposes of the present document, the following definitions apply:
Protocol Implementation Conformance Statement (PICS): statement made by the supplier of an Open System
Interconnection (OSI) implementation or system, stating which capabilities have been implemented for a given OSI
protocol (see ISO/IEC 9646-1 [2]).
PICS proforma: document, in the form of a questionnaire, designed by the protocol specifier or conformance test suite
specifier, which when completed for an OSI implementation or system becomes the PICS (see ISO/IEC 9646-1 [2]).
Static conformance review: review of the extent to which the static conformance requirements are met by the
Implementation Under Test (IUT), accomplished by comparing the PICS with the static conformance requirements
expressed in the relevant standard(s) (see ISO/IEC 9646-1 [2]).
ETSI
7 ETSI EN 300 324-2 V1.2.3 (1999-06)
4 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AN Access Network
AND
Boolean "and"
C Conditional requirements (to be observed if the relevant conditions apply)
DTMF Dual Tone Multiple Frequency
ID Identification
IUT Implementation Under Test
LE Local Exchange
M Mandatory requirements (to be observed in all cases)
N/A Not supported, not applicable or the conditions for status are not met
No not supported
NOT Boolean "not"
NT1 Network Termination 1
O Option (may be selected to suit the implementation, provided that any requirements applicable to
the option are observed)
O.n Options, but support required for either at least one or only one of the options in the group labelled
with the same numeral "n"
OR Boolean "or"
OSI Open Systems Interconnection
PICS Protocol Implementation Conformance Statement
PSTN Public Switched Telephone Network
SCS System Conformance Statement
SUT System Under Test
TS Time Slot
Yes Supported
5 Conformance
The supplier of a protocol implementation which is claimed to conform to EN 300 324-1 [1] is required to complete a
copy of the PICS proforma provided in the present document and is required to provide the information necessary to
identify both the supplier and the implementation.
ETSI
8 ETSI EN 300 324-2 V1.2.3 (1999-06)
6 PICS proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users
of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended
purposes and may further publish the completed PICS.
6.1 Identification of the implementation
6.1.1 Implementation Under Test (IUT) identification
IUT name:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
IUT version:
..............................................................................................................................................................................................
6.1.2 System Under Test (SUT) identification
SUT name:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
Hardware configuration:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
Operating system:
..............................................................................................................................................................................................
6.1.3 Product supplier
Name:
..............................................................................................................................................................................................
Address:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
Telephone number:
..............................................................................................................................................................................................
Facsimile number:
..............................................................................................................................................................................................
ETSI
9 ETSI EN 300 324-2 V1.2.3 (1999-06)
Additional information:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
6.1.4 Client
Name:
..............................................................................................................................................................................................
Address:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
Telephone number:
..............................................................................................................................................................................................
Facsimile number:
..............................................................................................................................................................................................
Additional information:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
6.1.5 PICS contact person
Name:
..............................................................................................................................................................................................
Telephone number:
..............................................................................................................................................................................................
Facsimile number:
..............................................................................................................................................................................................
Additional information:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
ETSI
10 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.2 PICS/System Conformance Statement (SCS)
Provide the relationship of the PICS with the SCS for the system:
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
..............................................................................................................................................................................................
6.3 Identification of the protocol
This PICS proforma applies to the following standard:
EN 300 324-1 (V1.2): "Signalling Protocols and Switching (SPS); V interfaces at the digital Local Exchange (LE);
V5.1 interface for the support of Access Network (AN); Part 1: V5.1 interface specification".
6.4 Global statement of conformance
The implementation described in this PICS meets all the mandatory requirements of the referenced standard.
[ ] Yes
[ ] No
NOTE: Answering "No" to this question indicates non-conformance to the protocol specification. Non-supported
mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is
non-conforming.
In the tabulations which follow, all references are to EN 300 324-1 [1].
ETSI
11 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.5 Local exchange
6.5.1 Main features
Table 1
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
M1 ISDN ports? O.1 6.1.2 [ ] Yes [ ] No
M2 PSTN ports? O.1 6.1.1 [ ] Yes [ ] No
M3 semipermanent leased lines? O 6.3 [ ] Yes [ ] No
M4 communication channel time slot allocation? M 8.4 [ ] Yes [ ] No
M41 communication path for control functions on TS 16? M 8.4 [ ] Yes [ ] No
M411 communication channel on TS16? M 8.4 [ ] Yes [ ] No
M412 communication channel on TS15? M1 M 8.4 [ ] Yes [ ] No
NOT M1 N/A
M413 communication channel on TS31? M1 and MX.1 M 8.4 [ ] Yes [ ] No
NOT (M1 and N/A
MX.1)
M421 communication path for P-type data on TS 16? M1 M 8.4 [ ] Yes [ ] No
NOT M1 N/A
M422 communication path for P-type data on TS 15? M1 and M412 M 8.4 [ ] Yes [ ] No
NOT (M1 and N/A
M412)
M423 communication path for P-type data on TS 31? M413 M 8.4 [ ] Yes [ ] No
NOT M413 N/A
M431 communication path for F-type data on TS 16? M1 M 8.4 [ ] Yes [ ] No
NOT M1 N/A
M432 communication path for F-type data on TS 15? M1 and M412 M 8.4 [ ] Yes [ ] No
NOT (M1 and N/A
M412)
M433 communication path for F-type data on TS 31? M413 M 8.4 [ ] Yes [ ] No
NOT M413 N/A
M441 communication path for D-channel signalling on TS 16? M1 M 8.4 [ ] Yes [ ] No
NOT M1 N/A
M442 communication path for D-channel signalling on TS 15? M1 and M412 M 8.4 [ ] Yes [ ] No
NOT (M1 and N/A
M412)
M443 communication path for D-channel signalling on TS 31? M413 M 8.4 [ ] Yes [ ] No
NOT M413 N/A
M451 communication path for PSTN signalling on TS 16? M2 M 8.4 [ ] Yes [ ] No
NOT M2 N/A
M452 communication path for PSTN signalling on TS 15? M2 and M412 M 8.4 [ ] Yes [ ] No
NOT (M2 and N/A
M412)
M453 communication path for PSTN signalling on TS 31? M2 and M413 M 8.4 [ ] Yes [ ] No
NOT (M2 and N/A
M413)
M51 allocation of bearer channels to user ports by M 7.2.2 [ ] Yes [ ] No
provisioning?
M52 allocation of EFaddr to ISDN user ports by provisioning? M1 M 7.2.2 [ ] Yes [ ] No
NOT M1 N/A
M53 allocation of L3addr to PSTN user ports by provisioning? M2 M 7.2.2 [ ] Yes [ ] No
NOT M2 N/A
M6 envelop function? M 9 [ ] Yes [ ] No
Predicated imaginary features
MX.1 If required by the network operator O
MX.2 If required by the national PSTN protocol O
O.1 = Support of at least one of these items is required
ETSI
12 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.5.2 Protocol
6.5.2.1 Layer 1
Table 2
Index Protocol capability Conditions for Status Referenc Support
Does the implementation support . status e
P1.1 layer 1 balanced? MX.1 M 4 [ ] Yes [ ] No
NOT MX.1 N/A
P1.2 layer 1 coaxial? MX.1 M 4 [ ] Yes [ ] No
NOT MX.1 N/A
P1.3 interface control procedures? M 14.3 [ ] Yes [ ] No
P1.4 detection of loss of signals; 1 ms below 20 dB? O.1 14.3.2 [ ] Yes [ ] No
P1.5 detection of loss of signals; 10 consecutive ZEROs? O.1 14.3.2 [ ] Yes [ ] No
O.1 = Support of at least one of these items is required.
6.5.2.2 Layer 2
Table 3
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
P2.11 frame structure for peer to peer communication? M 9.1 [ ] Yes [ ] No
P2.12 format of fields for data link envelop? M 9.2 [ ] Yes [ ] No
P2.13 envelop address value for control protocol? M 10.3.2.3 [ ] Yes [ ] No
P2.14 envelop address value for PSTN protocol? M2 M 10.3.2.3 [ ] Yes [ ] No
NOT M2 N/A
P2.15 envelop address values for ISDN ports? M1 M 9.2.2.2 [ ] Yes [ ] No
NOT M1 N/A
P2.2 data link sublayer of LAPV5 for control protocol? M 10 [ ] Yes [ ] No
P2.3 data link sublayer of LAPV5 for PSTN protocol? M2 M 10 [ ] Yes [ ] No
NOT M2 N/A
6.5.2.3 Layer 3
6.5.2.3.1 PSTN functions
Table 4
Index Protocol capability Predicate Status Referenc Support
Does the implementation support . e
P3.11 DTMF senders/receivers? M2 M 13.1.2 [ ] Yes [ ] No
NOT M2 N/A
P3.12 tone generators? M2 M 13.1.2 [ ] Yes [ ] No
NOT M2 N/A
P3.13 announcement? M2 M 13.1.2 [ ] Yes [ ] No
NOT M2 N/A
ETSI
13 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.5.2.3.2 PSTN protocol
Table 5
Index Protocol capability Predicate Status Reference Support
Does the implementation support .
P3.2 PSTN protocol entity? M2 M 13.2 [ ] Yes [ ] No
NOT M2 N/A
P3.3 PSTN call control entity? M2 M 13.5 - 13.7 [ ] Yes [ ] No
NOT M2 N/A
6.5.2.3.3 Control protocol
Table 6
Index Protocol capability Predicate Status Reference Support
Does the implementation support .
P4.0 Control protocol entity? M 14.4.4 [ ] Yes [ ] No
6.5.2.3.4 Port control protocol
Table 7
Index Protocol capability Conditions for Status Referenc Support
Does the implementation support . status e
P4.11 ISDN user port status indication and control? M1 M 14.1 [ ] Yes [ ] No
NOT M1 N/A
P4.12 performance monitoring? M1 AND MX.1 M 14.1.4 [ ] Yes [ ] No
NOT (M1 AND N/A
MX.1)
P4.2 PSTN user port status indication and control? M2 M 14.2 [ ] Yes [ ] No
NOT M2 N/A
6.5.2.3.5 Common control
Table 8
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
P5.1 variant and interface ID control? M 14.5 [ ] Yes [ ] No
P5.2 verify re-provisioning? MX.1 M 14.5 [ ] Yes [ ] No
NOT MX.1 N/A
P5.3 re-provisioning synchronization? MX.1 M 14.5 [ ] Yes [ ] No
NOT MX.1 N/A
ETSI
14 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.5.3 Protocol data units
6.5.3.1 PSTN protocol
6.5.3.1.1 Messages
Table 9
Index Protocol capability Conditions for Status Referenc Support
Does the implementation support . status e
U1.1 ESTABLISH? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.2 ESTABLISH ACK? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.3 SIGNAL? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.4 SIGNAL ACK? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.5 STATUS? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.6 STATUS ENQUIRY? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.7 DISCONNECT? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.8 DISCONNECT COMPLETE? M2 M 13.3 [ ] Yes [ ] No
NOT M2 N/A
U1.9 PROTOCOL PARAMETER? M2 AND MX.2 M 13.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
ETSI
15 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.5.3.1.2 Information elements, general
Table 10
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
U1.10 protocol discriminator? M2 M 13.4.2 [ ] Yes [ ] No
NOT M2 N/A
U1.11 layer 3 address? M2 M 13.4.3 [ ] Yes [ ] No
NOT M2 N/A
U1.12 pulse notification? M2 AND MX.2 M 13.4.6.1 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.13 line information? M2 AND MX.2 M 13.4.6.2 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.14 state? M2 M 13.4.6.3 [ ] Yes [ ] No
NOT M2 N/A
U1.15 autonomous signalling sequence? M2 AND MX.2 M 13.4.6.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.16 sequence response? M2 AND MX.2 M 13.4.6.5 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.17 sequence-number? M2 M 13.4.7.1 [ ] Yes [ ] No
NOT M2 N/A
U1.18 cadenced-ringing? M2 M 13.4.7.2 [ ] Yes [ ] No
NOT M2 N/A
U1.19 pulsed-signal? M2 M 13.4.7.3 [ ] Yes [ ] No
NOT M2 N/A
U1.20 steady-signal? M2 M 13.4.7.4 [ ] Yes [ ] No
NOT M2 N/A
U1.21 digit-signal? M2 M 13.4.7.5 [ ] Yes [ ] No
NOT M2 N/A
U1.22 recognition-time? M2 AND MX.2 M 13.4.7.6 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.23 enable-autonomous-acknowledge? M2 AND MX.2 M 13.4.7.7 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.24 disable-autonomous-acknowledge? M2 AND MX.2 M 13.4.7.8 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.25 cause? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.26 resource-unavailable? M2 M 13.4.7.10 [ ] Yes [ ] No
NOT M2 N/A
U1.27 enable-metering? M2 and MX.2 M 13.4.7.11 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.28 metering-report? M2 and MX.2 M 13.4.7.12 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.29 Attenuation? M2 and MX.2 M 13.4.7.13 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
ETSI
16 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.5.3.1.3 Information elements, pulse type
Table 11
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
U1.30 pulse type: Pulsed normal polarity? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.31 pulse type: Pulsed reversed polarity? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.32 pulse type: Pulsed battery on c-wire? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.33 pulse type: Pulsed on hook? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.34 pulse type: Pulsed reduced battery ? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.35 pulse type: Pulsed no battery? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.36 pulse type: Initial ring? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.37 pulse type: Meter pulse? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.38 pulse type: 50 Hz pulse? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.39 pulse type: Register recall? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.40 pulse type: Pulsed off hook? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.41 pulse type: Pulsed b-wire connected to earth? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.42 pulse type: Earth loop pulse? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.43 pulse type: Pulsed b-wire connected to battery? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.44 pulse type: Pulsed a-wire connected to earth? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.45 pulse type: Pulsed a-wire connected to battery? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.46 pulse type: Pulsed c-wire connected to earth? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.47 pulse type: Pulsed c-wire disconnected? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
ETSI
17 ETSI EN 300 324-2 V1.2.3 (1999-06)
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
U1.48 pulse type: Pulsed normal battery? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.49 pulse type: Pulsed a-wire disconnected? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.50 pulse type: Pulsed b-wire disconnected? M2 AND MX.2 M 13.4.7.3 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
6.5.3.1.4 Information elements, steady signals
Table 12
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
U1.51 steady signal: Normal polarity? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.52 steady signal: Reversed polarity? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.53 steady signal: Battery on c-wire? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.54 steady signal: No battery on c-wire? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.55 steady signal: Off hook? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.56 steady signal: On hook? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.57 steady signal: Battery on a-wire? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.58 steady signal: A-wire on earth? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.59 steady signal: No battery on a-wire? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.60 steady signal: No battery on b-wire? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.61 steady signal: Reduced battery? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.62 steady signal: No battery? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.63 steady signal: Alternate reduced power/no power? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.64 steady signal: Normal battery? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.65 steady signal: Stop ringing? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.66 steady signal: Start pilot frequency? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
ETSI
18 ETSI EN 300 324-2 V1.2.3 (1999-06)
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
U1.67 steady signal: Stop pilot frequency? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.68 steady signal: Low impedance on b-wire? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.69 steady signal: B-wire connected to earth? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.70 steady signal: B-wire disconnected from earth? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.71 steady signal: Normal battery on b-wire? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.72 steady signal: Low loop impedance? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.73 steady signal: High loop impedance? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.74 steady signal: Anomalous loop impedance? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.75 steady signal: A-wire disconnected from earth? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.76 steady signal: C-wire on earth? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.77 steady signal: C-wire disconnected from earth? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.96 steady signal: Signal:Ramp to Reversed Polarity? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
U1.97 steady signal: Signal: Ramp to Normal Polarity? M2 AND MX.2 M 13.4.7.4 [ ] Yes [ ] No
NOT (M2 AND N/A
MX.2)
ETSI
19 ETSI EN 300 324-2 V1.2.3 (1999-06)
6.5.3.1.5 Information elements, cause types
Table 13
Index Protocol capability Conditions for Status Reference Support
Does the implementation support . status
U1.78 cause type: Response to status enquiry? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.79 cause type: Protocol discriminator error? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.80 cause type: L3 address error? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.81 cause type: Message type unrecognized? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.82 cause type: Out of sequence information element? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.83 cause type: Repeated optional information element? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.84 cause type: Mandatory information element missing? M2 M 13.4.7.9 [ ] Yes [ ] No
NOT M2 N/A
U1.85 caus
...