SIST TBR 004 E1:2004/A1:2004

SLOVENSKI STANDARD
SIST TBR 004 E1:2004/A1:2004
01-oktober-2004
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'13ULNOMXþLWYHQH]DKWHYH]D
WHUPLQDOVNRRSUHPR]DSULNOMXþHYDQMHQDRPUHåMH,6'1SUHNSULPDUQHJDGRVWRSD
,6'1
Integrated Services Digital Network (ISDN); Attachment requirements for terminal
equipment to connect to an ISDN using ISDN primary rate access
Ta slovenski standard je istoveten z: TBR 004/A1 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST TBR 004 E1:2004/A1:2004 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST TBR 004 E1:2004/A1:2004

---------------------- Page: 2 ----------------------

SIST TBR 004 E1:2004/A1:2004
TBR 4
AMENDMENT A1
December 1997
Source: BTC Reference: RTBR/BTC-02075
ICS: 33.020
Key words: ISDN, primary, rate, terminal, testing
This amendment A1 modifies
the Technical Basis for Regulation TBR 4 (1995)
Integrated Services Digital Network (ISDN);
Attachment requirements for terminal equipment to connect
to an ISDN using ISDN primary rate access
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1997. All rights reserved.

---------------------- Page: 3 ----------------------

SIST TBR 004 E1:2004/A1:2004
Page 2
TBR 4: November 1995/A1: December 1997
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST TBR 004 E1:2004/A1:2004
Page 3
TBR 4: November 1995/A1: December 1997
Foreword
This amendment to Technical Basis for Regulation (TBR) has been produced by the Business
TeleCommunications (BTC) Technical Committee of the European Telecommunications Standards
Institute (ETSI).
This amendment should be considered as an urgent technical correction.
The amendment has been produced at the request of the Approvals Committee for Terminal Equipment
(ACTE) and:
- contains amendments to the requirements as determined by the special group of the ISDN Type
Approval Advisory Ad-Hoc Group (ITAAAG) in order to align with the "essential requirements"
according to Directive 91/263/EEC;
- contains corrections to reported shortcomings in the Tree and Tabular Combined Notation (TTCN)
at Layers 2 and 3;
- contains TTCN in ISO International Standard (IS) form in place of the Draft ISO International
Standard (DIS) form;
- deselects tests declared by the special group of ITAAAG as being not essential according to
Directive 91/263/EEC;
- contains a complete replacement of the TBR-RT (tables of annex A). The ETSI BTC2-TE5 joint
meeting to discuss the results of the UAP decided to give preference to a complete replacement of
the TBR-RT instead of an amendment of at least each second table which could lead to confusion
to the user of the document.
NOTE: The references to the changed pages in the standard refer to an old presentation. See
history box at the end of the standard itself.
The new presentation format, applied from 1 December 1995, may have different page
numbering. The clause numbering has not changed.

---------------------- Page: 5 ----------------------

SIST TBR 004 E1:2004/A1:2004
Page 4
TBR 4: November 1995/A1: December 1997
Amendments
Page 50, subclause 10.5.1
Add the word "Requirement:" in front of the last paragraph.
Add the following text to the end of the subclause:
Test: This requirement is implicitly tested by other TEI management tests.
Page 52, subclause 10.5.4.2
Amend the list of test cases as indicated:
Test: The test shall be conducted according to annex C, TTCN test cases TC14021, TC14022 TC24007
and TC27031 and test preamble PR31401.
Page 52, subclause 10.5.5.2
Amend the list of test cases as indicated:
Test: The test shall be conducted according to annex C, TTCN test case TC14019TC24007 and
TC27031.
Page 53, subclause 10.5.5.3
Delete entire subclause.
Page 55, subclause 10.6.1.1
Amend text as indicated below:
Reference: ETS 300 125, Part 2, subclause 5.5.1.1.
Requirement: These procedures shall be used to establish multiple frame operation between the network
and a designated user entity.
The data link layer entity shall initiate establishment of multiple frame operation on receipt of the DL-
ESTABLISH-REQUEST primitive from Layer 3. All frames other than unnumbered frame formats
received during the establishment procedures shall be ignored.
Test: The test shall be conducted according to annex C, TTCN test case TC25013 and test preamble
PR37004.
Page 56, subclauses 10.6.3 and 10.6.3.1
Delete entire subclauses.
Page 58, subclause 10.7.4
Delete test case TC28407 from the list of test cases.
Page 60, subclause 10.7.5.3
Delete test case TC27416 from the list of test cases.
Page 60, subclause 10.7.5.4
Delete test case TC27405 from the first list of test cases and replace delete TC27407 by TC27411 in from
the second list of test cases.

---------------------- Page: 6 ----------------------

SIST TBR 004 E1:2004/A1:2004
Page 5
TBR 4: November 1995/A1: December 1997
Page 61, subclause 10.7.5.5
Add the following text to the end of the subclause:
Test:
NOTE: It is not possible to replicate the conditions required to bring the IUT into the state
required to perform the test, and therefore no tests is specified.
Page 61, subclause 10.8
Delete test case TC28408 from the list of test cases.
Page 63, subclause 10.9.4
Delete test cases TC24007 and TC28019 from the list of test cases.
Page 124, subclause 11.4.2.2.2
Delete entire subclause.
Page 127, subclause 11.4.3.4.2
Delete test case TC11001 from the list of test cases.
Page 128, subclause 11.4.6.1
Delete entire subclause.
Page 130, subclause 11.4.6.3
Add test cases TC11908 and TC11909 to the list of test cases.
Page 130 subclause 11.4.6.5.1
Amend text as shown below:
Requirement: When a message other than SETUP, DISCONNECT, RELEASE or RELEASE
COMPLETE is received which has one or more mandatory information elements missing, no action shall
be taken on the message and no state change shall occur. A STATUS message shall then be returned
with Cause #96 "mandatory information element is missing".
When a SETUP or RELEASE message is received which has one or more mandatory information
elements missing, a RELEASE COMPLETE message shall be returned.
Other actions taken on receipt of a RELEASE message with the Cause information element missing shall
be the same as if a RELEASE message with Cause # 31 "normal, unspecified" had been received.
When a RELEASE message is received as the first clearing message and with a Cause information
element missing, the actions taken shall be the same as if a RELEASE message with Cause #31 "normal,
unspecified" was received (see subclause 11.4.3).
When a DISCONNECT message is received with the Cause information element missing, the actions
taken shall be the same as if a DISCONNECT message with Cause #31 "normal, unspecified" was
received (see subclause 11.4.3).
When a RELEASE COMPLETE message is received with a Cause information element missing, it shall
be assumed that a RELEASE COMPLETE message was received with Cause #31 "normal, unspecified".

---------------------- Page: 7 ----------------------

SIST TBR 004 E1:2004/A1:2004
Page 6
TBR 4: November 1995/A1: December 1997
Test: This requirement shall be tested according to the procedures of annex D, test cases TC10015,
TC10115, TC10222, TC11028 and TC11029.
NOTE:     No test for the action on receipt of a DISCONNECT message with the Cause
information element missing is specified in this version of the TBR because it was not
possible to develop and verify a test due to shortage of time and resources. ETSI
intends to develop and verify an appropriate test for inclusion in a later version.
Page 131, subclause 11.4.6.5.2
Delete entire subclause.
Page 131, subclause 11.4.6.6.1
Amend text as shown below:
Requirement: When a message is received which has one or more unrecognized information elements,
the TE shall check whether any are encoded to indicate "comprehension required" (refer to table 11.27 for
information element identifiers reserved with this meaning). If any unrecognized information element is
encoded to indicate "comprehension required", then the procedures in subclause 11.4.6.5.1 are followed;
i.e. as if a "missing mandatory information element" error condition had occurred. If all unrecognized
information elements are not encoded to indicate "comprehension required", then the TE shall proceed as
follows.

---------------------- Page: 8 ----------------------

SIST TBR 004 E1:2004/A1:2004
Page 7
TBR 4: November 1995/A1: December 1997
Action shall be taken on the message and those information elements which are recognized and have
valid content. When the received message is other than DISCONNECT, RELEASE or RELEASE
COMPLETE, a STATUS message may be returned containing one Cause information element. The
STATUS message shall indicate the Call state of the receiver after taking action on the message. The
Cause information element shall contain Cause #99 "information element non-existent or not
implemented", and the diagnostic field, if present, shall contain the information element identifier for each
information element which was unrecognized.
Subsequent actions are determined by the sender of the unrecognized information elements. If a clearing
message contains one or more unrecognized information elements, the error is reported to the local TE in
the following manner:
a)         when a DISCONNECT message is received which has one or more unrecognized
information elements, a RELEASE message shall be returned;
b)- when a RELEASE message is received which has one or more unrecognized
information elements, a RELEASE COMPLETE shall be returned;
c)         when a RELEASE COMPLETE message is received which has one or more
unrecognized information elements, no action shall be taken on the unrecognized
information.
Test: This requirement shall be tested according to the procedures of annex D, test cases TC10027,
TC10028, TC10718, TC11118 and TC11920.
Page 134, subclause 11.5
Amend text as indicated below:
DefinitionRequirement: The duration of timer T305 shall beis in the range 15 s to 45 s.
NOTE 1: A value of 30 s is recommended.
The duration of timer T308 shall beis in the range 3 s to 15 s.
NOTE 2: A value of 4 s is recommended.
Test: This requirement shall be tested according to the procedures of annex D, test cases TC21001 and
TC21006.
Page 134 to 135, clause A.2.
Replace entire subclause A.2. by the following:
A.2   Layer 1 and overvoltage requirements TBR-RT
Table A.1: Layer 1 and overvoltage conditions table
Refer- Condition Status Support Comment
ence. (Y/N)
1 Is TE mains powered? o Affects requirements in
clause 8

---------------------- Page: 9 ----------------------

SIST TBR 004 E1:2004/A1:2004
Page 8
TBR 4: November 1995/A1: December 1997
Table A.2: Overvoltage requirements table
No. Reference TBR Requirement Status Support
(Y/N)
1 8.1 Impulse transfer from mains, common mode c1
2 8.2 Impulse transfer from mains, transverse mode c1
3 8.3 Conversion of common mode to transverse mode m
c1 = m if A1.1 else n/a
Table A.3: Layer 1 physical characteristics requirements table
No. Reference TBR Requirement Status Support
(Y/N)
1 9.1.1 Hardwiring m
2 9.1.2 Alternative connection method o
Table A.4: Layer 1 output port electrical requirements table
No. Reference TBR Requirement Status Support
(Y/N)
1 9.2.1 Waveform shape m
2 9.2.2 Impedance towards ground m
3 9.2.3 Clock accuracy m
4 9.2.4a Output jitter, input timing derived from the same o1
primary rate access
5 9.2.4b Output jitter, input timing derived from a different o1
primary rate access
6 9.2.4c Output jitter, input timing derived from a non-ISDN o1
2 048 kbit/s access
7 9.2.4d Output jitter, input timing derived from internal o1
source.
8 9.2.4e Output jitter, input timing derived from dedicated o1
external reference
o1. One or more options shall be chosen.
Table A.5: Layer 1 input port electrical requirements table
...